board: ti: k3: Convert boot flow ascii flow to svg

Replace the ascii flow diagram with svg.

Signed-off-by: Nishanth Menon <nm@ti.com>
This commit is contained in:
Nishanth Menon 2023-07-27 13:59:02 -05:00 committed by Heinrich Schuchardt
parent 5c86c57f9d
commit 6e8fa0611f
4 changed files with 3 additions and 12 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.9 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 19 KiB

View File

@ -45,10 +45,7 @@ boot media needed to load the binaries packaged inside `tiboot3.bin`,
including a 32bit U-Boot SPL, (called the wakup SPL) that ROM will jump including a 32bit U-Boot SPL, (called the wakup SPL) that ROM will jump
to after it has finished loading everything into internal SRAM. to after it has finished loading everything into internal SRAM.
.. code-block:: text .. image:: img/boot_flow_01.svg
| WKUP Domain
ROM -> WKUP SPL ->
The wakeup SPL, running on a wakeup domain core, will initialize DDR and The wakeup SPL, running on a wakeup domain core, will initialize DDR and
any peripherals needed load the larger binaries inside the `tispl.bin` any peripherals needed load the larger binaries inside the `tispl.bin`
@ -57,10 +54,7 @@ application cores inside the main domain to initialize the main domain,
starting with Trusted Firmware-A (TF-A), before moving on to start starting with Trusted Firmware-A (TF-A), before moving on to start
OP-TEE and the main domain's U-Boot SPL. OP-TEE and the main domain's U-Boot SPL.
.. code-block:: text .. image:: img/boot_flow_02.svg
| WKUP Domain | Main Domain ->
ROM -> WKUP SPL -> TF-A -> OP-TEE -> Main SPL
The main domain's SPL, running on a 64bit application core, has The main domain's SPL, running on a 64bit application core, has
virtually unlimited space (billions of bytes now that DDR is working) to virtually unlimited space (billions of bytes now that DDR is working) to
@ -68,10 +62,7 @@ initialize even more peripherals needed to load in the `u-boot.img`
which loads more firmware into the micro-controller & wakeup domains and which loads more firmware into the micro-controller & wakeup domains and
finally prepare the main domain to run Linux. finally prepare the main domain to run Linux.
.. code-block:: text .. image:: img/boot_flow_03.svg
| WKUP Domain | Main Domain ->
ROM -> WKUP SPL -> TF-A -> OP-TEE -> Main SPL -> UBoot -> Linux
This is the typical boot flow for all K3 based SoCs, however this flow This is the typical boot flow for all K3 based SoCs, however this flow
offers quite a lot in the terms of flexibility, especially on High offers quite a lot in the terms of flexibility, especially on High