This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Blinky does not work after OTA Firmware update

Hi,

I am following the step by step tutorial "Getting Started with Secure DFU Bootloader Step by Step guide

Before following the above guide I compiled  ble_app_blinky from the examples/ble_peripheral folder of NRF52 SDK Ver 17.0.2

The above example was tested successfully on NRF52-DK along with NRF Blinky App running on an Android phone. Everything worked well.

I then followed the guide to create:

1. Secure bootloader (Steps A, B in the guide)

2. Created the application ZIP file (Step C)

3. Performed DFU using NRF Connect for mobile (Steps D1 to D3)

STEP D4 (Testing the Application after DFU)  - failed - Most of the time I could not see the BLE Device name in NRF Blinky App. Once I did see the BLE Device name "Nordic_Blinky" but it would not connect. Once it did connect and I was even able to switch on the LED but after that it seemed the program froze - there were no responses to LED on/off on Blinky App nor was there any response to BUTTON press on the NRF52-DK. 

I failed to understand what is it that I am doing that is breaking the Application!

Any help in this regard would be helpful. 

  • Hi,

    Following the same guide and using ble_app_blinky application on nRF52840 (with SoftDevice s140), I was able to see the "Nordic_blinky" after DFU has finished successfully. For testing I used Bluetooth Low Energy desktop application v3.0.0.

    There are several things you could try in order to find the cause of the problem.
    Make sure that you are using the proper unchanged application from ble_app_blinky_sample.
    You could try inputting some print statements into your code and see in the terminal if you get anything. This could indicate some other problem with your application (excluding Bluetooth).
    Another thing to try would be to flash the same application to your board and check if it is advertising. This would show that Bluetooth part is working correctly.
    Are you sure that you have not missed any steps describe in the guide or used a changed version of the same application?

    Best regards,
    Dejan

Related