This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
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

Getting Started with Master Control Panel

Sorry for this long message. I am new and quite lost. I just purchased a nRF51 DK and installed nRFGo Studio, Keil MDK and NRF51 SDK. With nRFGo, I programmed the Segger of my dev board with the S130 SoftDevice. I also was able to build and load the Heart Rate application from examples\ble_peripheral\ble_app_hrs\pca10028\s130\arm5_no_packs. (uVision V5.17.0) I got the nRF-Toolbox application on my iPhone from App Store, can connect to Nordic_HRM and it works.

But I ran into a few problems:

My ultime goal is to receive voltage measurements from a simple analog circuit, via ADC and bluetooth on my PC (windows7, ideally with a C# .net project), or my iPhone (objective C). I already did it w/out bluetooth with an Arduino, but now want to do it wireless w/.out arduino.

To begin with, I would like to test the Heart Rate application using the Master Control Panel (I downloaded version 3.10.0). I only have COM3 listed in the combo text box (and the device manager shows JLink CDC UART Port on Com3), so I use it. The log says "No response from master emulator" and I can't do anything else (in particular I can't Start discovery), whereas the Heart Monitor documentation suggests I should be able to use to Watch notifications of heart rate. (1st PB)

After digging for quite some time, I thought I should program the master emulator MFEW nRF51822 from MCP. I also connected pin 0.3 to ground. Doing so, I can start discovery. This gives me a list of 5 devices, but none of them seems to be the NRF51. (2nd PB) Besides, when I go back to Keil uVision and try loading the Heart Monitor program, its fails with message "Flash Downlaod Failed - Cortex-M0". (3rd PB).

At last the nRF51 device isn't discoverable (I have other Bluetooth devices that such as a headset), and I dont understand why. (4th PB)

Would you please give some advices?

    1. It looks like you solved this problem already. You have to flash the correct firmware for MCP to be able to work.

    2. This means that the device is not advertising properly. There could be many reasons for this, but remember that in the heart rate example, advertising times out after some time and the chip goes to sleep. You need to push a button to wake up the chip again and restore advertising. It could also be the iPhone connecting to the chip and making it stop advertising.

    3. A likely problem is that the chip is sleeping again, or hardfaults/resets/sleeps whenever the debugger attaches. This causes the debugger to fail to connect properly. Doing a search for "Download failed" here on DevZone should give you some solutions to this.

    4. The chip is likely not advertising. Could you check if it you are able to discover your device through nRF Toolbox? If you are not discovering it with MCP, but nRF Toolbox can see it, then it's likely that there is a range or interference issue near the device connected to the computer. Try moving it to a USB hub or something that's closer to the HRM device.

  • Thx a lot. The Learning curve looks steep.

    I didn't find any solution yet for the "download failed". I was under the impression that, either I program the SoftDevice with nRF go and I can download the HRM with Keil, or I program the firmware for MCP but Keil will not load HRM. When I program the firmware MFEW nRF51822 using MCP, does it not erase the Softdevice and make the load of HRM impossible?

    As for my incapacity to discover the device (I remembered BLE start with bluetooth 4.0), is this simply because of my oldish hardware: PC with bluetooth 3.0, iMac with LMP 0x4 (which means prior version of Bluetooth) I guess I need to get a Bluetooth 4.0 USB adapter?

  • You should be able to flash both the softdevice and the application using nRF Go. Please also make sure you are using the most recent version of it. It's likely that the device resets upon getting the debugger connected, which starts the chip and goes straight to HardFault because of no app present.

    And yes, you cannot use Bluetooth 3.0 devices to discover the Low Energy devices introduced in 4.0. The SoftDevices from NordicSemi has only the LE type of devices. I thought you were using the MCP on your computer (with the dongle/devkit) to discover, so I assumed you were on the correct hardware.

    You will need a 4.0 (or better, 4.1/4.2) compatible adapter if you want to discover LE devices yes :) If you bought a kit with a nRF51822 dongle in it, you can flash the Master Emulator Firmware on this and use it as a peer for testing.

  • Thank you. I got it working. I can't use the master control panel, but was able to listen to the port with a C# project. I went further and modified the UART app for my iPhone to receive ADC input measurements and send commands to NRF51 DK board, or to an external nRF51822 board. I have other questions but on a different subject. I guess I'd better start another post.

Related