There are known flashing issues with the Jetson TX2 platforms that NVIDIA is actively working to resolve. To provide transparency, and further support our customers, several of these issues, and where possible workarounds toward resolution, please refer to below:
Q1: How to export SDK Manager logs?
A: SDK Manager logs can be exported with below steps:
1. Launch SDK Manager.
2. Click on the 3 dots in the top right corner (“⋮”) and select Export Debug Logs.
3. A zip file of the logs is saved into ~/Downloads/nvidia/sdkm_downloads directory automatically.
Q1: I cannot flash Jetson device with SDK Manager. What to do next?
A: Please make sure there is no environment issue. We can confirm this by manually flashing Jetson.
1. Manually reset board to clear board status.
2. Put Jetson device to recovery mode.
3. Go to JetPack install directory. For example, ~/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3489/. The actual path may vary depending on the selected installation directory and selected board type.
4. cd Linux_for_Tegra
5. Run one of the below command to flash Jetson device:
- sudo ./flash.sh jetson-tx2 mmcblk0p1 // For Jetson TX2
- sudo ./flash.sh jetson-tx2i mmcblk0p1 // For Jetson TX2i
- sudo ./flash.sh jetson-xavier mmcblk0p1 // For Jetson Xavier
- sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1 // For Jetson Nano
6. Paste full log of step 5 if flashing fails.
Q2: Why manually flashing doesn’t work, although lsusb shows device is already in recovery mode?
A: lsusb alone is not sufficient. Need put device to recovery mode again. Specifically, lsusb simply shows that the Jetson device is attached to your PC and in recovery mode. However, there is a one-off setup communication that occurs between the PC and Jetson each time flashing is attempted, and once this has happened, any flash attempt will fail unless Jetson is forced back into recovery mode, even if it already appears to be in recovery mode. See comments from Stephen https://devtalk.nvidia.com/default/topic/1048660/jetson-tx2/i-can-t-install-jetpack-4-2-sdk-on-my-tx2/post/5328041/#5328041
Jetson SDK (target) installation issues
Q1. I cannot connect to Jetson device after flashing. I’ve created new user, and jetson device has boot up. Ubuntu desktop is shown on HDMI output. USB cable is connected between host and Jetson device. What to do next?
A: SDK Manager relies on usb-device mode to set up network connection between host and target. Please see Jetson usb-device mode issues section in this FAQ for more details.
Jetson usb-device mode issues
Q1: How to verify if usb-device mode is working?
A: After flashing and Jetson device booting up, usb-device mode is up . The expected results at this stage are
- 192.168.55.1 is assigned to Jetson device, and
- 192.168.55.100 is assigned to host machine.
Q2: usb-device mode is already up and running, however, 192.168.55.100 not assigned on host. Why?
A: One possible reason is that usb-ethernet network interface is disabled on host machine? To enable it,
- Disconnect and Connect the USB cable connecting the jetson and Host-PC, and check the dmesg log.
You might see a log similar to this:
[107833.388835] cdc_ether 2-2:1.5 usb1: register ‘cdc_ether’ at usb-0000:00:14.0-2, CDC Ethernet Device, 72:40:f7:72:c9:fa
- Next go to Settings->Network and check all the wired connections for the same MAC-address.
- In the top right corner there will be an option to enable it.
- Next follow the procedure as provided by the SDK manager to install the SDK components
Q3: How to check if there is any error during starting jetson usb-device mode?
A: Use below steps:
- Run “dmesg” on the host and provide the full output. This might show any errors the host might have had when enumerating the Jetson USB device.
Now, connect jetson device with a ethernet cable, get its IP address, ssh to Jetson and:
- Run “journalctl -u nv-l4t-usb-device-mode” to show any errors configuring the USB device mode service on Jetson, during boot.
- As root, run “/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh”. This is expected to show some errors; ignore them.
- As root, run “bash -x /opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode.sh” and provide the entire output that prints. This should
(a) show the same errors as in (2) above, and/or
(b) actually make L4T USB device mode work, if the reason it failed the first time was due to some missing dependency that wasn’t available right when the script ran at boot.