Flashing customized rootfs

Robotics & Edge Computing Jetson Systems Jetson Thor
, ,
1

Hi NV,

We’re trying to flash customized rootfs to NVMe on Jetpack 7.1, AGX Thor custom board.
The command we used to flash is:

$ sudo SKIP_EEPROM_CHECK=1 BOARDID=3834 BOARDSKU=0008 ./l4t_initrd_flash.sh jetson-agx-thor-devkit internal

and use below command to backup_restore image :

$ sudo SKIP_EEPROM_CHECK=1 BOARDID=3834 BOARDSKU=0008 ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-agx-thor-devkit

However, the customized rootfs seems to be too large :
image

So I referred to this link [ref] to help me solve the issue. However, when I followed the instructions, I found that the bootloader/generic/cfg/ directory mentioned in the first step does not provide any XML file for t264. As a result, I’m not sure how to proceed with the next steps.

For AGX Orin:
Step1. create internal(QSPI)
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --no-flash --network usb0 jetson-agx-orin-devkit internal

Step2. create external(NVMe SSD)
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --external-only --append --network usb0 jetson-agx-orin-devkit external

Step3. flash both
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --network usb0 --flash-only

Thanks!!

4

Hi @SamM11,

The steps in the referenced topic are for AGX Orin/T234, so they cannot be used directly for AGX Thor/T264. On Thor, please use the Thor partition configuration under tools/kernel_flash/, for example flash_l4t_t264_nvme.xml. You do not need to look for a flash_t264_qspi.xml file under bootloader/generic/cfg/ for that Orin command.

The error message:

Failed. Your APPSIZE might be too small.
Error: Failed to generate images for external device

usually means the APP/rootfs partition size used for generating system.img is smaller than your customized rootfs data.

Please check the size of your customized rootfs first:

sudo du -sh rootfs

Then specify an APP size larger than that value with -S. For example, if your customized rootfs is close to 90 GiB, try -S 100GiB.

For the separate QSPI + NVMe image generation flow on Thor, please try the Thor/T264 version of the steps:

# Step 1: create QSPI image
sudo SKIP_EEPROM_CHECK=1 BOARDID=3834 BOARDSKU=0008 \
  ./l4t_initrd_flash.sh --showlogs --qspi-only --no-flash \
  jetson-agx-thor-devkit internal

# Step 2: create NVMe image with a larger APP/rootfs size
sudo SKIP_EEPROM_CHECK=1 BOARDID=3834 BOARDSKU=0008 \
  ./l4t_initrd_flash.sh --showlogs --no-flash \
  --external-device nvme0n1p1 \
  -c ./tools/kernel_flash/flash_l4t_t264_nvme.xml \
  -S <APP_SIZE> \
  --external-only --append \
  jetson-agx-thor-devkit external

# Step 3: flash the generated images
sudo SKIP_EEPROM_CHECK=1 BOARDID=3834 BOARDSKU=0008 \
  ./l4t_initrd_flash.sh --showlogs --flash-only \
  jetson-agx-thor-devkit internal

Please replace <APP_SIZE> with a value large enough for your customized rootfs, and also make sure it is smaller than the actual NVMe capacity with enough space left for the other partitions.

For reference, the Jetson Linux r38.4 Developer Guide lists flash_l4t_t264_nvme.xml and flash_l4t_t264_qspi.xml as the Thor partition configuration files, and the Thor flashing guide documents using -S to set the external APP partition size:

Hope this helps!