Stats

  • Locked Locked
  • Replies 17
  • Subscribers 128
  • Views 30768
  • 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

Accessing a net from top level

Pramod
Hi All, I am using this forum for the first time though i have been using Cadence tools for sometime. I have a very basic question...(somebody might have already asked it) I have a GOLDENschematic for which I want to built a test bench in ADE.For this I built a schematic and instantiated the GOLDEN schematic in that.I added all the required stimuli for the pins available externally (through the GOLDEN symbol).Now my issue is that i need to add access a node(net) inside the GOLDEN schematic and want to put a current source on that.I don't want to change anything in GOLDEN.I tried to put the current source and label the net attached to it with . but this didn't work.While netlisting I could observe that the spectre was netlisting it like _. Can anybody guide me here,hope I am clear. Thanks, Pramod

  • Would this work with AMS or, as the doc says (currently), only for spectre?

    What would the workaround be to get it to work with AMS-APS?

     

    Thanks

  • I'm using IC5141ISR20110503, MMSIM11.1.0.341.isr6, and INCISIV12.10.3

    I have been able to get deepprobe to work with AMS(APS) using OSS through the ADE, however it requires modifying the resulting netlist.vams located in the simulation's "netlist" directory.  The toplevel netlist located in the netlist/ihnl/cds* directory has an iprobe line:

     _ANALOG_BEGIN
    x1 (x0.n0 n1) iprobe
    _ANALOG_END

    However when this makes it into the netlist.vams file, which is what AMS uses when running, it looks like:

     iprobe x1 (\x0.n0 , n1);

    The hierarchical name has a \ placed at the beginning of the name which causes it not to work.  Deleting this \ and rerunning without renetlisting allows the net to be accessed hierarchically.  There may be an option to stop this \ from being added, but I don't know what it is.  Until then, hand editting is a reasonable approach.

     Josh

  • Hand editing is to be deprecated as much as possible.

    Cadence gave me a solution a couple years back. You can place a deepprobe whose property form has 2 fields - one the hierarchical pathname for AMS and one for Spectre. It works good..

  • I've searched for "deepprobe" and I haven't found this solution.  I don't know where to start since I haven't found anything that describes how a hierarchical pathname for AMS differs from Spectre.  I've found hints that this may be the case, but not what it may be.  So, what is the difference?

     Thanks!

  • Attached file will work for IC6.

     

    RENAME to deepprobe_OA.tar.gz and then do tar -xzvf, etc..

  • Attached file will work for IC5

    RENAME to deepprobe.tar.gz and then do tar -zxvf, etc.

     

  • When accessing the schematic node xand<1>.A<0> :
    In AMS, use xand_1.A[0]
    In spectre, use xand\<1\>.A\<0\>

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.