Hi Nicola, I have always proposed the use of iPar and pPar when you want to describe the relationship between parameters as an important part of the design intent. The benefit then is that you can have an instance of your design under test (either in the test bench, or in the real design) and pass in the parameters you need, with no reference to any global variables. iPar tends to be used less frequently than pPar (in designs mostly used in leaf devices). So for example, if I have a common width that is used in a current mirror, I might have defined that using pPar("wnmir") or something like that - and used it on all the transistors in the current mirror. Then I can choose when I instantiate the device to change all of the widths at once, but keep the current mirror ratios correct. In terms of doing the sweeps however, it really doesn't matter too much. Another approach you can take is to use the "parameters" in ADE XL/Explorer/Assembler; this means you can then keep the design unedited, but define the relationships between the parameters on each device (e.g. matched parameters and so on) and you can sweep them without having to actually edit the schematic. Regards, Andrew.![]()
↧