Stats

  • Locked Locked
  • Replies 5
  • Subscribers 150
  • Views 2454
  • 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

maeCreateNetlistForCorner command is adding a _schematic to the subckt name, the same maestro view is generating the netlist without the suffix when netlisted from maestro interface

MFahmy

Hello,

I have a maestro view with a single test and referring to a top level schematic (no config view), also there are no instances with the same name from different libraries, and the subckt name start with a characted 

when I use the maeCreateNetlistForCorner command in the CIW or a skill file the subckt name get appended with a "_schematic" suffix and the confusing part is that when I netlist the same test (rightclick->Netlist_>create) and doing a diff,  the only difference I see aside from the data is the suffix "_schematic"

I am already setting the env var "maestro.polo" "supportDspfMasterOption" and it is set correctly if checked using envGetVal("maestro.polo" "supportDspfMasterOption")

- what could cause such a discrepancy between using the maeCreateNetlistForCorner and netlisting from the test ?

- is there a work around ?

Virtuoso version ICADVM20.1-64b 05/11/2023 
Sub-version ICADVM20.1-64b.500.28.EHF13629

Thanks, 

Fahmy 

  • ShawnLogan

    Dear Fahmy,

    You mentioned:

    MFahmy said:
    when I netlist the same test (rightclick->Netlist_>create)

    Did you actually re-create the netlist?

    That command may only display the netlist if one exists. If you want to compare the netlists for the same schematic at one time using maeCreateNetlistForCorner() and the ADE netlister, did you try to re-create the netlist in ADE (rightclick->Netlist->Recreate) and then compare it to the netlist generated by maeCreaetNetlistForCorner()?

    Shawn

  • MFahmy
    in reply to ShawnLogan

    Thanks for the reply,

    yes, i did re-recreate the netlist, and made sure the time stamps were new, I even deleted the previous files to make sure I am always creating a new netlist for the two netlists being compared 

    I have also to say  that the issue is nondeterministic, now I restarted virtuoso and I can't reproduce it anymore, and I don't recall having the issue few days back using the same script

  • Andrew Beckett
    in reply to MFahmy

    See the support links referenced in this thread.

    Andrew

  • MFahmy
    in reply to Andrew Beckett

    Hi Andrew, 

    Thanks for the link, I found some useful info there,

    - can I set the hnlRegenerateCellNames variable in  the CIW and if so, is it just setting the variable i.e hnlRegenerateCellNames = "All"  or do I need to to use the envSetVal

    - I am honestly not sure whether to use All or OnlyDuplicates and the performance trade-off it may cause, I don't have duplicates in the view being netlisted and the issue is not occurring each time, I went through the cases in the link, and it doesn't seem any would apply

    Thanks, 

    Fahmy 

  • Andrew Beckett
    in reply to MFahmy

    I think the choices are because we didn't have enough data to be confident there were no side effects. The plan however was to change the default to "All" in the upcoming IC23.1 release; an issue was found related to handling of schematic PCells (which has also been fixed now for IC23.1); I'm not sure whether we've put back in the change to make All the default yet, but in general "All" should be a safe choice.

    If you are generating the netlists in the foreground with a script, then setting the variable in the CIW would be sufficient. I don't think there's any significant performance issue by using this.

    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.