NameLast modifiedSizeLicense
Parent Directory Parent Directory
other MANIFEST 13-Jan-2018 02:26 253 open
other MD5SUMS 13-Jan-2018 02:26 285 open
application/x-tar boot.tar.bz2 13-Jan-2018 02:26 6.3M open
other kernel_config 13-Jan-2018 02:26 73.1K open
application/x-sh linaro_android_build_cmds.sh 13-Jan-2018 02:26 8.6K open
text pinned-manifest.xml 13-Jan-2018 02:26 93.6K open
other ramdisk.img 13-Jan-2018 02:26 918.4K open
text source-manifest.xml 13-Jan-2018 02:26 48.9K open
other system.img 26-Feb-2018 22:55 750.0M open
application/x-tar system.tar.bz2 26-Feb-2018 22:55 269.3M open
other userdata.img 26-Feb-2018 22:55 550.0M open
application/x-tar userdata.tar.bz2 26-Feb-2018 22:56 46.3M open


About the Linaro Confectionary Release for FVP (Multi-arch 64-bit)

The Linaro Confectionary release is based on the AOSP Lollipop
Android-5.1.1_r3 version. The reference build is the userdebug variant
build, it contains multi-arch support allowing full use of the 64-bit
ARMv8-A architecture and supports both 64-bit and 32-bit applications,
and has selinux enabled by default.

Java-only applications will run as 64-bit in the supplied configuration
with no modification. The release uses the kernel from the Linaro ARM
Landing team which is based on Android flavour of Linaro Stable
Kernel version 3.10, and with EFI enabled and all necessary android
configs.
The sources are built using Linaro GCC version 4.9-2015.04 for 64bit
and for 32bit.
To disable SELinux pass “selinux=0” as the boot parameter in the UEFI
bootargs configuration.

The Android AOSP software provided in this release is functionally
tested with CTS version 5.1r1 and the CTS results are shared with
members.

Additionally, the BIONIC component is validated with Android BIONIC
tests. Multi-arch support has been validated using examples provided in Android NDK.

Sources are also made available so you can build your own images
(see the Building from Source tab).

What is new

  • Android source changed to based on the Lollipop Android-5.1.1_r3 version

About the Android flavour of Linaro Stable Kernel (LSK)

The kernel used by Linaro Confectionary Release is based on the Android
flavour of Linaro Stable Kernel (LSK), which is produced, validated and
released by Linaro and is based on the Linux stable kernel tree.

The LSK focuses on quality and stability and is therefore a great
foundation for product development. It also includes backports of
commonly desired features, provided they meet the quality requirements,
and also any bug fixes.

Sources are also made available so you can build your own images (see
Building from Source).

Support

Subscribe to the important Linaro mailing lists and join our IRC
channels to stay on top of Linaro development.

  • Linaro Android Development ‘Mailing list’
  • Linaro Android IRC channel on irc.freenode.net at #linaro-android
  • Bug reports should be filed in ‘Bugzilla’ under “Linaro Android” product and “Reference Linaro Confectionery Release (R-LCR)” component.
    • You will need to login to your Linaro account. If you do not have an account or are having problems, email its@linaro.org for help.
  • More general bug reports should be filed in Bugzilla against the individual packages that are affected.
  • Questions? ‘ask linaro’
  • Interested in commercial support? inquire at ‘Linaro Support’

Android Patch Summary

There are patches developed by ARM and Linaro engineering teams
were applied to get Android booting to UI on the ARMv8-A fastmodels platform.
These patches can be found on Linaro’s Android
Git repositories via file LOLLIPOP-MLCR-PATCHSET.
Some of these patches have been submitted to AOSP and are being tracked
for acceptance.

Any patches can be contributed through the instructions described Here

Known Issues and Limitations

Known limitations

  • SW rendering for user interface only – there is no hardware accelerated graphics
  • Slow on high resolutions – we run on small screen size to avoid excessive delays
  • Lack of audio support may cause apps using audio to hang
  • HDLCD is not supported yet
  • Has long time problem to run some CTS test package because of the performance thing

Known issues

The following known issues are present in this release. Please contact support@linaro.org if you wish to know more information about these issues or have access problems when attempting to view them.

