Archive

Posts Tagged ‘qa’

Realtek RTL8710AF (PADI IoT Stamp) vs Espressif ESP8266 (ESP-07) WiFi RF Performance Comparison

October 27th, 2016 4 comments

After I posted about PADI IoT Stamp IoT kit based on RTL8710AF ARM Cortex M3 WiSoC yesterday, I was soon asked whether I could compare the RF performance against ESP8266 modules like ESP-12. I don’t have any equipment to do this kind of test, except for some simple test like testing range with WiFi Analyzer app, but I remember Pine64 told me they had some comparison data a little while, and accepted to share their results.

wifi-rf-performance-testingThe test setup is comprised of Litepint IQ2010 multi-communication connectivity test system and PC software, as well as the device under test (DUT) with PADI IoT Stamp (version with u.FL antenna connector) and ESP-07 ESP8266 module as a u.FL connector is required to connect the test system.

They’ve tested 802.11b, 802.11g, and 802.11n, but for IoT projects 802.11b is the most important as usually long range is more important than data rate. Test results below are based on CH1 input data with 1dBm compensation.

That’s the results for ESP8266…

esp8266-802-11b-test-data

ESP8266 802.11b Data, Spectral Mask and Constellation Diagram

.. and the results for RTL8710 using an 802.11b connection.

rtl8710af-802-11b-test-data

RTL8710AF 802.11b Spectral Mask and Constellation Diagram

The tables show peak and average power, LO leakage, EVM (Error vector magnitude), Frequency error and other parameters. The spectral mask, and constellation diagram are also shown for each case. If you’ve never studied or worked about RF signal, it’s quite all complicated, but can get some insights by reading Practical Manufacturing Testing of 802.11 OFDM Wireless Devices white paper.

A Spectral Mask describes the distribution of signal power across each channel. When transmitting in a 20 MHz channel, the transmitted spectrum must have a 0 dBr bandwidth not exceeding 18 MHz, –20 dBr at 11 MHz frequency offset, –28 dBr at 20 MHz frequency offset, and the maximum of –45 dBr and –53 dBm/MHz at 30 MHz frequency offset and above.

The Constellation Diagram is a representation of a signal modulated by a digital modulation scheme. It is useful to identify some types of corruption in signal quality. The EVM is a measure of the deviation of the actual constellation points from the ideal error-free locations in the constellation diagram (in % RMS or dB), and you’d want to keep this as small as possible.

In both diagrams, it appears that the signal is quite cleaner on PADI IoT stamp compared to ESP8266 module with more distortions. The diagram are not quite clear enough to check the Spectral Mask values. I’m sure we’ll get some more feedback in the comments section.

If you are interested in 802.11g and 802.11n results, you can access the rest of the report.

Test Widevine & PlayReady DRM, HDCP 1.x/2.x, 4K VP9 and H.265 in Android with Exoplayer App

October 21st, 2016 2 comments

I first heard about ExoPlayer in an Android TV Overview presentation at Linaro Connect 2014, but I never really looked into it. The source code is available on Github, and I’ve been given ExoPlayer.apk as it can be used to test UHD H265 support, HDCP 1.x, HDCP 2.x compatibility, PlayReady & Widevine DRM using different format and so on.

ExoPlayer Demo - Click to Enlarge

ExoPlayer Demo – Click to Enlarge

So I installed it on Beelink GT1 Android TV box which I’m currently reviewing, and only include basic Widewine Level 3 DRM, and certainly does not support HDCP features.

There are 9 sections in the app to test various videos and DRM schemes:

  • YouTube Dash
  • Widevine Dash Policy Tests (GTS) – Widewine with or without HDCP, with or without secure video path
  • Widevine HDCP Capabilities Tests – NoHDCP, HDCP 1.0, HDCP 1.1, HDCP 2.0, HDCP 2.1, HDCP 2.2, and HDCP no digital output
  • Widevine Dash MP4, H264 – Various resolution (SD, HD, UHD) for clear or secure videos
  • Widevine Dash WebM, VP9
  • Widevine Dash MP4, H.265
  • SmoothStreaming – Super speed or Super speed (PlayReady)
  • HLS – Apple master playlist, Apple TS media playlist, Apple ID3 metadata, etc…
  • Misc – Various video & audio formats and codecs (MKV, FLV, Google Play videos…)

