This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FDS fails to initialise with bootloader present

Hi,

I am getting a strange issue in my code where my FDS will run fine if there is no bootloader but fails to initialise if there is a bootloader present. I am using SDK 17.1.0 and S140 V7.2.0 on an nRF52840. I am using the pca10056_s140_ble secure bootloader example from SDK 17.1.0 unedited.

The error I am seeing is the function fds_init() returns with error code '0' (Success) but the FDS Event Handler is never invoked to say the Init has been complete. Without the bootloader present, the same code runs fine and the Event handler is invoked as expected.

Any help on why this might be the case would be much appreciated.

Parents
  • 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

Reply
  • 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

Children
  • 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.

    1. 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
    2. 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
    3. 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,

  • Hi,

    This post may be relevant to answer your questions.

    Best regards,
    Jørgen

Related