Stats

  • Locked Locked
  • Replies 14
  • Subscribers 90
  • Views 6050
  • 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

connectivity check after p&R

archive

Hi;
Thank you for the help.
Since this is my first time to use encounter, I have many problems.
When I am done with P&R and did connectivity check, I have connection problems with vdd and vss.
I have already done the following.

sroute -nets {vdd vss}

but still have this problem.
Can I check if this is a real problem?
If so, how can I solve this problem?

Thank you so much


Originally posted in cdnusers.org by semicond
Parents

  • Sorry, the sroute command was one of a series from the script. Later it was called with:
    sroute -noPadRings -jogControl { preferWithChanges differentLayer } -nets { VSS VDD }

    I solved the problem, actually. I had several blocks with block rings and there were stripes that were routed very close to the block rings. The followpins were routing to the stripes and not the block rings causing the open net. By increasing the value of the -merge_stripes_value option for addStripe, stripes that are too close to the block rings will merge and the problem was solved.

    Thank you for your help.


    Originally posted in cdnusers.org by umdcdn08
Reply

  • Sorry, the sroute command was one of a series from the script. Later it was called with:
    sroute -noPadRings -jogControl { preferWithChanges differentLayer } -nets { VSS VDD }

    I solved the problem, actually. I had several blocks with block rings and there were stripes that were routed very close to the block rings. The followpins were routing to the stripes and not the block rings causing the open net. By increasing the value of the -merge_stripes_value option for addStripe, stripes that are too close to the block rings will merge and the problem was solved.

    Thank you for your help.


    Originally posted in cdnusers.org by umdcdn08
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.