Remote Update IP not reporting CRC error

Hi 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.😉 😉 😉

​ Hi Mshafiq,

I tried to corrupt the first sector,

When I corrupt the first page (offset 0x01000000) after POR the application image loads correctly from the flash and the all bits of “reconfiguration trigger” is ‘0’.

When I corrupt the second page of the first sector (offset 0x01000100) the factory image loads and the “reconfiguration trigger” bit 0 is ‘1’ (0x1).

When I erase the whole sector the factory image loads and all the bits of “reconfiguration trigger” is ‘0’.

Thank for your help,

Roman.

Hi,

I'm really apologize for late reply. I got an urgent project in last month.

May I know your status in this issue? Are you able to solve and find the solution?

😉

Hi Mshafiq,

Unfortunately I didn’t manage to solve this issue,

I still receiving ‘0’ at all the bits of the “reconfiguration trigger” parameter when erasing the first sector.

Thanks in advance,

Roman.