Posts Tagged ‘automotive’

Renesas R-Car H3 Deca-Core Processor and Driverless Car Roadmap

December 7th, 2015 3 comments

Renesas has recently unveiled R-Car H3 deca-core processor for automotive applications with four Cortex A57 cores, four Cortex A5 cores, and two Cortex-R7 “dual-lock step” cores for real-time processor, and has part the releases showed the expected roadmap for the implementation of driverless / autonomous cars.

Renesas R-Car H3 Processor and SIP Module Block Diagram

Renesas R-Car H3 Processor and SiP (System-in-Package) Module Block Diagram (Click to Enlarge)

Let’s start with the processor (R8A77950) and SiP module (R8J77950) specifications:

  • CPU cores –  quad core  ARM Cortex-A57, quad core ARM Cortex-A53, and dual lock-step ARM Cortex-R7 cores with respectively 48KB/32KB, 32KB/32KB, and 32KB/32KB L1 instructions/operand cache.
  • GPU – IMG PowerVR Series6XT GX6650
  • External memory – LPDDR4-SDRAM up to 1600 MHz, data bus width: 32 bits x 4 ch (12.8GB/s x 4)
  • Expansion bus – 2 ch PCI Express2.0 (1 lane)
  • Video
    • Out – 3x display output
    • Input / camera – 8x video inputs
    • Video codec module (H.265, H.264/AVC, MPEG-4, VC-1, etc.)
    • IP conversion module
    • 2x TS Interfaces
    • Stream and Security Processor
    • Video image processing (Up and down scaling, Dynamic γ correction, Color space conversion, I/P conversion, Super resolution processing, Rotation, Visual near lossless image compression)
    • Distortion compensation module x 4 ch(IMR-LSX4)
    • High performance Real-time Image recognition processor(IMP-X5)
  • Audio
    • Audio DSP
    • 10x sampling rate converter, 10x serial sound interface
  • Storage – 4x SD host interfaces. 2x MMC interfaces, 1x SATA
  • USB – 1x USB 3.0 Host interface (DRD), 2x USB 2.0 Host/Function/OTG interface
  • In car network and automotive peripherals
    • 3-pin Media local bus (MLB) interface
    • 2x Controller Area Network (CAN-FD support) interfaces
    • Ethernet AVB 1.0-compatible MAC built in
    • RGMII interface
  • Security – 2x Crypto engine (AES, DES, Hash, RSA); SystemRAM
  • Other peripherals
    • 48x SYS-DMAC, 16x Realtime-DMAC, 32x Audio-DMAC, 26x Audio(peripheral)-DMAC
    • 26x 32bit timer
    • 7x PWM timer
    • 7x I2C, 11x Serial communication interface (SCIF)
    • 2x Quad serial peripheral interface (QSPI) for boot, HyperFlash support
    • 4x SPI/IIS Clock-synchronized serial interface (MSIOF)
    • Ethernet controller (IEEE802.3u, RMII, without PHY)
    • 4x Digital radio interface (DRIF)
    • Interrupt controller (INTC)
    • Clock generator (CPG) with built-in PLL
    • On chip debugger interface
  • Low power mode – Dynamic Power Shutdown, AVS(Adaptive Voltage Scaling), DVFS(Dynamic Voltage and Frequency Scaling), and DDR-SDRAM power supply backup mode
  • Supply voltages – 3.3/1.8V (/IO), 1.1V (LPDDR4), 0.8V (core), 2.5V (EthernetAVB)
  • Package
    • 1384 pin Flip chip BGA (21mm × 21mm, 0.5mm pitch)
    • 1255-pin SiP module (42.5mm × 42.5mm, 0.8mm pitch)
  • Manufacturing Process – 16nm FinFET+

Processor (Left) and SiP Module (Right)

This impressive system-on-chip supports Linux, Android, QNX Neutrino RTOS, Green Hills Integrity RTOS, and others operating systems. Development tools include an ICE for ARM CPU available from different vendors, and a development board with  “car information system-oriented peripheral circuits” that can  be used as a software development tool for application software. However, unless you decide to start a car company you probably won’t be able to buy this type of chip or evaluation board… Nevertheless, it could end up in your semi-autonomous car in a few years as while sample are available now,  mass production is scheduled to begin in March 2018, with ramping up to 100,000 units per month taking place in March 2019.


