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

nRF5_SDK_11 BLE DFU Bootloader - won't advertise

Ok - I'm trying to get my arms around this bootloader process.

I am using the nRF5_SDK_11.0.0_89a8197 SDK along with the PCA10040 develeopment kit. I also am using IAR tools.

Following the example for BLE DFU I did the following:

  1. Erased the device using nRFgo Studio - works.
  2. Programmed the SoftDevice using nRFgo Studio- C:/nRF5_SDK_11.0.0_89a8197/components/softdevice/s132/hex/s132_nrf52_2.0.0_softdevice.hex This woked as well.
  3. Programmed the BLE DFU Bootloader using nRFgo Studio. I built the IAR project supplied (C:\nRF5_SDK_11.0.0_89a8197\examples\dfu\bootloader\pca10040\dual_bank_ble_s132\iar) . It built fine. I was not sure how to program the bootloader using IAR so I used the nRFgo Studio tool to program the generated output file. It programmed fine.
  4. At this point I expected to see the device advertising the DFU service. It doesn't. LED1 is ON solid. LED3 is ON solid. There is not advertising going on.
  5. At this point I suspected that there was something wrong with my generated BLE DFU Bootloader file. So I decided to use the pre-canned that came with the SDK. When I tried to program the BLE DFU Bootloader using nRFgo Studio - it complains that the provided file contains data that is addressed to go in the SoftDevice area. The file used is: C:\nRF5_SDK_11.0.0_89a8197\examples\dfu\bootloader\hexdfu_dual_bank_ble_s132_pca10040.hex

So really - there's two issues here. I'm sure there is something simple that I'm doing wrong. Ideas?

  • @Eboris: If you use nRFGo Studio, Erase All, then flash the dfu_dual_bank_ble_s132_pca10040.hex with bootloader tab, it should work.

    When you test using the C:\nRF5_SDK_11.0.0_89a8197\examples\dfu\bootloader\pca10040\dual_bank_ble_s132\iar, 2 LEDs turned on. It sounds about right, I don't know why you can't find it advertising. Could you double check ? Make sure you flashed the correct softdevice.

  • Ok - I found the problem on why it wasn't advertising (or so I thought). I was using the nRfMasterControlPanel with the favorites filter ON. I expected to see the device advertising with the same MAC address. It turns out that the filter does not work based on the MAC address, it works off the advertised name. So - in the end - the device does advertise as expected and I was able to land an image vie the BLE based bootloader. Thanks for your help. EB

Related