Search Engine www.edaboard.com

97 Threads found on edaboard.com: Setup And Hold Violations
Hi, how to fix setup and hold on same path, if we fix hold increase setup violation, and if we fix setup increase hold violation.
If clock latency is the difference in clock arrival at a particular flop compared to the clock source then why do we even care about latency. for eg : if skew is 0 at latency 500 ps (500ps for both launch flop and capture flop) then why would it even factor in setup or hold violations since it is the same for both flops. (...)
Hello all , There are times, when I am not allowed to change the RTL, and all the clocking structure in the design are already optimized. Still I face situations where I have negative slack ( setup as well as hold ) Some times by trying few strategies in Vivado, the tool solves the timing violations, but what if it (...)
Hi frinds.. after post Route fixing setup/hold still i'm seeing some transition violation and fanout violations how to fix them , what are the violations are real....? here are the Fanoutviolation info... ---------------------------------------- *info: there are 121 max fanout load (...)
Hi All Is there any special commands for fixing setup and hold violations after post Route. optDesign doesn't looks good and it couldn't optimize the design. so I think I have to use setOptMode to set some values.. But I dont know the exact parameters. Can anyone Please (...)
Hello all, I have 2 questions here setup and hold violations in same path - yes / no ? setup and hold violations on the same flop - yes / no ? I have know that setup and hold (...)
check this link Fixing setup & hold violations
Better increase uncertainty. Because, increasing clock frequency will not issue any new hold violations (hold is freq. independent). But uncertainty will affect both: setup and hold.
setup violations are sometimes fixed by making changes to the logic. This can only be done preCTS. hold violations are fixed by adding buffers to the data path. This is usually done postCTS. CTS itself leads to many hold violations.
The crosstalk effect adds or subtracts delay from the signal which leads to setup/hold violations. It is because crosstalk adds or subtract energy to the signal which causes setup and hold violations. You can always run the timer with or without SI and see (...)
Hi, I am new to SOC Encounter and I am using First Encounter. When I try to do the physical design flow, I am having setup violations after nanorouting stage. The violation remains even after optimizing the design. I've read that addition of buffers will resolve the issue. But how can I add buffers in the design?? How can I identify (...)
Hi all, in my design after CTS, i have 132 hold violations, and 100 setup violations. how do i can fix with help of ECO. i'm new to ECO. please help me to write ECO script for setup or hold. thank you..
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.
setup failures: Slow scan clock down. hold failures: Increase temperature, decrease voltage. Then complain to the design team.
Hi All, i've a confusion why worst case report is considered as the Max delay violation(setup violation) and Best case report as Min delay(hold violations). and why we always calculate the hold violations at the launching flop. thanks in advance, Arjun
The asynchronous reset must be released synchronous to clock to avoid timing violations and among other issues metastable states. Similarly all inputs to the synchronous process must keep setup and hold timing requirements. Using an reset signal with unrelated timing in a synchronous process won't be (...)
The library timing defined the timing table with two axes: the output capacitance and the input transition, and also indicates max trans/cap for each pins, this value could be the limit of the axes, or smaller (not really good if this is higher than the axes). The max capacitance and max transition violations only indicate (...)
Hello all, Which violation has to give more importance setup , hold or transition comparatively?
The basic questions will be on 1. Clock constraints (master clock, generated clock, clock skew, jitter, clock network delay, source delay) 2. Input and output constraints 3. Virtual clock and the use of it 4. False path and multi cycle path. How will you identify them. 5. How will you fix setup and (...)
can you help me ,how to set the hold violations with out disturbing the setup path/time manually ....???