• 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 Design
  3. deepprobe not working for extracted cellview in ADE-XL run...

Stats

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

deepprobe not working for extracted cellview in ADE-XL run.

RFStuff
RFStuff over 6 years ago

Dear All,

I am using  deepprobe to measure the voltage of a net that is 1 hierarchy down in the PEX .spf file.

In the .spf file I have, the following line:-

R221_1 Xbuf<0>/MMNINP:G clkout_0:218 129.365.

The extracted cellView name is clkdiv.

In, the schematic viewer I have added a deepprobe with net name Xbuf\<0\>\/MMNINP\:G.

But, it is NOT probing the voltage. I see the following warning in output.log file.

WARNING (SFE-411): "input.scs" 391: Hierarchical node `clkdiv.XI221<0>/MMNINM\:G' does not exist in design. It will be treated as a regular (non-hierarchical) node.
WARNING (SFE-411): "input.scs" 392: Hierarchical node `clkdiv.XI221<0>/MMNINP\:G' does not exist in design. It will be treated as a regular (non-hierarchical) node.

Could anybody please tell, why it is happening like this and how to fix this ?

Kind Regards,

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Unfortunately I think this is something that needs fixing in Spectre. You need to add the backslash before the <,>,/ and : characters because they're not legal in spectre, but unfortunately it's retaining the \ before the colon and this is what leads to the problem (I think). To get this fixed you should contact customer support with a test case illustrating the problem (I hacked one together, but don't have the bandwidth to file this with R&D, and it would better to provide a real-life example whereas mine was completely artificial).

    I don't think there's a workaround for now other than modifying the DSPF file to alter the colon to be some other character. 

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RFStuff
    RFStuff over 6 years ago in reply to Andrew Beckett

    Dear Andrew,

    I replaced all Xbuf<0>/MMNINP:G to Xbuf<0>/MMNINP.G iin the netlist.spf file.

    I used the probe name in deepprobe as:- clkdiv.Xbuf\<0\>\/MMNINP.G.

    But it is still shwoing the following:-

    WARNING (SFE-411): "input.scs" 393: Hierarchical node `clkdiv.Xbuf<0>/MMNINP.G' does not exist in design. It will be treated as a regular (non-hierarchical) node.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to RFStuff

    Using dot is a particularly bad idea, because that’s spectre’s hierarchy separator. You might be able to escape it but why not just keep life simple and use underscore instead. There aren’t any prizes for making like hard for yourself!

    Colon is also probably a challenge because of its use as the terminal delimiter in spectre. However, I think if escaped it ought in principle to work. 

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RFStuff
    RFStuff over 6 years ago in reply to Andrew Beckett

    Dear Andrew,

    I replaced all Xbuf<0>/MMNINP:G to Xbuf<0>/MMNINP_G in the netlist.spf file.

    I used the probe name in deepprobe as:- clkdiv.Xbuf\<0\>\/MMNINP\_G.

    But still it is showing :- 

    WARNING (SFE-411): "input.scs" 393: Hierarchical node `clkdiv.Xbuf<0>/MMNINP_G' does not exist in design. It will be treated as a regular (non-hierarchical) node.

    In my netlist file, the include line is as follow for the extracted cell view is VCO_clkdiv :-

    dspf_include "/../VCO_clkdiv/spf_max_rcc_125/netlist.spf".

    I think the netlist.spf file is a binary file. Though I am opening this file in Library Manager through nedit and replacing the above pattern, it is actually not gettting reflected during spectre's netlist generation process.

    Is there a better way find and replace the dspf file so that it will be the final one that spectre would take ?

    Kind Regards,

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to RFStuff

    First of all, you don't need a backslash before the underscore in the deepprobe because underscore is a legal character in a net name, so doesn't need escaping. However, for me, it works with or without the backslash (using SPECTRE 18.1).

    The DSPF file itself isn't binary - it's an ASCII file. How are you referencing the file? If it's via Setup->Simulation Files, then it's just an ASCII file and all should be OK - you should be able to edit it. The only thing to consider is whether spectre really re-starts, which would definitely happen if you editing the deep probe on the schematic and re-did netlist and run. Otherwise you might have to hit the stop button (if using ADE L).

    If you're using a DSPF view (which I don't think you are because I would expect the file to end with design.dspf if you were), then it should also work.

    So I'm intrigued as to how you're editing this from the library manager. Which tool was used to do the extraction?

    The only case with a binary file is if you've extracted with Quantus QRC and are using a "Smart View" (the new extracted view format) in IC618/ICADVM181. That is then a binary file which netlists to DSPF, and so editing the DSPF file wouldn't help you...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RFStuff
    RFStuff over 6 years ago in reply to Andrew Beckett

    Dear Andrew,

    May I know how you are opening the dspf file (.spf) which is in ASCII format in a terminal and edit/save it.

    I am using Calibre-StarRC for extraction.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to RFStuff

    I used vi (might have been gvim, but essentially the same).

    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