Stats

Locked Locked
Replies 3
Subscribers 92
Views 9723
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

INNOVUS sroute error: not a CUT LAYER

I'm using INNOVUS20.17 to P&R on .13 SiGe BiCMOS technology. The tech lib are converted from LEF file to OA with the lef2oa command. When I'm doing the power planning, the sroute command gives me some error message and leave all the power pins unconnected. It seems that the DB technology information is not properly loaded. How can I debug it? Thanks.

sroute -connect {padPin} -allowJogging 0 -allowLayerChange 0

Begin option processing ...
srouteConnectPowerBump set to false
routeSpecial set to true
srouteConnectBlockPin set to false
srouteConnectConverterPin set to false
srouteConnectCorePin set to false
srouteConnectStripe set to false
srouteFollowCorePinEnd set to 3
srouteFollowPadPin set to false
srouteNoLayerChangeRoute set to true
sroutePadPinAllPorts set to true
sroutePreserveExistingRoutes set to true
srouteRoutePowerBarPortOnBothDir set to true
srouteStraightConnections set to "straightWithDrcClean"
End option processing: cpu: 0:00:00, real: 0:00:00, peak: 3321.00 megs.

Reading DB technology information...
*ERROR* LAYER Metal2 is not a CUT LAYER
*ERROR* LAYER Metal1 is not a CUT LAYER
Finished reading DB technology information.
Reading floorplan and netlist information...
Finished reading floorplan and netlist information.
A total of 2 errors.

Bowen Xia over 3 years ago

By the way, the NanoRouter is not affected, all other place and route steps are fine. Only the power routing are missing.
Cancel
Vote Up 0 Vote Down

Cancel
DimoM over 3 years ago

Hi,
it seems there is a problem that happened during the OA file creation, or while loading the tech information into the database.
The techOA topics are tricky, it requires expert knowledge. I don't think that it can be solved over the forum.

It would be best to contact Cadence support to help you with that.

- Dimo
Cancel
Vote Up 0 Vote Down

Cancel
Bowen Xia over 2 years ago in reply to DimoM

Hello Dimo,

It turns out that I missed the -useFoundryInnovus and -refLib in the lef2oa step, after re-generating the techOA the problem solved.

Bowen
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.