• 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. Missing EEnet connect modules

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 65
  • Views 20096
  • 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

Missing EEnet connect modules

drdanmc
drdanmc over 7 years ago

I have a systemVerilog real number model for an analog block.  There are some logic ports and several EEnet ports.  Next step was going to be to get dmv set up for model validation.  I have a top level schematic that has one instance of the block in question and one instance of a stimulus/measurement block.  For that test bench block I wrote a systemVerilog program that runs through all of the different control bits into the block.  This runs fine with ams within ADE-L.  Next, with the hierarchy editor, I picked the schematic view for my circuit block.  This won't simulate because of missing connect modules to provide the connection from EEnet to/from electrical.   I see what appears to be the correct connect module in

.../XCELIUM1704/tools.lnx86/affirma_ams/etc/connect_lib/EEnet_to_E_bidir.svams

but can't seem to figure out where I actually tell the elaborator to actually use this and so I get lots of:  

xmelab: *E,CUVNCM (./netlist.vams,1098|30): No connection module found:Need inout ports of nettype EEnet with attribute logic, continuous discipline electrical, at instance MyTopCell.ITEST_BENCH.

So I have three questions

1)  how to actually get this connect module into the tool?

2) in that error message it says '... of nettype EEnet with attribute logic...".  What is the "with attribute logic" part?

3) is there a way to put in some `ifdef stuff to switch my systemVerilog test bench to use electrical when connecting to the schematic version and avoid needing connect modules that way?  What would be more typical?  I've done a modest amount with Verilog-AMS and wreal but not much with dmv or systemVerilog and EEnet.

IC617, XCELIUM1704

Thanks

-Dan

  • Cancel
Parents
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago

    Hi Dan,

    To answer your questions:

    1. You'll have to point to the file 'EEnet_to_E_bidir.svams' (with the full path) in your xrun command. This is just like including any *.v or *.sv in your simulation run on the command-line.

    2. 'attribute logic' refers to discrete domain which applies to real numbers being solved by digital solver.

    3. I think what you are suggesting will need 'electrical' domain in a *.sv file, right? This isn't supported. I think what you are proposing will work on the same lines as the connect modules in *.svams file but that format is still being worked upon. With the auto-insertion of EEnet-to-electrical connect modules, you won't need to use electrical discipline in the SV testbench.

    Regards,

    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago in reply to Saloni Chhabra

    I must also add that auto-insertion of EEnet-to-electrical connect modules was introduced last year. Going forward, the user will not have to provide the path to the CM (*.svams) in the run command, but the version of Xcelium with this enhancement hasn't been finalized yet.

    Regards,

    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Saloni Chhabra
    Saloni Chhabra over 7 years ago in reply to Saloni Chhabra

    I must also add that auto-insertion of EEnet-to-electrical connect modules was introduced last year. Going forward, the user will not have to provide the path to the CM (*.svams) in the run command, but the version of Xcelium with this enhancement hasn't been finalized yet.

    Regards,

    Saloni

    • 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