Programming Raytac module through nordic nrf52832 development board.

[Divyashree]

I have got a Raytac module MDBT40(nRF51822) and development board nRF52832. Now I want to program the module using the development board. I have followed this video ( Programming and debugging custom nRF5 devices) and few blogs to make the connection as in the attached image.

I am completely new to keil and these things as I work on other platform. I am not sure about (Please let me know )

1. Is it possible to program nRF51 through nRF52?
2. If yes, How do I get a confirmation about my module is getting programmed?

I am using nrFgo Studio to program the softdevice and then Keil to program beacon code. Where in nRFgo the connected module is not visible. Why is this?

The supported sofdevice for MDBT40 is S110 but nordic nRF5-SDK-v12-zip as support for only s130 and s132. So Use s130 ? or else Please provide the link to SDK support for s110.

Please, somebody help me to connect the Raytac module through development kit for downloading the softdevice at first and then SDK's beacon code?

The reason why am trying this way is because I don't have J-Link Debugger.

If in case am wrong with my approach, please suggest how to go further.

Any guidance or links are helpful. Thanks.

[MartinBL]

Hi,

1. Yes it is possible to program an nRF51 device with a nRF52 DK (and vise versa).
2. It depends on how you program it. If you do it in nRFgo Studio it should look like this:

In Keil a successful programming looks like this:

---

When you program an external device with an nRF5x DK development kit three things can happen:

1. Everything works as you have intended and when you program your external device you get the "programmed successfully message". Note that there is no message telling you whether it was your external device or the nRF5 device on your DK kit that was programmed.
2. The nRF5 DK doesn't register that you have connected an external device. This will make nRFgo Studio automatically program the nRF5 device on your DK kit instead of the external one. And again, there is no warning telling you about this.
3. The programming fails altogether. Then you will get error messages.

Case #2 might happen if you have wired something incorrectly. It can also happen if you haven't powered on your external device so that the nRF5 DK doesn't sense a voltage on the Vtg pin. It could probably also happen if the voltage is too low. Have you measured that the voltage from your batteries is actually 2.8V?

Blinking LEDs can be an easy way of figuring out which device has been programmed. If you are programming BLE applications you can also use a phone to see which device is transmitting.