Replies: 2 comments 2 replies
-
If it's during the build, what recipe was building when the error was generated? The If it's happening during flashing, then double-check the modifications to your image recipe. They look right to me, though. |
Beta Was this translation helpful? Give feedback.
-
Hi I'm facing similar error based also on the same branch. | [ 3.3129 ] tegraparser_v2 --pt flash.xml.bin --generateflashindex /home/isalm/Desktop/mender-tegra/tegra-demo-distro/build/tmp/work/jetson_xavier_nx_devkit_emmc-oe4t-linux/tegra-minimal-initramfs/1.0-r0/bup-payload/signed/flash.xml.tmp flash.idx Any help would be appreciated. This error happens when I build I'm trying to build tegrademo-mender but based on Jetpack 5 which uses l4t-35.x.x. I could build already the one which was based on l4t-32.7.x. I've used also the PR-19 which is still open. I'm just trying to generate a minimal Image which is based on kirkstone branch to migrate it with the running project. |
Beta Was this translation helpful? Give feedback.
-
Hello,
for context, I am using kirkstone with l4t 35.2.1.
I have added an extra partition (backup.ext4.img) at my flash_t194_sdmmc_rootfs_ab.xml and all was working fine. We decided that we want it new flashed every time we "do_flash.sh" so I added also a file_name for it.
I followed the steps from this older discussion #858 (comment) but without the line
TEGRA_BUPGEN_STRIP_IMG_NAMES = "app.ext4.img"
since I want it directly in the flash tarball and not in any update payload.At the rootfs_ab.xml file:
At my recept under images:
And at my image file:
I get as an error, that tegraparser_v2 gets an erro: file backup.ext4.img open failed
Am I missing some alternative variable for the tegraflash? Has anybody of you a hint?
Thanks in advance,
Alvaro.
Beta Was this translation helpful? Give feedback.
All reactions