Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-12-14 07:13:03 +00:00
Code Issues Projects Releases Packages Wiki Activity
u-boot/doc/board/ti/j7200_evm.rst
Nishanth Menon c727b81d65 doc: board: ti: k3: Reuse build instructions 
Introduce common variables to define a generic build instruction that is
then used in specific board specific description.

Labels are introduced in the evm.rst files to be then reused in variant
board documentation as well.

While at this, drop using ARCH=arm when building u-boot sources. This
practice has been discouraged for some time and can potentially create
problems with Kconfig rules related to aarch64. It's best to avoid
this approach.

Signed-off-by: Nishanth Menon <nm@ti.com>
2023-07-28 11:36:37 +02:00

269 lines
8.3 KiB
ReStructuredText
Raw Blame History

.. SPDX-License-Identifier: GPL-2.0+ OR BSD-3-Clause
.. sectionauthor:: Udit Kumar <u-kumar1@ti.com>
J7200 Platforms
===============
Introduction:
-------------
The J7200 family of SoCs are part of K3 Multicore SoC architecture platform
targeting automotive applications. They are designed as a low power, high
performance and highly integrated device architecture, adding significant
enhancement on processing power, graphics capability, video and imaging
processing, virtualization and coherent memory support.
The device is partitioned into three functional domains, each containing
specific processing cores and peripherals:
1. Wake-up (WKUP) domain:
* Device Management and Security Controller (DMSC)
2. Microcontroller (MCU) domain:
* Dual Core ARM Cortex-R5F processor
3. MAIN domain:
* Dual core 64-bit ARM Cortex-A72
More info can be found in TRM: https://www.ti.com/lit/pdf/spruiu1
Boot Flow:
----------
Below is the pictorial representation of boot flow:
.. image:: img/boot_diagram_k3_current.svg
- Here DMSC acts as master and provides all the critical services. R5/A72
requests DMSC to get these services done as shown in the above diagram.
Sources:
--------
.. include:: k3.rst
:start-after: .. k3_rst_include_start_boot_sources
:end-before: .. k3_rst_include_end_boot_sources
Build procedure:
----------------
0. Setup the environment variables:
.. include:: k3.rst
:start-after: .. k3_rst_include_start_common_env_vars_desc
:end-before: .. k3_rst_include_end_common_env_vars_desc
.. include:: k3.rst
:start-after: .. k3_rst_include_start_board_env_vars_desc
:end-before: .. k3_rst_include_end_board_env_vars_desc
Set the variables corresponding to this platform:
.. include:: k3.rst
:start-after: .. k3_rst_include_start_common_env_vars_defn
:end-before: .. k3_rst_include_end_common_env_vars_defn
.. code-block:: bash
$ export UBOOT_CFG_CORTEXR=j7200_evm_r5_defconfig
$ export UBOOT_CFG_CORTEXA=j7200_evm_a72_defconfig
$ export TFA_BOARD=generic
$ # we dont use any extra TFA parameters
$ unset TFA_EXTRA_ARGS
$ export OPTEE_PLATFORM=k3-j7200
$ # we dont use any extra OP-TEE parameters
$ unset OPTEE_EXTRA_ARGS
.. j7200_evm_rst_include_start_build_steps
1. Trusted Firmware-A:
.. include:: k3.rst
:start-after: .. k3_rst_include_start_build_steps_tfa
:end-before: .. k3_rst_include_end_build_steps_tfa
2. OP-TEE:
.. include:: k3.rst
:start-after: .. k3_rst_include_start_build_steps_optee
:end-before: .. k3_rst_include_end_build_steps_optee
3. U-Boot:
* 4.1 R5:
.. include:: k3.rst
:start-after: .. k3_rst_include_start_build_steps_spl_r5
:end-before: .. k3_rst_include_end_build_steps_spl_r5
* 4.2 A72:
.. include:: k3.rst
:start-after: .. k3_rst_include_start_build_steps_uboot
:end-before: .. k3_rst_include_end_build_steps_uboot
.. j7200_evm_rst_include_end_build_steps
Target Images
--------------
In order to boot we need tiboot3.bin, tispl.bin and u-boot.img. Each SoC
variant (GP, HS-FS, HS-SE) requires a different source for these files.
- GP
* tiboot3-j7200-gp-evm.bin from step 4.1
* tispl.bin_unsigned, u-boot.img_unsigned from step 4.2
- HS-FS
* tiboot3-j7200_sr2-hs-fs-evm.bin from step 4.1
* tispl.bin, u-boot.img from step 4.2
- HS-SE
* tiboot3-j7200_sr2-hs-evm.bin from step 4.1
* tispl.bin, u-boot.img from step 4.2
Image formats:
--------------
- tiboot3.bin:
.. code-block:: console
+-----------------------+
| X.509 |
| Certificate |
| +-------------------+ |
| | | |
| | R5 | |
| | u-boot-spl.bin | |
| | | |
| +-------------------+ |
| | | |
| | FIT header | |
| | +---------------+ | |
| | | | | |
| | | DTB 1...N | | |
| | +---------------+ | |
| +-------------------+ |
| | | |
| | FIT HEADER | |
| | +---------------+ | |
| | | | | |
| | | sysfw.bin | | |
| | +---------------+ | |
| | | | | |
| | | board config | | |
| | +---------------+ | |
| | | | | |
| | | PM config | | |
| | +---------------+ | |
| | | | | |
| | | RM config | | |
| | +---------------+ | |
| | | | | |
| | | Secure config | | |
| | +---------------+ | |
| +-------------------+ |
+-----------------------+
- tispl.bin
.. code-block:: console
+-----------------------+
| |
| FIT HEADER |
| +-------------------+ |
| | | |
| | A72 TF-A | |
| +-------------------+ |
| | | |
| | A72 OP-TEE | |
| +-------------------+ |
| | | |
| | R5 DM FW | |
| +-------------------+ |
| | | |
| | A72 SPL | |
| +-------------------+ |
| | | |
| | SPL DTB 1...N | |
| +-------------------+ |
+-----------------------+
Switch Setting for Boot Mode
----------------------------
Boot Mode pins provide means to select the boot mode and options before the
device is powered up. After every POR, they are the main source to populate
the Boot Parameter Tables.
The following table shows some common boot modes used on J7200 platform. More
details can be found in the Technical Reference Manual:
https://www.ti.com/lit/pdf/spruiu1 under the `Boot Mode Pins` section.
*Boot Modes*
============ ============= =============
Switch Label SW9: 12345678 SW8: 12345678
============ ============= =============
SD 00000000 10000010
EMMC 01000000 10000000
OSPI 01000000 00000110
UART 01110000 00000000
USB DFU 00100000 10000000
============ ============= =============
For SW8 and SW9, the switch state in the "ON" position = 1.
eMMC:
-----
ROM supports booting from eMMC raw read or UDA FS mode.
Below is memory layout in case of booting from
boot 0/1 partition in raw mode.
Current allocated size for tiboot3 size is 1MB, tispl is 2MB.
Size of u-boot.img is taken 4MB for refernece,
But this is subject to change depending upon atf, optee size
.. code-block:: console
boot0/1 partition (8 MB) user partition
0x0+----------------------------------+ 0x0+------------------------+
| tiboot3.bin (1 MB) | | |
0x800+----------------------------------+ | |
| tispl.bin (2 MB) | | |
0x1800+----------------------------------+ | |
| u-boot.img (4MB) | | |
0x3800+----------------------------------+ | |
| | | |
0x3900+ environment | | |
| | | |
0x3A00+----------------------------------+ +-------------------------+
In case of UDA FS mode booting, following is layout.
All boot images tiboot3.bin, tispl and u-boot should be written to
fat formatted UDA FS as file.
.. code-block:: console
boot0/1 partition (8 MB) user partition
0x0+---------------------------------+ 0x0+-------------------------+
| | | tiboot3.bin* |
0x800+----------------------------------+ | |
| | | tispl.bin |
0x1800+----------------------------------+ | |
| | | u-boot.img |
0x3800+----------------------------------+ | |
| | | |
0x3900+ | | environment |
| | | |
0x3A00+----------------------------------+ +-------------------------+
In case of booting from eMMC, write above images into raw or UDA FS.
and set mmc partconf accordingly.
Reference in a new issue View git blame Copy permalink