Thus, is sdk manager able to flash Jetpack 5.1.2 to SSD?
When I installed Jetpack 5.1.2 from SDKmanager to SSD, the installation error occurred regardless of whether or not Ethernet was connected.
Attached are the logs of the installation from SDKmanager to SSD when Flash.sh and p3701.conf.common are rewritten.
I don’t know if this is related, but I am contacting you just in case.
After a failed jetson install on SSD, AGX ORIN Devkit may boot up after 30 seconds or so when AGX ORIN Devkit is put into recovery mode.
It is booted by boot loader which is loaded later.
For example:
EMMC
SSD
In this case, it boots with 2.SSD jetson.
(The screen remains dark because it is SSD…)
The document you gave as a reference is r36.4 and 5.1.2 is r35.4.1, so either it is not supported or I am not prepared enough. Could you please let me know how to improve it?
Also, here is what I have independently implemented.
Since you had previously mentioned that the problem was due to a malfunctioning SDK, I prepared a new Ubuntu PC.
I installed the SDK and performed the 5.1.2 installation, which was successful.
I apologize for the inconvenience, but I would like to improve the malfunction of the SDK. Reinstalling did not change the problem, so if there is another way, please let I know.
There is an addendum to the following information.
Also, here is what I have independently implemented.
Since you had previously mentioned that the problem was due to a malfunctioning SDK, I prepared a new Ubuntu PC.
I installed the SDK and performed the 5.1.2 installation, which was successful.
By using a newly prepared ubuntuPC, I was able to successfully install Jetson 5.1.2 on the AGX ORIN Devkit SSD.
Could you update your sdk manager first?
And check whether the issue exist during flash AGX Orin in Jetson 5.1.2.
Also attach .zip file and uart log for us to review.
If you think might takes some time for above actions, you could reinstall the ubuntu 20.04 with clean environment.
It seems like the issue still related to the smaller size emmc.
Could you check your num_sectors value whether is 124190720 in /Linux_for_Tegra/bootloader/t186ref/cfg/flash_t234_qspi_sdmmc.xml
It’s different after edit the num_sectors.
From your previous log NV_L4T_FLASH_JETSON_LINUX_COMP.log
11:50:39.833 - Info: [ 15]: l4t_flash_from_kernel: Error: partprobe failed. This indicates that:
11:50:39.833 - Info: - the xml indicates the gpt is larger than the device storage
11:50:39.833 - Info: - the xml might be invalid
11:50:39.833 - Info: - the device might have a problem.
11:50:39.833 - Info: Please make correction.
It solve the smaller size emmc but hit another issue.
Do you have other NVMe to cross check whether the issue exist?
Also please format NVMe to ext4 before flashing.
1/29
I couldn’t figure out the cause, so I overwroteflash.sh p3701.conf.common flash_t234_qspi_sdmmc.xmlfrom a computer that I had successfully installed before.
After overwriting the three files, I installed 5.1.2 on the SSD for cross-checking, and it succeeded.
The num_sectors in flash_t234_qspi_sdmmc.xml was before the rewrite, so I may have deleted some necessary data when rewriting flash.sh p3701.conf.common…
I apologize for the inconvenience.
Yes, it is operating without problems.
Thank you very much for fixing the problem.
I will contact you again if I have any further questions,
Thank you again in that case.