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]

Thank you for quick response. Programming the connectivity_1.2.2_1m is successful with your real hex file. It could be programed as soft device, boot loader or application, which one is correct? However, nRF Connect 2.3.0 cannot find COM port without Segger Embedded Studio active. When SES is active and application is download, nRF Connect still request to re-program it to the latest connectivity firmware, then still cannot find COM port when it tries to reprogram. It seems nRF Connect like different version firmware other than _1.2.2_1m!?

[Jørgen Holmefjord]

nRF Connect v2.3.0 works fine with this firmware on my board. Most likely nRF Connect think you have a different chip/board based on your serial number, and tries to flash a different firmware. What happens if you choose "No" when you are asked to flash the latest firmware?

[Jian Li]

If "No" is clicked, it cannot find Com port. I'll use nRF52 DK in development but still design Murata in product if there is no better choice. Has Nordic Semi has any BLE 5 module for sale that already got license and FCC certificate like MBN52832 has? Is there any SDK to help host processor firmware development interface to nRF52 SoC? Is there open source code in C that I can download? Thank you in advance for help!

[Jørgen Holmefjord]

Ok, sounds like we cannot help you with getting the Murata board to work. We only produce chips, no complete modules. Modules are created by our module partners. What do you mean by "host processor firmware development interface to nRF52 SoC"? 

[Jian Li]

Is there any example code similar to this http://www.ti.com/lit/ug/tidu532/tidu532.pdf? What is the recommended protocol between nRF52832 and host processor over UART port? Is nRF Connect code is open source code? Does Nordic semi has plan to produce dual mode BLE 5 IC in future?

[Jørgen Holmefjord]

We have serialization examples in the SDK, which allows you to control the softdevice over UART and SPI. You can port these libraries to other architectures if you want. nRF Connect for desktop is open source, and available on our GitHub account. Bluetooth Classic have much higher current consumption than BLE, and is not in our scope of ultra low power devices.

[Jian Li]

Hi, Jorgen, many thanks for your help. I download PC version nRF connect and am studying serialization and will try it next week. Regarding BLE module placement on a daughter PCB, I thought the module should be placed on the edge of outside of daughter PCB, not on the side between two PCBs, even it is on the edge of daughter PCB, am I right? How much percentage of signal loss comparing to mounted on the outside of PCB if I have to place it on this disadvantage position?

[Jørgen Holmefjord]

Yes, it is recommended to place it on the side to allow the signals to radiate freely. The reduction in signal will be dependent on many factors, we do not have any numbers on this,

[Jian Li]

Hi, Jorgen:  I try to follow this your link to set up serialization test with two nRF52DK boards, http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/nrf51_setups_serialization.html?cp=4_0_0_1_4   and find it lack of details, should I power up both board in set up connectivity board and application board? Or prepare software separately and then connect them together to do the test? Regarding application software, it mentioned only Keil, and I cannot find any examples in SDK14.2.0 in ser_s13x_transport folder. The normal BLE examples, they all need soft device programmed. Where can I find right examples? There is instructions to verify test results, should I use Mobile phone to verify test connectivity board or Tera term to verify UART in application board? Any more details of examples I can follow! Thank you in advance!

[Jørgen Holmefjord]

You should follow the steps in the order described in the Serialization software setup section. Also make sure you first cut the solderbridges as described in Serialization hardware setup. The application board should not have the softdevice programmed, only the connectivity board need this.