File system redundancy

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Hi,

The manual states “File system redundancy is disabled by default because only one file system partition (APP) is created. NVIDIA can provide guidance on enabling file system redundancy.” so here I am.

I have created 3 new partitions

<partition name="APP_b" type="data">
    <allocation_policy> sequential </allocation_policy>
    <filesystem_type> basic </filesystem_type>
    <size> APPSIZE </size>
    <file_system_attribute> 0 </file_system_attribute>
    <allocation_attribute> 0x8 </allocation_attribute>
    <align_boundary> 4096 </align_boundary>
    <percent_reserved> 0 </percent_reserved>
    <filename> APPFILE </filename>
</partition>
<partition name="overlay" type="data">
    <allocation_policy> sequential </allocation_policy>
    <filesystem_type> basic </filesystem_type>
    <size> 8053063680 </size>
    <file_system_attribute> 0 </file_system_attribute>
    <allocation_attribute> 0x8 </allocation_attribute>
    <percent_reserved> 0 </percent_reserved>
    <filename> overlay.img </filename>
</partition>
<partition name="overlay_b" type="data">
    <allocation_policy> sequential </allocation_policy>
    <filesystem_type> basic </filesystem_type>
    <size> 8053063680 </size>
    <file_system_attribute> 0 </file_system_attribute>
    <allocation_attribute> 0x808 </allocation_attribute>
    <percent_reserved> 0 </percent_reserved>
    <filename> overlay.img </filename>
</partition>

APP_b for the second slot file system image. overlay and overlay_b are used for factory reset and overlaid on top of their respective file system. There’s 2 of them to allow for user settings migration script during the updates.

Where can I assign the partition label to a partition number so that the correct partition number would be set in the boot parameters?

Currently u-boot sets the root partition as

root=/dev/mmcblk${@uboot_var('devnum')}p${@uboot_var('distro_bootpart')}

and even if the second slot is enabled, /dev/mmcblk0p1 still is the root device while it should be in my case /dev/mmcblk0p32

Thanks,

3

Please refer to this thread.

4

@WayneWWW, where do I find the cboot sources for TX2. I’m using L4T 32.2 and the sources seem to be for Xavier only.

1 Like
5

Unfortunately, there is no rel32 cboot src released for TX2 yet. We are still driving the release process.

6

@WayneWWW I used the 28.3.0 source on TX2 and I can boot.

With CONFIG_ENABLE_A_B_ROOTFS enabled, which copy of u-boot (which partition) cboot loads?

7

The uboot partition on tx2 is “kernel”.

8

OK, and cboot will automatically load kernel_b for slot 1 or do I have to implement it somehow?