path: root/docs/firmware-design.md
diff options
authorHarry Liebel <Harry.Liebel@arm.com>2014-04-01 19:28:07 +0100
committerHarry Liebel <Harry.Liebel@arm.com>2014-04-24 19:34:01 +0100
commitce19cf1bb56cfa72155b0c7f5d6c07bbf6efc11f (patch)
tree850417aea3a8bd5bba14bcce4cb2097ad3c1b725 /docs/firmware-design.md
parentf2199d95d931826be7f87af0935ac536812d0488 (diff)
FVP secure memory support documentation
Fixes ARM-software/tf-issues#64 Change-Id: I4e56c25f9dc7f486fbf6fa2f7d8253874119b989
Diffstat (limited to 'docs/firmware-design.md')
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/firmware-design.md b/docs/firmware-design.md
index 8c635a9..a40ddac 100644
--- a/docs/firmware-design.md
+++ b/docs/firmware-design.md
@@ -207,15 +207,17 @@ bits.
#### Platform initialization
-BL2 does not perform any platform initialization that affects subsequent
-stages of the ARM Trusted Firmware or normal world software. It copies the
-information regarding the trusted SRAM populated by BL1 using a
+BL2 copies the information regarding the trusted SRAM populated by BL1 using a
platform-specific mechanism. It calculates the limits of DRAM (main memory)
to determine whether there is enough space to load the BL3-3 image. A platform
defined base address is used to specify the load address for the BL3-1 image.
It also defines the extents of memory available for use by the BL3-2 image.
BL2 also initializes UART0 (PL011 console), which enables access to the
-`printf` family of functions in BL2
+`printf` family of functions in BL2. Platform security is initialized to allow
+access to access controlled components. On the Base FVP a TrustZone controller
+(TZC-400) is configured to give full access to the platform DRAM. The storage
+abstraction layer is initialized which is used to load further bootloader
#### BL3-1 (EL3 Runtime Firmware) image load