Difference between revisions of "CRYP internal peripheral"

[quality revision] [quality revision]
m
m
 


Applicable for STM32MP13x lines, STM32MP15x lines

Information about "CRYP internal peripheral" depends on the microprocessor device.

To manage this diversity and to provide the relevant level of information, several articles have been created. Please browse the one corresponding to the STM32 MPU you use.

STM32 MPU devices Associated articles
STM32MP13x STM32MP13 CRYP internal peripheral
STM32MP15x STM32MP15 CRYP internal peripheral

1 Article purpose[edit]

The purpose of this article is to:

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

2 Peripheral overview[edit]

The CRYP peripheral provides hardware acceleration to encrypt or decrypt data using the DES[1], TDES[2] or AES[3] algorithms. It also supports multiple key sizes and chaining modes.

2.1 Features[edit]

Refer to 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]

CRYP is a secure peripheral (under ETZPC control).

2.2.2 On STM32MP15x lines More info.png[edit]

CRYP1 is a secure peripheral (under ETZPC control).
CRYP2 is a non secure peripheral.

3 Peripheral usage and associated software[edit]

3.1 Boot time[edit]

3.1.1 On STM32MP13x lines Warning.png[edit]

CRYP could be used in ROM code during boot process for FSBL decryption.

3.1.2 On STM32MP15x lines More info.png[edit]

CRYP peripheral is not used during boot process.

3.2 Runtime[edit]

3.2.1 Overview[edit]

3.2.1.1 On STM32MP13x lines Warning.png[edit]

CRYP instance can be allocated to:

or

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

3.2.1.2 On STM32MP15x lines More info.png[edit]

CRYP1 instance can be allocated to:

or


CRYP2 instance can be allocated to:

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

3.2.2 Software frameworks[edit]

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

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 CRYP CRYP Assignment (single choice)
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 CRYP CRYP1 Assignment (single choice)
CRYP2

4 References[edit]




<noinclude>{{ApplicableFor
|MPUs list=STM32MP13x, STM32MP15x
|MPUs checklist=STM32MP13x, STM32MP15x
}}</noinclude>
Information about  "CRYP internal peripheral" depends on the microprocessor device.

To manage this diversity and to provide the relevant level of information, several articles have been created.
Please browse the one corresponding to the STM32 MPU you use.

{|class="st-table"
|-
! STM32 MPU devices !! Associated articles
|-
| STM32MP13x|| [[STM32MP13 CRYP internal peripheral]]
|-
| STM32MP15x|| [[STM32MP15 CRYP internal peripheral]]
|}
<noinclude>

{{ArticleBasedOnModel| Compatibility master article model}}==Article purpose==
The purpose of this article is to:
* briefly introduce the CRYP peripheral and its main features
* indicate the level of security supported by this hardware block
* explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components
* explain how to configure the CRYP peripheral.

==Peripheral overview==
The '''CRYP''' peripheral provides hardware acceleration to encrypt or decrypt data using the DES<ref>https://en.wikipedia.org/wiki/Data_Encryption_Standard</ref>, TDES<ref>https://en.wikipedia.org/wiki/Triple_DES</ref> or AES<ref>https://en.wikipedia.org/wiki/Advanced_Encryption_Standard</ref> algorithms. It also supports multiple key sizes and chaining modes.

===Features===
Refer to [[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}} ====
CRYP is a '''secure''' peripheral (under [[ETZPC_internal_peripheral|ETZPC]] control).<br>


==== On {{MicroprocessorDevice | device=15}} ====
CRYP1 is a '''secure''' peripheral (under [[ETZPC_internal_peripheral|ETZPC]] control).<br>

CRYP2 is a '''non secure''' peripheral.

==Peripheral usage and associated software==
===Boot time===
==== On {{MicroprocessorDevice | device=13}} ====
CRYP could be used in [[STM32_MPU_ROM_code_overview#FSBL_decryption_-28AES-29|ROM code]] during boot process for FSBL decryption.

==== On {{MicroprocessorDevice | device=15}} ====
CRYP peripheral is not used during boot process.

===Runtime===
====Overview====
===== On {{MicroprocessorDevice | device=13}} =====
CRYP instance can be allocated to:
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 secure core to be controlled in OP-TEE by the [[OP-TEE_overview|CRYP OP-TEE driver]]
or
* 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]]

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

