NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Vidar Berg — Fri, 23 Oct 2020 15:27:53 GMT

I'm glad to hear that. Thank you for the update.

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Serg22 — Fri, 23 Oct 2020 14:46:52 GMT

Ok, modified nrf_dfu_req_handler_init(), to initialize nrf_dfu_flash_init(), based on whether SD is enabled or not, and now it works. Thanks for support.

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Vidar Berg — Fri, 23 Oct 2020 13:38:10 GMT

You don't have to enable the Softdevice, but you do need to make sure you are using the correct fstorage backend at all times. So, you should use the SD backend during BLE DFU and the nvmc backend for everything else (i.e. during GSM DFU and image activation)

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Serg22 — Thu, 22 Oct 2020 14:05:16 GMT

Ok, looks like Softdevice was not enabled in my custom implementation, that explains why NVMC backend worked. Now flash erase/write works.
But the custom update implementation that used NVMC before seems to be blocking, and now when flash operations go through SD it seems to be asynchronous, and my bootloader goes to inactivity, because it does not get an event.
How can I track nrf_dfu_flash results by polling or with some feedback? See picture.

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Vidar Berg — Thu, 22 Oct 2020 10:04:58 GMT

Ok, sd_irq_initialized must be set to false if nrf_dfu_settings_init() is called before the Softdevice has been invoked through the BLE transport initialization. Anyway, I think the problem has to be that the bootloader is selecting the NVMC backend when the Softdevice is enabled.

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Serg22 — Wed, 21 Oct 2020 13:30:34 GMT

If I call nrf_dfu_settings_init() with sd_irq_initialized=true, an error occurs already during regular bootup(same for both FDS_BACKENDs). See screenshot.

RE: NRF_FSTORAGE fails to write/erase during update in Bootloader with two update options. BLE and GSM.

Vidar Berg — Wed, 21 Oct 2020 12:19:55 GMT

Hello,

The fault id from your DFU log corresponds to NRF_FAULT_ID_APP_MEMACC, and according to the "info" parameter, it's raised because of an access violation to the NVMC peripheral, which seems to match the behavior you're experiencing. But I'm not sure why the wrong fstorage backend gets selected. Does it work if you call nrf_dfu_settings_init() with sd_irq_initialized=true?