I tested a few the tests without HDCP nor secure data requirement will work just fine. Widevine secure SD (MP4, H.265) would work fine, but as expect Widevine Secure HD and UHD would not work, and only show a black screen with audio since Level 1 DRM is not supported by my device.

Then I switched to Widewine HDCP 2.2, and to my surprise the video could play… I later found out that HDCP does not kick-in immediately, and if I play the video for a longer time, the video will stop after 9 seconds because Beelink did not get the HDCP 2.2 license for their box.

AFAIC, there’s automatic testing, and each test must be started manually. But it’s still a useful if you are interested in copy protection schemes supported by your Android device.

I’ll complete the post with something unrelated with ExiPlayer, but still interesting to check HDCP support if you own an Amlogic device, as there are some commands to check the status of HDCP:

  • Show whether the TV is currently working with HDCP 2.x or HDCP 1.x:

22 = HDCP2, 11 = HDCP1, off = HDCP not enabled right now

  • Check HDCP authentication status:

1=authenticated ok, 0 = failed to authenticate.

  • HDCP keys for device

00 = no HDCP key, 14 = has HDCP1_key, 22 = has HDCP2_key

  • Check TV HDCP version

22 = TV supports HDCP2, 14 = TV supports HDCP1)

  • Disable HDCP protection:

GradientOne Brings Oscilloscopes, Spectrum Analyzers, Frequency Generators… to the Cloud

July 29th, 2016 No comments

Nowadays, product development often involves working with teams spread across the world, with for example hardware development in the US, software development in India, and manufacturing in China. Resolving issues may require several members of the teams to gather data and work together, and beside the distance issue, you have to handle different timezones too. GradientOne may help facilitating hardware and firmware debugging by connecting test equipments such as oscilloscopes, spectrum analyzers, frequency generators and others to the cloud, so that data can easily be shared, and any member of the team control the equipment remotely, even automatizing measurements if needed. It could also be useful to field application engineers who may bring portable equipment to the customer premises, and have one engineer investigate issues remotely.

GradientOneThere are two ways to integrate equipment with GradientOne:

  • Web user interface to control instruments, set parameters (e.g. trigger, acquisition type, etc), via the web interface.

The company already did the hard work, and current supports Tektronix MDO3000 series oscilloscopes + function generator, Tektronix MDO4000/MSO200/DPO 2000 & DPO 4000 series oscilloscopes, as well as Agilent/Keysight U2000 power meters, and more support is planned for Agilent 859xA/B series spectrum analyzers, Agilent 8340/1 A/B RF signal generators, Chroma 62000P series power supplies, Agilent 34401A digital multimeters.

GradientOne_Web_Interface

Customer will benefits from data storage, organization, search, reporting, collaboration, signal replay, etc… through the interface.

  • API to work with any existing test script to support sending test data and instrument configuration to GradientOne cloud as well as retrieve the data/configuration.

The HTTP(S) & JSON API is useful to add instruments not yet supported by the Web UI, and for customers who want to keep using their existing instrument scripts but securely (OAuth 2.0 authenticate) store and retrieve data from GradientOne cloud.

The promo video below quickly shows some of the features of GradientOne service.

The company also offer on-site or online (Google Hangouts) live demos to interested companies. More details can be found on GradientOne website.

Antutu Video Tester Automatically Tests Video and Audio Codecs & Playback Quality in Android

December 1st, 2014 11 comments

When I read a review about MK808B Plus this morning, I noticed the reviewer used Antutu Video Tester to evaluate video/audio performance of the device. Somehow I had never noticed it, and Antutu developers claim it can not only check whether video or audio codec are supported, but the tool can also give an appraisal of video quality:

AnTuTu Video Test is a professional tool for testing video playback capability of Android Smart TV, set-top boxes and other devices. It integrates a few featured videos and testing algorithms that can help users judge the playback performance of the devices clearly. AnTuTu video test can not only detect the video playback formats devices support, but also can test the playback quality of devices.

