--- Quote Start ---
You are absolutely right. The PLL generated clock directly drives an output pin, but I just don't understand, why it should drive an output pin via the dedicated routing resource?
--- Quote End ---
The warning explains the reason. If you use non-dedicated PLL outputs, then jitter performance might suffer a bit.
--- Quote Start ---
And as far as I know, the software globally recognize the PLL generated clock as global clock, so it should use the global routing resource, right?
--- Quote End ---
Once again, global clock is an internal routing issue, it has no relation to the PLL dedicated external output.
--- Quote Start ---
Does it have anything to do with the output pin assignment? How can I correct it?
--- Quote End ---
Yes, of course it is the output pin assignment. No big deal if you can't change it. Most people ignore that warning.
Honored Contributor
