The update-risk preventive method?

[Ralph]

Hi, we are using SoC nrf52810 SDKv14.2-SR3v1.2 for our RCU.

1.If there is a scenario the image transfer is finished, and the power lost happens when the old image is being replaced :

If BL update:  Will the whole boot loader crash and the RCU become malfunctioning permanently?

If App & SD update: Crash,too?  Can BL identify the app or the SD is uncompleted and back to DFU mode?

2.If the image has some bugs to freeze the the whole process in the begging before you can enter DFU mode,

Can BL know the App or SD even itself has some wrongs and back to DFU by a counter or a timer?

3. Updating BL maybe dangerous if it fails, but as SDK keeps upgrade with new version. Can we not update the BL but only App & SD? 

Thanks.

[Jørgen Holmefjord]

Hi,

Please see the last section (Support for nRF52810) of SR3 firmware v1.2 documentation: DFU - before you start:

The Smart Remote bootloader adds modifications required to run it on the nRF52810 SoC.

Due to smaller flash and RAM area available on nRF52810, there are significant configuration differences for the bootloader targeting nRF52832 and nRF52810. On nRF52810, it is not possible to update the bootloader or the SoftDevice (only the application can be updated). When the application is downloaded, the old application is always deleted (the in-place application update model is used).

Best regards,
Jørgen