Issue creating application partition using remaining SSD space during flash/build process

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi everyone,

We are trying to create a custom application partition that utilizes all remaining space on the SSD during the OS image build and flashing process. However, we are encountering issues where the configuration file doesn’t seem to be applied correctly and the partition is either not created or fails to resize.

Module: Jetson Orin NX

Flashing Command used: ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml -S 40GiB -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal

The Problem:

Despite following the NVIDIA documentation regarding custom partition layouts, the build process ignores our defined configuration. Specifically:

The new partition is not appearing in the final layout.

The num_sectors or size parameters for “APP” or custom partitions don’t seem to trigger the “fill remaining space” behavior as expected.

We’ve tried the standard resizing commands mentioned in the docs, but they return errors during the flash stage.

3

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context and the question, it appears that the issue lies in the configuration file not being applied correctly during the OS image build and flashing process. Here are some potential solutions and comparisons:

  1. Verify the configuration file: Ensure that the configuration file is correctly formatted and contains the necessary parameters. In the provided context, the disk_enc_enable and EMMC_CFG settings are used to enable disk encryption and specify the partition layout file. Compare your configuration file with the example provided in the context:

disk_enc_enable=1;
EMMC_CFG=flash_l4t_t234_qspi_sdmmc_enc_rfs.xml;

   Make sure that the `EMMC_CFG` parameter points to the correct partition layout file.

2. **Check the partition layout file**: Verify that the partition layout file (e.g., `flash_l4t_t234_qspi_sdmmc_enc_rfs.xml`) contains the correct settings for the custom application partition. Ensure that the `numsectors` or `size` parameters are set correctly to trigger the "fill remaining space" behavior.

3. **Use the correct flashing command**: Compare the flashing command used in the question with the recommended command in the NVIDIA documentation. The command used in the question is:

ROOTFSAB1 tools/kernels/flash_l4t_initrd.sh external device nvme0n1p1 c tools/kernels/flash_l4t_nvme_rootfs_ab.xml S 40GiB p c bootloader/generic.cfg flash_t234_qspi.xml showlogs network usb0 jetsonorinnanodevkit internal

   Ensure that the correct partition layout file is specified in the command.

4. **Resizing commands**: If the resizing commands mentioned in the documentation return errors during the flash stage, try using alternative methods to resize the partition. For example, you can use the `resize2fs` command to resize the file system after flashing.

5. **Jetson Orin NX vs. Jetson Orin Nano**: Although the question mentions the Jetson Orin Nano, the flashing command used is for the Jetson Orin NX. Ensure that the correct flashing command and configuration file are used for the Jetson Orin Nano.

6. **Comparison with the provided context**: The provided context mentions the `APP_ENC` partition's encrypted attribute, which indicates that the partition is encrypted. However, the question does not mention encryption. If encryption is not required, ensure that the configuration file and partition layout file are set up correctly for a non-encrypted partition.

By verifying the configuration file, partition layout file, and flashing command, and comparing the setup with the provided context, you should be able to resolve the issue and create a custom application partition that utilizes all remaining space on the SSD.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
6

hello sunny.QHT,

please see-also Topic 280983 and Topic 349242 for reference.

you may also note that..
since you’ve ROOTFS_AB=1 and also the -S xxxGiB enabled.
the -S option you’ve set to 40GiB, it means the root file system size for A and B.
hence, the EXT_NUM_SECTORS size need set to A+B=40+40=80 for your use-case.