Try to run the Openthread CLI Sample on nrf5340 DK but I can't get any feedback via Putty

[kakadua]

Hi, I'm trying to run the Openthread Cli sample on my nrf5340 DK, and it looks like that part is doing fine. But if I want to test the thread network with Putty I don't get any feedback from it. I already tried the 3 different COM ports and with and without different Control Flow Mechanism, but the only feedback I get is this:

 

In the https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/openthread/cli/README.html documentation, there has to be any feedback like this:

I did as well looked for any configuration but I can't find the sdkconfig.h file in SEGGER

I hope you could help me with this problem and because I'm a beginner every piece of advice is welcome! and thanks in advance!

[Øivind]

Hi,

It seems to work fine for me.

Have you doublechecked that PuTTY is setup correctly? As described in this page: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_testing.html

In terminal options: Implicit CR, Implicit LF, Local echo force on, local line editing force on.

In serial options: Correct COM port, Speed 115200, data bits 8, stop bits 1, parity none, flow control none.

[kakadua]

Thanks for the fast response!

Yes, I do have the correct setup or do I have overlooked something:

  

From the 3 COM ports, I choose the middle one because it's the only one responding with the "uart:~$"

Btw, my connection with my nrf 5340 dk is with just a 2.0 USB cable

[Øivind]

Have you changed anything in the SDK? Can you run a git status in the nrf, zephyr and modules/lib/openthread folders?

Do you get any warnings when you build the CLI sample?

Can you try using a different usb cable / different usb port?

[kakadua]

For the first question I did not change anything that I know, and I got these results:


No I dont have any warnings from SEGGER, but from the Openthread Cli example I got a hex file to upload and not a elf file.

I didn't change the port but will try now if that works, (I dont have any other 2.0 USB Cable)

(UPDATE:)
Got the same result with other ports

[Øivind]

Can you zip the build folder and attach it here using Insert->Image/video/file?

[kakadua]

Build dir for Hello world
build_nrf5340dk_nrf5340_cpuapp.zip

Build dir for Openthread Cli
build_nrf5340dk_nrf5340_cpuapp_cli.zip

(UPDATE:)

Are those the good ones?

[Øivind]

Ok, I don't see anything wrong with the build folder. But I was able to reproduce the issue when I swapped between SDK versions, and I was able to fix it.

Can you try building and flashing zephyr/samples/bluetooth/hci_rpmsg? Build for nrf5340dk_nrf5340_cpunet.

Then build nrf/samples/openthread/cli for nrf5340dk_nrf5340_cpuapp and flash that.

Make sure to delete any pre-existing build folders.

[kakadua]

sorry for the late answer but it still doesn't work: I got this error when flashing the openthread cli:

 

and this error when flashing the hci_rpmsg:

[Øivind]

In the command line, run these two commands:

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover

Then flash hci_rpmsg for cpunet, then try again.

[kakadua]

The flashing does work but I got now a different error when I use putty, 

[Øivind]

I'm sorry, you should flash zephyr/samples/boards/nrf/ieee802154/802154_rpmsg to cpunet.

That should fix the issues. You may have to run the recover again first.