Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 13086
  • 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

Congestion + Report RC + silicon ensemble

archive

I have a routed design (using silicon ensemble) to begin with to which I make modifications like adding additional logic (nets and components) afterwhich I place the design all over again and re-route. Is it possible to estimate congestion - in view of new nets/cells being added? How do I quantify congestion?

Is it possible to get capacitance information - using the dspf files that are written out? What do I look for either in a .dspf or .rspf file? How do i use the HyperExtract option while doing report RC - will that help?

I currently have def/dspf/rspf/setload files of design before modification and def/dspf/rspf/setload files of design after modification.

Any help would be appreciated.


Originally posted in cdnusers.org by kdurais

  • HI ,
    I am not sure if this can work around for analysing and the congestion .
    In my understanding you mean to say about ECO -right !!
    Its all depends on :
    1. how many nets or instances you have modified after routing initially .
    check with Eco report command
    2. to analysis how big the difference just compare two report files after
    global routing
    even you can get map displayed .

    Regards,
    Mohan


    Originally posted in cdnusers.org by mohanch007

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.