Reference Platform Build – CE OpenEmbedded
- Build URL: https://ci.linaro.org/job/96boards-reference-platform-openembedded-rocko/DISTRO=rpb,MACHINE=juno,label=docker-stretch-amd64/12/
- Manifest URL: https://github.com/96boards/oe-rpb-manifest.git
- Manifest branch: rocko
- Manifest commit: a8c4296
AArch64 OpenEmbedded ARM Fast Models Release
The AArch64 Open Embedded Engineering Build for ARM Fast Models for ARMv8 is produced, validated and released by Linaro, based on the latest AArch64 open source software from Tianocore EDK2 (UEFI), the Linux kernel, ARM Trusted Firmware and OpenEmbedded. It is produced to enable software development for AArch64 prior to hardware availability, and facilitates development of software that is independent of the specific CPU implementation. This build focuses on availability of new features in order to provide a basis for ongoing and dependent software development.
Linaro releases monthly binary images of this engineering build. This release includes Linaro OpenEmbedded images for Versatile Express, Base and Foundation Fixed Virtual Platform (FVP) models from ARM. Sources are also made available so you can build your own images.
About the AArch64 OpenEmbedded Engineering Build
This release has been tested on the Base FVPs from ARM (since September 2013), in addition to the updated Foundation FVP (since November 2013) and Versatile Express FVP.
The ‘Base’ platform is an evolution from the Versatile Express (VE) platform that is better able to support new system IP, larger memory maps and multiple CPU clusters. The changes in the Base platform memory map require that software or device trees which specify peripheral addresses may need to be modified for the Base FVPs. Device trees for these FVPs are included in this release.
This build has been tested to work on the following FVPs:
- FVP_VE_AEMv8A (previously called RTSM_VE_AEMv8A before v5.0)
The Foundation_v8 FVP is free to use (download from ARM http://www.arm.com/fvp), while the others are licensed from ARM. More information on these specific FVPs is included with this release documentation.
The Base and Foundation FVPs use the following software for boot and runtime firmware services in this engineering build:
- ARM Trusted Firmware provides a reference implementation of secure world software for ARMv8-A, including Exception Level 3 (EL3) software
- Tianocore EDK2 which provides a UEFI based boot environment for the normal world operating system or hypervisor (in this case, Linux)
The VE FVP continues to be booted using the AArch64 Linux boot-wrapper.
The same kernel image is used for all of these models, though the FVP_VE_AEMv8A image is encapsulated by the kernel boot-wrapper as in previous releases.
Where To Find More Information
More information on Linaro can be found on our website.
More information on ARM FVPs can be found on ARM’s website: http://www.arm.com/fvp.
More information on ARM Trusted Firmware and Platform Design Documents (PDDs) can be found on the project’s GitHub repository: http://github.com/ARM-software/arm-trusted-firmware.
More information on building UEFI for AArch64 can be found on Linaro’s wiki: https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/build.
Feedback and Support
Relating to the ARM Fixed Virtual Platforms:
- For technical support on the Foundation_v8 FVP use the ARM support forums, http://forums.arm.com
- For technical support on the Base and VE FVPs contact ARM Fast Models Support, firstname.lastname@example.org
- To provide feedback to ARM relating to any of the FVPs, please refer to the respective product documentation
To provide feedback or ask questions about the ARM Trusted Firmware, please create a new Issue at GitHub.
Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development.
- Linaro Development mailing list
- Linaro IRC channel on irc.freenode.net at
- Bug reports should be filed in Launchpad to Linaro OpenEmbedded project.
- Questions? ask Linaro.
- Interested in commercial support? Inquire at Linaro support
Changes in this release
- OpenDataPlane recipe added
- Linaro PowerDebug recipe added
- ACPICA updated to 20131115
- Add initscript for gator
Linaro OpenEmbedded releases are made up of the following components.
||pre-built images for minimal, LAMP and LEG root filesystems|
|hwpack_*.tar.gz||a single hardware pack for the Foundation, Versatile Express  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|
||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.
1 Linaro does not provide support for running the Versatile Express models.
Using pre-built image
- Ubuntu 12.04 64 bit or newer on your desktop PC (www.ubuntu.com)
- Foundation, Versatile Express, Base platform fast model (Linaro ARMv8 Engineering) or QEMU 2.1+
- All artifacts for this release downloaded from the above list.
- 14.04 linaro-image-tools or later
- Unzip the downloaded pre-built image
- Skip to the section below showing how to Boot the image.
Replace sd.img with the filename of the image unzipped above.
Build Your Own Image
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
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
cd <installation directory> wget http://releases.linaro.org/14.04/components/platform/linaro-image-tools/linaro-image-tools-2014.04.tar.gz tar zxvf linaro-image-tools-2014.04.tar.gz PATH=`pwd`/linaro-image-tools/2014.04:$PATH
- Method 3: Building from the GIT repository
cd <working direcory> git clone git://git.linaro.org/infrastructure/linaro-image-tools.git PATH=`pwd`/linaro-image-tools:$PATH
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
linaro-media-create --dev fastmodel --output-directory fastmodel --image_size 2000M --hwpack <hwpack filename> --binary <rootfs filename> cd fastmodel
Boot the image
Using the FVP Base AEMv8 model
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
Using the FVP Base Cortex model
To boot the A57×1 + A53×1 model:
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 A57×4 + A53×4 model, use the same command, only specify a different model binary:
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
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 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
-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>
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:
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.
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:
<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:
<path to model installation>/Foundation_v8 --image img-foundation.axf \ --block-device sd.img
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:
For Bridged networking, you will need to set up a network TAP as per the FastModels user guide. Then, the following options may work:
--network bridged --network-bridge=ARM$USER
Details of the Foundation Model’s command line options can be found in the Foundation model documentation on ARM’s website.
QEMU supports ARMv8 since 2.1 release. To boot up Linaro image with QEMU, you will need the kernel (filename Image) and selected prebuilt image (vexpress64-openembedded_IMAGENAME-armv8_IMAGEDATE-XYZ.img.gz). Uncompress the downloaded image and run:
qemu-system-aarch64 -m 1024 -cpu cortex-a57 -nographic -machine virt \ -kernel Image -append 'root=/dev/vda2 rw rootwait mem=1024M console=ttyAMA0,38400n8' \ -netdev user,id=user0 -device virtio-net-device,netdev=user0 -device virtio-blk-device,drive=disk \ -drive if=none,id=disk,file=vexpress64-openembedded_IMAGENAME-armv8_IMAGEDATE-XYZ.img
See QEMU manual for details on installing and using Qemu.
OpenJDK FCS Release for AArch64
This release of OpenJDK is a fully functional, stable release of OpenJDK. It has been extensively tested using test suites including the JTREG, JCK and Mauve test suites as well as real work applications such as Hadoop, Eclipse and industry standard benchmarks such as SPECjvm2008 and PECjbb2013. There are no known critical failures when used with standard options. There are a number of failures when used with certain non standard options. These failure are detailed below.
The release is being made available in two variants:
As JDK8 is a complete revision of JDK, a backport to OpenJDK 7 is provided for compatibility with the known and proven JDK7. This release is based on the jdk7u60-b04 tag of the JDK7 updates tree.
Supported HotSpot Technologies
Both OpenJDK releases support the Client (C1) and Server (C2) JIT compilers in addition to supporting the Template assembler based interpreter and the ‘Zero’ C based interpreter.
The default execution model is Server (C2) JIT using Tiered Compilation. Under this model code is first executed by the Template nterpreter. When code is deemed to be ‘hot’ it is compiled initially using the Client (C1) JIT. The code compiled by the C1 JIT contains profiling code. If a method is deemed to be sufficiently hot it is recompiled with the Server (C2) JIT. The C2 JIT uses the profiling information collected by the C1 JIT to generate highly optimal execution path targetted code.
Different execution models may be selected using the following command line options.
- -server – The default Server (C2) JIT
- -client – The Client (C1) JIT
- -Xint – The Template assembler based interpreter
- -zero – The ‘Zero’ C based interpreter
In addition the following options may be specified
- The default with -server. Enable Tiered compilation as described above.
- Disable Tiered compilation. Code is compiled directly with the Server (C2) JIT. Using this option will generate less efficient code because the profiling information gathered by the C1 compiler will not be available.
Source and binary bundles
Source bundles may be downloaded from:
Pre-built binaries may be downloaded from:
There are two categories of tests run on a daily basis.
These tests are run on the foundation model. Because of the performance limitations of the foundation model a limited subset of the JTreg and Mauve test suites are run daily.
Results are published daily.
These tests are run on ARMv8 hardware which is hosted in our Cambridge lab but is not publicly available in LAVA. The entire JTreg test suite is run on a daily basis for both Client and Server JITs.
Results are published by email to email@example.com. This email list may be subscribed to by visiting:
Note: that for the hosted tests, if the daily test determines that there has been no change to the source tree then the tests are not run. This is done to reduce bandwidth on the email list.
Note: In spite of the slowness of the tests executed on the foundation model, which prevents complete test execution on a daily basis, we periodically verify that the complete test execution provides the very same identical results on both the foundation model and the real h/w in our lab. Please note that no performance numbers are posted to the mailing lists, only functional pass/fail test results.
-XX:+UseBiasedLocking causes a fatal error
- The implementation of Biased Locking has not been completed in the AArch64 port and use of this option may cause fatal errors.
Workaround: Do not use the -XX:+UseBiasedLocking option.
Assertion failure with -XX:-InlineObjectHash and -XX:-ProfileInterpreter
This combination of options may cause the following fatal error to be generated:
- assert(false) failed: this call site should not be polymorphic
Workaround: Do not use this combination of options.
We would like to thank RedHat, and especially Andrew Haley and Andrew Dinn, for starting this project and for the huge efforts they have put in to deliver a high quality, high performance Java solution for AArch64 which is available as Open Software. We would also like to thank all in the Open Source community who have contributed to the projects, either through bug fixes or suggestions or through testing early releases of the software and submitting bug reports.