• 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. Logic Design
  3. How to preserve the internal signal name in synthesis when...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 18852
  • 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

How to preserve the internal signal name in synthesis when using Cadence RTL compiler

rexnyu
rexnyu over 12 years ago

Here is part of my script.

set_attribute write_vlog_preserve_net_name true

elaborate aes_fwd_top

ungroup -flatten -all

synthesize -to_mapped

write_hdl -mapped > aes_fwd_top-orig.v

But RTL compiler keeps changing my internal signal names with some random names in the verilog netlist file.

What is the proper way to use "write_vlog_preserve_net_name"? or I am using the wrong command.

  • Cancel
Parents
  • nightswhosayni
    nightswhosayni over 9 years ago

    Hmm....

    "Topic has 0 replies and 6091 views."

    Seems like there are a number of folks also having the same issue, yet "0" replies.

    You would think this might have made the  R&D priority list. 

    And  here we are three years later.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • nightswhosayni
    nightswhosayni over 9 years ago

    Hmm....

    "Topic has 0 replies and 6091 views."

    Seems like there are a number of folks also having the same issue, yet "0" replies.

    You would think this might have made the  R&D priority list. 

    And  here we are three years later.

    • 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