Forum Discussion
<message corrupted - please delete>
@JonWay_C_Intel i was providing an example of the issue as you had requested in the simplest form possible. It was intended to show the error encountered, not the real application as this is a public forum and i cannot disclose the company's intellectual property in this manner.
To clarify: this error persists, independent of the toggle rate of the pin, as it is an issue with the quartus software deriving the real toggle rate and has nothing to do with the datasheet specification. To highlight this i have modified the example to a division factor of 4, now delivering instead of 500Mhz (=1Gbps) as before an output rate of 250MHz (=500Mbps) which is well within the datasheet specification. You can modify this to any arbitrary division factor, the issue will persist no matter how low you make the toggle rate of the pin:
I have attached the modified examples:
1) version failing during the fitting process "correct implementation of the PLL parameters"
2) successfully compilable "dynamic pll workaround"
These represent the equivalent counterparts to the previous examples:
1) "Config_TestProgram - Not working (1GHz PLL intitial)" (08-28-2020 01:06 PM)
2) "Config_TestProgram - Working (500MHz PLL initial)" (08-28-2020 01:06 PM)
If you wish to have a look to the actual application causing this problem, please provide me a means to contact you in a non-public fashion to exchange the data and / or arrange the potential shipment of the demonstation hardware.
Thank you,
-Chris
P.S.: My appologies for the many posts/edits of this message - something went wrong while updating it to correct a spelling mistake and the post disappeared...
- chris_notsch5 years ago
New Contributor
@JonWay_C_Intel any updates?
- JonWay_altera5 years ago
Frequent Contributor
Thanks @chris_notsch for clarifying the issue. The problem statement is: PLL output clock 1Ghz is divided down by internal logics to 500Mhz at the output pin (set as LVDS IO Standard). Despite not toggling at 1Ghz, why did it complain that it is (thus causing an error of exceeding the maximum rate)?
I am checking on it and will get back to you as soon as i have an update. Thanks.
- JonWay_altera5 years ago
Frequent Contributor
The pll reconfiguration can be used as workaround for now. As for the timing violations related to pll reconfiguration, you may file a new forum case so that the subject matter expert can work on it with you.