Difference between revisions of "STM32MP15 Flash mapping for Android - v1.0.0"

[unchecked revision] [quality revision]
m

This is a sub-article, please refer to the main one here after: STM32MP15 Flash mapping for Android.

1 Flash partitions[edit]

The table below lists the partitions defined for STMP32MP15 boards.

Flash partitions for Android.png

2 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 white.png Information

The SD card can be unplugged from the board and inserted into a Linux® host computer for direct partitioning with Linux utilities and access to the vendor, system and userdata partitions. The file system can be Linux EXT4 or F2FS.

SD card mapping for Android.png

3 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.png


<noinclude>

This is a sub-article, please refer to the main one here after: [[STM32MP15 Flash mapping for Android]].</noinclude>

=== Flash partitions ===
The table below lists the partitions defined for STMP32MP15 boards.
[[File:Flash partitions for Android.png|750px|center|link=]]

=== SD card memory mapping ===
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|
The SD card can be unplugged from the board and inserted into a Linux<sup>&reg;</sup> host computer for direct partitioning with Linux utilities and access to the '''vendor''', '''system''' and '''userdata''' partitions. The file system can be Linux EXT4 or F2FS.
}}
[[File:SD card mapping for Android.png|750px|center|link=]]

=== eMMC memory mapping ===
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.<br />

[[File:eMMC mapping for Android.png|750px|center|link=]]
<noinclude>

[[Category:Sub-articles]]
[[Category:Android]]{{PublicationRequestId | 13246 | 2019-09-12 | AnneJ. This page is a copy of the "STM32MP15 Flash mapping for Android" page reviewed through the TLMS PR 13246}}</noinclude>
Line 28: Line 28:
 
[[Category:Sub-articles]]
 
[[Category:Sub-articles]]
 
[[Category:Android]]
 
[[Category:Android]]
  +
{{PublicationRequestId | 13246 | 2019-09-12 | AnneJ. This page is a copy of the "STM32MP15 Flash mapping for Android" page reviewed through the TLMS PR 13246}}
 
</noinclude>
 
</noinclude>