Runtime failure with ble_app_beacon_bcs project on beacon HW

Question

I've got 3 of the 51822 kits: smart beacon, m-kit, and eval-kit. 
 I've successfully installed Keil uVision 5.1 and developed/loaded applications for eval-kit.
I've successfully run and built the applications for the m-kit using mbed.org. 
 However, when trying to develop code for the beacon, I can't get anything to run successfully on the beacon. 
 Attempt 1: using the project ble_app_beacon_bcs
This project compiles/builds fine, however after loading the hex on the beacon,
Outcome:
the beacon light (instead of flashing purple) will flicker ever so slightly, unless the SW1 is pressed -- where it goes solid green. 
 Attempt 2: change the source of ble_app_beacon_bcs, to do some very basic thing, like turn on the LED at boot for extended period of time (comment out all other source for advertisement). Same outcome as above. 
 Attempt 3: build a simple/basic application for 81522 on mbed.org and upload to beacon hw.
Outcome:
Master Control panel doesn't even attempt to upload it to the device; just disconects immediately.
Now I would expect that an application build from mbed would probably not work due to differences in default HW config. 
 Attempt 4: import and attempt to build the BLE_beacon project on mbed.org.
Outcome: this appears much different then the ble_app_beacon_bcs project as it is C++ based, and equivalently, doesn't build out of the box on mbed.org. 
 Overall, I expect that the ble_app_beacon project should work fine when loaded, but can't seem to successfully load anything but the pre-compiled .hex on the HW. 
 I wonder if possible errors are: 
 
 
 loading issues when using the Master Control Panel via Android device. I don't believe this is the case, as when I load the "precompiled ble_app_beacon.hex" back on the device, it returns to normal operation. 
 
 
 there are differences in the ble_app_beacon_bcs project then the precompiled .hex, and the project isn't properly setup for my HW. 
 
 
 Perhaps someone can shed some light or further debugging tips?

FormerMember · Accepted Answer

A hex file compiled from ble_app_beacon_bcs should have the exact same functionality as the pre-compiled ble_app_beacon.hex. I have followed the exact same procedure as you describe for uploading the beacon firmware, with a hex file generated from the source code. It seems to work fine! 
 I have attached the hex file generated from the beacon source code ble_app_beacon_bcs. Could you try to upload/program this file to your beacon device and check if it works? 
 Attachment: ble_app_beacon_from_source_code.hex 
 Edit: It should not be necessary to have the SDK installed in order to compile the code that comes with the beacon kit. 
 The problem may have been related to the IROM and IRAM settings. These settings depends on the softdevice that is being used with the application.
The beacon kit v. 1.0.1 firmware should be used with softdevice S110 v.6.0.0, and the IROM and IRAM settings should be the following:
 
 How the IROM and IRAM setting are found is explained in chapter 6.2.1 in the nRF51822 development kit user guide . 
 The difference between the targets, PCA10001, PCA10000, PCA10024, etc, is the mapping of which GPIO pins on the specific board that is used for the buttons, LEDs, UART, etc. Remember that the chip (nRF51822) on the different boards is the same.

Runtime failure with ble_app_beacon_bcs project on beacon HW

Top Replies