remote update module for cyclone 10 GX

Hi Aiman,

Sorry for the late response as my company block this page and i try to use another account to reply.

Regarding the DCLK on the configuration device: before increasing the clock speed, the default setting of the clock divisor is 0x10 (which corresponds to a division by 32), resulting in a DCLK frequency of 1.5625 MHz. After changing the divisor to 0x1 (which corresponds to a division by 2), the DCLK frequency increased to 25 MHz, given that the input clock to the generic serial flash module is 50 MHz. This output appears to be as expected.

As for my understanding of the remote update module:

In the application image code, we can set the timeout value by writing to the RU_WATCHDOG_TIMEOUT parameter. Afterward, we enable the watchdog by setting the RU_WATCHDOG_ENABLE parameter to 1. To prevent the system from reconfiguring to the factory image, we need to periodically reset the timer by writing a value to RU_RESET_TIMER.

However, it seems that the watchdog does not function as intended, even though it is enabled and the timer is not being reset. Could you help me verify if I have misunderstood any of these functions?

Thanks

Paul

Hi Alman,

-What is the result of time out parameter?

In the application program, I set the following registers:

• IOWR_ALTERA_RU_CONFIG_MODE(REMOTE_UPDATE_BASE, 0x00); //Configures the factory image.

• IOWR_ALTERA_RU_PAGE_SELECT(REMOTE_UPDATE_BASE, 0x20);//Starts at address 0x20 for the factory image.

• IOWR_ALTERA_RU_RESET_TIMER(REMOTE_UPDATE_BASE, 0x00);//Does not reset the timer.

• IOWR_ALTERA_RU_WATCHDOG_TIMEOUT(REMOTE_UPDATE_BASE, 0x0A);//Sets the timeout value to 0x0A.

• IOWR_ALTERA_RU_WATCHDOG_ENABLE(REMOTE_UPDATE_BASE, 0x01);//Enables the watchdog.

After enabling the timer, the main loop continues to read back the watchdog timeout parameter, which same as the value I set with change in the timeout value:

• IORD_ALTERA_RU_WATCHDOG_TIMEOUT(REMOTE_UPDATE_BASE, 0x0A); //Reads back the timeout value of 0x0A.

• IORD_ALTERA_RU_WATCHDOG_ENABLE(REMOTE_UPDATE_BASE, 0x01); //Ensures the watchdog is enabled.

I expected that setting the timeout and enabling it without resetting the timer would trigger a reconfiguration after timeout value reduce to zero, but it did not (even the timeout value do not reduce). Please let me know if I misunderstood something.

-What is the value that you set to the reset timer?

To reset the timer, I set the value to 0 (IOWR_ALTERA_RU_RESET_TIMER(base, 0x0)) because I did not want to reset the timer and aimed to trigger the reconfiguration.

-Please provide scopeshot as per my previous response.

The reconfiguration process at higher DCLK frequencies has been resolved. The existing issue is with the watchdog timer not behaving as expected. I will return to the office next week and capture the waveform for your reference.

Thanks
Paul