diff options
authorHarry Liebel <Harry.Liebel@arm.com>2014-05-01 14:09:16 +0100
committerHarry Liebel <Harry.Liebel@arm.com>2014-05-19 14:28:53 +0100
commit36eb6a755245e4eb0a40567783db6234f9f20d3f (patch)
parentc5c9b69c132c823aabc1e29c2ff6f30323c85483 (diff)
Improve BL3-0 documentation
Provide some information about the expected use of BL3-0. Fixes ARM-software/tf-issues#144 Change-Id: I5c8d59a675578394be89481ae4ec39ca37522750
2 files changed, 10 insertions, 1 deletions
diff --git a/docs/firmware-design.md b/docs/firmware-design.md
index a40ddac..76c27f7 100644
--- a/docs/firmware-design.md
+++ b/docs/firmware-design.md
@@ -219,6 +219,15 @@ access to access controlled components. On the Base FVP a TrustZone controller
abstraction layer is initialized which is used to load further bootloader
+#### BL3-0 (System Control Processor Firmware) image load
+Some systems have a separate System Control Processor (SCP) for power, clock,
+reset and system control. BL2 loads the optional BL3-0 image from platform
+storage into a platform-specific region of secure memory. The subsequent
+handling of BL3-0 is platform specific. Typically the image is transferred into
+SCP memory using a platform-specific protocol. The SCP executes BL3-0 and
+signals to the Application Processor (AP) for BL2 execution to continue.
#### BL3-1 (EL3 Runtime Firmware) image load
BL2 loads the BL3-1 image from platform storage into a platform-specific address
diff --git a/tools/fip_create/fip_create.c b/tools/fip_create/fip_create.c
index c97204a..d1802b7 100644
--- a/tools/fip_create/fip_create.c
+++ b/tools/fip_create/fip_create.c
@@ -53,7 +53,7 @@ uuid_t uuid_null = {0};
* const char* format_type_str[] = { "RAW", "ELF", "PIC" };
-/* Currently only BL2 and BL31 images are supported. */
+/* The images used depends on the platform. */
static entry_lookup_list_t toc_entry_lookup_list[] = {
{ "Trusted Boot Firmware BL2", UUID_TRUSTED_BOOT_FIRMWARE_BL2,