Jetson AGX ORIN DevKit USB Problems

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
, ,
1

I am using Jetson AGX ORIN DevKit and my problem is similar to the one discussed here. I tried to follow what was suggested in there but no luck. Here is the output of dmesg --follow,

[  851.290173] systemd-journald[14071]: Received client request to flush runtime journal.
[  891.940611] usb 1-4.2: USB disconnect, device number 5
[  895.507962] usb 1-4.2: new full-speed USB device number 6 using tegra-xusb
[  895.592006] usb 1-4.2: device descriptor read/64, error -32
[  895.783996] usb 1-4.2: device descriptor read/64, error -32
[  897.291902] usb 1-4.2: new full-speed USB device number 8 using tegra-xusb
[  897.403267] usb 1-4.2: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[  897.403273] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  897.403276] usb 1-4.2: Product: u-blox GNSS receiver
[  897.403278] usb 1-4.2: Manufacturer: u-blox AG - www.u-blox.com
[  897.405563] cdc_acm 1-4.2:1.0: ttyACM0: USB ACM device
[ 1430.820577] usb 1-4.2: USB disconnect, device number 8
[ 1862.037656] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call result 0xffff:
[ 1862.108776] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call result 0xffff:
[ 1887.768911] usb 1-4.2: new full-speed USB device number 9 using tegra-xusb
[ 1887.884270] usb 1-4.2: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[ 1887.884278] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1887.884281] usb 1-4.2: Product: u-blox GNSS receiver
[ 1887.884283] usb 1-4.2: Manufacturer: u-blox AG - www.u-blox.com
[ 1887.886581] cdc_acm 1-4.2:1.0: ttyACM0: USB ACM device

Basically, when I open the GPS Serial port (connected to USB-A) from the ROS Node, or picocom, or minicom etc. Ofcourse, not simultaneously, it opens fine and if closed. The port won’t open again. The dmesg --follow also showed no change when the serial port was closed and re-opened.

I also tried to use the USB-C but it wouldn’t provide the necessary power to turn on the GPS module. I tried powering the GPS board separately and then connnected via USB-C to the ORIN. The port won’t even be detected. I tried both the USB-C ports.

Any suggestions or help will be appreciated. Thanks.

2

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks

4

Unfortunately no luck still. Need more support on this.

5

Hi,
From the log,it looks like the power supply is not stable. When it is enumerated, it is disconnected since power supply is not enough. Would suggest check if you can give external power supply to the GPS module.

6

Thanks for the response. Let me explain it more clearly what the logs are here based on the connection,

  1. Ublox gps was connected. You can see the connection in the log.

  2. I open the picocom and close the port. No behavior is shown in the log.

  3. I unplug the gps module and connect it back again. That is what is seen in the logs.

In short, I disconnected the gps once it was connected to see the behavior in the logs. Hope it further clearifies the issue.

I have tried what you suggested. It didn’t work as expected, unfortunately.

7

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

8

FYI, whenever it shows the following, then the device special file used to talk to serial devices should exist:

However, that device may be numbered differently after unplug/replug (it might still be ttyACM0, but it also might increment to ttyACM1).

As mentioned earlier, power supply issues are common related to this. What happens is that as a USB device starts consuming more power, it may not be enough and the device might disconnect (and perhaps reconnect automatically, with or without a device special file number increment). What you would need to do is to provide (A) a full serial console boot log from the start with the device connected, and (B), assuming there was some error, run “dmesg --follow”, and show only the log lines which occur as a result of unplug and replug of the device. Quite often, when testing for power issues, one can use an externally powered USB HUB to isolate power delivery to something external (versus supply from the Jetson) and eliminate power delivery as an issue.

10

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