Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Question

I am trying to integrate buttonless DFU with FDS in ble_app_uart example from sdk 15.3.0. Merge hex was done properly which includes bootloader_settings.hex+bootloader.hex+softdevice.hex+application.hex and programmed using JLink prior to that i erased the chip using nrfjprog -f nrf52 -e command successfully. Then i resetted the board, application started and reaches ble_dfu_buttonless_async_svci_init() which gives NRF_ERROR_NO_MEM error. I went into debug mode and found uint32_t bootloader address was 0xFFFFFFFF. I checked UICR register value using JLink command -> mem8 0x10001014 4 which results 0xFFFFFFFF. The bootloader i programmed was debug version and i got the below prints. PRINT_START 00> app: Inside main 00> 00> app: In nrf_bootloader_init 00> 00> nrf_dfu_settings: Calling nrf_dfu_settings_init()... 00> 00> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend. 00> 00> nrf_dfu_settings: Using settings page. 00> 00> nrf_dfu_settings: Copying forbidden parts from backup page. 00> 00> nrf_dfu_settings: Old settings page detected. Upgrading info. 00> 00> nrf_dfu_settings: Writing settings... 00> 00> nrf_dfu_settings: Erasing old settings at: 0x0007F000 00> 00> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x0007F000, len=1 pages), queue usage: 0 00> 00> nrf_dfu_flash: Flash erase success: addr=0x0007F000, pending 0 00> 00> nrf_dfu_flash: nrf_fstorage_write(addr=0x0007F000, src=0x20009188, len=896 bytes), queue usage: 1 00> 00> nrf_dfu_flash: Flash write success: addr=0x0007F000, pending 0 00> 00> nrf_dfu_settings: Backing up settings page to address 0x7E000. 00> 00> nrf_dfu_settings: Writing settings... 00> 00> nrf_dfu_settings: Erasing old settings at: 0x0007E000 00> 00> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x0007E000, len=1 pages), queue usage: 1 00> 00> nrf_dfu_flash: Flash erase success: addr=0x0007E000, pending 0 00> 00> nrf_dfu_flash: nrf_fstorage_write(addr=0x0007E000, src=0x20009508, len=896 bytes), queue usage: 1 00> 00> nrf_dfu_flash: Flash write success: addr=0x0007E000, pending 0 00> 00> app: Enter nrf_bootloader_fw_activate 00> 00> app: No firmware to activate. 00> 00> nrf_dfu_validation: CRC check of app failed. Return 1 00> 00> app: App is valid 00> 00> nrf_dfu_settings: Backing up settings page to address 0x7E000. 00> 00> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping. 00> 00> app: Running nrf_bootloader_app_start with address: 0x00001000 00> 00> app: Disabling interrupts. NVIC->ICER[0]: 0x0 00> 00> app: Setting vector table to bootloader: 0x00072000 00> 00> app: Setting vector table to main app: 0x00026000 00> No bootloader found 00> app: Fatal error 00> PRINT_ENDS The application Linker script has FLASH_PH_START=0x0 FLASH_PH_SIZE=0x80000 RAM_PH_START=0x20000000 RAM_PH_SIZE=0x10000 FLASH_START=0x26000 FLASH_SIZE=0x53000 RAM_START= 0x200030E0 RAM_SIZE=0xCF20 I don't know why UICR has 0xFFFFFFFF value and i know that because this my application stucks in Fatal error. Why UICR is not programmed properly? I am attaching nrf52832_xxaa_s132.map( from pca10040_ble_debug\armgcc\build ), bootloader_settings.hex, bootloader.hex, application.hex and sd_app_boot.hex for reference. 74862.nrf52832_xxaa_s132.map 6567.bootloader_settings.hex 1667.nrf52832_xxaa_s132.hex 8524.sd_app_boot.hex 0513.ble_app_uart_pca10040_s132.hex

Yogeshwaran · Accepted Answer

NRF_DFU_APP_DATA_AREA_SIZE 204800 which is 50 pages of FDS and i enabled 
 
 NRF_DFU_FORCE_DUAL_BANK_APP_UPDATES by setting to 1 now the issue got resolved and DFU successfully updating application and running properly after update. If i change the NRF_DFU_APP_DATA_AREA_SIZE to 80 pages then throwing error after update as '11' at fds_init() which denotes NO_PAGES. what is the reason? One more issue is if i call sd_nvic_SystemReset() gives Fatal error in loop(). This function will get called after device receives cmd from ble_client( nRF_Connect app ) so can you tell how to reset the device properly to go into DFU.

Einar Thorsrud · Answer

Hi, 
 Ah, yes. I did not spot that. You are right. Please note that if you want a BLE service for enabling DFU that is allready implemented for you in the SDK, with the DFU service. There you can also see how DFU mode is triggered by writing to GPREGRET and resetting using ble_dfu_buttonless_bootloader_start_finalize() implemented like this in ble_dfu.c (for your reference): 
 uint32_t ble_dfu_buttonless_bootloader_start_finalize(void)
{
 uint32_t err_code;

 NRF_LOG_DEBUG("In ble_dfu_buttonless_bootloader_start_finalize
");

 err_code = sd_power_gpregret_clr(0, 0xffffffff);
 VERIFY_SUCCESS(err_code);

 err_code = sd_power_gpregret_set(0, BOOTLOADER_DFU_START);
 VERIFY_SUCCESS(err_code);

 // Indicate that the Secure DFU bootloader will be entered
 m_dfu.evt_handler(BLE_DFU_EVT_BOOTLOADER_ENTER);

 // Signal that DFU mode is to be enter to the power management module
 nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_DFU);

 return NRF_SUCCESS;
}

Nrf52832 ble_app_uart DFU No bootloader found(NRF_ERROR_NO_MEM) | SDK 15.3.0 | Soft device S132 6.1.1

Top Replies