Jetson-io.py doesn't work on my Jetson Orin Nano

I am trying to use jetson-io.py to enable cameras and PWM on my Jetson Orin Nano, but when I run it, a gray intarface appeares for a moment and dissappears immediately. I have tried different ways to resolve the issue, but none of them work.
Below is a list of the methods I have tried:
-Ran the command sudo /opt/nvidia/jetson-io/jetson-io.py
-Navigated to the directory first with opt/nvidia/jetson-io, then run jetson-io.py
-sudo apt upgrade
-sudo apt update
-Uninstalled Jetson.Gpio version “2.1.7” and downgraded to version “2.1.6”
-Used dpkg-query -l |grep jetson-io to verify that jetson-io is installed
-Wrote a script to test the curses library, and it ran successfully
-Ran the command ls /boot/dtb and received the output kernel_tegra234-p3767-0003-p3768-0000-a0.dtb

I suspect there might be a problem related to the JetsonIO class in jetson-io.p, but I haven’t found more information about it.

Hi niklot47,

Do you have any screenshot or image for this behavior?
Or any error messages?

Are you using the devkit or custom board for Orin Nano?
What’s your Jetpack version in use?

Hi KevinFFF,

I am using the Devkit for the Orin Nano (Jetpack 5.1.3, Jetson.Gpio 2.1.7, python 3.8). When I run the script, a part of the UI briefly appears in the terminal for about a second — it’s a frame made of white characters on a gray background. There is no text inside it.

Example of what I see:


| |
| |

There are no error messages in the terminal by default. However, I modified the script to save errors to a file, and this is what I got:

No APP_b partition found!

Could you help me understand what might be causing this issue?

I would suggest using the latest JP5.1.4(R35.6.0) or JP6.1(R36.4.0) to verify.

Do you enable rootfs redundancy on your board?

Please share the result of the following command for further check.

$ cat /etc/nv_boot_control.conf
$ sudo nvbootctrl -t rootfs dump-slots-info

We are already using JetPack 5.1.4; apologies for the confusion.
I definitely did not enable rootfs redundancy before.

cat /etc/nv_boot_control.conf

TNSPEC 3767-300-0005-R.1.1-0-jetson-orln-nano-devkit-
COMPATIBLE_SPEC 3767–0005–1–jetson-orln-nano-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk1
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

sudo nvbootctrl -t rootfs dump-slots-info

RootFS A/B is not enabled.

It seems you are using Orin Nano devkit(SKU5).
Are you using SD as rootfs or you’ve also connected NVMe SSD?

Since we can not reproduce the similar behavior on the devkit, could you share the detailed steps how do you flash the devkit?

We are using only an SD card as the rootfs. We followed this guide get_started_jetson except for the “Update the Firmware” step, as it was not needed in our case.

Could you try to get an Ubuntu host PC and use SDK manager to flash JP5.1.4 and check if Jetson-IO can work on your devkit?

We tried using a host PC with Ubuntu 22.04 and JP6.1 installed on an NVme. Jetson-IO still does not work. There are no prints or errors in the terminal; it simply does not launch.

We need to control two stepper motors (2 pins with PWM), 2 cameras CSI, and also connect a module via I2C to read data from an analog sensor. Is there a way without Jetson-IO?

sudo /opt/nvidia/jetson-io/jetson-io.py

You can also refer to Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation to configure them in pinmux spreadsheet instead of using Jetson-IO.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.