• 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. Functional Verification
  3. Simulator ignores attributes during elaboration

Stats

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

Simulator ignores attributes during elaboration

FormerMember
FormerMember over 9 years ago

Hey everyone,

Does anyone have a good experience with the instantiation of different cells in the same verilogams file?

I'm building a testbench and want to instantiate two instances that have the same name but exist in different libraries, one is schematic and the other one is veriloga.

What I did is the following:
     cell1
     (*
     integer library_binding = "Lib1"; 
     integer view_binding = "veriloga"; 
     *) dutvams (
           .x(dutvams_x), 
           .y(dutvams_y), 
           .z(dutvams_z)
     );
     cell2
     (*
     integer library_binding = "Lib2"; 
     integer view_binding = "schematic"; 
     *) dutsch (
           .x(dutsch _x), 
           .y(dutsch _y), 
           .z(dutsch _z)
     );
I'm also including the path to the veriloga model at the beginning of the verilogams file.

What happens is that when it compiles, it ignores the attributes in between the asterisks completely no matter what I'm tossing in, would only generate syntax errors if it's wrong and generates two schematic instances for Lib2.

When I change the name of the veriloga cell to a different name than the one for the schematic, it works properly.

I'm using virtuoso IC6.1.6.500


I don't know what I'm missing here! Any help would be appreciated, thanks :)

  • 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