Looking at the log file in comment 20, it does seem like the very first read from the Tegra USB device timed out. The most likely cause is that something had previously communicated with Tegra between when it first entered recovery mode and when tegrarcm_v2 was run. Please try resetting or power cycling Tegra and re-entering recovery mode, then see if tegrarcm_v2 works as expected or not. If resetting Tegra and re-entering recovery mode doesn’t help, then something else is going on which I don’t understand.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| I can't install jetpack 4.2 sdk on my tx2 | 74 | 14770 | April 19, 2019 | |
| TX2 Flash Failed | 3 | 612 | June 6, 2019 | |
| Flashing Failed device could not be found | 20 | 1713 | October 18, 2021 | |
| install jetpack 4.2 and flash Tx2 failed | 4 | 1404 | October 18, 2021 | |
| Could not detect target hardware | 13 | 2585 | October 18, 2021 | |
| Boot up failure after Ubuntu upgrade (Snappy Daemon & Light Display Manager) | 8 | 3239 | June 25, 2019 | |
| ERROR : Flash Jetson AGX Xavier : lost connection | 59 | 9180 | July 14, 2021 | |
| Can't flash the TX2 with SDK manager | 14 | 3249 | October 18, 2021 | |
| Error when install Jetson Software with SDK Manager | 10 | 5696 | October 18, 2021 | |
| TX2 Flash Jetson OS error | 13 | 694 | October 18, 2021 |