Random single hold violations on Arria V design that doesn't push timing or util. ???

would prefer not to - delay buffers != registers - it adds analog (timing) delays to fix hold vios all over the chip. The solution here was to let it implement a few of the multipliers in LUTs

best

/j

Hold violations are cause by routes between registers being too long. To fix them, you make the distance between the reg's shorter. If this becomes too hard, because there are too many luts between the reg's, or the regs are inside the multiplers that cannot move, the easiest way to fix it is to add another stage in the pipeline between the multipliers to allow the fitter to shorten the distance between registers.

LUT based multipliers will have poorer timing performance that the hard ones.

--- Quote Start ---

there are no analogue buffers in FPGAs.

--- Quote End ---

so how does Quartus fix timing violations caused by clock skew? (sorry, I'm an ASIC guy where adding delay buffers is how you fix hold vios).

--- Quote Start ---

LUT based multipliers will have poorer timing performance that the hard ones..

--- Quote End ---

you think? :-)

/j

--- Quote Start ---

so how does Quartus fix timing violations caused by clock skew? (sorry, I'm an ASIC guy where adding delay buffers is how you fix hold vios).

--- Quote End ---

Basically, it will try and move the registers around, and maybe try a different routing.

There are no buffers in FPGAs. Unlike Asics - generates clocks in FPGAs are a bad idea. they can have massive skew on them as the routing is not up to scratch. Clock enables are the much prefered/recommended method

In the olden days, designers used to use LUTs to delay signals to account for skew or delay. AHDL even has an LCELL function that would insert an extra LUT for you at the HDL level. But as chips clocked faster, this trick became less reliable as the effects of temperature , placement and routing had a much greater effect on the delay than the LUTs themselves, so you have no reliable way to delay a signal enough.

So, in FPGA land, the only way to fix hold violations is to make the route shorter. Easiest way to make the gap shorter is to reduce the logic between registers. Or when it comes to DSPs or RAMs, add extra pipelining. It's quite common when you get to the limits of the chip fmax, you can only have 1 or 2 luts between registers, and even then as the chip gets full, extra pipeline states are required to account for the routing delay and congestion around the chip.