NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

[Jimmy]

We follow the OTA guide:  Add DFU support to your application 

Add below code in main.c:

    printk("build time: %s %s Version: %s\n", __DATE__, __TIME__, CONFIG_MCUBOOT_IMAGE_VERSION);

    os_mgmt_register_group();

    img_mgmt_register_group();

    smp_bt_register();

Our prj.conf:

CONFIG_MCUMGR=y

CONFIG_MCUMGR_CMD_IMG_MGMT=y

CONFIG_MCUMGR_CMD_OS_MGMT=y

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_MCUMGR_SMP_BT=y

CONFIG_MCUMGR_SMP_BT_AUTHEN=n

CONFIG_IMG_ERASE_PROGRESSIVELY=y

CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="child_image/mcuboot/mcuboot_private.pem"

CONFIG_MCUBOOT_IMAGE_VERSION="0.0.0+0"

......

Mcuboot prj.conf:

CONFIG_SIZE_OPTIMIZATIONS=y

CONFIG_HW_STACK_PROTECTION=n

CONFIG_SYSTEM_CLOCK_NO_WAIT=y

CONFIG_PM=n

CONFIG_MAIN_STACK_SIZE=10240

CONFIG_BOOT_BOOTSTRAP=n

CONFIG_BOOT_ENCRYPT_RSA=n

CONFIG_BOOT_SIGNATURE_TYPE_RSA=y

CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

CONFIG_BOOT_SIGNATURE_KEY_FILE="mcuboot_private.pem"

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_FLASH=y

CONFIG_BOOT_ERASE_PROGRESSIVELY=y

CONFIG_SOC_FLASH_NRF_EMULATE_ONE_BYTE_WRITE_ACCESS=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_LOG=y

CONFIG_LOG_DEFAULT_LEVEL=2

CONFIG_LOG_MAX_LEVEL=3

CONFIG_LOG_PRINTK=y

CONFIG_LOG_MODE_IMMEDIATE=y

CONFIG_LOG_BACKEND_SHOW_COLOR=n

CONFIG_LOG_BACKEND_FORMAT_TIMESTAMP=n

Build the project, then flash to device, the rtt log:

Then we change CONFIG_MCUBOOT_IMAGE_VERSION="0.0.1+0", rebuild project, and use nRF Connect update the app_update.bin to device, everything is ok, but after device reboot, the rtt log is the same with old one:

The nRF Connect log:

The mcuboot exec the old firmware after upload app_update.bin success, how can this happen? What i missed?

[Hung Bui]

Hi Jimmy, 

Have you tried to change the content of the application and rebuild ? Can be just as little as the text in the log. As far as I know if the hash of the image binary matches with the current image(s) on the chip it will reject the image upload. 

[Jimmy]

I have confirmed the main.c is changed before rebuild, and i can see the hash is diffrent from Device Manage app:

[Jimmy]

I have try both your bin file and build with source code. It stuck when i clieck start uploard:

[Hung Bui]

Hi Jimmy, 
Could you try: 
Flash merged.hex 
Use the phone to DFU update app_update3.bin  ?

How did you get it to advertise Zephyr heartrate 3 ? 

[Jimmy]

I tryed two way:

1. As you said, flash merged.hex, update app_update3.bin;

2. Build the source code you provide(Base on ncs2.0, 52833dk), flash, change ble name, rebuild, update;

Both two method are stuck when i clieck start upload buttion in Device Manage app.

[Hung Bui]

It's pretty strange that it didn't work for you. 

I noticed that you have the device advertised as "Zephyr Heartrate 3"  . Was that because you modified the BLE name and flash it manually ? 

Could you try to do DFU with nRF Connect and check the log ? 

Also if you build it for the nRF52833 DK, please check the UART log on the board as well (The UART log on the merged.hex file won't work because I built it for nRF52832 DK)

[Jimmy]

I have remove some code in my main.c(such as disable uart, disable rtt), make the flash usage at lower than 94%(before is 97%), ota ok now.

I don't know why flash used 97% not work, it's pretty strange.

[Hung Bui]

Hi Jimmy, 

I suspect that it doesn't fit into the secondary slot for some reason. Maybe you can check the log from MCUBoot  ?