Hi @Greetz,
Your explanation is clear to me and i understood effectively.
As you told adjust the Mender integration accordingly for my provision device, Let me tell you how initial artifact is generating for my device in wic.gz format, check below please.
1 .Their are four partitions created in initial image.
Device Start End Sectors Size Type
/dev/mmcblk0p1 34 2081 2048 1M HiFive Unleashed FSBL
/dev/mmcblk0p2 2082 10273 8192 4M HiFive Unleashed BBL
/dev/mmcblk0p3 16384 282623 266240 130M Microsoft basic data
/dev/mmcblk0p4 286720 54812671 54525952 26G Linux filesystem
here first partition contains first stage boot loader 2nd partition contains second stage boot loader 3rd contains kernel binaries and 4th partition has rootfs, so these all partitions are managed by .wks file in yocto .
2 . but first and second partitions assigned static fixed uuid so that ZSBL find to FSBL by checking the static uuid and FSBL also checking uuid for 2nd stage boot loader,
So this is my initial image content and partitions whereas mender only creating patitions like boot partition contains u-boot and active and inactive partion contains kernel+rootfs so how to manage it with my partions.
I am struggling with this please suggest me how to integrate it with mender according to my partitions to be set in mender initial image (as you told it can be any type).
Regards,
rock63