Antutu_Video_TesterSo I decided to try it out on Open Hour Chameleon Android media player based on Rockchip RK3288 processor. The first test you click on Video Test will it download the video samples (155 MB), all very short files based on Sintel video from the Blender Foundation with different resolutions, video & audio codecs. Once the download is complete, the test will automatically, and it last just maybe 2 or 3 minutes, so it’s much faster than manual testing.

Let’s check out the results and list of files.

Antutu_Video_Tester_Open_Hour_Chameleon

Video Tester Results (Click to Enlarge)

So they test a bunch of videos with 1080p and 2160p resolution with the most common codec, but it’s far from extensive. Based on this table, the only problem with the box is that it can not play DTS or AC-3 files with the video player (stock?) used in the tester. So overall it does not look that bad. But since I noticed some 1080p pixelated videos, and/or skipped frames, Chameleon got just 263 points, which is rather low compared to some other television sets or TV boxes, and should mean Antutu Video Tester does indeed take into account video playback “quality” as advertised.

Antutu_Video_Tester_Top_Scores_for_TVHimedia Q5 with HiSilicon SoC (three models are available), Letv C1S with a dual core processor @ 1.5 GHz / Mali-400MP2 GPU, and Kaiboer F5 featuring Mstar MSO9180 SoC are the top three TV boxes based on this test, but unfortunately these are mostly reserved to the Chinese market.

Have you tried on your Android media player? What’s your score?

AllWinner A80 Octa Core big.LITTLE Processor CPU Usage Under Various Loads in Android 4.4 (Video)

November 23rd, 2014 4 comments

Allwinner A80 is one of the few octa core processors featuring ARM’s big.LITTLE technology currently available on the market. The processor comes with four ARM Cortex A15 (big) cores, and four ARM Cortex A7 (LITTLE) core, and tasks will be scheduled to different processor depending on the load to optimize power consumption on mobile devices. However, earlier big.LITTLE processors like Samsung Exynos 5410 has some serious limitations, as they only supported “cluster migration” meaning you could only use the Cortex A7 cluster or Cortex A15 cluster at any given time, so Exynos 5410 could only make use of four cores at most due to hardware limitations. They also used to be two software implementations: In-kernel Switching (IKS) and Global Task Scheduling (GTS). The former could only handle one type of core at the same, and the latter, which I believe is now used in all new devices, can handle any combination of cores, so an octa core big.LITTLE SoC can indeed make use of all its eight cores.

Antutu_3D_CPU_Usage
To make sure it was the case with Allwinner A80 SoC, I did a little test using PVRMonitor app on Tronsmart Draco AW80 mini PC. I did this test to check all eight cores can be used, and to see which cores and how many cores are used for various loads such as multi-tab web browsing and gaming. The scheduler was set to Performance with No-frills CPU Control app.

I’ve run Antutu, the Android stock Browser with multiple tabs open, and Beach Buggy Blitz 3D racing games in the video above. The takeaway for this short test is that Allwinner A80 can run its eight cores simultaneously, but in typical use, it’s rare to see more than four cores used simultaneously. I forgot to include video playback in the video, so I tried to play 4K videos and H.265 videos with Kodi 14, and normally (hardware video decoding) only two Cortex A15 are used (around 30% per core),  and when software video decoding is needed (H.265), at most four cores are used, so it looks like Kodi has not been optimized yet to make full use of octa systems, at least on Allwinner A80.

So in Android mini PCs, there’s usually very little gain from an octa core processor instead of a quad core processor, unless you run apps that can make use of all cores such as video transcoding apps, or you want it convert it into a Linux mini PC to compile software or run a server.

LinuxCon North America 2013 Schedule

August 6th, 2013 1 comment

LinuxCon (North America) 2013 will take place on September 16 – 18, 2013 in New Orleans, LA. The event will be co-located with several other conferences: the Linux Plumbers Conference, the Xen Project User Summit, the OpenDaylight Mini-Summit, the Gluster Workshop 2013, the UEFI Plugfest, the Linux Wireless Summit, the Linux Security Summit, and CloudOpen 2013.

LinuxCon consists of 3 days of keynotes, and legal, operations, and developers related sessions as well as tutorials and workshops. There will be around 150 sessions and keynotes during those 3 days. I’ve gone through developer sessions and selected one for each time period.

