Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
I am getting below error in Hercules DRC run. Can anybody explain about this error and also how to solve this?
PO.RL.1: ALLPOLY maximum length = 200000nm (after poly_sub cut)
... 2 violations found
ERROR DETAILS
#####--- ERR_SELECT -----------------------------------...
I am getting below error in Hercules DRC run. Can anybody explain about this error and also how to solve this?
PO.RL.1: ALLPOLY maximum length = 200000nm (after poly_sub cut)
... 2 violations found
ERROR DETAILS
#####--- ERR_SELECT...
As per my knowledge synopsys encrypted files are read automatically by all synopsys tools.
But i am getting error; it says Unable to read the HDL (UID-59)...and those files are encrypted, provided by Synopsys
Whats going wrong?
Any clue?
Its PowerPC based SoC....
We have soft core IPs.
Deliverable (its little old !!) obtained are targeted for 130nm....
Now, same soft cores are used to implement SoC in 90nm.....
so this is the background story...!!!
i have slack of -0.6 (prelayout)......i must achieve zero !!!
Hence i am thinking if i can have accurate (or almost accurate.....because nothing can be accurate..its all design specific !!) constraint value suitable for 90nm i may achieve better timing.....
By the by i am synthesizing PowerPC...
I have design for which i have constraints and scripts targeted for 130nm. Now my requirement is to target it to 90nm libs. Is there is any thumb rule to change those constraints written for 130nm design to 90nm compatible?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.