--- Quote Start ---
Are you doing this in TimeQuest?
The Data Arrival Path includes your clock delay + data path delay. The Data Required is the clock delay to the latch register. For slack calculations it will do Data_Arrival-Data_Required, which means the two clock delays will be subtracted from each other(and the result will not be 0, which means the clock delay is important and can't be fully ignored, although hopefully the skew is small)
--- Quote End ---
It goes to timequest when you click on the setup time error.
The clock delay includes ti crystal input and PLL times, which are totally irrelevant and could be msec without having any effect since the clock to data out is only related to the PLL clock output. So there cannot be a delta in the clock delays (like best vs worst case timing) since it is the same clock for both endpoints.
Honored Contributor
