Unable to boot into Jetson Xavier NX after flashing Jetpack 5.1 on USB

Unable to boot into Jetson Xavier NX after flashing Jetpack 5.1 on USB

I flashed the 5.1 onto usb instead of eMMC. I was having Jetpack 5.0.2 runtime before doing this flash.

Could not detect a board is message I could see when I’m trying to reflash it with Jetpack 5.0.2 runtime.

Kindly help me with solution for this problem.

Hi rahul7manu,

Are you using the devkit or custom board?
How do you flash into external USB drive? Is there any flash log?
Please also provide the serial console log when boot up failed for further check.

1 Like

Hi KevinFFF,
Thank you for your response.
It’s a devkit.
Purchased from reComputer J2012 / J2021 - Edge AI Device with Jetson Xavier NX module – ThinkRobotics.in

I flashed onto usb using sdkmanager and gave the storage device at usb.
Unfortunately, I don’t have the flash log.

Neither am I able to boot into the board and see some boot console logs.

This is not devkit. It’s custom board by SeeedStudio.
SDKM is used for the devkit.

Please get the BSP package from your vendor first.
Then, You could use flash.sh to flash your board with custom board configuration.

1 Like

Ok, I’ll do that.
I’ll try to get the BSP package from the vendor.
Is there any other way I can get the BSP package from Nvidia website, as they’ve redirected to consult Nvidia forum for support.?

The board initially came with jetpack 4.6.3.
I had flashed jetpack 5.0.2 runtime, a few weeks back using sdkm.

I provide some jetpack release link as following:
Jetpack 4.6.3: Jetson Linux R32.7.3 | NVIDIA Developer
Jetpack 5.0.2 Jetson Linux 35.1 | NVIDIA Developer
Jetpack 5.1 Jetson Linux 35.2.1 | NVIDIA Developer

But the Driver Package(BSP) inside is for the devkit, there would not have the board configuration for your custom board.

Hi, this is the spec that I got from the vendor

Kindly guide if you can help reset it to factory settings or something like that.

I was able to boot into force recovery mode (How to place the jumpers on Xavier NX to put it in Force Recovery mode? - #4 by linuxdev)
In order to make it detectable by the sdk manager.
And then started the flashing process. But it seems to be stuck at 99%.
The storage device I selected is USB (128GB pen drive) instead of eMMC (16GB; which is insufficient for installation and our development)
Kindly support why this could be stuck and how can I possibly resolve this.

It seems the guide from Seeed telling you to use SDKM to flash their custom board.
Could you help to capture SDKM log while you flash the board?

Does the SDKM ask you to boot up the board?
SDK Component would be installed later after flash Jetson OS done and boot up.

Hi Kevin,
I paused it when the popup came asking whether to continue since the installation is taking longer than usual. Thankfully after that I’m able to boot into the board. However I need sdk components also to be installed.

I guess earlier I didn’t have enough space in my host machine where it was downloading. So, I’ve reinstalled Ubuntu 20.04 with more space in my host machine and trying to flash it again.

Kindly suggest if there’s any better approach than reflashing the entire setup. Can I just install the sdk components alone?

If you mean optional packages such as CUDA, then yes, just uncheck the parts you don’t want in sdkmanager. It doesn’t always look obvious, but you can uncheck flash, and uncheck installing anything to host PC. If you just install those optional packages, then boot the Jetson normally (not recovery mode).

1 Like

Yes, you could select the items what you want to install (which is shown in the Step 4. Review wanted components. of the guide from seeed).
and just like linuxdev said, if you want to install SDK components only, please boot up the board as normal first.

1 Like

Hi, Thanks. I’ve flashed the board with Jetpack 5.0.2 onto the USB drive by booting into force recovery mode and installed the SDK components also separately. Thanks for the precious help and support. Appreciate it.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.