Linuxcon_2013

Monday, September 16

UEFI has become ubiquitous on the PC client systems and is coming up on servers and ARM-based systems, it is becoming the converged firmware infrastructure. UEFI Secure Boot feature has attracted a lot of attention from the Linux community. Linux distros and Linux Foundation have found solutions.  This presentation provides a review of the motivations behind the creation of the UEFI technology, the history, the current status, and the future. It provides an update on the new significant developments since the publication of UEFI Spec v2.3.1C last June. It also serves as a venue for Q&A with the Linux community.

The LLVM project is an extensive compiler technology suite which is becoming commonplace in many industries. Technology built with LLVM is already shipped in millions of Linux devices as a part of Android/Renderscript. Increasingly it is becoming a big part of the development process for embedded projects, all the way up through to high performance computing clusters. This session will provide an update on the status of the LLVMLinux project; a project which is cooperating with both the Linux kernel and LLVM communities to build the Linux kernel with Clang/LLVM.

Memory compression has long been a topic confined to academic research and development sandboxes. However, with CPU and memory speed improvements outpacing improvements in I/O speed and latency, memory compression is now being deemed a viable way to increase in-memory data density and delaying or avoiding costly I/O.  Zswap, a feature for compressed swap caching, merged into the kernel in v3.11, is a first step toward deploying this functionality in the Linux kernel.

This presentation targets users who own hardware with maxed-out RAM capacities or pay per-GB for RAM usage (IaaS customers) and would like to determine if memory compression can reduce their costs and extend the useful lifetime of their computing assets.

This presentation will cover a brief introduction on how the Bluetooth Low Energy technology works. Then it will present the current status of its support on Linux, presenting the available APIs and how to interact with Bluetooth Smart devices, including the profiles we’re currently working on, and what can be expected to be finished in the near future. There will be also a few demos of Bluetooth Smart devices working with Linux.

With the Linux kernel now supporting NFC, a natural step forward seems to be enabling mobile payments, either cloud or NFC based. To do so we need to give payment applications access to secure elements, via the kernel. At the moment, both the secure element kernel interface and a generic secure element library are missing from any standard Linux distribution, effectively keeping Linux away from the mobile payments market. We will first go through a brief tour of the mobile payments ecosystem and see how it is actually implemented. Then we will describe the proposed kernel APIs for discovering, enabling and talking to secure elements. Finally we will discuss about the possible options for bringing a hardware agnostic secure element library to standard Linux distributions, and how it could be used to implement payment applications on Linux.

Tuesday, September 17

Linaro’s open source automated validation architecture (LAVA) enables developers to test their software on a broad range of hardware platforms. This presentation will describe to developers how they can utilize LAVA to test and validate kernels on real or emulated hardware. This session will showcase a new lightweight interface for testing kernels efficiently, and displaying test results. The goal being that we as developers can leverage automation to ensure that the Linux kernel is well tested and that each iteration becomes more robust than the last

Mobile processors are at the heart of hundreds of devices built on the Linux kernel, but are also being implemented in other Linux-compatible embedded systems. For the Linux community, it’s inevitable that challenges will arise when developing and pinpointing the origin of issues can be a setback. Leon will talk about tools that enable developers to test and refine systems and applications for these powerful mobile processors so the software runs pristinely when launched.

The target audience for this session is software developers, mobile and beyond. Developers can expect to learn how to test and fine tune applications across embedded systems to be not only be functional and problem free, but also visually enticing, battery efficient and packed with cutting-edge features.

With raising popularity of Linux on mobile devices the shortcomings of the default kernel memory management policies become more and more visible. The combination of limited physical memory and lack of swap device brings a challenge in the most efficient use of the available resources. This presentation will give an overview of the current state of improvements (i.e. memory control groups, per-process/group reclaim, memory compression) to the Linux memory management subsystem that together with the cooperating user-space components allow more custom control of the memory available in the system. The usage examples of specific features will be based on Tizen operating system.

This talk is intented mainly at kernel and distribution developers wishing to improve Linux memory management but it may be interesting to whoever would like to know more about the topic.