Bug ID Bug title Bug summary
Bug 1015 Monkey long run failure Blacklist does not seem to deployed or needs update – monkey testing has failed as result.
Bug 993 EVDEV failures in linaro android kernel test suite on 14.12 LCR build Few EVDEV tests have always been failing for us
Bug 224 Corrupted png files can cause crashes in gallery The stock Gallery application crashes when displaying known corrupt PNG files.
Bug 222 Dev Tools crashes on startup Dev Tools app fails to instantiate com.android.development.Development class from /system/app/Development.apk
Bug 64 Test test_pthread_rwlock from bionic libc test suite fails on Juno build – LAVA
Bug 23 backtrace_test reports failures on 64/64 build Failures reported with local trace and threads

Prerequisites

Run the build

You’ll need the latest ARM FVP Base models and a license to use the models. Follow the instructions at https://collaborate.linaro.org/display/ITS/FlexLM+and+Fast+Models for the same.

Get artifacts

Click on each link to download:

  • boot.tar.bz2
  • system.tar.bz2
  • userdata.tar.bz2

Get linaro image tools

Run these commands to get all the dependencies for linaro-image-tools and the tip of linaro-image-tools

  $ sudo add-apt-repository ppa:linaro-maintainers/tools
  $ sudo apt-get update
  $ sudo apt-get install linaro-image-tools

If you’re using a “tip” build then we suggest you use the tip of linaro-image-tools from http://git.linaro.org/ci/linaro-image-tools.git

Create binary for the ARM FVP Base AEMv8 models

Run linaro image tools

$ linaro-android-media-create --image_file mmc.bin --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2

If you’re using tip of linaro image tools

$ ./linaro-image-tools/linaro-android-media-create --image_file mmc.bin --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2

Extract the preboot files

tar -jxvf boot.tar.bz2

Setup the runtime environment

  $ export ARMLMD_LICENSE_FILE="8224@localhost"
  $ ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N $USER@flexlm.linaro.org &

Running the models (verified on FVP Base model build 6302)

  $ cd boot/
  $ /path/to/FVP_Base_AEMv8A-AEMv8A/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=1 \
        -C cluster1.NUM_CORES=1 \
        -C cache_state_modelled=0 \
        -C bp.pl011_uart0.untimed_fifos=1 \
        -C bp.secureflashloader.fname=bl1.bin \
        -C bp.flashloader0.fname=fvp_fip.bin \
        -C bp.virtioblockdevice.image_path=mmc.bin \
        -C bp.hostbridge.userNetworking=true \
        -C bp.hostbridge.userNetPorts="5555=5555" \
        -C bp.smsc_91c111.enabled=1

Console redirection

To redirect the console open a terminal and run

telnet 127.0.0.1 5000

Select UEFI configuration item, boot the build

Stop the UEFI prompt and select the Shell item, then it will boot up directly for you:



01:45:07 liuyq: m-lcr-fvp$ telnet localhost 5000

Trying ::1…

Trying 127.0.0.1…

Connected to localhost.

Escape character is ‘^]’.

Booting trusted firmware boot loader stage 1

Built : 12:14:12, May 23 2014

Booting trusted firmware boot loader stage 2

BL2 Built : 12:14:15, May 23 2014

Booting trusted firmware boot loader stage 3

BL31 Built : 12:14:19, May 23 2014

