After DFU Application at DFU_BANK_0_REGION_START is not valid

[Marco]

Hi,

I have a device with nRF52832 and firmware is composed of Bootloader (BL), softdevice (SD) S132 v2.0.0, application and I am using SDK 11.0.

I have created different firmware updates (BL, SD, App, BL+SD, etc.) in ZIP format (using nrfutil v2.2.0) and when I try to perform a DFU over BLE, I always end up with DFU_BANK_0_REGION_START (Addr: 0x0001C000) with all its content reset to 0xFFFFFFFF.

I use the application setting provided by Nordic support for nRF52 and I merge it together with the other HEX included in the ZIP files:

:020000040007F3    
:10F000000100000000000000FE000000FFFFFFFF05
:00000001FF

I have tried using the ZIP files provided in the SDK 11.0 in the example projects related to DFU usage, but even those fail. With the only difference that with those example ZIP files, actually the files get transferred (using Android app nRF Connect).

This is a sequence of events happening in my system when I try to perform a DFU (I have printed some log messages):

ble_evt_dispatch(): p_ble_evt->header.evt_id 16         -> BLE_GAP_EVT_CONNECTED
ble_evt_dispatch(): p_ble_evt->header.evt_id 18         -> BLE_GAP_EVT_CONN_PARAM_UPDATE
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE     
ble_evt_dispatch(): p_ble_evt->header.evt_id 81         -> BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE
bootloader_dfu_update_process() update_status = 4       -> DFU_BANK_0_ERASED
ble_evt_dispatch(): p_ble_evt->header.evt_id 1          -> BLE_EVT_TX_COMPLETE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 81         -> BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 80         -> BLE_GATTS_EVT_WRITE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 81         -> BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
ble_evt_dispatch(): p_ble_evt->header.evt_id 1          -> BLE_EVT_TX_COMPLETE
ble_evt_dispatch(): p_ble_evt->header.evt_id 1          -> BLE_EVT_TX_COMPLETE 
ble_evt_dispatch(): p_ble_evt->header.evt_id 81         -> BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
bootloader_dfu_update_process() update_status = 6       -> DFU_RESET
bootloader_app_is_valid(): EMPTY_FLASH_MASK

Resetting
[After restarting] 

bootloader_app_is_valid(): Application at DFU_BANK_0_REGION_START is not valid!

Do you have any suggestions on how to make it work. I am pretty sure it is just a matter of creating the proper ZIP file and/or incompatibility of SDK/DFU Manager/Android App.

Thank you for the support.

Marco

[bjorn-spockeli]

Hi Marco,

If you're using the bootloader from SDK v11.0.0, i.e. Legacy Bootloader, then you have to use nrfutil v0.5.2, which can be downloaded here.

If you want to flash a combined SoftDevice, Bootloader and Application hex file created with mergehex, where the device jumps to the application without having to perform a OTA update, you have to set the BANK_VALID_APP flag in bootloader_settings.c, i.e. change the line

uint8_t  m_boot_settings[CODE_PAGE_SIZE]    __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used));   

to the following

uint8_t  m_boot_settings[CODE_PAGE_SIZE]    __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used)) = {BANK_VALID_APP};

Please note that this modification must be removed if you plan to update the bootloader.

-Bjørn

[Marco]

It seems I managed to make big progresses. Now the DFU process can transfer the whole image (application only) to the nRF52. However I get "[DFU] Remote DFU error: REMOTE DFU INVALID CRC ERROR" on nRFConnect app. I have printed a a log message:

dfu_init_postvalidate(): received_crc 0x0002, image_crc 0xCCAD, image_len 63748

I have checked other posts related to CRC error, but with no luck. I tried to upload another image (application only) and the received_crc is always equal to 0x0002. I have also tried the DFU with the BL+SD and the loge message reports 0x0002 again as received_crc:

dfu_init_postvalidate(): received_crc 0x0002, image_crc 0x55C9, image_len 132076

Any ideas about what it could generate this issue?