summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan Harkin <ryan.harkin@linaro.org>2014-05-28 10:48:40 +0100
committerRyan Harkin <ryan.harkin@linaro.org>2014-05-28 10:48:40 +0100
commit62568fa2a2292e0cabe0e565ef1b40da411e9403 (patch)
tree09b36fec566365abfd18a4166dd91c754d1e60e3
parent4eb83ad27243e9d4e82f219583c992c7c6ae1555 (diff)
14.05: update instructions for using FIP binary
This release seeing *_fip.bin being deployed for the first time. The instructions have been updated to show the user how to use the new Trusted Firmware scheme. Change-Id: I2a8f90c44145b3c57791743947234f9a96caa6cd Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
-rw-r--r--INSTALL.textile26
1 files changed, 10 insertions, 16 deletions
diff --git a/INSTALL.textile b/INSTALL.textile
index 6248244..ca62106 100644
--- a/INSTALL.textile
+++ b/INSTALL.textile
@@ -6,9 +6,9 @@ Linaro OpenEmbedded releases are made up of the following components.
| Image | kernel used by UEFI |
| foundation.axf | kernel binary wrapped for the Foundation model |
| img.axf | kernel binary wrapped for the Versatile Express model |
-| [bB]*.bin | ARM Trused Firmware binaries |
+| *_bl1.bin | ARM Trused Firmware BL1 binaries |
+| *_fip.bin | ARM Trused Firmware Firmware Image Package (FIP) binaries |
| *.dtb files | Device Tree Binaries |
-| uefi_fvp-base.bin | UEFI binary |
Other files such as *.manifest, *.txt and *.html provide information such as package contents or MD5SUMs about the files they share a common filename with.
@@ -69,12 +69,6 @@ cd fastmodel
h2(#boot_the_image). Boot the image
-Before running the model, create links for the firmware images:
-
-bc. ln -s fvp_bl1.bin bl1.bin
-ln -s fvp_bl2.bin bl2.bin
-ln -s fvp_bl31.bin bl31.bin
-
h3. Using the FVP Base AEMv8 model
bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
@@ -85,8 +79,8 @@ bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
-C cluster1.NUM_CORES=4 \
-C cache_state_modelled=1 \
-C bp.pl011_uart0.untimed_fifos=1 \
--C bp.secureflashloader.fname=bl1.bin \
--C bp.flashloader0.fname=uefi_fvp-base.bin \
+-C bp.secureflashloader.fname=fvp_bl1.bin \
+-C bp.flashloader0.fname=fvp_fip.bin \
-C bp.virtioblockdevice.image_path=sd.img
h3. Using the FVP Base Cortex model
@@ -99,8 +93,8 @@ bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
-C bp.secure_memory=0 \
-C cache_state_modelled=1 \
-C bp.pl011_uart0.untimed_fifos=1 \
--C bp.secureflashloader.fname=bl1.bin \
--C bp.flashloader0.fname=uefi_fvp-base.bin \
+-C bp.secureflashloader.fname=fvp_bl1.bin \
+-C bp.flashloader0.fname=fvp_fip.bin \
-C bp.virtioblockdevice.image_path=sd.img
To boot the A57x4 + A53x4 model, use the same command, only specify a different model binary:
@@ -111,8 +105,8 @@ bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
-C bp.secure_memory=0 \
-C cache_state_modelled=1 \
-C bp.pl011_uart0.untimed_fifos=1 \
--C bp.secureflashloader.fname=bl1.bin \
--C bp.flashloader0.fname=uefi_fvp-base.bin \
+-C bp.secureflashloader.fname=fvp_bl1.bin \
+-C bp.flashloader0.fname=fvp_fip.bin \
-C bp.virtioblockdevice.image_path=sd.img
h3. Using Ethernet networking with the FVP Base Platform Models
@@ -135,8 +129,8 @@ bc. ln -sf fvp-foundation-gicv2-psci.dtb fdt.dtb
--no-secure-memory \
--visualization \
--gicv3 \
---data=bl1.bin@0x0 \
---data=uefi_fvp-base.bin@0x8000000 \
+--data=fvp_bl1.bin@0x0 \
+--data=fvp_fip.bin@0x8000000 \
--block-device=sd.img
note: it is intentional that we suggest using the GICv2 DTB file, whilst specifying GICv3 on the model command line. In this mode, you are using the GICv3 controller in GICv2 compatibility mode, which is the default recommended by ARM.