How to run UART/Serial Port Emulation over BLE on SDK v14.2.0?

[Jian Li]

I try to run UART/Serial Port Emulation over BLE on SDK v14.2.0 with nRF52 DK and nRF Connect on Android phone following link "http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.2.0%2Fble_sdk_app_nus_c.html&cp=4_0_1_4_2_0_2". I compile and download example code with softdevice S132, the phone detect Nordic-Uart, and connected, but nothing more than that, if I try to send something, BLE will disconnected, even it will be re-connected if requested. I run Tera Term on PC, it shows Nordic-UART, but does not show anymore thing, no response to keyboard. There are some code displayed in this link, they are said added to be added in softdevice, it is not clear that they are already added and I do not have to add them in again, if that is the case, why they are displayed here. If not added, where they should be added, in main.c or ble_nus.c? Please help!

[Jørgen Holmefjord]

Hi,

You are linking the the NUS central application. It sounds like you want to use the peripheral application? Did you change anything in the example? Have you tested the precompiled HEX-file found in the hex directory in the example folder? Could you please post some screenshots showing the output of the terminal, etc.? You should not need to add anything to the example to get it working, the code in the link explains how you can use the received strings to do things in the application. This is an extension to the application, and is not needed for the purpose of the example.

Best regards,
Jørgen

[Jørgen Holmefjord]

I see there is a bug in the example. Please have a look at this answer.

[Jørgen Holmefjord]

Do you get this error immediately, or after a while? Error code 8198 = 0x2006 = NRF_ERROR_SOC_POWER_OFF_SHOULD_NOT_RETURN. If you are running the application in debug mode (debug mode will be enabled when debugging or after programming the application), the application can enter emulated system off mode, which will make the function sd_power_system_off() return and cause this error.

[Jian Li]

Good morning, Jorgen. Thank you for help!

I re-test it by compiling in release mode, the error does not appear. But nRF UART in my  phone shows " The device does not support UART, disconnected", here is screenshot of my device, it is Android 5.1.1. I try nRF Connect, it works with other examples like Heart and Blinky, but cannot connect to UART emulator in client mode, in Server tab, it could show two generic access as shown in screenshot 2 as follows:

 

 What is phone OS requirements for nRF URAT V2.0? I remember nRF Connect works in Android 5, am I right? Any other phone app available for me to try?

I  also try desk version of nRF Connect, it responses cannot find COM port, Tera Term can find and open the com port, why nRF Connect cannot?

[Jørgen Holmefjord]

Please try to disable and enable Bluetooth on your phone. You can also try with the UART application in nRF Toolbox.

The error you get in nRF Connect is most likely due to that you are using it with a device that is not supported. Note that nRF Connect will only work with nRF51 Dongle and nRF5x-DKs.

[Jian Li]

Hi, Jorgen, Thank you for help. I download nRF Toolbox, it is better, but more complicated. There are 9 buttons are blank and there is no guide how to set them, I cannot find manual here http://www.nordicsemi.com/eng/Products/Nordic-mobile-Apps/nRF-Toolbox-App or other places. Where is it hidden?

My DVK is Murata MBN52832, Murata claims all your firmware and test codes could be tested without modification, it works fine with Blinky, Heart Rate etc examples. When PC version nRF Connect discovery the DVK, request to program the DVK with the latest connectivity firmware, but cannot program it because nRF Connect cannot find com port. I have to ask Murata why it behaviour like that, how its connectivity firmware could be re-programmed? Mean while I cannot wait so that I ordered two more nRF52 DK yesterday to see what differences when they arrive. This seriously damages my confidence to design MBN52832 module in my product if it could not be reprogrammed later. Am I right that the connectivity firmware is for ATSAM3U2CA-AU MCU, not for nRF52832 that is programmed by soft device S132.

[Jørgen Holmefjord]

Unfortunately, I don't think we have any user guide for nRF Toolbox. You can modify the buttons by clicking edit in the right corner (color turns red-ish), and clicking on each button. When done editing, click done. You can also slide the screen towards right, or rotate the phone, to see the "terminal view".

I have not tested Muratas DK, so you should ask murata about this. It looks like hey are using similar debugger chip and UART pins, so in theory it should work. You could aslo test with an older version of nRF Connect. The connectivity firmware is for the nRF52832 IC, and is used to control the softdevice using the serialization API. The interface MCU has its own firmware (Segger J-Link OB).

[Jian Li]

Hi, Jorgen:

  Here are two screenshots from SES debug and nRF Tool Box log (only the initial part in screenshot)

It seems there are repeated reports "Error (0x81) GATT INTERNAL ERROR", how this can it be fixed.

  I tried to run old SDK 14.1.0 yesterday after reading Mark's blog 5 months ago, he has the same problem as I have. The 14.1.0 contains the same bug as we already changed, wonder why Mark does not had the same problem!

  Will try an old nRF Connect later and let you know outcome. Thank you for help!