Bootloader Resets Once Right After Program

RE: Bootloader Resets Once Right After Program

Matt22 — Mon, 18 Feb 2019 17:57:55 GMT

I traced down the double reset after a flash program issue. It is actually a deliberate reset by the main app initialization code, due to using the NRF I/O pins as GPIO and not NRF.

In system_nrf52840.c SystemInit(), line 153 checks to see if the pins are configured as GPIO. If so, it checks, then clears bit 0 of the NFCPINS register (addr 0x1000120c). When a full chip erase is performed, this bit is set by default. Due to this register being a UICR, any modifications are only implemented after a reset. So, this routine forces a chip reset at line 161.

Since the UICR is non-volatile flash, no subsequent chip power-ups or resets go through the deliberate reset.

RE: Bootloader Resets Once Right After Program

Hakon — Fri, 15 Feb 2019 12:16:09 GMT

devzone.nordicsemi.com/.../ble_5F00_app_5F00_hrs_5F00_pca10056_5F00_s140.hex devzone.nordicsemi.com/.../secure_5F00_bootloader_5F00_ble_5F00_s140_5F00_pca10056_5F00_debug.hex devzone.nordicsemi.com/.../settings.hex

Try flashing these instead and see if you get the same result.

RE: Bootloader Resets Once Right After Program

Matt22 — Wed, 13 Feb 2019 04:28:08 GMT

I get the same results with the SDK example, secure_bootloader_ble_s140_pca10056_debug, unmodified. See the two <info> app: Inside main below. It appears to be trying to load the application but then fails, resets, and then successfully loads it.

<info> app: Inside main
<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> nrf_dfu_settings: Settings OK
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<debug> app: Enter nrf_dfu_app_is_valid
<debug> app: Return true. App was valid
<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.<info> app: Inside main
<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> nrf_dfu_settings: Settings OK
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<debug> app: Enter nrf_dfu_app_is_valid
<debug> app: Return true. App was valid
<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
<debug> app: Running nrf_bootloader_app_start with address: 0x00001000
<debug> app: Disabling interrupts. NVIC->ICER[0]: 0x0
<debug> app: running irq table set
<debug> app: After running irq table set

RE: Bootloader Resets Once Right After Program

Hakon — Mon, 11 Feb 2019 10:26:22 GMT

I suggest you enable nrf_log for the bootloader, and try to find the reason for the reset by logging, if you are not already doing that. Nrf_log can be enabled in sdk_config.h.

RE: Bootloader Resets Once Right After Program

Matt22 — Thu, 07 Feb 2019 14:56:10 GMT

There are plenty of tools to program them, nrfjprog, nrfgo studio, or just in Segger Embedded Studio as additional load files when you debug. The application can be reloaded without changing the bootloader and softdevice but if you want to go this route you probably should regenerate and program the settings.hex as it contains a CRC of the application which would change.

RE: Bootloader Resets Once Right After Program

Matt22 — Thu, 07 Feb 2019 14:52:34 GMT

Hi, I have tried version 4 and 5 with the same result. These are the ones that create the backup settings and I have verified that the address are FF000 and FE000 for the 2 settings.

RE: Bootloader Resets Once Right After Program

Hakon — Thu, 07 Feb 2019 09:35:43 GMT

Hello, what version of nrfutil are you using?

RE: Bootloader Resets Once Right After Program

AbhinavEV — Thu, 07 Feb 2019 07:06:12 GMT

Hi Matt,

Could you please explain me how to program bootloader.hex, application.hex, settings.hex and softdevice simultaneously using JTAG. Are you able to update the application.hex file again and again without disturbing bootloader.hex.

I am trying to develop an application and I am stuck here.

Thanks in advance.