The Tux3 filesystem project began in 2008 and has now reached a point where it is beginning to show favorable benchmark results compared to other Linux filesystems. Tux3 breaks new ground in Linux filesystem technology with its strong consistency semantics, novel high performance atomic commit and asynchronous frontend/backend design that maps well to the new generation of multi-core CPUs. Tux3 is expected to reach a mergable state in the next few months. Much work remains to be done, including incorporating versioning and replication support, improved filesystem checking and repair facilities, enterprise features such as quotas and end to end checksumming, and availability features such as online checking and repair. In this talk, Daniel Phillips, designer of Tux3, will discuss current implementation status, present benchmark results and lay out plans for kernel merge and beyond.

Software Freedom Conservancy announced last year a renewed effort for cross-project collaborative GPL compliance efforts, including copyright holders from BusyBox, Linux, and Samba. Conservancy uses an internal system of communication and collaboration to take input from stakeholders to discuss and engage in compliance activity to ensure compliance with the GPL throughout the technology industry and particularly in the embedded device market.  Compliance with the GPL is the responsibility of copyright holders of the software, and Conservancy helps those copyright holders pursue the work, so those developers can focus on coding. In this talk, the Executive Director of Conservancy will discuss how Conservancy handles compliance matters, what matters it focuses on, and how the copyright holders that work with Conservancy engage in a collaborative effort to ensure compliance with the GPL.

Wednesday, September 18

The Linux Kernel is currently supported on over 30+ different hardware architectures. This is a huge benefit for Linux adoption on a wide range of deployments. However, the ability to build and test Linux kernels on all possible supported architectures requires having access to such test systems for each of these architectures which is not easy by any means. Therefore, the ability to cross-compile non-native architectures on an architecture that is widely supported such as the x86_64 helps address the building kernels part of the problem.

This talk will present the details of where to find cross-compilers packages for architectures, how to install them, and how to automate compile on each of these architectures on an x86 system. This talk will be of great benefit to any software developer trying to build and test Linux kernel on non-native hardware architecture.

As ARM and ARM64 move out of gadgets and into more PC like hardware, there has been an increasing demand for the same tools to manage these devices as already exists in x86 world. Linaro has been working on UEFI and ACPI on arm/arm64 hardware and this talk is a summary of the current status of the work and the direction that will be taken in the future. We will show the areas of change to the ARM platform boot sequence, change to the ACPI core code, and change to drivers to support ACPI.

The Linux kernel contains multiple energy-saving features. Some of them act on the system as a whole while the others are concerned with individual processors or I/O devices. The majority of them have been developed in isolation and they work reasonably well individually, but that is often insufficient to address problems related to the progressing integration of hardware and growing user expectations. For this reason, it will be necessary to make them work more closely together and he’s going to talk about that in his presentation.  Rafael will describe the current status of the kernel’s energy-saving features, the most important problems they are facing and some possible ways to address those problems

This session is a BoF session organized by LTSI (Long Term Support Initiative) to discuss testing for Linux kernel. Testing is very important when delivering software, validating changes, shipping products and so on but actually each individual is doing its own testing and that are not shared with others. This BoF would like to discuss how to share testing, what is the common testing portion and so on.

Those are just a few choices, and you can check the full schedule to find out which sessions suit you best.

You can register to LinuxCon 2013 and CloudOpen 2013 online for the following fees:

  • US$475 through May 3rd (Early Bird)
  • US$575 May 4th through July 31st (Standard)
  • US$675 thereafter (Late)
  • Student Registration – $150

Fees are up between 11% to 50% compared to last year. Who said there’s no inflation?

Linaro 13.07 Release With Linux Kernel 3.10.1 and Android 4.2.2

July 31st, 2013 2 comments

Linaro 13.07 has been released with Linux Kernel 3.10.1 (both baseline and stable versions), and Android 4.2.2.

It’s summer time, so activity seems to have slowdown a bit, yet improvements have done to LAVA with the first LAVA Multi-purpose Prove (LMP) setup, and Linaro has released build with Linux 3.10.1, Ubuntu Raring, OpenEmbedded (ARMv8), and Android. For the very first time, there’s even an Android 4.2.2 community build for HiSilicon K3V2 hardware (HiSilicon Hi4511 development platform).

