• 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 SKILL
  3. Alternative option to asiMapOutputName

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 144
  • Views 13011
  • 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

Alternative option to asiMapOutputName

adeuser777
adeuser777 over 12 years ago

Hi,

I am using asiMapOutputName command to get terminal to output mapping information. Ex: asiMapOutputName("netlistDir" 'terminal "i0/i1%out". And it returns it corresponding output name. Something like, "i0/i1:1".

We use this methodology to create device and instance terminals to its output name mapping. This mapping information is used by our downstram tools. On a big design (pure schematic), with around 10000 different terminals, asiMapOutputName takes around 5 hrs to complete. Do we have a better way to get terminal to output mapping information?

 

Thanks,

Ram 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

     If you ran a simulation, you would have been able to do:

    openResults("/path/to/sim/results/psf")
    selectResult('tran) ; or whatever analysis
    mapTable=makeTable('myMap nil)
    foreach((sch net) outputs() outputs(?map nil)
      mapTable[sch]=net
    )

    and then you have a table where you can do mapTable["/out"] and get "out" or whatever mapping has occurred.

    If you need to do this pre-sim, please contact customer support - it might need an enhancement to allow faster access to the mapping information.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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