Autonomous car are a sure thing, with Google self-driving cars already on some roads (at slow speeds) and Formula E is even planning for driverless races, so the real question is about the time it may take to solve technical challenges, work out the regulations, and make the public confident enough to sit in autonomous cars. Renesas’ roadmap above shows R-Car H3 will be used for obstacle detection in 2018, semi-automated driving (ADAS = Advanced Driver Assistance Systems) in 2019, while fully autonomous cars may launch around year 2020 and beyond with the next generation (R-Car H4 ?) platform.

Renesas R-Car H3 Demo with 4K display and two secondary displays

Renesas R-Car H3 Demo with 4K display and two secondary displays

You can find more details on Renesas R-Car H3 page.

Via Nikkei Technology

iWave Systems iW-RainboW-G20M-Q7 SoM Features Renesas RZ/G1M Cortex A15 SoC

December 3rd, 2015 No comments

iWave Systems has unveiled a new Qseven 2.0 compliant system-on-module part of their RainboW family with iW-RainboW-G20M-Q7 module powered by Renesas RZ/G1M dual core ARM Cortex A15 SoC, and targeting industrial and automotive applications with over 10 years of support.

Click to Enlarge

Click to Enlarge

iW-RainboW-G20M-Q7 module specifications:

  • SoC – Renesas RZ/G1M dual core ARM Cortex A15 @ 1.5GHz with PowerVR SGX544MP2 GPU @ 520MHz
  • System Memory – 1GB DDR3(expandable)
  • Storage – 4GB eMMC Flash (expandable) + 2MB SPI NOR Flash for boot code, and optional Micro SD Slot
  • Connectivity – 1x Gigabit Ethernet  PHY
  • USB – 2 Port USB HUB
  • Renesas_som_back

    Click to Enlarge

    I/Os via 230-pin Qseven edge connector:

    • Storage – 1x SATA , 1x SDHC
    • USB – 1x USB3.0 host, 2x USB 2.0 hosts, or 1x USB 2.0 device
    • Display – 1x LVDS
    • Connectivity – 1x Gigabit Ethernet
    • Audio – 1x I2S Audio
    • 2x PWM, 2x I2C, SPI, CAN, UART, GPIOs
    • 1x PCIe (multiplexed with SATA)
    • JTAG or UART Console
  • Other expansion connectors:
    • 80-pin header 1 with
      • 24bpp RGB LCD or 16Bit Camera interface
      • 24Bit Camera or dual 8Bit Camera interface
      • 1x UART
    • 80-pin header 2 with
      • Memory bus interface (16-bit sync/async)
      • 1x CAN
      • 1x SSI/I2S for audio
      • 2x UART Port or 1x UART + 1x SPI
      • 2x PWM + GPIOs
  • Power Supply – 5V @  2A input through Qseven edge connector
  • Dimensions – 70mm x 70mm (Qseven 2.0 form factor)
  • Temperature Range – -40°C to +85°C Industrial
Block Diagram (Click to Enlarge)

Block Diagram (Click to Enlarge)

The module supports Linux 3.10.31, the company will provide BSPs and user’s manual for the Renesas module, and an optional RZ/G1M Qseven development kit is also available, and based on the company’s generic Qseven carrier board that supports both Qseven edge connector and the two non-standard 80-pin expansion connectors.

iWave Systems' generic Qseven Carrier Board with RainboW Q7 SoM

iWave Systems’ generic Qseven Carrier Board with RainboW Q7 SoM

Pricing and availability information is not publicly available, but you can request a quote for your project on RZ/G1M Qseven Module product page.

X5 ODB-II Head Up Display Shows Vehicle & Engine Speed, Fuel Consumption, and More on Your Windscreen

October 16th, 2015 5 comments

OBDII adapters have been around for a while. You simply attach it to the OBDII (aka OBD2) diagnostic connector of your car to get data such as engine’s RPM, vehicle’s speed, and failure logs over Bluetooth or USB onto your smartphone with apps such as Torque Lite. X5 ODB-II head up display uses the same technology but instead of displaying data your mobile’s screen, it shows it on the windscreen.


Some of X5 OBD2 HUD specifications and features:

  • Display – 3″ display with manual and automatic brightness adjustment
  • Vehicle interface – OBDII or EU OBD
  • Displayed Parameters / Alarms  – Vehicle speed (Km/h or M/h), engine speed (RPM), low voltage alarm, high temperature alarm (C or F), speed alarm, fuel consumption
  • Dimensions – 9 x 5.4 x 1.2 cm
  • Weight – 38 grams

