Additional Flashing Notes and Troubleshooting#

  • See the NVIDIA DriveOS 7.2 Release Notes for more information on flashing the target for this release.

  • DriveOS Docker containers have $NV_WORKSPACE set to /drive where the DriveOS SDK is installed.

  • See the “Terminal Emulation” chapter of the NVIDIA DriveOS SDK Developer Guide for more details on minicom.

  • /dev/ttyACM2 is the default sMCU port for the DRIVE AGX Thor Developer Kit on the x86 Host system if only one Developer Kit or another USB device is connected. If there are additional devices in this device range, disconnect them before flashing.

  • If flashing the target system fails, try the following:

    • Before retrying bootburn.py, verify that the host detects the target in recovery mode:

      $ lsusb | grep -i 'NVIDIA Corp. APX'

      If the command returns no output, the target is not visible to the host in recovery mode.

    • Some ADB/device reconnect messages can appear during flashing when the target switches USB modes. If bootburn.py later reports that flashing completed successfully, these messages are not fatal. If flashing fails, verify APX visibility, check for host ADB conflicts, and retry after reconnecting the USB cable.

    • Reseat the USB cable connected from the Host PC to the debug USB Type-C port on the target on both ends.

    • Use a USB 3.1 port on the host PC, if available.

    • Use a different USB C/SS cable, or a higher speed cable such as a USB SS10 (for example, Amazon Model Number L6LUC146-CS-R).

    • Use a USB 2.0 port on the host PC for flashing.