About 2 years ago, I badly screwed up the Ubuntu installation on my Jetson TX2. It’s been sitting in a box since. I am now trying to get Jetpack 4.3 installed on it. However, the SDK Manager cannot find the TX2. I put it into reset mode and didn’t see it on my host with lsusb.
How can I get the TX2 back to its original factory default without using Jetpack? Here’s some information:
Thanks for your reply! I’m not using a VM. I dual booted Ubuntu onto the ASUS ZenBook for the host.
I put the TX2 into recovery mode, connected the ZenBook to the microUSB port of the TX2, ran lsusb on the host, and did not see the device.
I believe that the TX2 is severely damaged in its software. I have no reason to believe it’s a hardware issue, although I cannot rule out the possibility.
Can you boot up your TX2 now?
If yes, you can use uart console and run below command to put your device into recovery mode: sudo reboot forced-recovery
We need to make sure the micro-usb port is working and into RCM, then we can start flash image.
You monitor also must be truly HDMI and not use a VGA adapter.
The cable used between the micro-B USB of the Jetson and the host PC must also be of good quality (charger cables usually fail). The cable which comes with the dev kit works quite well, and if you have switched to a different cable, then I would say the lack of success may be related to the cable quality.
I connected the TX2 to another monitor and I get console output now. It seems to freeze at the same point every time it turns on. I can type until it freezes, and then it becomes unresponsive.
This is the correct table in that image for flashing. Take care of this cable since quality data cables of this type are hard to get. If you’ve flashed with a different cable, then I would recommend flashing again using the correct cable.
In a case where the monitor shows freezing at some point, then you might use a serial USB UART cable (3.3V logic level). The lockup could be as simple as video not working, but the rest of the system functioning…or it could be a hard lockup, and a serial console would give you more information prior to video failing. Hard to say without that. This is the URL for serial console on the TX2: http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/