How to add bootloader to device

[Jorge]

Hi all,

I am started my project using the softdevice S130 v2.0.1 and the ble_app_uart example(SDK11) on a custom board with the nRF51822. I had to made some changes for the clock source because of the custom board, but I am able to connect to the device with the SD+app.

I wanted for the next step include the Bootloader so the device can be updated via DFU. For the bootloader I started with the example single_bank_serial_s130 from SDK11.

But when I load the 3 parts (SD+app+BL) the device doesn't advertise.

I had to made the same changes on the clock on the bootloader code, but I am still not able to connect to the device after loading the bootloader.

I thought it was the IRAM settings as I posted this question, but this seems to not being the case.

1- How should I debug this, start the debug session with the app code?

2- Do i need to press any button to go for the app?

3- Do I need to add something more to the bootloader?

Edit 1:

I tested everything on the DK51 board and when I load the bootloader the app stops advertising. Is there any specific order to load the parts (BL, SD and app)?

The bootloader example using single bank should work without any change on the DK51 board, correct?

[bjorn-spockeli]

Hi Jorge, the serial bootloader does not advertise, so this is expected, but I think the issue with the application not starting is that the bootloader settings does not state that there is a valid application.

In order to flash a combined SoftDevice, Bootloader and Application, where the device jumps to the application without having to perform a OTA update, you have to set the BANK_VALID_APP flag in bootloader_settings.c, i.e. change the line

uint8_t  m_boot_settings[CODE_PAGE_SIZE]    __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used));   

to the following

uint8_t  m_boot_settings[CODE_PAGE_SIZE]    __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used)) = {BANK_VALID_APP};

-Bjørn

[bjorn-spockeli]

Yes, the single bank serial bootloader should work without any modifications to the nRF51 DK. Also see my answer below.

[Jorge]

I have made this change but the app still doesn't advertise. I am not sure if I have to load the parts in some specific order, I am loading the SD130 first then the Bootloader130 and after this the app. But I still don't see the device advertising the uart profile.

If I load only the SD + app then I can see it advertising.

[bjorn-spockeli]

The order should not matter. Are you able to merge the Bootloader, SoftDevice and Application using mergehex with out any errors? If not then you have overlapping hex files. Could you try to start a debug session in the bootloader project, set a breakpoint in main and see if you reach it?

[Jorge]

I can merge the three files together without any errors.

For the debugging should I have all the parts on the board or just the SD and bootloader?