Customize partition with size 400MB fail

Hi,
We want new partition for log with 400MB(419430400),
add the item log ater the APP at the file: bootloader/t186ref/cfg/flash_t194_sdmmc.xml

    <partition name="APP" 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>
        <unique_guid> APPUUID </unique_guid>
        <filename> APPFILE </filename>
        <description> **Required.** Contains the rootfs. This partition must be defined after
          `primary_gpt` so it can be accessed as the fixed known special device
          `/dev/mmcblk0p1`. </description>
    </partition>

    <partition name="log" type="data">
        <allocation_policy> sequential </allocation_policy>
        <filesystem_type> basic </filesystem_type>
        <size> 419430400 </size>
        <file_system_attribute> 0 </file_system_attribute>
        <allocation_attribute> 0x8 </allocation_attribute>
        <align_boundary> 4096 </align_boundary>
        <percent_reserved> 0 </percent_reserved>
        <description> /dev/mmcblk0p2 </description>
    </partition>

flash.sh sudo ./flash.sh -r jetson-xavier mmcblk0p1

[ 13.2913 ] tegradevflash_v2 --oem platformdetails storage storage_info.bin
[ 13.2942 ] Bootloader version 01.00.0000
[ 13.2978 ] Saved platform info in storage_info.bin
[ 13.2994 ]
[ 13.2995 ] Flashing the device
[ 13.3040 ] tegraparser_v2 --storageinfo storage_info.bin --generategpt --pt flash.xml.bin
[ 13.3069 ] End sector for RECROOTFS, expected at: 61079518, actual: 61233839
[ 13.3078 ]
Error: Return value 4
Command tegraparser_v2 --storageinfo storage_info.bin --generategpt --pt flash.xml.bin
Failed flashing t186ref.

but we change the partition log size from 400MB to 200MB(209715200), no any errors.

thanks,

when we decrease the APPSIZE, works well.

thanks.

Good, thanks for the update!

default APPSIZE 28G, 0x700000000, change to 26G 0x680000000

    <partition name="APP" type="data">
        <allocation_policy> sequential </allocation_policy>
        <filesystem_type> basic </filesystem_type>
        <size> 0x680000000 </size>

@ host
[ 17.2345 ] Writing partition APP with system.img
[ 1032.8992 ] ] 000%

@ Jetson uart:
[0904.449] I> Writing APP partition.
[0904.514] E> NV3P_SERVER: Could not write 1048576 bytes.

restore to 28G 0x700000000, write system.img ok, but previous issue still exist.

any ideas? thanks.

chanage APP size 0x600000000, doesn’t work too.

same as
@ Jetson uart:
[0904.449] I> Writing APP partition.
[0904.514] E> NV3P_SERVER: Could not write 1048576 bytes.

so should not change the APP’s size, only APPSIZE can work?

bootloader/t186ref/cfg/flash_t194_sdmmc.xml
keep the APPSIZE, not touch the APPSIZE

p2972-0000.conf.common
change the ROOTFSSIZE from 28GiB to 26Gib

sudo ./flash.sh -r jetson-xavier mmcblk0p1 fail
@ Jetson uart:
[0904.449] I> Writing APP partition.
[0904.514] E> NV3P_SERVER: Could not write 1048576 bytes.

but sudo ./flash.sh jetson-xavier mmcblk0p1 succeed

“-r” means you will reuse the previous system.img. However, since you already configured a new APP size, the old system image size may not match to your current need. Thus, “-r” cannot be used here.

@WayneWWW thanks,

ls system.img show it’s size only 12G which is not the exact same as the old ROOTFSSIZE(28GiB).
I consider there is no need to make new system.img when I change the ROOTFSSIZE from 28GiB to 26Gib.