Any wks file that uses the bootimg-partition wic plugin with the intention of 
having files from the IMAGE_BOOT_FILES listing installed in it will fail.

Here is an example wic file that fails:

> 
> part  /boot  --source bootimg-partition --change-directory=boot 
> --fixed-size=512M  --fstype=vfat  --use-label  --label boot  --active 
> --align 4
> part  /      --source rootfs --exclude-path=boot/                       
> --fstype=ext4  --use-label  --label root            --align 4 
> --fixed-size=2G
> 

In this file I expect a vfat partition containing all the files listed in 
IMAGE_BOOT_FILES. This worked just fine previous to the aforementioned commit, 
but now fails with the following error:

> 
> TypeError: BootimgPartitionPlugin.do_prepare_partition() got an unexpected
> keyword argument 'sector_size'
> 

Below is the patch I used to fix it. There may be other bootimg-*.py files that 
need a similar change, but the above is the only one I was concerned with.

---
.../scripts/lib/wic/plugins/source/bootimg-partition.py         | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta-xilinx-core/scripts/lib/wic/plugins/source/bootimg-partition.py 
b/meta-xilinx-core/scripts/lib/wic/plugins/source/bootimg-partition.py
index 1071d1af..f061ebce 100644
--- a/meta-xilinx-core/scripts/lib/wic/plugins/source/bootimg-partition.py
+++ b/meta-xilinx-core/scripts/lib/wic/plugins/source/bootimg-partition.py
@@ -166,7 +166,7 @@ class BootimgPartitionPlugin(SourcePlugin):
@classmethod
def do_prepare_partition(cls, part, source_params, cr, cr_workdir,
oe_builddir, bootimg_dir, kernel_dir,
-                             rootfs_dir, native_sysroot):
+                             rootfs_dir, native_sysroot, sector_size):
"""
Called to do the actual content population for a partition i.e. it
'prepares' the partition to be incorporated into the image.
--

Thanks,
Drew

On Mon, Dec 22, 2025 at 07:22 PM, Mark Hatle wrote:

> 
> Can you provide us with an example of what you are trying to do?
> 
> Specifically an example wks file, and what you expect the output to be?
> 
> The only behavior that should have changed with the custom wic is the
> ability to change the sector size. We use this on VEK385 platform to
> generate the required 4k UFS images.
> 
> --Mark
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5813): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5813
Mute This Topic: https://lists.yoctoproject.org/mt/116833376/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to