QUADSPI internal peripheral

来自百问网嵌入式Linux wiki
Wiki讨论 | 贡献2020年11月2日 (一) 11:12的版本 (创建页面,内容为“==Article purpose== The purpose of this article is to * briefly introduce the QUADSPI peripheral and its main features * indicate the level of security supported by…”)
(差异) ←上一版本 | 最后版本 (差异) | 下一版本→ (差异)

Article purpose

The purpose of this article is to

  • briefly introduce the QUADSPI 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 needed, how to configure the QUADSPI peripheral.

Peripheral overview

The Quad-SPI interface (QUADSPI peripheral) is used to interface the processor with serial NOR Flash and serial NAND Flash memories.
It supports:

  • Single, dual or quad SPI Flash memories
  • A dual-flash mode, allowing to agregate two Flash memories into a virtual single one
  • Dual data rate and memory-mapped modes.

Features

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

Security support

QUADSPI is non secure peripheral.

Using the peripheral - associated software

Boot time

QUADSPI instance is boot device that support serial boot for Flash programming with STM32CubeProgrammer.

Runtime

Overview

The QUADSPI instances can be allocated to:

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

or

Chapter #Peripheral assignment describes which peripheral instances 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 QUADSPI Linux MTD framework STM32Cube QUADSPI 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 QUADSPI device tree configuration.

Peripheral assignment

Internal peripherals assignment table template

| rowspan="1" | Mass storage
| rowspan="1" | QUADSPI
| QUADSPI
|
| 
| 
| Assignment (single choice)
|-
|}

How to go further

References


<securetransclude src="ProtectedTemplate:ArticleBasedOnModel" params="Internal peripheral article model"></securetransclude>