docdrew32
Newbie
Hello everyone,
First time post, long time viewer. I've been using Cadence's Innovus P&R tool for several years now, but have not noticed this irritating feature until now because my timing has always been able to close. However, it seems like every time i run a command or set of commands to fix the hold violations, Innovus decides to also insert additional delay cells and/or buffers on my setup paths, even if those are already passing static timing analysis (STA). I have been digging through documentation and have even started a case with Cadence, but was optimistic someone else out there has figured out what commands are necessary to just fix the hold violations without degrading the setup timing.
thanks
First time post, long time viewer. I've been using Cadence's Innovus P&R tool for several years now, but have not noticed this irritating feature until now because my timing has always been able to close. However, it seems like every time i run a command or set of commands to fix the hold violations, Innovus decides to also insert additional delay cells and/or buffers on my setup paths, even if those are already passing static timing analysis (STA). I have been digging through documentation and have even started a case with Cadence, but was optimistic someone else out there has figured out what commands are necessary to just fix the hold violations without degrading the setup timing.
thanks