The device comes with an  OBD-II Cable, and anti-skid mat, and a reflective film to work around a double reflection issue with some windscreens. I found X5 in GeekBuying’s newsletter, where it sells for $38.99, but it’s not the only model, as the company also sells X6 and Q7 models, for respectively $43.09 and $61.99, with the latter featuring a larger 5.5″ display.

I wondered how well the display would reflect on the windscreen, so I looked for reviews, and one person did a very nice review with A8 OBD2 HUD which he bought on GearBest for $42.89, which appears to be a better deal, as the device features a 5.5″ display. The video starts with an unboxing, but if you want to check the display functions and setup menu jump around the 4:30 mark, while the double reflection issue is shown at 9:30, and the actual test after installation is complete starts at 11:30. It looks better than expected at night and under shadow, but it’s certainly a bit washed out under a strong sun.

Categories: Hardware, Testing, Video Tags: automotive, hud, obd2

Gateworks Introduces an Embedded Android LCD Touchscreen Development Kit

September 3rd, 2015 3 comments

Gateworks has launched a rugged touchscreen LCD devkit featuring one of their Freescale i.MX6 based Ventana SBC, namely Ventana GW5224, that is similar to Ventana GW5220, but with a quad core Freescale i.MX 6Quad instead of the i.MX 6Dual found in the latter.

GW11036 Embedded Android Development Kit features and specifications:

  • GW5224 single board computer
    • SoC- Freescale i.MX6 Quad with 4x Cortex A9 core @ 1GHz and Vivante GPU (automotive grade: -40 to +125C)
    • System Memory – 1GB DDR3-800 SDRAM
    • Storage – 2GB Flash, micro SD slot, serial configuration EEPROM
    • Connectivity – 1x Gigabit Ethernet port (RJ45)
    • Video Output and Input – HDMI 1.4 out,  LVDS output,  3x analog composite video inputs
    • Audio – HDMI, analog stereo Line In/Out
    • Expansion – 2x Mini PCIe sockets including one with PCIe signalling
    • Other I/O ports:
      • Serial – 2x RS232, CAN Bus 2.0B @ 1 Mbps
      • Master/slave SPI, GPIO
      • USB – 1x USB 2.0 OTG port up to 480 Mbps
    • Misc – RTC with battery,  voltage & temperature monitor; 6-axis accelerometer/magnetometer, watchdog timer,  etc…
    • Power Supply – 8 to 60V DC via a power barrel or 36 to 60V DC via 802.3af PoE
    • Typical power consumption – 2W Watts @ 25 C (0.08A @ 24VDC)
  • Display Panel – 7″ TFT-LCD LVDS panel (1024×600) with LED backlight and PCAP touchscreen; black anodized bezel
  • Connectivity – 802.11 b/g/n WiFi, Bluetooth 4.0 + HS radio (GW17022 module), GPS receiver ( Wi2Wi W2SG0008i)
  • Dimensions – 184x127x37.5 mm
  • Weight – 400 grams
  • Operating Temperature – SBC: -40 to +85 C; LCD Panel: -20 to +70 C; Radio: 0 to 60 C

Beside GW5224 single computer and the touch enabled LCD panel, the kit also comes with GW17022 wireless module, a 8GB class 10 micro SD card pre-loaded with Android 4.4.3, a GPS magnetic mount antenna, a 24V/1A power supply, as well as all required cables and mounting hardware.

Gateworks_Industrial_TabletYou can find some documentation about Android for the kit and Ventana boards in general on Gateworks Wiki.

The rugged LCD panel kit appears to be available now, but price is only given upon request. Further information may be found on Gateworks GW11036 Embedded Android Development Kit page.

VIA Introduces AMOS-3005 Fanless Rugged Computer with Eden X4 x86 Processor, and VX11 Media Processor

August 14th, 2015 3 comments

VIA Embedded Store has just sent a newsletter to announce the launch of the company’s latest rugged embedded computer, AMOS-3005, powered by VIA Eden X4 processor and VX11 media processor and chipset, supporting temperature ranges from -10°C to 60°C, and featuring a flexible 9V-36V DC input.

