Hello,
I am using Yocto (Kirkstone) to develop linux for my embedded linux device, which is stm32mp135f-dk board. In Yocto build system one can set the IMAGE_ROOTFS_SIZE variable, which (along with IMAGE_ROOTFS_EXTRA_SPACE and IMAGE_OVERHEAD_FACTOR variables) controls the size of created rootfs.
I set the IMAGE_ROOTFS_SIZE to 262144 (256 MiB), and I see that when my board is being programmed using CubeProgrammer the size of rootfs image matches:
After booting the board and using df -h command the output is:
How those values could be interpreted and compared to rootfs size of 256 MiB? I don't understand why there is a size of 229.9M there and what are those following filesystems (devtmpfs, tmpfs...).
There is also second thing I am concerned about. For flashing the SD card I use the STM32_Programmer_CLI along with my .tsv file (see attached pic1 for its content). As far as I can understand, the offset values set in the .tsv control the sizes of particular partitions. What sizes (offsets) should I set for rootfs-a and rootfs-b in my .tsv file? I have noticed that in orginal ST flashcardlayout.tsv file for stm32mp135f-dk board the sizes(offsets) for fsbl1, fsbl2 etc. partitions are bigger then the images sizes that go there. And why when I use fdisk -l command on my target device it shows me only one partiton, with size of entire SD card:
Any help in understanding those topics will be much appreciated
