Tegraflash Troubleshooting

This page includes some guidance about how to resolve or work around issues with device flashing using the tegraflash package build by the Yocto build.

General Troubleshooting Tips/Suggestions

1. Make sure you are using the correct flashing operation for your device/target storage. See the table here for guidance.
   • If your target can support either method, try the alternate method as a troubleshooting step.
2. Try swapping USB cables/ensure you are using a high quality cable.
3. Try power cycling the device/entering tegraflash mode from power on rather than reboot.
4. Switch to an alternative USB host controller as several people have noticed issues with these. See this issue for instance.
   • If you are using a USB 3.0 add-in card, switch to the one connected to the motherboard.
   • Try a USB 2.0 port if you have no other USB 3.0 controllers.
5. Note any failures in logs for the respective flashing method
   • Start with the console log.
   • Connect the serial console on the target device if possible.
   • For initrd-flash steps, consult the host and device logs which are output at the end of the flash process.
6. Suspect issues with partition table, especially if you've modified the partition table or increase sizes of partitions
   • Obscure errors like cp: cannot stat 'signed/*': No such file or directory typically mean you've got some problem with your custom partition table and/or target storage device size. See this issue for example.
7. Attempt to reproduce with a devkit and a similar setup from tegra-demo-distro.
8. Use hardware recovery mode entry
   • See instructions at https://github.com/OE4T/meta-tegra/wiki/Flashing-the-Jetson-Dev-Kit#setting-up-for-flashing for putting the device in recovery mode.
   • Although it's possible to use reboot force-recovery, note the issues here which can occur in some scenarios. Using hardware recovery is typically a safer option if you are experiencing issues with tegraflash.