Does the behaviour for the different eMMC areas of the Linux BSP v2.7b4 boot area partition 1/primary eMMC boot sector, boot area partition 2 aka secondary eMMC boot sector and user area aka general purpose eMMC region differ w.r.t. reliability of data storage/flashing, etc. when flashed onto the Apalis TK1 2GB v1.2A? The areas use different partitions which make them behave differently from a configuration/formatting point of view. But is there something to be considered from a HW feature support point of view w.r.t. the eMMC locations they are written to?
This eMMC layout is from update.sh
:
# The eMMC layout used is:
#
# boot area partition 1 aka primary eMMC boot sector:
# with cbootimage containing BCT and U-Boot boot loader and the U-Boot
# environment before the configblock at the end of that boot area partition
#
# boot area partition 2 aka secondary eMMC boot sector:
# reserved
#
# user area aka general purpose eMMC region:
#
# 0 -> IMAGE_ROOTFS_ALIGNMENT - reserved (not partitioned)
# IMAGE_ROOTFS_ALIGNMENT -> BOOT_SPACE - kernel and other data
# BOOT_SPACE -> SDIMG_SIZE - rootfs
#
# 4MiB 16MiB SDIMG_ROOTFS
# <-----------------------> <----------> <---------------------->
# ------------------------ ------------ ------------------------
# | IMAGE_ROOTFS_ALIGNMENT | BOOT_SPACE | ROOTFS_SIZE |
# ------------------------ ------------ ------------------------
# ^ ^ ^ ^
# | | | |
# 0 4MiB 4MiB + 16MiB EMMC_SIZE