ARM Development Platform Software

This page describes the monthly ARM landing team 15.07 software release for the ARM Platforms

TABLE OF CONTENTS

1. Preface

2. Software

2.1 Prerequisites

2.2 Downloading the software and binaries

2.3 Downloading the filesystem binaries

2.4 Building the software

2.5 Installing on your Juno or TC2

2.6 Running the FVP

2.7 Using prebuilt binaries

1. Preface

The ARM software images contained in this released are distributed according to the EULA

• This release supports the following hardware platforms:
  • Juno ARM Development Platform
  • Cortile Express V2P-CA15×2_CA7×3
• and the following FVP (Fixed Virtual Platform) models:
  • ARMv8 Foundation
  • AEMv8A Base

This document describes how to:

• 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, Fast Model / FVP, or this software, please contact support@arm.com.

For a description of the Juno hardware and how to get started with the platform see the Juno Getting Started Guide

For a description of ARM Fastmodels see Modeling and ESL

2. Software

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

• Linaro Tracking Kernel (latest), plus one of:
  • OpenEmbedded filesystem
  • BusyBox filesystem

Note: The Linaro Tracking Kernel does not support the Android LCR filesystem.

2.1 Prerequisites

• To be run on an Ubuntu 14.04 LTS system

• Preinstall the following packages:
  • acpica-tools
  • bc
  • bison
  • build-essential
  • curl
  • flex
  • g++-multilib
  • gcc-multilib
  • genext2fs
  • git
  • gperf
  • iasl
  • libc6:i386
  • libstdc++6:i386,
  • libncurses5:i386
  • libxml2-utils
  • make
  • openjdk-7-jdk
  • python
  • python-mako
  • uuid-dev
  • wget
  • zlib1g:i386
  • zlib1g-dev:i386
  • zip

• Install Linaro GCC (aarch64 little endian) from here

• Install the ‘Repo’ tool as per Installing Repo. Do not initialize the Repo client

• If necessary, also register for authenticated access by following the instructions in the “Using Authentication” section of Installing Repo

• Configure Git’s user.email and user.name attributes before using repo.

2.2 Downloading the software sources

• Create a workspace directory and cd into it
• Use the repo tool to sync all the software GITs
  For a LSK kernel:

repo init -u https://git.linaro.org/landing-teams/working/arm/manifest -b 15.07 -m pinned-lsk.xml

For the latest tracking kernel:

repo init -u https://git.linaro.org/landing-teams/working/arm/manifest -b 15.07 -m pinned-latest.xml

Then in both cases:

repo sync -j8

2.3 Downloading the filesystem binaries

Ignore this section if you want to boot BusyBox

For Juno Android, download juno.img.bz2 (accept the EULA to download)

For FVP Android, download fvp.img.bz2

For TC2 Android, download vexpress.img.bz2

For any 64-bit platform minimal OE, download lt-vexpress64-openembedded_minimal-armv8-gcc-4.9_20150620-722.img.gz

For any 64-bit platform LAMP OE, download lt-vexpress64-openembedded_lamp-armv8-gcc-4.9_20150620-722.img.gz

For any 32-bit platform ALIP OE, download lsk-vexpress-openembedded_alip-armv7a-gcc-4.9_20150620-722.img.gz

Unpack the compressed image file.

For FVP copy the image to the root directory of your workspace.

For Juno or TC2 insert a USB stick (minimum 4GB) into your system and run:

sudo dd if=<downloaded file>.img of=/dev/sd<x>

(where <x> is the letter corresponding to the USB stick)

For Juno Android, download ramdisk.img or
for FVP Android, download ramdisk.img or
for TC2 Android, download ramdisk.img
and copy to the root directory of your workspace.

2.4 Building the software

• First decide how you wish to specify your cross compiler:
  • Add the CROSS_COMPILE=<path-and-prefix> prefix to all build script invocations.
  • Edit <workspace>/build-scripts/variants files to make CROSS_COMPILE point at the path and prefix to where you installed Linaro GCC.
  • note: you may specify the prefix without a path if the compiler is on your path.
