Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updating numbered headings
Table of Contents
stylenone

1. Identifying Development Kits and Serial Ports

  1. Usenrfutil to list all connected development kits, their serial numbers and associated serial ports:

    Code Block
    $ nrfutil device list
    1050021575
    product         J-Link
    board version   PCA10095
    ports           /dev/ttyACM2, vcom: 0
                    /dev/ttyACM3, vcom: 1
    traits          devkit, jlink, seggerUsb, serialPorts, usb
    1050931892
    product         J-Link
    board version   PCA10153
    ports           /dev/ttyACM0, vcom: 0
                    /dev/ttyACM1, vcom: 1
    traits          boardController, devkit, jlink, modem, seggerUsb, serialPorts, usb
    Found 2 supported device(s)
    
  2. Use nrfutil to identify the specific devices:

    Code Block
    $ nrfutil device device-info --serial-number 1050931892
    serial_number: 001050931892
    	boardVersion: PCA10153
    	deviceFamily: NRF91_FAMILY
    	deviceVersion: NRF9161_xxAA_REV3
    	jlinkObFirmwareVersion: J-Link OB-nRF5340-NordicSemi compiled Apr 11 2024 17:44:26
    	protectionStatus: NRFDL_PROTECTION_STATUS_NONE
    $ nrfutil device device-info --serial-number 1050021575
    serial_number: 001050021575
    	boardVersion: PCA10095
    	deviceFamily: NRF53_FAMILY
    	deviceVersion: NRF5340_xxAA_ENGD
    	jlinkObFirmwareVersion: J-Link OB-nRF5340-NordicSemi compiled Apr 11 2024 17:44:26
    	protectionStatus: NRFDL_PROTECTION_STATUS_NONE

2. nRF9161-DK Serial Ports

Two USB ACM devices are detected by the Linux host when the nRF9161 DK is connected. They can be identified using nrfutil or dmesg:

...

Code Block
picocom -b 115200 /dev/ttyACM0

3. nRF5340-DK Serial Ports

Two USB ACM devices are detected by the Linux host when nRF5340 DK is connected:

...

Code Block
picocom -b 115200 <vcom: 0 port>

4. Serial Console of the nRF9161

After the Thingy-9151-Lite application image is programmed to the target board, reset the board and observe the Zephyr banner and shell on the serial console:

Code Block
*** Booting nRF Connect SDK v2.5.1-4-g0eb43b6d9219 ***
...
uart:~$

5. Serial Console of the nRF5340 Application Core

After the Thingy-9151-Lite application image is programmed to the target board, reset the board and observe the Zephyr banner and shell on the serial console:

Code Block
*** Booting nRF Connect SDK v2.5.1-4-g0eb43b6d9219 ***
...
uart:~$

6. Serial Console of the nRF5340 Network Core

After the Thingy-9151-Lite application image is programmed to the target board, reset the board and observe the Zephyr banner on the serial console:

...

The nRF5340 Network Core application only provides logging output to the console, as the Zephyr shell is disabled in the project configuration.

7. Zephyr Shell

Most of the standard Zephyr shell features are available, such as auto-completion, command history, etc.

...