• 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. Drive/monitor EEnet using virtual interface

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 1172
  • 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

Drive/monitor EEnet using virtual interface

jshaler
jshaler over 2 years ago

I am trying to write a UVM testbench for a block using EE_pkg::EEnet inputs/outputs, but it is not working. Is there something I'm missing for how to use interfaces with EEnet ports?

When I try to create an interface it does not compile:

import EE_pkg::*;
interface block_interface(input bit clk);
EEnet input_signal;

clocking driver_cb @ (posedge clk);
output input_signal;
endclocking

modport driver_mp (clocking driver_cb);
endinterface
 
I get an error:
  output input_signal;
|
xmvlog: *E,WOUPYR (block_interface.sv,70|22): As a temporary implementation restriction, unpacked structures nettype is not permitted in this context. 
  • Cancel
Parents
  • tpylant
    tpylant over 2 years ago

    I believe this issue has already been fixed in the latest releases. Which version are you using?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jshaler
    jshaler over 2 years ago in reply to tpylant

    I tried with 3 versions: 21.09.004, 22.09.004, and 23.01.071_agile

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • jshaler
    jshaler over 2 years ago in reply to tpylant

    I tried with 3 versions: 21.09.004, 22.09.004, and 23.01.071_agile

    • 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