Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cannot debug ble_app_buttonless_dfu with bootloader existing in SDK 15.3.0

Hi I checked the relevant topics in the forum but none of them fixed my issue so I just create a new one here.

Basic info:

Hardware: nRF52 DK PCA10040

SDK: nRF5_SDK_15.3.0_59ac345(freshly downloaded)

SEGGER Embedded Studio 3.40

Issue:

1. I flashed sd_s132_bootloader_buttonless_with_setting_page_dfu_secure_ble_debug_without_bonds.hex file from \dfu\secure_dfu_test_images\ble\nrf52832 to the DK and it started to do advertising, which meant the whole firmware was flashed successfully.

2. I opened up the ble_app_buttonless_dfu project from \ble_peripheral\ble_app_buttonless_dfu\pca10040\s132\ses, Debug mode, and clicked Build and Debug. And I got "No bootloader was found" "ERROR 4 [NRF_ERROR_NO_MEM] at the ble_dfu_buttonless_async_svci_init() place, which indicated bootloader_addr == 0xFFFFFFFF

3. And I double checked the bootloader_addr with command "nrfjprog -f nrf52 --memrd 0x10001014" and verified it was 0xFFFFFFFF.

NB:I had the same issue with the way using default secure_bootloader hex and then merged with softdevice, bootloader setting and application, that's why I wanted to minimize the scope by only using the step 1 pre-compiled hex file assuming that this should work and write some valid data to bootloader_addr, but still didnt work. The whole SDK was freshly downloaded just in case I by any chance changed something but didnt realize it.

Can you check whether you can duplicate the same issue at your side and help me out how to fix it?

Thanks

/CJ

Related