I’ve attached the minicom logs from trying the software approach. You can see in line 1594 that what happens after I entered the command. cmd-serial.log (166.7 KB)
Yes, I tried with the Jetson powered off: holding recovery button (middle one of the three buttons) → power button press → releasing recovery button
and with the Jetson powered on: holding recovery button → reset button press → releasing recovery button
But I noticed a normal boot takes around 45s and one with the button method around 90s. I still cannot flash anything even when running sudo ./flash.sh ${BOARD} mmcblk0p1 continuously in a loop. The output of lsusb is always:
Maybe try holding the reset (not the power button) button longer, like so:
(While power is connected)
• press reset & recovery buttons together
• release reset button
• release the recovery button after 3 seconds later.
The “abnormal” is probably the screenshot device with ID 0955:7045. What creates that ID? An AGX Orin would show up as 0955:7023. The manufacturer ID is correct, but the product ID is something else.
If you think the device is in recovery mode, e.g., you held down recovery, then powered it on, followed by releasing the recovery button, what shows up on the host PC upon plugin? You could monitor “dmesg --follow” on the host PC, and then watch what new log lines appear as a result of plugging in the USB. It’d be the USB-C to the right of the 40-pin header.