• 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. Mixed-Signal Design
  3. Simulating *.vams generated from ADE-L in DoT flow

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 15352
  • 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

Simulating *.vams generated from ADE-L in DoT flow

aarthymani
aarthymani over 7 years ago

Hi All, 

   Wondering, whether it is possible to simulate a *.vams generated from ADE-L (using AMS + ultrasim) in DoT flow?

To explain, I have a schematic which has both digital and analog components, so  I had to use AMS for netlisting. Now since my design is complex block, i Would like to use verilog testbench to reduce testbench development time, for each case. 

Is it possible to do? any hints? 

if not, could anyone suggest me any better way to use script based testbench.  Initially I was using VCD for doing the same, VCD has no issues with pure analog simulation. But When I change my simulator to AMS, the signals that are represented by bus (e.g: S<10:0>) all ends up floating nodes. I do have alias <*> [*] setup in my vcd control file. As I wasn't able to fix it. I had to move to DoT flow and I am not sure whether it will work or not.

any suggestions or ideas?

Thanks!

Aarthy

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Aarthy,

    Yes, this is possible, but it's unclear what  you don't know. Running AMS from the command line with a digital test bench (or doing the same from within ADE) is perfectly possible. You can use "runams" to generate the netlist of your design, and then incorporate that into a command-line "irun" (or "xrun" if using the newer Xcelium simulator).

    Note that if you're talking about using VCD inputs in the ADE Simulation Files form, then these can only drive analog nets (even in a mixed-signal simulation), and the names in the info file do need to match those in the netlist. Not quite sure exactly what your issue is.

    Maybe it would be better to contact customer support as it may need a bit of back and forth discussion to understand fully what your setup looks like and what you're trying to achieve.

    Thanks,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • aarthymani
    aarthymani over 7 years ago in reply to Andrew Beckett

    Hi Andrew, 

    Thank you for your response. The earlier question is to understand whether it is possible to do. 

    since this is in the initial phase, I am trying to understand and solve it from discussions & reading, if nothing works I will be contacting customer support for setup. 

    In this case I want to use digital test bench in command line to run, with my netlist being a *.vams. 

      * where does the definition of digital modules read from, as now my digital modules are buried deep in the hierarchy. 

      * assuming Including the definition for digital module in the irun options, how does the control transfer between irun and Ultrasim?  is it automated or do I need to define it in amsd control config?

      * When i use ADE-L AMS flow to generate the netlist, the files first line reads something like "for viewing purpose only, don't compile" ? Can i still use this file as my netlist? 

    My questions might not be correct, as I am trying to understand the flow from the files generated by ADE-L, but i couldn't find any files with definition of digital files, also there is partition file in */psf which defines all the nets property to be analog/digital/mixed signal. Not sure whether I need to write this file manually? 

       Thank you!  

        Aarthy  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to aarthymani

    If you are running with the UNL or OSS netlisting flow (Simulation->Netlist and Run Options; UNL is the preferred option nowadays), it will produce a variety of files in the netlist directory, including netlist.vams (the main netlist) and also reference text files using the textInputs file which is passed to irun with -f (the "runSimulation script in the netlist dir takes care of bringing everything together). You can do this from the command line using the "runams" program - this can be used just to netlist, or to netlist and simulate, and the information then goes into a given netlist dir rather than in the usual ADE place. To answer your questions (in the order of your bullet points):

    1. This is via the textInputs file in the netlist dir.
    2. This is something the simulator takes care of. The analog control file is needed to specify accuracy settings and the duration of the tran analysis (some accuracy controls need to know how long the simulation is expected to run for) - again, this will be in the netlist dir and if running with runams from an ADE state, it will create this for you.
    3. All you're doing here is looking at the Simulation->Netlist->Display - which is for display purposes only. It combines several of the files into one place so it can be viewed in one window for debugging purposes - but you're not intended to use that for simulation - the real files are in the netlist dir as I said.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • aarthymani
    aarthymani over 7 years ago in reply to Andrew Beckett

    Hi Andrew, 

    Thank you! Now i understand it a bit clear.

    Regards, 

    Aarthy

    • 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