Archive

Posts Tagged ‘gpu’

ODROID-XU4 Development Board is a Smaller and Cheaper Version of ODROID-XU3 Board

July 14th, 2015 17 comments

Many people are expecting Hardkernel to launch an Exynos 7 board, but this won’t be with ODROID-XU4, maybe with ODROID-XU5, as the latest development board from Hardkernel is a modified version of ODROID-XU3 with the same Exynos 5422 octa-core processor with four Cortex-A15 cores @ 2GHz and four Cortex-A7 cores.
ODROID-XU4ODROID-XU4 board specifications (differences with ODROID-XU3 highlighted and sometimes crossed out in bold):

  • SoC – Samsung Exynos 5422 quad core ARM Cortex-A15 @ 2.0GHz quad core ARM Cortex-A7 @ 1.4GHz with Mali-T628 MP6 GPU supporting OpenGL ES 3.0 / 2.0 / 1.1 and OpenCL 1.1 Full profile
  • System Memory – 2GB LPDDR3 RAM PoP (750 MHz, 12GB/s memory bandwidth, 2x32bit bus)
  • Storage – Micro SD slot (up to 64GB) + eMMC 5.0 module socket (16, 32, and 64GB modules available)
  • Video Output – micro HDMI (Up to 1080p) and DisplayPort (up to 2160p)
  • Audio Output – HDMI, 3.5mm headphone jack, and optional S/PDIF out via USB module
  • Network Connectivity – 10/100/1000Mbps Ethernet (~880 Mbps measured with iperf). and optional USB Wi-Fi dongle with antenna
  • USB – 2x USB 3.0 host port, 1x USB 2.0 ports
  • Expansion – 30-pin header for access to GPIO, IRQ, SPI and ADC signals + 12-pin headers for GPIO., I2S, and I2C
  • Debugging – Serial console header
  • Misc – Accurate current sensors and voltage sensors for energy measurement, Power and RGB LEDs, cooling fan header, power button, RTC
  • Power Supply – 5V/4A power adapter using 5.5/2.1mm barrel.
  • Dimensions – 82 x 58 x 22 mm (ODROID-XU3: 94x70x18mm;)
  • Weight – 60 grams with fan
Block Diagram for ODROID-XU4 Board (Click to Enlarge)

Block Diagram for ODROID-XU4 Board (Click to Enlarge)

One of the cool changes is the HDMI type A connector replacing the micro HDMI port found on most other ODROID boards, and which (indirectly) caused issues for several people, including myself. The Ethernet port now supports Gigabit Ethernet, there are two full-size USB 3.0 host ports, a few more I/Os, and the board is smaller. However, a few ports and ICs are gone including USB OTG support, DisplayPort output, the Audio codec (and audio jack), and the power monitoring sensors. The memory is now clocked at 750 MHz instead and 933 MHz in ODROID-XU3 and ODROID-XU3 Lite.

You can check the introduction video for a quick overview of the new board.

ODROID-XU4 is software compatible with ODROID-XU3 so there’s probably not much new here, and the board supports Ubuntu 15.04 (with OpenGL ES + OpenCL support), and Android 4.4 KitKat and 5.0 Lollipop.

I’m pretty sure most people will still be happy with the board despite some of the lost features, as while ODROID-XU3 costs $179, the new ODROID-XU4 sells for only $74 with a 5V/4A power supply, and the heatsink + fan (mounted). If you are interested, you can purchase it via Hardkernel website, or one of their distributors. It’s also cheaper than  ODROID-XU3 Lite ($99) with features the same Exynos processor but clocked at a lower frequency.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Open Source Linux Drivers for PowerVR GPUs Might Be in the Works

June 18th, 2015 8 comments

When I write about a new processor with a PowerVR GPU, I can be sure there will be one or two comments saying something like “It has a PowerVR GPU, it’s a non-starter”, mostly because of the status of graphics drivers in Linux. Luc Verhaegen (libv) also made a presentation at FOSDEM 2013 listing various open source projects for GPUs found in ARM processors and PowerVR was the only one without any community project. Bear in mind that apart from Nvidia, and to some extend Broadcom for the VideoCore IV GPU found in  BCM2835 / BCM2836 processors used in Raspberry Pi boards, no other companies have released user space drivers for their GPUs, and all work is done by volunteers for other open source GPU drivers, and I’m not sure any of them work 100% yet.

