Forum Discussion
New Contributorlocalparam and parameter values in Synthesis report
New ContributorThis is an old thread, but I found it because I have the same question. I may have a large number of localparams in a verilog module with complicated expressions. I would like to ensure that all of them are calculated as I expect, that I got operator precedence, rounding and such right.
Now since Quartus calculates all these localparams at some point, it would be very useful to be able to see the result in a report. I tried Parameter Settings by Entity Instance, but it only shows parameters, not localparams.
I would really not have to set up a simulation just to be able to see values that are already computed. Is there a way to see them? Would changing them from localparams to parameters (temporarily) do the trick?
Super ContributorOnly parameter will show in report. Yes, you can change localparams to parameters. If you want to use both localparam and parameter, you can use mix approach by specifying localparam equal to the parameter.
- cblixt1
Well, take it as a suggestion for improvement then.
Using localparam instead of parameter is a way to protect constants from inadvertently being modified by instantiation, so assigning them from parameters is pointless. I tried to temporarily change localparams to parameters and that works, but it is of course tedious.
Also the display in Parameter Settings by Entity Instance is not the best, with some parameters (for some reason) being of the type unsigned binary being displayed in binary rather than decimal or hexadecimal.
- ShengN_altera
Sure, I had filed an enhancement ticket for the request
