• 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 Design
  3. Probing wreal4state nets deep in hierarchy adds IE/connectLib...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 1663
  • 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

Probing wreal4state nets deep in hierarchy adds IE/connectLib element

MikeVP
MikeVP over 2 years ago

Cadence version:

IUS: 20.09.012
MMSIM: 20.10.354

My test bench is all digital (functional and systemVerilog, no spectre elements).

This test bench checks if a node value (wreal4state) deep in hierarchy is the same value that comes out of an analog mux at the top level.

I want to sample the value deep in hierarchy and then compare it to the value at the top level. However, with the code I am using, the elaborator is putting an IE R2L on the wreal4state net in hierarchy. So, for example, the value at the top level 1.24, but the sampled value in the stimulus is 1.0 because of the IE.

I looked at this article:  https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000009ESqBUAW&pageName=ArticleContent&shareID=1678896866867

This uses a system function $real_net_alias() that is used in v-ams.  When I try to use this, I get this error:

xmelab: *F,WRFUNCM (/design/x/x/x/x/x/x/x/x.sv,1035|30): Can not connect real net TB_xxx.IxxxxSTIM.abus0_mon.w_res with nettype 'wreal1driver' and resolution 'CDS_res_wreal1driver' to real net TB_xxxx.IxxxxSTIM.abus0_mon.signal with nettype 'wreal4state' and resolution 'CDS_res_wreal4state'.

Is there a version of $real_net_alias() for systemVerilog cds_rnm_pkg nets?  Or is there a better way to probe the node deep in hierarchy such that it does not add an R2L?

  • Cancel
  • MikeVP
    MikeVP over 2 years ago

    My local EDA support was able to help.  It needed to change the 'wreal' nodes in the vams file to 'wreal4state'

    • 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