USB-C Does not work on runtime, meaning no SSH with USB-mode

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

I’m aware that this issue is probably related more with the carrier board than with the Jetson, but I don’t know how to properly debug the issue.

I’m using the seed-studio carrier board for my Orin NX 8Gb

I can flash it normally and succesfully.

The only issue that I have is that after the USB-C doesn’t seem to work.
Usually with other boards and with a Xavier NX when I connect a USB-C cable to the board and to my computer I get assigned an IP, this doesn’t happen now with the Orin and that board.

With dmesg I don’t see anything appear or disappear when I plug or unplug the USB-C cable

Any suggestions on how to debug this issue would be highly appreciated.

2

Does the vendor provide their own BSP for their board to flash?

Generally the devkit BSP cannot fully work on custom board unless the board vendor claims it.

3

The vendor claims that the devkit BSP should work, in fact in their installation examples that’s what they used.
No extra files are provided

4

Did the BSP ever work on your board before? I mean if this issue is suddenly happened, then it is more like a hardware issue.

5

No, not suddenly. Everything works, apart from the USB-C when in running mode. I was just wondering if there was any steps I could do to kind of check what is going on

6

I am curious, what do you see from:
systemctl list-units | egrep 'nv-l4t'

7

Please start from sharing dmesg first. I will use the way to check Orin Nano devkit to check your log first.

8

$ systemctl list-units | egrep ‘nv-l4t’

nv-l4t-usb-device-mode.service loaded active exited Configure USB flashing port for device mode

9

dmesg logs with usb-c connected
dmesg_usb.txt (66.0 KB)

10

What do you see from:
systemctl status nv-l4t-usb-device-mode.service

11

I directly saw fusb301 driver fails to probe. Without this, for Orin NX/Nano devkit, the type C port won’t work.

[   12.377670] fusb301 1-0025: failed to read device id, err : 0xffffff87
[   12.429093] fusb301 1-0025: fusb301 not support
[   12.493147] fusb301: probe of 1-0025 failed with error -22
12

Could you expand a bit on this answer? Is this an hardware/carrierboard issue? Or is some driver missing?
How can the usb-c works to the flashing procedure, but then not work after flashed?

13

Hi,

  1. I already told. There is no answer from us because you are using a custom board. Why this fusb driver cannot work could be hardware or carrier board issue. The driver is not missing as the driver just ran and printed above log.

  2. Could you share the flash log and command you are using for flash so that I can tell how your usb-c work during flash?

14

FYI, you need a driver, and the less obvious part is that the driver must be able to find the hardware. Since the internal components are not plug-n-play, this means firmware (the device tree) must tell the driver everything it needs to talk to the USB hub chips. This is done with the device tree, and a third party carrier board will route lanes differently, and perhaps use different peripherals. Third party carrier board manufacturers provide that content. If you are building your own carrier board, then you would need to update the device tree.

15

Thanks for the support. It seems is more likely a problem with the carrier board. I have reached out to them and I am waiting for an answer. Thanks again

16

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