Dual bank update failing until first successful DFU

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Wed, 21 Jun 2023 13:11:24 GMT

Hi,

Please create a new support case for your own issue and upload the log from the bootloader with debug version.

-Amanda H.

RE: Dual bank update failing until first successful DFU

mort809 — Wed, 21 Jun 2023 03:58:29 GMT

Did you ever find a solution to this issue? I have just begun to notice the same thing.

I am using the iOS nRF Connect application.

I use the nRF Connect desktop programmer application to flash a hex file that contains the softdevice, bootloader, bootloader settings, and initial application hex.
I start the DFU process to upgrade to a later version of the application.
I cancel the update and it bricks the device. No bootloader or application is advertising, and power cycling doesn't bring it back.

If I allow the first update to succeed, and then start and cancel another update, it will correctly revert to the firmware version as I would expect.

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Wed, 05 Apr 2023 13:25:46 GMT

I would suggest you refer to this Easy way to merge bootloader and application RTT output to get the bootloader and application log together.

-Amanda H.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Tue, 04 Apr 2023 20:21:54 GMT

I don't see a log from the app after the device enters DFU mode. The last line I see is this:

00> [00:03:21.866,607] <info> app_dfu: Power management wants to reset to DFU mode.
00> 
00> [00:03:21.866,607] <info> app_dfu: Power management allowed to reset to DFU mode.
00>

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Mon, 03 Apr 2023 15:21:35 GMT

Hi,

[quote user="jdtoby_pa"]However the app is still logging to RTT. [/quote]

What is the log from the app?

-Amanda H.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Fri, 31 Mar 2023 18:39:58 GMT

I'm trying to get UART logging working. I set NRF_LOG_BACKEND_UART_ENABLED to 1, the buffer size to 64, the proper Tx pin, and the baudrate to 115200. I also set NRF_LOG_BACKEND_RTT_ENABLED to 0 for both the app and bootloader. However the app is still logging to RTT. When I print out NRF_LOG_BACKEND_UART_ENABLED, it says 0, and when I print out NRF_LOG_BACKEND_RTT_ENABLED, it says 1. Any advice here?

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Wed, 29 Mar 2023 15:50:58 GMT

Seems correct to me.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Tue, 28 Mar 2023 21:29:35 GMT

Ok thanks, I'll try having the app log to UART and the bootloader log to RTT. In the meantime, do you think there's a way to build the initial hex file that contains the SD, bootloader, settings, and app in such a way that this error never happens? Here's the command that builds that file:

# Build app and create full hex version (app + sd + bootloader)
build_full: build_app
	@echo Generating bootloader + SoftDevice
	make $(MODEL) TARGET_CONFIG=$(TARGET_CONFIG) -C ./bootloader
	mkdir -p $(OUTPUT_DIRECTORY)
	$(NRFUTIL) settings generate --family $(TARGET_FAMILY) \
  --application-version $(APP_VERSION_INT) \
  --bootloader-version $(BL_VERSION) \
  --bl-settings-version 1 $(OUTPUT_DIRECTORY)/settings.hex
	@echo Merging settings with bootloader
	mergehex -m $(OUTPUT_DIRECTORY)/settings.hex $(BL_DIRECTORY)/$(BL_HEX) \
  -o $(OUTPUT_DIRECTORY)/$(BL_HEX)
	@echo Merging with app
	mkdir -p $(DFU_DIRECTORY)
	mergehex -m $(OUTPUT_DIRECTORY)/$(BL_HEX) $(OUTPUT_DIRECTORY)/$(PROJECT_NAME).hex -o \
	$(DFU_DIRECTORY)/$(FULL_HEX)

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Tue, 28 Mar 2023 16:07:03 GMT

Hi,

[quote user="jdtoby_pa"]PC: 0x000262DE[/quote]

Seems the device has gotten stuck in the application since the app started at 0x26000 in s132v6.1.1.

