I am having difficulties connecting USB devices to my Jetson. I recently downgraded Jetpack to version 4.5.1 since later tegra versions were incompatible with librealsense. USB ports were initially functional but now I can’t connect anything. Is there any solution short of re-flashing the micro sd entirely? Below are my dmesg logs. I believe the issue is something to do with rndis0 and usb0 entering disabled mode, but I haven’t found any source of the issue.
dmesg_logs.txt (63.1 KB)
Hi,
What is going to be tested exactly? Your usecase seems to be realsense but you are tasking about device mode.
Are those ports running in host mode still working fine?
I’m not quite sure what you are referring to. Did I switch from host mode to device mode on the Jetson, and if so, how do I reverse this?
Sorry, are you talking about you didn’t know what your first comment revealed?
I recently downgraded Jetpack to version 4.5.1 since later tegra versions were incompatible with librealsense
As librealsense is for realsense camera, I guess you want to use usb camera on jetson, right? If so, then it should be host mode on jetson usb.
I believe the issue is something to do with rndis0 and usb0 entering disabled mode,
rndis0 and usb0 here are for device mode. So this does not matter with usb host mode.
Which means it should not be related to realsense here.
That is why I would like to understand what is the exact use case.
BTW, I am not providing any solution yet. I am just trying to figure out what you are doing.
If you just want to reflash the board, then just run sdkmaanger and it will flash the board.
please also tell me if you are using nv devkit or custom carrier board.
I am using the nvidia devkit board. I’m still fairly new to developing on the jetson; I only mentioned the rndis0 and usb0 because they seemed like the only things that could have caused an issue. If those are completely unrelated, is there anything in the logs that would cause an issue or do you suspect this to just be a physical issue with the ports?
You can do some basic checks first
→ Please plug any kind of usb device to the usb type A port on your devkit. It could be keyboard or mouse. Simple device should be okay.
After you plug in the device, check your dmesg if anything new got printed.
If nothing gets printed, then flash your board to latest jp4.6.3 and see if your usb could get detected or not. If this is really a hardware issue, then changing the software version won’t bring it back.
One unrelated question to usb, is the monitor you connect to the board going through any kind of adapter? I just feel it is weird to see those I2C timeout error in your dmesg from a NV devkit.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.