Hi Vasakpal,
This behavior is expected with MAX 10 RSU. RSU itself does not run your “autoboot” logic. It only controls which image is loaded on the next reconfiguration.
For a warm reconfiguration, the device will follow the CONFIG_SEL pin unless you explicitly enable overwrite in the RSU input register. The ru_config_sel bit only takes effect when ru_config_sel_overwrite = 1.
Recommended actions:
- Before triggering reconfiguration, write ru_config_sel_overwrite = 1 and ru_config_sel = 1 (select Application), then assert RU_nCONFIG. Remote System Upgrade Input Register
- If your flow relies on “Factory boots first, reads UFM, then triggers a second reconfig to Application”, you must still generate that second reconfig event in your RTL/firmware after the Factory image comes up. RSU will not do it automatically. Updating Image and Triggering Reconfiguration using UART
- Also check the user watchdog timer. If enabled and not reset by the Application image soon enough, the device will revert to the Factory image.
For reference patterns, MAX 10 RSU lab and AN 741 show the intended “select image then trigger reconfiguration” sequence.
Regards,
Fakhrul
New Contributor
