Cannot open connection to nRF52840 while using PUTTY or terminal emulator of SES

[Bo Chen]

Hi,

I'm a new guy for the development in nRF52840 and try to build the application by using 802.15.4. I have two questions, as follows:

Firstly, when I follow the instruction of Wireless UART Example (https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v14.0.0%2Fwireless_uart_15_4.html). I find that I cannot open the connection via PUTTY: there is no response when I configure all options in the instruction and click the "open" button. In fact, when I try to use putty in windows 10 to open the connection, there is a error: "Unable to open connection to COM1, unable to open serial port". I try to use Segger Embedded Studio (www.novelbits.io/.../): build the project, and start debugging. I can see the output in debug terminal: "<info> app: Wireless UART example started." However, when I try to type something in debug terminal, I cannot see any output in other computer's debug terminal (use "second" example in SDK with the my second board). I'm not sure whether the debug terminal has the same function of putty or not. Therefore, I also try to use the terminal emulator provided by SES to open the connection. But also failed with error: cannot open serial link `COM1` (messy code error in ubuntu). I believe I use the right serial port ("/dev/ttyACM0") and open putty with "sudo". I also try to copy the .hex file directly into JLINK volume of the board and try another USB port. But no different response. My platform details as follows: 

Ubuntu 18.04 LTS (Windows 10 for second PC); nRF SDK: 15.2.0; SES: ARM 4.10a; PUTTY: 0.7.0

Secondly, is there any more simple example that can tell us how to use 802.15.4 API in SDK? "Wireless UART Example" seems too complicated and I cannot see how to send and receive the packets by using 802.15.4 in it. I also search the API document of SDK and find it was too difficult to find the simple send/receive packets function or related high level function. Is there any function provided just like the example in "nrf-IEEE-802.15.4-ratio-driver"? Or, do you have any suggestions in this?

Really need your help. Thanks a lot!

Yours sincerely,

Bo Chen

[AndreasF]

Hi Bo Chen.

"Unable to open connection to COM1, unable to open serial port"

 Have you checked in your Device Manager that this is the correct COM port?

Best regards,

Andreas

[Bo Chen]

I pull out the board and insert the board again, to see the change of the port in both windows and ubuntu. Pretty sure I use the right port.

[AndreasF]

Hi.

The error says unable to open the connection to COM1, so this you have to be sure that COM1 is the right COM-port

I just tried the precompiled .hex files on two of my nRF52840 DK's, and it worked well.

And the LED's worked as intended in the tutorial.

Did you check in Device Manager that you actually are using COM1?

Like this:

I have used COM22 and COM7, as these are the COM ports Windows assigned to my development kits.

My PuTTY setup for the two development kits:

Best regards.

Andreas

[Bo Chen]

Really thanks for your reply. I will attach the screen shot and details of my operating process as follow:

First, I use SES to open the example under SDK folder and get the output .hex file as follows:

As you can see from next figure, I can debug the application via SES:

Then, I quit debugger mode and copy the corresponding .hex file into the board (I also try the .elf file):

file here:

copy to there:

Then, the JLINK will automatically vanish from the file explore and show again. I open the JLINK and I won't see the .hex file anymore. I think that proved the copy is successful. So, I start to use putty to connect to the board. First, I check the device management and find the port:

Obviously, this computer I used only have one port. Then I open putty and configure the options as follows:

Now, I try to click "open" button. But there is no response but only a sound from my PC (means error?). That's all of the process and my operations. I still cannot run the example. Hope you can analyze the process and see the problem. Thanks very much! 

Best 

Bo

[AndreasF]

Hi.

Can you try with a different terminal? For example Termite

Here is how I did it:

I don't think that any thing you do prior to trying to open the COM port should affect your chance of opening the COM port.

Best regards.

Andreas