Something strange with SOPC

OH NO ! ? ?????

If you have statemachines you would code something like :

// statemachine definition

//------------------------

parameter [2:0] /* synopsys enum states */

PLL_IL = 3'd0,

PLL_FL = 3'd1,

PLL_RC = 3'd2,

PLL_NC = 3'd3,

PLL_GO = 3'd4;

// define state variable(s)

reg [2:0] /* synopsys enum states */ pll_init_state;

// synopsys state_vector pll_init_state

If i understand that what you have posted here right, then the sopc component editor cannot handle parameter [x:y] but quartus can.

I had a quick look at ALL sources where i had these problems as posted before and ALL have this parameter with [x:y]. Now i understand why i can work with sopc component editor if there are no statemachines in verilog.

Now it is clear, Quartus SOPC has a Bug if the component sources have verilog statemachines.

I hope this BUG gets fixed soon. Altera ????

And for the future ... i wish i would get a clear message that tell why what and where instead of error 3 or 10000 ...

Regards.

Michael Schmitt