ble_app_uart_c not working on PCA10028 (with 51422)

[Vala]

Hi,

I have a PCA10028 which has a 51422, and trying to run ble_app_uart_c example on it. But no success. I don't get any thing on COM and LEDs do not turn on at all. Does any one have any idea about this issue? I am using nRFgo Studio for programming the dk.

I saw that in the SDK.v10 document it is mentioned that nRF51822 is needed for ble_app_uart_c (in the TESTING section). Is ble_app_uart_c also compatible with 51422?

Thanks.

[Einar Thorsrud]

The nRF51422 and nRF51822 are identical in all aspects except that nRF51822 does not have ANT support. So the ble_app_uart_c example will work on both without modification. Have you remembered to flash the SoftDevice before you flashed the application?

You can install the SoftDevice from Keil by selecting the SoftDevice in the drop down menue to the left of the load button on the Build tool bar. Alternativly using e.g. nRFgo Studio and the SoftDevice from components\softdevice\s130\hex\ if you are using the S130, or components\softdevice\s120\hex\ if using the S120 project.

[Vala]

Thank you very much for your answer.

Actually I recently started working with this DK and I don't have much experience about it and its tools. One thing that I'm not sure about is if I'm using nRFgo Studio correctly, although I have flashed the MCU several times successfully with different examples from SDK. In most of the cases it goes without any error. But for instance, about this example (ble_app_uart_c) I first flash the softdevice, it goes successfully and is verified. But when I try to flash the application hex file, it gives me an error that "this hex file has data in SoftDevice region, Try programming using "program SoftDevice", or erase all before programming". I thought Keil might sort of embedded the SoftDevice and application part together. So I erased the chip, and flashed only the application hex file. Am I doing any part wrong?

Should the LEDs start blinking only with the application hex file (without softdevice flashed)? Or there is a need to flash both parts to see MCU functioning?

Thanks.

[Anders Strand]

Check out the "Getting Started" Section on infocenter. You should erase the chip -> flash softdevice -> Flash application (usually with Keil, but you can use nRFgo studio for this as well).

[Vala]

Thanks for the answer.

Actually it is exactly the process I was doing. But I downloaded the SDK again, did the same process and now I'm able to exchange data between ble_app_uart_c and ble_app_uart examples. I don't know what the problem was. But there is still one problem. The PCA10031 with ble_app_uart_c only recognizes the PCA10028 with ble_app_uart and when I use another board (a custom board and not with nordic SoC But with UART profile) as a peripheral, PCA10031 (with ble_app_uart_c) doesn't find that and is not connected to it. Is there any part of the code of ble_app_uart_c which corresponds the specifications of the peripherals? Or do you think there is another problem?

I have tested that custom board with nRF Master and nRF UART and I see that it advertises and sends some data.

Appreciate your help.

[Vala]

OK it seems that the problem is because a different service UUID that the custom board uses. Is there any way that I can change what peripheral with what UUID the central (with ble_app_uart_c) should look for?

Please tell me if I should create a different question for this. Thanks.