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

Problems testing the button_radio_example

Hello

I have the nRF51822EK PCA10001 (V1.0) and PCA10000 (V1.0).

I'm working on a project where i'm going to send data from a custom board over to the PCA10000 dongle, and import the data from the COM-port to MATLAB.

Right now i'm trying to get the original PCA10001 board to transfer the button status over to the dongle. I'm programming the units using nRFgo Studio (Program application) with original button_radio_example_rx.hex for the dongle, and original button_radio_tx_example.hex for the main board. Programming the units is successfully.

I'm using PuTTY - Session to monitor the COM port for the dongle, using serial connection with 38400 speed, but nothing happens when I push the buttons.

I get no connection when I try to use the PuTTY - Connection - Serial with the dongle COMXX, speed 38400, 8 data bits, 1 stop bit, and all combinations of parity and flow control.

Do I also need to flash the SoftDevice to make it work? I have tied using S110, but then I get "This hex file has data in SoftDevice region ......"

Is there something important I have missed?

I have used this guide: devzone.nordicsemi.com/.../a00033.html

Other info: Keil µVision (5.13.0.0) MATLAB (R2013a) Win 7 Home Premium SP1 nrf51_sdk_v6_1_0_b2ec2e6 PuTTY 0.63 SoftDevice (s110_nrf51822_7.1.0)

Attachment: putty.JPG

  • Turns out because I have an earlier version of the PCA10000 board (rev 1.0). Check your board to see if you have V1.0 like I do. If so, this fix is easy... once you know anyway.

    Go to Includes/boards/pca10000.h. There is an #if /#else construct for selecting between board versions. Change to #if 0 for V1.0

    You then must compile the project to generate a updated hex-file.

    It works when using PuTTY - Session

    Nordic semiconductor should mention this in the documentation!

Related