summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan Harkin <ryan.harkin@linaro.org>2015-07-29 11:15:22 +0100
committerRyan Harkin <ryan.harkin@linaro.org>2015-07-29 11:15:22 +0100
commitcad0f6ca07fbfcb2522455fec9f28ebd79dc4eac (patch)
tree747c4aef5c429b61bda3d10f9ecc12f8e00d3c21
parent5d17a27525c2dbd9f5ab4628bd11fb28acab1373 (diff)
downloadmember-builds-15.07.tar.gz
15.07: update from ARM and gcc moved to 15.0215.07
Change-Id: I287429ff90a077b9ccc1f36bd1a0901038ab59f7 Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
-rw-r--r--members/arm/platforms/15.07/README.textile60
1 files changed, 18 insertions, 42 deletions
diff --git a/members/arm/platforms/15.07/README.textile b/members/arm/platforms/15.07/README.textile
index bcb7073..44fb315 100644
--- a/members/arm/platforms/15.07/README.textile
+++ b/members/arm/platforms/15.07/README.textile
@@ -1,6 +1,6 @@
h1. ARM Development Platform Software
-This page describes the monthly ARM landing team 15.07 software release for the ARM Juno and AEMv8-FVP Platforms
+This page describes the monthly ARM landing team 15.07 software release for the ARM Platforms
TABLE OF CONTENTS
@@ -16,13 +16,11 @@ TABLE OF CONTENTS
"2.4 Building the software":#build
-"2.5 Installing on your Juno":#install
+"2.5 Installing on your Juno or TC2":#install
"2.6 Running the FVP":#fvp
-"2.7 Installing on your TC2":#tc2
-
-"2.8 Using prebuilt binaries":#prebuilt
+"2.7 Using prebuilt binaries":#prebuilt
h2(#preface). 1. Preface
@@ -98,7 +96,7 @@ h3(#pre). 2.1 Prerequisites
** zlib1g-dev:i386
** zip
-* Install Linaro GCC (aarch64 little endian) from "here":http://releases.linaro.org/14.11/components/toolchain/binaries/aarch64-linux-gnu/gcc-linaro-4.9-2014.11-x86_64_aarch64-linux-gnu.tar.xz
+* Install Linaro GCC (aarch64 little endian) from "here":http://releases.linaro.org/15.02/components/toolchain/binaries/aarch64-linux-gnu/gcc-linaro-4.9-2015.02-3-x86_64_aarch64-linux-gnu.tar.xz
* Install the 'Repo' tool as per "Installing Repo":https://source.android.com/source/downloading.html. Do not initialize the Repo client
@@ -142,16 +140,12 @@ Unpack the compressed image file.
For FVP copy the image to the root directory of your workspace.
-For Juno insert a USB stick (minimum 4GB) into your system and run:
+For Juno or TC2 insert a USB stick (minimum 4GB) into your system and run:
bc. sudo dd if=<downloaded file>.img of=/dev/sd<x>
(where @<x>@ is the letter corresponding to the USB stick)
-For TC2 insert an USB stick (minimum 4GB) into your system and run:
-
-bc. sudo dd if=<downloaded file>.img of=/dev/sd<x>
-
For Juno Android, download "ramdisk.img":https://releases.linaro.org/15.06/android/reference-lcr/juno/ramdisk.img or
for FVP Android, download "ramdisk.img":https://releases.linaro.org/15.06/android/reference-lcr/fvp/ramdisk.img or
for TC2 Android, download "ramdisk.img":https://releases.linaro.org/15.06/android/reference-lcr/vexpress-tc2/ramdisk.img
@@ -180,7 +174,7 @@ h4. Choose your manifest
h4. Choose your environment type
-| Environment | Variable |
+| *Environment* | *Variable* |
| Android | @TYPE=android@ |
| BusyBox | @TYPE=busybox@ |
| OpenEmbedded | @TYPE=oe@ |
@@ -199,26 +193,28 @@ The build will create binaries for ARM Trusted Firmware, UEFI, U-Boot, Linux, ra
Running a different build will overwrite derived objects in the source tree, but will not overwrite the output folder created by the package step.
-h3(#install). 2.5 Installing on your Juno
+h3(#install). 2.5 Installing on your Juno or TC2
-* Mount the Juno flash device
+* Mount the board's flash device
Connect up the USB configuration port to your build system whereby the MMC which populates the NOR flash at boot will be mounted as a new drive.
-* Ensure your Juno system binaries are up to date
+* Ensure your system binaries are up to date
+
+For Juno, take the system binaries from the recovery folder from your workspace
+For TC2, take the system binaries from the vexpress-firmware folder from your workspace
-From your workspace recovery folder copy all of:
-SOFTWARE, SITE1, MB and config.txt overwriting the files that were already there on the mounted drive.
+For both Juno and TC2, delete all the files on the mounted drive and copy over all of @SOFTWARE@, @SITE1@, @MB@ and @config.txt@.
-* Copy the binaries you have built to your Juno
+* Copy the binaries you have built to your board
For UEFI copy the contents of @output/<variant>/uefi@ to the SOFTWARE folder
For U-Boot copy the contents of @output/<variant>/uboot@ to the SOFTWARE folder
-Where @<variant>@ is the argument to build-all.sh above - eg: juno-android
+Where @<variant>@ is the argument to build-all.sh above - eg: juno-android or tc2-android
-* For Android or OpenEmbedded Insert the USB stick created above into your Juno (not needed for BusyBox)
+* For Android or OpenEmbedded Insert the USB stick created above into your board (not needed for BusyBox)
-Power cycle your Juno and it will copy and run the new software images.
+Power cycle your board and it will copy and run the new software images.
h3(#fvp). 2.6 Running the FVP
@@ -248,27 +244,7 @@ Example 3: Running an OpenEmbedded UEFI variant:
bc. export DISK=lt-vexpress64-openembedded_minimal-armv8-gcc-4.9_20150620-722.img
./model-scripts/run_model.sh output/fvp-oe/uefi
-h3(#tc2). 2.7 Installing on your TC2
-
-* Mount the TC2 flash device
-
-Connect up the USB configuration port to your build system whereby the MMC which populates the NOR flash at boot will be mounted as a new drive.
-
-* Ensure your TC2 system binaries are up to date
-
-From your workspace vexpress-firmware folder copy all of:
-SOFTWARE, SITE1, MB and config.txt overwriting the files that were already there on the mounted drive.
-
-* Copy the binaries you have built to your TC2
-
-For UEFI copy the contents of @output/<variant>/uefi@ to the SOFTWARE folder
-Where @<variant>@ is the argument to build-all.sh above - eg: tc2-android
-
-* For Android or OpenEmbedded Insert the USB stick created above into your board (not needed for BusyBox)
-
-Power cycle your board and it will copy and run the new software images.
-
-h3(#prebuilt). 2.8 Using prebuilt binaries
+h3(#prebuilt). 2.7 Using prebuilt binaries
If you want to use prebuilt firmware and kernel binaries rather than download and build the software as described above, first, you should follow the instructions in "section 2.3":#down-bins and then download the prebuilt firmware images for the platform you wish to use.