Am 25. August 2020 18:57:57 MESZ schrieb Simon Glass sjg@chromium.org:
Hi Heinrich,
On Tue, 25 Aug 2020 at 04:16, Heinrich Schuchardt xypron.glpk@gmx.de wrote:
On 22.08.20 04:36, Simon Glass wrote:
Add an entry for ARM Trusted Firmware's 'BL31' payload, which is
the
device's main firmware. Typically this is U-Boot.
Signed-off-by: Simon Glass sjg@chromium.org
tools/binman/README.entries | 10 ++++++++++ tools/binman/etype/atf_bl31.py | 20 ++++++++++++++++++++ tools/binman/ftest.py | 9 +++++++++ tools/binman/test/165_atf_bl31.dts | 16 ++++++++++++++++ 4 files changed, 55 insertions(+) create mode 100644 tools/binman/etype/atf_bl31.py create mode 100644 tools/binman/test/165_atf_bl31.dts
diff --git a/tools/binman/README.entries
b/tools/binman/README.entries
index 97bfae16116..85b8ec9fa73 100644 --- a/tools/binman/README.entries +++ b/tools/binman/README.entries @@ -11,6 +11,16 @@ features to produce new behaviours.
+Entry: atf-bl31: Entry containing an ARM Trusted Firmware (ATF)
BL31 blob
+-------------------------------------------------------------------------
+Properties / Entry arguments:
- atf-bl31-path: Filename of file to read into entry
+This entry holds the run-time firmware started by ATF.
No, BL31 is started by U-Boot SPL on the Sunxi platform.
So perhaps I should reword this to indicate it can go either way?
If SPL is not loading BL31, we don't need this value. Instead we will pass U-Boot as BL33 to the TF-A make command.
Best regards
Heinrich
Best regards
[..]
Regards, Simon