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]

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.

[Jørgen Holmefjord]

Different versions of nRF Connect will flash different versions of the connectivity firmware, as the API in the low level driver used by nRF Connect (pc-ble-driver) have to correspond with the API of the used softdevice version. Different chips will have different softdevices, and this will decide which connectivity firmware that is flashed. nRF Connect use the serial number of the SEGGER chip to determine which chip is present, and to flash the correct connectivity firmware. This might be causing some issues for you, when you have a board with a serial number (4830* vs 68*) that is not recognized by nRF Connect as one of our DevKits. This could cause wrong connectivity firmware to be flashed to your board. You can try flashing the correct firmware manually (for nRF Connect 2.3.0, this will be connectivity_1.2.2_1m_with_s132_3.0.hex from here), using nrfjprog or nRFgo Studio.

[Jian Li]

Hi, Jorgen: Thank you for help. My first attempt is failed, here are screen shots

 

I tried erase all, program application, boot loader, but all end up in fail to read hex file. I am reading how to use nrfjprog and will try it and let you know outcome when I go through it.

[Jørgen Holmefjord]

How large is the hex-file on your computer? If it is other than 460KB, there might have happened something to the download from GitHub. When I left click the file and select download on GitHub, it looks like the file is actually downloaded, but when I open the file in an editor, I see a HTML file. Make sure you click in the file, click on RAW, and then left click and select "save page as" or similar.

[Jian Li]

I download the hex file from your web site the link in your last reply here https://github.com/NordicSemiconductor/pc-ble-driver/tree/v2.2.1/hex/sd_api_v3 and store in my local PC,

It is 2425kB shown above, is this right file. Why should I download it from GitHUB?

[Jørgen Holmefjord]

Like I explained above, if you left click it on GitHub (the page I linked is our account on GitHub), it will store the HTML page that shows the hex-file, not the actual hex-file. Please follow the method I described above to download the file, (or download this: connectivity_1.2.2_1m_with_s132_3.0.hex)