UEFI firmware (version  built at 12:13:11 on May 23 2014)


	
[=3h [=3h [=3h [=3h [=3h [=3h

The default boot selection will start in   1 seconds

ERROR: Did not find Linux kernel.

[1] Linaro disk image on virtio

[2] Shell

[3] Boot Manager

Start: 2

UEFI Interactive Shell v2.0

EDK II

UEFI v2.40 (ARM Fixed Virtual Platform EFI May 23 2014 12:13:52, 0×00000000)

Mapping table
      FS2: Alias(s):F8:
          VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)
      FS0: Alias(s):F3:
          MemoryMapped(0xB,0×88000000,0×8827FFFF)
      FS1: Alias(s):F4:
          MemoryMapped(0xB,0xFEC16000,0xFEDF987F)
      FS3: Alias(s):HD12b:;BLK5:
          VenHw(FE61BB5F-1B67-4C24-B346-73DB42E873E5)/HD(1,MBR,0×00000000,0×3F,0×41FC0)
      FS4: Alias(s):HD12e2:;BLK10:
          VenHw(FE61BB5F-1B67-4C24-B346-73DB42E873E5)/HD(4,MBR,0×00000000,0×242000,0×1BE000)/HD(2,MBR,0×00000000,0×362020,0×9DFE0)
     BLK3: Alias(s):
          VenHw(E7223039-5836-41E1-B542-D7EC736C5E59)
     BLK0: Alias(s):
          VenHw(02118005-9DA7-443A-92D5-781F022AEDBB)
     BLK1: Alias(s):
          VenHw(1F15DA3C-37FF-4070-B471-BB4AF12A724A)
     BLK2: Alias(s):
          VenHw(CC2CBF29-1498-4CDD-8171-F8B6B41D0909)
     BLK4: Alias(s):

Press ESC in 1 seconds to skip startup.nsh or any other key to continue.

Shell> kernel dtb=fvp-base-gicv2-psci.dtb initrd=ramdisk.img console=ttyAMA0 amba-clcd.mode=VGA

EFI stub: Booting Linux Kernel…4-B346-73DB42E873E5)/HD(2,MBR,0×00000000,0×42000,0×180000)

[    0.000000] Initializing cgroup subsys cpu

[    0.000000] Initializing cgroup subsys cpuacct3E5)/HD(3,MBR,0×00000000,0×1C2000,0×80000)

[    0.000000] Linux version 3.10.74 (buildslave@x86-64-07-android) (gcc version 4.9.3 20150413 (prerelease) (Linaro GCC Snapshot 4.9-2015.04) ) #1 SMP PREEMPT Mon May 25 11:45:33 CEST 20150000000,0×242000,0×1BE000)

Black screen

The boot screen has been disabled to speed up booting. This means you may not see anything on the CLCD terminal for a while depending on the performance of the machine the model is running on. For example a first boot on a 2 GHz machine with 32 GB of RAM took 20 minutes. Subsequent boots should take approximately half the time to boot.

Run the Android SDK

Attach ADB

If you run the models with the configurations mentioned above at the “Running the models” section, by default you can connect to the adb connection like this:

    adb connect 127.0.0.1

ADB on FVP Base models are supported over network as well. Follow the instructions here https://wiki.linaro.org/Internal/Projects/Juice/SetupNetworkingOnModelsUsingBridges to setup networking and use adb.

You can also run all of the standard Android SDK tools. Learn more at http://developer.android.com/sdk/index.html

Please Note: The adb connection will be only available after the Home screen is displayed.

Accessing Source Code

Linaro Android Source Code

Run the linaro_android_build_cmds.sh script, it will download the entire source code for both Android and the kernel and attempt to build it.

The pinned and source manifests can be found here:

Compiling Linaro Android RootFS+Kernel

The following simple steps download, install and compile a complete Linaro Android distribution

  • Download and install Ubuntu 14.04 64 bit or newer (download)
  • Download the Android building script for this build from the list of artifacts listed above or here
  • Run the script

Build from the tip of the source:

chmod a+x linaro_android_build_cmds.sh
./linaro_android_build_cmds.sh -t

Or reproduce the exactly the same as this buid:

chmod a+x linaro_android_build_cmds.sh
./linaro_android_build_cmds.sh -m pinned-manifest.xml

Booting the android with fastmodels

create the image file

$ linaro-android-media-create --image_file mmc.bin --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2

Extract the preboot files

tar -jxvf boot.tar.bz2

Setup the runtime environment

  $ export ARMLMD_LICENSE_FILE="8224@localhost"
  $ ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N $USER@flexlm.linaro.org &

Running the models (verified on FVP Base model build 6302)

  $ cd boot/
  $ /path/to/FVP_Base_AEMv8A-AEMv8A/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=1 \
        -C cluster1.NUM_CORES=1 \
        -C cache_state_modelled=0 \
        -C bp.pl011_uart0.untimed_fifos=1 \
        -C bp.secureflashloader.fname=bl1.bin \
        -C bp.flashloader0.fname=fvp_fip.bin \
        -C bp.virtioblockdevice.image_path=mmc.bin \
        -C bp.hostbridge.userNetworking=true \
        -C bp.hostbridge.userNetPorts="5555=5555" \
        -C bp.smsc_91c111.enabled=1

Console redirection

To redirect the console open a terminal and run

telnet 127.0.0.1 5000

Select UEFI configuration item, boot the build

Stop the UEFI prompt and select the Shell item, then it will boot up directly for you:



01:45:07 liuyq: m-lcr-fvp$ telnet localhost 5000

Trying ::1…

Trying 127.0.0.1…

Connected to localhost.

Escape character is ‘^]’.

Booting trusted firmware boot loader stage 1

Built : 12:14:12, May 23 2014

Booting trusted firmware boot loader stage 2

BL2 Built : 12:14:15, May 23 2014

Booting trusted firmware boot loader stage 3

BL31 Built : 12:14:19, May 23 2014

UEFI firmware (version  built at 12:13:11 on May 23 2014)


	
[=3h [=3h [=3h [=3h [=3h [=3h

The default boot selection will start in   1 seconds

ERROR: Did not find Linux kernel.

[1] Linaro disk image on virtio

[2] Shell

[3] Boot Manager

Start: 2

UEFI Interactive Shell v2.0

EDK II

UEFI v2.40 (ARM Fixed Virtual Platform EFI May 23 2014 12:13:52, 0×00000000)

Mapping table
      FS2: Alias(s):F8:
          VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)
      FS0: Alias(s):F3:
          MemoryMapped(0xB,0×88000000,0×8827FFFF)
      FS1: Alias(s):F4:
          MemoryMapped(0xB,0xFEC16000,0xFEDF987F)
      FS3: Alias(s):HD12b:;BLK5:
          VenHw(FE61BB5F-1B67-4C24-B346-73DB42E873E5)/HD(1,MBR,0×00000000,0×3F,0×41FC0)
      FS4: Alias(s):HD12e2:;BLK10:
          VenHw(FE61BB5F-1B67-4C24-B346-73DB42E873E5)/HD(4,MBR,0×00000000,0×242000,0×1BE000)/HD(2,MBR,0×00000000,0×362020,0×9DFE0)
     BLK3: Alias(s):
          VenHw(E7223039-5836-41E1-B542-D7EC736C5E59)
     BLK0: Alias(s):
          VenHw(02118005-9DA7-443A-92D5-781F022AEDBB)
     BLK1: Alias(s):
          VenHw(1F15DA3C-37FF-4070-B471-BB4AF12A724A)
     BLK2: Alias(s):
          VenHw(CC2CBF29-1498-4CDD-8171-F8B6B41D0909)
     BLK4: Alias(s):

Press ESC in 1 seconds to skip startup.nsh or any other key to continue.

Shell> kernel dtb=fvp-base-gicv2-psci.dtb initrd=ramdisk.img console=ttyAMA0 amba-clcd.mode=VGA

EFI stub: Booting Linux Kernel…4-B346-73DB42E873E5)/HD(2,MBR,0×00000000,0×42000,0×180000)

[    0.000000] Initializing cgroup subsys cpu

[    0.000000] Initializing cgroup subsys cpuacct3E5)/HD(3,MBR,0×00000000,0×1C2000,0×80000)

[    0.000000] Linux version 3.10.74 (buildslave@x86-64-07-android) (gcc version 4.9.3 20150413 (prerelease) (Linaro GCC Snapshot 4.9-2015.04) ) #1 SMP PREEMPT Mon May 25 11:45:33 CEST 20150000000,0×242000,0×1BE000)

Black screen

The boot screen has been disabled to speed up booting. This means you may not see anything on the CLCD terminal for a while depending on the performance of the machine the model is running on. For example a first boot on a 2 GHz machine with 32 GB of RAM took 20 minutes. Subsequent boots should take approximately half the time to boot.

Run the Android SDK

Attach ADB

If you run the models with the configurations mentioned above at the “Running the models” section, by default you can connect to the adb connection like this:

    adb connect 127.0.0.1

ADB on FVP Base models are supported over network as well. Follow the instructions here https://wiki.linaro.org/Internal/Projects/Juice/SetupNetworkingOnModelsUsingBridges to setup networking and use adb.

You can also run all of the standard Android SDK tools. Learn more at http://developer.android.com/sdk/index.html

Please Note: The adb connection will be only available after the Home screen is displayed.