nRF51822 Beacon won't load application

[chris]

I tried loading SoftDevice, Bootloader, and Application using the SoftDevice and Precompiled hex files that come from the example code version v1.1.0. I am using nRFgo Studio v1.17.0. SoftDevice programs and verifies fine. Bootloader looks like it programs fine and I start getting the pulsing blue light as described in the user manual for DFU mode. I load the program application and it continues with the blue pulsing light. Holding down SW1 during power up doesn't change anything. Program of the application works but verify fails. The device still shows up as "DfuTarg". I have tried loading the application code using nRFgo and using the iOS nRF Toolbox application with the same results.

As I understand from the documentation if I power up without holding down any buttons and I have application code loaded the bootloader should jump to the application. Is the the expected behavior using the precompiled hex?

Thanks

[chris]

I tried the same radio/bootloader/app with another board (of our own design) with a nrf51822 on it and I get the same behavior. Device shows up as "DfuTarg", no luck loading it over DFU with the iOS app, and not exiting DFU mode despite having loaded the application via nRFgo with a j-link pro. At this point it looks like an issue with the bootloader precompiled hex that comes with the beacon v1.1.0 example code, either that or I don't understand what I need to do to get this bootloader to jump to application code.

[Stefan Birnir Sverrisson]

Hi

When you have programmed the Beacon kit with the softdevice and the bootloader, you should upload the application with the Android beacon app or with nRFToolbox DFU, provided both for Android and IOS. You can also use DFU located in the DFU tab in the Android nRFBeacon app to upload the new application.

Note that you will need both application (.hex) and an init file (.dat) to upload the application successfully to the Beacon kit via the bootloader.

In the apps (Android or IOS), you must first select the application, the init file and the device you want to upload to. If you have installed the Android nrf beacon app version 1.2.3, then you will find the beacon application and the init file in location "Nordic Semiconductor/Board/pca20006/…"

You can also upload the beacon application via Master Control Panel DFU function as described in the "firmware upgrade procedure" section in the nRF51822 Beacon v1.1.0 firmware documentation, follow steps 11-17 and load the \nRF51822 Beacon v1.1.0\Precompiled hex\nrf51822_beacon_app.hex beacon application. Before uploading, put the nRF Beacon kit into bootloader mode by pressing the SW1 button on the Beacon kit. First look at the section at the bottom of the page in order to provide the Master Control Panel with the correct python files. When the Python files are in place, follow the instructions on the page on how to upload the application to the device via the bootloader.

[chris]

Stefan,

Thanks for the response. I had previously updated MCP with the python files as you described. I can select the device under the Master emulator dropdown but when I hit "start discovery" I get the error message "Device discovery failed to start" and the popup window "No command complete event received". I seem to be at a dead end with the MCP method.

So far I have not tried the Android app, I'll work on trying out an android device. In the iOS application the device is found but when I try to upload it hangs at 1%. The first version of the nRF Loader iOS application I tried required a .bin file. This version did not work. I have read how to generate the .dat file (no dat file comes with the example code). I have generated a .bin, .hex, and .dat and next I will work on getting an android device since MCP and the iOS application both seem to be broken.

[Stefan Birnir Sverrisson]

The nRF Loader does not work with the new bootloader present. For IOS, you need the most recent nRF Toolbox DFU app v1.5

[Stefan Birnir Sverrisson]

I have edited my answer to include more information on how to upload the beacon firmware via MCP. I have verified on my side that it works.