• State Verified Answer
  • Replies 3 replies
  • Subscribers 71 subscribers
  • Views 2349 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 101072
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Working with RF51422 Development Kit

Vamsi Talla

I am having trouble getting up and running with the development kit (without the starter kit).

My setup is as follows:

The PCB antenna module is hooked up to the JTAG programmer/debugger and simple_tx_broadcast is downloaded on the chipset. The power is supplied directly via an external DC power supply to pins 1 (VTG) and 39 (GND) of P2 connector. LED_0 (pin 29 on P1 connector) and LED_1 ports (pin 29 on P1 connector) are monitored on the oscilloscope.

nRFAP2 development kit USB dongle is connected to the PC and ANTware II is used to receive data (the USB dongle that came with the RF51422 kit is not recognized by the PC).

The screenshot of the oscilloscope (corresponding to LED's) and ANTware is attached. In the scope trace, Channel 1 is LED_0 and Channel 2 is LED_1.

Can someone help me out why the simple tx broad demo is not working. Is it something to do with the fact that I do not have the starter kit and I am not supplying power to the right pins?

Thanks, Vamsi

Scope Traces.jpg

antware_screenshot.png

Parents
  • 0

    The error code you're getting (if it's hex 0x1000) means that the clock source is invalid. This doesn't make much sense given the code snippet you shared, so I suspect that you may be using an SDK that is built for a different chip than you have.

    Beware that SDK 5.0.0 requires a chip revision DA or later, due to upgraded S210 softdevices. If you have an earlier chip revision, you should make sure to use SDK 4.x.x, as stated in the SDK's release notes.

Reply
  • 0

    The error code you're getting (if it's hex 0x1000) means that the clock source is invalid. This doesn't make much sense given the code snippet you shared, so I suspect that you may be using an SDK that is built for a different chip than you have.

    Beware that SDK 5.0.0 requires a chip revision DA or later, due to upgraded S210 softdevices. If you have an earlier chip revision, you should make sure to use SDK 4.x.x, as stated in the SDK's release notes.

Children
No Data
Related
Terms of service