Imagination has already provided working GPU drivers for their MIPS Creator-CI20 board, these are closed source binaries, but at least they should be usable in Linux. Now Alexandru Voica, Senior Marketing Specialist at Imagination Technologies, and who seems to handle press releases and many of the posts in the company’s blog, has hinted that Imagination is currently working on open source drivers for their GPU in reddit.

Q: Is there plans to make/help/fund open PowerVR driver for Linux?

A: Yes, there is a plan and it is one of the things I’ve been working on for the past few months. Hopefully I’ll have something more to share soon(-ish?).

Sadly, there aren’t any details right now, so we’ll have to be patient and see what comes out of this.

Via Phoronix and Harley.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Embedded Systems Conference 2015 Schedule – May 6-7, 2015

March 11th, 2015 No comments

The Embedded Systems Conference took the name “Design West” for a couple of years, but this year, there’s no mention of Design West, and the Embedded System Conference 2015 will take place in Boston, MA, US on May 6-7, 2015. The 2-day event will have a demo hall, and well as sessions divided into 8 tracks:Embedded_Systems_Conference_2015

  • Connected Devices and the IoT
  • Embedded Software Design
  • Hardware: Design, I/O and Interfacing
  • Prototyping
  • Embedded Systems Design
  • Software: Design, Languages, & Quality
  • Fantastical Theater
  • Teardowns

The full schedule has now been posted, and I’ll build a virtual schedule with some of the sessions provided.

Wednesday May 6, 2015

  • 8:00 – 8:45 – Understanding Google/Nest Thread by Michael Anderson, Chief Scientist, The PTR Group, Inc.

The IoT will live or die based on its connectivity. In examining existing wireless protocols, Google/Nest found most of them lacking. In order to address the needs for low-power wireless communications in the home, Thread was created. Thread is an implementation of an IEEE 802.15.4 mesh-based network that provides IP connectivity using existing radio silicon. Come to this session to get the latest information on Thread, its capabilities and characteristics and how you can use Thread in your next IoT device.

  • 9:00 – 9:45 – Best Practices for Designing Hardware APIs by Matt Haines, Communications Manager, Electric Imp

We are rapidly heading toward a world in which most of the objects we interact with on a daily basis will be connected to the Internet. What does this world look like, and how do we design Connected Things that will live in this world? This presentation will address the issue of API design; a topic often talked about in web development but just as often overlooked in conversations about the IoT. What should we be thinking about when we’re designing an API for a connected product? Why do our connected products even need APIs? What strategies and best practices can we apply from web API design?

  • 10:00 – 10:45 – Choosing Between Multicore CPU, GPU & FPGA Technology for Vision Applications by Julianne Kline, Systems Engineer, National Instruments

FPGA, GPU, and multi-core CPU processing will be compared and contrasted. Examples will be highlighted on when customers may want to use one technology over the other. A heavier focus will be placed on FPGA technology. This presentation will discuss recommendations for when to integrate FPGA technology into vision applications, such as for image pre-processing, high-speed control, or processing parallelism. Types of algorithms well-suited to FPGA technology will also be discussed, and resources for accessing existing FPGA IP will be provided.

  • 11:00 – 11:45 – Mob Programming for Embedded Systems Software by Nancy Van Schooenderwoert, President, Lean-Agile Partners, Inc.

Mob Programming is a practice where a whole software team works together, at one computer, one line of code at a time, outperforming their previous work significantly in both quality and volume. Impossible? Maybe except for the teams actually doing it now. One team in California began in 2011, and it’s been spreading since. This session tells the story of the first embedded systems teams to use MobProgramming.This session is a double experience report plus a demo: Speaker Simon Clements-Hawes gives his observations as an embedded systems team member starting to use MobProgramming, and Nancy describes how to get a team started in MobProgramming. Thru video clips, the team’s coding of a LeanKit interrogator in C# will be shown using Mob Programming of course!

  • 14:00 – 14:45 – Is There an Arduino Debugger in the House? by Guido Bonelli, President, Innovative Electronic Solutions LLC

Arduino development and the hardware debugging landscape OR THE LACK THEREOF! In this session you will delve into the Arduino developer’s tool chain from a hardware perspective. What hardware debugging solutions are currently available and how Dr.Duino the Arduino hardware debugger can reduce your debugging pain. We shall discuss the blissful highs of easy firmware development on a standard platform while then exploring the lowliest of lows when debugging the hardware/firmware interactions.

  • 15:00 – 15:45 – ARMv8 Kernel Internals by Arun Thomas, Senior Principal Engineer, BAE Systems

