• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 145 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289490
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Question about CLI Connection Issue

user116200

Dear Support Team,

I'm trying to test 802.15.4 feature with the precompiled radio_test hex file, but got an error when connecting the CLI through PuTTY. Below is the detail.

Purpose: I would like to test basic function of 15.4, like send an Tx signal and check it with spectrum analyzer, or receive a package and check its power and EVM. I plan to use precompiled hex file and config the board with CLI commands here https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.1.0%2Fnrf_radio_test_example.html 

Board: nRF52840, PCA10056, version 3.0.0

Hex File: loaded only nRF5_SDK_17.1.0_ddde560\examples\peripheral\radio_test\hex\radio_test_pca10056.hex

PuTTY Setup: I mainly followed the instruction on this link to config PuTTY https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.1.0%2Flib_cli.html&anchor=lib_cli_terminal_settings_uart

And then I got a fatal error about network error, as show in picture below.

I'm guessing this related to my PuTTY as I'm not quite sure for certain settings.

First, it's about the terminal line discipline options. It has been mentioned several times on the instruction page with different selection. I'm not quite sure which is the right config for my test. While I tried all three and they all failed with same connection error.

The second part I'm not sure is about the COM port number. There are two COM port numbers appeared after I connecting the nRF52840 board. I double checked it by connecting to different computers, and it always has two COM port numbers. I'm not sure which one should I use in the PuTTY Serial line selection. I also tried both COM4 and COM8, but don't have it work yet. 

The session config is as below.

I'll appreciate it if you could review the PuTTY config and let me know whether I should change anything or if you have other suggested action to try.

  • +1

    Hi,

    From your first and last pictures it looks like your are trying to connect via RTT instead of UART. In the 'Session' settings in PuTTY you should select 'Serial', and not 'Telnet', and then add COM port and the baud rate there:

    Best regards,

    Marte

  • 0 in reply to user92402

    Hi Marte,

    Thanks a lot for your instruction. Now I can connect without any error. While I cannot get any return when typing CLI commands. Also should I expect something like board connected successfully?

    Below are my setting details. The rest pages are using default settings but let me know if you need those info.

    Do you have any suggestion? Looking forward to your reply!

  • 0 in reply to user116200

    Hi,

    The settings seem correct. In the guide the settings for local echo and local line editing are auto instead of force on, but it should still work.

    cindy66666 said:
    Also should I expect something like board connected successfully?

    Not from PuTTY, no. You will get an error if you are trying to connect to a COM port that is not in use, but by looking at your picture the connection has been opened correctly. The radio test example should print the text "Radio test example started" at the beginning though. You can try pressing the reset button on your DK after you have established the connection in PuTTY and see if it prints when it starts up.

    You also mentioned that you are unsure which COM port is correct, since both COM4 and COM8 shows up. One thing you can do to find this is to run the command nrfjprog --com. This will show connected JLink debuggers and their associated serial ports. The debugger will show up as the serial number of your DK.

    Best regards,

    Marte

  • 0 in reply to user92402

    Hi Marte,

    After pressing reset I was able to see the text and communicate with the board. I guess previously the board was somehow not responding.

Related
Terms of service