• 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. RF Design
  3. Extract parasitic capacitance of MOSFET

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 63
  • Views 16119
  • 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

Extract parasitic capacitance of MOSFET

Duy Hien
Duy Hien over 10 years ago

Hi everyone,

I tried to extract parasitic capacitance of MOSFET. I use Cadence IC615, in ADE L: Result -> Annotate -> Show parasitics. And what I see is:

Error* hdbGetLibName: argument #1 should be a hierarchical database configuration object (type template = "h") - nil
<<< Stack Trace >>>
(... in _mspsConfigToSchExt ...)
(... in _mspsInitConfData ...)
(... in _mspsGetConfData ...)
(... in _mspsGetSessionParCV ...)
(... in _mspsBackAnnotate ...)
(... in _mspsBAPushHilight ...)
_mspsBAPushHilight(path schCV ses)
when((_mspsIsSchInWindow(window(ses)) && (_mspsFlowIsEnabled ses ?flow flow)) (path = strcat(geGetInstHier(&) "/")) if(index(path "//") then (path = "/")) (schCV = geGetWindowCellView(window(ses))) _mspsBAPushHilight(path schCV ses))
foreach(ses (sessionContext->sessions) when((_mspsIsSchInWindow(&) && (_mspsFlowIsEnabled ses ?flow flow)) (path = strcat(& "/")) if(index(path "//") then (path = "/")) (schCV = geGetWindowCellView(&)) _mspsBAPushHilight(path schCV ses)))
progn((sessionContext = _mspsGetSessionContext(sessionId)) foreach(ses (sessionContext->sessions) when((& && &) (path = &) if(& then &) (schCV = &) _mspsBAPushHilight(path schCV ses))))
(val = progn((sessionContext = _mspsGetSessionContext(sessionId)) foreach(ses (sessionContext->sessions) when(& & & & &))))
let((val prevFlow) (prevFlow = _mspsGetFlow(sessionId)) _mspsSetFlow(sessionId flow) (val = progn((sessionContext = &) foreach(ses & &))) _mspsSetFlow(sessionId prevFlow) ... )
_mspsWithFlow(sessionId flow (sessionContext = _mspsGetSessionContext(sessionId)) foreach(ses (sessionContext->sessions) when((& && &) (path = &) if(& then &) (schCV = &) _mspsBAPushHilight(path schCV ses))))

I don't know what these codes mean. Please explain it to me. Thank in advanced.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I believe (from a quick scan of the reported issues) that this can happen if you are not descended into a schematic view that corresponds to an out-of-context view alongside an extracted view. In other words, you need to descend into the schematic view corresponding to your extracted view.

    If that's not it, please contact customer support so that we can look at your data with you.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Duy Hien
    Duy Hien over 10 years ago

    Dear Mr. Beckett,

    Thank for your time.

    I ran a basic DC simulation: Save DC Operating Point

    I didn't descend into any symbol but the error still happened, I cannot see the parasitic.

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

    I'm not that sure how the menu appears (it should be greyed out). The Show Parasitics menu should only appear (and only is useful) if you have:

    1. Done a parasitic extraction using QRC
    2. Simulated using the extracted view that was produced
    3. Descended down into the schematic view corresponding to the extracted view (usually referred to as "out of context"). This part of the check was only added during an IC615 hotfix, so maybe you're using too early a version for this.

    Clearly in this case you are at your testbench level rather than in the out of context view. In fact I'd be surprised if you've done a QRC extraction here -  so that's why I can't work out how the menus have appeared at all!

    Kind 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