I have tried everthing over the last week to be able to flash 5.1.2 on my jetson NX
NOW NVIDIA HAS RENDERED SDK MANAGER USELESS FOR FLASHING
XAVIER NX WITH NVME.
I have been pointed to this by my previous post re this subject.
MY REPLY IS -------------------------
There is no directory nvidia/nvidia_sdk /Linux_for_Tegra on my host machine only nvidia/nvidia_sdk/
It should read “~/nvidia/nvidia_sdk/Jetpack_5.1.2_Linux_JETSON_NX_TARGETS/Linux_for_tegra/”
This is because there 2 versions of JETSON-NX (5.1.1 & 5.1.2) TARGETS
and 2 versions of AGX_ORIN (5.1.1 & 5.1.2) TARGETS
and also Jetpack_5.1.1_Linux and Jetpack_5.1.2_linux directories
I have also tried editing
ITS NEVER WORKED.
I HAVE BEEN INVOLVED IN THE COMPUTER INDUSTRY FOR THE LAST 50 YEARS AND NEVER HAD SO MANY DIFFICULTIES JUST TO UPGRADE
Calm down, dude.
Capital letters make it hard to read the post.
Just for your information, Xavier NX needs the SD card to be flashed and inserted for it to boot up normally.
You may run this command inside Linux_for_Tegra to flash both bootloader on QSPI and SD card and rootfs on NVMe SSD:
Thanks for yor reply
Sorry about the capitals but it is just frustration not getting any explainantion to why jetpack 5.1.1 works and 5.1.2 does not when upgrading.
I am at a loss to understand why I need a sd card for
xavier NX to proceed to upgrade to 5.1.2 as it has not been necessary for previous version of Jetpack ie 5.1.1 which is now installed and working fine.
What is the point ot the grub bootloader where you stipulate what perhipheral you want to boot from ?
Why does sdk manager ask what pheripheral you want to flash too?
Before I try the command you have given me , I have inserted a sd card which comes up just as another device (I have just taken the sd card from a jetson nano I think it has jetpack 4.6 installed on it)
so 5.1.1 is not looking at the sd card.
Sorry to be a pain but I would be gratfull if you could answer the above questions, and given the above senario how do I proceed to upgrade to 5.1.2.
Thanks in anticipation
The reason is that for Xavier NX, parts of bootloader stuff is stored on SD cards, instead of entirely on the QSPI memory. I’m not sure how you flash the device before, but I’m 100% sure the system will fail to boot up with the following message when the SD card is not present, and it’s the same for both L4T 35.3.1 and L4T 35.4.1.
I flashed the xavier nx manually to nvme using sdk manager with system reset cable on 9 & 10.
When the system is flashed the xavier nx start up procedure
goes through language etc etc and then asked the size of your file system
which in my case is 490 odd gb and then continues on.
When trying to flash 5.1.2 the same way the file system question does not come up when the xavier nx starts up .
So I’m also 100% sure that prior to 5.1.2 and after 5.0.0 I have not needed the sd Card.
Is there any file on my system or logs I can show you that might show some light on this anomaly
I don’t have an issue
I have reset and flashed 5.1.1 yesterday and I am a little reluctant to upgrade to 5.1.2 as I have and had a working system. But as I have a agx orin 64gb I will now give your command a go.
Watch This SPace
YOU WILL BE PLEASED TO KNOW I HAVE A FRESH INSTALL OF JETPACK 5.1.2 ON XAVIER NX WITH SD CARD !!!
You will be pleased to know I have a fresh install of Jetpack 5.1.2 on xavier nx with a sd card.!!!
Thank you for your help.
My next question for the next upgrade I do not want to wipe out the NVME of my work. How can I succesfully upgrade ?
I had severe issues with the UEFI BIOS being stuck in an upgrade process every time the Jetson Xavier NX would boot after I used the debian update instructions (so using sudo apt dist-upgrade to get 5.1.2 on my 5.1.1 NX).
I also ran into the APP partition not getting sized right by SDK manager while installing the 5.1.2 version of JetPack with it.
I did manage in the end to get it to install JetPack 5.1.2 with the use of the full capacity of my SSD through SDK Manager, by modifying one of the scripts. The entire saga (with instructions) can be found here:
Since this does wipe the contents of the SSD, I would advise you to backup any important data from your SSD before attempting my solution!