This talk is meant to be a quick start guide for embedded developers who are new to the ARMv8 architecture. I will discuss how operating systems interface with the 64-bit ARMv8 architecture and will cover the ARMv8 specific kernel internals of Linux and FreeBSD. I will discuss how booting, memory management, exceptions, and interrupts work using examples drawn from the kernel source.

Thursday May 7, 2015

  • 08:00 – 08:45 – Open Source Software: Tips for Avoiding Licensing Surprises by Jason Kunze, Attorney, Nixon Peabody LLP

A practical, quick hitting summary of the key considerations that anyone developing, purchasing or licensing software should consider. After a brief discussion of legal basics, practical concerns relating to open source software will be explained through the lens of actual cases in this developing area of law. The participant will gain a general understanding of:

  1. The intellectual property rights that may attach to software
  2. The competing ideologies behind open source software and how this drives licensing terms
  3. Some of the leading open source software licenses and their relative level of restrictions
  4. Pitfalls to recognize and avoid in relation to open source software
  • 09:00 – 09:45 – How NOT To Do Embedded Development! Practical Lessons From Real Projects That Almost Went Off A Cliff by Dave Nadler, President, Nadler & Associates

In an interactive (Socratic) discussion, we’ll review some real-world projects in trouble and how they were sorted. Projects include an automated toll-collection system, an aircraft collision-avoidance system (cool movie!), a manufacturing instrumentation product, and an integrated flight computer. We’ll cover a variety of coding and testing techniques used to get these projects on track.

  • 10:00 – 10:45 – Designing for the IoT with Lower Power and Way More Intelligence by Dana Myers, Channel Marketing Manager, Wireless Connectivity Solutions, Texas Instruments

As the Internet of Things (IoT) has changed the way we live, do business and make decisions, it has also impacted engineers’ designs. This presentation will address the benefits and challenges of designing for the IoT in regards to low-power, integration and performance. This will let engineers weigh the tradeoffs of each connectivity architecture and provide a quick pathway to begin designing their products for the fast-growing IoT.

  • 11:00 – 11:45 – Squeezing the Most Out of Battery Life using ARM Cortex-M Processors by Jacob Beningo, Principal Consultant, Beningo Engineering

The proliferation of mobile devices has led to the need of squeezing every last micro-amp-hour out of batteries. Minimizing the energy profile of a micro-controller is not always straight forward. A combination of sleep modes, peripheral control and other techniques can be used to maximize battery life. In this session, strategies for optimizing micro-controller energy profiles will be examined which will extend battery life while maintaining the integrity of the system. The techniques will be demonstrated on an ARM Cortex-M processor.

  • 14:00 – 14:45 – Network Insecurity: Simple Hacks of ARM Cortex-M Devices by Jonny Doin, CEO, Grid Vortex Systems

The IoT is a very new domain of a very old activity: Embedded Systems Design, with a twist: connection to the most toxic of environments, the Internet. One of the main concerns of the IoT is how to cope with the massive amount of unanticipated network traffic and problems. Malformed packets, corrupted messages, specifically targeted attacks, buffer overflow exploits, spoofing, stuxnet emulation messages, denial of service, fake OTAP, and other exploits and attacks can transform your IoT devices into something you did not design for. This situation demands several good practices and programming concerns regarding network safety and security into even the smallest of things. Buffer integrity checks, full parameters domain verification, message authentication, data path integrity verification, and crypto security are among the needed elements of a safe and secure IoT system, and can be implemented on nearly any Embedded System. Examples of simple attacks on ARM Cortex-M devices will be presented, including RET2ZP and buffer attacks.

  • 15:00 – 15:45 – RTOS Smackdown: 7 RTOSes in 45 Minutes! by 7 speakers

There are a lot of Real Time Operating System (RTOS) options out there. Which one is right for your embedded system? Do you even need an RTOS at all? In this feisty presentation, one industry expert will argue that an RTOS is superfluous to requirements, while another will contend that an RTOS is an invaluable, “must-have” asset, even if your embedded application performs only a handful of tasks. After the dust dies down, proponents of seven of the leanest, meanest, coolest, hottest contenders in the RTOS multi-universe will take it in turns to explain why their RTOS is the bestest of the best.

