Search Engine

33 Threads found on Recovery Removal
This is asynchronous pin so it has nothing to be constrained with REG/CP. I believe you can check its timing by removal/recovery checks.
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 of removal check).. please reply..
there should not be any setup/hold/recovery/removal/transition violations present in design , input will be constraint file and post layout netlist , output will be your generated reports.
Hai all, What is recovery Check,removal Check? please could u tell me Eqs for recovery check,removal Check like setup time and Hold time ? Thank u............
Hello, what is the issue - in my GLS run I see many timing violations, now on selected port/module I wanted to disbale/mask any setup/hold/recovery/removal violation. Question is how do I do that? what command I use? and how I use that command? In VCS I have checked related site, and internet, I came across notimingcheck. But is this c
Hai all, what is the difference between recovery time & removal time? Where we are we are using these ? What is the advantage of these both? Thanks.......
Hi all, While doing removal & recovery time characterization for 45nm library, i find erroneous results for high clock pin & CDN/SDN pin transition time. Please suggest me what measures can be taken for characterizing flops with higher transition times values of clock signal or asynchronous signals ( reset/clear ). Regards, Nitin
Hi all. What is the similarity between recovery / removal & setup/hold time characterization ? to find recovery time charac, do we need to consider clk-Q delay again like setup charac ? Thanks, Nitin
Hi, I am confused which should be set for asynchronous control signal, false path or recovery and removal constrain? Could you tell me how to choose and why? Thanks!
Is reset recovery time with respect to assertion of the reset and reset removal time is with respect to reset removal time? Is there any good document which says basics about reset recovery and removal time?
to my knowledge enable_recovery_removal_arcs is the only method to enable reset recovery checks.. what kind of violation do you see in PT...
Functional ECO - to CORRECT/Change the design functionality after the implementation has started and dont have a chance to go back to synthesis Timing ECO - to fix all timing violations such as setup, hold, recovery, removal, DRV (max_fanout, max_capacitance, max_tranisiton)
1. recovery time check and removal time check are the two timing issues in combinational circuits. Glitch is termed as short pulse which happens during undesired time period. For example, a clock glitch will cause a small clock pulse and for that particular pulse, the frequency will be high enough to affect circuit behavior. Pulse width checks will
we use a reset synchronizer in an asynchronous reset design such that it doesnt issue reset in recovery or removal time. Cant we use a synchronous reset in a design instead of going for a reset synchroniser in asynchronous reset design? What would be the real purpose of reset synchronizer?
Types of violation: Setup, hold, recovery, removal, pulse width. How to remove them? setup: Redesign your logic, use more/better synthesis/layout optimisations, change techonology/libraries hold: add buffers
Hi All In the Async Reset based designs the Reset covery and reset removal time plays an important role. We go for the concept even like Async reset assertion and Synchronous removal. 1. My question is when the Async reset is asserted it doesnot looks for the clock signal. Is there any chance of flops going to metastable state when Asyc res
For any asynchronous signal used in a synchronous domain, there are two time constraints called recovery and removal contrainsts. These should be satisfied to ensure glitch free operation. The resets should be synchronously deasserted to overcome removal time constraints associated with the reset. Added after 1 minutes:
I think the problem is how width the rstn plus is. There are several cases: 1. the rstn voilated for recovery or removal time. 2. Even if reset synchrinized. if the plus is too narrow, the clk_a/clk_b/clk_a can't sample it. Thus, i think you should make sure the rstn plus is wide enough.
Setup and hold time checks applies to latches (enable pins) while recovery and removal applies to reset pin checks (of flops).
I heard about recovery time & removal Time.. Its similar to setup time & hold time, but we use these terminology only for asynchronous(Reset & set) pins. What is revival time?.