Here are the highlights of this release:

  • LAVA

    • LAVA Core
      • VExpress A9 test images no longer use the master image’s boot loader
      • Support added for interactive bootloader commands.
      • Support for OpenID / Crowd added for LAVA.
      • LAVA Master images updated on images.validation.linaro.org
      • LAVA Multi-node – Multi-Node support has an initial implementation which can support communication between nodes under test via the use of a GroupDispatcher.
    • LAVA Lab Capabilities – LMP (LAVA Multi-purpose Probe) prototypes built and integration efforts into LAVA have begun. Focus will be integrating and stress testing the SDMUX LMP and then adding support for the other boards.
  •  Builds and Baselines

    • Linaro Stable Kernel (preview) 3.10.1 2013.07 released
      • Based on 3.10.1 stable tree
      • big.LITTLE support: ARM MP patch set, IKS
      • VExpress TC2 support
      • Power efficient workqueue support
      • Android v3.10 experimental patch set from AOSP
    • Linux Linaro 3.10.1 2013.07 released
      • updated Versatile Express patches from ARM LT
      • arndale/exynos patches from Samsung LT (rebased version of the 13.06 topic)
      • a patch to enable perf in Android by Bernhard Rosenkraenzer (same as in 13.05)
      • vexpress64 support (both RTSM and Foundation model)
      • omap-fixes-13.06 topic: to make USB host and the on-board ethernet operational on Panda (same as in 13.06 release)
      • config fragments changes arndale.conf and distribution.conf. Added xen.conf
    • Linaro OpenEmbedded baseline updates:
      • Added PAM to DISTRO_FEATURES
      • Set libjpeg-turbo as the preferred provider for jpeg
      • Updated to Linaro GCC 4.8-2013.07 release
      • Switched builds to use Linaro versions of binutils and eglibc (2.17)
    • Linaro Android baseline updates:
      • Arndale build updated with display support on HDMI using software graphics stack
      • pm-qa, mmtest, cachecoherency, gatortest and imetest migrated to lava-test-shell
      • Android builds updated to build with Linaro GCC 4.8 2013.07 release
    • Linaro Toolchain Binaries 2013.07 released. It includes latest Linaro GCC 4.8 2013.07-1 and Linaro Eglibc 2.17-2013.07-2 releases.
  • Kernel

    • Convert Moxart to GENERIC_CLOCKEVENTS
    • Storage EXT4 journal in enhanced area of eMMC – Club journal and metadata together in enhanced area
  • Power Management

    • Linaro Powerdebug 2013.07 released with support for multiple key code for ENTER key, and Clocks modifications (Allow child clock to be seen)
  • QA

    • Successfully completed 13.07 release testing on Android (linux-linaro and LSK), Ubuntu and OpenEmbedded builds. Test results and bug reports have been shared.
    • Manual UEFI testing was performed on Versatile Express A9 board.
    • Initial setup for KVM testing is in place
  • Toolchain

    • Linaro GCC 4.8 2013.07 released with address sanitizer support for ARM, new -mrestrict-it option, backport of support for further AArch64 and ARMv8 AArch32 instructions.
    • Linaro GCC 4.7 2013.07 released.
    • Linaro eglibc 2.17 2013.07 released – Optimized string functions for AArch64: memcmp, memset, memcpy, memmove, bzero, strcmp, strlen, strnlen, strncmp.
  • Graphics

    • CMA-ION patches reviewed and merged in Android Kernel.
    • CMA-ION activity Closed.

Visit https://wiki.linaro.org/Cycles/1307/Release for a list of known issues and further release details about the LEB and community builds, Android, Kernel, Graphics, Multimedia, Landing Team, Platform, Power management and Toolchain (GCC / Qemu) components.

Linaro 13.05 Release With Linux Kernel 3.10, Android 4.2.2, and Ubuntu Raring Ringtail

May 31st, 2013 No comments

Linaro 13.05 has just been released with Linux Kernel 3.10-rc2 and Android 4.2.2. This is the first release with Ubuntu 13.04 (Raring Ringtail) images. There’s also Linux Linaro Stable (LSK) preview based on kernel 3.9.4.