VIA_AMOS-3005AMOS-3005 specifications:

  • Processor –  VIA Eden X4 quad core 64-bit x86 processor @ 1.2 GHz (NanoBGA2 package) with 2MB L2 cache, 1066 MHz front side bus
  • Chipset – VIA VX11 Media System Processor with an integrated VIA Chrome 640/645 graphics processor supporting DirectX 11, and OpenCL, as well as a VIA ChromotionHD 5.0 video engine supporting dual 1080p HD decoding of H.264, MPEG-2, WMV9, and VC-1 codecs.
  • System Memory – 1x DDR3 1333 SDRAM SODIMM socket (Up to 8GB memory size)
  • Storage – 1x mSATA slot, 32Mbit Flash memory for AMI BIOS.
  • Video Output- 1x HDMI, 1x VGA up to 2048×1536, with dual independent displays support
  • Audio – VIA VT2021 High Definition Audio Codec, Line-out and Mic-in
  • Connectivity – 2x Gigabit Ethernet ports (via Realtek RTL8111G PCIe controller), 1x SIM slot. 3G, GPS and Wi-Fi can be added via optional wireless modules.
  • USB – 2x USB 3.0 ports, 2x USB 2.0 ports (lockable for secure connections)
  • Serial – 2x RS-232/422/485 serial ports (DB9)
  • Expansion – 1x miniPCIe slot, 1x DIO port for 8-bit GPIO
  • Misc – Power on/off button, LED for HDD and Power, Watchdog Timer
  • Power Supply
    • 9 ~ 36V DC-in (typical: 19 Watts) via 2-pole Phoenix DC jack
    • Supports Wake-on LAN, keyboard power-on, timer power-on, system power management, AC power failure recovery, Watchdog timer control
  • Dimensions – 150.5mm(W) x 48.1mm(H) x 109.8mm(D)
  • Weight – 1.4 kg
  • Temperature Range – Operating: 0°C ~ 60°C with qualified industrial grade mSATA; Storage: -20°C ~ 70°C
  • Relative humidity – 0% ~ 95% (relative humidity; non-condensing)
  • Vibration loading during operation with mSATA Flash Drive: 5Grms, IEC 60068-2-64, random, 5 ~ 500Hz, 1 Oct./min, 1hr/axis
  • Shock during operation with mSATA Flash Drive: 50G, IEC 60068-2-27, half size, 11ms duration
  • Compliance – CE/FCC


The kits includes AMOS-3005 system, a 12V/5A AC-to-DC adapter with a 2-pole phoenix plug to DC jack, screw packs for mounting and  Mini PCI-e card,  washer rubbers pack, thermal pad for the mSATA module, and a syringe with thermal grease. The computer also supports Wall/DIN rail/VESA mounting system. Memory and storage are not included, which means you’ll also need to install your own operating systems, which can be Windows 10/8.1/8/7, WES 7, or Linux distributions.

The computer targets industrial automation, remote terminal and data collection, as well as in-vehicle computing applications. The barebone system is not quite cheap, but it’s expected for an industrial & automotive PC, as it sells without storage nor memory for $539 on VIA Embedded Store. More details, including the user’s manual and Windows drivers, can be found on AMOS-3005 product page.

Allwinner T2 Dual Core Processor is Made for Automotive Infotainment and Navigation

June 4th, 2015 1 comment

Allwinner already has several processor families, the most famous being the A-series for tablets, followed bythe H-series for home entertainment, the V-series for video application, the R-series for IoT as found in R8 module used in C.H.I.P $9 computer, and now I’ve just found out the company launched T-series with Allwinner T2 and T8 for “Transportation”/automotive applications.

Allwinner T2 Block Diagram (Click to Enlarge)

Allwinner T2 Block Diagram (Click to Enlarge)

I don’t have any details about T8 processor, but the company kindly shared a product brief with the specs for Allwinner T2:

  • CPU – Dual core Cortex A7
  • CPU – Mali-400MP2 supporting OpenGL ES 1.1/2.0
  • Memory – DDR2, DDR3, and DDR3L controller, NAND flash controller with 64-bit ECC
  • Video Inputs – 4x AV Inputs
  • Video – H.264 2160p video decoding, multi-format decoding, h.264 encoding @1080p30 / 720p60.
  • Display – Multi-channel HD display with integrated HDMI 1.4 transmitter, CPU/RGB/LVDS display interface, support for VGA/CVBS/YPbPr, and integrated TV decoder.
  • Camera – Integrated parallel 8-bit interface YUV sensor, integrated 24-bit parallel YUV 444 I/F, supports 5MP CMS sensors, and dual sensors
  • Audio – Integrated HiFi 100 dB audio codec, dual analog MIC amplifier
  • Low speed I/F – 5x TWI, 4x SPI, 8x UART
  • 3x USB 2.0, 4x SDIO

