Forum Discussion
Occasional ContributorArria 10: Remote Update Watchdog unpredicted behavior
Hello Fabian,
Thanks for the reply.
Functional error in that context is when the logic that is responsible to reset the WD timer fails to do its task, which will initiate a fallback mechanism. The third paragraph actually correlates with the first paragraph. Factory fallback needs to meet certain conditions when in application configuration for it to happen, so expecting the fallback mechanism to occur with everything working correctly is a wrong understanding.
regards,
Farabi
Occasional ContributorHello Farabi,
actually yes. From the datasheet section, I would interpret this in the way, that the watchdog needs to be triggered or disabled by the application image and serves as a functional validation:
Additionally, the remote update mode features an optional user watchdog timer that can detect functional errors in an application configuration.
It seems to be even more clear from section 1.3.2. Remote System Configuration Components
Arria® 10 and Cyclone® 10 GX devices are equipped with a built-in watchdog timer for remote system configuration to prevent a faulty application configuration from indefinitely stalling the device.
If the application configuration does not reset the user watchdog timer before time expires, the dedicated circuitry reconfigures the device with the factory configuration and resets the user watchdog timer.
But maybe I have a wrong understanding of these datasheet sections.
So you state, once the application image is successfully loaded the watchdog will be disabled and won't trigger any fallback anymore?
So it only covers the image loading procedure?
best regards
Fabian
Farabi_AlteraRegular Contributor
Hello Fabian,
If your Application Image is not corrupted, the system will stay with Application Image and not fallback to factory image. Why you want your system to load factory image after a successful Application image load?
regards,
Farabi
- Farabi_Altera
Hello Fabian,
Can you response to my last question?
regards,
Farabi
- FabianL
Hello Farabi,
I'm very sorry for my very late reply. As mentioned, that is what I have read from the official Intel/Altera datasheet. Please read my last post with the relevant citations.
the datasheet explicitly mentions that the "application configuration" resets the watchdog. ==> Hence I expect that the application load needs to reset the watchdog.
It also explicitly mentions "functional errors in an application configuration". If it's designed to cover functional errors and not only format errors (as for a corrupted application load) it requires interaction with the application configuration to allow functional verification. e.g. it could be triggered only after the configuaration has checked that is functional with all peripherals.
Anyway that is the Intel/Altera datasheet which makes this claim. If it is not the case, please clarify what the intention of these datasheet sections is.
Additionally, the remote update mode features an optional user watchdog timer that can detect functional errors in an application configuration.
Arria® 10 and Cyclone® 10 GX devices are equipped with a built-in watchdog timer for remote system configuration to prevent a faulty application configuration from indefinitely stalling the device.
If the application configuration does not reset the user watchdog timer before time expires, the dedicated circuitry reconfigures the device with the factory configuration and resets the user watchdog timer.
- Farabi_Altera
Hello Fabian,
Thanks for the reply.
Functional error in that context is when the logic that is responsible to reset the WD timer fails to do its task, which will initiate a fallback mechanism. The third paragraph actually correlates with the first paragraph. Factory fallback needs to meet certain conditions when in application configuration for it to happen, so expecting the fallback mechanism to occur with everything working correctly is a wrong understanding.
regards,
Farabi
