Have to run DFU OTA twice

RE: Have to run DFU OTA twice

Hung Bui — Fri, 05 Jan 2018 16:06:31 GMT

Please try to update with just the bootloader + softdevice first. No merging or manually write bootloader setting.

When you update did you update a different application or same application ? Please try to test using SDK example first. I have a blog here that you may want to follow.

RE: Have to run DFU OTA twice

Chris — Fri, 05 Jan 2018 16:05:25 GMT

another datapoint: sending the device back to bootloader again via sd_power_gpregret_set(0, BOOTLOADER_DFU_START); and letting it timeout actually updates the app even after the first OTA. But that's not a solution, I think...

RE: Have to run DFU OTA twice

Chris — Fri, 05 Jan 2018 15:43:42 GMT

I did another run, to show the output after 2nd OTA as well:

Initial flash

Family:               nRF52
CRC:                  0xB591D895
Settings Version:     0x00000001 (1)
App Version:          0x00000003 (3)
Bootloader Version:   0x00000002 (2)
Bank Layout:          0x00000000
Current Bank:         0x00000000
Application Size:     0x00015F34 (89908 bytes)
Application CRC:      0x05475C39
Bank0 Bank Code:      0x00000001

After 1st OTA

Family:               nRF52
CRC:                  0xCC460A3F
Settings Version:     0x00000001 (1)
App Version:          0x00000003 (3)
Bootloader Version:   0x00000002 (2)
Bank Layout:          0x00000000
Current Bank:         0x00000001
Application Size:     0x00015F34 (89908 bytes)
Application CRC:      0x05475C39
Bank0 Bank Code:      0x00000000

After 2nd OTA

Family:               nRF52
CRC:                  0xD32C0C63
Settings Version:     0x00000001 (1)
App Version:          0x00000003 (3)
Bootloader Version:   0x00000002 (2)
Bank Layout:          0x00000000
Current Bank:         0x00000001
Application Size:     0x00015F34 (89908 bytes)
Application CRC:      0x704102E6 **<-- now the CRC changed**
Bank0 Bank Code:      0x00000000

RE: Have to run DFU OTA twice

Chris — Fri, 05 Jan 2018 15:31:59 GMT

My testing is set up as follows:

flash the initial bootloader + sd + app + bl settings via nrfjprog
generate a package (debug) with only the app via nrfutil pkg generate --application-version 3 --application app.hex --hw-version 52 --sd-req 0x9D --debug-mode --key-file private.pem package.zip

And here's the nrfutil settings display output:

After initial flash

Family:               nRF52
CRC:                  0x9600BC1B
Settings Version:     0x00000001 (1)
App Version:          0x00000003 (3)
Bootloader Version:   0x00000002 (2)
Bank Layout:          0x00000000
Current Bank:         0x00000000
Application Size:     0x00015F34 (89908 bytes)
Application CRC:      0x42280D65
Bank0 Bank Code:      0x00000001

** After OTA dfu (secure ble w/o bonding) **

Bootloader DFU Settings:
File:                 temp.hex
Family:               nRF52
CRC:                  0x40FB9CB2
Settings Version:     0x00000001 (1)
App Version:          0x00000003 (3)
Bootloader Version:   0x00000002 (2)
Bank Layout:          0x00000000
Current Bank:         0x00000001
Application Size:     0x00015F34 (89908 bytes)
Application CRC:      0x42280D65
Bank0 Bank Code:      0x00000000

it looks like the bank was switched, but the application is still the same, right?

Thanks for the hint about logging!

RE: Have to run DFU OTA twice

Hung Bui — Fri, 05 Jan 2018 15:20:47 GMT

What did you use to update the firmware ? How did you update the initial application firmware ? Should it work on the initial OTA DFU ? Have you tried to update SDK examples instead of your app ?

If you want RTT logging for both application and bootloader you can have a look here.

RE: Have to run DFU OTA twice

Chris — Thu, 04 Jan 2018 11:09:57 GMT

SDK 14.1 and the softdevice is the same :(

I use Ozone, but as the bootloader is a different image file (it has to be, right?) I can either debug the bootloader or the app

RE: Have to run DFU OTA twice

shibshab — Thu, 04 Jan 2018 11:02:16 GMT

You should try Ozone. Its a free cross platform debugging tool from Segger. It will allow you to set breakpoints, inspect variables etc. like any IDE.

Also: What SDK version are you on? If you are on 14.0.0 then there is a known bug with doing SoftDevice updates where the new SoftDevice does not have the same size as the old one.