Adding partitions

[rsym3000]

Hi all, I am new to openembedded so I have a basic question.

I am using scarthgap-l4t-r35.x and I've modded the core-image-minimal image to support an Orin NX 8GB on a custom carrier board, using nvme external storage. The image was flashing and working with no problems, but then I went to add a partition to our flash image and I hit a wall.

I modified the tegra-storage-layout_35.6.0.bb recipe to include the following:

<partition name="Docker" type="data"> <allocation_policy> sequential </allocation_policy> <filesystem_type> basic </filesystem_type> <size> 275000000000 </size> <file_system_attribute> 0 </file_system_attribute> <allocation_attribute> 0x8 </allocation_attribute> <align_boundary> 16384 </align_boundary> <percent_reserved> 0 </percent_reserved> <description> docker partition </description> </partition> <partition name="Logs" type="data"> <allocation_policy> sequential </allocation_policy> <filesystem_type> basic </filesystem_type> <size> 75000000000 </size> <file_system_attribute> 0 </file_system_attribute> <allocation_attribute> 0x8 </allocation_attribute> <align_boundary> 16384 </align_boundary> <percent_reserved> 0 </percent_reserved> <description> log partition </description> </partition>

I can see in my build directory that this change is making its way into the flash-nvme xml file that is used during the flash process, but flashing fails:

sudo ./initrd-flash Starting at 2025-01-03T15:16:24-05:00 Machine: orin-nx-machine-name Rootfs device: nvme0n1p1 Found Jetson device in recovery mode at USB 3-11 == Step 1: Signing binaries at 2025-01-03T15:16:24-05:00 == cp: cannot stat 'signed/*': No such file or directory cp: cannot stat 'signed/flash.xml.tmp': No such file or directory

It seems something else is needed to make the changes stick. I see stuff about wic, etc. but I don't see anything in my build defined for WKS_FILE, and IMAGE_FSTYPE is 'tegraflash'. What am I missing here? Thanks for your time. Cheers

[dwalkes]

@rsym3000 I think this error can occur when the resulting xml file is invalid, including when the num_sectors
for the storage device is wrong. See https://github.com/orgs/OE4T/discussions/1300 for instance. Double check that this is correct in the resulting xml file, or attach the entire resulting file here.

[rsym3000]

Thanks. I see that my disk size declaration is not updating for some reason. I see instructions for defining TEGRA_EXTERNAL_DEVICE_SECTORS, which I defined in my tegra-storage-layout_35.6.0.bb file. Are these instructions still relevant?

[dwalkes]

The output of sh -x initrd-flash:

Sorry you'd need to use bash -x instead of sh -x since the shebang references bash.

If I open the external-flash.xml.in file in the flash package and delete only the "Logs" partition, it flashes just fine

Good clue. Based on nvidia documentation I'd probably try an empty <filename> segment next. Might also play around with the size and align it to the align_boundary in case that's somehow related. Not sure what it doesn't like though, every time I've seen this error it's been related to the storage size and it doesn't look like this is an issue based on the file you shared previously. Trying the same modified partition layout with unmodified NVIDIA jetpack is another thing you could try to see if it behaves any differently.

[rsym3000]

Thanks... I updated my previous post to include the debug output! I'll try to add the filename tags.

[rsym3000]

I played with a few of the tags and got the same output:

1. changed/removed align_boundary
2. removed unique_guid
3. added empty filename tag
4. added explicit "id" to partition tag

[dwalkes]

Relevant logs near the failure are:

+ '[' -e external-flash.xml.in ']'
+ /tmp/tmp.OwjsHAyoXU/nvflashxmlparse --extract --type rootfs --change-device-type=sdmmc_user -o external-flash.xml.tmp external-flash.xml.in
+ MACHINE=sym-orin-nx-symmach
+ BOARDID=
+ FAB=
+ BOARDSKU=
+ BOARDREV=
+ CHIPREV=
+ CHIP_SKU=
+ /tmp/tmp.OwjsHAyoXU/tegra-flash-helper.sh --no-flash --sign -u '' -v '' --usb-instance 3-3 external-flash.xml.tmp tegra234-sym-orin-nx-symmach.dtb tegra234-p3767-0001-sdram-l4t.dts gbe-uphy-config-8,hsstp-lane-map-3,hsio-uphy-config-0 boot.img symmach-image-base.ext4
cp: cannot stat 'signed/*': No such file or directory
cp: cannot stat 'signed/flash.xml.tmp': No such file or directory
sed: can't read flash.xml.tmp: No such file or directory

The fact that variables BOARDID and friends are empty, combined with the fact that the boardvars script isn't called until after this step and that doesn't match ordering in master branch logic looks suspicious. Looks like the reordering happened in 57a87f3 as a part of the update to r36.3.

You might try moving boardvars execution up before the call to tegra-flash-helper.sh to see if that makes any difference.

Modifying the call to tegra-flash-helper.sh to use bash -x and see exactly where this call fails might also be instructive.

[rsym3000]

Okay, here's another data point: I pushed the log partition node before the APP partitions, and that passes the signing stage. I'm not sure why the order here matters. I have seen others post that the new partition defs have to appear before the secondary_gpt node, but not APP_a and APP_b...