• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Accessing spectre simulation results in an ocean script

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15331
  • 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

Accessing spectre simulation results in an ocean script

berbagci
berbagci over 8 years ago

Hi Andrew,

I have a very weird problem. I have checked other posts but couldn't figure it out. Hence, I decided to post here.

So I'm simulating a design in spectre simulator (an extracted netlist in spectre format). I have an ocean script and simulation runs without any problem. I want to do some calculations with the results.

However, I cannot seem to access any of the low level nets (although I can see them with outputs() command). 

For instance after typing outputs(), I get:

("/C/N_XC11/XLC/TCONF<128>_XC11/XLC/XBLE<2>/XLUT/XLUT_L1<0>/XI0<0>/MM2<0>_g" "/C/N_XC11/XLC/TCONFB<128>_XC11/XLC/XBLE<2>/XLUT/XLUT_L1<0>/XI0<0>/MM13<0>_g" "/C/N_XC11/XLC/TCONF<130>_XC11/XLC/XBLE<2>/XLUT/XLUT_L1<0>/XI0<0>/MM2<2>_g" "/C/N_XC11/XLC/TCONFB<130>_XC11/XLC/XBLE<2>/XLUT/XLUT_L1<0>/XI0<0>/MM13<2>_g" "/C/N_XC11/XLC/VSS_FIRE<5>_XC11/XLC/XBLE<2>/XLUT/XOTP<2>/XPUF_CELL/MHCI_TR_s" "/C/N_VSS_XCH_DUMMY/X33/XI8/XI203/MM5_s"

)

As seen here, I'm trying to access some low level nets. 

when I try getData("/C/N_VSS_XCH_DUMMY/X33/XI8/XI203/MM5_s"), it returns nil. Also tried to access nets that were part of an array (<>) by using "\", that didn't work either.

I tried getData("C.N_VSS_XCH_DUMMY.X33.XI8.XI203.MM5_s"), again getting nil. For some reason I cannot access any of the available nets. I checked runObjFile, directories (netlist>map, amap, psf etc.). Everything seems to be ok. I will be glad if you can help me out. 

Any help greatly appreciated. Thanks

Burak

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Burak,

    It's a bit odd that Calibre is creating hierarchical names with / as the hierarchy separator. Assuming this is an extracted view, I'm not sure how they are creating the view because a "/" should be an illegal character in the name. Maybe it's being done directly in OA (I'd have to check what's allowed in OpenAccess), but if so, it's breaking Virtuoso's allowed namespace, so I think you should take that up with Mentor. If it's an included netlist, that's odd too because i would have expected a "." as the hierarchy separator then.

    Generally speaking if hierarchical names are used in an extracted view, they should be encoded using the "CDBAflat" name space (which uses the pipe "|" character as the hierarchy separator).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Burak,

    It's a bit odd that Calibre is creating hierarchical names with / as the hierarchy separator. Assuming this is an extracted view, I'm not sure how they are creating the view because a "/" should be an illegal character in the name. Maybe it's being done directly in OA (I'd have to check what's allowed in OpenAccess), but if so, it's breaking Virtuoso's allowed namespace, so I think you should take that up with Mentor. If it's an included netlist, that's odd too because i would have expected a "." as the hierarchy separator then.

    Generally speaking if hierarchical names are used in an extracted view, they should be encoded using the "CDBAflat" name space (which uses the pipe "|" character as the hierarchy separator).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information