The processor supports Android 4.2. Allwinner T2 can be used in dual-channel HD car DVR applications, including features such as around view parking (with 4x AV inputs), WiFi and AP hotspot, voice assistance, rapid reverse image function, 3G/2G voice and data, multimedia playback, radio, Bluetooth Voice/Music/Dial, DVD playback, GPS navigation, and keys and touch panels. also uploaded a video showing a few solutions featuring Allwinner T2.

There’s no product page yet, but according to the video above, Allwinner T2 solutions are already in mass production in China.

Freescale Announces i.MX 6SoloX ARM Cortex A9 & Cortex M4 Processor

February 25th, 2015 7 comments

Freescale i.MX6 SoloX processor started to show up in the ARM Linux Kernel mailing list last year, and Cortex A9 + Cortex M4 processor showed up in some marketing documents, but so far all documentation was tied to a non-diclosure agreement. However, all resources are now publicly available, as the company officially launched i.MX 6SoloX processor at Embedded World 2015.

IMX6SX Block Diagram

IMX6SX Block Diagram (Dotted line are for optional features)

Freescale i.MX 6SoloX specifications:

  • CPU – ARM Cortex-A9 up to 1 GHz with 512 KB L2 cache, 32 KB instruction and data caches and NEON SIMD media accelerator
  • MCU – ARM Cortex-M4 up to 200 MHz with 16 KB instruction and data caches, 64 KB TCM, MPU and FPU
  • Memory Interface
    • 16/32-bit DDR3-800 and DDR3L-800, 16/32-bit LPDDR2-800
    • SLC/MLC NAND, 62-bit ECC, ONFI2.2
    • 2x DDR Quad SPI NOR flash, 16/32-bit NOR Flash
  • Display and Camera Interfaces
    • Parallel RGB
    • LVDS
    • 20-bit parallel CMOS sensor interface
    • NTSC/PAL analog video input interface
  • Multimedia
    • GPU – Vivante GC400T 3D GPU supporting OpenGL ES 2.0. 27Mtri/s & 133Mpxl/s and 2D GPU
    • PiXel Processing Pipeline (PXP) – Image re-sizing, rotation, overlay and CSC
  • I/O and Peripherals
    • 2x 10/100/1000 Ethernet with \hardware AVB and support for IEEE1588
    • 1x PCIe 2.0 (1 lane)
    • 2x 8ch 12-bit ADC
    • 3x USB 2.0 ports, 2x HS OTG + PHY, 1x HS Host HSIC
    • 4x SD/MMC 4.5
    • 5x SPI, 6x UART, 4x I²C, 5x I²S/SSI
    • FlexCAN
    • MLB 25/50
  • Power management – Partial PMU integration,Freescale PF0200 PMIC
  • Security
    • Multicore unit includes for multi-core isolation and sharing
    • Resource Domain Controller (RDC)
    • Secure Messaging Unit (MU)
    • Hardware Semaphores
    • High Assurance Boot, cryptographic cipher engines, random number generator, and tamper detection
  • Packages – 19 x 19 mm 0.8 mm BGA;  17 x 17 mm 0.8 mm BGA (two ball map options); or 14 x 14 mm 0.65 mm BGA
  • Temperature Range
    • Consumer (Extended Commercial) –  -20C to +105C
    • Industrial – -40C to +105C
    • Automotive – -40C to +125C)

There are 13 i.MX 6SoloX parts divided into consumer, industrial and automotive categories with or without GPU, and different peripherals options as shown in the table below.

Freescale i.MX 6SoloX Family (Click to Enlarge)

Freescale i.MX 6SoloX Family (Click to Enlarge)

Documentation including datasheets, migration guide, various applications, and the full Technical Reference Manual can be freely downloaded, as well as Android 4.4.3 BSP and Linux 3.10.53 documentation. The Yocto Project has also been ported to i.MX 6SoloX (IMX6SX). The Cortex M4 core can run MQX RTOS in parallel.

SABRE-SDB Board for i.MX 6SoloX (Click to Enlarge)

“SABRE for Smart Devices”- Board based on Freescale i.MX 6SoloX (Click to Enlarge)

