• 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 - ams - issue with \ in netlist

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 3638
  • 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 - ams - issue with \ in netlist

michael10
michael10 over 2 years ago

Hi,

I have a similar issue as in this thread: https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/41411/deepprobe-to-a-bussed-net-in-ams

My testbench looks like this:

tb_circuit -> schematic:

  • DUT -> device under Test
    • submodule1
    • submodule2
    • net "control_signal_dig" connecting 2 ports of submodule1 and submodule2
  • net named "control_signal_dig_probed"
  • deepprobe, connected to net "control_signal_dig_probed"
    • Hierarchical Node: "DUT.control_signal_dig"

What I want to do with this, is probing the net "control_signal_dig" from the DUT, and make it available at the top level of the testbench schematic.

This is also working when the submodules are running on transistor level (control_signal_dig is an output of submodule1 - which is an analog levelshifter).
The netlist looks like this:

iprobe IPRB0 (DUT.control_signal_dig, control_signal_dig_probed);

However, when I change the submodules to a verilog model (by setting up a config view), this doesn't work anymore. When I plot the "control_signal_dig", the output of the verilog model is correct (logical 0 or 1).
But the "control_signal_dig_probed" is 0V (so not even a digital signal) in the waveform viewer.

The netlist looks like this:
iprobe IPRB0 (\DUT.control_signal_dig, s2d_phi2_dig_probed);

Note the "\" which, as mentioned in the other thread, is " added out of nowhere by the netlister."

I assume that the "\" is also my problem, but I don't know how to solve it.
In my case, the issue is not due to a bus. The net "control_signal_dig" is a single signal, not a bus.

The simulation is started from ADE Assembler, simulator is set to ams.

Tool versions:

xrun(64)    20.09-s016
spectre     20.1.0.404.isr13

Thanks!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    Which IC version are you using? That would help with me checking this out.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • michael10
    michael10 over 2 years ago in reply to Andrew Beckett

    Sorry that I missed this.

    The Virtuoso Version is ICADVM20.1-64b.500.22

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • michael10
    michael10 over 2 years ago

    Hi,

    I've noticed the following behavior:
    As soon as I add an analog device in the DUT, the deepprobe works again and the "\" in the netlist is gone.

    Example:
    DUT -> Device under Test

    • ... see first post
    • add a analogLib -> VDC source, even if it just floating.

    With this, the deepprobe is working also when the submodules are set to verilogams.

    Unfortunately, this does not help me in my real testcase (the design is an analog schematic which is going into layout, I can not add add "VDC" there).
    Also in my real testcase, the problem occurs in different hierachies, so I would have to touch many schematics.

    One more screenshot of the problem.

    • 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