AGX Orin 64GB jetpack6 cannot detect USB devices, GPIO pin cannot detect UART devices

Hi Nvidia,

I am using jetpack6.0 in AGX Orin 64GB developer version. When I plug in the xbox joystick, the Orin cannot detect it. Also when I use the GPIO pin of the Orin to connect an IMU with UART port, the Orin also cannot detect it. I have checked dmesg log, it doesn’t show any new connection for both the joystick and the IMU. Things worked on jetpack5.1.1 .Please take a look.

Hi xjh4438318846,

Could you share the details of your connection?
Are you using UART or GPIO interface for IMU? Which pins are you using?

Have you also verified with the latest JP6.1?

yes, jetpack6.1 installed by SDK manager also doesn’t work. The joystock is connected by usb port, lsusb can see the device, but I cannot see /dev/js0, so I cannot launch it by ros2 joystick driver. The aUasrt ports I am using are UART1_TX and Uart1_RX, I use pin1 and pin6 as power and ground.

Is this still an issue to support? Any result can be shared?

I haven’t managed to solve this problem. For now, my team chose to use remote controller sending cmds through ros2 to the robot.

Is there any error in dmesg when you load the custom joystick driver?

Could you share the block diagram of your connection?
Sorry that I’m not clear about if your device is controlled by USB or UART or both?
It seems IMU is connected through UART and Joystick is connected through USB.
Is my understanding correct?

Don’t worry about the IMU, we don’t use it anymore. We care more about the USB port, which directly connects to the joystick. To run the ros2 joystick driver, I need to see /dev/joy0 but I cannot see it after I connect the xbox joystick. The light of the xbox is on, so I am not sure why this issue happens

Okay, let’s focus on USB.

If the node is not appear, it may be caused from the driver probe failed.
Is there any error when your plug the joystick or probing the driver?
Please share the full dmesg for further check.

here is the log, I only connected one USB(jooystick port), I hope to see /dev/input/js0 in th Orin
dmesg.log (59.8 KB)

[  607.234233] tegra-xusb 3610000.usb: Firmware timestamp: 2023-02-10 03:48:10 UTC
[  607.576781] usb 1-4.2: new full-speed USB device number 3 using tegra-xusb

Is it the time when you connect USB joystick?

What’s the driver for your joystick?
Please also share the result of lsusb before and after you plug USB joystick.

before:

jiahe@ubuntu:~$ lsusb
Bus 002 Device 002: ID 0bda:0420 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:5420 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

after:
jiahe@ubuntu:~$ lsusb

Bus 002 Device 002: ID 0bda:0420 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 2f24:00b7    ESM GAME FOR WINDOWS 1.05
Bus 001 Device 002: ID 0bda:5420 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

time:jiahe@ubuntu:~$ date Tue Dec 10 10:20:19 AM EST 2024

new dmesg.log:
dmesg.log (76.2 KB)

it should be a ros-humble-joy driver

It seems AGX Orin can detect your USB device.
I would suggest you requesting the vendor for the detailed steps to setup the joystick.

Have you run the following command to install ros-humble-joy?

$ sudo apt-get install ros-humble-joy

It seems you should refer to the instructions in joy/Tutorials/ConfiguringALinuxJoystick - ROS Wiki.

yes, it’s jetpack6 ubuntu22.04 so the cmd is correct, and after I installed that package, I should be about to see the /dev/input/js0, but I cannot

Do you reboot the board to check if it could help?
Have you run $ sudo lsmond|grep js to check the the module is loaded?

Since it is custom device and driver, we don’t have the module and related joystick to verify it locally.
We would still suggest you asking the help from your vendor. They may know how to setup for this device.

sudo lsmod | grep js

has no output

It seems your driver is not probed at all.

Could you compare the log when it can work with JP5.1.1?

And also check if there’re some related kernel configa are enabled in JP5.1.1 but disabled in JP6.0.

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