Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13348
  • 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

how to save signals in hierarchy using ocean save()?

Wing2

I am using the ams simulator (part of the circuit is in extracted view and the rest in digital domain). I tried using the following and it all gave this error: *Error* hdbResolveConstants: argument #2 should a string (type template = "ht") - nil

Each of the following net names has been tried individually and separately:

            (save 'v "TestBench/I1/I0/N108")  ; does not work
            (save 'v "/TestBench/I1/I0/N108") ; does not work
            (save 'v "/I1/I0/N108")           ; does not work
            (save 'v "I1/I0/N108")            ; does not work
            (save ?categ 'analog 'v "/I1/I0/N108")           ; does not work
            (save ?categ 'analog 'v "I1/I0/N108")           ; does not work
            (save ?categ 'analog 'v "TestBench/I1/I0/N108")           ; does not work
            (save ?categ 'analog 'v "/TestBench/I1/I0/N108")           ; does not work
            (save 'v "TestBench:I1:I0:N108")           ; does not work
            (save 'v "I1:I0:N108")           ; does not work
            (save 'v "I1:I0")           ; does not work
            (save 'v "TestBench.I1.I0.N108")           ; does not work
            (save ?categ 'analog 'v "TestBench.I1.I0.N108")           ; does not work
            (save 'v "/I1/I0/+0/D") ; does not work.

/I1/I0 is the instance with the extracted view and N108 is the net name inside that extracted view.

I tried using the ADE window and use Output -> to be saved. Both the "select from HED" and "select on schematic" are tried. Every time I click on a net, I see this error in the CIW: *Error* parseString: argument #1 should be either a string or a symbol (type template "SS") - nil

 The cadence version that I am using is IC6.1.4

 Thanks!

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.