What is the application? Is it an nRF5 example or your application? I would suggest getting the log from the app to debug. It can be tricky to get RTT logging working with both a bootloader and app running on the same device: https://devzone.nordicsemi.com/f/nordic-q-a/30310/easy-way-to-merge-bootloader-and-application-rtt-output. I would suggest to enable UART logging in the app if that's an option.

-Amanda H.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Mon, 27 Mar 2023 18:16:53 GMT

Yes, I'm using s132 v6.1.1. Here is the command I'm using to build the DFU package:

# Build app and generate DFU zip
build_dfu: build_app
	@echo Generating DFU scriplean
	mkdir -p $(DFU_DIRECTORY)
	$(NRFUTIL) pkg generate --hw-version $(DFU_HW_ID) \
  --application-version $(APP_VERSION_INT) \
  --application $(OUTPUT_DIRECTORY)/$(PROJECT_NAME).hex \
  --sd-req $(SD_REQ) \
  --key-file $(KEY_DIRECTORY)/private.key \
  $(DFU_DIRECTORY)/$(DFU_ZIP)

SD_REQ is 0xB7. I believe all the other variables are just file/folder/version names specific to the project.

I got the device stuck again and read the registers, and this was the result. However, I didn't see any RTT outputs after entering into DFU mode this time:

R0: 0x00000004
R1: 0x00031E3C
R2: 0x00026000
R3: 0x000262DF
R4: 0x00001000
R5: 0x200080B4
R6: 0x2000A094
R7: 0x00000004
R8: 0x00000000
R9: 0x00000000
R10: 0x20000000
R11: 0x00000000
R12: 0x00000000
SP: 0x2000FFD0
LR: 0xFFFFFFF9
PC: 0x000262DE
xPSR: 0x21000003
MSP: 0x2000FFD0
PSP: 0x00000000

I reset the device by pulling the reset pin low, and then I was able to see the "Disabling interrupts" RTT printout. I then read the registers again after that:

R0: 0x00000004
R1: 0x00000000
R2: 0x00026000
R3: 0x000262DF
R4: 0x00001000
R5: 0x200080B4
R6: 0x2000A094
R7: 0x00000715
R8: 0x00000000
R9: 0x00000000
R10: 0x20000000
R11: 0x00000000
R12: 0x00000000
SP: 0x00000010
LR: 0x0003A703
PC: 0x000262DE
xPSR: 0x21000000
MSP: 0x00000010
PSP: 0x00000000

Thanks and hope this helps.

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Mon, 27 Mar 2023 16:56:04 GMT

Hi,

Are you using s132 v6.1.1?

What is the command you are using to generate the updated package? Please post the command.

Can you run "nrfjprog --readregs" when the device has gotten stuck in this state? I.e. after the "00> <debug> app: Disabling interrupts. NVIC->ICER[0]: 0x120000" line is printed. The Program Counter (PC) should tell us exactly where it hangs.

-Amanda H.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Fri, 24 Mar 2023 15:24:08 GMT

devzone.nordicsemi.com/.../dfu_5F00_failure_5F00_log.txtI've attached a file that contains the RTT viewer output while the DFU failure was occurring (i.e. DFU is aborted midway through, then gets stuck in bootloader mode). Is this what you're looking for?

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Fri, 24 Mar 2023 14:36:31 GMT

Connect with J-Link RTT view to get the log from the bootloader debug version.

-Amanda H.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Fri, 24 Mar 2023 14:19:09 GMT

I'm not sure where to find that, what would the file be named?

RE: Dual bank update failing until first successful DFU

Amanda Hsieh — Fri, 24 Mar 2023 14:05:22 GMT

Hi,

Is it possible to provide the log with the bootloader debug version for the issues? Thanks.

Regards,
Amanda H.

RE: Dual bank update failing until first successful DFU

jdtoby_pa — Thu, 23 Mar 2023 20:43:46 GMT

Mine are ~80KB when compiling in release mode and ~160KB when compiling in debug mode

RE: Dual bank update failing until first successful DFU

Shahin97 — Thu, 23 Mar 2023 15:13:10 GMT

Out of curiosity how big are your updates?, I have found that the nrf52832 flash size is too small for Dual bank without external flash for my needs.