# Custom PCB: How to quick check if BLE is working? nRF51822AB

Hi guys,

I hope you can answer my question: I made myself a custom pcb for testing purpose. I can program the nRF51822 just fine. Thats the actual state right now.

In combination with the nRF51822-EK: How can I just quick check if my BLE is working? I just want to kinda sniff, if I got RF-Output. It doesn't need to be a connection. I just want to be sure, that RF works before I'm getting into SW-debugging and API and stuff like that.

How can I check that? Is there a plain, simple solution?

Regards, Stephan

edit retag close delete

If you have a newer iphone, I've found a very good tool to use is LightBlue on the iphone app store.

( 2013-08-28 15:28:20 +0200 )editconvert to answer

Sort by » oldest newest most voted

Hi Stephan,

more

I use the simple code in led_radio_example. The USB dongle code transmits a packet and the EVK sample code receives the packet. I've modified the code somewhat to go in both directions, but the simple sample code Nordic supplies works. So load the USB dongle that comes with the EK with the led_radio_example code for the dongle, and load your PCB with the led_radio_sample code for the EVK board. If you have an LED or scope you can modify the code to toggle the IO upon receiving a packet, or just set a break point in the debugger. You then need to open a serial port terminal to the USB dongle and type 0 or 1 to send the packet. These packets use the 2mpbs Nordic RF mode and are not BLE compatible, but they show that the RF hardware is working OK. But, it is best to modify the code to send both ways, I once had a hand soldered PCB that could receive but would not transmit until I cleaned up the soldering on the nrf51822 chip.

more

I have a RF Explorer, a dirt cheap spectrum analyzer. If I run the DTM example, I can clearly see the energy at the frequency that the nRF is transmitting at.

It's a cool toy if you just want to test out stuff like this, also useful for setting up WiFi.

This doesn't check much, but at least you know the PLL is working

more

Simplest, turn on the radio with this:

Then check radio output with any handy 2.4GHz spectrum analyzer and antenna :)

Slightly more complex, set up radio_test_example from the SDK (and set up your board to talk with uart), then use uart commands to control radio. If you have a BLE test rig such as Anritsu that can be hooked up to the uart as well, enabling BLE DTM.

My first try, BLE wasn't working but the radio was just fine, due to bad crystal. That's why it seems best to test radio directly without BLE first. Something to watch out for, anyway.

more

Hi guys,

wow, thanks for all that cool feedback! Really nice hints here! My problem is that I can program the nRF51822 just fine with the SoftDevice and all but I can't get any RF-Output of it. ATM I dont know if it's just soldered badly or if the mistake is somewhere else....

But since I do it as a hobby, unfortunately I do not own \$-RF-Teststands ;)

So I might just try to set up a UART example to see if the chip is working. Maybe some blinking LEDs and stuff like that.....

I'm wondering why the heck it won't work, though! :(

more

This really sounds like a separate question from the one originally posted here, but if the chip works nicely except for radio, I guess it's the 16 MHz crystal being mounted incorrectly. If the chip functions correctly, including proprietary radio examples, but BLE softdevice initialization hangs, Pål is most likely on the right track below, with regard to low frequency clock source used.

( 2013-09-03 14:18:36 +0200 )editconvert to answer

Pål,

I don't believe it! It works! It truly works! :) :) :) :) Thank you SO much! This one made me mad for the last days because I could not figure out what was wrong! Seriously, thank you SO SO much!

This one should be "pinned" somewhere where other users might find it fast!

It's early in the morning but you just made my day!

Stephan

more

No problem, I'm really glad to be of assistance it would help others if you could mark my answer as accepted, because then other people can look at the symptoms and find the solution. :)

( 2013-09-04 05:54:36 +0200 )editconvert to answer

[hide preview]

## Recent blog posts

• ### Nordic Developer Zone celebrates its 4th year of helping developers succeed - Celebrate with us and win a Nordic Thingy: 52’

Posted 2017-06-23 10:12:53 by John Leonard
• ### nRF52 Development with CLion

Posted 2017-06-22 09:50:54 by dansheme
• ### Simple GPIO driver example

Posted 2017-06-22 13:38:36 by Hans Elfberg
• ### What mom didn't tell you about ble_app_att_mtu_throughput on the nRF52840 evaluation board

Posted 2017-06-16 16:12:15 by George
• ### Introducing Nordic’s new software licensing schemes

Posted 2017-06-15 11:21:39 by Reidar Martin Svendsen

## Recent questions

• ### NRF51822 to NRF51822 Over the air update (DFU)

Posted 2017-06-25 16:25:45 by wogisha
• ### Advertising with device_name Vs whitelisting

Posted 2017-06-25 14:39:12 by raju

Posted 2017-06-25 11:14:42 by Eric
• ### NRF24L01+ Minimum order quantity

Posted 2017-06-25 10:14:55 by tabrown
• ### Can I use MDBT40 with ATMEGA328 ?

Posted 2017-06-25 09:59:42 by sai