My Xavier NX just showed up. I flashed an SD card per the directions, went through all the linux setup. Since that, the device is totally dead, no fan, no hdmi output, wont register on my switch (shows the port is in use, but no device info).
Is there anything I can do, some special sd recovery card, jumper or dance I can do to bring it back to life?
You could actually check the board status by using the UART console as below link showed.
This will at least show some logs so that we can help you tell what is happened to the board.
Thank you for the tip. It looks like the device does still have some life in it! I am trying to load the Jetpack SDK 5.1.2 so it is compatible with my target production device. JetPack SDK 5.1.2 | NVIDIA Developer
ChatGPT says I should not run anything newer than JetPack 4.6.1, is that correct?
[0000.025] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.034] I> MB1 (prd-version: 1.5.1.3-t194-41334769-d2a21c57)
[0000.039] I> Boot-mode: Coldboot
[0000.042] I> Chip revision : A02P
[0000.045] I> Bootrom patch version : 15 (correctly patched)
[0000.050] I> ATE fuse revision : 0x200
[0000.054] I> Ram repair fuse : 0x0
[0000.057] I> Ram Code : 0x0
[0000.059] I> rst_source : 0xb
[0000.062] I> rst_level : 0x1
[0000.066] I> Boot-device: QSPI
[0000.068] I> Qspi flash params source = brbct
[0000.072] I> Qspi using bpmp-dma
[0000.075] I> Qspi clock source : pllp
[0000.079] I> QSPI Flash Size = 32 MB
[0000.082] I> Qspi initialized successfully
[0000.086] E> LOADER: Failed to verify SMD.
[0000.090] I> Primary SMD copy is invalid, try with secondary copy..
[0000.096] E> LOADER: Failed to verify SMD.
[0000.100] E> LOADER: Failed to verify SMD & SMD_b.
[0000.104] E> Error: SMD: Load failed
[0000.108] E> Load SMD failed
[0000.110] E> LOADER: Failed to get slot for boot chain from SMD.
[0000.116] E> LOADER: Failed to get storage info for binary 0 from loader.
[0000.122] E> LOADER: Failed to get info for binary 0 from loader.
[0000.128] C> LOADER: Could not read binary 0.
[0000.132] C> Fail to load mb1-bct bin
[0000.135] E> Task 24 failed (err: 0x1d1d1318)
[0000.139] E> Top caller module: LOADER, error module: LOADER, reason: 0x18, aux_info: 0x13
[0000.147] I> MB1(1.5.1.3-t194-41334769-d2a21c57) BIT boot status dump :
0000000000011111111110111000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I don’t think the what the GPT told you is right. Not sure why it said so.
You could use any Jetpack5 software on it.
Please try to flash it first and see if you could be alive again.
I tried refreshing it to JetPack 4.6.1 but I still get the same output on the console bool loop. Do you have any other suggestions?
What was the version that in use with above log provided?
Thanks for the response! The log above is from 5.1.2 I am trying to make an analog device to match the boston dynamics Core/IO device. Per the instructions they suggest a docker image of (JetPack 5.1.2 (L4T R35.4.1). So I thought I would just build out my Xavier as a 5.1.2 machine.
Hi,
There are few questions that I need your answers first
Is this a NVIDIA devkit or a custom board? Or you are not sure what I mean in this question?
Did the sdkmanager really tell you that it successfully flash the board? or the log itself is from a flash failure?
This is an official Jetson Xavier NX dev kit. I made an sd card with 5.1.2 and popped it in the sd card slot. I know it worked because the ubuntu setup took me through all the steps and I got to the desktop.
Hi,
Actually I don’t really know what you are talking about.
When you said sdcard, are you referring to sdcard image or you let sdkmanager flash your empty sdcard?
Sdcard image is not same as sdkmanager.
Also, you mentioned “I got to the desktop”. What does that mean? Jetson shows the Ubuntu desktop GUI to you? Then why did you said it fails to boot?
Sorry if I am not clear, I am new at Jetson development. I followed the instructions here and made a micro-sd card: Jetson Xavier NX Developer Kit - Get Started | NVIDIA Developer
Once I did that, and booted the device with hdmi, the screens took me through a lot of onboarding and finally I got to the desktop (gnome?)
On my next boot, the device was dead, no fan, no hdmi output, nothing. Today I found that I could use a serial connection and see what is going on. The jetson seems to be in a boot loop spitting out the message from the console over and over.
Ok. Then just to make sure.
Did your really know how to operate sdkmanager there to flash your board but not using sdcard image?
Your corruption here is in the bootloader which is not located on sdcard. If you keep changing things on sdcard, you didn’t fix anything there. The Boolotader is on the QSPI memory on the Jetson itself. Only using sdkmanager from other host PC to flash your Jetson would recover it.
OH…
I thought since the sd card wasn’t working I couldn’t get to the sdkmanager. So I can load the sdkmanager on my Orion and use that to resurrect the Xavier?
No, sdkmanager can only work on x86 host PC. You need to get one ubuntu20.04 host first.
Quite the can of worms. I get ubuntu on a pc and go from there. Thank you for all the support.
I am stoked to have a working device, but what a brutal process… I tried so many things.
Installed VirtualBox on my PC and installed Ubuntu
Installed SDKManager only to find no Xavier NX images are supported
After a lot of runaround on the command line, I wound up making an Ubuntu USB stick
From the Ubuntu USB I was able to re-flash the QSPI Bootloader and get the Jetson Xavier NX working with Jetpack 4.6.1
From what I can tell I am limited to Jetpack 4.6.1 on my jetson devkit due to the Ratchet level 2 vs lever 4 issues. Any time I try to get the device running on 5.1.2 I run into the ratchet boot loop.
Thanks again for all the support.
Solution:
Xavier NX Devkit sd card edition I was able to recover the QSPI Bootloader after flashing it with Jetpack 5.1.2 and corrupting it. It took a bootable Ubuntu USB and commandline tools to get the job done.
Get these two from NVIDIA:
# Extract BSP
tar xvf Jetson_Linux_R32.7.1_aarch64.tbz2
cd Linux_for_Tegra
# Extract rootfs
cd rootfs
sudo tar xpf ../../Tegra_Linux_Sample-Root-Filesystem_R32.7.1_aarch64.tbz2
cd ..
# Apply NVIDIA binaries
sudo ./apply_binaries.sh
# Boot the jetson into recovery mode and connect it to the Ubuntu machine via usb not serial ttl
sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
Hi,
What you are talking about does not make sense. I still don’t see you really flashed your board with sdkmanager +jetpack5.
If you are fine with this situation and don’t want to do anything more, then I am also fine.
But just to clarify that
There is no rule to “must use jetpack4.6.1” on any Xavier NX device.
I don’t know why you are doing this. If this is just because chatGPT told you so, then it is wrong. We should look into why Jetapck5 has issue (or flash totally didn’t happen)
Sdkmanager is actually equal to the flash command you are using. It is just sdkmanager run those commands for you versus you need to run those commands manually. Basically you just did a manual flash with rel-32.7.1 and sdkmanager can flash that one (jetpack4.6.1) for you too.
If you still want to check why Jetpack5 does not work, flash it with sdkmanager and give out logs. That is the real thing matters here.
or if you don’t want sdkmanager, you could use similar manul commands but with rel-35.6 or rel-35.5 package (in comparison with your r32.7.1 package).
Wayne,
Thank you for looking at my solution (which I have since rescinded). I would much rather use the SDK manager.
Windows11 running Virtualbox running Ubuntu:
When I attached the Jetson in recovery mode, the sdk manager never showed a valid SDK selection. I was hoping to download manually and then use the SDK manager to do the flash but I was never able to get that working.
Next on the Virtualbox from the command line things started working but the flash never worked. (moved to the USB stick at this point)
Bootable USB Ubuntu
Never tried the SDK manager in this configuration, but was able to complete the flash with the commands from above.
Now that I know the device is recoverable I would love to try 5.1.2 again. I was under the impression that hardware on the jetson or the devkit were not Ratchet 4 compatible. Ill give it another go with the bootable usb and sdk manager and report back.
Hi,
Just to clarify that Virtual machine was never truly supported. Some users have their own trick to make it work but we don’t really officially support that.
That is why sdkmanager cannot work on your side. A native host might be needed.
Actually, there is one point that I don’t understand here.
As I told, “flash.sh” and “sdkmanager” are basically equal in flashing Xavier NX. If you could use flash.sh to flash your board then sdkmanager can do that too.
Also, another weird point here is, I am not sure why you are talking about “USB stick” but also mentioned flash.sh. Flash.sh cannot make a USB stick.
What I feel here is you make your own theory but I don’t think your theory is correct.
Just some questions first
Did you ever use flash.sh to flash the board successfully? No matter Jetpack5 or 4.
So are you making a usb stick after you flash the board with (1)?
Phew!
I got the thing working and flashed to jetpack 5.1.4.
The first part of this thread holds true about using the serial connection to get a deeper look at what is going on as well as recovery mode to get the device out of the boot loop. From there I have been trying all sorts of stuff till I finally was able to successfully run the SDK Manager.
Since my target version was 5.1.4 I had to run the 20.04 version of the SDK Manager. That is why I was not seeing valid versions. Using the latest from the download site was my 1st mistake.
Next was running from a bootable Ubuntu USB Stick, there are certain commands and operations that requires a writeable filesystem. After flipping two older computers to Ubuntu, I finally used a more modern one with a bigger drive to run 20.04 and the SDK manager.
Once I figured all that out, things started working. But here we are, Two weeks later. I am new to the jetson world and this was slow going. Trial by fire though, I learned a lot.
Thank you @WayneWWW for all your help!