• State Not Answered
  • Replies 33 replies
  • Subscribers 63 subscribers
  • Views 11121 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 201866
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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!

Parents
  • 0

    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

  • 0 in reply to Jørgen Holmefjord

    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!

  • 0 in reply to 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.

  • 0 in reply to Jian Li

    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.

  • 0 in reply to Jørgen Holmefjord

    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.

  • 0 in reply to Jian Li

    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.

Reply Children
Related