boot from app to bootloader SDK12 and S132 V3.0

RE: boot from app to bootloader SDK12 and S132 V3.0

Adrian Eggenberger — Fri, 09 Dec 2016 10:21:00 GMT

Hi Darren, All that's needed on the bootloader side is to add the upper code at the top of the nrf_dfu_enter_check function. Regards Adrian

RE: boot from app to bootloader SDK12 and S132 V3.0

WestCoastDaz — Thu, 08 Dec 2016 19:09:13 GMT

Adrian,

Are you willing to share your changes on using GPREGRET? I'm just about to do this on our design.

RE: boot from app to bootloader SDK12 and S132 V3.0

JosePastor23 — Mon, 05 Dec 2016 10:58:42 GMT

Thanks Adrian, It worked. I will have into account for future updates. I will also create a new question thread to let nordic explain the bootloader check method.

RE: boot from app to bootloader SDK12 and S132 V3.0

Adrian Eggenberger — Mon, 05 Dec 2016 10:29:18 GMT

The new signed DFU doesn't use the GPREGRET registers to decide if the bootloader should enter bootloader mode or not. The new mechanism is based on a bit in the bootloader settings that is manipulated by the application. I personally would have preferred the method with the GPREGRET because I don't like that fact that the application must write to the bootloader settings. In my opinion only the bootloader should write to the bootloader settings. Side question: Why did Nordic change the way to enter the bootloader?

The new implemenation of Nordic is in the service implementation ble_dfu.c. This file is also used in there buttonless example.

For my own projects modified there code to the old behavior with the GPREGRET registers. In the implementation of the function "nrf_dfu_enter_check" I've added the following code:

if (NRF_POWER->GPREGRET == BOOTLOADER_DFU_START)
{
  NRF_POWER->GPREGRET = 0;
  return true;
}

Additionally the define for BOOTLOADER_DFU_START must be added. With this modification you could enter the bootloader the same way as you did with the old basic DFU.

Regards Adrian