Hi @mmichala,
Thanks for your feedback,
On my side, it seems PARTUUID returned by blkid is similar with guid returned in u-boot (mmc dev 0 ; mmc part), but /dev/disk/by-partuuid is different.
I will dig into this later, as you're not blocked anymore....
Hello @mmichala,
I fixed partUUID issue seen with CubeProgrammer:
- I've created a tsv file for eMMC on top of stm32mp257f-ev1 board (with bootfs-a and bootfs-b)
- The default partUUID (e91c4e10-16e6-4c0e-bd0e-77becf4a3582) was set for the partitio...
Hello @mmichala,
Instead of configuring an hardcoded PARTUUID for rootfs-b, I think it's better to read it at runtime (with blkid) in order to update the kernel command line accordingly.
I updated the meta-st-ota layer with this correction.
BR,
C...
Hello @mmichala,
I guess you use meta-st-ota layer : to avoid that problem, I would recommand to flash the image into the sdcard with create_sdcard_from_flashlayout.sh script available in the layer, where bootfs-b UUID is managed.
Neverthless, I ta...
Hello @anpa,
Some actions have been taken to upstream 157f boards (ev1 and dk2), but I can't tell you on which tag it will be merged.
The recommandation is to use stm32mp branches provided through ecosystem releases where all non-yet-upstreamed patch...
