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.

[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!

[Jørgen Holmefjord]

Please also check that you are not bonded with the device. If you are, you need to delete the bonding information from the Android Bluetooth settings.

[Jian Li]

Hi, Jorgen, Great, it works now!

Here are two screenshots:

  Thank you for help.

 Good night!

[Jørgen Holmefjord]

That is good to hear! Happy to help!

[Jian Li]

Hi, Jorgen: 

Just let you know that I tried an older nRF Connect-Windows V2.2.1, the outcome is the same as V2.3.0. Here is the screenshots:

 

As far as I know, MBN52832 module and DVK use nRF52832 IC silicone version specification v1.3, not the latest v1.4, not sure it is too old? Why does Murata not update it to latest connectivity firmware.

   I'll test nRF52 DK when they arrived. Thank you for advise!

[Jørgen Holmefjord]

I should have specified this in more detail. I meant an even older version of nRF Connect (v1.x.x). There have been some changes in how the J-Link devices are identified in the later versions. Maybe Murata have not tested this with their DKs. Note that a new version of the product specifications does not neccessary indicate a change in silicone, only that the documentation have been updated to make sure the information within is as complete and accurate as possible. Silicone revision is given by the markings on the chip and can be compared to the compatibility matrix, but I do not know if you have this markings available on the module?

[Jian Li]

Hi, Jorgen: Just let you know that I tested older version 1.1.1 and it is worse, it does not discover COM13 and ask to re-program the latest firmware, all three pull down menus are not responsive, the open log, clear log functions works, as shown in screenshot.

   My order of nRF52DK has not arrived, Mouser is slower and I'll chase next Monday. I'll let you know after test them. Have a good weekend!

[Jian Li]

Hi, Jorgen: Great! Both nRF Connect v1.1.1 and V2.3.0 works with nRF52DK, I try to find out why Murata DVK module does not work, it has the same host MCU and nRF52832 SoC. I noticed that both versions like to re-program DK with the latest connectivity firmware, are they programming different connectivity firmware? How important is the latest connectivity firmware, it seems mobile version nRF Tool box does not requires the latest firmware, is this firmware mainly required on serial communication that nRF52832 talk to the host MCU, not BLE radio communication? If yes, do I need the latest firmware code in my host processor to control Murata module apart from your SDK code to control BLE radio, if yes, where can I find the source code? Murata does not know why its module cannot be reprogrammed and they has no tool to program its module, their support is really poor.