The company also also launched an i.MX 6SoloX version of their SABRE development board with the following key features:

  • SoC – Freescale i.MX 6SoloX Cortex A9 processor @ 1GHz with Cortex M4 MCU @ 200MHz
  • System Memory – 1 GB DDR3 SDRAM
  • Storage – 32 MB x2 QuadSPI Flash + 3x full-size SD/MMC card slots
  • Display
    • LVDS connector – Pairs with MCIMX-LVDS1 LCD display board
    • LCD expansion connector (parallel, 24-bit) – Pairs with MCIMXHDMICARD adapter board
  • Audio – Stereo audio codec; 1x 3.5mm audio ports
  • Connectivity – 2x 10/100/1000 Ethernet ports; optional Wi-Fi module
  • USB – 1x USB 2.0 Host Type A connector, 1x micro USB 2.0 OTG connector
  • Other ports and I/O Expansion
    • mPCIe connector
    • 2x CAN (DB-9) connectors; Freescale MC34901 High-Speed CAN Transceiver
  • Debugging – 20-pin JTAG connector
  • Sensors – Freescale MMA8451 3-Axis Accelerometer, Freescale MAG3110 3D Magnetometer, ambient light sensor
  • Power Supply – 5V
  • Power Management – Freescale PF0200 PMIC
Back of SABRE i.MX 6SoloX Board (Click to Enlarge)

Back of SABRE i.MX 6SoloX Board (Click to Enlarge)

The board comes with a 5V/5A power supply, the printed quick start guide, a micro USB to USB cable, and a bootable SD card pre-loaded with a Linux image built with the Yocto Project. Android, Linux and Yocto BSP are available for the board, as well as hardware design files. Some optional hardware modules can be purchased with the board such as a 10.1″ touchscreen display (XGA resolution), an RGB to HDMI adapter, and a Wi-Fi radio card.

You can watch an overview of the board, and learn how to get started in the video below.

Freescale i.MX 6SoloX applications processors and SABRE board are both shipping in volume production, with the SoC selling for $10.84 to $13.99 in 1K quantities depending on exact SKU, and the development board priced at $399. For complete details, software and hardware documentation, visit Freescale i.MX 6SoloX and SABRE board product pages. Freescale also exhibits the solution at Embedded World, in Hall 4A, Booth 4A-220, on February 24-26, 2015.

Embedded Linux Conference 2015 Schedule – IoT, Cars, and Drones

February 6th, 2015 2 comments

Embedded Linux Conference 2015 will take place in San Jose, California, on March 23 – 25, 2015, and will focus on Drones, Things and Automobiles. The schedule has been published, and whether you’ll attend or not, it’s always interested to have a look at what will be talked about to have a peak into the future of Embedded Linux, or simply keep abreast with the progress in the field.

Embedded_LInux_Conference_2015So as usual, I’ve gone through the schedule, and made my own virtual program with talks that I find interesting.

Monday 23rd

  • 9:00 – 9:30 – Driving standards and Open Source to Grow the Internet of Things by Mark Skarpness, Director of Systems Engineering at Intel

Billions of devices are beginning to come online, and many of these devices, large and small, are running open source software.  To fuel this innovation, it’s more important than ever for these devices to use a common framework to communicate with each other and the cloud.  Intel is a founding member of the Open Interconnect Consortium (OIC), which will use both open source innovation and standards specifications to drive interoperability across multiple operating systems and communication protocols to enable the Internet of Things. As one of the founding members of the Linux Foundation, a top external contributor to the Android Open Source Project, and a leader behind USB, WiFi, Bluetooth and other projects and standards, Intel has the depth of knowledge and a unique approach to move things forward to benefit developers and consumers.

  • 9:30 – 10:00 – Project Ara with Paul Eremenko, Head of Project Ara, ATAP at Google & Marti Bolivar, Project Ara Software Lead, Google

Marti and Paul will discuss Project Ara’s aim to develop an open hardware platform for modular smartphones, with the goal of creating a vibrant module developer community and a marketplace from which consumers can create an entirely custom mobile device.

  • 10:45 – 11:35 – Generalizing Android for Low-Cost 64-Bit ARM-Based Community Boards by Khasim Syed Mohammed, Linaro

Linaro is developing an open hardware platform specification to encourage software development on low-cost boards to lower the cost and accelerate the availability of maker and embedded products based on ARM SoCs. By end of 2015 there will be many compliant boards based on and adhering to this specification. The key challenge for the Android community is to enable and maintain Android for multiple platforms on a common code base. This presentation highlights the issues like non-standard SoC customizations, peripheral controller customizations from vendors and shares the possible solutions through Android software generalization.

  • 11:45 – 12:35 – Open Source Drones on Linux by Lorenz Meier

