Narrow down by specifying conditions
現在1888件がヒットしています。check
For those who have purchased a Jetson product and cannot install JetPack on Jetson using SDK Manager, we will introduce troubleshooting for JetPack installation.
When JetPack cannot be installed, there are two main cases: "When L4T cannot be written to Jetson" and "When Jetson SDK Component cannot be installed".
In this article, we will delve into the details of "When L4T cannot write to Jetson".
Please refer to this article for "When Jetson SDK Component cannot be installed".
NVIDIA JetPack Installation Troubleshooting ~Unable to install Jetson SDK Components~
If Jetson cannot write L4T
If L4T cannot be written, it may be caused by one or more of the following.
・Using an unsupported host PC for writing
・Defective USB cable
・Host PC environment
・Effect of PCN
Let's explore the causes one by one.
Cause 1: Using an unsupported host PC for writing
Writing L4Trequires a host PC with native Linux.
Please note that writing from a virtual PC such as VMWare is not supported. We cannot support it.
Here are the supported environments:
https://docs.nvidia.com/sdk-manager/system-requirements/index.html
If the environment is not supported, prepare a supported environment again and check whether L4T can be written again. (*At this time, please do not use the 3rd party BSP.)
If writing is not possible even in a supported environment, check the following causes.
Cause 2: Bad USB cable
Enter the following command on the terminal while Jetson is in recovery mode.
If "Nvidia Corp." is displayed, the USB cable itself is fine.
If it does not appear, replace with a new USB cable and try again.
$ lsusb | grep -i nvidiaCause 3: Host PC environment problem
There may be a problem with the environment settings of the host PC that writes.
First, make sure you are using the SDK Manager to install.
■ Notes
・At this time, it is necessary to connect to the network.
・Prepare a host PC with native Linux and use SDK Manager.
・When connecting the Jetson product and the host PC, put the Jetson product in recovery mode.
Next, let's check if you're connected to the intranet.
Please refer to the link below and check the proxy settings of the SDK Manager.
https://docs.nvidia.com/sdk-manager/0.9beta14/sdkm-settings/index.html
Please check if you can write by connecting the host PC to the external network.
If writing is not possible, check whether writing to other modules is possible in the same way.
If only a specific module cannot be written, it may be affected by PCN.
Cause 4: Effect of PCN
As an example of TX2, asdescribed in "Method of identifying Changed Product" and "Recommended Action for Customers" in the "Jetson_TX2_PCN" document, the TX2 module product after applying PCN is "699-83310- Individuals with a part number of ****-D02 are
JetPack 4.4 / BSP 32.4.2 or newer
or
JetPack 3.3.3 / BSP 28.4
must be written and may fail if that condition is not met.
PCN is posted on the following page, so please check the contents.
※Jetson Download Center
Example: Jetson TX2 NX PCN 207500 Addition of Manufacturing BOM Components: SK Hynix Memory
Matters related to writing trouble
Please refer to the following article for "When Jetson SDK Component cannot be installed".