STM32MP15 Flash mapping for Android

Revision as of 06:29, 12 June 2020 by Nicolas Louboutin (talk | contribs) (Supported Flash memory technologies)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

1 Supported Flash memory technologies[edit]

The STM32MP15 boards support different kind of Flash memories:

  • A SD card connected to an SDMMC interface, which is present on Evaluation board.
  • An eMMC connected to an SDMMC interface, which is present on Evaluation board only.

The next section lists all the partitions used on STM32MP15 boards (size, name and content). The following sections show how they are mapped on the different types of Flash memories.

2 Flash partitions[edit]

The table below lists the partitions defined for STMP32MP15 boards.

Flash partitions for Android Super.png

3 SD card memory mapping[edit]

The SD card has to be partitioned with GPT format to be recognized by STM32MP15 microcontrollers. The easiest way to achieve this is to use STM32CubeProgrammer.

The ROM code searches the GPT entries which name begins with "fsbl", such as fsbl1 and fsbl2.

Info.png

The SD card can be unplugged from the board and inserted into a Linux® host computer for direct partitioning with Linux utilities.

SD card mapping for Android Super.png

4 eMMC memory mapping[edit]

The eMMC embeds four physical partitions:

  • Boot area partition 1: it is used to store the first copy of the FSBL.
  • Boot area partition 2: it is used to store the second copy of the FSBL.
  • User data area: it is formatted with GPT partitioning and used to store all remaining partitions.
  • Replay protected memory block (RPMB): this partition is not shown in the figure below since it is not involved in the current boot chain.

STM32CubeProgrammer has to be used to prepare the eMMC with the layout shown below and to populate each partition.

EMMC mapping for Android Super.png