===== On {{MicroprocessorDevice | device=15}} =====
CRYP1 instance can be allocated to:
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 secure core to be controlled in OP-TEE by the [[OP-TEE_overview|CRYP OP-TEE driver]]
or
* 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]]<br>

CRYP2 instance can be allocated to:
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-M4 to be controlled in STM32Cube MPU Package by [[STM32CubeMP1 architecture|STM32Cube CRYP driver]]

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

====Software frameworks====
===== On {{MicroprocessorDevice | device=13}} =====
{{:STM32MP13_internal_peripherals_software_table_template}}
 | Security
 | [[CRYP internal peripheral|CRYP]]
 | [[OP-TEE_overview|CRYP OP-TEE driver]]
 | [[Crypto_API_overview|Linux Crypto framework]]
 |
 |-
 |}

===== On {{MicroprocessorDevice | device=15}} =====
{{:STM32MP15_internal_peripherals_software_table_template}}
 | Security
 | [[CRYP internal peripheral|CRYP]]
 | [[OP-TEE_overview|CRYP OP-TEE driver]]
 | [[Crypto_API_overview|Linux Crypto framework]]
 | [[STM32CubeMP1 architecture|STM32Cube CRYP 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====
===== On {{MicroprocessorDevice | device=13}} =====
{{:STM32MP13_internal_peripherals_assignment_table_template}}<section begin=stm32mp13 />

 | rowspan="1" | Security
 | rowspan="1" | [[CRYP internal peripheral|CRYP]]
 | CRYP
 | <span title="system peripheral" style="font-size:21px"></span>

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

 | Assignment (single choice)
 |-<section end=stm32mp13 />

 |}

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

 | rowspan="2" | Security
 | rowspan="2" | [[CRYP internal peripheral|CRYP]]
 | CRYP1
 | <span title="system peripheral" style="font-size:21px"></span>

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

 | 
 | Assignment (single choice)
 |-
 | CRYP2
 | 
 | 
 | <span title="system peripheral" style="font-size:21px"></span>

 | 
 |-<section end=stm32mp15 />

 |}

==References==<references/>

<noinclude>

{{ArticleBasedOnModel| Internal peripheral article model}}
{{PublicationRequestId | 8787 | 2019-09-18 | AlainF}}[[Category:Security peripherals]]</noinclude>
(One intermediate revision by the same user not shown)
Line 1: Line 1:
  +
 
<noinclude>{{ApplicableFor
 
<noinclude>{{ApplicableFor
 
|MPUs list=STM32MP13x, STM32MP15x
 
|MPUs list=STM32MP13x, STM32MP15x
|MPUs checklist=STM32MP13x,STM32MP15x
+
|MPUs checklist=STM32MP13x, STM32MP15x
 
}}</noinclude>
 
}}</noinclude>
Information about "CRYP internal peripheral" depends on the microprocessor device.
+
==Article purpose==
  +
The purpose of this article is to:
  +
* briefly introduce the CRYP peripheral and its main features
  +
* indicate the level of security supported by this hardware block
  +
* explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components
  +
* explain how to configure the CRYP peripheral.
  +
 
  +
==Peripheral overview==
  +
The '''CRYP''' peripheral provides hardware acceleration to encrypt or decrypt data using the DES<ref>https://en.wikipedia.org/wiki/Data_Encryption_Standard</ref>, TDES<ref>https://en.wikipedia.org/wiki/Triple_DES</ref> or AES<ref>https://en.wikipedia.org/wiki/Advanced_Encryption_Standard</ref> algorithms. It also supports multiple key sizes and chaining modes.
  +
 
  +
===Features===
  +
Refer to [[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}} ====
  +
CRYP is a '''secure''' peripheral (under [[ETZPC_internal_peripheral|ETZPC]] control).<br>
  +
 
  +
==== On {{MicroprocessorDevice | device=15}} ====
  +
CRYP1 is a '''secure''' peripheral (under [[ETZPC_internal_peripheral|ETZPC]] control).<br>
  +
CRYP2 is a '''non secure''' peripheral.
  +
 
  +
==Peripheral usage and associated software==
  +
===Boot time===
  +
==== On {{MicroprocessorDevice | device=13}} ====
  +
