Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 16070
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Syntax error

manudupouy

hello,

I am in trouble. I am using Assura LVS (VLDB) to verify my design. My DK is CMRF7SF from IBM. When I try to run Assura LVS, it returns this error:

Top cell  inverter schematic intro_microE vs inverter layout intro_microE

l 1.800000e-07 wt 6.000000e-07 nf 1 m 1 par "iPar("m")" rf 0 gcon 1 psp 0 mSwitch 0 idg 0
                                                                                                 ^
SYNTAX ERROR found at line 1 column 53 of file *string*
*Error* lineread/read: syntax error encountered in input
******* Non-recoverable error (no top-level or error handler)
******* Exiting program ...


*****  nvn fork terminated abnormally  *****


*WARNING* nvn exit with bad status
*WARNING* Status 65280
*WARNING* Assura execution terminated

How can I solve this problem?

Thanks in advance.

Emmanuel

Parents

  • 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.

Reply

  • 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.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.