Stats

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

Simulation with dspf_include

BrJaWr

I'm trying to make a single testbench that will work with schematic or dspf simulations with ADE.  When switching from the schematic to dspf the hierarchical delimiter changes from "/" to ".".  Reading through old messages it appears that "/" is always for a schematic and "." for a netlist.  I also see that some extraction tools will create an amap file to take care of translation.  

I'm wondering if there is anyway to change the netlist delimiter to use a "/" so I can only have one testbench?  Alternatively, can an amap file be created manually?  Is the format documented anywhere?  In our case we are making sure the signal names exist in both the schematic and in the dspf so naming shouldn't be required.

I can think of some ugly was to do this with skill and/or hierarchical probes but I really don't want to have to mess with that...

Thanks

  • Andrew Beckett

    You should take a look at What’s New in Virtuoso IC6.1.8 and ICADVM18.1 ISR3 - there's a section there on a new capability for performing out-of-context probing for DSPF include files and DSPF views.

    The names with "/" are "schematic" names, and the mapping to "netlist" names is performed at netlisting time, and so only gets generated for things that are actually netlisted. The format is not documented (and liable to change), and I'm not convinced that would be the right solution anyway. The newly released approach is a solution to solve this problem by giving hints as to how the mapping should be performed for external DSPF files.

    Regards,

    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.