BeagleBone Black support has been added and preliminary hwpack and images are available, an Android Arndale image with virtual framebuffer is also available. You can now get a desktop environment (XFCE) on Aarch64 / ARMv8. Hardware packs with Real-time Linux kernel (PREEMPT_RT) can be downloaded for Pandaboard and Arndale. More work has gone into Aarch64, big.LITTLE HMP, and ARM virtualization (KVM). Finally an UEFI is available not only for Vexpress boards, but also Samsung Origen and Arndale boards, as well as Texas Instruments Pandabord and Beagleboard.

Here are the highlights of this release:

  • LAVA

    • First prototype production run of LAVA Lmp completed, tested functional.
    • Beaglebone Black is now running in LAVA.
    • TC2s is now running fully with latest firmware and master image, booting on A7 core.
    • Different client tools were consolidated into a single package to simplifies the process of updating the tools and makes it easier for the team to provide new features for LAVA users.
    • Android build howtos are published along the build artifacts themselves (Patch).
    • linaro-patchmetrics is now able to work in local environment.
    • RT patchset testing enabled in LAVA.
  •  Builds and Baselines

    • The detailed CTS report in the standard format is now generated in LAVA. The QA Services Team will include these reports in the weekly/monthly testing reports for platforms in LAVA.
    • The Galaxy Nexus CI loop is done. The images (without graphics acceleration) can be deployed with a graphics overlay for testing in LAVA.
    • The full Android engineering build for Arndale is now available with virtual framebuffer.
    • Clean up of the independent test suite builder is done. All the dependent projects are now built from sources for the test suite.
    • Test migration from lava-test-shell to lava-android-test continues: tjbench, big.LITTLE IKS test are available in lava-test-shell.
    • The Toolchain WG has optimized string routines for A15. These routines are now integrated into bionic for Android.
    • Setup of the initial CI loop for Linaro Stable Kernel (LSK). A preview is released as part of Linaro 13.05 release. A tree has been created with the collaboration of the Kernel WG and the related CI/LAVA jobs are done.
    • Linux Linaro Kernel moved from 3.9 to be 3.10-rc2 based.
    • Calxeda EnergyCore (Highbank) server CI loop is now completed. Daily builds are produced and submitted to LAVA.
    • Support for BeagleBone Black board has been added. The initial CI loop is complete: hardware pack and pre-built images are available.
    • Progress on the CI loop for LNG. The realtime Linux kernel (PREEMPT_RT) is built on ci.linaro.org and hwpack targeting PandaBoard/Arndale boards are published.
    • Linaro Ubuntu baseline images are updated to the latest Ubuntu stable release, Raring Ringtail (13.04).
    • Support for Linaro external toolchain (pre-built binaries) is added to Linaro OpenEmbedded baseline.
    • Integration of OpenJDK zero build for Aarch64 cross-compile to Linaro OpenEmbedded baseline.
    • libunwind support for ARMv8, contributed by the Toolchain WG, is available in Linaro OpenEmbedded baseline.
    • Linux Linaro 3.10-rc2 2013.05 released
      • big-LITTLE-MP-master-v17 (new version vs 13.04 release)
      • updated config fragments for Arndale and Panda
      • updated Versatile Express patches from ARM LT: new MCPM and IKS patch sets
      • updated arndale/exynos patches from Samsung LT
      • a patch to enable perf in Android by Bernhard Rosenkraenzer
      • vexpress64 support (both RTSM and Foundation model)
      • omap-fixes-13.05 topic: serial and gpio fixes for omap2+ from v3.10-rc3
      • OpenStack support: CONFIG_[IP,IP6]_NF_IPTABLES, CONFIG_NF_CONNTRACK*, and CONFIG_NF_NAT* enabled in ubuntu builds (added to ubuntu-minimal.conf)
    • Linaro Toolchain Binaries 2013.05 released
  • Graphics
    • Mali driver ported and brought up for the Arndale board.
    • An XFCE based graphics image now works in the RTSM simulator: http://fullshovel.wordpress.com/2013/05/24/arm-aarch64-running-a-graphical-stack/
    • CDFv2 is up on an eDP panel on Arndale.
    • Patches v1 and v2 implementing a DT node for the DP controller, clock provider and display timings for Arndale.
    • Android patches for piglit are finished. They enable current and future testcases to be built as part of automated build and test process.
    • Fixed GStreamer bugs
  • Kernel

    • Exynos core and drivers now use common clk infrastructure. It’s been merged in 3.10-rc1.
    • The <mach/*> and <plat/*> namespaces for the Nomadik and Ux500 platforms were depopulated. It’s been merged in 3.10-rc1.
    • Refactored EHCI controller code to allow configuration of multiple EHCI controllers as both modules or static drivers in the same kernel.
    • Uncompress message is now supported on multi-platform kernels. It’s been merged in 3.10-rc1.
    • Samsung platform (Exynos) converted to use Generic Clock Events.
    • Android Sync infrastructure has been upstreamed to staging for 3.10-rc1.
    • Upstream Android ram_console driver functionality.
    • Implement and upstream ARM 32 bit uprobes support
    • Improve eMMC Power Management Support
    • Android ETM(Embedded Trace Macrocell)/ETB(Embedded Trace Buffer) upstreaming (arch/arm/kernel/etm.c)
    • Remove ARM specific dependencies in Android’s ION
    • Android upstreaming: Ashmem
    • Port some of the simpler platforms to multiplatform support: u300 and Nomadik
    • Android FIQ debugger for ARM
    • Migrate Android Alarmtimer driver over to using the upstreamed Alarmtimers
    • Android ION infrastructure upstreaming
  • Power Management

    • First big.LITTLE release with IKS code integrated into the public linux-linaro tree.
    • Removal of hardcoded assumptions of CPU topology in IKS code, test scripts. It allows test suite and code to be more easily adopted to member platforms.
    • Integration tree to bring together big.LITTLE MP related work
    • Small task packing by scheduler
    • CPU Hot Plug Latency on Android
    • sched: modify timer and workqueue framework to allow migration
  • QA

    • Successfully completed 13.05 release testing on Android, Ubuntu and OpenEmbedded builds. Test results and bug reports have been shared.
    • Review of existing test cases was completed. Descriptions and steps were updated.
    • Improvements in big.LITTLE IKS test suite
    • Checked that breakpoints are inherited correctly across switches.
  • Toolchain
    • Linaro GCC 4.8 2013.05 released, based off the latest GCC 4.8.0+svn198615 release.
      • Backport of support for prologue/epilogues using LDRD and STRD in ARM mode.
      • Backport of support for further AArch64 instructions.
      • Backport of support for further ARMv8 AArch32 instructions.
    • Linaro GCC 4.7 2013.05 released, based off the latest GCC 4.7.3+svn198701 release
    • Linaro GCC 4.6 2013.05 released, based off the latest GCC 4.6.4+svn197894 release. It’s the final one of 4.6 series.
    • libunwind support for ARMv8 is committed upstream.
    • Address Sanitizer support for ARMv7 in GCC is committed upstream.
    • Shrink-wrapping support in GCC is committed upstream.
    • Load-time function selection (IFUNC) in GLIBC is accepted upstream.
    • GLIBC will now choose the best memcpy depending on the presence of VFP and NEON hardware.
    • Patches for gprof support for ARMv8 are submitted upstream.
  • LEG

    • Cross-building OpenJDK javac binary on Aarch64 – currently testing and seems functional.
    • Linaro UEFI 2013.05 released with support for:
      • Versatile Express A5/A9/TC1/TC2 and RTSM A9×4 and A15×1, A15 MPCore.
      • Samsung Arndale &  Origen
      • TI Pandaboard & Beagleboard
  • Virtualization

    • ARMv8 uniprocessor guest running on KVM ARMv8 SMP hardware (APM X-Gene Mustang board).
    • ARMv7 uniprocessor guest booted on KVM ARMv8 SMP hardware.
    • First successful boot to a shell in ARMv8 guest on KVM ARMv8 host running on Foundation Model and being controlled by QEMU.

Visit https://wiki.linaro.org/Cycles/1305/Release for a list of known issues and further release details about the LEB and community builds, Android, Kernel, Graphics, Multimedia, Landing Team, Platform, Power management and Toolchain (GCC / Qemu) components.