New Contributor
New Contributor
Hi Mshafiq,
Actually the parameter “Enable reconfig POF checking” is disabled (grayed out) in the IP parameters menu.
The RU IP user guide states about this parameter:
“Not available as this option is handled by the FPGA AS
controller instead of the Remote Update Intel FPGA IP
core. The same application image is loaded for three
times before reverting to factory application image, to
ensure no unexpected system failure occurred.”
Also I tried to disable and enable the “Auto-restart configuration after error” option “from the device and pin options“ menu.
No luck so far.
Please advise ,
Thanks Roman.
Frequent ContributorHi Roman,
I'm sorry I missed that you are using Cyclone 10 GX (this device didn't have POF checking option).
If I'm not mistaken, POF checking option already embedded for Cyclone 10 GX (you can't disable it anymore.)
Another thing that I suspect is Remote Update IP detect your programming file as Blank. Since you are erasing the first sector (offset 0x01000000) of the application image, Remote Update IP detect as Blank file, not corrupted file. Therefore, the “Reconfiguration trigger Conditions” parameter state show 0x0 (bit 0 - no CRC error), because the file is blank not corrupted.
Maybe you can try to corrupt the first sector (offset 0x01000000) by replace it with Random bit rather than erase it. Let me know if this is working.
I wondering when you mention “Reconfiguration trigger Conditions” parameter state 0x0 (no error), do you mean only bit 0 is 0x0(no error)? Or for all bit 0-4 is 0x0?
Some of bit 0-4 should trigger when you able to load to Factory Image.
Thanks.😉 😉 😉
