• State Suggested Answer
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 2684 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 129440
Options
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

Romain

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
  • 0

    Hi,

    I can't use nRF Sniffer.

    My problem is that when the application received on ble_dfu service the case BLE_DFU_EVT_ENTERING_BOOTLOADER I disable current connection (sd_ble_gap_disconnect then ble_conn_params_stop then pm_peers_delete) then the target enters in bootloader mode. But in bootloader mode the connection failed with the mobile which tries to send new application and the target re-enters in old application.

Reply
  • 0

    Hi,

    I can't use nRF Sniffer.

    My problem is that when the application received on ble_dfu service the case BLE_DFU_EVT_ENTERING_BOOTLOADER I disable current connection (sd_ble_gap_disconnect then ble_conn_params_stop then pm_peers_delete) then the target enters in bootloader mode. But in bootloader mode the connection failed with the mobile which tries to send new application and the target re-enters in old application.

Children
No Data
Related