From: <kamlesh@ti.com>
To: <u-boot@lists.denx.de>
Cc: Kamlesh Gurudasani <kamlesh@ti.com>
Subject: [PATCH 1/2] arm: mach-k3: am62: move scratch board area to HSM RAM
Date: Thu, 2 Mar 2023 19:40:46 +0530 [thread overview]
Message-ID: <20230302141047.3175114-2-kamlesh@ti.com> (raw)
In-Reply-To: <20230302141047.3175114-1-kamlesh@ti.com>
From: Kamlesh Gurudasani <kamlesh@ti.com>
On high security devices, ROM enables firewalls to protect the OCSRAM
region access during bootup. Only after TIFS has started (and had
time to disable the OCSRAM firewall region) will we have write access to
the region.
So, move scratch board area to HSM RAM.
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
---
arch/arm/mach-k3/include/mach/am62_hardware.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/mach-k3/include/mach/am62_hardware.h b/arch/arm/mach-k3/include/mach/am62_hardware.h
index 17d3228cba..db4a32cd46 100644
--- a/arch/arm/mach-k3/include/mach/am62_hardware.h
+++ b/arch/arm/mach-k3/include/mach/am62_hardware.h
@@ -55,7 +55,6 @@
#define ROM_EXTENDED_BOOT_DATA_INFO 0x43c3f1e0
-/* Use Last 2K as Scratch pad */
-#define TI_SRAM_SCRATCH_BOARD_EEPROM_START 0x70000000
+#define TI_SRAM_SCRATCH_BOARD_EEPROM_START 0x43c30000
#endif /* __ASM_ARCH_AM62_HARDWARE_H */
--
2.34.1
next prev parent reply other threads:[~2023-03-02 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 14:10 [PATCH 0/2] add support for hs bootflows on am62 devices kamlesh
2023-03-02 14:10 ` kamlesh [this message]
2023-03-22 18:03 ` [PATCH 1/2] arm: mach-k3: am62: move scratch board area to HSM RAM Tom Rini
2023-03-02 14:10 ` [PATCH 2/2] configs: am62: move stack and heap " kamlesh
2023-03-22 18:03 ` Tom Rini
2023-03-03 1:21 ` [PATCH 0/2] add support for hs bootflows on am62 devices Bryan Brattlof
2023-03-03 9:09 ` Kamlesh Gurudasani
2023-03-16 10:35 ` Kamlesh Gurudasani
2023-03-16 18:15 ` Tom Rini
2023-03-17 8:51 ` [EXTERNAL] " Kamlesh Gurudasani
2023-03-17 14:37 ` Tom Rini
2023-03-20 8:34 ` 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=20230302141047.3175114-2-kamlesh@ti.com \
--to=kamlesh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.