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.
Ok. i shown M5 here for simplicity, i don't use M5 for mesh. my mesh consist of M12(H),M11(V) top ring and M11(V) stripes, its connected to M6(H) and its again to M3(V) and then M2 for site row rail.
upto M6 i can able to create stripes with out any warning. but while creating M3 stripes i get...
how to calculate M5 spacing while adding power mesh.
lef only having spacing table not the minimum spacing value. for higher metal layers its having minspacing value, lower layer spacing table only there.
so how to calculate spacing fro this table and what is PARALLELRUNLENGTH in that.
LAYER...
ok. that's solved.
how to create path_group in rc compiler?
i want to create r2r path using path_group command and find. so how to detect all reg output and input using find command? can i make it in a single command?
or should i write tcl script with reg expressions for finding reg ports...
do you have any .io file from fab/design ? this file help to solve the issue.
or you can edit pin and connectivity information from encounter itself.( edit -> pin editor)
STA tools will report async path violations(recovery and removal) and we can specify delay in async path with the command in ETS set_max_delay (with respect to clock edge).
why fab provides separate .lib for OCV even-though it has .lib for corner analysis?
ie, only derating factors(early and late) for clock path timing and data path timing is only specified in this .lib right? so why don't they try to mix it with .lib for corner analysis(resulting in a .lib with...
In ideal mode the clock signal can arrive at all clock pins simultaneously. But in fact, that perfection is not achievable. So, to anticipate the fact that the clock will arrive at different times at different clock pins, the "ideal mode" clock assumes a clock uncertainty.
Major reasons for the...
At what point we are able to fully fix both these recovery and removal violations?
Can do it at postCTS itself or postRoute and please provide some guidelines for that..
which is the effective way to resolve this violations either adding buffers in asyncpath or resizing clockcells(in the case...
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.