AGX Xavier - SD flash - JetPack 5.1.4

[hammer.mcmc]

Hi there,
I’m trying to flash JetPack 5.1.4 onto an SD card and have my AGX Xavier boot from it. I previously flashed the same device onto EMMC, but I quickly ran out of storage.
I found this post on the forum which seems to cover that: https://forums.developer.nvidia.com/t/nvidia-jetson-agx-xavier-expanding-storage-via-sd-card/287385
As mentioned there, I also face the fact that - after inserting the SD card (freshly formatted ext4), and connecting the Xavier to my host pc and putting it in recovery mode - the SD slot does not show up as a destination in the SDK manager (only EMMC; NVMe; USB; custom).
So I followed the steps to flash via command line described there, but after the command runs, the Xavier just keeps on booting as before from the eMMC. I am clearly missing something; below is the log - any help is much appreciated!

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk1p1 \
  -c tools/kernel_flash/flash_l4t_external.xml \
  --showlogs --network usb0 jetson-agx-xavier-devkit internal

Board ID() FAB() sku() revision()
42011 blocks

gzip: /home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
58270 blocks
20+0 records in
20+0 records out
20 bytes copied, 0,00103263 s, 19,4 kB/s
131072+0 records in
131072+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 1,3487 s, 49,8 MB/s
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
tar: Write checkpoint 10000
tar: Write checkpoint 20000
tar: Write checkpoint 30000
tar: Write checkpoint 40000
tar: Write checkpoint 50000
tar: Write checkpoint 60000
tar: Write checkpoint 70000
tar: Write checkpoint 80000
tar: Write checkpoint 90000
tar: Write checkpoint 100000
tar: Write checkpoint 110000
tar: Write checkpoint 120000
tar: Write checkpoint 130000
tar: Write checkpoint 140000
tar: Write checkpoint 150000
tar: Write checkpoint 160000
tar: Write checkpoint 170000
tar: Write checkpoint 180000
tar: Write checkpoint 190000
tar: Write checkpoint 200000
tar: Write checkpoint 210000
tar: Write checkpoint 220000
tar: Write checkpoint 230000
tar: Write checkpoint 240000
tar: Write checkpoint 250000
tar: Write checkpoint 260000
tar: Write checkpoint 270000
tar: Write checkpoint 280000
tar: Write checkpoint 290000
tar: Write checkpoint 300000
tar: Write checkpoint 310000
tar: Write checkpoint 320000
tar: Write checkpoint 330000
tar: Write checkpoint 340000
tar: Write checkpoint 350000
tar: Write checkpoint 360000
tar: Write checkpoint 370000
tar: Write checkpoint 380000
tar: Write checkpoint 390000
tar: Write checkpoint 400000
tar: Write checkpoint 410000
tar: Write checkpoint 420000
tar: Write checkpoint 430000
tar: Write checkpoint 440000
tar: Write checkpoint 450000
tar: Write checkpoint 460000
tar: Write checkpoint 470000
tar: Write checkpoint 480000
tar: Write checkpoint 490000
tar: Write checkpoint 500000
tar: Write checkpoint 510000
tar: Write checkpoint 520000
tar: Write checkpoint 530000
tar: Write checkpoint 540000
tar: Write checkpoint 550000
tar: Write checkpoint 560000
XPath set is empty
tar: Write checkpoint 10000
tar: Write checkpoint 20000
tar: Write checkpoint 30000
tar: Write checkpoint 40000
tar: Write checkpoint 50000
tar: Write checkpoint 60000
tar: Write checkpoint 70000
tar: Write checkpoint 80000
tar: Write checkpoint 90000
tar: Write checkpoint 100000
tar: Write checkpoint 110000
tar: Write checkpoint 120000
tar: Write checkpoint 130000
tar: Write checkpoint 140000
tar: Write checkpoint 150000
tar: Write checkpoint 160000
tar: Write checkpoint 170000
tar: Write checkpoint 180000
tar: Write checkpoint 190000
tar: Write checkpoint 200000
tar: Write checkpoint 210000
tar: Write checkpoint 220000
tar: Write checkpoint 230000
tar: Write checkpoint 240000
tar: Write checkpoint 250000
tar: Write checkpoint 260000
tar: Write checkpoint 270000
tar: Write checkpoint 280000
tar: Write checkpoint 290000
tar: Write checkpoint 300000
tar: Write checkpoint 310000
tar: Write checkpoint 320000
tar: Write checkpoint 330000
tar: Write checkpoint 340000
tar: Write checkpoint 350000
tar: Write checkpoint 360000
tar: Write checkpoint 370000
tar: Write checkpoint 380000
tar: Write checkpoint 390000
tar: Write checkpoint 400000
tar: Write checkpoint 410000
tar: Write checkpoint 420000
tar: Write checkpoint 430000
tar: Write checkpoint 440000
tar: Write checkpoint 450000
tar: Write checkpoint 460000
tar: Write checkpoint 470000
tar: Write checkpoint 480000
tar: Write checkpoint 490000
tar: Write checkpoint 500000
tar: Write checkpoint 510000
tar: Write checkpoint 520000
tar: Write checkpoint 530000
tar: Write checkpoint 540000
tar: Write checkpoint 550000
tar: Write checkpoint 560000
XPath set is empty
Board ID() FAB() sku() revision()
42011 blocks

