FDS fails to initialise with bootloader present

RE: FDS fails to initialise with bootloader present

Jørgen Holmefjord — Tue, 15 Feb 2022 15:53:53 GMT

Hi,

This post may be relevant to answer your questions.

Best regards,
Jørgen

RE: FDS fails to initialise with bootloader present

RPDben — Tue, 08 Feb 2022 14:29:04 GMT

Hi Jørgen,

I have done a bit more investigation and have concluded the following. The below results were all achieved with the same Bootloader, Softdevice and application.

Program SD and BL using nRF Connect and DFU application.
1. Application runs as expected.
2. A hard reset was performed by pulling the RESET pin low and application still runs as expected
Program SD and BL using nRF Connect and DFU application. Try to "Debug" from SES with same application.
1. Application starts to run but fds_evt_handler is never invoked after the fds_init
Program SD and BL using nRF Connect and DFU application. Try to "Download" from SES with same application.
1. Application fails to initialise the stack - nrf_sdh_enable_request() returns ERROR 8 [NRF_ERROR_INVALID_STATE] (As viewed through J-Link RTT Viewer)

It would be great to understand why there is a difference in the behaviours despite all code being the same and I can get my code working while Debugging in SES.

Thanks,

RE: FDS fails to initialise with bootloader present

Jørgen Holmefjord — Thu, 03 Feb 2022 14:11:07 GMT

Hi,

Which application are you testing with?

I just tried out the flash_fds pca10056/s140 example from SDK 17.1.0 together with the S140 secure BLE bootloader on nRF52840 DK, and this works fine.

Are you using the softdevice or NVMC backend in your FDS application? Are you enabling the softdevice in the application before using FDS?

Best regards,
Jørgen