nRF51822 beacon kit - programming and detecting

[Dan]

I have the nRF51822 beacon kit, using Keil uVision, downloaded the beacon app and all associated files. Compiles, but how to program the beacon board?

I've done two things: Thing 1: I have connected a programming cable between my NRF52-DK board and the beacon (using the 10 pin "Debug Out" connector). Using nRFgo Studio, I erased the device, then "program softdevice", then "program application" without error. I think it is really programming the NRF52-DK (NOT my beacon target board).

Thing 2: Plugged in a nRF51-Dongle and programmed this the same way as above, again with no errors.

Now, I am trying to use the iPhone app "nRF Beacons" to detect my beacons, and I get nothing.

In "thing 1" above how do I use the nRF52-DK to program the beacon board? in both things above, why doesn't the iPhone app detect my beacon? Is there another app that I can use that will sniff them out?

Thanks in advance - Dan

[Håkon Alseth]

Hi Dan,

It is important that the external device you're programming has the same voltage as the nRF5x-DK board. There's logic present that will automatically switch when it detects the same voltage on the DEBUG_OUT header.

Have you tried powering the beacon with one of the "VDD" pins on the nRF52-DK ? (note: Do not use the "5V")

Cheers, Håkon

[Dan]

Thanks - yes, I powered the beacon from a separate lab supply (3.1V). I had some progress. Turned out my 10 pin (FTSH) connector was backwards. When I put it in the right way, I think it detected the external beacon. However, it won't program. In Keil, it doesn't see anything in the "target driver setup" when I plug in the beacon. If I remove the beacon it sees the nRF52 development board. The beacon is working, it transmits, so it's alive but I can't program it. Maybe the backwards header damaged the interface? I've ordered a new beacon board. One of the docs I found said that I should ground P0.30 on the dev kit when programming the beacon. Do you know if that's true? I also read that there may be issues with the programming clock speed, so I lowered that, with no change. Any other ideas?