• 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. Custom netlisting procedure

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 14584
  • 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

Custom netlisting procedure

jmss
jmss over 13 years ago

Hi,

I am trying to customize the netlist procedure for hspice.

In the hspice view I configured these properties:

  • hnlHspiceFormatInst = dummy()
  • hnlHspiceParamList = hnlHspiceMOSfetParamList

Then I wrote dummy() like this:

procedure(dummy()
printf("Custom netlisting procedure...\n")
inst = hnlCurrentInst
print(inst->??)
formatter = nlGetFormatter(inst)
;nlPrintInstName(formatter, inst)
)

When I run netlisting with:

  1. simInitEnvWithArgs(runDir libName cellName viewName "hspice" t)
  2. simReNetlistAll = 't
  3. simNetlistHier = 't
  4. netlist()

I get this error:

Running netlist

Begin Incremental Netlisting Sep 23 18:22:53 2011

Custom netlisting procedure...

(db:0x151eca14 cellView db:0x151ecd12 objType "inst" prop nil bBox ((-1.925 -1.8625) (-0.725 -1.25)) children nil groupMembers nil isAnyInst t isShape nil matchPoints nil net nil parent nil pin nil purpose "cell" textDisplays nil assocTextDisplays nil markers nil figGroup nil baseName "MN1" cellName "nmos_dummy" instHeader db:0x151ec612 instTerms (db:0x151ec11c db:0x151ec11b db:0x151ec11a db:0x151ec119) libName "devLib" master db:0x151edd92 name "MN1" numInst 1 viewName "symbol" conns (db:0x151ec11c db:0x151ec11b db:0x151ec11a db:0x151ec119) mag 1.0 orient "R0" status nil transform ((-1.5 -1.5) "R0" 1.0) xy (-1.5 -1.5) cluster nil blockages nil physOnly nil source "netlist")

 

*Error* (Default-reader-method) generic:nlGetFormatter class:dbobject

End netlisting Sep 23 17:47:44 2011

 

I can't find anything on this error. Is it related to mixing nl and hnl functions?

 

Any help would be appreciated.

 

Best regards,

João M. S. Silva

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    The nl functions are for the "direct" netlisters, as used in ADE. So that would be where the netlister is hspiceD. The hspice netlister is a traditional hnl netlister.

    So you are mixing in the nl functions in an hnl netlister, and that doesn't make sense.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jmss
    jmss over 13 years ago

     Hi Andrew,

     Thanks.

     Can you show the skeleton for an hnl-based netlister?

     Regards,

    João M. S. Silva

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Hi Joao,

    I don't have one to hand (I don't tend to see too many questions about the hspice rather than hspiceD netlister). Best thing is to log a service request for this.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jmss
    jmss over 13 years ago

     Thanks, I've created an SR.

     Just one more question: is that because hspice will be dropped and hspiceD is to be made the one official netlisting method?

     Regards.

     João M. S. Silva

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    No, there are no plans to drop hspice in favour of hspiceD. They're just different interfaces (one from schematic, not CDF based, and the other from ADE and is CDF-based).

    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