• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 73 subscribers
  • Views 2883 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110682
Options
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

antoine

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?

Parents
  • 0

    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.

Reply
  • 0

    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.

Children
  • 0 in reply to Ulrich Myhre

    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
Terms of service