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 | 29 | 1841 | October 18, 2021 | |
| Can't flash the TX2 with SDK manager | 14 | 3424 | October 18, 2021 | |
| [Jetpack 3.2] Problems flashing TX2 using native Ubuntu host machine | 25 | 3063 | May 13, 2020 | |
| Flashing failed with sdkmanager for Jetson TX2 | 17 | 1957 | October 18, 2021 | |
| Jetson TX2 - Failed to flash device | 35 | 3843 | October 18, 2021 | |
| Jet Pack installation jetson TX2 | 28 | 1025 | October 18, 2021 | |
| I can't install jetpack 4.2 sdk on my tx2 | 74 | 15312 | April 19, 2019 | |
| Flash Jetson TX2 error : CPU Bootloader is not running on device && Failed to execute commands with GenericInstaller | 30 | 5648 | October 18, 2021 | |
| TX2 flashing : CPU Bootloader is not running on device. Error: Return value 4 | 32 | 10146 | January 15, 2020 | |
| Jetson TX-2 fail to flash; Ubuntu 16; Jetpack 3.1, 3.2 | 33 | 6209 | October 18, 2021 |