How to add bootloader to device

RE: How to add bootloader to device

Jorge — Mon, 11 Sep 2017 09:10:25 GMT

What I have made for my DFU to work was to not check the crc inside the function bootloader_app_is_valid(). I have made that this function always returns true.

The other way I could not update the bootloader.

RE: How to add bootloader to device

bjorn-spockeli — Fri, 08 Sep 2017 14:32:22 GMT

You're not able to update the bootloader using Serial DFU, but you're able to update the application and the SoftDevice? You have to remove the BANK_VALID_APP flag from the code when you generate the bootloader hex to use in the DFU zip packet, i.e. set

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

Otherwise the hex file will be to large( you'll include an empty flash page) which will result in the image being rejected.

RE: How to add bootloader to device

Jorge — Wed, 30 Aug 2017 12:54:18 GMT

I have successfully built the bootloader. And with it I can now load every part of the code except the bootloader itself. I can load via DFU different applications, Softdevice and even different bootloaders. But I cannot load via DFU this bootloader project. I am not sure why but it's giving me a timeout error. Do you have any idea why the bootloader project is not loaded correctly using the serial DFU?

RE: How to add bootloader to device

Jorge — Fri, 04 Aug 2017 13:55:54 GMT

I don't know why, but it seems that I have to load first the SD, then the Bootloader and at the end the app. Doing this everything work. On my board and on the DK, not sure why it doesn't work if I send the bootloader after the application...

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 12:12:28 GMT

Ok, let me know what you find out.

RE: How to add bootloader to device

Jorge — Fri, 04 Aug 2017 11:40:08 GMT

It has the 32KHz crystal connected. On my ble_app_uart I use this clock configuration and then I use NRF_CLOCK->XTALFREQ = 0xFFFFFF00; to set the 32KHz clock.

When I want to use the app on the DK board I just comment this last part and it still works. So I think the bootloader is not running on my custom board because of some clock configuration related problem. I will make more tests on this then.

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 11:29:42 GMT

Does your custom board have the optional 32kHz crystal? If not, then the configuration you had is correct.

RE: How to add bootloader to device

Jorge — Fri, 04 Aug 2017 11:24:07 GMT

I had the clock configuration different, using the RC, because of my custom board.

Now with your configuration of the clock the device advertises.

The clock configuration I had was :

 nrf_clock_lf_cfg_t rc_clock_lf_cfg = { .source = NRF_CLOCK_LF_SRC_RC,	\
.rc_ctiv = 4,											\
.rc_temp_ctiv = 1};

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 11:07:36 GMT

What kind of clock configuration do you have in the bootloader project, i.e. is the NRF_CLOCK_LFCLKSRC set to the following?

#define NRF_CLOCK_LFCLKSRC      {.source        = NRF_CLOCK_LF_SRC_XTAL,            \
                                 .rc_ctiv       = 0,                                \
                                 .rc_temp_ctiv  = 0,                                \
                                 .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM}

Because the debugger will force the clocks of nRF51 to stay on, but once you disconnect it then they will not be on.

RE: How to add bootloader to device

Jorge — Fri, 04 Aug 2017 09:26:14 GMT

I have runned the debugger on the bootloader, and after the breakpoint on the bootloader_app_start() I just let it run. If I do this then the app works, but the moment I stop the debugging the app stops to work. Even rebooting the board doesn't work.

It seems there is some difference running from the debug session or not.

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 08:59:19 GMT

Flash all the .hex files, i.e. SD, app and BL. If you reach the breakpoint in main, then set a breakpoint at the bootloader_util_app_start(CODE_REGION_1_START); statement in bootloader_app_start() in bootloader.c at line 308. If you reach this function, then it means that the bootloader is branching to the application. You should then start a debug session in the application and set a breakpoint in its main.

RE: How to add bootloader to device

Jorge — Fri, 04 Aug 2017 08:49:15 GMT

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?

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 08:32:52 GMT

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?

RE: How to add bootloader to device

Jorge — Fri, 04 Aug 2017 07:59:05 GMT

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.

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 07:55:30 GMT

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

RE: How to add bootloader to device

bjorn-spockeli — Fri, 04 Aug 2017 07:48:56 GMT

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