summaryrefslogtreecommitdiff
path: root/members/arm/openembedded/aarch64/15.07/INSTALL.textile
diff options
context:
space:
mode:
Diffstat (limited to 'members/arm/openembedded/aarch64/15.07/INSTALL.textile')
-rw-r--r--members/arm/openembedded/aarch64/15.07/INSTALL.textile162
1 files changed, 0 insertions, 162 deletions
diff --git a/members/arm/openembedded/aarch64/15.07/INSTALL.textile b/members/arm/openembedded/aarch64/15.07/INSTALL.textile
deleted file mode 100644
index 400457c..0000000
--- a/members/arm/openembedded/aarch64/15.07/INSTALL.textile
+++ /dev/null
@@ -1,162 +0,0 @@
-Linaro OpenEmbedded releases are made up of the following components.
-
-| *.img.gz | pre-built images for minimal, LAMP and LEG root filesystems |
-| hwpack_*.tar.gz | a single hardware pack for the Foundation, Versatile Express [1] and Base platform models |
-| linaro-image-*.rootfs.tar.gz | a choice of Root file system (RootFS) images |
-| Image | kernel used by UEFI |
-| foundation.axf | kernel binary wrapped for the Foundation model |
-| img.axf | kernel binary wrapped for the Versatile Express model |
-| *_bl1.bin | ARM Trused Firmware BL1 binaries |
-| *_fip.bin | ARM Trused Firmware Firmware Image Package (FIP) binaries |
-| *.dtb files | Device Tree Binaries |
-
-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.
-
-fn1. Linaro does not provide support for running the Versatile Express models.
-
-h2. Using pre-built image
-
-h3. Prerequisites
-
-* Ubuntu 12.04 64 bit or newer on your desktop PC ("www.ubuntu.com":http://www.ubuntu.com)
-* Foundation, Versatile Express or Base platform fast model ("Linaro ARMv8 Engineering":http://www.linaro.org/engineering/armv8/)
-* All artifacts for this release downloaded from the above list.
-* 14.04 linaro-image-tools or later
-
-
-h3. Installation Steps
-
-* Unzip the downloaded pre-built image
-
-bc. gunzip vexpress64-openembedded_*-armv8*.img.gz
-
-* Skip to the section below showing how to "Boot the image":#boot_the_image.
-Replace sd.img with the filename of the image unzipped above.
-
-h2. Build Your Own Image
-
-h3. Installing Linaro Image Tools
-
-There are multiple ways you can get the latest Linaro Image Tools:
-
-* Method 1: Install them from the Linaro Image Tools PPA
-
-bc. sudo add-apt-repository ppa:linaro-maintainers/tools
-sudo apt-get update
-sudo apt-get install linaro-image-tools
-
-* Method 2: Install from release tarball
-
-bc. cd <installation directory>
-wget http://releases.linaro.org/14.12/components/platform/linaro-image-tools/linaro-image-tools-2014.12.tar.gz
-tar zxvf linaro-image-tools-2014.12.tar.gz
-PATH=`pwd`/linaro-image-tools-2014.12:$PATH
-
-* Method 3: Building from the GIT repository
-
-bc. cd <working direcory>
-git clone git://git.linaro.org/infrastructure/linaro-image-tools.git
-PATH=`pwd`/linaro-image-tools:$PATH
-
-h3. Creating a disk image
-
-* Download the hardware pack (hwpack-*.tar.gz) from the above list
-* Download the rootfs (linaro-*.tar.gz) of your choice from the above list, LAMP is usually a good selection for a more fully featured disk image
-* Create the image
-
-bc. linaro-media-create --dev fastmodel --output-directory fastmodel --image_size 2000M --hwpack <hwpack filename> --binary <rootfs filename>
-cd fastmodel
-
-h2(#boot_the_image). Boot the image
-
-h3. Using the FVP Base AEMv8 model
-
-bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
-<path to model installation>/models/Linux64_GCC-4.1/FVP_Base_AEMv8A-AEMv8A \
--C pctl.startup=0.0.0.0 \
--C bp.secure_memory=0 \
--C cluster0.NUM_CORES=4 \
--C cluster1.NUM_CORES=4 \
--C cache_state_modelled=1 \
--C bp.pl011_uart0.untimed_fifos=1 \
--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
-
-To boot the A57x1 + A53x1 model:
-
-bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
-<path to model installation>/models/Linux64_GCC-4.1/FVP_Base_Cortex-A57x1-A53x1 \
--C pctl.startup=0.0.0.0 \
--C bp.secure_memory=0 \
--C cache_state_modelled=1 \
--C bp.pl011_uart0.untimed_fifos=1 \
--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:
-
-bc. ln -sf fvp-base-gicv2-psci.dtb fdt.dtb
-<path to model installation>/models/Linux64_GCC-4.1/FVP_Base_Cortex-A57x4-A53x4 \
--C pctl.startup=0.0.0.0 \
--C bp.secure_memory=0 \
--C cache_state_modelled=1 \
--C bp.pl011_uart0.untimed_fifos=1 \
--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
-
-To enable networking in the Base FVP models, you should install a network TAP on your local machine. See the "Fast Models User Guide":http://infocenter.arm.com/help/topic/com.arm.doc.dui0370q/ch02s13s01.html for more information on setting up a TAP for use with the models.
-
-Then, with the network TAP enabled, run with model as above, but with these additional parameters
-
-bc. -C bp.hostbridge.interfaceName=ARM$USER \
--C bp.smsc_91c111.enabled=true \
--C bp.smsc_91c111.mac_address=<MAC address, eg, 00:11:22:33:44:55>
-
-h3. Booting the image on the Foundation Model
-
-The latest version of the Foundation Model (version 0.8.5206, as of November 2013) is compatible with the ARM Trusted Firmware and UEFI. To launch the Foundation Model, use the following command:
-
-bc. ln -sf fvp-foundation-gicv2-psci.dtb fdt.dtb
-<path to model installation>/Foundation_v8 \
---cores=4 \
---no-secure-memory \
---visualization \
---gicv3 \
---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.
-
-h3. Booting the image on the Foundation Model using the AXF file
-
-If you are using an older version of Foundation Model (i.e. older than version 0.8.5206) and wish to use a pre-built image, you can simply unzip the downloaded pre-built image and the img-foundation.axf file and run the following command:
-
-bc. <path to model installation>/Foundation_v8 --image img-foundation.axf \
- --block-device vexpress64-openembedded_IMAGENAME-armv8_IMAGEDATE-XYZ.img
-
-To use the image you built with linaro-media-create in the steps above, run this command:
-
-bc. <path to model installation>/Foundation_v8 --image img-foundation.axf \
- --block-device sd.img
-
-h3. Using Ethernet networking on the Foundation Models
-
-The Foundation Models can be configured to use either NAT or Bridged mode.
-
-For the basic NAT confgiuration, add the following option to the command used to launch the model:
-
-bc. --network nat
-
-For Bridged networking, you will need to set up a network TAP as per the "FastModels user guide":http://infocenter.arm.com/help/topic/com.arm.doc.dui0370q/ch02s13s01.html. Then, the following options may work:
-
-bc. --network bridged --network-bridge=ARM$USER
-
-Details of the Foundation Model's command line options can be found in the "Foundation model documentation":http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0677b/BBAEFJEF.html on ARM's website.