SDMMC internal peripheral

Article purpose

The purpose of this article is to

• briefly introduce the SDMMC peripheral and its main features
• indicate the level of security supported by this hardware block
• explain how each instance can be allocated to the three runtime contexts and linked to the corresponding software components
• explain, when necessary, how to configure the SDMMC peripheral.

Peripheral overview

The SDMMC peripheral is used to interconnect STM32 MPU to SD memory cards, SDIO and MMC devices.

Features

Refer to the STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are implemented.

Security support

SDMMC1/2/3 instances are either non-secure or secure peripherals (under ETZPC control).

When an SDMMC instance is secure internal, the DMA cannot be used to perform data transfers. STMicroelectronics does not provide secure MMC driver (see below chapter)

Peripheral usage and associated software

Boot time

SDMMC1/2 instances can be used to support memory boot on SD or MMC Flash devices.

The SDMMC3 is not used at boot time.

The SDMMC instances are ordered by address in the device tree arch/arm/boot/dts/stm32mp151.dtsi| |}} arch/arm/boot/dts/stm32mp151.dtsi file: sdmmc3: sdmmc@48004000 { ... sdmmc1: sdmmc@58005000 { ... sdmmc2: sdmmc@58007000 { By default, in OpenSTLinux distribution, sdmmc3 is disabled so the sdmmc1 (SD card on Evaluation boards and Discovery kits) and sdmmc2 (eMMC on Evaluation boards and Wifi on Discovery kits) are respectively aliased to mmc0 and mmc1. If you enable sdmmc3, it will take the mmc0 alias and the aliases above will shift, so don't forget to update the Linux kernel boot command accordingly! For instance, 'root=/dev/mmcblk0p6' will become 'root=/dev/mmcblk1p6' to mount the rootfs from the sdmmc1 (SD card) when sdmmc3 is enabled.

Runtime

Overview

SDMMC1/2/3 instances can be allocated to:

• the Arm^® Cortex^®-A7 non-secure core to be controlled in Linux^® by the MMC framework

or

• the Arm^® Cortex^®-M4 to be controlled in STM32Cube MPU Package by STM32Cube SDMMC driver

Chapter #Peripheral assignment describes which peripheral instance can be assigned to which context.

Software frameworks

Domain	Peripheral	Software frameworks			Comment
		Cortex-A7 secure (OP-TEE)	Cortex-A7 non-secure (Linux)	Cortex-M4 (STM32Cube)
Mass storage	SDMMC		Linux MMC framework	STM32Cube SDMMC driver

Peripheral configuration

The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the STM32CubeMX tool for all internal peripherals, and then manually completed (particularly for external peripherals), according to the information given in the corresponding software framework article.

For Linux^® kernel configuration, please refer to SDMMC device tree configuration.

Peripheral assignment

Internal peripherals assignment table template

| rowspan="3" | Mass storage
| rowspan="3" | SDMMC
| SDMMC1
| 
| ☐
|
|
|-
| SDMMC2
| 
| ☐
| 
|
|-
| SDMMC3
| 
| ☐
| ☐
| Assignment (single choice)
|-

|}

How to go further

References

<securetransclude src="ProtectedTemplate:ArticleBasedOnModel" params="Internal peripheral article model"></securetransclude> <securetransclude src="ProtectedTemplate:PublicationRequestId" params="8316 | 2018-08-06 | AnneJ"></securetransclude>