• 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. Nanoroute writes out def without the property definition...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 91
  • Views 14254
  • 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

Nanoroute writes out def without the property definition section.....

NAADHAN
NAADHAN over 16 years ago

Hi,

            In our current project we use Standalone Nanorouter for routing......here we faced a problem were the core started shrinking in the final def file written out... When we looked in..we found that the nanorouter writes out def without "PROPERTYDEFINITIONS" section.. and when it is loaded further in  a normal encounter for further route optimisation, the core-size shrinks as the definition of space from core doesnt exist.....


One Solution is that we load the cts def + route def incrementally so that the "PROPERTYDEFINITIONS" are retainted....but is there any other way to def-out with this "PROPERTYDEFINITIONS"section using nanorouter ?????????

 

Thanks & Regards,
Naadhan

  • Cancel
  • archive
    archive over 16 years ago
    Hi Naadhan, Standalone nanoroute does not write out property definitions in def.I'm assuming you are using stand alone nanoroute. It ignores properties, property definitions, placement blockages, groups, and regions. Workaround I can suggest would be : 1) -- save the placed datbase within encounter. -- export only the routing information in nanoroute. without -full option -- once in encounter restore the placed database and read the routed def. 2) -- save the FP file in encounter -- save routed def as usual through stand alone nanoroute. -- once in encounter load the fp file and read the routed def from nanoroute.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 16 years ago

     Hi Naadhan,

    Us Cadence folks are just curious why you're running nanoroute standalone. :-)

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • NAADHAN
    NAADHAN over 16 years ago

    Thanks Vishnu....  Seems that this is a known problem...thanks for the solution...But i felt it would be better if cadence can do something in the tool itself to add this section in def also ;P.....

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • NAADHAN
    NAADHAN over 16 years ago

    Hi Kari....

          thats what our customer is comfortable with :P...and they recomend us to go with stand Alone Nanorouter for smaller nodes ... Though we have not compared the routing capabilities of standAlone Nanorouter and the 8.1 route version we still feel that Stand Alone Nano-router is better...But will get back once we compare this aspect ...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 15 years ago

     Naadhan,

     There's no reason you should have to go with standalone nanoroute for smaller nodes (or any nodes). If you come across something in your experiments, do let us know!

     Thanks,

    - Kari

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • NAADHAN
    NAADHAN over 15 years ago

    Hi Kari... definetly will get back when i get some information regarding this.

    • 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