Hi,
I use the Xavier NX on a RC car for autonomous racing. Today the car rolled over and I believed the Jetson was damaged. When I started the Xavier NX, it showed a very short few lines of log (It used to have many many lines of log) and then went into the login page. After I logged in, it seems normal. But after I moved the mouse a little bit, the screen froze.
How can I fix it? How can I tell if the carrier board was damaged or the module was damaged?
Thanks,
Please share the log info of that first. And have you observed the Jetson board to try to find out if something broken or damaged?
This image does not indicate a hardware damage. Probably got recovered after you flash it with sdkmanager.
Try with sdkmanager first. If it got froze, then we discuss the next to check.
@WayneWWW Thank you very much. DO you mean rebuild the SDCard? Can I follow the instruction here?
No, doing full flash with the method here. Do not user sdcard image. SDcard image isn’t full flash the whole device.
Hi @WayneWWW Why do you think flashing the Xavier NX will solve the problem?
We have two boot devices over the module. The first one is the bootloader sfotwares which are on the QSPI flash on your module. The second one is the sdcard slot.
The sdcard image actually provides only the rootfs, kernel and kernel-dtb. If what you’ve done is just change one sdcard to another sdcard, then it is obvious that you didn’t do anything to your QSPI.
If the software on the QSPI is corrupted, then what you’ve done didn’t fix the bootloader. That is why I said sdcard image is not doing “full flash” to the board.
There is still chance to be a hardware defect. But full flash is the common way to check before filing a RMA request.
@WayneWWW thank you very much.
I am going to follow jetsonhacks to flash because it is much easier. Native Boot for Jetson Xaviers - JetsonHacks Is this ok?
Err… no . I don’t suggest to try that.
IMO, sdkmanager is easier… Following jetsonhacks website at this moment just makes the situation more complicated… Their usecase is different too.
No need to mention their tools are from sdkmanager too.
Hi @WayneWWW On my Xavier NX, I have a SD card and SSD. I have been run the Xavier NX from the SSD. The SSD has a lot of data and software. Now I am going to flash the NX with sdkManager. After I flash my Nx, can I reuse the SSD? I could not remember which version of Jetpack I had on the NX (I purchased March, 2021). If I flashed with the wrong version of Jetpack, can I still use the SSD?
Hi,
Just put a sdcard to your board, remove the SSD in case some wrong operation in sdkm makes your data gone. Flash the sdcard first and see if the board is able to boot up fine.
Your SSD should always be fine if kernel is able to detect it. AFAIK, this should be no problem.
But making your SSD fully back may need some bootloader knowledge. We can discuss that later. Please make sure the board is still able to work with sdcard first.
Hi @WayneWWW, I got the following error in SDKManager step 02:
Could not load the NVIDIA SDK details
Failed to get configuration file fomr the server. Please check your network connectivity.
My host PC use ubuntu 16.0. The internet is fine. Please also see the SDKM log:
21:35:14.372 - info: start to download https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.6.
1/Jetson_461_b110/sdkml3_jetpack_461.json
21:35:14.681 - info: sdkml3_jetpack_461.json from https://developer.download.nvidia.com/assets/embedded/secure/tools/files/jetpa
ck-sdks/jetpack-4.6.1/Jetson_461_b110/sdkml3_jetpack_461.json?_BAzhLVNJB682JZb7_aHIs3O_c4FE–Zy0LMUCy0MqwQzlVjWfH3sD8dPI7tWB5lG1
mIMulUD2BMeZa7OhVT1jir6nPbeNbPsPhRcBlGW5381OoiaWjL3ghOROrgkF13AFTdY7Cs2KptHQnCFXMNd2RRYnwTp_J2u4s_xwRESFovZPHJ5qXTF_XXnrnNR77jHD
PR53v-6tl5RrS7V9F9Sq_tr0o has been downloaded to /home/gcong/.nvsdkm/dist successfully. Time used 0.309 sec
21:35:14.689 - error: initializeGroups error: Could not load components list. Error: Read json failed: /home/gcong/.nvsdkm/dist
/sdkml3_jetpack_461.json The whole json file is:
Sorry that there is an outage. Some services are down. We will fix this soon.
@WayneWWW, I am now getting the follow problem with SDK Manager :
Your system is not ready for install, see specific errors below. Once fixed, click ‘Retry’ to verify system readiness again.
Access to APT repository and ability to install Debian packages with it.: Apt repository check failure (1. sudo -S apt-get update && sudo -S apt-get check; 2. dpkg --audit). command < sudo timeout 200 apt-get update && sudo timeout 200 apt-get check > terminated with error, exitCode: 124.
Hi,
You can click only to flash OS in sdkmanager. No need to install SDK.
@WayneWWW, Thank you.
On STEP 02 of SDKManager, I unckecked Jetson SDK Components, and click “Continue”, but the same problem.
If I ran sudo -S apt-get update in the terminal, it stucked at
Hit:35 Index of /ubuntu trusty Release
0% [Connecting to security.ubuntu.com (2620:2d:4000:1::16)] [Connecting to archive.canonical.com (2001:67c:1360:8001::27)] [Con
Could you let me know where the problem is?
sudo -S apt-get update
[sudo] password for gcong:
Get:1 file:/var/cuda-repo-10-0-local-10.0.326-410.108 InRelease
Ign:1 file:/var/cuda-repo-10-0-local-10.0.326-410.108 InRelease
Get:2 file:/var/cuda-repo-10-0-local-10.0.326-cross-aarch64 InRelease
Ign:2 file:/var/cuda-repo-10-0-local-10.0.326-cross-aarch64 InRelease
Get:3 file:/var/cuda-repo-8-0-local InRelease
Ign:3 file:/var/cuda-repo-8-0-local InRelease
Get:4 file:/var/cuda-repo-9-0-local InRelease
Ign:4 file:/var/cuda-repo-9-0-local InRelease
Get:5 file:/var/cuda-repo-cross-aarch64-ubuntu1804-10-2-local InRelease
Ign:5 file:/var/cuda-repo-cross-aarch64-ubuntu1804-10-2-local InRelease
Get:6 file:/var/cuda-repo-ubuntu1604-10-2-local InRelease
Ign:6 file:/var/cuda-repo-ubuntu1604-10-2-local InRelease
Get:7 file:/var/nccl-repo-2.1.4-ga-cuda9.0 InRelease
Ign:7 file:/var/nccl-repo-2.1.4-ga-cuda9.0 InRelease
Get:8 file:/var/visionworks-repo InRelease
Ign:8 file:/var/visionworks-repo InRelease
Get:9 file:/var/visionworks-sfm-repo InRelease
Ign:9 file:/var/visionworks-sfm-repo InRelease
Get:10 file:/var/visionworks-tracking-repo InRelease
Ign:10 file:/var/visionworks-tracking-repo InRelease
Get:11 file:/var/cuda-repo-10-0-local-10.0.326-410.108 Release [574 B]
Get:11 file:/var/cuda-repo-10-0-local-10.0.326-410.108 Release [574 B]
Get:12 file:/var/cuda-repo-10-0-local-10.0.326-cross-aarch64 Release [574 B]
Get:12 file:/var/cuda-repo-10-0-local-10.0.326-cross-aarch64 Release [574 B]
Get:13 file:/var/cuda-repo-8-0-local Release [574 B]
Get:13 file:/var/cuda-repo-8-0-local Release [574 B]
Get:14 file:/var/cuda-repo-9-0-local Release [574 B]
Get:14 file:/var/cuda-repo-9-0-local Release [574 B]
Get:15 file:/var/cuda-repo-cross-aarch64-ubuntu1804-10-2-local Release [563 B]
Get:15 file:/var/cuda-repo-cross-aarch64-ubuntu1804-10-2-local Release [563 B]
Get:16 file:/var/cuda-repo-ubuntu1604-10-2-local Release [564 B]
Get:16 file:/var/cuda-repo-ubuntu1604-10-2-local Release [564 B]
Get:17 file:/var/nccl-repo-2.1.4-ga-cuda9.0 Release [574 B]
Get:17 file:/var/nccl-repo-2.1.4-ga-cuda9.0 Release [574 B]
Get:18 file:/var/visionworks-repo Release [1,999 B]
Get:18 file:/var/visionworks-repo Release [1,999 B]
Get:19 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:19 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:20 file:/var/visionworks-tracking-repo Release [2,008 B]
Get:20 file:/var/visionworks-tracking-repo Release [2,008 B]
Ign:25 Index of /ubuntu trusty InRelease
Hit:26 Index of /ubuntu trusty-updates InRelease
Hit:28 Index of /ubuntu trusty-backports InRelease
Hit:29 https://nvidia.github.io/libnvidia-container/ubuntu16.04/amd64 InRelease
Hit:30 https://nvidia.github.io/nvidia-container-runtime/ubuntu16.04/amd64 InRelease
Hit:31 https://nvidia.github.io/nvidia-docker/ubuntu16.04/amd64 InRelease
Hit:35 Index of /ubuntu trusty Release
0% [Connecting to security.ubuntu.com (2620:2d:4000:1::16)] [Connecting to archive.canonical.com (2001:67c:1360:8001::27)] [Con
0% [Connecting to security.ubuntu.com (2620:2d:4000:1::16)] [Connecting to archive.canonical.com (2001:67c:1360:8001::27)] [Con
0% [Connecting to security.ubuntu.com (2620:2d:4000:1::19)] [Connecting to archive.canonical.com (2001:67c:1562::1c)] [Connecti
Hi,
Please try to attach full log as a text file.
Based on experience, this is your host side apt issue.
SDKM just tries to run apt-get update and notice there are some errors. With those errors, sdkm doesn’t dare to install and hope you fix those errors first before installing.
Such error is case by case.
If it is just stuck, maybe you can check the connection with that server first.
