Syntax error

Emmanuel,

It looks as if one of the parameters in the CDF for whichever device this is corresponding to has the wrong setting for parseAsCEL (and maybe parseAsNumber).

I'd suggest you look in your run directory and do:

vldbToVnl RUNNAME.sdb

(whatever RUNNAME is in your case) and maybe redirect the output to a file. Look for the iPar but - it's that which is causing the problem. This should tell you the component that is the problem, and what type of component it is. You can then look in the CDF for that device.

If it's a PDK device though, you may need to contact IBM over this unless you're happy fixing it yourself. You'd need to look in the CDF for that device, at the auLvs simulation information, and find out how the parameter "par" is being netlist - it might have come from a "propMapping" to another parameter name. Once you've identified what the parameter name is called, you can see whether that CDF parameter has parseAsNumber=yes/parseAsCEL=yes.

If that's all a mystery, contacting customer support might be a good approach! Giving precise instructions is quite hard when I don't have access to this PDK and can't see your data.

Regards,

Andrew.

Hi Andrew,

Thank you for your help. But in this case, it was a problem with Cadence configuration.

I forgot to initialize 2 variables:

export CDS_LOAD_ENV=CSF
export CDS_Netlisting_Mode=Analog

Oh, so much time wasted for this detail ! Why Cadence is not more user friendly?

Best regards and thank you again.

Emmanuel

The first one isn't relevant here. The second one is. This is not a matter of being user friendly - there are two modes of operation (for long standing legacy compatibility reasons) - and if you are ADE-based then you have to set CDS_Netlisting_Mode. The tools have both a digital and analog netlister which controls how CDF parameters are used (or not) and we have customers using both flows. $CDS_Netlisting_Mode is pretty much one of the few essential variables to set in your environment (sorry I did not spot this as being the root cause - usually people hit the problem during the simulation phase and the symptoms there I am more familiar with - plus this particular symptom is PDK-dependent too).

I'm sure contacting customer support would have avoided you wasting time...

Regards,

Andrew.