partial success with custom rootfs, boots but not network interface and usb comes up late

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX1
1

Good evening,

Trying to build a custom root filesystem for the Jetson TX1. I use an ubuntu base rootfs (16.04.5) and used the apply_binaries.sh. resulting files have been written to a SD Card and my TX1 boots with this new filesystem.

I have several issues I can’t fix after a intensive web search, I guess all coming from the same root problem. The boot starts and looks okay. But, USB comes ready approx 60 secs after boot, after a series of console message like :

[ 65.xx] xhci-tegra 7009000.xusb: cannot find firmware… retry after 1 second
…
…
[ 65.xx] r8152 2-1:1.0 eth0: v2.09.00 (2017/08/21)
[ 65.xx] r8152 2-1:1.0 eth0: This product is covered by one of more of…

I can finally log in using keyboard.
Network shows only local interface, no eth0 (/dev/eth0 does not exist). I suspect this is caused by the late USB

lspci : nothing, empty

the TX1 was previously “freshly flashed” with Jetpack 3.3 and the internal eMMC contains a working, up to date kernel, with the demo ubuntu rootfs.
looking at dmesg and searching xusb messages before the long delay, I see :

[ 5.xx] xhci-tegra 7009000.xusb: Direct firmware load for tegra21x_xusb_firmware failed with error -2

Any suggestion ?
Thanks

2

The “apply_binaries.sh” step (run sudo) adds a number of files. You can use this with the “-r /some/where/else” to apply it somewhere other than the “rootfs/” subdirectory. Note that one of the files unpacked by this step is the “Linux_for_Tegra/kernel/kernel_supplements.tbz2”, and that this file provides firmware (it ends up as the “rootfs/lib/firmware/” content). Did you run “apply_binaries.sh” as root/sudo to the location where your SD card was being built?

3

Hi @linuxdev @sylvain.azarian we are having the same issue but with the nano. Did you get a fix for this?

4

This is a very old thread, and releases have changed a lot in that time. I suggest you start a new thread and include some details, e.g., what release it starts with, and whether you’ve used the apply_binaries.sh script.