TrustedDomainFlavor

1. Usage[edit source]

The TrustedDomainFlavor template is used to return the term, defined with marketing team, to name the different trusted domain flavors available with STM32MP2.

Usage: {{TrustedDomainFlavor | flavor=<flavor> | outcome =<outcome>}}

Where:

<flavor> is the mandatory parameter that specifies the trusted domain flavor that must be returned. The possible values are:
- M33-TD: to use when we want to mention that boot and system resources are managed by the Arm® Cortex®-M33 processor
- A35-TD: to use when we want to mention that boot and system resources are managed by the Arm® Cortex®-A35 processor
- Any-TD: to use when we want to mention any of possible flavor or any processor managing boot and system resources
<outcome>: is an optional parameter that is useful only for <flavor> is Any-TD and that specifies whether the outcome is the flavor or the processor
- flavor: default value, to return "the trusted domain flavor"
- processor: to return "the trusted domain processor"

2. Templatedata[edit source]

This template is used to return the term, defined with marketing team, to name the different trusted domain flavors available with STM32MP2.

Template parameters
Parameter		Description	Type	Status
Flavor	`flavor`	mandatory parameter that specifies the trusted domain flavor that must be returned Suggested values `M33-TD` `A35-TD` `Any-TD`	String	required
Outcome	`outcome`	optional parameter that is useful only for <flavor> as Any-TD and that specifies whether the outcome is the flavor or the processor Suggested values `processor` `flavor` Default flavor	String	optional

3. Basic examples[edit source]

3.1. M33-TD[edit source]

You type

You get

Arm® Cortex-M33 is the processor managing boot and system resources.

{{TrustedDomainFlavor | flavor=M33-TD}}

M33-TD flavor

Arm® Cortex®-M33 is the processor managing boot and system resources. Here, template is used in a title. Purpose of this example is to check that link to this chapter is working correctly.

====Boot in case of {{TrustedDomainFlavor | flavor=M33-TD}} ====
This chapter has been created to test how the template behaves when used in title.
Test the link: [[Template:TrustedDomainFlavor#Boot_in_case_of_M33-TD_flavor]]

3.1.1. Boot in case of M33-TD flavor [edit source]

This chapter has been created to test how the template behaves when used in title. Test the link: Template:TrustedDomainFlavor#Boot_in_case_of_M33-TD_flavor

3.2. A35-TD[edit source]

You type

You get

Arm® Cortex®-A35 is the processor managing boot and system resources.

{{TrustedDomainFlavor | flavor=A35-TD}}

A35-TD flavor

Arm® Cortex®-A35 is the processor managing boot and system resources. Here, template is used in a title. Purpose of this example is to check that link to this chapter is working correctly.

====Boot in case of {{TrustedDomainFlavor | flavor=A35-TD} ====
This chapter has been created to test how the template behaves when used in title.
Test the link: [[Template:TrustedDomainFlavor#Boot_in_case_of_A35-TD_flavor]]

3.2.1. Boot in case of A35-TD flavor [edit source]

This chapter has been created to test how the template behaves when used in title. Test the link: Template:TrustedDomainFlavor#Boot_in_case_of_A35-TD_flavor

3.3. Any-TD[edit source]

3.3.1. Wished outcome is flavor[edit source]

You type

You get

Test1

{{TrustedDomainFlavor | flavor=Any-TD}}

TD flavor (A35-TD or M33-TD)

Test2

RCC RIF configuration must be done by the Secure OS of the processor with '''{{TrustedDomainFlavor | flavor=Any-TD}}'''

RCC RIF configuration must be done by the Secure OS of the processor with TD flavor (A35-TD or M33-TD)

Test3

Depending '''{{TrustedDomainFlavor | flavor=Any-TD}}''', you have 2 solutions.

Depending TD flavor (A35-TD or M33-TD) , you have 2 solutions.

3.3.2. Wished outcome is processor[edit source]

You type

You get

Test1

{{TrustedDomainFlavor | flavor=Any-TD | outcome=processor}}

TD processor (Cortex®-A35 or Cortex®-M33)

Test2

RCC RIF configuration must be done by the Secure OS of '''{{TrustedDomainFlavor | flavor=Any-TD | outcome=processor}}'''

RCC RIF configuration must be done by the Secure OS of the TD processor (Cortex®-A35 or Cortex®-M33)

Test3

HPDMA RIF configuration must be done by the Secure OS of the '''{{TrustedDomainFlavor | flavor=Any-TD | outcome=processor}}'''.<br>

HPDMA RIF configuration must be done by the Secure OS of the TD processor (Cortex®-A35 or Cortex®-M33) .

4. Concret examples[edit source]

4.1. With A35-TD[edit source]

Arm Cortex-A35
Arm Cortex-M33
Coprocessor management overview => find solution for MP15
External device tree
FMC device tree configuration => find solution for MP15
RCC internal peripheral
RIFSC internal peripheral
RISAF_internal_peripheral
Resource manager for coprocessing => find solution for MP15
STM32MP21_memory_mapping
STM32MP23-25_memory_mapping
STM32MP2_OP-TEE_overview
STM32MP2_SRAM_internal_memory
STM32MP2_VREFBUF_internal_peripheral
STM32MP2_boot_chain_overview
STM32MP2_ROM_code_resource_isolation
STM32MP2 firewall configuration
STM32_MPU_Flash_mapping
STM32 MPU Flash mapping for Android
TF-M overview

4.2. With M33-TD[edit source]

4.3. With Any-TD[edit source]

4.4. Simply removal of main processor term[edit source]

5. More examples[edit source]

You type	You get
Example when flavor parameter is not given {{TrustedDomainFlavor}}	unknown flavor
Example when flavor given in parameter is unknown {{TrustedDomainFlavor \| flavor=A35TD}}	unknown flavor
Example when outcome parameter is specified for a flavor different of Any-TD {{TrustedDomainFlavor \| flavor=A35-TD \| outcome=processor}}	A35-TD flavor
Example when outcome given in parameter is unknown (for Any-TD flavor) {{TrustedDomainFlavor \| flavor=Any-TD \| outcome=unknown}}	TD flavor (A35-TD or M33-TD)

6. Maintenance[edit source]

This template is a template common to all ST wikis.
Modifications must be done into the WikiModel. They must be reviewed by all ST wikis maintainers.
When approved, the template can be pushed/merged towards all ST wikis.

7. Code[edit source]

unknown flavor