###########################################
# L4T BSP Information:
# R34 , Revision: 1.0
###########################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
Is there something that I am doing wrong?
PS:
How I try to setup the Force Recovery Mode
Plug in the power supply in Jetson AGX Orin Developer Kit in 4 (USB Type-C port)
Power off using power button.
Plug in the USB C in the USBC port next to 40-pin connector.
Press and hold down the Force Recovery button.
Press, then release the Power button
Release the Force Recovery button.
In my host ubuntu terminal, using lsusb, I can see the follwing output: Bus 001 Device 010: ID 0955:7023 Nvidia Corp. APX
Just to confirm, if the board is in recovery mode, the “lsusb” will show the device immediately after you release the recovery button. This behavior will not wait for a while.
Yes, I can see the device as Bus 001 Device 010: ID 0955:7023 Nvidia Corp. APX but the problem is when I run: sudo ./flash.sh ${BOARD} mmcblk0p1, it runs into following error that I am unable to figure out.
Using “lsusb” to tell whether this board is in recovery mode is not a 100% correct method. Because if your board boots into kernel, then you will see it in host “lsusb” too. But that one is not recovery mode.
Thus, I just want to double confirm, if you are really sure your board is in recovery mode.
There is no other way to confirm if I really get into the recovery mode as I can’t boot the system (Don’t know why).
Do you have any ideas how to confirm if the board is really in recovery mode?
We don’t support ubuntu 22.04 and Raspberry pi 4. ARM64 host is not supported. You have to use x86_64 host.
My host is Raspberry Pi 4 with Ubuntu 22.10.
If you want to check the board status, you can use the micro usb port on your board and follow this page to dump log. Please be aware that you must use “micro usb port”, cannot use type C.
Note that WSL itself also won’t work. Dual boot with a native Ubuntu 20.04 is the best method. Some VMs can be made to work, but it isn’t officially supported. You’d have to figure out how to make sure USB passes through correctly even if USB disconnects and reconnects. WSL2, in addition to that, also lacks loopback support (someone on the forums once made this work, but adding loopback to WSL2 is apparently not trivial). A native install with an ext4 file system is by far the easiest thing to do.
So here is the thing:
I was able to flash my Jetson Orin with new OS.
The only thing that was important to use the 86_64 host as suggested by @WayneWWW