Difference between revisions of "Boot chain overview"

[quality revision] [quality revision]
m (Overview)
m

Template:ArticleMainWriter Template:ArticleApprovedVersion

1 Generic boot sequence[edit]

1.1 Linux start-up[edit]

Starting Linux® on a processor is done in several steps that progressively initialize the platform peripherals and memories. Those These steps are explained in the following parapraphs paragraphs and illustrated by the diagram on the right, which also gives typical memory sizes for each stage.

Generic Linux boot chain
Generic Linux boot chain

1.1.1 ROM code[edit]

The ROM code is a piece of software that takes its name from the read only memory (ROM) where it is stored. It fits in a few tens of Kbytes and maps its data in embedded RAM. It is the first code executed by the processor, and it embeds all the logic needed to select the boot device (serial link or Flash) from where which the first-stage boot loader (FSBL) is loaded to the embedded RAM.
Most products require to trust the application that is running on the device and the ROM code is the first link in the chain of trust that must be established across all started components: this trust is established by authenticating the FSBL before starting it. In turn, the FSBL and each following component will authenticate the next one, up to a level defined by the product manufacturer.

1.1.2 First stage boot loader (FSBL)[edit]

Among other things, the first stage boot loader (FSBL) initializes (part of) the clock tree and the external RAM controller. Finally, the FSBL loads the second-stage boot loader (SSBL) into the external RAM and jumps to it.

The Trusted Firmware-A (TF-A) and U-Boot secondary program loader (U-Boot SPL) are two possible FSBLs.

1.1.3 Second-stage boot loader (SSBL)[edit]

The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on), that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (by showing a splash screen to the user). U-Boot is commonly used as a Linux bootloader in embedded systems.

1.1.4 Linux kernel space[edit]

The Linux kernel is started in the external memory and it initializes all the peripheral drivers that are needed on the platform.

1.1.5 Linux user space[edit]

Finally, the Linux kernel hands control to the user space starting the init process that runs all initialization actions described in the root file system (rootfs), including the application framework that exposes the user interface (UI) to the user.

1.2 Other services start-up[edit]

STM32MP boot chain
STM32MP boot chain

In addition to  Linux  startup, the boot chain can also be responsible for the start-up of other servicesinstalls the secure monitor and may support coprocessor firmware loading.

For instance, for the STM32MP15, the boot chain starts:

  • the  secure monitor , supported by the Arm® Cortex®-A secure context (TrustZone). Examples of use of a secure monitor are: user authentication, key storage, and tampering management.
  • the  coprocessor  firmware, running on the Arm Cortex-M core. This can be used to offload real-time or low-power services.


The dotted lines in the diagram on the right mean that:

  • the  secure monitor  can be started by the first stage boot loader (FSBL) or the second stage boot loader (SSBL)the  coprocessor  can be started by the second stage boot loader (SSBL), known as “early boot”, or Linux kernel


2 STM32MP boot sequence[edit]

2.1 Diagram frames and legend[edit]

STM32MP hardware execution contexts
STM32MP hardware execution contexts

The hardware execution contexts are shown with vertical frames in the boot diagrams:

  • the  Arm Cortex-A secure  context, in pink
  • the  Arm Cortex-A non-secure  context, in dark blue
  • the  Arm Cortex-M  context, in light blue

The horizontal frame in:

  • the bottom part shows the boot chain
  • the top part shows the runtime services, that are installed by the boot chain


Boot chain diagrams legend
Boot chain diagrams legend

The legend on the right shows how information about the several various components shown in the frames, and which are involved in the boot process, is highlighted:

  • The box color shows the component source code origin
  • The arrows show the loading and calling actions between the components
  • The Cube logo is used on the top right corner of components that can be configured via STM32CubeMX
  • The lock show the components that can be authenticated during the boot process


2.2 STM32MP STM32MP15 boot chainschain[edit]

2.2.1 Overview[edit]

Zoom out to STM32MPU Embedded Software

Two different STM32MP15 boot chain flavors are supported on STM32MP processors with STM32MPU Embedded Software:

The trusted boot chain

uses Trusted Firmware-A (TF-A) as the FSBL

, so it should

