• 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 SKILL
  3. Default (or script) ADE Stimuli

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 16434
  • 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

Default (or script) ADE Stimuli

meland
meland over 12 years ago

Hello All,

I am wondering if there is a way to either alter the default ADE stimuli or change it through script. I would prefer if all of my stimuli would default to a 0v DC source which is enabled. 

I suspect that this is done in some way through the asi function calls in the ADE L Skill reference manual, but I'm not able to figure it out. I have some level of skill experience, but I have never skill scripted anything with the ADE.

I work in both cadence 5.1.41 and 6.1.5, but if there is not an easy method for cadence 5 that is fine.

Perhaps my overall approach is flawed though and there is a better way of doing what I want. My overall goal is to more easily set up and test at higher levels where there are potentially hundreds of stimuli. I haven't found a way which works well for doing this. Going through and editing one by one is quite tedious. I tried vector files, but I couldn't do anything bigger than a 4 bit bus . I had issues scripting a general stimuli file (An issue I had scripting the two of these was getting cadence to return the pins with the buses expanded and keeping reference to the pin direction). I could also do AMS, but I do not know an easy way to set up AMS and have never gone down that road. Note, I do not have an ncverilog license available

Some direction on how to go about this would be great.

Thanks,

-Matt

  • Cancel
Parents
  • meland
    meland over 12 years ago

     Hi Andrew,

     Sorry my first question was misleading. I'll try to be more clear in the future. I consider myself warned as far as using private functions.

     I have a follow up question. The code which I've provided works great for me when there are just a few input signals. However, it appears that this solution has some kind of memory leak issue. I tried running this on a block with 100 pins and the first few run fine, but each progressive setting of a stimuli takes slightly longer and longer. I noticed when it was approximately half way through the list it was taking ~6 seconds per stimuli. And it would just get longer to the point where the best thing to do is walk away for a little. 

     Is there some way around this that might not take as long? It seems the issue is with the line 'formId->artStmBox->value = list(choice)' but I'm not sure any other way of doing this. 

     Any idea what is going on here?

     Thanks,

    -Matt

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • meland
    meland over 12 years ago

     Hi Andrew,

     Sorry my first question was misleading. I'll try to be more clear in the future. I consider myself warned as far as using private functions.

     I have a follow up question. The code which I've provided works great for me when there are just a few input signals. However, it appears that this solution has some kind of memory leak issue. I tried running this on a block with 100 pins and the first few run fine, but each progressive setting of a stimuli takes slightly longer and longer. I noticed when it was approximately half way through the list it was taking ~6 seconds per stimuli. And it would just get longer to the point where the best thing to do is walk away for a little. 

     Is there some way around this that might not take as long? It seems the issue is with the line 'formId->artStmBox->value = list(choice)' but I'm not sure any other way of doing this. 

     Any idea what is going on here?

     Thanks,

    -Matt

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information