Hi! We’re using Digi embedded yocto to produce images for the ccardimx28js configuration. The bitbake process produces two images that we can flash using U-boot.
-rw-r–r-- 1 swbuild swbuild 42917888 Nov 2 15:09 dey-image-minimal-ccardimx28js-20171102190445.128.rootfs.ubifs
-rw-r–r-- 1 swbuild swbuild 44187648 Nov 2 15:09 dey-image-minimal-ccardimx28js-20171102190445.256.rootfs.ubifs
What are the differences between these two ubifs images? We have no partitions on our 256MB chips larger than 106 MiB, so does this mean that it doesn’t matter which image I use?
Those two images have the same content, but are generated for different NAND flash configurations.
The number after the timestamp refers to the “erase block size” of your flash memory and that does not have anything to do with your partition sizes.
You can verify your module’s erase block size by running “nand info” at the u-boot’s prompt.
CCARDIMX28 # nand info
Device 0: nand0, sector size 128 KiB
So for your 256MB NAND flash memory you should be using the “dey-image-minimal-ccardimx28js-20171102190445.128.rootfs.ubifs” image.