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 Tamas,

    Testing here with your hex showed the same issue. However, when I tried your bootloader with our HRM example (from SDK v6.1) I saw no issue, the device can enter DFU bootloader mode and then I can update to other firmware. I attached the the source code (it should be the same as in your SDK v6.1) and the hex file I compiled. (please see that in the answer, it's not possible to attach file in comment)

    I suspect that the could be something wrong with the way you disable the softdevice, jump to the bootloader and enable it again. The issue must be with the gatt table, because it can advertise without problem, but having trouble when we do service discovery. I haven't tested to compile with gcc, but if you can send me your tool chain set up with your HRM and bootloader source code , I can try to compile and debug here.

Reply
  • Hi Tamas,

    Testing here with your hex showed the same issue. However, when I tried your bootloader with our HRM example (from SDK v6.1) I saw no issue, the device can enter DFU bootloader mode and then I can update to other firmware. I attached the the source code (it should be the same as in your SDK v6.1) and the hex file I compiled. (please see that in the answer, it's not possible to attach file in comment)

    I suspect that the could be something wrong with the way you disable the softdevice, jump to the bootloader and enable it again. The issue must be with the gatt table, because it can advertise without problem, but having trouble when we do service discovery. I haven't tested to compile with gcc, but if you can send me your tool chain set up with your HRM and bootloader source code , I can try to compile and debug here.

Children
No Data
Related