--- Quote Start ---
If your PLL settings in the MegaWizard can't be implemented exactly, you probably got compilation messages (it seems like they happen in the Fitter, but I don't remember for sure) comparing the requested settings and the settings actually being implemented. I prefer to change the MegaWizard settings to the actually implemented values to get rid of these messages about the mismatch.
--- Quote End ---
I'm not getting any warning whatsoever. Of course that the difference is minimal, not really significant. Otherwise, if the difference is important, the MegaWizard does display a "red" warning that the PLL setting can't be implemented.
However I was wrong about TimeQuest using the "requested" frequency. It is just a cosmetic issue in the clock report, where the clock frequency displayed is rounded. The period is accurate and it is the actual one.
--- Quote Start ---
The output enable path will be reported if the data port is constrained by either set_output_delay or set_max_delay. Run report_timing with a data port in the -to field
--- Quote End ---
Ah, yes, I see it now, and it is being constrained automatically as another path.
I was right-clicking in the I/O report to make the Timing Report. But then the "from" field is set, and that's why it didn't include other paths.
It still seems odd to me that the datasheets don't even mention the Txz/Tzx timing. It was included in the older families.
Honored Contributor
