Difference between revisions of "CRC internal peripheral"

[quality revision] [quality revision]
m (Cleanup)
m
 
Applicable for STM32MP13x lines, STM32MP15x lines

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 STM32MP13 reference manuals or 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]

2.2.1 On STM32MP13x lines Warning.png[edit]

CRC is a non-secure peripheral.

2.2.2 On STM32MP15x lines More info.png[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, on STM32MP15x lines More info.png only

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

3.2.2 Software frameworks[edit]

Internal peripherals software table template

| rowspan="9" | Security | rowspan="9" | CRC |- | | Linux Crypto framework | STM32Cube CRC driver |- |}
3.2.2.1 On STM32MP13x lines Warning.png[edit]
Domain Peripheral Software components Comment
OP-TEE Linux
Security CRC Linux Crypto framework
3.2.2.2 On STM32MP15x lines More info.png[edit]
Domain Peripheral Software components Comment
OP-TEE Linux STM32Cube
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
3.2.4.1 On STM32MP13x lines Warning.png[edit]

Click on the right to expand the legend...

STM32MP13IPsOverview.png

Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:

  • means that the peripheral can be assigned () to the given runtime context.
  • means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
  • is used for system peripherals that cannot be unchecked because they are statically connected in the device.

Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP13 reference manuals.

Domain Peripheral Runtime allocation Comment
Instance Cortex-A7
secure
(OP-TEE)
Cortex-A7
non-secure
(Linux)
Security CRC CRC
3.2.4.2 On STM32MP15x lines More info.png[edit]

Click on the right to expand the legend...

STM32MP15 internal peripherals

Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:

  • means that the peripheral can be assigned () to the given runtime context.
  • means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
  • is used for system peripherals that cannot be unchecked because they are statically connected in the device.

Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP15 reference manuals.

Domain Peripheral Runtime allocation Comment
Instance Cortex-A7
secure
(OP-TEE)
Cortex-A7
non-secure
(Linux)
Cortex-M4

(STM32Cube)
Security CRC CRC1
CRC2

4 References[edit]




==<noinclude>{{ApplicableFor
|MPUs list=STM32MP13x, STM32MP15x
|MPUs checklist=STM32MP13x,STM32MP15x
}}</noinclude>

==Article purpose==
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.
==Peripheral overview==
The '''CRC''' peripheral is used to verify data transmission or storage integrity.<br />


