Unable to flash after adding bootloader

RE: Unable to flash after adding bootloader

bjorn-spockeli — Mon, 05 Aug 2019 14:14:29 GMT

The application should not place any data to that specific UICR register, its only the bootloader that should do this. 0x10001014 is the register that the MBR checks to see if there is a bootloader present or not.

Do not use nRFGo Studio to flash nRF52 ICs. Use the nRF Programmer app in nRF Connect for Desktop or nrfjprog the latest version of the nRF Command Line Tools instead. See Programming nRF5x SoCs with nrfjprog on how to use nrfjprog.

The layout does not look right. There should be a blue section that contains the SoftDevice inbetween the MBR(orange) and the application (green).

RE: Unable to flash after adding bootloader

Xavier — Fri, 02 Aug 2019 18:21:03 GMT

I can now flash everything normally using nrfgo studio, I just erased all the memory on the device and it now works and an updated version of my app can run. Although, when I use eclipse to debug, I do not know how to use the .hex file instead of the .out and run and debug normally. If I use the .out file generated, it does not update the app. I tried to flash the setting instead of combining with the app using

nrfjprog -f nrf52 --program ./setting.hex --sectorerase

but sadly the debugging still does not work.

RE: Unable to flash after adding bootloader

Xavier — Fri, 02 Aug 2019 15:04:38 GMT

Actually I have fixed this error, I have removed the line

uicr_bootloader_start_address (r) : ORIGIN = 0x10001014, LENGTH = 0x4

in my application linker file, but I still cannot flash.

It says I am flashing in the softdevice section using nrfGo, and for nrf connect programmer I get this layout

I cannot flash using nrf connect programmer, I do not know why. The buttons are simly disabled and the device memory layout is never working

RE: Unable to flash after adding bootloader

bjorn-spockeli — Fri, 02 Aug 2019 14:59:22 GMT

Can you upload the .map files for both the application and the bootloader?

RE: Unable to flash after adding bootloader

Xavier — Fri, 02 Aug 2019 13:39:53 GMT

I tried using nrf connect programmer to flash, but I get a similar error

RE: Unable to flash after adding bootloader

Xavier — Fri, 02 Aug 2019 13:22:28 GMT

Hi Bjørn, thanks for the input.

I tried to merge the settings the bootloader and the app hexfiles by using these commands

../../../nrfutil/nrfutil.exe settings generate --family NRF52 --application ./_build/nrf52832_xxaa.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 setting.hex
mergehex -m ../../bootloader/_build/nrf52832_xxaa_s132.hex setting.hex -o bootloader_and_setting.hex
mergehex -m ./_build/nrf52832_xxaa.hex bootloader_and_setting.hex -o app_bootloader_and_setting.hex

But I get the error "The hex files cannot be merged since there are conflicts" on the last command to merge the bootloader with settings and the app. Since you said my linker settings are correct I am a bit confused.

Here is my linker setting for the Bootloader: (I used the one form the buttonless dfu example so it should work in theory)

/* Linker script to configure memory regions. */

SEARCH_DIR(.)
GROUP(-lgcc -lc -lnosys)

MEMORY
{
  FLASH (rx) : ORIGIN = 0x72000, LENGTH = 0xc000
  RAM (rwx) :  ORIGIN = 0x200057b8, LENGTH = 0xa848
  uicr_mbr_params_page (r) : ORIGIN = 0x10001018, LENGTH = 0x4
  mbr_params_page (r) : ORIGIN = 0x0007E000, LENGTH = 0x1000
  bootloader_settings_page (r) : ORIGIN = 0x0007F000, LENGTH = 0x1000
  uicr_bootloader_start_address (r) : ORIGIN = 0x10001014, LENGTH = 0x4
}

SECTIONS
{
  .uicr_mbr_params_page :
  {
    PROVIDE(__start_uicr_mbr_params_page = .);
    KEEP(*(SORT(.uicr_mbr_params_page*)))
    PROVIDE(__stop_uicr_mbr_params_page = .);
  } > uicr_mbr_params_page
  .mbr_params_page(NOLOAD) :
  {
    PROVIDE(__start_mbr_params_page = .);
    KEEP(*(SORT(.mbr_params_page*)))
    PROVIDE(__stop_mbr_params_page = .);
  } > mbr_params_page
  .bootloader_settings_page(NOLOAD) :
  {
    PROVIDE(__start_bootloader_settings_page = .);
    KEEP(*(SORT(.bootloader_settings_page*)))
    PROVIDE(__stop_bootloader_settings_page = .);
  } > bootloader_settings_page
  .uicr_bootloader_start_address :
  {
    PROVIDE(__start_uicr_bootloader_start_address = .);
    KEEP(*(SORT(.uicr_bootloader_start_address*)))
    PROVIDE(__stop_uicr_bootloader_start_address = .);
  } > uicr_bootloader_start_address
}

