I’ve flashed my TX1 with J120 carrier board, the top connector USB port works well, but nothing can be detected on the lower connector of USB port of J2.
lsusb shows below (keyboard/mouse receiver on top USB connector when lsusb below):
nvidia@tegra-ubuntu:~$ lsusb
Bus 002 Device 002: ID 0955:09ff NVidia Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 029: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvidia@tegra-ubuntu:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-tegra/4p, 5000M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-tegra/5p, 480M
|__ Port 3: Dev 29, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 29, If 1, Class=Human Interface Device, Driver=usbhid, 12M
The USB3 device on “Bus 02.Port 1” is LAN controller. I chose to use LAN instead of wifi on J120 as I don’t have a place to connect the wifi antena. Does this matter?
Any clue why the lower USB connector doesn’t work?
I have no experience with Auvidea boards, but each carrier board requires its own separate board support package. Have you used the BSP for that specific board from Auvidea (a custom device tree is a major component of any BSP)?
Until today, Auvidea hasn’t published updated kernel patch/dtb updates for TX1 on top of J120 board to support L4T R28.*, the latest one they support is as below.
Date Product Version Description
Jan. 2018 J100/J106/J120/J130/J140 firmware (kernel and patches) 2.3 supports: Jetson TX1 only (L4T 24.2.1)
The R24.x L4T is a kernel 3.x series, while R27.x+ L4T is a kernel 4.x series, so the two will have some incompatibilities (depending on how drivers have changed).
Other than waiting for Auvidea to release the changes I don’t have any easy answer for you. Assuming you are attempting this yourself, then a comparison of the 3.x kernel device tree USB sections of the stock dev kit R24.2.1 tree with Auvidea’s tree it might give some hints for where edits are needed, but then you would have to figure out how that translates to a 4.x kernel. You could compare the stock dev kit’s USB tree of R24.2.1 with R28.2.1 just to see how going from a 3.x kernel to 4.x kernel changes things, and then try to merge the 3.x kernel device tree Auvidea changes into the newer 4.x kernel device tree.
If you take this route be sure to use the correct device tree flash procedures since this is no longer a simple file.