CRC internal peripheral

Revision as of 15:23, 21 January 2020 by Registered User (Software frameworks)

1 Article purpose[edit]

The purpose of this article is to

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

2 Peripheral overview[edit]

The CRC peripheral is used to verify data transmission or storage integrity.

2.1 Features[edit]

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.

2.2 Security support[edit]

CRC1 and CRC2 are non secure peripherals.

3 Peripheral usage and associated software[edit]

3.1 Boot time[edit]

CRC instances are not used at boot time.

3.2 Runtime[edit]

3.2.1 Overview[edit]

CRC instances can be allocated to:

or

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

3.2.2 Software frameworks[edit]

Internal peripherals software table template

| Security
| CRC
|
| Linux Crypto framework
| STM32Cube CRC driver
|
|-
|}

3.2.3 Peripheral configuration[edit]

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.

3.2.4 Peripheral assignment[edit]

Internal peripherals assignment table template

| rowspan="2" | Security
| rowspan="2" | CRC
| CRC1
| 
| 
|
|
|-
| CRC2
| 
| 
| 
|
|-
|}

4 How to go further[edit]

Not applicable.

5 References[edit]