Replies: 1 comment 1 reply
-
The answer depends on where the contents for the extra partitions comes from. If you look at how the If the images are created by some other recipe, you would still need the |
Beta Was this translation helpful? Give feedback.
-
Ok, next question. I have some img files I want to use with the custom flash layout that I figured out how to use. Including setting the IMAGE_ROOTFS size smaller to be able to leave space for my new partitions.
HINT, leave the "UDA" partition just after the APP_b, modify for size (3221225472 is what the default DATAFILE is (xxx.dataimg)) and change the allocation attribute to 0x08, then add your partitions, with your last one using 0x808 for the allocation attribute. Otherwise you have to track down where the mender layout sets the partitions or you'll be wondering why mender service and other things fail.
Anyway, how to get the xxx.img files I want to use into the proper place?
I tried a tegra-bootfiles_%.bbappend
`FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_append = "
file://xxx.img
"
BOOTBINS_append = "
xxx.img
"`
but it ends up failing:
'install: cannot stat '/home/dgoetz/yocto/src/tegra-demo-distro/jetson-tx2-asg929/tmp/work-shared/L4T-tegra-32.5.1-r0/Linux_for_Tegra/bootloader/xxx.img': No such file or directory'
I think maybe there is two places I need a bbappend, one to get the files into the bootloader folder, and the above to append the files to BOOTBINS, I'm guessing one of the other recipes gets the source (to which I'll need to append my img files) while bootfiles (well obviously now that I look at it more) moves files from bootloader to tegraflash...
Pardon my yocto naivity is showing again - further digging maybe I need to do something (by something I mean I have no idea) with image_type_tegra.bbclass overriding tegraflash_custom_post() (how?) to dump the img files in the IMGDEPLOYDIR before the zip is created...??
Thanks much
Beta Was this translation helpful? Give feedback.
All reactions