Update application from SD 2.0.1 to SD 4.0.2

RE: Update application from SD 2.0.1 to SD 4.0.2

Bjørn Kvaale — Mon, 20 Nov 2017 14:48:48 GMT

Hi Vladimir, talked to a dfu expert here at nordic. His suggestions are the following: firstly, could you provide more information on your procedure in step 5? Then, it would be useful if you did a hex dump. Finally, check if the new application and bootloader are copied to your device (i.e. does the bootloader start or not).

Note that with the current smartphone app, when you try to update the softdevice, application and bootloader, there is no flexible option to only re-upload the application of the softdevice & bootloader update was successful. If you then try to update again via the smartphone, the dfu will fail because the bootloader rejects it because of the version check.

RE: Update application from SD 2.0.1 to SD 4.0.2

Vladimir Petrigo — Wed, 15 Nov 2017 15:02:00 GMT

Hello Bjørn,

I tried to do so, but met several issues with missed struct definitions and softdevice function declarations during dfu_transport_ble.c and softdevice_handler.c compilation. This files were taken from SDK 11.

Here are some of them that I've noticed:

ble_gap_whitelist_t type is not defined in the ble_gap.h header anymore
ble_gap.h does not contain sd_ble_gap_address_get anymore
ble.h does not contain ble_enable_params_t for softdevice_handler.c
NRF_LOG_INFO implicit definition - SDK 11 does not have such macro

I've also updated ble_stack_init function in the main.c for legacy bootloader to a newer version provided in nrf_ble_dfu.c in SDK 13.

RE: Update application from SD 2.0.1 to SD 4.0.2

Bjørn Kvaale — Wed, 15 Nov 2017 14:40:01 GMT

Is the custom bootloader in step 4 compiled against the v4.0.2 headers?