This presentation will summarize the current state in academia and industry using Linux on drones, which is by now already a widespread and common pattern.

  • 14:00 – 14:50 – IoTivity and Embedded Linux Support by Kishen Maloor, Intel

IoTivity is a new collaborative project, hosted at the Linux Foundation and sponsored by the Open Interconnect Consortium. Its goal is to facilitate interconnections across the billions of “things” to be on the Internet in coming years. A majority of these “things” would be low-power embedded devices. To satisfy their connectivity needs, IoTivity must support a variety of transmission media, such as WiFi, Bluetooth, Bluetooth LE, 6LoWPAN over 805.15.4, etc. This session will present an overview of IoTivity’s current support for the Yocto Linux environment on embedded platforms, and how it allows us to be flexible for multiple purposes. It will also present how a developer can enable IoTivity on Yocto and make modifications.

  • 15:00 – 15:50 – Performance Analysis Using the perf Suite by Mans Rullgard

When faced with a performance problem, the initial steps towards a solution include identifying the sections of code responsible and the precise reasons they are time-consuming. To this end, the ‘perf’ profiling tools provide valuable insight into the characteristics of a program. The presentation will show, using real-world examples, how the ‘perf’ tools can be used to pinpoint the parts of a program in need of optimisation.

This presentation will be a version of that given at ELCE 2014 updated based on questions and audience feedback.

  • 16:20 – 17:10 – Poky meets Debian: Understanding How to Make an Embedded Linux by Using an Existing Distribution’s Source Code by Yoshitake Kobayashi, Toshiba

Poky has already become one of the most popular build system to make an embedded Linux environment. Poky refers to OpenEmbedded originally. However if you want to use other source code, how to do it? We have some experience we would like to share with you. For this study, We choose Debian source and already tried two ways to use it. The first try was probably an incorrect way and the second try may be a correct way.

In this talk, we will show both of them and also describe why we choose Debian. If you are interested in this implementation, you can download the source code from GitHub (cnxsoft: empty for now). There are some implementations available for development boards such as pandaboard, minnowboard and etc. Let’s enjoy Bitbake!

  • 17:20 – 18:10 – Teaching More Fish to Fly by John Hawley, Intel

n 2013, at the Embedded Linux Conference in Europe in Edinburgh, there was a race between a dog and a blimp. It was said that despite the dogs win, that the blimp had participated in the miracle of flight. In 2014 we started showing how the MinnowBoard can be lofted and show useful. In 2015 we just want to give an update on where we are at and what interesting projects are being done both with the MinnowBoard and other platforms in the UAV space. The talk is mainly targeting taking an off the shelf embedded platform, Minnowboard Max, and it’s use in UAVs, specifically quad-copters. With the ability to do real time computer vision, as well as various GPIO capabilities we’ll explore the directions that significantly more autonomous UAVs can take with Linux and embedded platforms using, mostly, off the shelf components.

Tuesday 24th

  • 9:00 – 10:50 – Customizing AOSP for my Device by Rafael Coutinho, Phi Innovations

Android BSP gives you some tools to create your own device customizations. This can be achieved without changes on the Android main code, and just some customizations on the devices folder. It is possible to overlay some system apk configurations, ui and even services. In this tutorial I plan to show the step by step of creating a custom Android device using a AOSP. Setting up some Kernel parameters, customizing the lights HAL and sensors HAL, changing the look and feel of Settings apk etc.

  • 11:20 – 12:10 – Room For Cooperation: Bionic and musl by Bernhard Rosenkränzer, Linaro

A while after Android started Bionic, another interesting libc project was started: musl. Its licensing is compatible with Android’s – so there may be room for picking the best of both worlds. This talk investigates where musl outperforms Bionic and vice versa — and whether or not (and how) Android can benefit from pulling musl code into Bionic.

  • 13:40 – 14:10 – Dronecode Project and Autopilot With Linux by Andrew Tridgell, Technical Steering Committee Chair of Dronecode Project

