Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 14752
  • 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

save all device data in dc sweep

Josef

 Hi *,

i'd like to perform a dc sweep and with the opend results I need to access the device data directly, e.g. by typing something like vgs("M1") without using the netname connected to the gate and source port of the M1 device.  

 I should be a kind of save opPoint value but not a scalar but a vector.

 searched for a while in this forum but didn't get a proper answer, yet.

 thanks in advance

josef

 

 

 

Parents

  •  Hi Josef,

     Here we go:

     

    Create one additional file to include with your simulations and fill it with some lines like

     

    save DUT.MP0:oppoint

    save DUT.Q0:oppoint

     

    and so on ... of course you have to adjust the hierarchy information andthe devicenames

     

    If you enter "spectre -h save" you will get some extra info on whats possible with

    wildcards, filtering options and so on. However this scheme does not work for every PDK.

    I just had one case where the probing was broken :( I'm waiting for an updated PDK right now ...

     

    Best Regards

     

    Andi

     

Reply

  •  Hi Josef,

     Here we go:

     

    Create one additional file to include with your simulations and fill it with some lines like

     

    save DUT.MP0:oppoint

    save DUT.Q0:oppoint

     

    and so on ... of course you have to adjust the hierarchy information andthe devicenames

     

    If you enter "spectre -h save" you will get some extra info on whats possible with

    wildcards, filtering options and so on. However this scheme does not work for every PDK.

    I just had one case where the probing was broken :( I'm waiting for an updated PDK right now ...

     

    Best Regards

     

    Andi

     

Children
No Data

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.