This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52832 sdk 13.0 Bootloader example not running

Hi,

I'm using the example dfu/bootloader_secure_ble for NRF52832 (PCA10040 board) in nRF SDK 13.0.0 version and on my mobile the "nRF Connect" application.

If I use Keil uVision to compile the bootloader I can see and connect to it before perform a DFU operation.

If I use armgcc (makefile command line) with the same source files (as perform as the given example) I see the target by doing "scan" on my mobile but I can't connect to it.

What is the difference at the compilation between the 2 tools? My problem is the generate executable.

Best regards, Romain

Parents
  • There are 2 problems:

    • first use the GCC toolchain version 4.9 2015q3 instead of 7 2017-q4-major (if someone knows this reason please to explain me it)

    • in the file {NRF52 SDK 13.0.0}/libraries/bootloader/ble_dfu/nrf_ble_dfu.c in the function advertising_stop(): replace "m_flags |= DFU_BLE_FLAG_IS_ADVERTISING;" by "m_flags &= ~DFU_BLE_FLAG_IS_ADVERTISING;"

Reply
  • There are 2 problems:

    • first use the GCC toolchain version 4.9 2015q3 instead of 7 2017-q4-major (if someone knows this reason please to explain me it)

    • in the file {NRF52 SDK 13.0.0}/libraries/bootloader/ble_dfu/nrf_ble_dfu.c in the function advertising_stop(): replace "m_flags |= DFU_BLE_FLAG_IS_ADVERTISING;" by "m_flags &= ~DFU_BLE_FLAG_IS_ADVERTISING;"

Children
No Data
Related