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

bootloader stuck in wait_for_events if started programatically

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

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

  • Hi,

    Your are correct, just a remark: for the first time I enter bootloader mode because there's no application on device, button is not needed nor it is available on the board. The workaround you have suggested is the workaround I have used, but I would like to use the official code to the extent possible for easy migration to new SDK versions if I should. I do see the DFU bootloader advertisement after entering DFU mode, but after connection it gets stuck. I see that the code is stuck at wait_for_events() by issuing gpio_pin_toggle command in the bootloader code. During transfer the led blinks rapidly but blinking is seen by eye (as events are arriving), after the problem arises, the led is lit with approximately half power because of rapid toggle of GPIO pin value (no way to tell its actually blinking with bare eyes).

Reply
  • Hi,

    Your are correct, just a remark: for the first time I enter bootloader mode because there's no application on device, button is not needed nor it is available on the board. The workaround you have suggested is the workaround I have used, but I would like to use the official code to the extent possible for easy migration to new SDK versions if I should. I do see the DFU bootloader advertisement after entering DFU mode, but after connection it gets stuck. I see that the code is stuck at wait_for_events() by issuing gpio_pin_toggle command in the bootloader code. During transfer the led blinks rapidly but blinking is seen by eye (as events are arriving), after the problem arises, the led is lit with approximately half power because of rapid toggle of GPIO pin value (no way to tell its actually blinking with bare eyes).

Children
No Data
Related