From: Jit Loon Lim <jit.loon.lim@intel.com>
To: u-boot@lists.denx.de
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Vignesh R <vigneshr@ti.com>, Marek <marex@denx.de>,
Simon <simon.k.r.goldschmidt@gmail.com>,
Tien Fong <tien.fong.chee@intel.com>,
Kok Kiang <kok.kiang.hea@intel.com>,
Siew Chin <elly.siew.chin.lim@intel.com>,
Sin Hui <sin.hui.kho@intel.com>, Raaj <raaj.lokanathan@intel.com>,
Dinesh <dinesh.maniyam@intel.com>,
Boon Khai <boon.khai.ng@intel.com>,
Alif <alif.zakuan.yuslaimi@intel.com>,
Teik Heng <teik.heng.chong@intel.com>,
Hazim <muhammad.hazim.izzat.zamri@intel.com>,
Jit Loon Lim <jit.loon.lim@intel.com>,
Sieu Mun Tang <sieu.mun.tang@intel.com>,
Yau Wai Gan <yau.wai.gan@intel.com>
Subject: [PATCH 4/4] doc: README.socfpga: Add official boot flow support info
Date: Sun, 13 Nov 2022 21:55:36 +0800 [thread overview]
Message-ID: <20221113135536.9920-4-jit.loon.lim@intel.com> (raw)
In-Reply-To: <20221113135536.9920-1-jit.loon.lim@intel.com>
From: Yau Wai Gan <yau.wai.gan@intel.com>
The official boot-up flow for SoC FPGA 64-bit is with
Arm Trusted Firmware, ATF BL31. The non-ATF flow is
legacy and is not supported officially moving forward.
Update the README to include the information.
Signed-off-by: Yau Wai Gan <yau.wai.gan@intel.com>
Signed-off-by: Jit Loon Lim <jit.loon.lim@intel.com>
---
doc/README.socfpga | 30 +++++++++++++++++++++++++++++-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git a/doc/README.socfpga b/doc/README.socfpga
index 362361e014..3f0ce8ce7b 100644
--- a/doc/README.socfpga
+++ b/doc/README.socfpga
@@ -17,6 +17,7 @@ Table of Contents
6. mkimage for Cyclone V, Arria V and Arria 10
7. SDRAM secure region in U-boot ATF flow
8. binman for U-boot ATF flow
+ 9. Official Boot-up Flow Support
1. Device Family Support vs Tested Intel Quartus
@@ -304,4 +305,31 @@ Table of Contents
This command generate u-boot.itb only.
$ <U-boot path>/tools/binman/binman build -u -d u-boot.dtb -O . -i kernel
- This command generate kernel.itb only.
\ No newline at end of file
+ This command generate kernel.itb only.
+
+9. Official Boot-up Flow Support
+---------------------------------------------------------------------
+ U-boot with Arm Trusted Firmware (ATF, TF-A) boot-up is the official supported
+ boot flow for Intel SoC FPGA Arm 64-bit architecture devices including
+ Stratix 10, Agilex and N5X. ATF is the secure runtime firmware running at EL3
+ which handles secure accesses from U-boot proper and Linux running at EL2 and EL1.
+
+ Official boot flow:
+ U-boot -> ATF BL31 -> U-boot proper -> Linux
+
+ Legacy (aka non ATF) boot flow:
+ U-boot -> U-boot proper -> Linux
+
+ U-boot version socfpga_v2021.07 and onwards change the defconfig name to match
+ the official boot flow. The non ATF flow defconfigs are renamed with _legacy_
+ appended and is not officially supported moving forward. See details as follow.
+
+ Legacy boot flow:
+ socfpga_agilex_defconfig -> socfpga_agilex_legacy_defconfig
+ socfpga_n5x_defconfig -> socfpga_n5x_legacy_defconfig
+ socfpga_stratix10_defconfig -> socfpga_stratix10_legacy_defconfig
+
+ Official boot flow:
+ socfpga_agilex_atf_defconfig -> socfpga_agilex_defconfig
+ socfpga_n5x_atf_defconfig -> socfpga_n5x_defconfig
+ socfpga_stratix10_atf_defconfig -> socfpga_stratix10_defconfig
\ No newline at end of file
--
2.26.2
prev parent reply other threads:[~2022-11-13 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 13:55 [PATCH 1/4] makefile: tools: socfpgaimage: update padding flow Jit Loon Lim
2022-11-13 13:55 ` [PATCH 2/4] doc: README.socfpga: Add guide for mkimage Jit Loon Lim
2022-11-13 13:55 ` [PATCH 3/4] doc: README.socfpga: Update for U-boot 2022.04 Jit Loon Lim
2022-11-13 13:55 ` Jit Loon Lim [this message]
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=20221113135536.9920-4-jit.loon.lim@intel.com \
--to=jit.loon.lim@intel.com \
--cc=alif.zakuan.yuslaimi@intel.com \
--cc=boon.khai.ng@intel.com \
--cc=dinesh.maniyam@intel.com \
--cc=elly.siew.chin.lim@intel.com \
--cc=jagan@amarulasolutions.com \
--cc=kok.kiang.hea@intel.com \
--cc=marex@denx.de \
--cc=muhammad.hazim.izzat.zamri@intel.com \
--cc=raaj.lokanathan@intel.com \
--cc=sieu.mun.tang@intel.com \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=sin.hui.kho@intel.com \
--cc=teik.heng.chong@intel.com \
--cc=tien.fong.chee@intel.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=yau.wai.gan@intel.com \
/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