gzip: /home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
58270 blocks
20+0 records in
20+0 records out
20 bytes copied, 0,000971234 s, 20,6 kB/s
131072+0 records in
131072+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 1,35859 s, 49,4 MB/s
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
58270 blocks
65261 blocks
/home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh: line 48: /home/kevin/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/Cleaning.conf: No such file or directory
Failed to restart nfs-kernel-server.service: Connection timed out
See system logs and ‘systemctl status nfs-kernel-server.service’ for details.
Cleaning up…

[infox22oo]

In case that’s a possibility for you, i can confirm that using SDKmanager to flash Jetpack 5.1.4 to a 2 TB Samsung NVME works. There is an issue with the Intel Wifi not waking up from sleep but don’t know if that’s related to the NVME or not.
Otherwise everything works very well and all standard Ubuntu updates can be applied… no more worry about running out of space.

Ubuntu also offers upgrade to 22 LTS and with the NVME there would be sufficient space for that as well but I’m sure that allowing the upgrade to new Ubuntu would brick the installation otherwise I’d think that Nvidia would offer Jetpack 6 with Ubuntu 22 for the AGX Xavier.

[hammer.mcmc]

Yes, I figured that NVME would be the next option, but I prefer SD for now as I don’t have one lying around and I read some potential issues with overheating … it’s supposed to work with SD, so I’d like some product support there …

[DavidDDD]

Hi,

Please upload the full log attached as a file for us to review.
Also please record the serial console log during the flash process and attach it too.

NVIDIA Jetson Xavier AGX

Thanks

[hammer.mcmc]

Hi,
log.txt (139.5 KB)
serial.txt (6.1 KB)
sorry for the delay; I’m attaching the full log.
Many thanks in advance!

[DavidDDD]

Hi,

What is your host pc?
Is it a native ubuntu 20.04/22.04 or a virtual machine (e.g. VMware, VirtualBox)

Thanks

[hammer.mcmc]

It’s a native Ubuntu but an older machine running 18.04 … will need an upgrade I suppose?

[DavidDDD]

Hi,

It’s fine to use ubuntu 18.04.
Also some questions to confrim

• Do you format your sd card to ext4
• What is your size for sd card

Thanks

[hammer.mcmc]

Yes, I did a fresh format to ext4 and the size is 512GB

[DavidDDD]

Hi,

Could you try to use sdk manager to flash your device to cross check whether the issue exist.
Also record a serial console log if issue exist.

Thanks

[hammer.mcmc]

Hi, I already flashed the device successfully before, using the SDK manager (on the same host machine), but that was on eMMC. SDK manager doesn’t let me select SD as a target.
Best

[DavidDDD]

Hi,
Sorry for the late response.

@hammer.mcmc

log.txt (139.5 KB)
serial.txt (6.1 KB)

We recheck your log. It’s weird with your log.
Could you confirm your device in recovery mode and reflash again ?
To check device in recovery mode, please check below link
https://docs.nvidia.com/jetson/archives/r35.6.0/DeveloperGuide/IN/QuickStart.html#to-determine-whether-the-developer-kit-is-in-force-recovery-mode

Thanks

[hammer.mcmc]

Sorry for the late reply - I will do so asap

[hammer.mcmc]

Hi, sorry for the delay, I checked the recovery mode and flashed again. Still the device boots from eMMC. I attached the log and serial output.
console.txt (204.8 KB)
serial.txt (106.7 KB)

[kayccc]

Sorry for the late response.
Is this still an issue to support? Any result can be shared?