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 | |
|---|---|---|---|---|
| Flash issue - Flashing JETSON TX2 using sdk manager-jetpack 4.4 onto target OS HW | 28 | 2096 | January 17, 2021 | |
| Can't flash the TX2 with SDK manager | 13 | 3515 | March 17, 2021 | |
| Flashing failed with sdkmanager for Jetson TX2 | 16 | 2092 | December 3, 2020 | |
| JetPack 4.2 Flashing Issues and how to resolve | 67 | 36180 | November 1, 2021 | |
| [Jetpack 3.2] Problems flashing TX2 using native Ubuntu host machine | 25 | 3149 | May 13, 2020 | |
| Flash Jetson TX2 error : CPU Bootloader is not running on device && Failed to execute commands with GenericInstaller | 29 | 5754 | May 21, 2021 | |
| Jet Pack installation jetson TX2 | 27 | 1212 | April 16, 2020 | |
| Jetson TX2 - Failed to flash device | 34 | 4124 | May 20, 2019 | |
| Jetson TX-2 fail to flash; Ubuntu 16; Jetpack 3.1, 3.2 | 32 | 6376 | August 11, 2020 | |
| unable install any JetPacks Jetson TX2 | 31 | 6125 | October 28, 2020 |