Problem with bootloader-mode after DFU procedure

RE: Problem with bootloader-mode after DFU procedure

bjorn-spockeli — Wed, 19 Apr 2017 09:36:26 GMT

RE: Problem with bootloader-mode after DFU procedure

Ray Breslin — Thu, 13 Apr 2017 13:12:19 GMT

Here is also the output of my flashing procedure:

Part 1 (eraseall)

make VERBOSE=1 erase 
nrfjprog --eraseall -f nrf52
Erasing code and UICR flash areas.
Applying system reset.

Part2 (flashing softdevice)

make VERBOSE=1 flash_softdevice 
Flashing: s132_nrf52_3.0.0_softdevice.hex
nrfjprog --program ../../../../../../components/softdevice/s132/hex/s132_nrf52_3.0.0_softdevice.hex -f nrf52 --sectorerase 
Parsing hex file.
Erasing page at address 0x0.
Erasing page at address 0x1000.
Erasing page at address 0x2000.
Erasing page at address 0x3000.
Erasing page at address 0x4000.
...
Erasing page at address 0x1B000.
Erasing page at address 0x1C000.
Erasing page at address 0x1D000.
Erasing page at address 0x1E000.
Applying system reset.
Checking that the area to write is not protected.
Programing device.
nrfjprog --reset -f nrf52
Applying system reset.
Run.

Part 3 (flashing bootloader_secure-example)

make VERBOSE=1 flash 
Flashing: _build/secure_dfu.hex
nrfjprog --program _build/secure_dfu.hex -f nrf52 --sectorerase
Parsing hex file.
Erasing page at address 0x78000.
Erasing page at address 0x79000.
Erasing page at address 0x7A000.
Erasing page at address 0x7B000.
Erasing page at address 0x7C000.
Erasing page at address 0x7D000.
Applying system reset.
WARNING: A UICR write operation has been requested but UICR has not been
WARNING: erased. Please verify that the result is correct.
Checking that the area to write is not protected.
Programing device.
nrfjprog --reset -f nrf52
Applying system reset.
Run.

Part 4 (DFU through nRF Toolbox-app)

Now I can discover a bt-device DfuTarg within the nRF Connect-app and LED1+LED3 on the nRF52832 DK are lighted up. After selecting the generated pkg-file for the buttonless_dfu-example (see initial post) and the device DfuTarg within the nRF Toolbox-app, I can start the dfu-procedure. When I press 'Upload' the nRF52832 DK is showing a connection state, with LED1 going off while LED2 goes on. The upload-progress gets shown in the app and finally I get the message 'Application has been transferred successfully.', which is resulting in a reset and them immediatly I am back in the bootloader-mode.

Maybe someone could verify this behaviour with the given files in my initial post!?

[Edit:] Apparently the problem wasnt the dfu-procedure itself, but some issue within both the bootloader_secure-example and the ble_dfu_send_hex-example regarding the need of doing a hard off-/on-switching for the nRF52832 DK in order to get to the application after completing the dfu-procedure! Isnt it possible to integrate the same kind of 'system-restart' automatically within the code?

[Edit2:] Now I also added a watchdog-timeout to the bootloader_secure-example (used this tutorial) which gets triggered after 30s of idle-time, but unfortunately this timeout only triggers a soft-reset which isnt enough to get to the application again...

RE: Problem with bootloader-mode after DFU procedure

Ray Breslin — Thu, 13 Apr 2017 12:11:25 GMT

Now only the problems 3.1 (bootloader being stuck - not starting the application), 3.2 (REMOTE DFU DATA SIZE EXCEEDS LIMIT-error) and 3.3 (debugging bootloader_secure-example) remain, where I would realy appreciate some help...

[Edit:] Attached all of my used files in the initial post for further investigations!

RE: Problem with bootloader-mode after DFU procedure

Ray Breslin — Thu, 13 Apr 2017 12:05:55 GMT

After integrating the bug-fix for writing into the characteristic of the buttonless-dfu-service (see here), it is also possible to request a restart in bootloader-mode which results in the following messages:

...
APP:INFO:Device is entering bootloader mode!
:INFO:Erasing old settings at: 0x0007f000
:INFO:Erasing: 0x0007f000, num: 1
:INFO:Writing 0x00000057 words
:INFO:Writing settings...
:INFO:Obtained settings, enter dfu is 1

So I am assuming the buttonless-dfu-example works pretty much as expected, even though it needed some adjustments which should have long been integrated officially into the recent SDK-releases.

RE: Problem with bootloader-mode after DFU procedure

Ray Breslin — Wed, 12 Apr 2017 14:31:23 GMT

As for the problem in (2) I came across this topic here, which mentioned a potientially missing part in the MEMORY-block and also in the SECTIONS-block of the corresponding loader-file.

Now I am getting the following output for the buttonless_dfu-example:

:INFO:running nrf_dfu_settings_init
:INFO:!!!!!!!!!!!!!!! Resetting bootloader settings !!!!!!!!!!!
:INFO:Erasing old settings at: 0x0007f000
:INFO:Erasing: 0x0007f000, num: 1
:INFO:Writing 0x00000057 words
:INFO:Writing settings...
:INFO:running nrf_dfu_settings_init

When activating/deactivating notifications for the Nordic_Template-Device I am also seeing those messages:

APP:INFO:Indication for BLE_DFU is enabled
APP:INFO:Indication for BLE_DFU is disabled

Is that the expected behaviour!?

RE: Problem with bootloader-mode after DFU procedure

Ray Breslin — Wed, 12 Apr 2017 13:01:13 GMT

Just checked this topic here, but even after adjusting the application- and bootloader-version to 1 the nRF52832 DK is still stuck in bootloader-mode after a successfull dfu and multiple resets...