If you’d like to attend the conference you can register online. Access to the demo hall is free, unless you come without registration, in which case you’d have to pay $75 for entry. A pass is required for the full conference and access to sessions with the following pricing:

  • SUPER EARLY BIRD (Ends January 30) – $799
  • EARLY BIRD (Ends March 6) – $949
  • ADVANCED (Ends May 1) – $1,149
  • REGULAR/ONSITE – $1,299

Seven vendors’ sponsored sessions can be attended with a free “demo hall” registration.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Meet Vulkan, The Successor of OpenGL and OpenGL ES 3D Graphics APIs

March 4th, 2015 4 comments

So far embedded systems are typically using SoCs with GPU supporting OpenGL ES, a subset of the full fledge OpenGL API used in desktop computers and workstations. These royalty-free standards are defined by Khronos Group non-profit organization, and as features in the embedded space and traditional computers merge, the group has now revealed the next-generation OpenGL specs will be called Vulkan. The new API will run on GPUs supporting OpenGL ES 3.1 or greater, take less CPU resources than its predecessors, and support multiple command buffers that can be created in parallel.

OpenGL_ES_vs_Vulkan

More work will be required at the application level, but direct GPU control by the drivers will apparently result in less memory copies improving performance, or at least off-loading the CPU. It might be transparent to developers using game engines. GPU drivers will also be less complex.

Vulkan will also use the new SPIR-V language shared with OpenCL 2.1 for graphics and compute. A (possibly open source) GLSL shader source to SPIR-V translator / compiler will be provided for legacy code.

Vulkan_SPIR-V

Vulkan Language Ecosystem

You’ll find more technical details, and some information about tools on Khronos Vulkan page.

I understand that Vulkan is still work-in-progress, but Imagination Technologies has already written alpha Vulkan compatible drivers for their PowerVR GPU, and run their Library demo on Android 5.0, so progress appears to be good, but it looks like more work has to be done to improve performance.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Imagination PowerVR GT7900 GPU is Made for Game Consoles and Notebooks

February 27th, 2015 3 comments

Imaginatino Technologies has just introduced the most powerful GPU of their new PowerVR Series7 GPU family with GT7900 featuring 16 unified shading clusters and 512 ALU cores for game consoles, micro-servers, and notebooks.

PowerVR_Series_7XT_GPUPowerVR GT7900 is still an embedded GPU with support for OpenGL ES 3.1 + AEP (Android Extension Pack) compatibility, full hardware support for tessellation and ASTC LDR and HDR texture compression standards. The new GPU delivers up to 800 GFLOPS (FP32) or 1.6 TFLOPS (FP16) graphics and compute performance at 800 MHz (using 16 nm FinFET+ manufacturing process), which compares to about 550 GFLOPS (FP32) for an Nvidia GeForce GT730M at comparable frequency. This is even more powerful than the Maxwell GPU found in Tegra X1 which delivers 1+ TFLOPS (FP16), although the Nvidia processor may have a lower power envelope.

FT7900 Block Diagram

GT7900 Block Diagram (Click to Enlarge)

Combined with PowerVR Series5 decode and encode video processors and PowerVR V2500 camera processor, GT7900 can be integrated into SoC that support 4K video output, playback (10-bit @ 60 fps) and recording.

Imagination Technologies did not disclose information regarding availability, but they may provide further details at the Game Developers Conference (GDC) 2015 and Mobile World Congress (MWC) 2015.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Categories: Graphics Tags: games, gpu, imagination

ARM Releases Kernel Drivers for Mali-T880 / T860 GPUs, User Space Drivers for Mali-T76x GPUs

February 23rd, 2015 17 comments

ARM Mali GPU drivers includes both open source kernel drivers, and binary userspace drivers supporting framebuffer and/ior X11 implementation. The former is rarely an issue and is quickly released, but the latter requires porting and testing for a specific hardware platform, as well legal work, which greatly delay the releases.

ARM_Mali_GPU_Drivers

Release r5p0-06rel0 for User Space Binary Drivers

Mali-T880 GPU was announced at the beginning of the month together with ARM Cortex A72, and on February 17, 2015, ARM released an update to their Mali-T600 series, Mali-T700 series & Mali-T860/T880 GPU kernel device drivers with revision r5p1-00rel0 that adds supports to Mali-T860 and Mali-T880 GPU. These open source drivers are available for Android and Linux, and also support early Mali-T700 and T600 GPUs.