CRYP could be used in [[STM32_MPU_ROM_code_overview#FSBL_decryption_-28AES-29|ROM code]] during boot process for FSBL decryption.
  +
 
  +
==== On {{MicroprocessorDevice | device=15}} ====
  +
CRYP peripheral is not used during boot process.
  +
 
  +
===Runtime===
  +
====Overview====
  +
===== On {{MicroprocessorDevice | device=13}} =====
  +
CRYP instance can be allocated to:
  +
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 secure core to be controlled in OP-TEE by the [[OP-TEE_overview|CRYP OP-TEE driver]]
  +
or
  +
* 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]]
  +
 
  +
Chapter [[#Peripheral assignment|Peripheral assignment]] describes which peripheral instance can be assigned to which context.
  +
 
  +
===== On {{MicroprocessorDevice | device=15}} =====
  +
CRYP1 instance can be allocated to:
  +
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A7 secure core to be controlled in OP-TEE by the [[OP-TEE_overview|CRYP OP-TEE driver]]
  +
or
  +
* 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]]
  +
<br>
  +
CRYP2 instance can be allocated to:
  +
* the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-M4 to be controlled in STM32Cube MPU Package by [[STM32CubeMP1 architecture|STM32Cube CRYP driver]]
  +
 
  +
Chapter [[#Peripheral assignment|Peripheral assignment]] describes which peripheral instance can be assigned to which context.
  +
 
  +
====Software frameworks====
  +
===== On {{MicroprocessorDevice | device=13}} =====
  +
{{:STM32MP13_internal_peripherals_software_table_template}}
  +
| Security
  +
| [[CRYP internal peripheral|CRYP]]
  +
| [[OP-TEE_overview|CRYP OP-TEE driver]]
  +
| [[Crypto_API_overview|Linux Crypto framework]]
  +
|
  +
|-
  +
|}
  +
 
  +
===== On {{MicroprocessorDevice | device=15}} =====
  +
{{:STM32MP15_internal_peripherals_software_table_template}}
  +
| Security
  +
| [[CRYP internal peripheral|CRYP]]
  +
| [[OP-TEE_overview|CRYP OP-TEE driver]]
  +
| [[Crypto_API_overview|Linux Crypto framework]]
  +
| [[STM32CubeMP1 architecture|STM32Cube CRYP 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====
  +
===== On {{MicroprocessorDevice | device=13}} =====
  +
{{:STM32MP13_internal_peripherals_assignment_table_template}}
  +
<section begin=stm32mp13 />
  +
| rowspan="1" | Security
  +
| rowspan="1" | [[CRYP internal peripheral|CRYP]]
  +
| CRYP
  +
| <span title="system peripheral" style="font-size:21px">☐</span>
  +
| <span title="system peripheral" style="font-size:21px">☐</span>
  +
| Assignment (single choice)
  +
|-
  +
<section end=stm32mp13 />
  +
|}
   
To manage this diversity and to provide the relevant level of information, several articles have been created.
+
===== On {{MicroprocessorDevice | device=15}} =====
Please browse the one corresponding to the STM32 MPU you use.
+
{{:STM32MP15_internal_peripherals_assignment_table_template}}
  +
<section begin=stm32mp15 />
  +
| rowspan="2" | Security
  +
| rowspan="2" | [[CRYP internal peripheral|CRYP]]
  +
| CRYP1
  +
| <span title="system peripheral" style="font-size:21px">☐</span>
  +
| <span title="system peripheral" style="font-size:21px">☐</span>
  +
|
  +
| Assignment (single choice)
  +
|-
  +
| CRYP2
  +
|
  +
|
  +
| <span title="system peripheral" style="font-size:21px">☐</span>
  +
|
  +
|-
  +
<section end=stm32mp15 />
  +
|}
   
{|class="st-table"
+
==References==
|-
+
<references/>
! STM32 MPU devices !! Associated articles
 
|-
 
| STM32MP13x|| [[STM32MP13 CRYP internal peripheral]]
 
|-
 
| STM32MP15x|| [[STM32MP15 CRYP internal peripheral]]
 
|}
 
   
 
<noinclude>
 
<noinclude>
{{ArticleBasedOnModel| Compatibility master article model}}
+
{{ArticleBasedOnModel| Internal peripheral article model}}
  +
{{PublicationRequestId | 8787 | 2019-09-18 | AlainF}}
 
[[Category:Security peripherals]]
 
[[Category:Security peripherals]]
 
</noinclude>
 
</noinclude>