• 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. Digital Implementation
  3. RTL compiler technology transformation

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 91
  • Views 14619
  • 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

RTL compiler technology transformation

kenambo
kenambo over 9 years ago

Hi all,  

I am converting an already synthesized netlist to another technology using RTL compiler.. while doing this the generic netlist coud not generate a scan latch. It just reflects the same name in the generic netlist.

For scan flops we can unmap scan flops using,     set_attribute unmap_scan_flops true  . but for latches it doesn't apply...

so please share anything that makes this possilble.

Tanks

  • Cancel
Parents
  • grasshopper
    grasshopper over 9 years ago
    CGICs cannot be inferred from HDL hence cannot be 'uninferred'. You can indeed do 'clock_gating remove' and then rely on them being added again but I believe change_link is a better approach. Note change_link can relink to a module/subdesign so if your library does not have one, you would have to create a module/subdesign for it using latches/or/etc.

    gh-
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 9 years ago
    CGICs cannot be inferred from HDL hence cannot be 'uninferred'. You can indeed do 'clock_gating remove' and then rely on them being added again but I believe change_link is a better approach. Note change_link can relink to a module/subdesign so if your library does not have one, you would have to create a module/subdesign for it using latches/or/etc.

    gh-
    • 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