8 years, 11 months ago.

Can't get Nordic nRF51-DK FOTA working.

I have followed the steps as closely as possible, and can not seem to get FOTA working. I have tried on both iOS and Android.

Here are the steps I have done.

1) I have downloaded the initial image found on this page https://developer.mbed.org/platforms/Nordic-nRF51-DK-FOTA/ 2) I have unzipped that file and copied BLE_Default_Bootloader_App_DK.hex to the filesystem of the DK board. At this point, LED1 is blinking. 3) I have my project in mBed compiler, and have selected "Nordic nRF51-DK" as the target, and selected "App for FOTA" as the build type. 4) I have installed "nRF Toolbox" onto an iPhone 4S with iOS 7.1.1. 5) I have copied "my_project_NRF51_DK_OTA.hex" to the iPhone using iTunes. 6) I have selected "DFU" from the nRF Toolbox app, selecting the file, file type (application), and device. In selecting the device, I notice that the device name is DRUTarg. 7) The "Upload" button turns from grey to blue, and I click it. A pop up appears saying: "DFU - The connection has been lost". I press OK to dismiss the dialogue. At this point, LED1 is no longer blinking. 8) I select device again, this time is has the name "nRFx". 9) I press Upload, and the file appears to be successfully uploaded to the board, I see a success message. 10) The following appears in Terminal as debug messages from the board: Initialising BTLE transport ping ping ping ping ping ping

So far, so good. Here's where things start not working.

10) My app is not functioning. It is not broadcasting BLE advertisements, and no messages are being sent to Terminal. The app was tested without FOTA, and was working well. 11) DRU Toolbox is no longer able to see "DRUTarg" in the list of devices. I understand the bootloader should remain on the device and allow me to upload another update to the firmware. 12) I have tried this on Android with the nRF Master Control Panel following a similar process, and getting the same result. 13) If I do this entire process using the app within the nRF Toolbox, "ble_app_hrs_s110_v5_0_0_0...", then the update works and I'm able to connect to it using the "HRM" button, and then connect to the actual board and see the test data as expected.

My suspicion is that my app is being compile to use the latest SoftDevices (and not being included in the build) and the initial image has a previous version of the SoftDevice on it, although I am not able to confirm this. Since I downloaded the SoftDevice from the site, as a hex, I am not able to recompile it with a newer SoftDevice.

Any suggestions? How do I get or create an updated initial image for this?

Thanks in advance.

Question relating to: