Hi guys,
When running the RC extraction with Encounter at the end of the PnR flow, I get the following messages:
**ERROR: (ENCEXT-3423): Detected 2 nets with incomplete RC network. Low-value resistances have been added by the software to complete the RC network of these nets. Review the list of affected nets in the 'ctrl_top.rc_typ.incomplete_res.net' file to ensure they are not along the critical path because results of timing analysis performed on nets with incomplete RC network can be inaccurate.
This happens only on 2 nets, that have nothing special from a design point of view.
Looking at the man of (ENCEXT-3423), this appears because the resistance for the given nets is not found in the SPEF.
But I am kind of stuck in tracing back the root cause of this problem.
Would you have hint about where to look?
Thanks!
this happens when routing fails to complete
Thanks for your comment,
I ran a connectivity check, and it reports no Error... How can I check this problem after routing?
Thanks
read the execution log of the routing step
Hi timof,
Tanks for taking hte tme to explain this in detail.
What I get in the SPEF header is :
*VENDOR "Cadence Design Systems, Inc."
*PROGRAM "Encounter"
*VERSION "14.28-s033_1"
I'm reporting this point to the guy taking care of the integration of this digital block in Virtuoso.
This is on a non critical path, so I don't care about timing here. But I do care about functionality.
If there is a real connectivity problem,can it be caught by LVS in Virtuoso?
Thanks again!
Hi timof,
Tanks for taking hte tme to explain this in detail.
What I get in the SPEF header is :
*VENDOR "Cadence Design Systems, Inc."
*PROGRAM "Encounter"
*VERSION "14.28-s033_1"
I'm reporting this point to the guy taking care of the integration of this digital block in Virtuoso.
This is on a non critical path, so I don't care about timing here. But I do care about functionality.
If there is a real connectivity problem,can it be caught by LVS in Virtuoso?
Thanks again!
Two points I have to make: if you are using Cadence-only flow, you generally trust the spef to be correct. The tool handles all of that for you, you don't even know that there is a spef file being used under the hood.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?