Stats

  • Locked Locked
  • Replies 8
  • Subscribers 127
  • Views 4234
  • 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

Netlister's subcircuit naming convention

ZoltanT

Hi everybody,

I just stumbled upon a case where the netlister generated subcircuit names as `subckt libraryname_cellname_cellviewname port_list` instead of the usual `subckt cellname port_list` in the input.scs. How can this be enabled or disabled?

It made the simulation with dspf file problematic due to the different subcircuit naming. I overcome the issue by simply rebuilding the ADE's state. I am just curious what could have caused it.

Thanks,

Zoltan

The used Cadence version is ICADV 12.30.721.

------------------------------
Update: I've just found a saved ADE state, where I have found subcircuits with names with and without _schematic suffix. Also in this case there was no libraryname_ prefix.

  • Andrew Beckett

    Zoltan,

    There's a number of cases where the view name gets appended. Sometimes it's because the same cell exists in more than one library; sometimes it's because instance or occurrence bindings have been used in the config which means that it has to be able to distinguish between different cells. Sometimes it's because the incremental netlister gets its state info messed up - and forcing a renetlist can fix it (there's a variable for this, but it's bad to set it in general because it can lead to performance loss). You might be able to clear out the netlist directory (if you're using ADE Explorer/Assembler, there's a tmp dir that needs clearing out too), but the best thing would be to contact customer support. Please mention CCR 1592892 where this is discussed in length, and a solution is being pursued to allow spectre to be told about the mapping from the DSPF subckt name to the netlister subckt name.

    Andrew.

  • Ponien Lin
    in reply to Andrew Beckett

    Hi Andrew, I met the same issue. It adds "_schematic" to the cell name so the dspf include fail.  Could you point me where to find the discussion of "CCR 1592892"?

  • Andrew Beckett
    in reply to Ponien Lin

    There is no public discussion on this - I mentioned that CCR in the previous reply in order to suggest that Zoltan contacted customer support, and then referenced that (internal Cadence Change Request) number so that when the Application Engineer dealing with his case filed another issue with R&D, it could reference that existing internal discussion.

    So you should do the same thing...

    Andrew

  • Frank Wiedmann
    in reply to Ponien Lin

    I just got a notice that this CCR has been implemented in ISR24 of IC 6.1.8 and ICADVM 20.1.

  • lchensd
    in reply to Frank Wiedmann

    I recently ran into this exact issue running ic201_isr24. The netlister randomly appends the _schematic suffix to a subckt and it is making the use of dspf netlists unreliable.

  • Andrew Beckett
    in reply to lchensd

    The "randomness" is supposed to be fixed in ISR24 - see https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/51922/netlist-creation-issue/1383953#1383953 . There are still cases where the _schematic might be added (if instance-based or occurrence-based bindings are used). You might want to try setting:

    envSetVal("maestro.polo" "supportDspfMasterOption" 'boolean t)

    (in the .cdsinit). If that doesn't fix it, please contact customer support.

    Andrew

  • lchensd
    in reply to Andrew Beckett

    Thank you, Andrew! I am using instance-based binding, so perhaps that is the root cause. I will try the above setting. 

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.