From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/6] board: ti: am65x: Add README
Date: Tue, 21 Aug 2018 20:03:12 +0530 [thread overview]
Message-ID: <20180821143316.29329-3-lokeshvutla@ti.com> (raw)
In-Reply-To: <20180821143316.29329-1-lokeshvutla@ti.com>
Add README file that describes the building and booting procedure.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
---
board/ti/am65x/README | 134 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 134 insertions(+)
create mode 100644 board/ti/am65x/README
diff --git a/board/ti/am65x/README b/board/ti/am65x/README
new file mode 100644
index 0000000000..1956142270
--- /dev/null
+++ b/board/ti/am65x/README
@@ -0,0 +1,134 @@
+Introduction:
+-------------
+The AM65x family of SoCs is the first device family from K3 Multicore
+SoC architecture, targeted for broad market and industrial control with
+aim to meet the complex processing needs of modern embedded products.
+
+The device is built over three domains, each containing specific processing
+cores, voltage domains 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:
+ - Quad core 64-bit ARM Cortex-A53
+
+More info can be found in TRM: http://www.ti.com/lit/pdf/spruid7
+
+Boot Flow:
+----------
+On AM65x family devices, ROM supports boot only via MCU(R5). This means that
+bootloader has to run on R5 core. In order to meet this constraint,
+keeping safety in picture and to have faster boot time, the software boot
+architecture is designed as below:
+
++------------------------------------------------------------------------+
+| DMSC | R5 | A53 |
++------------------------------------------------------------------------+
+| +--------+ | | |
+| | Reset | | | |
+| +--------+ | | |
+| : | | |
+| +--------+ | +-----------+ | |
+| | *rom* |----------|-->| Reset rls | | |
+| +--------+ | +-----------+ | |
+| | | | : | |
+| | rom | | : | |
+| |services| | : | |
+| | | | +-------------+ | |
+| | | | | *R5 rom* | | |
+| | | | +-------------+ | |
+| | |<---------|---|Load and auth| | |
+| | | | | tiboot3.bin | | |
+| | | | +-------------+ | |
+| | | | : | |
+| | | | : | |
+| | | | : | |
+| | | | +-------------+ | |
+| | Start | | | *R5 SPL* | | |
+| | System | | +-------------+ | |
+| |Firmware|<---------|---|Load and auth| | |
+| +--------+ | | sysfw bin | | |
+| : | +-------------+ | |
+| +---------+ | | DDR | | |
+| | *SYSFW* | | | config | | |
+| +---------+ | +-------------+ | |
+| | |<--------|---| Load | | |
+| | | | | tispl.bin | | |
+| | | | +-------------+ | |
+| | |<--------|---| Start A53 | | |
+| | | | | and Reset | | |
+| | | | +-------------+ | |
+| | | | | +-----------+ |
+| | |---------|-----------------------|---->| Reset rls | |
+| | | | | +-----------+ |
+| | DMSC | | | : |
+| |Services | | | +-----------+ |
+| | |<--------|-----------------------|---->|*ATF/OPTEE*| |
+| | | | | +-----------+ |
+| | | | | : |
+| | | | | +-----------+ |
+| | |<--------|-----------------------|---->| *A53 SPL* | |
+| | | | | +-----------+ |
+| | | | | | Load | |
+| | | | | | u-boot.img| |
+| | | | | +-----------+ |
+| | | | | : |
+| | | | | +-----------+ |
+| | |<--------|-----------------------|---->| *u-boot* | |
+| | | | | +-----------+ |
+| | | | | | prompt | |
+| | | | | +-----------+ |
+| +---------+ | | |
+| | | |
++------------------------------------------------------------------------+
+
+- Here DMSC acts as master and provides all the critical services. R5/A53
+requests DMSC to get these services done as shown in the above diagram.
+
+Sources:
+--------
+1. SYSFW:
+ System Firmware repo is closed source and the binaries are delivered
+ to users with NDA. Please contact TI to get the System Firmware
+ Binary named ti-sci-firmware-am6x.bin that runs on AM65x SoC.
+
+2. ATF:
+ Tree: https://github.com/ARM-software/arm-trusted-firmware.git
+ Branch: master
+
+3. OPTEE:
+ Tree: https://github.com/OP-TEE/optee_os.git
+ Branch: master
+
+4. U-Boot:
+ Tree: http://git.denx.de/u-boot.git
+ Branch: master
+
+Build procedure:
+----------------
+1. SYSFW:
+ ROM expects a signed binary that contains the X509 certificate. So
+the binary ti-sci-firmware-am6x.bin cannot be uses as-is and needs to be signed.
+Contact TI on the procedure to sign the system firmware binary.
+
+2. ATF:
+$ make CROSS_COMPILE=aarch64-linux-gnu- ARCH=aarch64 PLAT=k3 TARGET_BOARD=generic SPD=opteed
+
+3. OPTEE:
+$ make PLATFORM=k3-am65x CFG_ARM64_core=y
+
+4. U-Boot:
+
+4.1. R5:
+ TBD.
+
+4.2. A53:
+$ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- am65x_evm_a53_defconfig O=/tmp/a53
+$ make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- ATF=<path to ATF dir>/build/k3/generic/release/bl31.bin TEE=<path to OPTEE OS dir>/out/arm-plat-k3/core/tee-pager.bin O=/tmp/a53
+
+Target Images
+--------------
+Copy the below images to an SD card and boot:
+- tiboot3.bin from step 4.1
+- tispl.bin, u-boot.img from 4.2
--
2.18.0
next prev parent reply other threads:[~2018-08-21 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 14:33 [U-Boot] [PATCH 0/6] [3/3] Initial support Texas Instrument's AM654 Platform Lokesh Vutla
2018-08-21 14:33 ` [U-Boot] [PATCH 1/6] board: ti: am654: a53: Add initial support for am654 Lokesh Vutla
2018-08-24 14:13 ` Tom Rini
2018-08-21 14:33 ` Lokesh Vutla [this message]
2018-08-24 14:13 ` [U-Boot] [PATCH 2/6] board: ti: am65x: Add README Tom Rini
2018-08-21 14:33 ` [U-Boot] [PATCH 3/6] include: am654_evm: Establish initial environment for SD card boot Lokesh Vutla
2018-08-24 14:13 ` Tom Rini
2018-08-21 14:33 ` [U-Boot] [PATCH 4/6] arm64: dts: k3: Add Support for AM654 SoC Lokesh Vutla
2018-08-24 14:13 ` Tom Rini
2018-08-21 14:33 ` [U-Boot] [PATCH 5/6] arm64: dts: k3: Add u-boot specific nodes Lokesh Vutla
2018-08-24 14:13 ` Tom Rini
2018-08-21 14:33 ` [U-Boot] [PATCH 6/6] configs: am65x_evm_a53: Add initial support Lokesh Vutla
2018-08-24 14:13 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180821143316.29329-3-lokeshvutla@ti.com \
--to=lokeshvutla@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox