Why No firmware to activate?

[MichaelKilleen]

Hello

Using PCA10040 dev board,

Building with SDK 16, & S112 - using ses

Running  ..\examples\dfu\secure_bootloader\pca10040_uart_debug

Using nrfutil to download my package via serial port - all looks good  ( package is just app hex file)

via RTT see following from dev board

<info> app: Inside main

<warning> nrf_dfu_settings: Resetting bootloader settings since neither the settings page nor the backup are valid (CRC error).

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> app: No firmware to activate.

<info> app: Boot validation failed. No valid app to boot.

<info> nrf_bootloader_wdt: WDT is not enabled

<info> app: Entering DFU mode.

<info> nrf_dfu_serial_uart: Allocated buffer 200016F0

...

<info> nrf_dfu_serial_uart: Allocated buffer 20001774

<info> nrf_dfu_validation: Signature required. Checking signature.

<info> nrf_dfu_validation: Calculating hash (len: 65)

<info> nrf_dfu_validation: Verify signature

<info> nrf_dfu_validation: Image verified

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> nrf_dfu_serial_uart: Allocated buffer 20001774

....

<info> nrf_dfu_serial_uart: Allocated buffer 20001774

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.<info> app: Inside main

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> app: Inside main

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

<info> app: No firmware to activate.

<warning> nrf_dfu_settings: No additional data erased

<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.

All was going so well... why do I get No Firmware to activate?

My app is modified version of "..\examples\peripheral\twi_scanner\pca10040"

My app runs ok on its own - via debugger or if flashed to board

What are the tricks to get to run with boot-loader?  dfu etc?

Thank you

Used:

nrfutil pkg generate --hw-version 52 --sd-req 0xCD --application-version-string 1.01.01 --application my_scanner_pca10040.hex --key-file private.pem my_scanner_pca10040.zip

nrfutil dfu serial -pkg my_scanner_pca10040.zip -p com13 -t 3

[Jørgen Holmefjord]

Hi,

pca10040_uart_debug can only be used with the test-images in examples\dfu\secure_dfu_test_images, as it uses the public key for Nordic's un-published private key. Please make sure you follow the instructions in the documentation closely, to generate keys, bootloader settings, DFU package, etc.

Best regards,
Jørgen

[Jørgen Holmefjord]

Have you made many changes to the bootloader? It seems that the log shows multiple resets, is that correct, or have you reset the board yourself?

What is the output from 'nrfutil dfu serial' command?

[MichaelKilleen]

boot loader has different keys, otherwise no difference, when program boot loader get restart messages (maybe some already captured in RTT viewer), nrfutil gets to 100% - Device programmed

So possibly messages/errors output not very clear. Going back to build my test app again, may be missed a trick or two in that project. Possibly related to MBR?

Thanks

[Jørgen Holmefjord]

MBR should only be used for updating bootloader, and jumping to bootloader on boot, so I do not think the problem is with that one. You may also try to rebuild the bootloader with a clean SDK in case the application-rebuild does not help.

[MichaelKilleen]

Thank you, moved to sample app with ble already included. Updated app with our test code. Building this worked and was also able to upgrade via dfu/boot loader. My previous app was based of sample code with ble support. Not sure what made this work