===Features===
Refer to the [[STM32MP13 resources#Reference manuals|STM32MP13 reference manuals]] or [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete list of features, and to the software components, introduced below, to see which features are implemented.

===Security support======= On {{MicroprocessorDevice | device=13}} ====
CRC is a '''non-secure''' peripheral.
==== On {{MicroprocessorDevice | device=15}} ====CRC1 and CRC2 are '''non -secure''' peripherals.

==Peripheral usage and associated software==
===Boot time===
CRC instances are not used at boot time.

===Runtime===
====Overview====
CRC instances can be allocated to:
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 non-secure for using in Linux<sup>&reg;</sup> with [[Crypto_API_overview|Linux Crypto framework]]
or
, on {{MicroprocessorDevice | device=15}} only* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-M4 for using in STM32Cube with [[STM32CubeMP1 architecture|STM32Cube CRC driver]]

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

====Software frameworks===={{:Internal_peripherals_software_table_template}}
 | rowspan="9" | Security
 | rowspan="9" | ===== On {{MicroprocessorDevice | device=13}} =====
{{:STM32MP13 internal peripherals software table template}}
 | Security
 | [[CRC internal peripheral|CRC]]
 |
 | [[Crypto_API_overview|Linux Crypto framework]]
 |
 |-
 |}
===== On {{MicroprocessorDevice | device=15}} =====
{{:STM32MP15_internal_peripherals_software_table_template}}
 | Security
 | [[CRC internal peripheral|CRC]]
 |-
 |
 | 

 | [[Crypto_API_overview|Linux Crypto framework]]
 | [[STM32CubeMP1 architecture|STM32Cube CRC 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.

====Peripheral assignment===={{:Internal_===== On {{MicroprocessorDevice | device=13}} =====
{{:STM32MP13_internal_peripherals_assignment_table_template}}<onlyinclude><section begin=stm32mp13 />

 | rowspan="21" | Security
 | rowspan="21" | [[CRC internal peripheral|CRC]]
 | CRC1CRC

 | 
 | <span title="assignable peripheral" style="font-size:21px"></span>

 |
 |

 |-
 | CRC2
 | 
 | 
 | <span title="assignable peripheral" style="font-size:21px"></span>

 |
 |-</onlyinclude>

 |}

==How to go further==
Not applicable.
-<section end=stm32mp13 />

 |}
===== On {{MicroprocessorDevice | device=15}} =====
{{:STM32MP15_internal_peripherals_assignment_table_template}}<section begin=stm32mp15 />

 | rowspan="2" | Security
 | rowspan="2" | [[CRC internal peripheral|CRC]]
 | CRC1
 | 
 | <span title="assignable peripheral" style="font-size:21px"></span>

 |
 |
 |-
 | CRC2
 | 
 | 
 | <span title="assignable peripheral" style="font-size:21px"></span>

 |
 |-<section end=stm32mp15 />

 |}
==References==<references/>

<noinclude>

{{ArticleBasedOnModel| [[Internal peripheral article model]]}}
{{PublicationRequestId | 8786 | 2018-09-19 | AlainF}}
[[Category:Security peripherals]]</noinclude>
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  +
<noinclude>{{ApplicableFor
  +
|MPUs list=STM32MP13x, STM32MP15x
  +
|MPUs checklist=STM32MP13x,STM32MP15x
  +
}}</noinclude>
 
==Article purpose==
 
==Article purpose==
 
The purpose of this article is to
 
The purpose of this article is to
 
* briefly introduce the CRC  peripheral and its main features
 
* briefly introduce the CRC  peripheral and its main features
 
* indicate the level of security supported by this hardware block
 
* 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 each instance can be allocated to the runtime contexts and linked to the corresponding software components
 
* explain how to configure the CRC peripheral.
 
* explain how to configure the CRC peripheral.
  +
 
==Peripheral overview==
 
==Peripheral overview==
 
The '''CRC''' peripheral is used to verify data transmission or storage integrity.<br />
 
The '''CRC''' peripheral is used to verify data transmission or storage integrity.<br />
   
 
===Features===
 
===Features===
Refer to the [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete list of features, and to the software components, introduced below, to see which features are implemented.
+
Refer to the [[STM32MP13 resources#Reference manuals|STM32MP13 reference manuals]] or [[STM32MP15 resources#Reference manuals|STM32MP15 reference manuals]] for the complete list of features, and to the software components, introduced below, to see which features are implemented.
   
 
===Security support===
 
===Security support===
CRC1 and CRC2 are '''non secure''' peripherals.
+
==== On {{MicroprocessorDevice | device=13}} ====
  +
CRC is a '''non-secure''' peripheral.
  +
==== On {{MicroprocessorDevice | device=15}} ====
  +
CRC1 and CRC2 are '''non-secure''' peripherals.
   
 
==Peripheral usage and associated software==
 
==Peripheral usage and associated software==
Line 22: Line 30:
 
CRC instances can be allocated to:
 
CRC instances can be allocated to:
 
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 non-secure for using in Linux<sup>&reg;</sup> with [[Crypto_API_overview|Linux Crypto framework]]
 
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 non-secure for using in Linux<sup>&reg;</sup> with [[Crypto_API_overview|Linux Crypto framework]]
or
+
or, on {{MicroprocessorDevice | device=15}} only
 
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-M4 for using in STM32Cube with [[STM32CubeMP1 architecture|STM32Cube CRC driver]]
 
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-M4 for using in STM32Cube with [[STM32CubeMP1 architecture|STM32Cube CRC driver]]
   
Line 28: Line 36:
   
 
====Software frameworks====
 
====Software frameworks====
{{:Internal_peripherals_software_table_template}}
+
===== On {{MicroprocessorDevice | device=13}} =====
  | rowspan="9" | Security
+
{{:STM32MP13 internal peripherals software table template}}
  | rowspan="9" | [[CRC internal peripheral|CRC]]
+
  | Security
  +
  | [[CRC internal peripheral|CRC]]
  +
|
  +
| [[Crypto_API_overview|Linux Crypto framework]]
  +
|
 
  |-
 
  |-
  +
|}
  +
===== On {{MicroprocessorDevice | device=15}} =====
  +
{{:STM32MP15_internal_peripherals_software_table_template}}
  +
| Security
  +
| [[CRC internal peripheral|CRC]]
 
  |
 
  |
 
  | [[Crypto_API_overview|Linux Crypto framework]]
 
  | [[Crypto_API_overview|Linux Crypto framework]]
 
  | [[STM32CubeMP1 architecture|STM32Cube CRC driver]]
 
  | [[STM32CubeMP1 architecture|STM32Cube CRC driver]]
  +
|
 
  |-
 
  |-
 
  |}
 
  |}
Line 42: Line 60:
   
 
====Peripheral assignment====
 
====Peripheral assignment====
{{:Internal_peripherals_assignment_table_template}}
+
===== On {{MicroprocessorDevice | device=13}} =====
<onlyinclude>
+
{{:STM32MP13_internal_peripherals_assignment_table_template}}
  +
<section begin=stm32mp13 />
  +
| rowspan="1" | Security
  +
| rowspan="1" | [[CRC internal peripheral|CRC]]
  +
| CRC
  +
|
  +
| <span title="assignable peripheral" style="font-size:21px">☐</span>
  +
|
  +
|-
  +
<section end=stm32mp13 />
  +
|}
  +
===== On {{MicroprocessorDevice | device=15}} =====
  +
{{:STM32MP15_internal_peripherals_assignment_table_template}}
  +
<section begin=stm32mp15 />
 
  | rowspan="2" | Security
 
  | rowspan="2" | Security
 
  | rowspan="2" | [[CRC internal peripheral|CRC]]
 
  | rowspan="2" | [[CRC internal peripheral|CRC]]
Line 58: Line 89:
 
  |
 
  |
 
  |-
 
  |-
</onlyinclude>
+
<section end=stm32mp15 />
 
  |}
 
  |}
 
==How to go further==
 
Not applicable.
 
   
 
==References==
 
==References==
Line 68: Line 96:
   
 
<noinclude>
 
<noinclude>
{{ArticleBasedOnModel| [[Internal peripheral article model]]}}
+
{{ArticleBasedOnModel| Internal peripheral article model}}
 
{{PublicationRequestId | 8786 | 2018-09-19 | AlainF}}
 
{{PublicationRequestId | 8786 | 2018-09-19 | AlainF}}
 
[[Category:Security peripherals]]
 
[[Category:Security peripherals]]
 
</noinclude>
 
</noinclude>