The eMMC (internal memory of the device) is split into four physical partitions to perform the various functions of the device:

  • BOOT 1: This partition contains the Trusted Firmware-A (TF-A) image, which is the first piece of firmware that runs after the ROM loader. Its primary purpose is to perform any additional initialization required to load and authenticate all third-level firmware images into their executable RAM locations. The U-Boot environment is also stored at the end of this partition.

  • BOOT 2: This partition contains a redundand Trusted Firmware-A (TF-A) image. If the ROM loader cannot boot from BOOT 1, it will fall back to boot from BOOT 2. The redundant U-Boot environment is also stored at the end of this partition.

  • RPMB: This is the replay-protected memory-block partition, used to manage data in an authenticated and replay-protected manner. It is not currently in use.

  • User Data: Holds the U-Boot bootloader, secure-world operating system, and the normal-world operating system. It’s divided into logical partitions.

Dual boot partition table

eMMC layout for dual boot

On a dual boot-enabled system (see Prepare your target for dual boot) the user data area has the following partitions:

  • metadata1, metadata2: TF-A firmware update data. These partitions contain the Platform Security Firmware Update (PSA FWU) binary to support A/B redundant mechanism.

  • fip-a, fip-b: FIP stands for Firmware Image Package. These partitions contain a FIP image that contains the Trusted Execution Environment (TEE) firmware and the U-Boot bootloader.

  • linux_a: Contains the Linux kernel, device tree files, and U-Boot boot scripts. U-Boot reads the operating system files from this default partition.

  • linux_b: Same as linux_a (for system B).

  • rootfs_a: Linux root file system partition (for system A)

  • rootfs_b: Linux root file system partition (for system B)

  • safe/safe2: Contains the encryption key for encrypted partitions. This partition is not currently in use for the ConnectCore MP25.

  • data: Empty placeholder partition for storing user data.

Single boot partition table

eMMC layout for dual boot

The default partition table for the user data area has the following partitions:

  • metadata1, metadata2: TF-A firmware update data. These partitions contain the Platform Security Firmware Update (PSA FWU) binary to support A/B redundant mechanism.

  • fip-a, fip-b: FIP stands for Firmware Image Package. These partitions contain a FIP image that includes the Trusted Execution Environment (TEE) firmware and the U-Boot bootloader.

  • linux: Contains the Linux kernel, device tree files, and U-Boot boot scripts. U-Boot reads the operating system files from this default partition.

  • recovery: Serves as a placeholder for a recovery Linux ramdisk image that can be launched (instead of the default operating system) to perform firmware updates on the device.

  • rootfs: Linux root file system partition.

  • update: Serves as a placeholder partition to store firmware update files prior to launching a firmware update process on the device.

  • safe/safe2: Contains the encryption key for encrypted partitions. This partition is not currently in use for the ConnectCore MP25.

  • data: Serves as a placeholder partition for storing user data.