Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 14391
  • 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

AMS simulation using smartview extraction

HasanArd

Hi all,

I am running a mixed-signal simulation (xrun netlister) in ADE assembler. I am using smartview extracted for this simulation. 

Got some errors when I am netlisting. Does anyone know what these errors are and why?

\e *Error* parseString: argument #1 should be either a string or a symbol (type template = "SSg") - nil
\o ERROR (OSSHNL-411): Stopping netlisting due to SKILL error while formatting devices. To bypass this
\o check, set the environment variable oss.core stopNetlistingOnFormatterError
\o
\o ERROR (OSSHNL-514): Netlist generation failed because of the errors reported above. The netlist might not have been generated at all, or the generated netlist could be corrupt. Fix the reported errors and regenerate the netlist.
\e *ERROR* (AMS-1245): AMS UNL netlisting has failed because of errors in the design.
\e Right-click the test name on the Outputs assistant pane
\e and check Output Log->Netlister Log for errors.
\e Correct your design and netlist again.
\o ...unsuccessful.
\e *Error* Error during netlisting of design for the point ID (6 1).
\e ("error" 0 t nil ("*Error* "))
\e
\e
\o
\o *Error* Error ID = 5012
\o *Error* Error Msg = Failed to create netlist.

  • Unless there's some more information in the Netlister Log that's mentioned, it's going to be hard to pinpoint here. Assuming you can reproduce this with SImulation->Netlist->Create in ADE Explorer (say - descend into the test and see whether you can do that), then you could try doing:

    _stacktrace=50
    sstatus(errsetTrace t)

    and see if you get a more comprehensive stack trace when you try to create the netlist. Not sure which version you're using (you didn't mention), but I'd suggest trying with the latest hot fix (IC6.1.8 or ICADVM20.1 ISR16) and if it still occurs, then contacting customer support would be sensible. It might be a PDK issue - but we should be able to help pinpoint the problem.

    Andrew

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.