Separately, the company has also released Mali-T76X GPU drivers for Firefly board powered by Rockchip RK3288 quad core Cortex A17 processor featuring a Mali-T764 GPU. The first release only supports the framebuffer driver, but ARM is expecting to be able to release the X11 version in the next release (r5p1) planned at the end of March, which means some Linux desktop graphics accelerated will soon be available on Rockchip RK3288, and not only some OpenGL ES 3.0 demos on the framebuffer. The latest release (r5p0-06rel0) also supports Exynos powered Arndale Octa board, Samsung Chromebook 2, Arndale board, and Samsung Chromebook. According to an ARM representative, Rockchip also plans to release their own Linux GPU drivers targeting “TopMetal” hardware platform (should probably read PopMetal).

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

ARM Unveils Cortex A72 Processor and Mali-T880 GPU

February 4th, 2015 5 comments

ARM has just announced their new Cortex A72 ARMv8 core with 3.5 times the performance of Cortex A15 ARMv7 cores, together with Mali-T880 GPU delivering 1.8 times the performance of  Mali-T760, and CoreLink CCI-500 Cache Coherent Interconnect to link the new CPU, GPU and I/Os together.

ARM Cortex A72

Cortex-A72Some of the key features of the new core include:

  • Architecture – ARMv8-A
  • Multicore – 1-4x SMP within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
  • ISA Support
    • AArch32 for full backward compatibility with ARMv7
    • AArch64 for 64-bit support and new architectural features
    • TrustZone security technology
    • NEON Advanced SIMD
    • DSP & SIMD extensions
    • VFPv4 Floating point
    • Hardware virtualization support
  • Cache – 48KB I-cache, 32KB D-cache, and 512 KB to 2MB L2 cache with ECC
  • Debug & Trace – CoreSight DK-A57
  • Process – 16nm FinFET

A cluster can support up to 4 Cortex A72 cores clocked up to 2.5 GHz in mobile devices and higher frequencies for larger form factor devices such as servers. Cortex A72 cores may also be combined with low power Cortex A53 cores in big.LITTLE configuration for power efficient SoCs.

Cortex_A72_Performance

Relative Performance – Cortex A15 vs Cortex A57 vs Cortex A72

ARM also claims 75% power usage reduction in typical mobile workloads thanks to the new 16nm FinFET manufacturing processor. Expected applications include premium smartphones, larger screen mobile devices, enterprise networking, servers, wireless infrastructure, digital TV, and automotive ADAS/IVAI.

ARM Mali-T880 GPU