• Next, choose the setup from the tables below and copy the variables into your shell before executing the “Commands to run”:

Choose your platform

Platform	Variable
Juno ARM Development Platform	PLATFORM=juno
FVP Foundation or AEMv8 models	PLATFORM=fvp
Versatile Express TC2	PLATFORM=tc2

Choose your manifest

Kernel Version	Variable
LSK 3.10	MANIFEST=lsk
Latest Tracking Kernel	MANIFEST=latest

Choose your environment type

Environment	Variable
Android	TYPE=android
BusyBox	TYPE=busybox
OpenEmbedded	TYPE=oe

Commands to run

Once you have configured the variables in your shell, run these commands from the root directory of your workspace to build the software components and package them into an output folder:

repo init -u https://git.linaro.org/landing-teams/working/arm/manifest -b 15.07 -m pinned-${MANIFEST}.xml
repo sync -j8
./build-scripts/build-all.sh ${PLATFORM}-${TYPE}
./build-scripts/build-all.sh ${PLATFORM}-${TYPE} package

The build will create binaries for ARM Trusted Firmware, UEFI, U-Boot, Linux, ramdisk and a DTB where appropriate. For Aarch64 platofrms, the Firmware components will then be packaged into a FIP. 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.

2.5 Installing on your Juno or TC2

• 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 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

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 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 or 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.

2.6 Running the FVP

To run the FVP models, you must first set the following variables:

Variable	Usage	Example
$MODEL	This sets the path and filename of the model executable	/usr/local/FVP_Base_AEMv8A-AEMv8A
$DISK	This sets the path and filename of the disk image. Busybox variants don’t need to set DISK, however both OE and Android variants will fail to boot without it. You should download and unzip the disk image before running the model.	$USER/Downloads/fvp.img

Then, from your workspace root directory, you launch the model, telling it the path of the variant you wish to boot.

First set the model variable

export MODEL=/usr/local/FVP_Base_AEMv8A-AEMv8A

Example 1: Running a busybox uboot variant:

./model-scripts/run_model.sh output/fvp-busybox/uboot

Example 2: Running an Android uboot variant:

export DISK=fvp.img
 ./model-scripts/run_model.sh output/fvp-android/uboot

Example 3: Running an OpenEmbedded UEFI variant:

export DISK=lt-vexpress64-openembedded_minimal-armv8-gcc-4.9_20150620-722.img
./model-scripts/run_model.sh output/fvp-oe/uefi

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 and then download the prebuilt firmware images for the platform you wish to use.

The pre-built ZIPs contain the 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). For TC2, the files should be copied to the SOFTWARE folder of the mounted drive as per the vexpress-firmware image in section 2.7.

Other variants are only available when built from source. The current prebuilt binaries are targeted at Mobile, Enterprise and developer segments.

Juno Prebuilt Binaries

Prebuilt binaries are available by following the links in the table below. These binaries contain the Juno recovery images and so can be used to restore a broken system.

Filename/Link	Variant	Kernel	Bootloader
juno-lsk-android-uboot.zip	Android	LSK 3.10	U-Boot
juno-latest-oe-uefi.zip	OpenEmbedded	latest	UEFI
juno-latest-busybox-uboot.zip	BusyBox	latest	U-Boot

FVP Prebuilt Binaries

Prebuilt binaries are available by following the links in the table below.

Filename/Link	Variant	Kernel	Bootloader
fvp-lsk-android-uboot.zip	Android	LSK 3.10	U-Boot
fvp-latest-oe-uefi.zip	OpenEmbedded	latest	UEFI
fvp-latest-busybox-uboot.zip	BusyBox	latest	U-Boot

TC2 Prebuilt Binaries

Prebuilt binaries are available by following the links in the table below.

Filename/Link	Variant	Kernel	Bootloader
tc2-lsk-android-uefi.zip	Android	LSK 3.10	U-Boot
tc2-latest-oe-uefi.zip	OpenEmbedded	latest	UEFI
tc2-latest-busybox-uefi.zip	BusyBox	latest	U-Boot