# Xavier NX can not start after damage

**URL:** <https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519>\
**Category:** Jetson Xavier NX\
**Tags:** hw\
**Created:** [March 28, 2022, 3:43am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519 "2022-03-28T03:43:32Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [March 28, 2022, 3:43am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/1 "2022-03-28T03:43:32Z")

</div>

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,

---

<div class="post-metadata">

**Author:** ![Trumany](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trumany/32/14043_2.png) [@Trumany](https://forums.developer.nvidia.com/u/Trumany)\
**Post date:** [March 28, 2022, 7:21am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/3 "2022-03-28T07:21:07Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [March 28, 2022, 4:32pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/4 "2022-03-28T16:32:48Z")

</div>

Here is the log

 ![image](https://global.discourse-cdn.com/nvidia/original/3X/a/a/aa955942750dc39b0be5ed74fb75e67ffb7cb34c.jpeg)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 28, 2022, 5:12pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/5 "2022-03-28T17:12:01Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [March 28, 2022, 5:31pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/6 "2022-03-28T17:31:05Z")

</div>

@WayneWWW Thank you very much. DO you mean rebuild the SDCard? Can I follow the instruction here?

> **[Getting Started With Jetson Xavier NX Developer Kit](https://developer.nvidia.com/embedded/learn/get-started-jetson-xavier-nx-devkit#write)**
>
> Introduction Included in the Box Items not Included Write Image to the microSD Card Instructions for Windows Instructions for Mac Instructions for Linux Setup and First Boot Setup Steps First Boot After Logging In Next Steps Next Step \>...

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 29, 2022, 2:14am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/7 "2022-03-29T02:14:30Z")

</div>

No, doing full flash with the method here. Do not user sdcard image. SDcard image isn’t full flash the whole device.

> **[NVIDIA SDK Manager](https://developer.nvidia.com/nvidia-sdk-manager)**
>
> Everything You Need to Set Up Your Development Environment NVIDIA SDK Manager provides an end-to-end development environment setup solution for NVIDIA’s DRIVE, Jetson, Holoscan, Rivermax, DOCA and Ethernet Switch SDKs for both host and target...

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [March 30, 2022, 9:16pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/8 "2022-03-30T21:16:02Z")

</div>

Hi @WayneWWW Why do you think flashing the Xavier NX will solve the problem?

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 31, 2022, 2:35am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/9 "2022-03-31T02:35:35Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [March 31, 2022, 3:36am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/10 "2022-03-31T03:36:48Z")

</div>

@WayneWWW thank you very much.

I am going to follow jetsonhacks to flash because it is much easier. [Native Boot for Jetson Xaviers - JetsonHacks](https://www.jetsonhacks.com/2021/08/25/native-boot-for-jetson-xaviers/amp/) Is this ok?

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [March 31, 2022, 3:41am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/11 "2022-03-31T03:41:25Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [March 31, 2022, 5:28pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/12 "2022-03-31T17:28:14Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [April 1, 2022, 3:10am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/13 "2022-04-01T03:10:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [April 1, 2022, 4:44am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/14 "2022-04-01T04:44:54Z")

</div>

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](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](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:

21:35:14.692 - info: initializeGroups ended with failure. Duration: 0.576s 21:35:14.692 - info: Event: Step3 load complete: failed 21:35:14.711 - error: Found unhandledrejection Promise { 'Failed to get configuration file from the server. Please check your network connectivity.' } 21:38:02.691 - info: Event: Step3 load started 21:38:02.691 - info: initializeGroups. User selections: Product: Jetson Version: 4.6.1 selectedHW: target selectedTargetCa tegoryId: JETSON\_XAVIER\_NX\_TARGETS selectedOS: Linux 21:38:02.933 - info: loading l3 data from repo url: ['https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.6.1/Jetson\_461\_b110/sdkml3\_jetpack\_461 .json', 'https://developer.nvidia.com/assets/deepstream/deepstream\_6.0.1/deepstream\_601\_b11/sdkml3\_deepstream.json'] 21:38:02.934 - 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:38:03.258 - 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.324 sec 21:38:03.259 - 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: 21:38:03.260 - info: initializeGroups ended with failure. Duration: 0.568s 21:38:03.260 - info: Event: Step3 load complete: failed 21:38:03.271 - error: Found unhandledrejection Promise { 'Failed to get configuration file from the server. Please check your network connectivity.' }

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [April 1, 2022, 4:48am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/15 "2022-04-01T04:48:38Z")

</div>

Sorry that there is an outage. Some services are down. We will fix this soon.

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [April 2, 2022, 4:08am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/16 "2022-04-02T04:08:46Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [April 2, 2022, 4:12am UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/17 "2022-04-02T04:12:05Z")

</div>

Hi,

You can click only to flash OS in sdkmanager. No need to install SDK.

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [April 2, 2022, 6:13pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/18 "2022-04-02T18:13:39Z")

</div>

@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](http://us.archive.ubuntu.com/ubuntu) trusty Release  
0% [Connecting to [security.ubuntu.com](http://security.ubuntu.com) (2620:2d:4000:1::16)] [Connecting to [archive.canonical.com](http://archive.canonical.com) (2001:67c:1360:8001::27)] [Con

Could you let me know where the problem is?

---

<div class="post-metadata">

**Author:** ![AutoCar](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/autocar/32/166725_2.png) [@AutoCar](https://forums.developer.nvidia.com/u/AutoCar)\
**Post date:** [April 2, 2022, 6:14pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/19 "2022-04-02T18:14:24Z")

</div>

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](http://us.archive.ubuntu.com/ubuntu) trusty InRelease  
Hit:26 [Index of /ubuntu](http://us.archive.ubuntu.com/ubuntu) trusty-updates InRelease  
Hit:28 [Index of /ubuntu](http://us.archive.ubuntu.com/ubuntu) trusty-backports InRelease  
Hit:29 [https://nvidia.github.io/libnvidia-container/ubuntu16.04/amd64](https://nvidia.github.io/libnvidia-container/ubuntu16.04/amd64) InRelease  
Hit:30 [https://nvidia.github.io/nvidia-container-runtime/ubuntu16.04/amd64](https://nvidia.github.io/nvidia-container-runtime/ubuntu16.04/amd64) InRelease  
Hit:31 [https://nvidia.github.io/nvidia-docker/ubuntu16.04/amd64](https://nvidia.github.io/nvidia-docker/ubuntu16.04/amd64) InRelease  
Hit:35 [Index of /ubuntu](http://us.archive.ubuntu.com/ubuntu) trusty Release  
0% [Connecting to [security.ubuntu.com](http://security.ubuntu.com) (2620:2d:4000:1::16)] [Connecting to [archive.canonical.com](http://archive.canonical.com) (2001:67c:1360:8001::27)] [Con  
0% [Connecting to [security.ubuntu.com](http://security.ubuntu.com) (2620:2d:4000:1::16)] [Connecting to [archive.canonical.com](http://archive.canonical.com) (2001:67c:1360:8001::27)] [Con  
0% [Connecting to [security.ubuntu.com](http://security.ubuntu.com) (2620:2d:4000:1::19)] [Connecting to [archive.canonical.com](http://archive.canonical.com) (2001:67c:1562::1c)] [Connecti

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [April 2, 2022, 6:18pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/20 "2022-04-02T18:18:27Z")

</div>

Hi,

Please try to attach full log as a text file.

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [April 2, 2022, 6:21pm UTC](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519/21 "2022-04-02T18:21:16Z")

</div>

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.

[Next page](https://forums.developer.nvidia.com/t/xavier-nx-can-not-start-after-damage/209519.md?page=2)
