Remote Update of Cyclone 10

Hi,
Cyclone 10 remote upgrade logic is expecting that application image is started through factory image. Start address and parameters, e.g. watchdog are set in this step. Starting application image directly would probably prevent fallback to factory image in case of failure. What's against using the standard solution?

The standard solution just doesn't fit that nicely into my application. I just want the factory page to be a fallback golden configuration in case anything corrupts the reprogramming process of the application page. This will then still allow additional tries at programming the new application config data. If I have to load the factory config, then trigger another load of the application config, which if it failed would then cause a third configuration cycle to reload the factory config. This would take extra time to get to a point where the FPGA is operational. It also adds extra requirements on the factory config to trigger the application load and also determine if that failed previously and therefore shouldn't be loaded again. It all just makes it more convoluted and complex. I just need a simple system that loads my application at power on and falls back to the factory config if an error occurs. Is there not a way to do this without the baggage of the remote config as you describe above?

Should I take the silence on this thread to mean there is no way to accomplish the simpler option I an looking for and will have to load the factory config first then load the application?

Thanks

Brad

Hi BCrowell,

Unfortunately, executing a direct switch from the application image to another application image (golden configuration) in the event of an error, without intermediate steps (such as going through the factory image), is not possible. This intentional design decision is made to bolster security and mitigate the risk of unauthorized access.

Regards,

Fakhrul

Fakhrul,

I am ok with my golden config being the factory image, I just want to directly load the application config and only load the factory config if that fails. It sounds like that can't be done and the system needs to load the factory config first before switching to the application config in order to properly fall back in the event of an error. I don't necessarily see the advantage of this process but I haven't used Intel/Altera FPGAs in many years, so I just may be missing something. Is there something that the factory config does that differentiates it from an application config besides initiating the loading of an application config?

Thanks

Brad

Hi BCrowell,

The factory configuration initializes the FPGA into a known state, ensuring that all essential components are set up correctly. This is crucial for the reliable and safe operation of the FPGA. It helps prevent undefined behavior that might occur if the FPGA were to start with no configuration or an arbitrary state.

Regards,

Fakhrul

Hi BCrowell,

Please ignore my earlier comment. I consulted with my senior, who is an expert in RSU, and it turns out you can load the application configuration directly and only resort to loading the factory configuration if error occurs. This is known as "Direct to Application" (DTA). For more detailed information about DTA, please refer to pages 6-7 in the Remote Update Intel® FPGA IP User Guide : https://cdrdv2.intel.com/v1/dl/getContent/794025?fileName=ug_altremote-683695-794025.pdf

Regards,

Fakhrul

I agree with FvM as it appears Direct to Application is not included for Cyclone 10 LP. In my Cyclone 10 LP project however I can select that option to have the device auto restart after an error. Not sure that it means it will do it though. Also, in direct to application mode how does the address register get set in the remote update IP core?

Hi BCrowell,

Regarding the address register, you may refer to this Cyclone 10 LP Remote System Upgrade Design Example User Guide. The mentioned design example can be found here: Intel® Cyclone® 10 LP FPGA – Remote System Update Design Example

Regards,

Fakhrul

Fakhrul,

Yes, that is the example I am trying to simulate. I reviewed the user manual already and downloaded the design files. When I put together the simulation for these files and extended it to read the data from the update core though I get the X's when the registers are read back.

Brad