in order to fulfill all the requirements for security-sensitive customers, and it uses U-Boot as the SSBL. Note that the authentication is optional with this boot chain, so it can run on any

STM32MP

2.2.2 STM32MP15 case[edit]

2.2.2.1 Overview[edit]

The diagrams below illustrate the two boot chain flavors availble on the STM32MP15: the trusted boot chain and the basic boot chain.

Trusted boot chain
File:Basic boot chain.png
Basic boot chain
Notes:
  • The second-stage boot loader (SSBL) can run in ARM Secure/Trustzone mode (basic boot chain) or Non-Secure mode (trusted boot chain).
  • The STM32MP

    STM32MP15 device security variant (that is, with or without the Secure boot).

    The trusted boot chain is the default solution delivered by STMicroelectronics, with a complete feature set (for example, all Flash devices are supported).
  • The basic boot chain is also available to generate both the FSBL (U-Boot SPL) and SSBL (U-Boot) from a unique piece of source code, U-Boot. STMicroelectronics upstreams the Basic boot chain with a limited number of features, and the U-Boot community is able to extend this.

  • Refer to the security overview for an introduction of the secure features available on STM32MP15, from the secure boot up to trusted applications execution.

    STM32MP15 boot chain


    Note:

    2.2.2

    .2

    ROM code[edit]

    The ROM code starts the processor in secure mode. It supports the FSBL authentication and offers authentication services to the FSBL.

    2.2.

    2.

    3 First stage boot loader (FSBL)[edit]

    The FSBL is executed from the SYSRAM.
    Among other things, this boot loader initializes (part of) the clock tree and the DDR controller. Finally, the FSBL loads the second-stage boot loader (SSBL) into the DDR external RAM and jumps to it.
    The boot loader stage 2, so called TF-A BL2, is the Trusted Firmware-A (TF-A) and U-Boot secondary program loader (U-Boot SPL) are the two possible FSBLs on the STM32MP15, for the trusted boot chain and the basic boot chain, respectively binary used as FSBL on STM32MP15.

    2.2.

    2.

    4 Second stage boot loader (SSBL)[edit]

    The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on) that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (showing a splash screen to the user).
    U-Boot is commonly used as a bootloader in embedded software and it is the one used on STM32MP15.

    2.2.

    2.

    5 Linux[edit]

    Linux® is OS is loaded in DDR by U-Boot and executed in the non-secure context.

    2.2.

    2.

    6 Secure OS / Secure Monitor[edit]

    The Cortex-A7 secure world can implement a minimal secure monitor (from TF-A SP-MIN or U-Boot) or a real secure OS, such as OP-TEE.

    2.2.

    2.

    7 Coprocessor firmware[edit]

    The coprocessor STM32Cube firmware can be started at the SSBL level by U-Boot with the remoteproc feature (rproc command) or, later, by Linux remoteproc framework, depending on the application startup time-targets.


    <noinclude>
    
    {{ArticleMainWriter | GeraldB}}
    {{ArticleApprovedVersion | GeraldB | PatrickD, LionelD | GeraldB - 24Jan'18 | PhilipS - 14Nov'18 - 9286 | 27Sep'18}}
    [[Category:Platform boot|0]]</noinclude>
    
    __FORCETOC__
    __FORCETOC__== Generic boot sequence ==
    === Linux start-up ===
    Starting Linux<sup>&reg;</sup> on a processor is done in several steps that progressively initialize the platform peripherals and memories. ThoseThese steps are 
    explained in the following parapraphsparagraphs and illustrated by the diagram on the right, which also gives typical memory sizes for each stage.
    [[File: Boot_chains_overview.png|thumb|upright=4|right|center|link=|Generic Linux boot chain]]
    
    ==== ROM code ====
    The ROM code is a piece of software that takes its name from the read only memory (ROM) where it is stored. It fits in a few tens of Kbytes and maps its data in embedded RAM. It is the first code executed by the processor, and it embeds all the logic needed to select the boot device (serial link or Flash) from wherewhich the first-stage boot loader (FSBL) is loaded to the embedded RAM.
    
    <br>
    
    Most products require to trust the application that is running on the device and the ROM code is the first link in the chain of trust that must be established across all started components: this trust is established by authenticating the FSBL before starting it. In turn, the FSBL and each following component will authenticate the next one, up to a level defined by the product manufacturer.
    ==== First stage boot loader (FSBL) ====
    Among other things, the first stage boot loader (FSBL) initializes (part of) the clock tree and the external RAM controller. Finally, the FSBL loads the second-stage boot loader (SSBL) into the external RAM and jumps to it.<br />
    
    
    The [[TF-A overview|Trusted Firmware-A (TF-A)]] and [[U-Boot overview|U-Boot]] secondary program loader (U-Boot SPL) are two possible FSBLs.
    
    ==== Second-stage boot loader (SSBL) ====
    The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on), that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (by showing a splash screen to the user). [[U-Boot overview|U-Boot]] is commonly used as a Linux bootloader in embedded systems.
    
    ==== Linux kernel space ====
    The Linux kernel is started in the external memory and it initializes all the peripheral drivers that are needed on the platform.
    
    ==== Linux user space ====
    Finally, the Linux kernel hands control to the user space starting the init process that runs all initialization actions described in the root file system (rootfs), including the application framework that exposes the user interface (UI) to the user.<br />
    
    
    === Other services start-up ===
    [[File: STM32MP boot chain.png|thumb|upright=2|right|link=|STM32MP boot chain]]
    In addition to <span style="color:#FFFFFF; background:#002052{{STDarkBlue}};">&nbsp;Linux&nbsp;</span> startup, the boot chain can also be responsible for the start-up of other services.<br /><br />
    
    installs the secure monitor and may support coprocessor firmware loading.<br /><br />
    For instance, for the STM32MP15, the boot chain starts:
    * the <span style="color:#FFFFFF; background:#D4007A{{STPink}};">&nbsp;secure monitor&nbsp;</span>, supported by the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A secure context (TrustZone). Examples of use of a secure monitor are: user authentication, key storage, and tampering management.
    * the <span style="color:#FFFFFF; background:#39A9DC{{STLightBlue}};">&nbsp;coprocessor&nbsp;</span> firmware, running on the Arm Cortex-M core. This can be used to offload real -time or low -power services.<br />
    
    The dotted lines in the diagram on the right mean that:
    * the <span style="color:#FFFFFF; background:#D4007A{{STLightBlue}};">&nbsp;secure monitor&nbsp;</span> can be started by the '''first stage boot loader (FSBL)''' or the '''second stage boot loader (SSBL)'''
    * the <span style="color:#FFFFFF; background:#39A9DC">&nbsp;coprocessor&nbsp;</span> can be started by the '''second stage boot loader (SSBL)''', known as “'''early boot'''”, or '''Linux kernel'''<br clear=all>
    
    
    == STM32MP boot sequence ==
    === Diagram frames and legend ===
    [[File:Boot diagrams contexts.png|thumb|upright=2|right|link=|STM32MP hardware execution contexts]]
    The [[Getting_started_with_STM32_MPU_devices#Multiple-core_architecture_concepts|hardware execution contexts]] are shown with vertical frames in the boot diagrams:
    * the <span style="color:#FFFFFF; background:#D4007A{{STPink}};">&nbsp;Arm Cortex-A secure&nbsp;</span> context, in pink
    * the <span style="color:#FFFFFF; background:#002052{{STDarkBlue}};">&nbsp;Arm Cortex-A non-secure&nbsp;</span> context, in dark blue
    * the <span style="color:#FFFFFF; background:#39A9DC{{STLightBlue}};">&nbsp;Arm Cortex-M&nbsp;</span> context, in light blue
    The horizontal frame in:
    * the bottom part shows the '''boot chain'''
    * the top part shows the '''runtime''' services, that are installed by the '''boot chain'''<br clear=all>
    
    [[File:Boot chains legend.png|thumb|upright=2|right|link=|Boot chain diagrams legend]]
    The legend on the right shows how information about the severalvarious components shown in the frames, and which are involved in the boot process, is highlighted:
    * The box '''color''' shows the component source code origin
    * The '''arrows''' show the loading and calling actions between the components
    * The '''Cube''' logo is used on the top right corner of components that can be configured via [[STM32CubeMX]] 
    * The '''lock''' show the components that can be authenticated during the boot process<br clear=all>
    
    
    === STM32MPSTM32MP15 boot chainschain ===
    ==== Overview ====
    [[File: STM32MPU Embedded Software architecture overview.png|link=STM32MPU Embedded Software architecture overview|thumb|Zoom out to STM32MPU Embedded Software]]Two different STM32MP15 boot chain flavors are supported on STM32MP processors with [[STM32MPU Embedded Software architecture overview|STM32MPU Embedded Software]]:
    * The '''trusted boot chain''' uses [[TF-A overview|Trusted Firmware-A (TF-A)]] as the FSBL, so it should in order to fulfill all the requirements for security-sensitive customers, and it uses [[U-Boot overview|U-Boot]] as the SSBL. Note that the authentication is optional with this boot chain, so it can run on any STM32MP STM32MP15 device [[STM32MP15_microprocessor#Part_number_codification|security]] variant (that is,  with or without the Secure boot). '''The trusted boot chain is the default solution delivered by STMicroelectronics''', with a complete feature set (for example, all Flash devices are supported).
    * The '''basic boot chain''' is also available to generate both the FSBL (U-Boot SPL) and SSBL (U-Boot) from a unique piece of source code, [[U-Boot overview|U-Boot]]. STMicroelectronics upstreams the Basic boot chain with a limited number of features, and the U-Boot community is able to extend this.<br clear=all>
    
    
    ==== STM32MP15 case ====
    ===== Overview =====
    The diagrams below illustrate the two boot chain flavors availble on the STM32MP15: the '''trusted boot chain''' and the '''basic boot chain'''<br>
    
    Refer to the [[Security overview|security overview]] for an introduction of the secure features available on STM32MP15, from the secure boot up to trusted applications execution.
    [[File:Trusted boot chain.png|center|link=|frame|TrustedSTM32MP15 boot chain]]<br clear=all>
    [[File:Basic boot chain.png|center|link=|frame|Basic boot chain]]<br clear=all>
    
    Notes:
    * The second-stage boot loader (SSBL) can run in ARM Secure/Trustzone mode (basic boot chain) or Non-Secure mode (trusted boot chain).
    * The STM32MP Note:
    * The STM32MP15 coprocessor can be started at the SSBL level by the [[U-Boot overview|U-Boot early boot]] feature or, later, by the [[Linux remoteproc framework overview|Linux remoteproc framework]], depending on the application startup time -targets.
    
    ===== ROM code =====
    
    The [[STM32MP15 ROM code overview|ROM code]] starts the processor in secure mode. It supports the FSBL authentication and offers authentication services to the FSBL.
    
    ===== First stage boot loader (FSBL) =====
    
    The FSBL is executed from the [[SYSRAM_internal_memory|SYSRAM]].<br />
    
    Among other things, this boot loader initializes (part of) the clock tree and the [[DDRCTRL and DDRPHYC internal peripherals|DDR controller]]. Finally, the FSBL loads the second-stage boot loader (SSBL) into the DDR external RAM and jumps to it.<br />
    
    The boot loader stage 2, so called TF-A BL2, is the [[TF-A overview|Trusted Firmware-A (TF-A)]] and [[U-Boot overview|U-Boot]] secondary program loader (U-Boot SPL) are the two possible FSBLs on the STM32MP15, for the '''trusted boot chain''' and the '''basic boot chain''', respectively.
    
    =====binary used as FSBL on  STM32MP15.<br>
    
    
    ==== Second stage boot loader (SSBL) =====
    The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on) that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (showing a splash screen to the user).<br />
    
    [[U-Boot overview|U-Boot]] is commonly used as a bootloader in embedded software.
    
    ===== Linux ===== and it is the one used on STM32MP15.
    
    ==== Linux ====
    
    Linux<sup>&reg;</sup> is OS is loaded in DDR by U-Boot and executed in the non-secure context.
    
    ===== Secure OS / Secure Monitor =====
    
    The Cortex-A7 secure world can implement a minimal secure monitor (from [[TF-A_overview#BL32|TF-A SP-MIN]] or [[U-Boot overview|U-Boot]]) or a real secure OS, such as [[OP-TEE overview|OP-TEE]].
    
    ===== Coprocessor firmware =====
    
    The coprocessor [[STM32CubeMP1 architecture|STM32Cube]] firmware can be started at the SSBL level by [[U-Boot overview|U-Boot]] with the remoteproc feature (rproc command) or, later, by [[Linux remoteproc framework overview|Linux remoteproc framework]], depending on the application startup time -targets.
    
    <noinclude>
    
    [[Category:Platform boot|0]]
    {{PublicationRequestId | 13223 |2019-09-11}}</noinclude>
    (51 intermediate revisions by 8 users not shown)
    Line 1: Line 1:
    <noinclude>
     
    {{ArticleMainWriter | GeraldB}}
     
    {{ArticleApprovedVersion | GeraldB | PatrickD, LionelD | GeraldB - 24Jan'18 | PhilipS - 14Nov'18 - 9286 | 27Sep'18}}
     
    [[Category:Platform boot|0]]
     
    </noinclude>
     
     
    __FORCETOC__
     
    __FORCETOC__
     
     
    == Generic boot sequence ==
     
    == Generic boot sequence ==
     
    === Linux start-up ===
     
    === Linux start-up ===
    Starting Linux<sup>&reg;</sup> on a processor is done in several steps that progressively initialize the platform peripherals and memories. Those steps are  
    +
    Starting Linux<sup>&reg;</sup> on a processor is done in several steps that progressively initialize the platform peripherals and memories. These steps are  
    explained in the following parapraphs and illustrated by the diagram on the right, which also gives typical memory sizes for each stage.
    +
    explained in the following paragraphs and illustrated by the diagram on the right, which also gives typical memory sizes for each stage.
    [[File: Boot_chains_overview.png|thumb|upright=4|right|link=|Generic Linux boot chain]]
    +
    [[File: Boot_chains_overview.png|center|link=|Generic Linux boot chain]]
       
     
    ==== ROM code ====
     
    ==== ROM code ====
    The ROM code is a piece of software that takes its name from the read only memory (ROM) where it is stored. It fits in a few tens of Kbytes and maps its data in embedded RAM. It is the first code executed by the processor, and it embeds all the logic needed to select the boot device (serial link or Flash) from where the first-stage boot loader (FSBL) is loaded to the embedded RAM.
    +
    The ROM code is a piece of software that takes its name from the read only memory (ROM) where it is stored. It fits in a few tens of Kbytes and maps its data in embedded RAM. It is the first code executed by the processor, and it embeds all the logic needed to select the boot device (serial link or Flash) from which the first-stage boot loader (FSBL) is loaded to the embedded RAM.<br>
      +
    Most products require to trust the application that is running on the device and the ROM code is the first link in the chain of trust that must be established across all started components: this trust is established by authenticating the FSBL before starting it. In turn, the FSBL and each following component will authenticate the next one, up to a level defined by the product manufacturer.
       
     
    ==== First stage boot loader (FSBL) ====
     
    ==== First stage boot loader (FSBL) ====
    Line 21: Line 16:
       
     
    ==== Second-stage boot loader (SSBL) ====
     
    ==== Second-stage boot loader (SSBL) ====
    The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on), that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (showing a splash screen to the user). [[U-Boot overview|U-Boot]] is commonly used as a Linux bootloader in embedded systems.
    +
    The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on), that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (by showing a splash screen to the user). [[U-Boot overview|U-Boot]] is commonly used as a Linux bootloader in embedded systems.
       
     
    ==== Linux kernel space ====
     
    ==== Linux kernel space ====
    Line 27: Line 22:
       
     
    ==== Linux user space ====
     
    ==== Linux user space ====
    Finally, the Linux kernel hands control to the user space starting the init process that runs all initialization actions described in the root file system (rootfs), including the application framework that exposes the user interface (UI) to the user<br />
    +
    Finally, the Linux kernel hands control to the user space starting the init process that runs all initialization actions described in the root file system (rootfs), including the application framework that exposes the user interface (UI) to the user.<br />
       
     
    === Other services start-up ===
     
    === Other services start-up ===
    [[File: STM32MP boot chain.png|thumb|upright=2|right|link=|STM32MP boot chain]]
    +
    [[File: STM32MP boot chain.png|right|link=|STM32MP boot chain]]
    In addition to <span style="color:#FFFFFF; background:#002052">&nbsp;Linux&nbsp;</span> startup, the boot chain can also be responsible for the start-up of other services.
    +
    In addition to <span style="color:#FFFFFF; background:{{STDarkBlue}};">&nbsp;Linux&nbsp;</span> startup, the boot chain also installs the secure monitor and may support coprocessor firmware loading.
     
    <br /><br />
     
    <br /><br />
     
     
    For instance, for the STM32MP15, the boot chain starts:
     
    For instance, for the STM32MP15, the boot chain starts:
    * the <span style="color:#FFFFFF; background:#D4007A">&nbsp;secure monitor&nbsp;</span>, supported by the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A secure context (TrustZone). Examples of use of a secure monitor are: user authentication, key storage, and tampering management.
    +
    * the <span style="color:#FFFFFF; background:{{STPink}};">&nbsp;secure monitor&nbsp;</span>, supported by the Arm<sup>&reg;</sup> Cortex<sup>&reg;</sup>-A secure context (TrustZone). Examples of use of a secure monitor are: user authentication, key storage, and tampering management.
    * the <span style="color:#FFFFFF; background:#39A9DC">&nbsp;coprocessor&nbsp;</span> firmware, running on the Arm Cortex-M core. This can be used to offload real time or low power services.
    +
    * the <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;coprocessor&nbsp;</span> firmware, running on the Arm Cortex-M core. This can be used to offload real-time or low-power services.
     
    <br />
     
    <br />
     
    The dotted lines in the diagram on the right mean that:
     
    The dotted lines in the diagram on the right mean that:
    * the <span style="color:#FFFFFF; background:#D4007A">&nbsp;secure monitor&nbsp;</span> can be started by the '''first stage boot loader (FSBL)''' or the '''second stage boot loader (SSBL)'''
    +
    * the <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;coprocessor&nbsp;</span> can be started by the '''second stage boot loader (SSBL)''', known as “'''early boot'''”, or '''Linux kernel'''
    * the <span style="color:#FFFFFF; background:#39A9DC">&nbsp;coprocessor&nbsp;</span> can be started by the '''second stage boot loader (SSBL)''', known as “'''early boot'''”, or '''Linux kernel'''
     
     
    <br clear=all>
     
    <br clear=all>
       
     
    == STM32MP boot sequence ==
     
    == STM32MP boot sequence ==
     
    === Diagram frames and legend ===
     
    === Diagram frames and legend ===
    [[File:Boot diagrams contexts.png|thumb|upright=2|right|link=|STM32MP hardware execution contexts]]
    +
    [[File:Boot diagrams contexts.png|right|link=|STM32MP hardware execution contexts]]
     
    The [[Getting_started_with_STM32_MPU_devices#Multiple-core_architecture_concepts|hardware execution contexts]] are shown with vertical frames in the boot diagrams:
     
    The [[Getting_started_with_STM32_MPU_devices#Multiple-core_architecture_concepts|hardware execution contexts]] are shown with vertical frames in the boot diagrams:
    * the <span style="color:#FFFFFF; background:#D4007A">&nbsp;Arm Cortex-A secure&nbsp;</span> context, in pink
    +
    * the <span style="color:#FFFFFF; background:{{STPink}};">&nbsp;Arm Cortex-A secure&nbsp;</span> context, in pink
    * the <span style="color:#FFFFFF; background:#002052">&nbsp;Arm Cortex-A non-secure&nbsp;</span> context, in dark blue
    +
    * the <span style="color:#FFFFFF; background:{{STDarkBlue}};">&nbsp;Arm Cortex-A non-secure&nbsp;</span> context, in dark blue
    * the <span style="color:#FFFFFF; background:#39A9DC">&nbsp;Arm Cortex-M&nbsp;</span> context, in light blue
    +
    * the <span style="color:#FFFFFF; background:{{STLightBlue}};">&nbsp;Arm Cortex-M&nbsp;</span> context, in light blue
     
    The horizontal frame in:
     
    The horizontal frame in:
     
    * the bottom part shows the '''boot chain'''
     
    * the bottom part shows the '''boot chain'''
     
    * the top part shows the '''runtime''' services, that are installed by the '''boot chain'''
     
    * the top part shows the '''runtime''' services, that are installed by the '''boot chain'''
     
    <br clear=all>
     
    <br clear=all>
    [[File:Boot chains legend.png|thumb|upright=2|right|link=|Boot chain diagrams legend]]
    +
    [[File:Boot chains legend.png|right|link=|Boot chain diagrams legend]]
    The legend on the right shows how information about the several components shown in the frames, and which are involved in the boot process, is highlighted:
    +
    The legend on the right shows how information about the various components shown in the frames, and which are involved in the boot process, is highlighted:
     
    * The box '''color''' shows the component source code origin
     
    * The box '''color''' shows the component source code origin
     
    * The '''arrows''' show the loading and calling actions between the components
     
    * The '''arrows''' show the loading and calling actions between the components
    Line 62: Line 55:
     
    <br clear=all>
     
    <br clear=all>
       
    === STM32MP boot chains ===
    +
    === STM32MP15 boot chain ===
     
    ==== Overview ====
     
    ==== Overview ====
     
    [[File: STM32MPU Embedded Software architecture overview.png|link=STM32MPU Embedded Software architecture overview|thumb|Zoom out to STM32MPU Embedded Software]]
     
    [[File: STM32MPU Embedded Software architecture overview.png|link=STM32MPU Embedded Software architecture overview|thumb|Zoom out to STM32MPU Embedded Software]]
    Two different boot chain flavors are supported on STM32MP processors with [[STM32MPU Embedded Software architecture overview|STM32MPU Embedded Software]]:
    +
    STM32MP15 boot chain uses [[TF-A overview|Trusted Firmware-A (TF-A)]] as the FSBL in order to fulfill all the requirements for security-sensitive customers, and it uses [[U-Boot overview|U-Boot]] as the SSBL. Note that the authentication is optional with this boot chain, so it can run on any STM32MP15 device [[STM32MP15_microprocessor#Part_number_codification|security]] variant (that is,  with or without the Secure boot).<br>
    * The '''trusted boot chain''' uses [[TF-A overview|Trusted Firmware-A (TF-A)]] as the FSBL, so it should fulfill all the requirements for security-sensitive customers, and it uses [[U-Boot overview|U-Boot]] as the SSBL. Note that the authentication is optional with this boot chain, so it can run on any STM32MP [[STM32MP15_microprocessor#Part_number_codification|security]] variant (that is,  with or without the Secure boot). '''The trusted boot chain is the default solution delivered by STMicroelectronics''', with a complete feature set (for example, all Flash devices are supported).
    +
    Refer to the [[Security overview|security overview]] for an introduction of the secure features available on STM32MP15, from the secure boot up to trusted applications execution.
    * The '''basic boot chain''' is also available to generate both the FSBL (U-Boot SPL) and SSBL (U-Boot) from a unique piece of source code, [[U-Boot overview|U-Boot]]. STMicroelectronics upstreams the Basic boot chain with a limited number of features, and the U-Boot community is able to extend this.
    +
    [[File:Trusted boot chain.png|center|link=|STM32MP15 boot chain]]
     
    <br clear=all>
     
    <br clear=all>
      +
    Note:
      +
    * The STM32MP15 coprocessor can be started at the SSBL level by the [[U-Boot overview|U-Boot early boot]] feature or, later, by the [[Linux remoteproc framework overview|Linux remoteproc framework]], depending on the application startup time-targets.
       
    ==== STM32MP15 case ====
    +
    ==== ROM code ====
    ===== Overview =====
     
    The diagrams below illustrate the two boot chain flavors availble on the STM32MP15: the '''trusted boot chain''' and the '''basic boot chain'''.
     
    [[File:Trusted boot chain.png|center|link=|frame|Trusted boot chain]]
     
    <br>
     
    [[File:Basic boot chain.png|center|link=|frame|Basic boot chain]]
     
    <br clear=all>
     
    Notes:
     
    * The second-stage boot loader (SSBL) can run in ARM Secure/Trustzone mode (basic boot chain) or Non-Secure mode (trusted boot chain).
     
    * The STM32MP coprocessor can be started at the SSBL level by the [[U-Boot overview|U-Boot early boot]] feature or, later, by the [[Linux remoteproc framework overview|Linux remoteproc framework]], depending on the application startup time targets.
     
     
     
    ===== ROM code =====
     
     
    The [[STM32MP15 ROM code overview|ROM code]] starts the processor in secure mode. It supports the FSBL authentication and offers authentication services to the FSBL.
     
    The [[STM32MP15 ROM code overview|ROM code]] starts the processor in secure mode. It supports the FSBL authentication and offers authentication services to the FSBL.
       
    ===== First stage boot loader (FSBL) =====
    +
    ==== First stage boot loader (FSBL) ====
     
    The FSBL is executed from the [[SYSRAM_internal_memory|SYSRAM]].<br />
     
    The FSBL is executed from the [[SYSRAM_internal_memory|SYSRAM]].<br />
    Among other things, this boot loader initializes (part of) the clock tree and the [[DDRCTRL and DDRPHYC internal peripherals|DDR controller]]. Finally, the FSBL loads the second-stage boot loader (SSBL) into the DDR external RAM and jumps to it.<br />
    +
    Among other things, this boot loader initializes (part of) the clock tree and the [[DDRCTRL and DDRPHYC internal peripherals|DDR controller]]. Finally, the FSBL loads the second-stage boot loader (SSBL) into the DDR external RAM and jumps to it.<br>
    The [[TF-A overview|Trusted Firmware-A (TF-A)]] and [[U-Boot overview|U-Boot]] secondary program loader (U-Boot SPL) are the two possible FSBLs on the STM32MP15, for the '''trusted boot chain''' and the '''basic boot chain''', respectively.
    +
    The boot loader stage 2, so called TF-A BL2, is the [[TF-A overview|Trusted Firmware-A (TF-A)]] binary used as FSBL on  STM32MP15.<br>
      +
     
      +
    ==== Second stage boot loader (SSBL) ====
      +
    [[U-Boot overview|U-Boot]] is commonly used as a bootloader in embedded software and it is the one used on STM32MP15.
       
    ===== Second stage boot loader (SSBL) =====
    +
    ==== Linux ====
    The second-stage boot loader (SSBL) runs in a wide RAM so it can implement complex features (USB, Ethernet, display, and so on) that are very useful to make Linux kernel loading more flexible (from a Flash device, a network, and so on), and user-friendly (showing a splash screen to the user).<br />
    +
    Linux<sup>&reg;</sup> OS is loaded in DDR by U-Boot and executed in the non-secure context.
    [[U-Boot overview|U-Boot]] is commonly used as a bootloader in embedded software.
     
       
    ===== Linux =====
    +
    ==== Secure OS / Secure Monitor ====
    Linux<sup>&reg;</sup> is OS is loaded in DDR by U-Boot and executed in the non-secure context.
    +
    The Cortex-A7 secure world can implement a minimal secure monitor (from [[TF-A_overview#BL32|TF-A SP-MIN]] or [[U-Boot overview|U-Boot]]) or a real secure OS, such as [[OP-TEE overview|OP-TEE]].
       
    ===== Secure OS / Secure Monitor =====
    +
    ==== Coprocessor firmware ====
    The Cortex-A7 secure world can implement a minimal secure monitor (from [[TF-A_overview#BL32|TF-A]] or [[U-Boot overview|U-Boot]]) or a real secure OS, such as [[OP-TEE overview|OP-TEE]].
    +
    The coprocessor [[STM32CubeMP1 architecture|STM32Cube]] firmware can be started at the SSBL level by [[U-Boot overview|U-Boot]] with the remoteproc feature (rproc command) or, later, by [[Linux remoteproc framework overview|Linux remoteproc framework]], depending on the application startup time-targets.
       
    ===== Coprocessor firmware =====
    +
    <noinclude>
    The coprocessor [[STM32CubeMP1 architecture|STM32Cube]] firmware can be started at the SSBL level by [[U-Boot overview|U-Boot]] with the remoteproc feature (rproc command) or, later, by [[Linux remoteproc framework overview|Linux remoteproc framework]], depending on the application startup time targets.
    +
    [[Category:Platform boot|0]]
      +
    {{PublicationRequestId | 13223 |2019-09-11}}
      +
    </noinclude>