Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 2979
  • 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 perform out-of-context probing with dspf file extracted from Calibre PEX

TzuYun Chang

Hi,

I designed a layout of a BGR with IC23.1 and used Calibre PEX to extract the parasitics of the design as a dspf file. I include the dspf file in simulation under the Setup > Simulation Files > Parasitic Files (DSPF) section. As I need to debug the BGR layout, I want to do out-of-context probing to probe the nets within it; however, despite modifying the ./.simrc in the simulation directory to include the dspf options as below, the netlist names still don't match and doesn't seem to be different to the netlist names before adding the dspf options. I am wondering if there is a way for me to check if the .simrc file is run or somewhere that I can specify the .simrc location. Additionally, if my setup of the dspfFileEnvOptions is correct.

dspfFileEnvOptions = '(
(nil
spfFileNameMappingFormat "cdl"
spfFileHierDelimiter "/"
spfFileTermDelimiter ":"
spfFileNetMapping "mixed"
spfFileDevicePrefixForTermCurrent "M"
spfFileAddPrefixToDevice "t"
spfFileTerminalMapping "lower"
)
)

  • Hi,

    I'm also struggling with this currently. I do see that my netlist gets modified by the .simrc file, but the mapping remains incorrect, even when following the dspf mapping RAK as presented by Cadence. From your example above, I see you're missing other lines that are required as per RAK document. See.

    The correctness of your mapping above depends on the syntax of your dspf, so we can't say, but you should be able to see it at the header of your dspf. Perhaps you get better luck than me when running through the RAK tutorial found in:

    support.cadence.com/.../articleattachmentportal

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.