Mali-T880_GPUTechnical specifications for Mali-T880 GPU:

  • Anti-Aliasing – 4x MSAA, 8x MSAA, 16x MSAA
  • API Support
    • OpenGL ES 1.1, 1.2, 2.0, 3.0, 3.1
    • OpenCL 1.1, 1.2
    • DirectX 11 FL11_2
    • RenderScript
  • Bus Interface – AMBA4, ACE-LITE
  • L2 Cache – 256 to 2048KB (256 to 512KB for every 4 shader cores
  • Memory System – Virtual Memory with built-in Memory Management Unit (MMU)
  • Multi-Core Scaling – 1 to 16 cores
  • Adaptive Scalable Texture Compression (ATSC) – Low dynamic range (LDR) and high dynamic range (HDR) for 2D and 3D images
  • ARM Frame Buffer Compression (AFBC) – 4×4 pixel block size (lossless image compression format)
  • Transaction Elimination – 16×16 pixel block size (Only performs a partial update to the frame buffer with the changed pixel blocks)
  • Smart Composition – 16×16 pixel block size (Identical pixel blocks of input surfaces are not read, not processed for composition and not written to final frame buffer)

The GPU is also manufactured with 16nm FinFET process. Mali-T880MP16 can be clocked up to 850 MHz, and outputs up to 1700 million triangles per second, and 13.6 gigapixels per second. That’s 1.8 times better performance than Mali-T760, and ARM also claims 40% more energy efficiency.

ARM Cortex A75 processor, Mali-T880 GPU, CoreLink-C500 cache coherent interconnect, Mali-DP550 display processor unit, and  Mali-V550 video processor can be combined to create SoCs support 4K video output, and decoding up to 120 fps.

Ten partners have already become licensees including Rockchip, Mediatek, and HiSilicon, and products are expected in (early) 2016. Further details may be found on ARM’s Cortex A72 and Mali-T880 product pages.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

FOSDEM 2015 Schedule – January 31 – February 1 2015

January 29th, 2015 8 comments

FOSDEM (Free and Open Source Software Developers’ European Meeting) takes place every year during the first week-end of February. This year the developer-oriented event expects to bring over 5000 geeks to share ideas and collaborate on open source projects. Contrary to most other events, it’s free to attend, and you don’t even need to register, just show up. FOSDEM 2015 will take place on January 31- February 1 in Brussels.

Fosdem_2015There will be 551 sessions divided into 5 keynotes, 40 lightning talks, 6 certification exams, and with the bulk being developer rooms and main tracks,  divided into 7 main tracks this year: Languages, Performance, Time, Typesetting, Hardware, Security and Miscellaneous.

I’m not going to attend, but it’s still interested to see what will be talked about, and I’ve concocted my own little virtual program out of the main tracks and developers’ rooms. There’s a few minutes overlap between some talks on Sunday.. Oh well.

If you won’t be able to attend, you should be able to watch the video and access the slides in a few weeks, as most sessions will be recorded.

What is the current status of Allwinner support in upstream u-boot and the kernel, which SoCs are supported, and which features (sound, video, etc.) are supported ?

The linux-sunxi community has been slowly but steadily working on getting Allwinner SoCs like the A10 supported in upstream u-boot and the kernel.

This talk will present the current status of Allwinner support upstream. Which SoCs are supported and which ones are not (yet) supported ? Which blocks if the supported SoCs are supported, and which are not ? Why are some SoCs / blocks not supported, and what are the plans to get them supported ? This are some of the questions this talk tries to answer.

Not all free operating systems are feature-full POSIX systems. FreeRTOS is a minimal operating system which is designed to run on micro-controllers, and provide real-time scheduling. It is used in industrial automation and automotive.

A brief introduction to FreeRTOS, depending on audience preference, will be followed by either a hands-on workshop using PCs, or a demonstration on a board. The workshop includes how to get started, what can be done with it, and what type of features and pitfalls to expect from FreeRTOS.

As ADAS and infotainment require more electronics, using an hypervisor is a solution to gather multiple boards into one. Xvisor is an open source lightweight hypervisor for embedded systems that perfectly fits the needs of the automative industry. It is a complete monolithic type-1 hypervisor with full virtualization and paravirtualisation support, showing better performances than KVM. We, OpenWide and the Institute for Technological Research SystemX, are working on its port on i.MX6 boards.

F*watch is an infinitely hackable GPS watch with many sensors based on a 100% Free design. Everything is Free, from the PCB and watch housing design to the software stack. Moreover, only Free software tools have been used during the development.

F*watch. Why should your watch be different?

The talk describes the development process and shows a first prototype, along with performance measurements and future plans.

The lowRISC project was established in the summer of 2014 with the aim of producing a complete open-source System-on-Chip in volume, with low-cost development boards. Alex Bradbury, one of the co-founders of the project will discuss the progress to date and the path to the first test chip. lowRISC implements the open RISC-V instruction set architecture and is exploring ideas on improving security via tagged memory and increasing flexibility through the addition of RISC-V ‘Minion’ cores to implement soft peripherals. This talk will discuss the potential benefits of a fully open-source hardware ecosystem, the challenges of getting to first silicon, and how the open source community at large can help.

Digital cameras provide almost every feature you could want. But if they don’t, you are forced to upgrade or go without. CHDK is a project which allows you to program new functionality to the majority of Canon cameras, in either C, Lua, or Basic. The talk features background on the project, code, tools, and the methods of compiling and introducing a new firmware into the camera.

Over the course of 1 hour, Steven Goodwin will guide the audience through the entire process of taking a normal (proprietary) camera and converting it into an open source version by installing custom firmware on it. He will then cover some of the features available (such as the on-device scripting language) and continue by explaining how to build and debug your own functionality. Starting with simple grids, continuing with games, and time-lapse code. And ending with a fully recompiled firmware running on the device.

The video4linux kernel subsystem reports which colorspace the captured video uses. But what does that really mean, and what do you have to do to correctly reproduce those colors? This talk will dive into the crazy world of colorspaces and give you a practical guide to colorspace handling. I will also demonstrate colorspace handling, both right and wrong.

Kernel profiling tools status on ARM and ARM64: – perf status, – ARM and ARM64 support, – callchain unwinding mechanisms and support, – patches status: merged, pending, in development, – links to discussions (LKML) and patches.

The profiling tools in the kernel are changing at a fast pace. This talk is about the support for ARM and ARM64 architecture and the development of features for these architectures, namely the callchain unwinding. The presentation goes over: – the detailed description of the feature, – the methods used to do the callchain unwinding (fp, exidx, dwarf etc.), – the status of the on-going patches, – the remaining work to be done, – the links to patches, discussions on the mailing lists, – -if needed and if time allows- a demo of the feature.

Building a medical device requires to follow certain rules specially when health care depend on it. The presentation will explain how Yocto help us in Kaptalia to solve this issue. In particular we will focus on fast boot, update with unskilled user base, Bluetooth Low Energy, security and data privacy.

During this event we will show how our team succeeded to build our first OS, start from a company with medical expert only and no prior expertise on embedded systems. At the end, a live demonstration for using the the monitor and sensor will be held.

LAVA is a python service created by Linaro for testing software on hardware which accepts test jobs to perform on selected hardware to provide a black box to continuous integration tests. Bisecting is a technique for finding commit in version control system that broke the software. Git provides the powerful “git bisect” subcommand for this purposes. In this talk we give and introduction to LAVA and explain howto combine LAVA and git bisect to automatically find offending commits in the Linux kernel.

Prospero Technologies has made a Linux based Digital Video Recorder which constantly records all UK broadcast TV so that the consumer no longer needs to schedule recordings. This will be a talk on the technologies used to achieve this, the open source software on the consumer device and how you can build your own 30 channel DVR.

The final version of the DVR uses a Freescale i.MX6 CPU with a video processing unit running a Linux built with Yocto. The talk will cover how well this is supported by gstreamer and how we built a QT application to display our HTML5 interface.

More and more embedded projects require support for advance connectivity. With it, comes the requirement to enforce a better security as well as private data protection. Using the layer model of Yocto, we show how we can extract from a complex project such as Tizen, advance connectivity and security and apply it to any embedded project.

The Internet of Things (IoT) is growing fast and opens large opportunities to embedded Linux. Unfortunately traditional embedded Linux has been weak when it comes to security and complex connectivity enabling. Tizen which has been developed as a Linux base OS for connected object (phone, TV, car) is on the other side very well equipped in that area. We will start by explaining what is Tizen architecture and how it provides Security and Connectivity facilities on top of a base Linux. We will then show how Yocto and Tizen-meta can be used to create embedded devices which benefit from several years of work done by the Tizen community. In particular we will review : – the mandatory access control enabling in an embedded device – the enforcement of good behavior by applications – resource access control – connectivity layers – HTML5 App enabling. – multi user mode enabling.

The ARM LLVM backend has been around for many years and generates high quality code, yet there are still standard benchmarks where GCC is generating more efficient code than LLVM. The goal of this talk is to get a better understanding of why the GCC-generated code for those benchmarks is executing more efficiently and also about finding out what we need to do on the LLVM side to address those code generation deficiencies. This talk presents current performance numbers for the SPEC CPU benchmark suites on ARM, comparing the performance of LLVM and GCC, with the main focus on the SPEC CPU integer benchmarks. To dive a little bit deeper, we will also have a closer look at the generated assembly code of selected benchmarks where LLVM is performing worse than GCC and use the results of this performance analysis to point out potential code generation opportunities for LLVM.

Connectivity is crucial for Internet of Things concept. For moving devices like position data loggers is typical solution GSM network. I will show you how you can use different types of GSM network for your IoT projects.

GSM network is easy way how to connect almost any device to internet. There are lot of GSM modules on market from different vendors but all devices has one thing in common – AT commands. There is standardized AT commands set for GSM networks. Using AT command you can send text messages, read phone number from list on SIM card, connect to internet and much more. I will show you basic command set for HTTP communication using basic GSM module SIM900 and Arduino.

This talk will give an overview over the Linux backports project and how to use it. The Linux backports project makes it possible to use a driver from a recent Linux mainline kernel with an older kernel version.

When you have a vendor board support package which does not use a bleeding edge mainline kernel, like it is the case most times, but you want to use some driver from a bleeding edge Linux kernel you can use backports. Backports “automatically” generates a tar with many drivers from a specific Linux mainline kernel which can be used with older kernel versions.

In this talk I will describe how the backports project, with its compatibility layer, the spatches and the normal patches. For practical usage I will show how to use backports with your own kernel in addition I will give a brief overview on how to add a new driver to backports.

Patchwork is a toolkit for connecting various devices into a network of things or, in a more broad case – Internet of Things (IoT). The main goal of creating this toolkit is to have a lightweight set of components that can help to quickly integrate different devices (i.e. Arduino, Raspberry Pi, Plugwise, etc) into a smart environment and expose specific devices’ capabilities as RESTful/SOAP/CoAP/MQTT/etc services and data streams.

The key features of patchwork include:

  • Lightweight (no RAM-consuming sliced pie of Java and OSGi, only bare necessities)
  • Cross-platform (can be deployed on OSX/Linux/Windows, tested on Raspberry Pi and BeagleBone Black boards)
  • Language-agnostic (device agents can be written in any programming language, APIs can be consumed by app written in any programming language)
  • Easily deployable (no JARs, no Eggs or Wheels for the core components, just a single native binary with statically linked dependencies)
  • Easily extendable (integrate new devices without modification of the core components, drop in solution)
  • Interchangeable (not happy with current existing Device Gateway or Catalog? replace it with another implementation without breaking the infrastructure)
  • Not re-inventing the wheel (we re-use as many existing technologies and components as possible)

libcurl is the world’s most used and most popular Internet transfer library, already used in every imaginable sort of embedded device out there. How did this happen and how do you use libcurl to transfer data to or from your device?

Embedded devices are very often network connected these days. Network connected embedded devices often need to transfer data to and from them as clients, using one or more of the popular internet protocols.

Daniel once founded the project and is still lead developer and maintainer of the curl project, making curl and libcurl. He is also active within IETF and maintain several other open source projects. Daniel is employed by Mozilla.

This presentation will reveal the process of porting Tizen:Common to open source hardware developer boards with SoC manufactured by Allwinner, Rockchip or Intel such as OLinuXino, Radxa Rock, Minnowboard. The following topics will be covered:

  • Building Tizen ARMv7 and x86 images from scratch
  • Adapting the Linux kernel, bootloader and Tizen:Common to popular single board computers
  • Do it yourself (DIY) open-source hardware Tizen tablet or laptop
  • Sharing knowledge and experience of the community.
The presentation will also provide information about U-Boot, Yocto project, the Linux-Sunxi and Linux-Rockchip, Minnowboard communities.

Although Tegra K1 uses the same Kepler architecture as NVIDIA desktop cards that Nouveau already supports, there are other challenges that need to be addressed before Nouveau can drive K1’s graphic acceleration: the fact that the GPU does not reside on the PCI bus requires architectural changes in the Nouveau core. The absence of dedicated GPU memory directly interferes with the way Nouveau is used to do memory management and leads to potentially sub-optimal behavior. Also, in a system where all devices share the same system memory, PRIME support is mandatory to perform any useful work and the relevance of a driver-agnostic memory allocator becomes perceptible.

This talk will discuss these challenges, and in particular the consequences of using a unified memory architecture, in the hope of triggering discussions that will help improving the general support of GPU architectures for new mobile platforms.

A brief look at the past, present, and future of the KiCad project. The discussion will be primarily on what near and long term future development is planned for the project as well as discussing the potential for collaboration with other EDA projects.

Yocto has an alleged steep learning curve. It can be a challenge for modules and evaluation board manufacturers to add support for their devices in Yocto as they don’t necessarily have a software background. This talk will highlight the steps required, techniques and good practices to create a well integrated machine configuration allowing to build images using the Yocto Linux build system. The Crystalfontz support from meta-fsl-arm-extra will be used to illustrate the talk.

The bitbox console is a small open hardware & open source game console. I will present the rationale behind it and the current status of the project, detail the hardware conception and particularly video signal generation from a cortex-m4 chip with no video subsystem. I will then proceed to show the different elements of the software stack : kernel, video engines, the boot loader and, finally, current programs and games, including a Gameboy emulator and a full motion video player.

If you want to build your own schedule before going, you can check the full list of events by subjects, but an easier way to organize your day is to check the sessions in chronological order, by checking out Saturday and Sunday schedules.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter