DFU with bonds issue

RE: DFU with bonds issue

bjorn-spockeli — Thu, 31 Jan 2019 15:43:55 GMT

Hi Gerardo,

I sincerly appologize for the late reply. I did a quick test with the secure bootloader and buttonless DFU example from SDK v15.2.0 and I did not see any issues when doing this in this order:

Set NRF_DFU_BLE_BUTTONLESS_SUPPORTS_BONDS to 1 in the sdk_config.h file of the ble_app_buttonless_dfu project.
Set NRF_DFU_BLE_REQUIRES_BONDS to 1 and NRF_SDH_BLE_SERVICE_CHANGED to 1 in the sdk_config.h file of the secure_bootloader project.
Replace the
Compile both projects
Download nrfutil v4.0.0 or newer from https://github.com/NordicSemiconductor/pc-nrfutil/releases

Generate the settings page using the following nrfutil command

nrfutil.exe settings generate --family NRF52 --application ble_app_buttonless_dfu_pca10040_s132.hex --application-version 1 --bl-settings-version 1 --bootloader-version 1 settings.hex

Use mergehex to merge the SD, BL and APP using the following command:
mergehex -m ble_app_buttonless_dfu_pca10040_s132.hex s132_nrf52_6.1.0_softdevice.hex secure_bootloader_ble_s132_pca10040_debug.hex -o sd_ble_app.hex
Use mergehex to merge the sd_ble_app.hex with the settings.hex:
mergehex -m sd_ble_app.hex settings.hex -o sd_ble_app_settings.hex
Flash the combined SD, BL and APP + Settings hex file to the nRF5X device:
nrfjprog --program sd_ble_app_settings.hex --chiperase --reset
nRF5x device should start advertising as "Nordic_Buttonless"

Best regards
Bjørn

RE: DFU with bonds issue

gercer — Mon, 28 Jan 2019 21:04:05 GMT

Still no success, any idea of what I am doing wrong?

RE: DFU with bonds issue

gercer — Wed, 23 Jan 2019 20:07:58 GMT

Thanks for the fast answer.

Yeah, that is what is causing an error.

I tried to do what you suggested but it's not working. Since it's the first time I am using nrfutil for the bootloader settings page i will explain step by step what i did.

1. NRF_DFU_BLE_BUTTONLESS_SUPPORTS_BONDS to 1 in ble_app_buttonless_dfu_pca10040_s132.hex

2. nrfutil settings generate --family NRF52 --application ble_app_buttonless_dfu_pca10040_s132.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 settings.hex

3. then merged the SD, bootloader and the settings.hex i just created using mergehex -m settings.hex secure_bootloader_ble_s132_pca10040_debug.hex s132_nrf52_6.1.0_softdevice.hex -o output_file.hex

4. nrfjprog -f NRF52 --program output_file.hex --chiperase

Could you explain me what I am doingwrong?

As a possible solution, I was wondering if there was possible to do something like this

#if (NRF_DFU_BLE_REQUIRES_BONDS)
    /* Copy out the peer data if bonds are required */
    if (nrf_dfu_settings_peer_data_is_valid())
    {
        NRF_LOG_DEBUG("Copying peer data");

        err_code = nrf_dfu_settings_peer_data_copy(&m_peer_data);
        UNUSED_RETURN_VALUE(err_code);
    }
    else
    {
        restart_application_hex();
    }
#else

RE: DFU with bonds issue

bjorn-spockeli — Wed, 23 Jan 2019 16:05:51 GMT

Hi Gerardo,

The 0x03 error code is NRF_ERROR_INTERNAL.

Can you set a breakpoint in app_error_handler_bare() in main.c and then look at the call stack when this breakpoint is hit? Which function is generating the error code?

I believe its the following snippet that is called after ble_stack_init() in ble_dfu_transport_init() in nrf_dfu_ble.c that is causing the error, i.e. that nrf_dfu_settings_peer_data_is_valid() returns false,

#if (NRF_DFU_BLE_REQUIRES_BONDS)
    /* Copy out the peer data if bonds are required */
    if (nrf_dfu_settings_peer_data_is_valid())
    {
        NRF_LOG_DEBUG("Copying peer data");

        err_code = nrf_dfu_settings_peer_data_copy(&m_peer_data);
        UNUSED_RETURN_VALUE(err_code);
    }
    else
    {
        APP_ERROR_HANDLER(NRF_ERROR_INTERNAL);
    }
#else

It this is the case, then could you try to flash nRF52832 with the Buttonless DFU example with NRF_DFU_BLE_BUTTONLESS_SUPPORTS_BONDS set to 1 in addition to the bootloader and SD. And then also generate a bootloader settings page using nrfutil with the compiled application hex as input and flash that as well.

This should ensure that the device jumps to the application first, which sets the peer data. You can then try to perform DFU, which should now work.

Best regards

Bjørn