SECTIONS
{
  . = ALIGN(4);
  .mem_section_dummy_ram :
  {
  }
  .log_dynamic_data :
  {
    PROVIDE(__start_log_dynamic_data = .);
    KEEP(*(SORT(.log_dynamic_data*)))
    PROVIDE(__stop_log_dynamic_data = .);
  } > RAM
  .fs_data :
  {
    PROVIDE(__start_fs_data = .);
    KEEP(*(.fs_data))
    PROVIDE(__stop_fs_data = .);
  } > RAM

} INSERT AFTER .data;

SECTIONS
{
  .mem_section_dummy_rom :
  {
  }
  .crypto_data :
  {
    PROVIDE(__start_crypto_data = .);
    KEEP(*(SORT(.crypto_data*)))
    PROVIDE(__stop_crypto_data = .);
  } > FLASH
    .nrf_queue :
  {
    PROVIDE(__start_nrf_queue = .);
    KEEP(*(.nrf_queue))
    PROVIDE(__stop_nrf_queue = .);
  } > FLASH
  .dfu_trans :
  {
    PROVIDE(__start_dfu_trans = .);
    KEEP(*(SORT(.dfu_trans*)))
    PROVIDE(__stop_dfu_trans = .);
  } > FLASH
  .log_const_data :
  {
    PROVIDE(__start_log_const_data = .);
    KEEP(*(SORT(.log_const_data*)))
    PROVIDE(__stop_log_const_data = .);
  } > FLASH
    .nrf_balloc :
  {
    PROVIDE(__start_nrf_balloc = .);
    KEEP(*(.nrf_balloc))
    PROVIDE(__stop_nrf_balloc = .);
  } > FLASH
    .svc_data :
  {
    PROVIDE(__start_svc_data = .);
    KEEP(*(.svc_data))
    PROVIDE(__stop_svc_data = .);
  } > FLASH
  .sdh_ble_observers :
  {
    PROVIDE(__start_sdh_ble_observers = .);
    KEEP(*(SORT(.sdh_ble_observers*)))
    PROVIDE(__stop_sdh_ble_observers = .);
  } > FLASH
  .sdh_state_observers :
  {
    PROVIDE(__start_sdh_state_observers = .);
    KEEP(*(SORT(.sdh_state_observers*)))
    PROVIDE(__stop_sdh_state_observers = .);
  } > FLASH
  .sdh_stack_observers :
  {
    PROVIDE(__start_sdh_stack_observers = .);
    KEEP(*(SORT(.sdh_stack_observers*)))
    PROVIDE(__stop_sdh_stack_observers = .);
  } > FLASH
  .sdh_req_observers :
  {
    PROVIDE(__start_sdh_req_observers = .);
    KEEP(*(SORT(.sdh_req_observers*)))
    PROVIDE(__stop_sdh_req_observers = .);
  } > FLASH
  .sdh_soc_observers :
  {
    PROVIDE(__start_sdh_soc_observers = .);
    KEEP(*(SORT(.sdh_soc_observers*)))
    PROVIDE(__stop_sdh_soc_observers = .);
  } > FLASH

} INSERT AFTER .text

INCLUDE "nrf_common.ld"

And as you can see the bootloader does start at 0x72000.

Thank you.

RE: Unable to flash after adding bootloader

bjorn-spockeli — Fri, 02 Aug 2019 07:59:32 GMT

Hi Xavier,

If the bootloader starts at 0x72000, then the linker settings are correct.

We do not recommend using nRFGO Studio as it is deprecated for the nRF52 Series, use the nRF Programmer app in nRF Connect for Desktop or the latest version of the nRF Command Line Tools instead.

When debugging an application with the bootloader present you need to generate the bootloader settings page that contains the CRC of the application. This is done with pc-nrfutil, see https://github.com/NordicSemiconductor/pc-nrfutil#settings.

So my advice would be to add a build step in your IDE calls nrfutil and generates the settings.hex file and then flashes this using nrfjprog.

Best regards

Bjørn