We recently rebooted our Orin and instead of coming up normally all we got was a long list of the normal LInux hardware/startup messages and then the whole thing hung leaving the screen blank. We tried rebooting and power cycling it and it always did the same thing. So we tried to put it into recovery mode using the defined sequence (and lots of variations) but it did not do so and instead jumped into the above linux preboot sequence. We ran lsusb on the linux system (ver 20) running the SDK and it did not show up. We are pretty much at wits end here and could use some help if anyone has an idea
Hello,Have you tried connecting a Type-C cable to the AGX Orin and a Type-A cable to the host, then checking if /dev/ttyACM0
exists using the command ls /dev/ttyACM0
? If it does, you can try accessing the AGX Orin using tools like minicom
or picocom
.Additionally, I have a few questions for further troubleshooting:
- Is your Ubuntu 20.04 running on a physical machine or in a virtual machine (e.g., VMware, VirtualBox, WSL, etc.)?
- Could you provide the output of
dmesg
after plugging the cable into the host to check for any USB-related information? - Is your AGX Orin a dev kit or a custom carrier board?
Thanks
Hi, I have connected the Orin and a Ubuntu 20.04 machine running on a physical platform. When I run the ls command I do not see the /dev/ttyACM0. The Orin is a dev kit. there are no dmesg events associated with plugging or unplugging the Orin machine.
BTW, I have verified that dmesg is responding to USB devices by plugging and removing a usb mouse. I get a number of msgs indicating it has been inserted and removed.
Just to clarify as you are using a devkit
-
If the board is in recovery mode, you won’t see any log from Jetson because it is the nature of Jetson.
-
The micro usb port on the NV devkit is to dump log. It is actually a UART port with adapter so it “looks like” a usb port but it does not have any function like real usb
-
Only the type C port opposite to the power jack side has the ability to flash board. Which means if you connect the wrong port, then no matter how many times you enter recovery mode, you won’t see it in your lsusb on host PC.
What does this mean here? You run dmesg command on your host?
I used the correct type C port which is on the opposite side from the power port. About the dmesg comment, I just wanted to say that I verified the USB port on the host works and that I was using dmesg correctly.
Maybe you should take a video for how is your connection and how is your method to put the board into recovery mode for us to review.
I have uploaded two videos and one picture. One video shows a mouse being plugged and unplugged and the resulting output from dmesg. This is to show the usb port is okay. The picture shows how the Orin is connected. The third picture shows how I tried to initiate recovery mode and how no messages are reported via dmesg
Hi,
Have you successfully used a white USB Type-C cable to flash the AGX Orin? Are you certain that this USB cable is capable of data transfer? Some cables are designed solely for charging and do not support data transfer.
To enter recovery mode, please hold down the Force Recovery button until the power light turns white. The video shows that you release the button first.
Thanks
Hi
I have tried it with two different cables with the same result.
I will try your suggested button/power sequence.
Thanks
Bob
Hi David
I tried a third cable, this one a Type-C to Type-C and everything is working fine now. I connected to the SDK and am downloading a new boot image.
Evidently not all USB cables are the same.
thanks for all your help
Bob
Hello David
As I wrote earlier, I discovered that the problem I had entering recovery mode was due to the two USB cables I was using.
I am able now to run sdk manager and start to flash the system but it always seems to die when building the linux image. I have attached a zip file of the log files. Can you help?
Thanks
Bob
Hi Bob,
The error you’re experiencing might be similar to the issue discussed in this topic. Please try executing the following commands:
sudo apt-get update
sudo apt-get install --reinstall sdkmanager
If the problem persists, consider the following suggestions:
- Manually flash the device by following the documentation provided.
- Attempt to flash the device using another host machine with SDK Manager.
Thanks