• 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. Extracted View Netlisting Issue

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 64
  • Views 12901
  • 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

Extracted View Netlisting Issue

MMueller
MMueller over 8 years ago

Hi all,

i have got an issue with the netlisting of my mixed signal design (using the UNL Flow):

I am running a "text on top" design from ADE Assembler with a config view - toplevel being a verilog view and an instance being a schematic view.

This worked fine until i tried to exchange the schematic view with an av_extracted view (created with PVS/ QRC).

The netlist with the schematic looked like this:

Module:

module SCHEMATIC_MODULE_NAME (BUS_NAME_A);
output [3:0] BUS_NAME_A;

...

...

..
endmodule

Instantiation:

wire [3:0] bus_wire;

SCHEMATIC_MODULE_NAME INSTANCE_NAME ( .BUSNAME_A(bus_wire));

which worked fine.

Now, the extraction view is netlisted as:

module SCHEMATIC_MODULE_NAME  (\BUSNAME_A(3) , \BUSNAME_A(2) , \BUSNAME_A(1) , \BUSNAME_A(0));

output \BUSNAME_A(3), \BUSNAME_A(2), \BUSNAME_A(1), BUSNAME_A(0);

.

.

.

endmodule

Which gives an error during elaboration....

I found that i can add a callProc.il to the QRC run in order to get [ ] brackets instead of parathesis (), but still the bus is split in this way, which means the simulation does not work.

Is there a way to get the extracted_view netlisted "the right way"?

Best regards,

Markus

  • 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