Andrew “Tridge” Tridgell provides updates on the progress of Dronecode’s open source software project for commercial drones, and insight into the future of drone development. He will also delve into the specific task of running an autopilot directly on a Linux-based platform.

  • 14:10 – 14:55 – IoT Panel with Dominig Ar Foll, Intel (Tizen); Greg Burns, AllSeen Alliance; Bryant Eastham, Panasonic; Guy Martin, Samsung; Tim Bird, Sony Mobile (Moderator)
  • 15:40 – 16:30 – Linux for Microcontrollers: From Marginal to Mainstream by Vitaly Wool, Softprise Consulting OU

The story of a DRAM-less Linux-operated microcontroller delivered at ELC a year ago, which came as a surprise for many, wouldn’t be that surprising now. However, there are some important updates to share: moving to mainline-aligned 3.x baseline, compiling out VM-specific code, optimizing kernel XIP, and the last but not the least, starting to use picoTCP kernel networking stack.

Some size and performance benchmarks will also be presented, along with the Linux demo on the DRAM-less microcontroller board.

  • 16:40 – 18:20 – Building a General Purpose Android Workstation by Ron Munitz

In this tutorial, you will have a hands-on journey of customizing, building, and using a General Purpose Desktop variant of the Android-X86 project. The tutorial assumes previous experience with building Android off the AOSP, Android-IA, CyanogenMod, or any other build system, and describes the special additions of Android-X86, such as a Kernel build system, general X86 hardware detection based HAL’s/firmware and live cd/disk installer generation and more. Then, we will explore the Linux friendly busybox minimal image, and describe the way a fully fledged Android version can be spawned out of it (with similar techniques for any other Linux distribution with the Android patches!) using chroot, and provide a listing of the ultimate Android init process.

We will continue the discussion with day to day uses, and a joint brainstorming of Linux developer uses, and justify Android-X86 as yet another X-less Linux distribution – until the time we add X to it… As a special bonus, we will address how to make any app run using a user-QEMU based ARM translator.

  • 18:20 – 19:20 – BoFs: Yocto Project / OpenEmbedded by Jeff Osier-Mixon

Got a question, comment, gripe, praise, or other communication for the Yocto Project and/or OpenEmbedded? Or maybe you’d just like to learn more about these projects and their influence on the world of embedded Linux? Feel free to join us for an informal BoF.

Wednesday 25th

  • 9:00 – 9:30 – Embedding Openness in the Connected Car by Matt Jones, Jaguar Land Rover

A future vehicle will be a “thing” on the Internet, but how can industry and community come together to accelerate the future concepts into production. The keynote will explore the platforms and standard needed for the future, and relate them to open prototypes from Jaguar Land Rover and the Automotive Grade Linux projects.

  • 9:30 – 10:00 – Community Involvement: Looking Forward and Looking Back by Deepak Saxena

Linux has grown by leaps and bounds in the last decade, finding its way into billions of mobile devices and also into the core of cloud based services that we rely on for business, entertainment, and increasingly, security. With this explosion of devices, we have seen more companies get involved with the kernel community, some successfully, and some struggling. In this talk, we will look at some of the challenges that the industry and the community continue to face in working with each other and also more importantly think about what is next? The adoption of Linux will continue to increase throughout all market segments, bringing in numerous new organizations and new developers. How do we move forward and what changes need to happen within the industry and community cultures to work better together?

  • 10:45 – 17:50 – Embedded Android Workshop by Karim Yaghmour, Opersys

While Android has been created for mobile devices — phones first and now tablets — it can, nonetheless, be used as the basis of any touch-screen system, whether it be mobile or not. Essentially, Android is a custom-built embedded Linux distribution with a very elaborate and rich set of user-space abstractions, APIs, services and virtual machine. This one-day workshop is aimed at embedded developers wanting to build embedded systems using Android. It will cover Android from the ground up, enabling developers to get a firm hold on the components that make up Android and how they need to be adapted to an embedded system. Specifically, we will start by introducing Android’s overall architecture and then proceed to peel Android’s layer one-by-one.

That’s a just a small selection of the talks, and there are many other interested sessions if you are interested in IoT, automotive or drone applications.

If you’d like to attend, you can register online with a single fee for the Embedded Linux Conference and Android Builders Summit 2015, as well as breakfasts and breaks, a T-shirt, and access to evening events:

  • Early Bird Registration Fee – US$500 through January 30, 2015
  • Standard Registration Fee – US$650 through March 5, 2015
  • Late Registration Fee – US$750 after March 5, 2015
  • Student Registration Fee – US$150
  • Hobbyist Registration Fee – US$150

If you attend as a hobbyist, you need to contact events [at] to receive a discount code.