Why does my Intel® Stratix® 10 SoC device fail to boot or configure correctly, if I reset the HPS while a configuration event is taking place?

Due to a problem in the Intel® Stratix® 10 Secure Device Manager firmware, the Intel Stratix 10 SoC may fail to boot or configure correctly if a HPS reset event is triggered during a configuration event.  

If Intel Stratix 10 SoC Remote System Update is enabled on the device:  

• A boot failure during Phase 1 (re-)configuration can trigger a Remote System Update Watchdog event to trigger a reconfiguration event to recover the device.

To avoid this problem ensure the following situations do not occur: 

•  nCONFIG and HPS_COLD_nRESET  SDM I/O pins are both asserted
•  A HPS reset (HPS_COLD_nRESET SDM I/O pin) is issued during an FPGA configuration or re-configuration event. For example:  In a system using the HPS Boot First flow: While the HPS is (re-)configuring the FPGA Core Logic using a Phase 2 configuration bitstream.

Note:

• It is not required to cold reset the HPS if the intention is to reconfigure the device using the nConfig signal. The nConfig event will wipe the entire device, and then reconfigure the device from the selected boot device (MSEL pin setting).
• nConfig must not be issued when an HPS reset is in process. If there is a HPS reset in process,  wait for the HPS reset to finish before issuing nConfig : Greater than 10 ms from the time a HPS reset is triggered.
• If Intel Stratix 10 SoC Remote System Update is enabled on the device:  A boot failure during Phase 1 (re-)configuration can trigger a Remote System Update Watchdog event to trigger a reconfiguration event to recover the device.

Also see:  Why does my Intel Stratix 10 SoC design sometimes fail to detect a transition on hps_cold_nReset

This problem is fixed starting with the Intel® Stratix® 10 Secure Device Manager firmware version 20.3.