RFS A and B parition size increase with OTA update support

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
,
1

Hi,

I am working on the jetson-agx-xavier-industrial with RFS A/B support enabled. I am looking to increase the RFS size to a maximum and reduce the data partition size to a minimum. But changing the ROOTFSSIZE variable on the file p2972-0000.conf.common emits the flash error.

I also found the following thread, which says changing the rootfs size could affect the OTA.

Whether increasing the ROOTFS size with OTA update support possible?

2

Hi,

As I know currently, if you need ROOTFS A/B support(ROOTFS redundancy), you won’t be able to increase the size of ROOTFS. But I think it’s possible if you only need an OTA update without ROOTFS redundancy.

br,
Hermes wu

4

Hi saaisanthosh.r,

Are you using the devkit or custom board for AGX Xavier Industrial?
What’s your Jetpack version in use?

Are you using the internal eMMC or connecting external NVMe SSD?
Please share the result of sudo fdisk -l on your board.

It is not supported to increase rootfs size during image-based OTA.

5

Hello Kevin,
We are facing similar issue.
We are using custom board for AGX Xavier Industrial, Jetpack 5.1.3 and using internal eMMC.
Current observation is with ROOTFS A/B enabled: ROOTFS_A and ROOTFS_B are ~13.6GB EACH. However, since the internal eMMC for Jetson Xavier Industrial is 64GB, there is another partition which has ~30GB marked as data.
The question is, can we modify the .xml files and flash using ./flash.sh script that ROOTFS_A and ROOTFS_B can be ~25GB EACH since the internal eMMC is 64GB and can support it. Is this possible and how to achieve this?

P.S.

  1. We tried modifying p2972-0000.conf.common (ROOTFSSIZE variable) from 28GiB to 50GiB but the flashing fails.
  2. We also tried passing in -S argument to ./flash.sh script and it still fails to flash.
7

That line of code is for OTA compatiblity from rel-32 to rel-35.
If you only work on rel-35, then it’s safe to remove it even in the usecase of OTA.

Please modify Linux_for_Tegra/bootloader/t186ref/cfg/flash_l4t_t194_spi_emmc_jaxi_rootfs_ab.xml to fix it.

8

Please remove the following line in flash_l4t_t194_spi_emmc_jaxi_rootfs_ab.xml.

        <partition name="RECNAME" type="kernel">
            <allocation_policy> sequential </allocation_policy>
            <filesystem_type> basic </filesystem_type>
            <size> RECSIZE </size>
-           <start_location> 0x70C100000 </start_location> <!-- aligned to 0x100000 -->
            <file_system_attribute> 0 </file_system_attribute>
            <allocation_attribute> 8 </allocation_attribute>
            <percent_reserved> 0 </percent_reserved>
            <filename> RECFILE </filename>
            <description> **Required.** Contains recovery image. </description>
        </partition>
9

Thanks for the response KevinFFF/DaveYYY!

I think you meant remove line : <start_location> 0x70C100000 </start_location>

We removed it from flash_l4t_t194_spi_emmc_jaxi_enc_rootfs_ab.xml and it works.
Just wanted to confirm that this is valid for Encrypted Rootfs and will not have any impact to current operation or OTA update in the field at some point in the future?

Thanks!

10

Yes, please modify that XML if both rootfs a/b and disk-enryption are enabled.

Please just confirm that you use the same partition layout to generate image-based OTA payload in the future.

1 Like
12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.