The ADB device is not yet found online

Robotics & Edge Computing Jetson & Embedded Systems Jetson Thor
1

I’ve ran in to problems with my Nvidia Thor dev-kit. When I try to flash the device it doesn’t manage to establish a connection over adb.

On host side the output is: (full log attached)

[flash_bsp_jetson-t264_die0]: [executeShellCommand(156)] : command = /work/nvidia/Jetson_Linux_R38.2.1_aarch64/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/flash/adb devices -l
cwd = /work/nvidia/Jetson_Linux_R38.2.1_aarch64/Linux_for_Tegra/unified_flash/out/bsp_images/flash_workspace/flash-images
[flash_bsp_jetson-t264_die0]: [executeShellCommand(163)] : List of devices attached

[flash_bsp_jetson-t264_die0]: [ListADBDevices(180)] : listing connected adb devices with sudo
[flash_bsp_jetson-t264_die0]: [executeShellCommand(156)] : command = /work/nvidia/Jetson_Linux_R38.2.1_aarch64/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/flash/adb devices -l
cwd = /work/nvidia/Jetson_Linux_R38.2.1_aarch64/Linux_for_Tegra/unified_flash/out/bsp_images/flash_workspace/flash-images
[flash_bsp_jetson-t264_die0]: [executeShellCommand(163)] : List of devices attached

On target side: (full log attached)

insmod /lib/modules/6.8.12-tegra/updates/dri[ 6.112570] tegra��pll_��-qsp��c0 h��i 81��as n��0c5b��o dy��0000��n ra��.spi��mp
��: Adding to iommu group 20
[ 6.126828] tegra-qspi 810c5b0000.spi: Prod settings list not found
vers/spi/spi-tegra210-quad.ko
modprobe: FATAL: Module mods not found in directory /lib/modules/6.8.12-tegra
Finding UDC
insmod /lib/modules/6.8.12-tegra/kernel/drivers/net/dummy.ko numdummies=1
[ 7.328206] file system registered
adbd64 E 01-01 00:00:07 490 490 adbd_auth.cpp:183] Failed to get adbd socket: No such file or directory
[ 8.340522] bcdVersion must be 0x0100, stored in Little Endian order. Userspace driver should be fixed, accepting 0x0001 for compatibility.
to get adbd socket: No such file or directory
adbd64 I 01-01 00:00:07 490 492 usb.cpp:264] initializing functionfs
adbd64 I 01-01 00:00:07 490 492 usb.cpp:285] opening control endpoint /dev/usb-ffs/adb/ep0
libc: Using old property service protocol (“ro.property_service.version” is not set)
adbd64 I 01-01 00:00:07 490 492 usb.cpp:370] functionfs successfully initialized
adbd64 I 01-01 00:00:07 490 492 usb.cpp:377] registering usb transport
[ 9.362110] tegra-xudc a808670000.usb: EP 0 (type: ctrl, dir: out) enabled

I have been able to flash my device at least one time and this is a new thing. What can cause this issue? How to recover from it?

target.log (117.4 KB)

host.log (444.5 KB)

2

Solved! You must have the correct cable. This is a mystery that I would like you at Nvidia to describe to me how it works.

When I flashed my target for the first time I had trouble getting it to flash. Finally it worked when I had a USB-C (target) to USB-A (host) cable. Now some time later I only succeeded to flash my target when I use USB-C to USB-C cable. Can you please explain this to me! Is there any persistent settings on target side that can have impact on this?

4

Hi,

The cable you successfully used for flashing previously should still work for flashing again.
Please ensure that your flashing cable is connected to the J81 port, as shown in the guide.

Thanks

5

Sure, that is what I also expects. Is the flashing procedure always performed on USB2? I wonder if there is some feature selecting between USB2 and USB3 that comes in to play here? Can someone give the information if the flashing through USB is USB2 or USB3?

6

Hi,

Please file a new topic, as this question isn’t related to the existing topic.

Thank you.

7

Then I need to reformulate the question. I want to know the details of the behavior I experience. I put it more general then; can you explain to me why it in some situations works with USB-A connected cable and in some situations USB-C connected cable? Or put it the other way, do you have any requirements on the cable to use for flashing in order for it to always work?

8

Hi,

We recommend using the flashing cable included in the developer kit.
Would you like to know the requirements for the flashing cable?

Thanks