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

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

Reply

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

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.