Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 6037
  • 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

Fail to generate netlist as cell view specified to a SPICE file in Hierarchy Editor

Leo66

Hi guys, I'm going to running my post-simulation with parasitic extracted, and the netlist of my device has been generated as "cell.pex.netlist", the directory is "/net/server4a/export/user/Desktop/cell.pex.netlist". When I select the cell view of the device as "Specify SPICE Source File" in Hierarchy Editor, it's always unsuccessful to generate the netlist in ADE. 

A message says:

*Error* _emsGetMsg: argument #3 should be an integer (type template = "ooxtl") - "EMS_ERROR"

Does anyone have the same problem? What's this mean?

  • Which IC sub-version are you using? (Help->About will show this). Which netlister are you running (i.e. which simulator are you using in ADE)?

    The error message is a low-level error and something has gone badly enough wrong that even the error message reporting is being called with the wrong arguments. There's a change request (CCR) on a similar issue reported and fixed in 6.1.8/20.1 ISR30

    Andrew

  • in reply to Andrew Beckett

    Hi, IC sub-version is IC6.1.8-64b.500.27. Simulator is ADE_XL? I'm not sure if it's enough.

  • in reply to Leo66

    ADE XL is not a simulator - it's a simulation environment. Presumably the simulator is Spectre, AMS Designer or maybe something else (maybe a third-party simulator?).

    You're certainly using a hotfix version from before the fix I mentioned above. Can you try the latest hotfix (the current is IC6.1.8-64b.500.35)?

    Andrew

  • in reply to Andrew Beckett

    Thanks Andrew, simulator is Spectre, but I can't try any new version before my public server upgrades it. 

    For now, I select CDF-edit and designate the termOrder & componentName to my device, while include the netlist file into Model Library. It worked, but seems only one component can be attached to the netlist file with the same termOrder at one time.

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.