From: Bryan Brattlof <bb@ti.com>
To: Tom Rini <trini@konsulko.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Andrew Davis <afd@ti.com>,
Judith Mendez <jm@ti.com>, Kamlesh Gurudasani <kamlesh@ti.com>
Cc: UBoot Mailing List <u-boot@lists.denx.de>, Bryan Brattlof <bb@ti.com>
Subject: [PATCH 0/5] add support for hs bootflows to am62a
Date: Fri, 23 Dec 2022 19:15:20 -0600 [thread overview]
Message-ID: <20221224011525.4696-1-bb@ti.com> (raw)
Hello everyone!
Texas Instruments has started to enable security settings inside all the
boot ROM and TIFS firmware in all of their SoCs. One of the few changes
this brings is ROM and TIFS will now begin protecting the RAM regions
they're using with firewalls.
This means the wakeup domain's SPL will need to move the stack and heap
to HSM RAM to ensure it stays within its allotted memory regions as well
as move the needed boot information to the main domain's bootloaders that
will no longer have access to HSM RAM.
We will also need to edit the bootcmd to pull in the kernel and dtb's
fitImage if uboot is enforcing the high security bootflow. While we're
editing this bootcmd, we can also take the opportunity to convert it to
a distro_bootcmd macro.
Thanks for reviewing!
~Bryan
Bryan Brattlof (5):
configs: restrict am62ax wakup SPL size
configs: am62a: move stack and heap to HSM RAM
arm: mach-k3: copy bootindex to OCRAM for main domain SPL
configs: am62a: convert bootcmd to distro_bootcmd
configs: am62a: use kernel fitImage when using secure bootflow
arch/arm/mach-k3/Kconfig | 4 ++-
arch/arm/mach-k3/am62a7_init.c | 16 +++++++--
.../arm/mach-k3/include/mach/am62a_hardware.h | 17 +++++++++-
configs/am62ax_evm_a53_defconfig | 1 -
configs/am62ax_evm_r5_defconfig | 15 +++++---
include/configs/am62ax_evm.h | 34 +++++++++++++++++--
6 files changed, 74 insertions(+), 13 deletions(-)
base-commit: 52d91e1c20b399ddab276e2c03e5788ed5e5fdd2
--
2.39.0
next reply other threads:[~2022-12-24 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 1:15 Bryan Brattlof [this message]
2022-12-24 1:15 ` [PATCH 1/5] configs: restrict am62ax wakup SPL size Bryan Brattlof
2023-01-11 2:16 ` Tom Rini
2022-12-24 1:15 ` [PATCH 2/5] configs: am62a: move stack and heap to HSM RAM Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-24 1:15 ` [PATCH 3/5] arm: mach-k3: copy bootindex to OCRAM for main domain SPL Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-24 1:15 ` [PATCH 4/5] configs: am62a: convert bootcmd to distro_bootcmd Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-24 1:15 ` [PATCH 5/5] configs: am62a: use kernel fitImage when using secure bootflow Bryan Brattlof
2023-01-11 2:17 ` Tom Rini
2022-12-29 9:14 ` [PATCH 0/5] add support for hs bootflows to am62a Kamlesh Gurudasani
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=20221224011525.4696-1-bb@ti.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=jm@ti.com \
--cc=kamlesh@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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