bootloader stuck in wait_for_events if started programatically

[Tamas Varga]

Hi,

I have modified slightly the OTA bootloader sample in SDK6.1 and SoftDevice 7.1.0. After flashing the bootloader code to the nrf51822 it works like charm, I can update the firmware on the module OTA with MCP. If I upload OTA a modified version of hrs example code in SDK with OTA DFU support, the bootloader gets started by writing 0x01 to the DFU control characteristic, but afterwards it is stuck in wait_for_events function in bootloader.c. I use gcc 4.9.3 as compiler on Linux. Do you have any ideas what I should check?

I have checked with the unmodified codes in SDK v6.1. DFU does not work with MCP with those codes either. Is gcc problematic with bootloader?

Thanks,

Tamas

[Hung Bui]

Hi Tamas,

MCP v3.7 should work with DFU from SDK v6.1. Could you try and test with stock example (ble_app_hrs_dfu) in SDK v6.1 and let me know the result ?

Note that the ble_app_hrs_dfu won't do a chip reset, but jump directly from the application code to the bootloader when writing 1 to DFU control characteristic. So in the bootloader you should not reinitialize the softdevice when triggered from application.

Attached file: ble_app_hrs - TestDFU.zip ble_app_hrs_dfu.hex

[Tamas Varga]

I've uploaded some additional information.

I use gcc Makefile for bootloader (Board/nrf6310/device_firmware_updates/bootloader/gcc/Makefile) with the following contents: Makefile

I use gcc Makefile for hrs application (Board/nrf6310/s110/ble_app_hrs/gcc/Makefile) with the following contents: Makefile

Source codes are not modified, just the bootloader start address is altered to 0x35000 in dfu_types.h and linker script. I'm pretty sure I miss something trivial, but I don't know what it is.

Board is custom made, an I2C sensor is connected to MCU.