15.07: Readme updates from ARM-PEG

Change-Id: Iaacd224c2941260db5e83f485b3ff2bea62b0488
Signed-off-by: James King <james.king@arm.com>

1 files changed, 28 insertions, 14 deletions

diff --git a/members/arm/platforms/README.textile b/members/arm/platforms/README.textile
index 587186e..03a813e 100644
--- a/members/arm/platforms/README.textile
+++ b/members/arm/platforms/README.textile
@@ -27,25 +27,38 @@ h2(#preface). 1. Preface
 
 The ARM software images contained in this released are distributed according to the "EULA":https://wiki.linaro.org/ARM/Juno/EULA
 
-This release page describes how to download the source code and binaries, build the source code and install all the binaries on your platform. There are also links below to download Linaro prebuilt binaries.
+This release supports both the "ARM Juno board":http://www.arm.com/products/tools/development-boards/versatile-express/juno-arm-development-platform.php and the "AEMv8-A FVP":http://www.arm.com/products/tools/models/fast-models/foundation-model.php platforms.
 
-For a description of the Juno hardware and how to get started with the platform see the "Juno Technical Overview":http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.subset.boards.express/index.html
+This document describes how to:
 
-For a description of ARM Fastmodels see "Modeling and ESL":http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.set.models/index.html
+* Obtain software sources and related binaries
+* Build the software sources
+* Install the resulting binaries on your platform
+
+There are also instructions detailing the use of Linaro's prebuilt binaries.
 
-For any problems with your Juno system, fastmodel or this software please contact support@arm.com providing details of which release you are using.
+For any problems with your Juno system, Fast Model / FVP, or this software, please contact "support@arm.com":mailto:support@arm.com.
+
+For a description of the Juno hardware and how to get started with the platform see the "Juno Getting Started Guide":http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0928a/index.html
+
+For a description of ARM Fastmodels see "Modeling and ESL":http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.set.models/index.html
 
 h2(#sw). 2. Software
 
-This release supports 3 different software stacks which have been validated on the platforms. All include board firmware, System Power Controller firmware, ARM Trusted firmware and a choice of UEFI or u-boot loader. The options are:
+This release supports three different software stacks, each of which have been validated on both the ARM Juno board and the AEMv8-A FVP. These software stacks include board firmware, System Control Processor firmware, ARM Trusted Firmware, and a choice of either UEFI or U-Boot.
+
+The options are:
+
+* LSK - Linaro Stable Kernel (v3.10), plus one of:
+** Android LCR filesystem
+** OpenEmbedded filesystem
+** BusyBox filesystem
 
-* LSK - Linaro Stable Kernel (v3.10) + Android LCR
-* LSK - Linaro Stable Kernel (v3.10) + OpenEmbedded Filesystem
-* LSK - Linaro Stable Kernel (v3.10) + BusyBox Filesystem
-* Linaro Tracking Kernel (latest) + OpenEmbedded Filesystem
-* Linaro Tracking Kernel (latest) + BusyBox Filesystem
+* Linaro Tracking Kernel (latest), plus one of:
+** OpenEmbedded filesystem
+** BusyBox filesystem
 
-For each option the instructions here use 15.06 release prebuilt binaries for the Android or OpenEmbedded filesystems. Standard Linaro instructions can be used to rebuild the filesystem yourself.
+Note: The Linaro Tracking Kernel does not support the Android LCR filesystem.
 
 h3(#pre). 2.1 Prerequisites
 
@@ -175,7 +188,7 @@ bc. ./build-scripts/build-all.sh fvp-oe
 bc. ./build-scripts/build-all.sh fvp-busybox
 ./build-scripts/build-all.sh fvp-busybox package
 
-The build will create binaries for ARM Trusted Firmware, UEFI, u-boot, Linux, ramdisk and a DTB. The Firmware components will then be packaged into a FIP and all the binaries copied under the "output" folder.
+The build will create binaries for ARM Trusted Firmware, UEFI, U-Boot, Linux, ramdisk and a DTB. The Firmware components will then be packaged into a FIP and all the binaries copied under the "output" folder.
 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
@@ -192,7 +205,7 @@ SOFTWARE, SITE1, MB and config.txt overwriting the files that were already there
 * Copy the binaries you have built to your Juno
 
 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
+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
 
 * For Android or OpenEmbedded Insert the USB stick created above into your Juno (not needed for BusyBox)
@@ -232,7 +245,8 @@ 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.
 
-The pre-built ZIP contains the following ZIP files for each supported configuration. For Juno the contents should be  copied to the SOFTWARE folder as described in section 2.5 and for FVP the contents should be copied to your workspace output folder (which you will need to create if you have not run a build).
+The pre-built ZIP contains the following ZIP files for each supported configuration. For Juno the contents should be copied to the
+root of the mounted drive as per the recovery image in section 2.5. For FVP the contents should be copied to your workspace output folder (which you will need to create if you have not run a build).
 
 Other variants are only available when built from source.  The current prebuilt binaries are targeted at Mobile, Enterprise and developer segments.