RE: Problem with nRF53dk Thread CLI example and some feedback

Sigurd Hellesvik — Fri, 20 Aug 2021 11:42:39 GMT

Hi Peter

Thank you or the feedback, I will address it in short, then go on to answering your questions.

[quote user=""]

Downloaded nRF Connect, installed the Toolchain Manager. Installed nRF Connect SDK v1.6.1, changed the path to my own liking (D:\Program Files\NordicSemiconductor).

When trying to compile the Thread CLI example I get the following error "create_nordic_project.py failed (1)" looking at the output it looks like part of the script can't handle the space in "Program Files".

[/quote]

The nRF Connect SDK Toolchain cannot be located in a path containing space(" "). This should probably be a warning message before you choose a path. I will suggest it to the developers.

[quote user=""]

Uninstalling and reinstalling nRF Connect SDK v1.6.1 to a new path (D:\Program\NordicSemi).

Trying a new to compile the Thread CLI example, now it can't compile a crypto something file.. reading on the web and looking at the whole path, it is too long, something like 274 chars (where I've given around 25 of them..).

[/quote]

This is a known issue. As far as I know, it is due to a limitation in windows, and not the nRF Connect SDK.

[quote user=""]

Once again reinstalled nRF Connect SDK v1.6.1 to a new path (C:\N), it now compiles and builds the example. I'm following the "Developing Thread Products using nRF Connect SDK". Suddenly the tutorial author has two PuTTY consoles open connected to the nRF. When I plug the DK into my computer I get three COM-ports, and none if I plug it into the “nRF USB”-connector.. and no PuTTY connection information. After some trial and error and looking at the web I get it right.

[/quote]

For the three TTY ports, see Q2(below). The nRF USB(J3) connector connects (almost) directly to the nRF, while the J2 USB Connects to the PCA10095 - Interface MCU. By default, debugging UART and goes trough the J2 USB connector. I believe this is the default connector used in most tutorials as well.

[quote user=""]

When I boot my DK I get a “uart” prompt on my comport I can communicate with the DK and I can see a “ot” command in the list of commands. When I try for example “ot help” it freezes, nothing happens, and I must reboot my DK. I thought this example should work out of the box? I.e. I have done nothing to the code (following the "Developing Thread Products using nRF Connect SDK" youtube video).

[/quote]

The tutorial would have worked fine for the nRF52840, but there is an extra step you need to do for the nRF5340.

The nRF5340 has two different cores. One network core and one application core. To use thread, the application running on the application will use the network core for thread or multi protocol communication. Your network core is likely empty, and when the "ot help" command tries to communicate with the network core, the program freezes.

To fix this, follow the Working with nRF53 Series howto on Using SEGGER Embedded Studio.
When you get to the part where you need to program the network core, see either IEEE 802.15.4 (Thread and Zigbee) or Multiprotocol (Thread or Zigbee in combination with Bluetooth LE).

[quote user=""]

What are the othe two COM-ports for? If I remember correctly the first time I plugged the DK in COM3 (the others were COM4 and COM5) was the working one, last time it was COM5 that was working.

[/quote]

The three different COM-ports are explained in the Getting logging output section.

I hope this was helpful, please let me know if anything is still unclear or you have more questions.

Regards,
Sigurd Hellesvik