aboutsummaryrefslogtreecommitdiffstats
path: root/docs/firmware-design.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/firmware-design.md')
-rw-r--r--docs/firmware-design.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/firmware-design.md b/docs/firmware-design.md
index 294349d9c..74ea5eb88 100644
--- a/docs/firmware-design.md
+++ b/docs/firmware-design.md
@@ -1511,11 +1511,16 @@ The ToC header and entry formats are described in the header file
ARM Trusted firmware.
The ToC header has the following fields:
+
`name`: The name of the ToC. This is currently used to validate the header.
`serial_number`: A non-zero number provided by the creation tool
- `flags`: Flags associated with this data. None are yet defined.
+ `flags`: Flags associated with this data.
+ Bits 0-13: Reserved
+ Bits 32-47: Platform defined
+ Bits 48-63: Reserved
A ToC entry has the following fields:
+
`uuid`: All files are referred to by a pre-defined Universally Unique
IDentifier [UUID] . The UUIDs are defined in
`include/firmware_image_package`. The platform translates the requested
@@ -1532,7 +1537,7 @@ that can be loaded by the ARM Trusted Firmware from platform storage. The tool
currently only supports packing bootloader images. Additional image definitions
can be added to the tool as required.
-The tool can be found in `tools/fip_create`.
+The tool can be found in `tools/fiptool`.
### Loading from a Firmware Image Package (FIP)