Easy development with BL + SD + APP

RE: Easy development with BL + SD + APP

raphael_gsa — Wed, 15 May 2019 11:59:23 GMT

Hi awneil,

Simply because some applications like app_ble_buttonless_dfu require a bootloader to be flashed to be able to start.

Regards

RE: Easy development with BL + SD + APP

raphael_gsa — Wed, 15 May 2019 11:57:49 GMT

Hi Einar,

Your second solution seems to be exactly what I was looking for !

Thanks a lot.

RE: Easy development with BL + SD + APP

awneil — Wed, 15 May 2019 11:24:06 GMT

[quote userid="76201" url="~/f/nordic-q-a/47310/easy-development-with-bl-sd-app"]like I'm used to do it for any non-bootloader related application ?[/quote]

Why not just do your development as a non-bootloader application?

Then only do the bootloader stuff when it's actually ready to be deployed in a bootloadable format ...

RE: Easy development with BL + SD + APP

Einar Thorsrud — Wed, 15 May 2019 11:20:35 GMT

Hi,

The problem when building and testing/debugging a modified application when you have a bootloader is that the bootloader does a CRC check of the application at startup, and if the CRC does not match, the bootloader enters DFU mode instead of starting the application. There are a few ways to handle this problem:

1. After building and programming the updated application, use nrfutil to generate a new setting page providing the new application .hex, and then program it using nrfjprog with the --sectorerase option. This will make the settings page contain the correct CRC and the bootloader will start the application.

2. A simpler option is to just modify the bootloader so that it does not do a CRC check during startup. Then you can always add back the CRC check before going to production. This can be done in several ways, for instance by modifying the crc_on_valid_app_required() implementation in <SDK 15.3>\components\libraries\bootloader\nrf_bootloader.c like this:

static bool crc_on_valid_app_required(void)
{
    return false;
}