Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

RE: Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

HeneryH — Wed, 23 Feb 2022 14:43:24 GMT

RTT worked but I needed two settings in the prj file.

Thank you

CONFIG_SHELL_BACKEND_RTT=y
CONFIG_USE_SEGGER_RTT=y

RE: Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

HeneryH — Wed, 23 Feb 2022 13:56:47 GMT

Ah, on the RTT viewer, I saw this warning in the log.

warning: SHELL_BACKEND_RTT (defined at c:\Users\jjfly\nrf_apps\v1_9\openthread_cli\Adafruit_Feather_nrf52840\subsys\shell\backends\Kconfig.backends:122) was assigned the value 'y' but got the value 'n'.

I'll investigate.

RE: Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

HeneryH — Wed, 23 Feb 2022 13:32:15 GMT

I just built it again from scratch from sample and only added that single new line to the prj.cfg file. Same behavior.

I'll try adding the USB overlay to the project to see if I can get it that way. [maybe a better way at the end of this post]

The problem I am trying to solve is figuring out how to get the eui64 for any device? Maybe there is a better way of determining that data value?

If I have a bunch of devices I want to deploy to the field, I need to generate join qr codes for each of them. Maybe flash it with CLI, determine the eui64, then reflash with the desired project?

RE: Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

Jørgen Holmefjord — Wed, 23 Feb 2022 10:50:45 GMT

Hi,

Did you make any other modifications to the config of the coap_client example? I got the log and CLI on RTT from adding this single config. Did you build for the feather target, or for the nrf52840dk board? Also, you should select "nRF52840_XXAA" in RTT viewer when connecting, the other settings looks correct.

[quote user="HeneryH"]When I connect that USB port to the win11 machine I do not get any serial ports detected like I do when I connect any of the DKs.[/quote]

This is normal if the firmware running on the nRF52840 does not initialize the USB peripheral. You can check if the USB port works by building the OpenThread CLI sample with usb-overlay configuration and build it for the 'nrf52840dongle_nrf52840' target. This should use the native USB port of the nRF52840 for the shell transport.

Best regards,
Jørgen

RE: Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

HeneryH — Tue, 22 Feb 2022 14:56:51 GMT

Thank you Jørgen. I will try these options.

The schematic for the Adafruit Feather nrf52840 Express does seem to show the SoC D+/D- being routed off the module and to the microusb connector with just some resitstors inline.

When I connect that USB port to the win11 machine I do not get any serial ports detected like I do when I connect any of the DKs.

I am trying the Backend RTT method now. I rebuilt the config with your suggested config item.

Connecting with J-Link RTT Viewer I get the following. I will investigate further and try the alternate methods. FYI, J-Link RTT Viewer prompted me for a fw update. I tried both with the same result.

RE: Zephyr Console on Adafruit Feather nrf52840 connected via SWD to nrf52840dk

Jørgen Holmefjord — Tue, 22 Feb 2022 14:05:00 GMT

Hi,

I assume you are referring to the "ot eui64" command? I could not find any commands named "ot eiud".

There is no UART interface available through the debug connector. You will either have to use the SWD interface, or the UART interface of the Adafruit Feather nRF52840 Express externally through a UART-to-USB adapter.

It is possible to enable RTT support for the Shell, by setting "CONFIG_SHELL_BACKEND_RTT=y" in your prj.conf file. You can then send the shell commands from an RTT client, like J-Link RTT Viewer (Enable: "Input->Sending...->Send on Enter for erase of reading):

Depending on which target you built for when building the firmware for the Feather, the UART will be available on some of the GPIOs of the board. You can connect the UART TX/RX pins to an UART-to-USB cable, or to P0.06/P0.08 pins of an (erased) nRF52840 DK, which will allow you to use the Virtual COM port functionality.

One final option is to use the USB port of the Feather. It looks from the schematics as this is connected directly to the native USB port of the nRF52840, which means you will have to enable USB support in the application. I can't find any simple configs to enable USB CDC ACM support for the shell, but you may be able to achieve it following the procedure described in this thread.

Finally, the EUI64 is by default generated from Nordic's MA-L + the random number stored in FICR->DEVICEID[n] registers. You can read it out using nrfjprog:

Best regards,
Jørgen