I have a Jetson TX2 with an Orbitty carrier board. I had set a patched DTB from Jetson/TX2 USB - eLinux.org to make USB work, and it does.
However, on USB 3.0 port, only some devices, like an USB 3.0 hub or flash drive, are properly registered, while others don’t register when plugged (there’s nothing in dmesg or lsusb).
I checked the voltage while those non-working devices were plugged and it was normal (about 5V), so it doesn’t look like a power issue. What could be the problem?
Edit:
I made an USB cable extension cable that powers with 5V separately form a 5v power adapter and with it suddenly the devices started working. So it does seem like a power issue. I wonder if it might be something with the DTB/DTS settings.
I’ve never looked at how the device tree relates to power delivery, but USB3 does have higher power delivery current than does USB2. If…and I don’t know about this case…the device tree has to be changed to also provide USB3 standards of current limits, then it is possible your USB3 is set to limit at USB2 currents…in which case a USB3 device approaching USB3 limits would fail to get the current it requires.
Anyone know if device tree has any influence over the current limit on the USB power delivery rail?
I highly recommend making sure that all code you write on the module is pushed to a source repository, and that all the data you store on the module is synced (copied) to some other system (such as the host) regularly.
“Fear of losing data” should never be a thing; if it is, that’s a signal you need to step up your data management process!
When using the TX2 module with a Connect Tech carrier you will require our BSP to be installed. You will need to re-flash your module with our BSP, instructions can be found in the links below. This will fix you USB issue.
You will require the latest CTI BSP, Jetpack3.0 and Ubuntu 14.04.1 when flashing the TX2 module.
@Snarky: We do have our software under a revision system, but we have tons of software installed and would have to reinstall again after a full reflash, so I wanted to avoid that.
@cnoble-cti: Thanks, that worked overall.
However I now have a small issue remaining. My camera works perfectly in 3.0 mode when I plug it in after booting the TX2+Orbitty. However, when I boot with the camera already plugged in, it seems detected but I can’t read image from it. Do you happen to know what could be the issue?
How did you manage to flash the CTI BSP into the board without erasing the existing files?
I have an orbitty one on a TX2, and tried to install the BSP first then to flash the tegra linux it didnt work then I tried the other way (tegra then the BSP). Each time the previous image was erased by the new without my peripherical working.
@CocoChannel2:
I unpacked Tegra186_Linux_R27.1.0_aarch64.tbz2, changed the name to Linux_for_Tegra_tx2, unpacked CTI-L4T-V103.tgz inside of it, ran install.sh script. I made a backup of system partition on my TX2 (see: Jetson/TX2 Cloning - eLinux.org), which should be saved in bootloader/system.img, and then flashed with ./flash.sh -r orbitty mmcblk0p1. After flashing, I copied files from rootfs directory to my jetson via scp (watch out for file permissions).