nRF52840 wouldn't reset automatically after DFU update

RE: nRF52840 wouldn't reset automatically after DFU update

Vidar Berg — Thu, 14 May 2020 12:19:02 GMT

It's hard to say what the problem is without being able to debug it. Have you had any success with enabling logs, and have you tried to place breakpoints inside the nrf_bootloader.c->dfu_enter_check() function?

RE: nRF52840 wouldn't reset automatically after DFU update

Aftab — Wed, 13 May 2020 13:52:40 GMT

Hello Vidar,

I have tried this but it's not working, the device does not reset by sending 0xC0 command. To demonstrate I have made a video, please have a look at that:

drive.google.com/.../view

Thanks.

RE: nRF52840 wouldn't reset automatically after DFU update

Vidar Berg — Wed, 06 May 2020 10:44:41 GMT

Notifications need to be enable before you can send command requests.

Debug logging over RTT is enabled in the debug project 'pca10056_s140_ble_debug'. The logs can be viewed with RTTViewer or RTTClient.

RE: nRF52840 wouldn't reset automatically after DFU update

Aftab — Tue, 05 May 2020 15:03:20 GMT

I have tried Abort to no success. The device remains in the DFU mode. See the attached picture.

I have also tried to debug the bootloader. For that I enabled the log by:

#define NRF_LOG_ENABLED 1

But I get compile errors like:

Building ‘secure_bootloader_ble_s140_pca10056’ from solution ‘secure_bootloader_ble_s140_pca10056’ in configuration ‘Release’
  Compiling ‘nrf_log_str_formatter.c’
  Compiling ‘nrf_log_frontend.c’
  Compiling ‘app_error_weak.c’
  Compiling ‘app_scheduler.c’
  Compiling ‘crc32.c’
  Compiling ‘mem_manager.c’
  Compiling ‘nrf_atfifo.c’
  Compiling ‘nrf_atomic.c’
  Compiling ‘nrf_balloc.c’
  Compiling ‘nrf_fprintf.c’
  Compiling ‘nrf_fprintf_format.c’
  Compiling ‘nrf_fstorage.c’
  Compiling ‘nrf_fstorage_nvmc.c’
  Compiling ‘nrf_fstorage_sd.c’
  Compiling ‘nrf_memobj.c’
  Compiling ‘nrf_queue.c’
  Compiling ‘nrf_ringbuf.c’
  Compiling ‘nrf_strerror.c’
  Compiling ‘nrf_section_iter.c’
  Compiling ‘cc310_bl_backend_ecc.c’
  Compiling ‘cc310_bl_backend_ecdsa.c’
  Compiling ‘cc310_bl_backend_hash.c’
  Compiling ‘cc310_bl_backend_init.c’
  Compiling ‘cc310_bl_backend_shared.c’
  Compiling ‘boards.c’
  Compiling ‘nrf_sdh.c’
  Compiling ‘nrf_sdh_ble.c’
  Compiling ‘nrf_sdh_soc.c’
  Compiling ‘nrf_nvmc.c’
  Compiling ‘nrfx_atomic.c’
  Compiling ‘nrf_crypto_ecc.c’
  Compiling ‘nrf_crypto_ecdsa.c’
  Compiling ‘nrf_crypto_hash.c’
  Compiling ‘nrf_crypto_init.c’
  Compiling ‘nrf_crypto_shared.c’
  Compiling ‘main.c’
  Compiling ‘nrf_dfu_svci.c’
  Compiling ‘nrf_dfu_svci_handler.c’
  Compiling ‘nrf_bootloader.c’
  Compiling ‘nrf_bootloader_app_start.c’
  Compiling ‘nrf_bootloader_app_start_final.c’
  Compiling ‘nrf_bootloader_dfu_timers.c’
  Compiling ‘nrf_bootloader_fw_activation.c’
  Compiling ‘nrf_bootloader_info.c’
  Compiling ‘nrf_bootloader_wdt.c’
  Compiling ‘nrf_dfu.c’
  Compiling ‘nrf_dfu_ble.c’
  Compiling ‘nrf_dfu_flash.c’
  Compiling ‘nrf_dfu_mbr.c’
  Compiling ‘nrf_dfu_handling_error.c’
  Compiling ‘nrf_dfu_req_handler.c’
  Compiling ‘nrf_dfu_settings.c’
  Compiling ‘nrf_dfu_settings_svci.c’
  Compiling ‘nrf_dfu_transport.c’
  Compiling ‘nrf_dfu_utils.c’
  Compiling ‘nrf_dfu_validation.c’
  Compiling ‘nrf_dfu_ver_validation.c’
  Compiling ‘oberon_backend_chacha_poly_aead.c’
  Compiling ‘oberon_backend_ecc.c’
  Compiling ‘oberon_backend_ecdh.c’
  Compiling ‘oberon_backend_ecdsa.c’
  Compiling ‘oberon_backend_eddsa.c’
  Compiling ‘oberon_backend_hash.c’
  Compiling ‘oberon_backend_hmac.c’
  Linking secure_bootloader_ble_s140_pca10056.elf
    .text is too large to fit in FLASH memory segment
    .crypto_data is too large to fit in FLASH memory segment
    .dfu_trans is too large to fit in FLASH memory segment
    .svc_data is too large to fit in FLASH memory segment
    .log_const_data is too large to fit in FLASH memory segment
    .nrf_balloc is too large to fit in FLASH memory segment
    .sdh_ble_observers is too large to fit in FLASH memory segment
    .sdh_state_observers is too large to fit in FLASH memory segment
    .sdh_stack_observers is too large to fit in FLASH memory segment
    .sdh_req_observers is too large to fit in FLASH memory segment
    .sdh_soc_observers is too large to fit in FLASH memory segment
    .fs_data is too large to fit in FLASH memory segment
    .rodata is too large to fit in FLASH memory segment
    .data is too large to fit in FLASH memory segment
    Output/secure_bootloader_ble_s140_pca10056 Release/Obj/main.o: in function `main':
    undefined reference to `nrf_log_default_backends_init'
Build failed

It seems like I have to change the memory areas for bootloader but I'm not sure which areas and what changes to make. This project uses softdevice as well.

RE: nRF52840 wouldn't reset automatically after DFU update

Vidar Berg — Tue, 05 May 2020 08:36:06 GMT

Yes, you can send the Abort request to trigger a reset (ie write 0xC to control point)

RE: nRF52840 wouldn't reset automatically after DFU update

Aftab — Tue, 05 May 2020 07:33:18 GMT

Thank you Vidar for the reply.

Is there any way to exist the DFU mode by accessing GATT characteristics of DfuTarg? There "Secure DFU Packet" and "Secure DFU Control Point". May be we send some packet with reset command?

RE: nRF52840 wouldn't reset automatically after DFU update

Vidar Berg — Mon, 04 May 2020 13:39:47 GMT

Hello,

It sounds like the bootloader falls back to DFU mode after the update. Are you able to debug the bootloader when this happens? If so, please try to debug the nrf_bootloader.c->dfu_enter_check() function to see if any of these checks return true. RESETREAS and GPREGRET are both cleared through power on reset so maybe the explanation is that one of these registers are not properly cleared after the update was completed.

Regards,

Vidar