eLinux.org - User contributions [en]

ELCE Europe 2012 Presentations

2012-11-09T16:44:41Z

Kaa-ching: added PDF Klaas van Gend

Presenters, Demo-ers, Participants:
Thanks very much for your participation in Linux Foundation's [https://events.linuxfoundation.org/events/embedded-linux-conference-europe Embedded Linux Conference Europe 2012].

This page is for collecting the presentations that were made at the conference. During and
after the conference we will collect materials from the presenters and place them here.
Please watch this page if you are interested in a particular presentation - and if it
doesn't show up, please [[Special:EmailUser/Wmat | send me and email]] and we'll try to track it down.

== Videos ==

Usually appear a month or so after the conference ends.

== Instructions ==
'''Presenters:''' Please post your technical conference presentations on this page.
(See Instructions below the tables)

= Table of Presentations =

NOTE: If you add a wikilink to your presentation and attempt to upload it via the link, it may fail. If it does, use the [[Special:Upload]] page to upload your file.

== Keynotes ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Keynotes'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
| Mark Shuttleworth, Founder at Canonical
| Advancing the User Experience
| -
|-
| Dave Engberg, CTO Evernote
| Why Evernote Runs Their Own Linux Servers Instead of "The Cloud"
| -
|-
| Brian Stevens, CTO and VP Worldwide Engineering at Red Hat
|
|
|-
| Jonathan Corbet, Editor at LWN
| The Kernel Report
|
|-
| Matt Locke, Texas Instruments
| [[Session:Are we headed for a complexity apocalypse for embedded SoCs ELCE 2012|Are we headed for a complexity apocalypse for embedded SoCs]]
|
|-
| Catarina Mota, Founder at openMaterials
| [[Session:Research into open hardware ELCE 2012|Research into open hardware]]
|
|-
| Linux Creator Linus Torvalds and Intel's Open Source Technologist, Dirk Hohndel
| [[Session:Linux where are we going ELCE 2012|Linux: Where are we going?]]
|
|}

<br />

== Presenters ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Presentations'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 10:10am
|-
| Matt Ranostay
| Beaglebone: The Perfect Telemetry Platform?
| [[Media:Beaglebone_Telemetry-_E-ELC_2012.pdf|PDF]]
|-
| Jim Huang, 0xlab
| Implement Checkpointing for Android
| [[Media:placeholder.pdf|PDF]]
|-
| Wolfram Sang, Pengutronix e.K.
| Maintainer's Diary: Devicetree and Its Stumbling Blocks
| [[Media:placeholder.pdf|PDF]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 11:05am
|-
| Matthias Brugger, ISEE 2007 S.L.
| A War Story: Porting Android 4.0 to a Custom Board
| [[Media:placeholder.pdf|PDF]]
|-
| Kishon Vijay Abraham
| USB Debugging and Profiling Techniques
| [[Media:placeholder.pdf|PDF]]
|-
| Alan Ott, Signal 11 Software
| Wireless Networking with IEEE 802.15.4 and 6LoWPAN
| [[Media:placeholder.pdf|PDF]]
|
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 1:20pm
|-
| João Paulo Rechi Vita, INdT
| Bluetooth Smart devices and Low Energy support on Linux
| [[Media:placeholder.pdf|PDF]]
|-
| Peter Stuge
| OpenOCD: Hardware Debugging and More
| [[Media:placeholder.pdf|PDF]]
|-
| Alessandro Rubini
| PF_ZIO: Using Network Frames to Convey I/O Data and Meta-Data
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 2:15pm
|-
| Joo-Young Hwang, Samsung
| A New File System Designed for Flash Storage in Mobile
| [[Media:placeholder.pdf|PDF]]
|-
| Alexandre Belloni, Adeneo Embedded
| Boot Time Optimizations
| [[Media:Alexandre_Belloni_boottime_optimizations.pdf‎|PDF]]
|-
| Philipp Zabel, Pengutronix e.K.
| Modular Graphics on Embedded ARM
| [[Media:ELCE2012-Modular-Graphics-on-Embedded-ARM.pdf|PDF]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 3:30pm
|-
| Karim Yaghmour, Opersys
| Inside Android's User Interface
| [[Media:placeholder.pdf|PDF]]
|-
| Samuel Ortiz, Intel
| Near Field Communication with Linux
| [[Media:placeholder.pdf|PDF]]
|-
| Arnout Vandecappelle, Essensium/Mind
| Upgrading Without Bricking
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 6:15pm
|-
| Tim Bird, Sony Network Entertainment
| BoFs: Developer Tools and Methods: Tips & Tricks
| [[Media:placeholder.pdf|PDF]]
|-
| Nithya Ruff & Ruud Derwig
| BoFs: Is HW Availability a Gating Item for Your Software Development
| [[Media:placeholder.pdf|PDF]]
|-
| Elizabeth Flanagan, Intel
| BoFs: Yocto Project & OpenEmbedded Community
| [[Media:placeholder.pdf|PDF]]
|-
| Alexandre Belloni
| BoFs: The Need For a Fast Bootloader
| [[Media:plachoder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 10:10am
|-
| Sascha Hauer, Pengutronix e.K.
| Barebox Bootloader
| [[Media:PRE-20121108-1-Barebox.pdf|PDF]]
|-
| Benjamin Zores, Alcatel-Lucent
| Dive Into Android Networking: Adding Ethernet Connectivity
| [[Media:placeholder.pdf|PDF]]
|-
| Jiyoun Park, Samsung
| Experiences as an OEM with Development of UI Frameworks
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 11:05am
|-
| Keshava Munegowda, Texas Instruments
| FFSB and IOzone: File system Benchmarking Tools, Features and Internals
| [[Media:placeholder.pdf|PDF]]
|-
| Chris Simmonds, 2net Limited
| The End of Embedded Linux (As We Know It)
| [[Media:Csimmonds-end-of-embedded-linux.pdf‎|PDF]]
|-
| Steven Rostedt, Red Hat
| Understanding PREEMPT_RT (The Real-Time Patch)
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 1:20pm
|-
| Klaas van Gend, Vector Fabrics
| Application Parallelization for Multi-Core Android Devices
| [[Media:Application-Parallelization-Android-KlaasVanGend.pdf|PDF]]
|-
| David Anders, Texas Instruments
| Board Bringup: You, Me, and I2C
| [[Media:placeholder.pdf|PDF]]
|-
| Rama Pallala, Intel
| Linux Power Supply Charging Subsystem
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 2:15pm
|-
| Agusti Fontquerni, ISEE 2007 S.L.
| Embedded Linux RADAR Device
| [[Media:placeholder.pdf|PDF]]
|-
| Matt Porter, Texas Instruments
| What's Old Is New: A 6502-based Remote Processor
| [[Media:placeholder.pdf|PDF]]
|-
| Thomas Petazzoni, Free Electrons
| Your New ARM SoC Linux Support Check-List
| [[Media:Arm-soc-checklist.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 3:30pm
|-
| Tracey M. Erway, Intel & Nithya A. Ruff, Synopsys
| Can You Market an Open Source Project?
| [[Media:placeholder.pdf|PDF]]
|-
| Lars Knoll
| Qt on Embedded Systems
| [[Media:placeholder.pdf|PDF]]
|-
| Koen Kooi, Circuitco
| Supporting 200 Different Expansionboards: The Broken Promise of Devicetree
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 4:25pm
|-
| Wolfgang Mauerer, Siemens
| Àndroit: Real-Time for the Rest of Us
| [[Media:placeholder.pdf|PDF]]
|-
| Anna Dushistova
| Eclipse and Embedded Linux Developers: What it Can and Cannot Do For You
| [[Media:EclipseForEmbeddedLinuxDevelopers-AnnaDushistova2012.pdf|PDF]]
|-
| Dave Stewart, Intel
| Yocto Project Overview and Update
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 10:40am
|-
| Vineet Gupta, Synopsys
| ARC Linux: From a Tumbling Toddler to a Graduating Teen
| [[Media:placeholder.pdf|PDF]]
|-
| Laurent Pinchart, Ideas on Board
| DRM/KMS, FB and V4L2: How to Select a Graphics and Video API
| [[Media:placeholder.pdf|PDF]]
|-
| Frank Rowand, Sony Network Entertainment
| Practical Data Visualization
| [[Media:placeholder.pdf|PDF]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 11:35am
|-
| Marcin Juszkiewicz, Linaro
| ARM 64-Bit Bootstrapping with OpenEmbedded
| [[Media:2012-ELCE-Bootstrapping-ARM-64bit-with-OpenEmbedded.pdf|PDF]]
|-
| Wim Decroix, TPVision
| Practical Experiences With Software Crash Analysis in TV
| [[Media:placeholder.pdf|PDF]]
|-
| Mark Brown, Wolfson Microelectronics
| Regmap: The Power of Subsystems and Abstractions
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 1:50pm
|-
| Wolfgang Mauerer, Siemens
| Low-Level Linux Debugging Without Grey Beards
| [[Media:placeholder.pdf|PDF]]
|-
| Hans Verkuil, Cisco Systems
| Video4Linux: Current Status and Future Work
| [[Media:placeholder.pdf|PDF]]
|-
| Holger Behrens, Wind River
| Yocto Layer for In-Vehicle Infotainment
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 2:45pm
|-
| Tero Kristo, Texas Instruments
| Debugging Embedded Linux (Kernel) Power Management
| [[Media:placeholder.pdf|PDF]]
|-
| Martin Bis, BIS
| Real-Time Linux in Industrial Appliances
| [[Media:placeholder.pdf|PDF]]
|-
| Jens Georg, Openismus GmbH
| Rygel: Open Source DLNA, ready for Customer Products?
| [[Media:placeholder.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 3:40pm
|-
| Yoshitake Kobayashi, Toshiba
| Improvement of Scheduling Granularity for Deadline Scheduler
| [[Media:placeholder.pdf|PDF]]
|-
| Tsugikazu Shibata, NEC
| LTSI (Long-Term Stable Initiative) Status Update
| [[Media:placeholder.pdf|PDF]]
|-
| Thomas Gleixner, Linutronix
| UBI Fastmap
| [[Media:placeholder.pdf|PDF]]
|
|}

<br />

== Instructions for Presenters ==
Please create a link in the table for your presentation, copying the style of other links.
(You may need to create an account in order to edit the wiki or upload files.)

When you have created the link, click on it to upload the file containing your slides.
[[Category:ELCE]]
[[Category:2012]]
[[Category:Events]]
[[Category:Presentations]]

File:Application-Parallelization-Android-KlaasVanGend.pdf

2012-11-09T16:43:52Z

Kaa-ching:

User:Kaa-ching

2012-11-06T22:26:41Z

Kaa-ching: update

Kaa-ching is nowadays on various forums and irc the alias for Klaas van Gend.

== Origin of nickname ==

Klaas originally always used kvangend as login - until he realized that 'vangend' means catching in his native language, Dutch.

For about a day, he changed his nickname to kcatching, and then switched over to kaa-ching.
It looks better and also had some bearing on his job (At the time, he worked in the sales organization of [[MontaVista]]).

Several people already confused his new nickname to be Chinese, which of course adds to the fun.

Klaas nowadays works for [http://www.vectorfabrics.com/ Vector Fabrics], a small company based in Eindhoven, The Netherlands
that works on a tool to help parallelization of sequential C or C++ code.

== Focus in this wiki ==
Back in 2008-2009, Klaas has been spending most of his time in this wiki on the various books in the [[:Category:Books]] category.

== Activities ==
Klaas was the lead developer for the open source user land project to bring support for UMTS to Linux: [http://umtsmon.sf.net umtsmon].
If time permits, he still programs on his other open source project [http://www.the-butterfly-effect.org The Butterfly Effect], a physics computer game about cause and effect, not entirely unlike the famous "The Incredible Machine".

Klaas was a board member of the [http://www.nluug.nl NLUUG] and is one of the co-organizers of the Embedded Linux Conference Europe, nowadays merged with LinuxCon Europe.

He is famous for doing the end game.

List of Embedded Linux Presentations

2012-11-06T22:20:12Z

Kaa-ching: /* Presentation List */

Here is a list of all the embedded Linux presentations given at ELC over the years.

The purpose of this list is to provide an overview of the talks and their transcript completion status.
See the [[Video transcription project]]. This list is sorted roughly by date.

== Presentation List ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
| align="center" | '''Event'''
| align="center" | '''Presenter(s)'''
| align="center" | '''Title (linked)'''
| align="center" | '''Status'''
|-
| [Kernel Recipes Paris 2012
| David Woodhouse, Intel
| [[Session:Embedded is not special KR 2012|Embedded is not special KR 2012]]
| template made
|-
| ELC 2012
| Jonathan Corbet, LWN.net
| Keynote: [[Session:The Kernel Report ELC 2012|The Kernel Report ELC 2012]]
| template made
|-
| ELC 2012
| Mike Anderson, CTO at The PTR Group
| Keynote: [[Session:The Internet of Things|The Internet of Things]]
| in progress (23 minutes of 52 transcribed)
|-
| ELC 2012
| Pintu Kumar, Samsung
| [[Session:Controlling Linux Memory Fragmentation and Higher Order Allocation Failure: Analysis, Observations and Results|Controlling Linux Memory Fragmentation and Higher Order Allocation Failure: Analysis, Observations and Results]]
| done (missing video)
|-
| ELC EU 2012
| Matt Locke, Texas Instruments
| [[Session:Are we headed for a complexity apocalypse for embedded SoCs ELCE 2012|Are we headed for a complexity apocalypse for embedded SoCs]]
| halfway complete
|-
| ELC 2008 (Mountain View)
| Andrew Morton, Google
| [[Session:The Relationship Between kernel.org Development and the Use of Linux for Embedded Applications ELC 2008|The Relationship Between kernel.org Development and the Use of Linux for Embedded Applications]]
| template made, 4 minutes done (the famous 'submit your patches').
|-
| ELC Europe 2009 (Grenoble)
| Gregory CLEMENT, Adeneo
| [[Session:How We Got a 3D Application Booting in 5 Seconds Under Linux|How We Got a 3D Application Booting in 5 Seconds Under Linux]]
| template made
|}

== Links to presentation collection pages ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
| align="center" | '''Event'''
| align="center" | '''Presentation collection'''
| align="center" | '''Video collection'''
| align="center" | '''Session count'''
| align="center" | '''# pages created'''
| align="center" | '''# transcribed (or not available)'''
| align="cetner" | '''Status'''
|-
| ELCE 2012 (Barcelona)
| [[ELCE_Europe_2012_Presentations | ELC Europe 2012]]
| not available yet
| 57
| 0
| 0
| not started
|-
| ELC 2012 (Redwood Shores)
| [[ELC 2012 Presentations]]
| [http://free-electrons.com/blog/elc-2012-videos/ here (free-electrons)] and [http://video.linux.com/categories/2012-embedded-linux-conference here (linux foundation)]
| 54
| 2
| 1
| in-progress
|-
| ELCE 2011 (Prague)
| [[ELCE 2011 Presentations]]
| [http://free-electrons.com/blog/elce-2011-videos/ here]
| 59
| 0
| 0
| not started
|-
| ELC 2011 (San Francisco)
| [[ELC 2011 Presentations]]
| [http://free-electrons.com/blog/elc-2011-videos/ here]
| 53
| 0
| 0
| not started
|-
| ELCE 2010 (Cambridge)
| [[ELC Europe 2010 Presentations]]
| [http://free-electrons.com/blog/elce-2010-videos/ here]
| 48
| 0
| 0
| not started
|-
| ELC 2010 (San Francisco)
| [[ELC 2010 Presentations]]
| [http://free-electrons.com/blog/elc-2010-videos/ here]
| 53
| 0
| 0
| not started
|-
-----------
| ELCE 2009 (Grenoble)
| [[ELC Europe 2009 Presentations]]
| [http://free-electrons.com/blog/elce-2009-videos/ here]
| 40
| 0
| 0
| not started
|-
| ELC 2009 (San Francisco)
| [[ELC 2009 Presentations]]
| [http://free-electrons.com/blog/elc-2009-videos/ here]
| 45
| 0
| 0
| not started
|-
| ELCE 2008 (Ede, The Netherlands)
| [[ELC Europe 2008 Presentations]]
| [http://free-electrons.com/blog/elce-2008-videos/ here]
| 34
| 0
| 0
| not started
|-
| ELC 2008 (Mount View, California)
| [[ELC 2008 Presentations]]
| [http://free-electrons.com/blog/fosdem-elc-2008-videos here]
| 53
| 0
| 0
| not started
|-
| ELCE 2007 (Linz, Austria)
| [[ELC Europe 2007 Presentations]]
| [http://free-electrons.com/blog/elce-2007-videos/ here]
| 45
| 0
| 0
| not started
|-
| ELC 2007 (San Jose)
| [[ELC 2007 Presentations]]
| (no recordings made)
| 51
| 0
| 0
| not possible
|-
| ELC 2006 (San Francisco)
| [[ELC 2006 Presentations]]
| [http://free-electrons.com/blog/elc-2006-videos/ here]
| 35
| 0
| 0
| not started
|-
| CELF Worldwide Technical Conference (San Jose)
| [[Technical Conference 2005]]
| (no video recordings)
| 24
| 0
| 0
| not possible
|}

''Note: the 'completed' data in this table should be calculated from the presentation page status field''

Session:The Relationship Between kernel.org Development and the Use of Linux for Embedded Applications ELC 2008

2012-11-06T22:18:54Z

Kaa-ching: add transcript for minutes 17 and 18: don't sit on your pile of patches.

== Session Details ==
; Event : ELC 2008 (Mountain View)
; Date : April 16 2008
; Presenter : Andrew Morton
; Organization: Google
; Slides : [[Media:Morton-elc-08.ppt]]
; Video : http://free-electrons.com/pub/video/2008/elc/elc2008-andrew-morton-keynote.ogg
; Duration : 55 minutes

=== Abstract ===
Andrew will summarize the kernel.org development and decision-making processes. Special focus will be placed upon how they impact the developers of Linux for embedded products, including the economics of using a modern kernel versus staying on a frozen older kernel version, and the economics of maintaining private patchsets versus merging work back into the public kernel. For those who choose to work with the kernel.org team, Andrew will look at how that can most effectively be done. Andrew works with Linus Torvalds and other members of the Linux development community (including open source developers and distribution vendors and industry contributors) to shepherd new features and quality improvements into the Linux kernel.

=== Biography ===
Andrew has worked at Nortel Networks' R&D labs, and Digeo Interactive, a maker of digital home entertainment products. He is currently employed by Google, working fulltime on the Linux kernel. His long experience with Linux development, and experience in the embedded realm, give Andrew a unique and valuable perspective on the issues facing embedded Liux developers.

=== Notes ===
Reports on this talk are at: http://lwn.net/Articles/278647/ and http://www.linuxfordevices.com/c/a/News/Linux-kernel-maintainer-calls-for-embedded-specialist/

== Transcript ==
; Transcribed by:
; Verified by: 1 -

0:00 - 1:00:

1:00 - 2:00:

2:00 - 3:00:

3:00 - 4:00:

4:00 - 5:00:

5:00 - 6:00:

6:00 - 7:00:

7:00 - 8:00:

8:00 - 9:00:

9:00 - 10:00:

10:00 - 11:00:

11:00 - 12:00:

12:00 - 13:00:

13:00 - 14:00:

14:00 - 15:00:

15:00 - 16:00:

Over time, it will help prioritize it was work.
You help people understand what things are most beneficial to the most users as they work on the Linux kernel.

I find that a lot of people are monitoring the mailing lists, websites, release announcements and that sort of things.
Often they come to conferences and people tell me things they didn't know.
And that's bad.
I shouldn't not know anything.
If you know something that is potentially of use to the kernel, to help or guide development, tell us.
And a way to tell us, is by sending an e-mail to you-know-which-mailinglist.
Tell us what you need.
There's no way we can do it if we don't know that there's a need.

Another way in which a person can contribute to kernel.org development is to review the patches as they go past.

16:00 - 17:00:

You can help us to check if the change will not damaging to embedded in any way.
You may see a feature which is close to what you need, but it needs a few tweaks to be more useful.
Please tell us!
Reviewing the patches, checking them for correctness and suitability for your application is direct
contribution and it's not a lot of work.

"Squeaky gates get the oil" is an old English phrase in that the person who makes the most
noise, is the one that gets the most attention. I'm afraid that's how kernel work is.
There's historically been a group of people who were very good at making a lot of fuss about
for example latency on a desktop and as a consequence, quite a lot of developers and
resources have been devoted to improving the latency on desktops for multimedia applications
and games.

17:00 - 18:00:

That wouldn't have happened if the first people hadn't appeared on the mailing
list and make us look bad.
So if you want something done; come on the mailing list and make us look bad.
Chances are, it will happen.

What a secretly fruitful group embedded is.
All ### and companies making embedded products.
They tend to sit on their own pile of patches
which they think are only relevant to your own product and you maintain them
out of tree. Consequently, these patches get larger and larger and your ###
becomes older and older and it becomes harder and harder to ###.
and basically never gets merged in the mainline tree.

18:00 - 19:00:

it's quite a bit of work to make a patch to merge with the mainline tree.
I hope the main reason why people sit on their work without sending it
upstream is because it's quite a lot of work to get it upstream.
But I've also heard of companies who want to keep the patches to themselves
because they believe they will be beneficial to their competitors.

sorry, that's not a good reason.
This is an open source product.
Yes, it will potentially be some small damage if software becomes available to your
competitors, but I think you have to see that as the price of admission to use
Linux. It's an open source product, everybody else is contributing into it, you
have at least the moral, if not a legal obligation to contribute to it
yourself.

Another problem of patch hoarding is that it gets increasingly expensive over
time as you have to roll forward through kernel versions.

19:00 - 20:00:

20:00 - 21:00:

21:00 - 22:00:

22:00 - 23:00:

23:00 - 24:00:

24:00 - 25:00:

25:00 - 26:00:

26:00 - 27:00:

27:00 - 28:00:

28:00 - 29:00:

29:00 - 30:00:

30:00 - 31:00:

31:00 - 32:00:

32:00 - 33:00:

33:00 - 34:00:

34:00 - 35:00:

35:00 - 36:00:

36:00 - 37:00:

37:00 - 38:00:

38:00 - 39:00:

39:00 - 40:00:

40:00 - 41:00:

41:00 - 42:00:

42:00 - 43:00:

43:00 - 44:00:

44:00 - 45:00:

45:00 - 46:00:

46:00 - 47:00:

47:00 - 48:00:

48:00 - 49:00:

49:00 - 50:00:

50:00 - 51:00:

51:00 - 52:00:

52:00 - 53:00:

53:00 - 54:00:

54:00 - 55:00:

55:00 - 56:00:

56:00 - 57:00:

57:00 - 58:00:

58:00 - 59:00:

59:00 - 60:00:

Session:The Relationship Between kernel.org Development and the Use of Linux for Embedded Applications ELC 2008

2012-11-06T22:02:52Z

Kaa-ching: remove instructions from view.

== Session Details ==
; Event : ELC 2008 (Mountain View)
; Date : April 16 2008
; Presenter : Andrew Morton
; Organization: Google
; Slides : [[Media:Morton-elc-08.ppt]]
; Video : http://free-electrons.com/pub/video/2008/elc/elc2008-andrew-morton-keynote.ogg
; Duration : 55 minutes

=== Abstract ===
Andrew will summarize the kernel.org development and decision-making processes. Special focus will be placed upon how they impact the developers of Linux for embedded products, including the economics of using a modern kernel versus staying on a frozen older kernel version, and the economics of maintaining private patchsets versus merging work back into the public kernel. For those who choose to work with the kernel.org team, Andrew will look at how that can most effectively be done. Andrew works with Linus Torvalds and other members of the Linux development community (including open source developers and distribution vendors and industry contributors) to shepherd new features and quality improvements into the Linux kernel.

=== Biography ===
Andrew has worked at Nortel Networks' R&D labs, and Digeo Interactive, a maker of digital home entertainment products. He is currently employed by Google, working fulltime on the Linux kernel. His long experience with Linux development, and experience in the embedded realm, give Andrew a unique and valuable perspective on the issues facing embedded Liux developers.

=== Notes ===
Reports on this talk are at: http://lwn.net/Articles/278647/ and http://www.linuxfordevices.com/c/a/News/Linux-kernel-maintainer-calls-for-embedded-specialist/

== Transcript ==
; Transcribed by:
; Verified by: 1 -

0:00 - 1:00:

1:00 - 2:00:

2:00 - 3:00:

3:00 - 4:00:

4:00 - 5:00:

5:00 - 6:00:

6:00 - 7:00:

7:00 - 8:00:

8:00 - 9:00:

9:00 - 10:00:

10:00 - 11:00:

11:00 - 12:00:

12:00 - 13:00:

13:00 - 14:00:

14:00 - 15:00:

15:00 - 16:00:

Over time, it will help prioritize it was work.
You help people understand what things are most beneficial to the most users as they work on the Linux kernel.

I find that a lot of people are monitoring the mailing lists, websites, release announcements and that sort of things.
Often they come to conferences and people tell me things they didn't know.
And that's bad.
I shouldn't not know anything.
If you know something that is potentially of use to the kernel, to help or guide development, tell us.
And a way to tell us, is by sending an e-mail to you-know-which-mailinglist.
Tell us what you need.
There's no way we can do it if we don't know that there's a need.

Another way in which a person can contribute to kernel.org development is to review the patches as they go past.

16:00 - 17:00:

You can help us to check if the change will not damaging to embedded in any way.
You may see a feature which is close to what you need, but it needs a few tweaks to be more useful.
Please tell us!
Reviewing the patches, checking them for correctness and suitability for your application is direct
contribution and it's not a lot of work.

"Squeaky gates get the oil" is an old English phrase in that the person who makes the most
noise, is the one that gets the most attention. I'm afraid that's how kernel work is.
There's historically been a group of people who were very good at making a lot of fuss about
for example latency on a desktop and as a consequence, quite a lot of developers and
resources have been devoted to improving the latency on desktops for multimedia applications
and games.

17:00 - 18:00:

18:00 - 19:00:

19:00 - 20:00:

20:00 - 21:00:

21:00 - 22:00:

22:00 - 23:00:

23:00 - 24:00:

24:00 - 25:00:

25:00 - 26:00:

26:00 - 27:00:

27:00 - 28:00:

28:00 - 29:00:

29:00 - 30:00:

30:00 - 31:00:

31:00 - 32:00:

32:00 - 33:00:

33:00 - 34:00:

34:00 - 35:00:

35:00 - 36:00:

36:00 - 37:00:

37:00 - 38:00:

38:00 - 39:00:

39:00 - 40:00:

40:00 - 41:00:

41:00 - 42:00:

42:00 - 43:00:

43:00 - 44:00:

44:00 - 45:00:

45:00 - 46:00:

46:00 - 47:00:

47:00 - 48:00:

48:00 - 49:00:

49:00 - 50:00:

50:00 - 51:00:

51:00 - 52:00:

52:00 - 53:00:

53:00 - 54:00:

54:00 - 55:00:

55:00 - 56:00:

56:00 - 57:00:

57:00 - 58:00:

58:00 - 59:00:

59:00 - 60:00:

Session:The Relationship Between kernel.org Development and the Use of Linux for Embedded Applications ELC 2008

2012-11-06T22:02:18Z

Kaa-ching: add transcript for minutes 15 and 16.

''Name the page 'Session:<title>', fill in the details below, and remove this line''
== Session Details ==
; Event : ELC 2008 (Mountain View)
; Date : April 16 2008
; Presenter : Andrew Morton
; Organization: Google
; Slides : [[Media:Morton-elc-08.ppt]]
; Video : http://free-electrons.com/pub/video/2008/elc/elc2008-andrew-morton-keynote.ogg
; Duration : 55 minutes

=== Abstract ===
Andrew will summarize the kernel.org development and decision-making processes. Special focus will be placed upon how they impact the developers of Linux for embedded products, including the economics of using a modern kernel versus staying on a frozen older kernel version, and the economics of maintaining private patchsets versus merging work back into the public kernel. For those who choose to work with the kernel.org team, Andrew will look at how that can most effectively be done. Andrew works with Linus Torvalds and other members of the Linux development community (including open source developers and distribution vendors and industry contributors) to shepherd new features and quality improvements into the Linux kernel.

=== Biography ===
Andrew has worked at Nortel Networks' R&D labs, and Digeo Interactive, a maker of digital home entertainment products. He is currently employed by Google, working fulltime on the Linux kernel. His long experience with Linux development, and experience in the embedded realm, give Andrew a unique and valuable perspective on the issues facing embedded Liux developers.

=== Notes ===
Reports on this talk are at: http://lwn.net/Articles/278647/ and http://www.linuxfordevices.com/c/a/News/Linux-kernel-maintainer-calls-for-embedded-specialist/

== Transcript ==
; Transcribed by:
; Verified by: 1 -

0:00 - 1:00:

1:00 - 2:00:

2:00 - 3:00:

3:00 - 4:00:

4:00 - 5:00:

5:00 - 6:00:

6:00 - 7:00:

7:00 - 8:00:

8:00 - 9:00:

9:00 - 10:00:

10:00 - 11:00:

11:00 - 12:00:

12:00 - 13:00:

13:00 - 14:00:

14:00 - 15:00:

15:00 - 16:00:

Over time, it will help prioritize it was work.
You help people understand what things are most beneficial to the most users as they work on the Linux kernel.

I find that a lot of people are monitoring the mailing lists, websites, release announcements and that sort of things.
Often they come to conferences and people tell me things they didn't know.
And that's bad.
I shouldn't not know anything.
If you know something that is potentially of use to the kernel, to help or guide development, tell us.
And a way to tell us, is by sending an e-mail to you-know-which-mailinglist.
Tell us what you need.
There's no way we can do it if we don't know that there's a need.

Another way in which a person can contribute to kernel.org development is to review the patches as they go past.

16:00 - 17:00:

You can help us to check if the change will not damaging to embedded in any way.
You may see a feature which is close to what you need, but it needs a few tweaks to be more useful.
Please tell us!
Reviewing the patches, checking them for correctness and suitability for your application is direct
contribution and it's not a lot of work.

"Squeaky gates get the oil" is an old English phrase in that the person who makes the most
noise, is the one that gets the most attention. I'm afraid that's how kernel work is.
There's historically been a group of people who were very good at making a lot of fuss about
for example latency on a desktop and as a consequence, quite a lot of developers and
resources have been devoted to improving the latency on desktops for multimedia applications
and games.

17:00 - 18:00:

18:00 - 19:00:

19:00 - 20:00:

20:00 - 21:00:

21:00 - 22:00:

22:00 - 23:00:

23:00 - 24:00:

24:00 - 25:00:

25:00 - 26:00:

26:00 - 27:00:

27:00 - 28:00:

28:00 - 29:00:

29:00 - 30:00:

30:00 - 31:00:

31:00 - 32:00:

32:00 - 33:00:

33:00 - 34:00:

34:00 - 35:00:

35:00 - 36:00:

36:00 - 37:00:

37:00 - 38:00:

38:00 - 39:00:

39:00 - 40:00:

40:00 - 41:00:

41:00 - 42:00:

42:00 - 43:00:

43:00 - 44:00:

44:00 - 45:00:

45:00 - 46:00:

46:00 - 47:00:

47:00 - 48:00:

48:00 - 49:00:

49:00 - 50:00:

50:00 - 51:00:

51:00 - 52:00:

52:00 - 53:00:

53:00 - 54:00:

54:00 - 55:00:

55:00 - 56:00:

56:00 - 57:00:

57:00 - 58:00:

58:00 - 59:00:

59:00 - 60:00:

ELC Presentations

2012-01-13T12:04:44Z

Kaa-ching: updated ELCE part for the 2011 conference presentations

=North America=
* [[ELC_2006_Presentations]]
* [[ELC_2007_Presentations]]
* [[ELC_2008_Presentations]]
* [[ELC_2009_Presentations]]
* [[ELC_2010_Presentations]]
* [[ELC_2011_Presentations]]

=Europe=
* [[ELC Europe 2007 Presentations]]
* [[ELC Europe 2008 Presentations]]
* [[ELC Europe 2009 Presentations]]
* [[ELC Europe 2010 Presentations]]
* [[ELCE Europe 2011 Presentations]]

[[Category:ELC]]
[[Category:ELCE]]

User:Kaa-ching

2012-01-13T12:00:54Z

Kaa-ching:

Kaa-ching is nowadays on various forums and irc the alias for Klaas van Gend.

== Origin of nickname ==

Klaas originally always used kvangend as login - until he realized that 'vangend' means catching in his native language, Dutch.

For about a day, he changed his nickname to kcatching, and then switched over to kaa-ching.
It looks better and also has some bearing on his job (At the time, he worked in the sales organization of [[MontaVista]]).

Several people already confused his new nickname to be Chinese, which of course adds to the fun.

== Focus in this wiki ==
Klaas has been spending most of his time in this wiki on the various books in the [[:Category:Books]] category.

== Activities ==
Klaas is the lead developer for the open source user land project to bring support for UMTS to Linux: [http://umtsmon.sf.net umtsmon].

Professionally, he has been spending significant effort in promoting embedded Linux and more specifically real time Linux.

He also is a board member of the [http://www.nluug.nl NLUUG] and is one of the co-organizers of the Embedded Linux Conference Europe.

ELCE 2011 Presentations x

2011-11-10T14:27:20Z

Kaa-ching:

{{db-g7}}
#REDIRECT [[ELCE Europe 2011 Presentations]]

ELC Europe 2011 Presentations old

2011-11-10T14:26:43Z

Kaa-ching:

{{db-g7}}
#REDIRECT [[ELCE_2011_Presentations]]

ELCE 2011 Presentations

2011-11-10T14:22:24Z

Kaa-ching: Redirected page to ELC Europe 2011 Presentations

#REDIRECT [[ELC Europe 2011 Presentations]]

ELCE Europe 2011 Presentations

2011-11-10T14:21:36Z

Kaa-ching: moved ELCE 2011 Presentations x to ELCE Europe 2011 Presentations: This is the correct name for the page

Presenters, Demo-ers, Participants:
Thanks very much for your participation in Linux Foundation's [http://events.linuxfoundation.org/events/embedded-linux-conference-europe Embedded Linux Conference Europe 2011].

This page is for collecting the presentations that were made at the conference. During and
after the conference we will collect materials from the presenters and place them here.
Please watch this page if you are interested in a particular presentation - and if it
doesn't show up, please [[Special:EmailUser/Wmat | send me and email]] and we'll try to track it down.

== Videos ==

Once again, through the diligent work of the [http://free-electrons.com/ Free Electrons] team, all videos for ELCE2011 can be found at [http://free-electrons.com/blog/elce-2011-videos/ ELCE2011 Videos].

== Instructions ==
'''Presenters:''' Please post your technical conference presentations on this page.
(See Instructions below the tables)

= Table of Presentations =

NOTE: If you add a wikilink to your presentation and attempt to upload it via the link, it may fail. If it does, use the [[Special:Upload]] page to upload your file.

== Keynotes ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Keynotes'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
| Jim Zemlin, Executive Director of The Linux Foundation
| Imagine a World Without Linux
|
|-
| Linus Torvalds, Alan Cox, Thomas Gleixner, Paul McKenney
| Kernel Developer Panel
| No presentation.
|-
| Antti Aumo, President of Global Solutions at Ixonos
| Re-Defining the Cloud Phone
|
|-
| Dirk Hohndel, Chief Linux and Open Source Technologist at Intel
| Reflection on 20 Years of Linux
|
|-
| Jonathan Corbet, Editor at LWN
| The Kernel Report: 20th Anniversary Edition
|
|-
| Wim Coekaerts, Senior Vice President, Linux and Vistualization Engineering at Oracle
| Engineered Systems With Linux
|
|-
| Matt Jones, Vice President, GENIVI Alliance & Technical Lead - Next Generation Infotainment, Jaguar Land Rover
| Linux for In Car Infotainment
|
|}

<br />

== Presenters ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Presentations'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 10:45am
|-
| Zach Pfeffer (Linaro)
| Linaro's Android Platform
| [[Media:Linaro Android Presentation 5.pdf|PDF]]
|-
| Thomas Gleixner (Linutronix)
| Another Mile Down the RT Road
|
|-
| Jessica Zhang (Intel)
| The Yocto Project Eclipse PlugIn: An Effective IDE Environment for both Embedded Application and System Developers
| [[Media:ELCE Yocto Plugin 2011 latest.pdf|PDF]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 11:45am
|-
| Satoru Ueda (Sony/Japan OSS Promotion Forum)
| Contributing to the Community? Does your manager support you?
|
|-
| Benjamin Zores (Alcatel-Lucent)
| Embedded Linux Optimization Techniques: How Not To Be Slow
| [[Media:ELCE_2011_-_BZ_-_Embedded_Linux_Optimization_Techniques_-_How_Not_to_Be_Slow.pdf|PDF]]
|
|-
| Ohad Ben-Cohen (Texas Instruments/Wizery)
| Asymmetric Multiprocessing using VirtIO (was: "Remote Processor Messaging")
| [[Media:AMP_ELCE2011.pdf|PDF]]
|
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 2:00pm
|-
| Jeff Osier-Mixon (Intel)
| Collaborative Initiatives in Embedded Linux
| [[Media:ELCE2011-Collaborative-Initiatives.pdf|PDF]]
|-
| Karim Yaghmour (Opersys, Inc.)
| Leveraging Android's Linux Heritage
|
|-
| Pierre Tardy (Intel)
| Using pytimechart For Real World Analysis
| [[Media:elce11_tardy.pdf|PDF]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 3:00pm
|-
|-
| Arnd Bergmann (Linaro)
| Optimizations for Cheap Flash Media
|
|-
| Vitaly Wool (Sony Ericsson)
| Saving Power With Wi-Fi: How to Prolong Your Battery Life and Still Stay Connected
| [[Media:elce11_wool.odp|ODP]]
|-
| David Stewart (Intel)
| Developing Embedded Linux Devices Using the Yocto Project and What's New in 1.1
| [[Media:elce11_stewart.pdf|PDF]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 4:15pm
|-
| Tetsuyuki Kobayashi (Kyoto Micro Computer)
| Android is NOT Just "Java On Linux"
| [[Media:elce11_kobayashi.pdf|PDF]]
|-
| Thomas Petazzoni (Free Electrons)
| Using Buildroot for a Real Project
| [[Media:Using-buildroot-real-project.pdf|PDF]]
|-
| Rajesh Lal (Nokia)
| Qt Quick: The Most Advanced UI Technology for Mobile
| Talk was canceled
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 5:15pm
|-
|-
| Tim Bird (Sony)
| Status of Embedded Linux BoFs
| [[media:Status-of-Embedded-Linux-2011-10-ELCE.pdf|Status-of-Embedded-Linux-2011-10-ELCE.pdf]]
|-
| Lauro Ramos Venancio (Instituto Nokia de Technologia) & Samuel Ortiz (Intel)
| The Linux NFC Subsystem
| [[Media:elce11_venancio_ortiz.pdf|PDF]]
|-
| David Anders (Texas Instruments)
| Board BringUp: LCD and Display Interfaces
| [[media:elce-2011-anders.pdf|PDF]] [[media:elce-2011-anders.odp|ODP]] [[BoardBringupLCD|Resource Page]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 10:15am
|-
| Grant Likely (Secret Lab)
| Device Tree Status Report
|
|-
| Laurent Pinchart (Ideas on Board)
| Success Story of the Open Source Camera Stack: The Nokia N9 Case
| [[Media:elce11_pinchart.pdf|PDF]]
|-
| Avinash Mahadeva & Vishwanth Sripathy (Texas Instruments)
| SOC Power Management - Debugging and Optimization Techniques
|
|-
| Tia Cassett (Qualcomm) & Mike Chalupa (BSquare)
| Android Development with the Snapdragon Processor
|
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 11:15am
|-
| Rafael J. Wysocki (Faculty of Physics, U. Warsaw/SUSE Labs)
| Power Management Using PM Domains on SH7372
| [[Media:elce11_wysocki.pdf|PDF]]
|-
| Sascha Hauer (pengutronix e.K.)
| A Generic Clock Framework in the Kernel: Why We Need It & Why Wee Still Don't Have It
|
|-
| Ruud Derwig (Synopsys)
| Android Platform Optimizations
| [[Media:Android_Platform_Optimizations_SNPS_20111027.pdf|PDF]]
|-
| Tia Cassett & David Brown (Qualcomm)
| Kernel Development Using the Dragonboard with the Snapdragon Processor
|
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 3:00pm
|-
| Inki Dae (Samsung Electronics)
| DRM Driver Development For Embedded Systems
| [[Media:elce11_dae.pdf|PDF]]
|-
| Lorenzo Pieralisi (ARM Ltd.)
| Consolidating Linux Power Management on ARM Multiprocessor Systems
| [[Media:elce11_pieralisi.pdf|PDF]]
|-
| Thomas Petazzoni (Free Electrons)
| Using Qt For Non-Graphical Applications
| [[Media:qt-for-non-graphical-applications.pdf|PDF]]
|-
| David Anders (Texas Instruments)
| PandaBoard Workshop: Booting the PandaBoard
|
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 4:00pm
|-
| Marek Szyprowski & Kyungmin Park (Samsung)
| ARM DMA-Mapping Framework Redesign and IOMMU Integration
| [[Media:elce11_szyprowski_park.pdf|PDF]]
|-
| Keerthy Jagadeesh & Vishwanath Sripathy (Texas Instruments)
| Thermal Framework for ARM based SOCs
|
|-
| Marc Titinger (ST Microelectronics)
| Efficient JTAG-Based Linux Kernel Debugging
| [[Media:elce11_titinger.pdf|PDF]]
|-
| David Anders (Texas Instruments)
| PandaBoard Workshop: PandaBoard Expansion I/O
|
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 5:00pm
|-
| Tsugikazu Shibata (NEC & Linux Foundation Board Member)
| Toward the Long Term Stable Kernel Tree for The Embedded Industry
|
|-
| Lisko Lappalainen (MontaVista Software)
| Secure Virtualization in Automotive
|
|-
| Jeff Osier-Mixon (Intel)
| Yocto Project Community BoFs
|
|-
| Luca Coelho (Texas Instruments)
| PandaBoard Workshop: WLAN Kernel Hacking with PandaBoard
|
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 10:15am
|-
| Andrea Gallo (ST-Ericsson)
| ARM Linux Kernel Alignment & Benefits for Snowball
| [[Media:elce11_gallo.pdf|PDF]]
|-
| Liam Girdwood & Peter Ujfalusi (Texas Instruments)
| Smart Audio: Next-Generation A SoC For Smart Phones
|
|-
| Pawel Moll (ARM Ltd)
| Linux on Non-Existing SoCs
|
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 11:15am
|-
| Koen Kooi (The Angstrom Distribution)
| Integrating Systemd: Booting Userspace in Less Than 1 Second
| [[Media:elce11_koen.pdf|PDF]]
|-
| Sylvain Leroy & Philippe Thierry
| Grsecurity in Embedded Linux Used in Android
| [[Media:elce11_thierry_leroy.pdf|PDF]]
|-
| MyungJoo Ham (Samsung))
| Charger Manager: Aggregating Chargers, Fuel Gauges and Batteries
| [[Media:elce11_ham.pdf|PDF]]
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 2:30pm
|-
| Frank Rowand (Sony)
| How Linux PREEMPT_RT Works
| [[Media:elce11_rowand.pdf|PDF]]
|-
| Catalin Marinas (ARM Ltd.)
| Linux Support For the Large Physical Address Extensions
| [[Media:elce11_marinas.pdf|PDF]]
|-
| Jim Huang (0xlab)
| Build Community Android Distribution and Ensure the Quality
|
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 3:45pm
|-
|-
| Till Jaeger (JBB Rechtsanwalte)
| The Case AVM v. Cybits: The GPL and Embedded Systems
|
|-
| Darren Hart (Intel)
| Tuning Linux For Embedded Systems: When Less Is More
| [[Media:elce11_hart.pdf|PDF]]
|-
| Wolfram Sang (Pengutronix e.K.)
| Developer's Diary: It's About Time
| [[Media:elce11_sang.pdf|PDF]]
|
|}

<br />

== Workshops ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Workshops'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
| Chris Simmonds, Freelance Embedded Linux Consultant
| Workshop 1: Outside the Box: An Introduction to Embedded Linux and Hardware Interfacing Using the Snowball Board
| [[Media:Outside-the-box-elce-2011.tar.gz|tar.gz]]
|-
| Karim J. Yaghmour
| Workshop 2: Embedded Android Workshop
|
|-

|}

<br />
== Instructions for Presenters ==
Please create a link in the table for your presentation, copying the style of other links.
(You may need to create an account in order to edit the wiki or upload files.)

When you have created the link, click on it to upload the file containing your slides.
[[Category:ELCE]]
[[Category:2011]]
[[Category:Events]]
[[Category:Presentations]]

ELCE 2011 Presentations x

2011-11-10T14:21:36Z

Kaa-ching: moved ELCE 2011 Presentations x to ELCE Europe 2011 Presentations: This is the correct name for the page

#REDIRECT [[ELCE Europe 2011 Presentations]]

ELC Europe 2011 Presentations old

2011-11-10T14:18:58Z

Kaa-ching: moved ELC Europe 2011 Presentations to ELC Europe 2011 Presentations old

#REDIRECT [[ELCE_2011_Presentations]]

ELC Europe 2011 Presentations

2011-11-10T14:18:58Z

Kaa-ching: moved ELC Europe 2011 Presentations to ELC Europe 2011 Presentations old

#REDIRECT [[ELC Europe 2011 Presentations old]]

ELCE 2011 Presentations redirect

2011-11-10T14:17:12Z

Kaa-ching: moved ELCE 2011 Presentations to ELCE 2011 Presentations redirect

#REDIRECT [[ELCE 2011 Presentations x]]

ELCE 2011 Presentations

2011-11-10T14:17:12Z

Kaa-ching: moved ELCE 2011 Presentations to ELCE 2011 Presentations redirect

#REDIRECT [[ELCE 2011 Presentations redirect]]

ELCE Europe 2011 Presentations

2011-11-10T14:16:43Z

Kaa-ching: moved ELCE 2011 Presentations to ELCE 2011 Presentations x

ELCE 2011 Presentations redirect

2011-11-10T14:16:43Z

Kaa-ching: moved ELCE 2011 Presentations to ELCE 2011 Presentations x

#REDIRECT [[ELCE 2011 Presentations x]]

ELC Europe 2011 Presentations old

2011-11-10T14:14:08Z

Kaa-ching: adding redirect.

#REDIRECT [[ELCE_2011_Presentations]]

ELCE Europe 2011 Presentations

2011-11-10T14:11:12Z

Kaa-ching: adding two more categories

File:Deflate-virtualization.pdf

2010-10-28T21:21:43Z

Kaa-ching:

ELC Europe 2010 Presentations

2010-10-28T21:18:27Z

Kaa-ching: add link to slides

Presenters, Demo-ers, Participants:
Thanks very much for your participation in CELF's [http://www.embeddedlinuxconference.com/elc_europe10/index.html Embedded Linux Conference Europe 2010].

This page is for collecting the presentations that were made at the conference. During and
after the conference we will collect materials from the presenters and place them here.
Please watch this page if you are interested in a particular presentation - and it if
doesn't show up, please send me an e-mail and we'll try to track it down.

== Videos ==

Videos from the conference were recorded by [http://free-electrons.com/ Free Electrons]
These will be made available as soon as they have time to transcode them for Internet
download. An announcement will be made, and a link placed here, when these are ready.

== Instructions ==
'''Presenters:''' Please post your technical conference presentations on this page.
(See Instructions below the tables)

== Table of Presentations ==

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Keynotes'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|Ralf Baechle
|Embedded Linux - The State of the Nation
|
|-
|Ari Rauch
|The Dynamic Role of Open Linux Architectures in Today's Mobile Landscape
|
|}

<br />

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Presentations'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|Andrew Murray
|The Right Approach to Minimal Boot Times
|
|-
|Andrey Fedotov
|Linux Application in Safety-Critical Environment: A Real-Life Example
|
|-
|Anna Dushistova
|Eclipse and Embedded Linux Developers: What It Can and What It Cannot Do For You
||[[Media:EclipseForEmbeddedLinuxDevelopers-AnnaDushistova.pdf|EclipseForEmbeddedLinuxDevelopers-AnnaDushistova.pdf]]
|-
|Armijn Hemel
|Introducing the Binary Analysis Tool
||[[Media:Elce2010.odp|Elce2010.odp]]
|-
|[mailto:arnout@mind.be Arnout Vandecappelle]
|[http://www.mind.be/?page=embedded-software-testing Practical Testing of Open Source Embedded Systems]
|[[Media:Embedded_software_testing.pdf|PDF]], [[Media:Embedded_software_testing.odp|Editable (odp)]]
|-
|Arun Raghavan
|PulseAudio In The Embedded World
|
|-
|Benjamin Gaignard
|Android and GStreamer
|[[Media:Android_and_Gstreamer.ppt|Android_and_GStreamer.ppt]]
|-
|Benjamin Zores
|State of Multimedia in 2010's Embedded Linux Devices
|[[Media:State_of_Multimedia_in_2010_Embedded_Linux_Devices.pdf|State_of_Multimedia.pdf]]
|-
|Carmelo Amoroso and Rosario Contarino
|Lightweight Prelinker for Kernel Modules
|
|-
|David Anders
|Board Bringup: Methods and Utilities
|
|-
|Frank Rowand
|Identifying Embedded Real-Time Latency Issues: I-Cache and Locks
|[[Media:Rt_latency_cache_and_locks.pdf|Rt_latency_cache_and_locks.pdf]]
|-
|Grant Likely
|ARM Flattened Device Tree Status Report
|
|-
|Gustavo F. Padovan
|The Linux Bluetooth Stack
|[[Media:Bluetooth_conference.pdf | Bluetooth_stack.pdf]]
|
|-
|Hans Verkuil
|Supporting SoC Video Subsystems in Video4linux
|[[Media:SoC_and_V4L2.odp|SoC_and_V4L2.odp]]
|-
|Harald Welte
|Running your own GSM+GPRS network using OpenBSC, OsmoSGSN and OpenGGSN
|[[Media:elce2010-welte-openbsc.pdf|OpenBSC.pdf]]
|-
|Iago Toral Quiroga
|Grilo: Integrating Multimedia Content in Applications
|
|-
|Jake Edge
|Understanding Threat Models for Embedded Devices
|
|-
|Jean-Paul Saman
|Porting VLC to TI DaVinci
|
|-
|[mailto:kees-jan.dijkzeul@sioux.eu Kees-Jan Dijkzeul]
|A Gentle Introduction to Autotools
|[[Media:101028-autotools-celf.odp|slides]] - [[Media:autotools-demo-code.tgz|demo code]]
|-
|Kevin Hilman
|Runtime Power Management
|
|-
|Klaas Van Gend
|Deflating the Virtualization Hype in 3 Simple Steps
|[[Media:Deflate-virtualization.pdf|slides]]
|
|-
|Koen Kooi
|The State of OpenEmbedded and Tooling to Make Life Easier
|
|-
|Leif Lindholm
|Software Considerations When Using High-Performance Memory Systems
|
|-
|Michael Opdenacker
|Flash Filesystem Benchmarks
|
|-
|Peter Korsgaard
|Do More With Less - On Driver-less Interfacing with Embedded Devices
||[[Media:Do_more_with_less.pdf|Do_more_with_less.pdf]]
|-
|Philippe Robin
|Facilitating Open Source Development and Collaboration
|
|-
|Ray Kinsella
|Xen in Embedded Systems
|[[Media:Xen_in_Embedded_Systems.pdf|Xen_in_Embedded_Systems.pdf]]
|-
|Robert Schuster
|OpenJDK for Embedded Linux Devices
|[[Media:Cross-compiling_OpenJDK.pdf|Cross-compiling_OpenJDK.pdf]]
|-
|Robert Schwebel and Sascha Hauer
|Barebox: Booting Linux Fast and Fancy
|
|-
|Ruud Derwig and/or Mischa Jonker
|Portability Is For People Who Cannot Write New Programs - Experience with GNU, LINUX, and other Open Source on ARC Processors
|
|-
|Stefan Kost
|Meego Multimedia
|
|-
|Tim Bird
|Android System Programming - Tips and Tricks
|[[Media:Android-tips-and-tricks-2010-10.pdf|Android-tips-and-tricks-2010-10.pdf]]
|-
|Wolfram Sang
|Developer's Diary: Supporting Maintainers
|
|-
|Wookey
|YAFFS Updates
|
|-
|Yann E. Morin
|Crosstool-NG, A Cross-Toolchain Generator
|
|-
|Yoshitake Kobayashi
|Linux Kernel Acceleration for Long-term Testing
|
|}

<br />

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Short Sessions'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|John Ogness
|IPL+UBI: Flexible and Reliable with Linux as the Bootloader
|[[Media:ipl_and_ubi.pdf | ipl_and_ubi.pdf]]
|-
|Martin Michlmayr
|Adapting Debian Installer to NAS and Other Consumer Devices
|
|-
|Ravi Sankar Guntur
|A Simple Method to Detect Memory Leaks and Buffer Overruns
|[[Media:SafeMem-ELC-E-2010.pdf | SafeMem-ELC-E-2010.pdf]]
|
|-
|Vitaly Wool
|Porting Legacy Code to Linux Userspace Driver Framework
|
|-
|Will Newton
|Exploiting On-chip Memories in Embedded Linux Applications
|
|}

<br />

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Birds-of-a-Feather Sessions (BOFS)'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|David Anders - Jayabharath Goluguri
|OMAP3/4 BoF
|
|-
|Frank Scholz
|Android and Its Impact On Home Entertainment and Home Automation
|
|-
|Grant Likely
|Small Business Owners BoF
|
|}

<br />

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Tutorial workshops'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
|Chris Simmonds
|The Embedded Linux Quick Start Guide
|[[Media:linux-quick-start.tar.gz|linux-quick-start.tar.gz]]
|-
|Chris Simmonds
|What Else Can You Do with Android?
|[[Media:android-inside.tar.gz|android-inside.tar.gz]]
|}

== Instructions for Presenters ==
Please create a link in the table for your presentation, copying the style of other links or as follows:

<nowiki>[[Media:name_of_your_presentation.pdf | name_of_your_presentation.pdf]]</nowiki> Note the supported mime types on the [[Special:Upload | Upload file]] page. The latter example uses a PDF example, your file type can be different.

(You may need to create an account in order to edit the wiki or upload files.)

When you have created the link, click on it to upload the file containing your slides.

ELC Europe 2007 Presentations

2010-10-20T13:19:33Z

Kaa-ching:

== Presentations ==
{| border="1"
|- style="background-color:#c0e0e0"
| align="left" | '''Person'''
| align="left" | '''Session Description'''
| align="left" | '''Presentation'''
|-
|Francois Audeon
|Detection & Resolution of Real Time Issues Using TimeDoctor
|[[Media:Detection-of-RT-issues-with-TimeDoctor.pdf|Detection-of-RT-issues-with-TimeDoctor.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-francois-audeon-time-doctor.ogg video]
|-
|Tim Bird
|BOF: State of Embedded Linux BOF
|[[Media:ELCE-BOF_State_of_Embedded_linux.pdf|ELCE-BOF_State_of_Embedded_linux.pdf]]
|-
|Tim Bird and Satoru Ueda
|Keynote: CE Linux Forum: the Past, Present and Future
|[[Media:CE_Linux_Forum-Ueda-Bird.pdf|CE_Linux_Forum-Ueda-Bird.pdf]]
|-
|Gustavo Sverzut Barbieri
|Fancy and Fast GUIs on Embedded Devices
|[[Media:Fancy_and_Fast_GUIs_on_Embedded_Devices.pdf|Fancy_and_Fast_GUIs_on_Embedded_Devices.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-gustavo-sverzut-barbieri-fast-fancy-gui.ogg video]
|-
|Hugh Blemings
|arch/ppc, arch/powerpc and Device Trees - A Walk Through a Port
|[http://free-electrons.com/pub/video/2007/elce/elce-2007-hugh-blemings-ppc-port.ogg video]
|-
|Shane Martin Coughlan
|Free Software, Licensing and Business Processes
|[[Media:FSFE-presentation-ELCE-03-11-2007.pdf|FSFE-presentation-ELCE-03-11-2007.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-shane-martin-coughlan-fsfe.ogg video]
|-
|Carsten Emde
|Introduction to the Open Source Automation Development Lab ([http://www.osadl.org/ OSADL])
| [[Media:CELF-OSADL.pdf|CELF-OSADL.pdf]]
|-
|Jörn Engel
|Introduction to LogFS
|PDF not available [http://free-electrons.com/pub/video/2007/elce/elce-2007-jorn-engel-logfs.ogg video]
|-
|Nils Faerber
|Overview of LiPS Mission Statement, Architecture and Roadmap
|not available
|-
|Zhang Feng, Zhao Chunlei, Chen Deyong, Meng Yan
|Tutorial: Linux As Handheld Device OS in Lenovo
|not available
|-
|Harald Fernengel
|Qtopia for Developers
|not available
|-|
|Holger Freyther
|WebKit on Linux and How It Compares to Other Open Source Engines
|[[Media:ELCE2007_WebKit.pdf|ELCE2007_WebKit.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-holger-freyther-webkit.ogg video]
|-
|Thomas Gleixner
|Status Overview of Real-Time
| [http://free-electrons.com/pub/video/2007/elce/elce-2007-thomas-gleixner-realtime-status.ogg video]
|-
|Thomas Gleixner
|Kernel Summit Report
|[http://free-electrons.com/pub/video/2007/elce/elce-2007-thomas-gleixner-kernel.ogg video]
|-
|Mark Gross
|Power Management BoF
|not available
|-
|Mark Gross
|Power Management Quality of Service
|not available
|-
|Takanari Hayama
|Writing DirectFB gfxdriver For Your Embedded System
| [[Media:elce2007_directfb_gfx.pdf|elce2007_directfb_gfx.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-takanari-hayama-gfxdrivers.ogg video]
|-
|Marcel Holtmann
|Integration of Bluetooth in Embedded Devices
|not available
|-
|Alexey Korolev
|Improving JFFS2 RAM Usage and Performance
|[[Media:ELC-E-JFFS2_RAM_Usage_impr.ppt]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-alexey-korolev-improving-jffs2.ogg video]
|-
|Matthew Locke
|OpenEmbedded for Commercial Development
|not available
|-
|Matthew Locke
|A Power Management Architecture For Mobile Devices
|[[Media:mlocke-elce2007-pmarch.pdf|mlocke-elce2007-pmarch.pdf]]
|-
|Hiroyuki Machida
|Linux for Cell/B.E. and PS3, Related Open Source Projects BoF
| [[Media:20071102-ELCE-Cell-PS3-BoF-E.pdf|20071102-ELCE-Cell-PS3-BoF-E.pdf]]
|-
|Paul Mundt
|Asymmetric NUMA: Multiple-Memory Management For The Rest of Us
| [[Media:ELCE2007-Asymmetric_NUMA.pdf|ELCE2007-Asymmetric_NUMA.pdf]]
|-
|Hadi Nahari
|Trusted Secure Isolation For Embedded Linux
|[[Media:ELC-E_SecureIsolation.pdf|ELC-E_SecureIsolation.pdf]]
|-
|Hadi Nahari
|Linux Security: Carrier Grade Moving 3G Networks Forward
|not available
|-
|Sampo Nurmentaus
|Creating Cross Platform Multimedia Applications: Case Embedding a Mozilla Based Browser
|[[Media:Sampo-Nurmentaus-Cross-Platform-Linux.pdf|Sampo-Nurmentaus-Cross-Platform-Linux.pdf]]
|-
|Michael Opdenacker
|Linux Tiny - The Diet Must Go On
|[[Media:linux-tiny.pdf|linux-tiny.pdf]]
|-
|Tsutomu Owa
|RT Patch for Celleb - Patch Status and Performance Measurements
|[[Media:ELCE2007_RTpatchForCelleb.pdf|ELCE2007_RTpatchForCelleb.pdf]]
|-
|Matt Porter
|Methods to Protect Proprietary Components in Device Drivers
|[[Media:Proprietary_Components_In_Device_Drivers.pdf|Proprietary_Components_In_Device_Drivers.pdf]]
|-
|Manas Saksena
|Fedora on ARM Platforms
|not available
|-
|Gene Sally
|How GCC Works, an Embedded Engineers Perspective
|not available
|-
|Gene Sally
|Tutorial: Getting Started with Embedded Linux
|not available
|-
|Gene Sally
|Tutorial: Using RPM as Your Build Environment
|not available
|-
|Rus Sani
|Experiences Using Linux In Carrier Grade Telecom Equipment on Control and Data Plane
|[[Media:srus_elce2007.zip]]
|-
|Frank Scholz
|[https://coherence.beebits.net Coherence], an open source DLNA/UPnP framework
|[[Media:CELF-E_2007_Coherence_slides.pdf|CELF-E_2007_Coherence_slides.pdf]]
|-
|Dodji Seketeli
|The PokyLinux Distribution: Mobile GNOME at Your Fingertips
|[[Media:poky.pdf|poky.pdf]]
|-
|Satoru Ueda and Tim Bird
|CE Linux Forum: the Past, Present and Future
| [[Media:CE_Linux_Forum-Ueda-Bird.pdf|CE_Linux_Forum-Ueda-Bird.pdf]]
|-
|Klaas de Waal
|Linux in TV, Going From Prototype To Product
|[[Media:LinuxOnTv520.pdf|LinuxOnTv520.pdf]]
|-
|Wookey
|YAFFS
|[[Media:yaffs.pdf|yaffs.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-wookey-yaffs.ogg video]
|-
|Wookey and Neil Williams
|Tutorial: Embedded Debian Workshop
|not available
|-
|Vitaly Wool
|Parallelizing Linux boot on CE Devices
|[[Media:par.pdf|par.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-vitaly-wool-parallel-boot.ogg video]
|-
|Vitaly Wool
|Linux Suspend-to-Disk Objectives for Consumer Electronic Devices
|[[Media:std.pdf|std.pdf]] [http://free-electrons.com/pub/video/2007/elce/elce-2007-vitaly-wool-suspend-to-disk.ogg video]
|-
|Siarhei Yermalayeu
|Linux Clock Management Framework
|[[Media:ELC_2007_Linux_clock_fmw.pdf|ELC_2007_Linux_clock_fmw.pdf]]
|-
|Fuxin Zhang
|A High Performance Linux-based Home Server Design
|not available
|-
|Tim Bird
|Panel: the ideal embedded Linux distribution
| [http://free-electrons.com/pub/video/2007/elce/elce-2007-panel.ogg video]
|}

[[Category:Presentations]]
[[Category:ELC Europe]]
[[Category:2007]]
[[Category:Events]]

ELC Europe 2008 Presentations

2010-10-20T13:18:47Z

Kaa-ching:

== Presentations ==
* [http://free-electrons.com/blog/elce-2008-videos/ ELCE Videos] page.

== Sessions ==

{| border="1"
|- style="background-color:#c0e0e0"
| align="left" | '''Person'''
| align="left" | '''Session Description'''
| align="left" | '''Presentation'''
|-
| Mike Anderson
|Using a JTAG in Linux Driver Debug
|[[Media:JTAG_In_Linux_Driver_Debug_Anderson.pdf|JTAG_In_Linux_Driver_Debug_Anderson.pdf]]
|-
| Mike Anderson
|Understanding and Using SMP/Multicore Processors
|[[Media:Understanding_And_Using_SMP_Multicore_Processors_Anderson.pdf|Understanding_And_Using_SMP_Multicore_Processors_Anderson.pdf]]
|-
| Gustavo Sverzut Barbieri
| Rich GUI without pain
|[[Media:Rich_GUI_without_pain.pdf|Rich_GUI_without_pain.pdf]]
|-
|Tim Bird
|Tools and Techniques for Reducing Bootup Time
|[[Media:Tools-and-techniques-for-reducing-bootup-time.pdf|Tools-and-techniques-for-reducing-bootup-time.pdf]] [[Media:Tools-and-techniques-for-reducing-bootup-time.ppt|Tools-and-techniques-for-reducing-bootup-time.ppt]]
|-
| Vitaly Bordug
| Device tree and Embedded Linux
|[[Media:vitb-ELCE-2008-presentation.pdf|vitb-ELCE-2008-presentation.pdf]]
|-
| Andrew Christian
| Handhelds Mojo - Building and Running Ubuntu Distributions on ARM
| not available
|-
| Shane Coughlan
| Strategic Implementation of Free Software in Business
| [[Media:shane-coughlan-presentation-ELCE-07-11-2008.odp|shane-coughlan-presentation-ELCE-07-11-2008.odp]]
|-
| Jake Edge
|Avoiding Web Application Flaws In Embedded Devices
|[[Media:elce-2008.pdf|elce-2008.pdf]] [[Media:elce-2008.odp|elce-2008.odp]] [http://lwn.net/talks/elce2008 LWN page]
|-
| Bas Engel
| Digital TV with Linux
|[[Media:Digital_Television_With_Linux.pdf|Digital_Television_With_Linux.pdf]]
|-
| George France, Brian Avery, & Andrew Christian
| Handhelds Mojo: Building and running Ubuntu distributions on ARM
| [[Media:Mojo_CELF_Nov2008.pdf|Mojo_CELF_Nov2008.pdf]]
|-
| Klaas van Gend & Ned Miljevic
| Building Embedded Userlands
| [[Media:ELCE2008-Building_embedded_user_lands.vGend.Miljevic.pdf|ELCE2008-Building_embedded_user_lands.vGend.Miljevic.pdf]]
|-
| Klaas van Gend
| The ELC Europe 2008 end game: Linux Fortunes
| [http://www.opentux.nl/talks/elce2008/ Opentux page]
|-
| Peter Griffin
| Porting uClinux to a new architecture
| [[Media:Porting_uClinux_CELF2008_Griffin.pdf|Porting_uClinux_CELF2008_Griffin.pdf]]
|-
| Armijn Hemel
| Abusing Universal Plug and Play
| [[Media:elce-presentatie.pdf|elce-presentatie.pdf]]
|-
| Marcel Holtmann
| BlueZ 4.0
| not available
|-
| Perry Ismangil & Benny Prijono
| PJSIP: Open Source Compact SIP and Media Stack
|[[Media:pjsip_at_Embedded_Linux_Conference_Europe_2008.pdf|pjsip_at_Embedded_Linux_Conference_Europe_2008.pdf]]
|-
| Mischa Jonker
| Power management on an ARM11 platform
|[[Media:MischaJonker_ARM11_power_management_CELF_ELC_2008.pdf|MischaJonker_ARM11_power_management_CELF_ELC_2008.pdf]]
|-
| Denis Oliver Kropp
| Open Integration Layer - DirectFB 2.0
| not available
|-
| Jaya Kumar
| Deferred IO and E-Paper Display
|[[Media:E_paper_Displays.pdf|E_paper_Displays.pdf]]
|-
| Vasileios Laganakos
|Portability and Optimizations of GNU Applications for ARM Embedded Linux
|[[Media:ARM_EmbeddedLinux_Apps_Port.pdf|ARM_EmbeddedLinux_Apps_Port.pdf]]
|-
| Philip Lougher
| Overview of SquashFS filesystem
|[[Media:squashfs-elce.pdf|squashfs-elce.pdf]]
|-
| Eugeny S. Mints
| Taking Linux Power Management to Production Quality
| not available
|-
| Denis Mishin
| A Corner-to-Corner Approach for Cost-Effective Implementation of Consumer Electronics Human Machine Interfaces
| not available
|-
| Michael Opdenacker
| Update on filesystems for flash storage
|[[Media:flash-filesystems.pdf|flash-filesystems.pdf]] [[Media:flash-filesystems.odp|flash-filesystems.odp]]
|-
| Thomas Petazzoni
|Choosing embedded graphical libraries
|[[Media:choosing-embedded-graphical-libraries.pdf|choosing-embedded-graphical-libraries.pdf]] [[Media:choosing-embedded-graphical-libraries.odp|choosing-embedded-graphical-libraries.odp]]
|-
| Gregers Petersen
| Embedded Magic, or How People Suddenly Find Out That They Are Collaborating (Some Thoughts Parsed Through the Brain of an Anthropologist)
| not available
|-
| Matt Porter
| Managing NAND Flash to Optimize Product Longevity
|[[Media:managing_nand_flash_elce.pdf|managing_nand_flash_elce.pdf]]
|-
| Bill Roman
| Using Appropriate Wear-leveling to Extend Product Lifespan
| [[Media:Datalight_ELC_Presentation_6_Nov_2008.pdf|Datalight_ELC_Presentation_6_Nov_2008.pdf]]
|-
| Frank Rowand
| Adventures in real-time performance tuning, part 1
|[[Media:adventures_in_real_time_performance_tuning_part_1-no_hidden.pdf|adventures_in_real_time_performance_tuning_part_1-no_hidden.pdf]]
|-
| Frank Rowand
| Adventures in real-time performance tuning, part 2
|[[Media:adventures_in_real_time_performance_tuning_part_2-no_hidden.pdf|adventures_in_real_time_performance_tuning_part_2-no_hidden.pdf]]
|-
| Frank Scholz
| Building bridges - coherence, a DLNA/UPnP framework
| not available
|-
| David Woodhouse
| Community and Embedded Linux
|[[Media:dwmw2-community_and_embedded_linux.pdf|dwmw2-community_and_embedded_linux.pdf]]
|-
| Wookey
| Solar hot water geekery: making infinitely versatile home heating controllers with free software and open hardware
| [[Media:hotwaterballoon-CELF2008.pdf|hotwaterballoon-CELF2008.pdf]] [[Media:hotwaterballoon-CELF2008.tar.gz|src.tgz]]
|-
| Vitaly Wool
| Using "Dot Clock" Displays In Embedded Linux Devices
| [[Media:dotclock.pdf|dotclock.pdf]] [[Media:dotclock.odp|dotclock.odp]]
|-
| Vitaly Wool
| NAND Chip Driver Optimizaton and Tuning
| [[Media:nand_opt.pdf|nand_opt.pdf]], [[Media:nand_opt.odp|nand_opt.odp]]
|}

[[Category:Presentations]]
[[Category:ELC Europe]]
[[Category:2008]]
[[Category:Events]]

ELC Europe 2009 Presentations

2010-10-20T13:17:58Z

Kaa-ching:

[[Category:ELC Europe]]
[[Category:Presentations]]
[[Category:2009]]
[[Category:Events]]

Videos of most talks are available at: [http://free-electrons.com/blog/elce-2009-videos/ Free Electrons ELCE 2009]

== Presentations ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Keynotes and Panel'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
| Jon Masters
| Porting Linux
| [[Media:Masters-PortingLinux.odp|Masters-PortingLinux.odp]] [[Media:Masters-PortingLinux.pdf|Masters-PortingLinux.pdf]]
|-
| Philippe Gerum
| State of Real-Time Linux: Don't Stop Until History Follows
| [[Media:gerum-elce-09.odp|gerum-elce-09.odp]] [[Media:gerum-elce-09.pdf|gerum-elce-09.pdf]]
|}

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Sessions'''
|- bgcolor="#c0e0e0"
| align="center" | '''Session Presenter(s)'''
| align="center" | '''Presentation'''
| align="center" | '''File Links'''
|-
| Carmelo Amoroso
| LKM Fast Loader Based on ELF Hash Table
| [[Media:C_AMOROSO_Fast_lkm_loader_ELC-E_2009.pdf|C_AMOROSO_Fast_lkm_loader_ELC-E_2009.pdf]]
|-
| Jean-Pierre André, Szabolcs Szakacsits
| Unexpected Emergence of Wide Use of NTFS in CE Devices
| [[Media:andre-NTFS3G.pdf|andre-NTFS3G.pdf]] [[Media:Andre-NTFS3G.ppt|Andre-NTFS3G.ppt]]
|-
| Gustavo Sverzut Barbieri
| Canola Application and Framework for Rich GUI
| [[Media:GustavoSverzutBarbieri-elce2009-canola2.pdf|GustavoSverzutBarbieri-elce2009-canola2.pdf]]
|-
| Patrick Bellasi
| Constrained Power Management
| [[Media:Bellasi-ConstrainedPowerManagement.pdf|Bellasi-ConstrainedPowerManagement.pdf]]
|-
| Gilad Ben-Yossef
| The Good, The Bad and Ugly: On Threads, Processes and Co-Processes
| [[Media:Ben-Yossef-GoodBadUgly.odp|Ben-Yossef-GoodBadUgly.odp]] [[Media:Ben-Yossef-GoodBadUgly.pdf|Ben-Yossef-GoodBadUgly.pdf]]
|-
| Tim Bird
| Analyzing Kernel Function Execution with Ftrace
| [[Media:Bird-Ftrace.pdf|Bird-Ftrace.pdf]] [[Media:Bird-Ftrace.ppt|Bird-Ftrace.ppt]]
|-
| Vladislav Buzov
| Digital TV and Application Store, Solving Security Problems
| [[Media:Buzov-SMACK.pdf|Buzov-SMACK.pdf]]
|-
| Grégory Clement
| How We Got a 3D Application Booting in 5 Seconds Under Linux
| [[Media:Clement-Boot3DApplicationIn5s.pdf|Clement-Boot3DApplicationIn5s.pdf]]
|-
| Bas Engel
| Accelerating Digital Television Innovating -- Joint SPACE Initiative
| [[Media:2009_ELC_Accelerating_Digital_Television_Innovation.pdf|2009_ELC_Accelerating_Digital_Television_Innovation.pdf]]
|-
| Florian Fainelli
| OpenWrt, as Rapid Embedded Systems Prototyping Framework
| [[Media:fainelli-openwrt-elce2009.pdf|fainelli-openwrt-elce2009.pdf]]
|-
| Pierre Ficheux
| Using QEMU for Industrial Embedded Applications
| [[Media:pficheux_elce09.pdf|pficheux_elce09.pdf]]
|-
| Adriaan de Groot
| Software Licensing - A Lot Like Programming
| [[Media:DeGroot-SoftwareLicensing.pdf|DeGroot-SoftwareLicensing.pdf]]
|-
| Sascha Hauer, Marc Kleine-Budde
| U-Boot-v2
| [[Media:Hauer-U_BootV2.pdf|Hauer-U_BootV2.pdf]]
|-
| Gordon Hecker
| e2factory - Open Source Embedded Linux Build System
| [[Media:e2factory_elc-e09.pdf|e2factory_elc-e09.pdf]]
|-
| Cedric Hombourger
| Why OpenEmbedded Proved a Good Foundation for MontaVista
| [[Media:Hombourger-Why_oe_good_foundation_for_mv.odp|Hombourger-Why_oe_good_foundation_for_mv.odp]] [[Media:Hombourger-Why_oe_good_foundation_for_mv.pdf|Hombourger-Why_oe_good_foundation_for_mv.pdf]]
|-
| Marcin Juszkiewicz
| Hacking with OpenEmbedded
| [[Media:Juszkiewicz-HackingWithOpenEmbedded.pdf|Juszkiewicz-HackingWithOpenEmbedded.pdf]]
|-
| Guennadi Liakhovetski
| Embedded Video Capture Under Linux: The Soc Camera Framework
| [[Media:soc-camera.pdf|soc-camera.pdf]]
|-
| Bruno Cardoso Lopes
| The LLVM MIPS and ARM Back-ends
| [[Media:Lopes-LLVM.pdf|Lopes-LLVM.pdf]]
|-
| Michael Opdenacker
| Update on Boot Time Reduction Techniques
| [[Media:opdenacker-boot-time.pdf|opdenacker-boot-time.pdf]] [[Media:opdenacker-boot-time.odp|opdenacker-boot-time.odp]]
|-
| Samuel Ortiz
| Linux Wifi Solutions for Mobile Platforms
| [[Media:Ortiz-elce-2009.pdf|Ortiz-elce-2009.pdf]]
|-
| Nicolas Palix, Julia Lawall, Gilles Muller
| Coccinelle: A Program Matching and Transformation Tool for Systems Code
| [[Media:Coccinelle_ELC-E_2009.odp|Coccinelle_ELC-E_2009.odp]][[Media:Coccinelle_ELC-E_2009.pdf|Coccinelle_ELC-E_2009.pdf]]
|-
| Pascal Pellet
| Linux Embedded Applications in Machine Vision
| [[Media:pascalPellet-e2vELC-E.pdf|pascalPellet-e2vELC-E.pdf]]
|-
| Matt Porter
| Mythbusters: Android
| [[Media:Mythbusters_Android.pdf|Mythbusters_Android.pdf]]
|-
| Frank Rowand
| A Survey of Linux Measurement and Diagnostic Tools
| [[Media:survey_of_linux_measurement_and_diagnostic_tools.pdf|survey_of_linux_measurement_and_diagnostic_tools.pdf]]
|-
| Alessandro Rubini
| Use of the Fast IRQ (FIQ) in ARM-Linux
| [[Media:0910-elce-fiq.pdf|0910-elce-fiq.pdf]]
|-
| Wolfram Sang
| Developer's Diary: The Device Tree
| [[Media:Sang-DiaryDeviceTree.pdf|Sang-DiaryDeviceTree.pdf]]
|-
| Stefan Schwarzer
| Disko v1.6 – An Application Framework for Embedded Devices
| TBD: legal status of 1 slide is unclear
|-
| Robert Schwebel
| Customizing Embedded Linux Systems with PTXdist
| [[Media:Schwebel-Customizing_with_PTXdist.pdf|Schwebel-Customizing_with_PTXdist.pdf]]
|-
| Jean-Marc Temmos
| Genivi Alliance : An Effort to Build a Linux-based In Vehicle Infotainement Platform
| [[Media:Temmos-GeniviVisteon.pdf|Temmos-GeniviVisteon.pdf]]
|-
| Francesco Virlinzi
| A Generic Clock Framework Implementation
| [[Media:ELC_E_2009_Generic_Clock_Framework.pdf|ELC_E_2009_Generic_Clock_Framework.pdf]]
|-
| Alex de Vries
| Technical Features and Components of Open Source Build Systems
| not available
|-
| Nina Wilner
| Porting Android to Power Architecture
| [[Media:Android_On_Power.pdf|Android_On_Power.pdf]]
|-
| Vitaly Wool
| Using Device Trees on ARM Platforms
| [[Media:vwool-device_trees_arm.odp|vwool-device_trees_arm.odp]] [[Media:vwool-device_trees_arm.pdf|vwool-device_trees_arm.pdf]]
|}

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Birds-Of-A-Feather Sessions'''
|- bgcolor="#c0e0e0"
| align="center" | '''BOF Presenter(s)'''
| align="center" | '''Presentation'''
| align="center" | '''File Links'''
|-
| Tim Bird
| Android
| [[Media:Bird-Android-BOF.pdf|Bird-Android-BOF.pdf]] [[Media:Bird-Android-BOF.ppt|Bird-Android-BOF.ppt]]
|-
| Peter Korsgaard, Thomas Petazzoni
| Buildroot
| [[Media:buildroot-bof.pdf|buildroot-bof.pdf]]
|-
| Yann E. Morin
| Building Our Own Toolchains For Our Embedded Projects: Why, and How To
| [[Media:Morin-Crosstool-NG.pdf|Morin-Crosstool-NG.pdf]] [[Media:Morin-Crosstool-NG.odp|Morin-Crosstool-NG.odp]]
|-
| Michael Opdenacker
| Small Business
| [[Media:opdenacker-small-business-bof.pdf|opdenacker-small-business-bof.pdf]] [[Media:opdenacker-small-business-bof.odp|opdenacker-small-business-bof.odp]]
|-
| Pierre Pronchery
| Hackable Devices: The New Possibilities of Open Hardware
| not available
|}

ELC Europe 2008 Presentations

2010-10-20T13:17:33Z

Kaa-ching:

ELC 2008 Presentations

2010-10-20T13:17:08Z

Kaa-ching:

== Presentations ==

* Video of the ELC 2008 keynotes and various sessions can now be viewed online at http://free-electrons.com/community/videos/conferences.
* An extensive report of this year's conference is now online at http://free-electrons.com/articles/conferences/elc2008-report.

== Keynotes ==
{| border="1"
|- style="background-color:#c0e0e0"
| align="left" | '''Person'''
| align="left" | '''Session Description'''
| align="left" | '''Presentation'''
|-
|Henry Kingman
|Tux in Lights
|[[Media:henry_kingman_welcoming_address.pdf|henry_kingman_welcoming_address.pdf]]
|-
|Andrew Morton
|The Relationship Between kernel.org Development and the Use of Linux for Embedded Applications
|[[Media:morton-elc-08.ppt|morton-elc-08.ppt]]
|-
|Tim Bird
|Status of Embedded Linux and CELF Plenary Meeting
|[[Media:Status-of-embedded-Linux-ELC2008.ppt|Status-of-embedded-Linux-ELC2008.ppt]]
|}

== Sessions ==

{| border="1"
|- style="background-color:#c0e0e0"
| align="left" | '''Person'''
| align="left" | '''Session Description'''
| align="left" | '''Presentation'''
|-
|Kate Alhola
|Maemo Mobile Linux Platform, Current Status and Future Directions
|[[Media:elc_maemo_2008.pdf|elc_maemo_2008.pdf]]
|-
|Mike Anderson
|Using a JTAG for Linux Driver Debugging
|[[Media:CELF_JTAG_Anderson.ppt|CELF_JTAG_Anderson.ppt]]
|-
|Alexander Belyakov
|Compressed Swap Solution for Embedded Linux
|[[Media:belyakov_elc2008_compressed_swap_final_ppt.pdf|belyakov_elc2008_compressed_swap_final_ppt.pdf]] [[Media:belyakov_elc2008_compressed_swap_final_doc.pdf|belyakov_elc2008_compressed_swap_final_doc.pdf]]
|-
|Hugh Blemings
|Learning Kernel Hacking from clever people
|[[Media:elc-us-2008-slides-final.pdf|elc-us-2008-slides-final.pdf]]
|-
|Andrew Christian
|Compiling Full Desktop Distributions for ARM: The Handhelds Rebuild Project
|[[Media:HandheldsMojo_ELC2008.pdf|HandheldsMojo_ELC2008.pdf]]
|-
|Felipe Contreras
|Gstreamer and OpenMAX IL: plug and play
|[[Media:gst-openmax.pdf|gst-openmax.pdf]]
|-
|Jake Edge
|Avoiding Web Application Flaws in Embedded Devices
|[http://lwn.net/talks/elc2008/ LWN Article]
|-
|Jörn Engel
|Status of LogFS
|not available
|-
|Nils Faerber
|GPE Phone Edition - An Open Source Software Stack for Linux Mobile Phones
|[[Media:gpe2-celf2008.odp|gpe2-celf2008.odp]]
|-
|Klaas van Gend
| Using Real-Time Linux
|[[Media:Using_Real-Time_Linux.KlaasVanGend.ELC2008.pdf|Using_Real-Time_Linux.KlaasVanGend.ELC2008.pdf]]
|-
|Liam Girdwood
|Every Microamp is Sacred - A Dynamic Voltage and Current Control Interface for the Linux Kernel
|[[Media:regulator-api-celf.pdf|regulator-api-celf.pdf]]
|-
|Mark Gross
| Power Management Quality of Service and How You Could Use it in Your Embedded Application
|[[Media:elc2008_pm_qos_slides.pdf|elc2008_pm_qos_slides.pdf]]
|-
|Takanari Hayama
|DirectFB Internals - Things You Need to Know to Write Your DirectFB gfxdrive
|[[Media:elc2008_directfb_gfx.pdf|elc2008_directfb_gfx.pdf]]
|-
|Seo Hee
|APCS (ARM Procedure Call Standard) Tutorial
|[[Media:CELF_APCS_Seohee_lge.pdf|CELF_APCS_Seohee_lge.pdf]]
|-
|Seo Hee
|Trouble Shooting for Blocking Problem
|not available
|-
|Kevin Hilman
|Building Blocks for Embedded Power Management
|[[Media:PM_Building_Blocks1.pdf|PM_Building_Blocks1.pdf]]
|-
|Stuart Hughes
|Roll-Your-Own Linux the Easy Way with LTIB
|[[Media:celf_ltib_bof_v1 1. pdf|celf_ltib_bof_v1 1. pdf]]
|-
|Jared Hulbert
|AXFS: Architecture and Results
|[[Media:AXFS_at_ELC_2008.ppt|AXFS_at_ELC_2008.ppt]]
|-
|Hirohisa Iijima
|Episodes of LKST for Embedded Linux Systems
|[[Media:EpisodesLKST_Lineo_CELF_ELC2008.pdf|EpisodesLKST_Lineo_CELF_ELC2008.pdf]]
|-
|YoungJun Jang
|Avoiding OOM on Embedded Linux
|[[Media:CELF_AvoidOOM.pdf|CELF_AvoidOOM.pdf]]
|-
|YungJoon Jung
|Real-Time Linux BOF
|[[Media:RT-BoF-2008-04-15.pdf|RT-BoF-2008-04-15.pdf]]
|-
|Jong-Sung Kim
|Back-tracing in MIPS-based Linux Systems
|[[Media:ELC2008 - Back-tracing in MIPS-based Linux Systems.pdf|ELC2008 - Back-tracing in MIPS-based Linux Systems.pdf]]
|-
|Min-Chan Kim, Oleksiy Kokachev
|Instant Startup for Application Using Reducing Relocation Time and Rearrange Function
|[[Media:DDLink FunctionReorder 08 04.pdf|DDLink FunctionReorder 08 04.pdf]]
|-
|KaiGai Kohei
|Recent Security Features and Issues in Embedded Systems
|[[Media:ELC2008_KaiGai.pdf|ELC2008_KaiGai.pdf]]
|-
|Jyunji Kondo
|Development of Mobile Linux Open Platform
|[[Media:Development_of_Mobile_Linux_Open_Platform.pdf|Development_of_Mobile_Linux_Open_Platform.pdf]]
|-
|Rob Landley
|Cross Compiling Linux (tutorial)
|not available
|-
|Grant Likely
|Shifting Sands: Lessons Learned from Linux on an FPGA
|[[Media:glikely--fpga-lessons-learned.pdf|glikely--fpga-lessons-learned.pdf]]
|-
|Grant Likely
|A Symphony of Flavours; Using the Device Tree to Describe Embedded Hardware
|[[Media:glikely--device-tree.pdf|glikely--device-tree.pdf]]
|-
|Matt Locke
|Building Custom Embedded Linux Distributions
|[[Media:mlocke-elc2008-oe.pdf|mlocke-elc2008-oe.pdf]]
|-
|Matt Mackall
|Kernel Size Report, and Bloatwatch Update
|[[Media:elc2008.odp|elc2008.odp]]
|-
|Guido Madaus
|Disko - An Application Framework for Digital Media Devices
|[[Media:elc.tar|elc.tar]]
|-
|David Mandala
|UME - Ubuntu Mobile and Embedded
|[[Media:UbuntuMobileEmbedded.pdf|UbuntuMobileEmbedded.pdf]]
|-
|Katsuya Matsubara, Hisao Munakata
|Using UIO on an Embedded Platform
|[[Media:uio080417celfelc08.pdf|uio080417celfelc08.pdf]]
|-
|Nicholas McGuire
|Real-Time Virtualization Solutions for Linux - A Comparison of Strategies
|not available
|-
|Yuichi Nakamura
|Development of Embedded SE Linux
|[[Media:ELC2008_nakamura.pdf|ELC2008_nakamura.pdf]]
|-
|Jeff Osier-Mixon
|Effectively Managing Documentation for Embedded Linux Projects
|[[Media:jeffrey-osier-mixon-elc.ppt|jeffrey-osier-mixon-elc.ppt]]
|-
|Kyungmin Park, Sunmi Yoo
|Filesystem Support on Multi Level Cell (MLC) Flash in Open Source
|[[Media:ELC2008 Filesystem support on Multi Level Cell flash in open source.ppt|ELC2008 Filesystem support on Multi Level Cell flash in open source.ppt]]
|-
|Thomas Petazzoni
|Linux Tiny - Penguin Weight Watchers
|[[Media:linux-tiny.pdf|linux-tiny.pdf]]
|-
|Matt Porter
|Leveraging Free and Open Source Software in a Product Development Environment
|[[Media:elc-foss.pdf|elc-foss.pdf]]
|-
|Conrad Roeber
|Enhancements to USB Gadget Framework
|[[Media:ELC2008-gadget-enhancements-web.pdf|ELC2008-gadget-enhancements-web.pdf]]
|-
|Frank Rowand
|Adventures In Real-Time Performance Tuning
|[[Media:mips_real_time.pdf|mips_real_time.pdf]]
|-
|Gene Sally
|How GCC Works, An Embedded Engineer's Perspective
|[[GCC_Tips]]
|-
|Deepak Saxena
|Appropriate Community Practices: Social and Technical Advice
|not available
|-
|Christian Schaller
|GStreamer on Embedded - Latest Developments and Features
|[[Media:celinux-mountainview-gstreamer-tim.ppt|celinux-mountainview-gstreamer-tim.ppt]]
|-
|Michael Shiloh
|OpenMoko
|not available
|-
|York Sun
|Adding Framebuffer support for Freescale SoCs
|[[Media:Adding Framebuffer support to Freescale SoCs York Sun.ppt|Adding Framebuffer support to Freescale SoCs York Sun.ppt]]
|-
|Kentaro Takeda
|How to Analyze Your Linux's Behavior with TOMOYO Linux
|[http://sourceforge.jp/projects/tomoyo/document/elc2008.pdf elc2008.pdf]
|-
|JT Thomas
|Embedded Linux Development with Eclipse
|[[Media:Embedded Linux Development with Eclipse.ppt|Embedded Linux Development with Eclipse.ppt]]
|-
|Justin Treon
|Making a Phone Call With Phase Change Memory
|[[Media:Making_a_Phone_Call_With_PCM_at_ELC_2008.ppt|Making_a_Phone_Call_With_PCM_at_ELC_2008.ppt]]
|-
|Richard Woodruff
|Linux System Power Management on OMAP3430
|[[Media:TI_OMAP3430_Linux_PM_reference.ppt|TI_OMAP3430_Linux_PM_reference.ppt]]
|}

[[Category:Presentations]]
[[Category:ELC]]
[[Category:2008]]
[[Category:Events]]

ELC 2010 Call for Presentations

2010-10-20T13:16:37Z

Kaa-ching:

The CE Linux Forum would like to invite you to make a presentation at
our upcoming Embedded Linux Conference. The conference will be held April 12-14, 2010
in San Francisco, California.

''Please see the [http://www.embeddedlinuxconference.com/elc_2010/index.html embeddedlinuxconference.com ELC 2010 web site] for more information about the conference.''

== Guidelines ==
Presentations should be of a technical nature, covering topics related to use of Linux in
embedded systems. The CE Linux Forum is focused on the use of Linux in consumer electronics
products, but presentations may cover use of Linux in other embedded areas, as long as the
topic is of general relevance to most embedded users.

Presentations that are commercial advertisements or sales pitches are not appropriate
for this conference.

Presentations on the following topics are encouraged:
* Audio, Video, and Graphics systems for embedded products
* Security
* System size
* Bootup time
* Meeting real-time constraints
* Power management
* Streaming media
* Flash memory devices and filesystems
* Build systems
* Embedded distributions
* Development tools for embedded users
* Technologies related to cell phones, digital settop boxes, televisions, cameras, handheld devices, or other CE products
* Use of Linux in actual products, practical experience and war stories
* Standards for CE products

Most presentation slots are 50 minutes long, including time for questions.

=== No paper required ===
A paper submission is NOT required in conjunction with the presentation. However,
if a paper is produced, it is requested to be published in wiki format on the
[http://elinux.org/ Embedded Linux Wiki]

=== Tutorials ===
You may also submit a request to present a tutorial. Tutorials are
intended to be longer, interactive learning sessions.
A tutorial may occupy more than one session slot at the conference.

=== Birds of a Feather (BOF) sessions ===
You may also submit a request to be the session leader for a "Birds Of A Feather" (BOF)
session. This is an informal discussion on a topic of group interest. For a BOF
proposal, please describe the topic area you would like to discuss. You should
come prepared to help move the discussion along with a "lead in" presentation (a
few slides) or some thought-provoking questions.

=== Technical Showcase (Demo) ===
Finally there will be a "poster" demo session at the event. The demo session consists of
table-top demos, with an accompanying poster describing each demo. In this session,
the demonstrator can interact with individuals or small groups, describe their work and
answer questions.

=== General Guidelines ===
We prefer presentations that have not been previously presented, but exceptions will
be made for material that is either of great interest or has been seen previously only
by a limited audience.

A single person may submit more than one proposal. However, since the number of slots is limited,
it is likely that at most one proposal from an individual will be accepted.

=== Examples from previous years ===
For examples of presentations from previous years' conferences, see:
* [http://tree.celinuxforum.org/CelfPubWiki/ELC2009Presentations ELC 2009 Presentations]
* [http://www.celinux.org/elc08_presentations/ ELC 2008 Presentations]
* [http://tree.celinuxforum.org/CelfPubWiki/ELC2007Presentations ELC 2007 Presentations]
* [http://elinux.org/ELC_2006_Presentations ELC 2006 Presentations]

For information about previous demo sessions, see the
[http://www.celinuxforum.org/CelfPubWiki/ELC2009TechnicalShowcase ELC 2009 Technical Showcase page]

== Technical Facilities ==
Presentations will be in rooms with 1024×768 XGA data projectors. Please bring your
own laptop for your presentation. Please contact us if you have further requirements.

== Reward and possible assistance ==
Speakers for presentation and tutorial sessions, as well as leaders of BoF sessions,
will receive complimentary professional registration
for the conference. That is, if you make a presentation or lead a session, you
get into the rest of the conference for free! Please note, that if a session
has multiple speakers, only the primary speaker for that session will receive
free admission.

Please note that event admission includes access to the Linux Foundation
Collaboration Summit, which is normally an invitation-only event.

Travel and accomodation assistance is available for a limited number of speakers,
under certain circumstances. Please contact the e-mail address below if you believe your
circumstances would qualify you for this assistance.

== Review Process ==
All presentation, tutorial, demo and BOF proposals will be reviewed by the ELC program committee,
and submitters will be notified of their acceptance (or not) by February 5, 2010.

Proposals will be assessed on a number of criteria:
* Is the topic of interest to embedded Linux developers?
** That is, is it relevant for using Linux in embedded products?
* Does the presentation describe something new or interesting?
* Does the topic fit with other presentations planned for the conference?
* Is source code for the project (if applicable) available now?
* May the forum publish your presentation on it's web site?

== Submission method ==
To submit a presentation proposal, send an e-mail to [mailto:elc10@tree.celinuxforum.org elc10@tree.celinuxforum.org]

A presentation proposal should include:

* the name of the presenter
* the presentation (or session) title
* a brief (one or two paragraph) description
* Also, please indicate with whether your presentation may be published by the forum on a web site, after the conference.

If you are submitting for someone else, please provide
an e-mail address for the presenter.

If your proposal is accepted, you will be requested to provide a short
paragraph describing yourself, for use in conference materials.

If you have any questions about the submission requirements,
the status of your submission, the review process, or the event itself,
please feel free to contact the program committee, at:
[mailto:elc10@tree.celinuxforum.org elc10@tree.celinuxforum.org].

== Deadlines ==
Proposals for presentations, demos and Birds-of-a-Feather
sessions must be received by January 15, 2010.

Speakers will be notified by February 5, 2010.

[[Category:Presentations]]
[[Category:ELC]]
[[Category:2010]]
[[Category:Events]]

ELC 2010 Call for Presentations

2010-10-20T13:15:44Z

Kaa-ching:

ELC Europe 2008 Presentations

2010-10-20T13:14:40Z

Kaa-ching:

ELC Europe 2009 Presentations

2010-10-20T13:14:38Z

Kaa-ching:

[[Category:ELC Europe]]
[[Category:Presentations]]
[[Category:2009]]

Videos of most talks are available at: [http://free-electrons.com/blog/elce-2009-videos/ Free Electrons ELCE 2009]

== Presentations ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Keynotes and Panel'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
| Jon Masters
| Porting Linux
| [[Media:Masters-PortingLinux.odp|Masters-PortingLinux.odp]] [[Media:Masters-PortingLinux.pdf|Masters-PortingLinux.pdf]]
|-
| Philippe Gerum
| State of Real-Time Linux: Don't Stop Until History Follows
| [[Media:gerum-elce-09.odp|gerum-elce-09.odp]] [[Media:gerum-elce-09.pdf|gerum-elce-09.pdf]]
|}

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Sessions'''
|- bgcolor="#c0e0e0"
| align="center" | '''Session Presenter(s)'''
| align="center" | '''Presentation'''
| align="center" | '''File Links'''
|-
| Carmelo Amoroso
| LKM Fast Loader Based on ELF Hash Table
| [[Media:C_AMOROSO_Fast_lkm_loader_ELC-E_2009.pdf|C_AMOROSO_Fast_lkm_loader_ELC-E_2009.pdf]]
|-
| Jean-Pierre André, Szabolcs Szakacsits
| Unexpected Emergence of Wide Use of NTFS in CE Devices
| [[Media:andre-NTFS3G.pdf|andre-NTFS3G.pdf]] [[Media:Andre-NTFS3G.ppt|Andre-NTFS3G.ppt]]
|-
| Gustavo Sverzut Barbieri
| Canola Application and Framework for Rich GUI
| [[Media:GustavoSverzutBarbieri-elce2009-canola2.pdf|GustavoSverzutBarbieri-elce2009-canola2.pdf]]
|-
| Patrick Bellasi
| Constrained Power Management
| [[Media:Bellasi-ConstrainedPowerManagement.pdf|Bellasi-ConstrainedPowerManagement.pdf]]
|-
| Gilad Ben-Yossef
| The Good, The Bad and Ugly: On Threads, Processes and Co-Processes
| [[Media:Ben-Yossef-GoodBadUgly.odp|Ben-Yossef-GoodBadUgly.odp]] [[Media:Ben-Yossef-GoodBadUgly.pdf|Ben-Yossef-GoodBadUgly.pdf]]
|-
| Tim Bird
| Analyzing Kernel Function Execution with Ftrace
| [[Media:Bird-Ftrace.pdf|Bird-Ftrace.pdf]] [[Media:Bird-Ftrace.ppt|Bird-Ftrace.ppt]]
|-
| Vladislav Buzov
| Digital TV and Application Store, Solving Security Problems
| [[Media:Buzov-SMACK.pdf|Buzov-SMACK.pdf]]
|-
| Grégory Clement
| How We Got a 3D Application Booting in 5 Seconds Under Linux
| [[Media:Clement-Boot3DApplicationIn5s.pdf|Clement-Boot3DApplicationIn5s.pdf]]
|-
| Bas Engel
| Accelerating Digital Television Innovating -- Joint SPACE Initiative
| [[Media:2009_ELC_Accelerating_Digital_Television_Innovation.pdf|2009_ELC_Accelerating_Digital_Television_Innovation.pdf]]
|-
| Florian Fainelli
| OpenWrt, as Rapid Embedded Systems Prototyping Framework
| [[Media:fainelli-openwrt-elce2009.pdf|fainelli-openwrt-elce2009.pdf]]
|-
| Pierre Ficheux
| Using QEMU for Industrial Embedded Applications
| [[Media:pficheux_elce09.pdf|pficheux_elce09.pdf]]
|-
| Adriaan de Groot
| Software Licensing - A Lot Like Programming
| [[Media:DeGroot-SoftwareLicensing.pdf|DeGroot-SoftwareLicensing.pdf]]
|-
| Sascha Hauer, Marc Kleine-Budde
| U-Boot-v2
| [[Media:Hauer-U_BootV2.pdf|Hauer-U_BootV2.pdf]]
|-
| Gordon Hecker
| e2factory - Open Source Embedded Linux Build System
| [[Media:e2factory_elc-e09.pdf|e2factory_elc-e09.pdf]]
|-
| Cedric Hombourger
| Why OpenEmbedded Proved a Good Foundation for MontaVista
| [[Media:Hombourger-Why_oe_good_foundation_for_mv.odp|Hombourger-Why_oe_good_foundation_for_mv.odp]] [[Media:Hombourger-Why_oe_good_foundation_for_mv.pdf|Hombourger-Why_oe_good_foundation_for_mv.pdf]]
|-
| Marcin Juszkiewicz
| Hacking with OpenEmbedded
| [[Media:Juszkiewicz-HackingWithOpenEmbedded.pdf|Juszkiewicz-HackingWithOpenEmbedded.pdf]]
|-
| Guennadi Liakhovetski
| Embedded Video Capture Under Linux: The Soc Camera Framework
| [[Media:soc-camera.pdf|soc-camera.pdf]]
|-
| Bruno Cardoso Lopes
| The LLVM MIPS and ARM Back-ends
| [[Media:Lopes-LLVM.pdf|Lopes-LLVM.pdf]]
|-
| Michael Opdenacker
| Update on Boot Time Reduction Techniques
| [[Media:opdenacker-boot-time.pdf|opdenacker-boot-time.pdf]] [[Media:opdenacker-boot-time.odp|opdenacker-boot-time.odp]]
|-
| Samuel Ortiz
| Linux Wifi Solutions for Mobile Platforms
| [[Media:Ortiz-elce-2009.pdf|Ortiz-elce-2009.pdf]]
|-
| Nicolas Palix, Julia Lawall, Gilles Muller
| Coccinelle: A Program Matching and Transformation Tool for Systems Code
| [[Media:Coccinelle_ELC-E_2009.odp|Coccinelle_ELC-E_2009.odp]][[Media:Coccinelle_ELC-E_2009.pdf|Coccinelle_ELC-E_2009.pdf]]
|-
| Pascal Pellet
| Linux Embedded Applications in Machine Vision
| [[Media:pascalPellet-e2vELC-E.pdf|pascalPellet-e2vELC-E.pdf]]
|-
| Matt Porter
| Mythbusters: Android
| [[Media:Mythbusters_Android.pdf|Mythbusters_Android.pdf]]
|-
| Frank Rowand
| A Survey of Linux Measurement and Diagnostic Tools
| [[Media:survey_of_linux_measurement_and_diagnostic_tools.pdf|survey_of_linux_measurement_and_diagnostic_tools.pdf]]
|-
| Alessandro Rubini
| Use of the Fast IRQ (FIQ) in ARM-Linux
| [[Media:0910-elce-fiq.pdf|0910-elce-fiq.pdf]]
|-
| Wolfram Sang
| Developer's Diary: The Device Tree
| [[Media:Sang-DiaryDeviceTree.pdf|Sang-DiaryDeviceTree.pdf]]
|-
| Stefan Schwarzer
| Disko v1.6 – An Application Framework for Embedded Devices
| TBD: legal status of 1 slide is unclear
|-
| Robert Schwebel
| Customizing Embedded Linux Systems with PTXdist
| [[Media:Schwebel-Customizing_with_PTXdist.pdf|Schwebel-Customizing_with_PTXdist.pdf]]
|-
| Jean-Marc Temmos
| Genivi Alliance : An Effort to Build a Linux-based In Vehicle Infotainement Platform
| [[Media:Temmos-GeniviVisteon.pdf|Temmos-GeniviVisteon.pdf]]
|-
| Francesco Virlinzi
| A Generic Clock Framework Implementation
| [[Media:ELC_E_2009_Generic_Clock_Framework.pdf|ELC_E_2009_Generic_Clock_Framework.pdf]]
|-
| Alex de Vries
| Technical Features and Components of Open Source Build Systems
| not available
|-
| Nina Wilner
| Porting Android to Power Architecture
| [[Media:Android_On_Power.pdf|Android_On_Power.pdf]]
|-
| Vitaly Wool
| Using Device Trees on ARM Platforms
| [[Media:vwool-device_trees_arm.odp|vwool-device_trees_arm.odp]] [[Media:vwool-device_trees_arm.pdf|vwool-device_trees_arm.pdf]]
|}

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Birds-Of-A-Feather Sessions'''
|- bgcolor="#c0e0e0"
| align="center" | '''BOF Presenter(s)'''
| align="center" | '''Presentation'''
| align="center" | '''File Links'''
|-
| Tim Bird
| Android
| [[Media:Bird-Android-BOF.pdf|Bird-Android-BOF.pdf]] [[Media:Bird-Android-BOF.ppt|Bird-Android-BOF.ppt]]
|-
| Peter Korsgaard, Thomas Petazzoni
| Buildroot
| [[Media:buildroot-bof.pdf|buildroot-bof.pdf]]
|-
| Yann E. Morin
| Building Our Own Toolchains For Our Embedded Projects: Why, and How To
| [[Media:Morin-Crosstool-NG.pdf|Morin-Crosstool-NG.pdf]] [[Media:Morin-Crosstool-NG.odp|Morin-Crosstool-NG.odp]]
|-
| Michael Opdenacker
| Small Business
| [[Media:opdenacker-small-business-bof.pdf|opdenacker-small-business-bof.pdf]] [[Media:opdenacker-small-business-bof.odp|opdenacker-small-business-bof.odp]]
|-
| Pierre Pronchery
| Hackable Devices: The New Possibilities of Open Hardware
| not available
|}

[[Category:Events]]

ELC Europe 2007 Presentations

2010-10-20T13:14:06Z

Kaa-ching:

BeagleBoard

2010-10-20T13:10:53Z

Kaa-ching: /* Other OMAP boards - add ref to PandaBoard */

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
'''NEWS:'''
* An [http://www.liquidware.com/shop/show/BB-BT/BeagleTouch OLED touchscreen module "BeagleTouch"] and [http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice lithium battery module "BeagleJuice"] are now available from [http://www.liquidware.com/shop Liquidware]
* [[BeagleBoard_Trainer|Trainer Boards]] are now available from [http://tincantools.com/product.php?productid=16149&cat=0&page=1&featured TinCanTools]
* [[BeagleBoard_Zippy|Zippy Boards]] are now available from [http://www.sparkfun.com/commerce/product_info.php?products_id=9731 SparkFun]!
* [[BeagleBoard_Zippy2|Zippy2]] 100baseT Expansion boards for the [[BeagleBoard]] are now available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=zippy2 Digikey]!<br>
</div>
<br>
=Events=
* Meet BeagleBoard at TI booth in June, 9-12th @ Linux Tag, Berlin, Germany, http://www.linuxtag.org/2010/
* See TI BeagleBoard demo @ Embedded World, Nuremberg, Germany, March 2-4, 2010, Hall 11. booth 308
* Each last Saturday of the month, next August 29, 2009: [[BeagleBoard/bangalore user meet|BeagleBoard Bangalore user meeting]] (Beagle Clinic India)
* all over the world 2009: [http://www.ti.com/corp/docs/landing/techday09/index.shtml# TI Technology Days 2009].
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
'''NEWS:'''
First person to post a "HowTo" for use with the [http://en.wikipedia.org/wiki/Wii_Remote#Nunchuk Nintendo Wii NunChuk] and Trainer board wins $150 cash

* Must have working code example
* Must have pictures of hardware interface
* Must have complete instructions
</div>
<br>

=Hardware=

The Beagle Board is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.

The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.

==Components==

{|border=0
!Top view of rev B:
!Top view of rev C:
|-
|[[Image:Bb revb top numbered.jpg]]
|[[Image:Bb revc top numbered.jpg]]
|-
|}
{|border=1
!No.
!Name
!Comment
|-
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 256MB NAND

+ 128MB DDR (rev B)

+ 256MB DDR (rev C)
|PoP: Package-On-Package implementation for Memory Stacking
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256MB NAND/128MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]

([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])

[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]
|-
|'''2'''
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]
|
|-
|'''3'''
|[[BeagleBoard#DVI|DVI-D]]
|Connection via HDMI connector
|-
|'''4'''
|[[BeagleBoard#JTAG|14-pin JTAG]]
|1.8V only!
|-
|'''5'''
|Expansion connector: I2C, I2S, SPI, MMC/SD
|User must solder desired header into place
|-
|'''6'''
|[[BeagleBoard#User_button|User button]]
|Allows setting boot order.
|-
|'''7'''
| Reset button
|
|-
| '''8'''
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]
|Rev A and B: not working, unpopulated

Rev C: populated and working
|-
|'''9'''
|SD/MMC+
| SDHC cards are supported
|-
|'''10'''
|[[BeagleBoard#RS232|RS-232 serial]]
|
|-
|'''11'''
|Alternate power
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])
|-
|'''12'''
|[[BeagleBoard#OTG|USB 2.0 HS OTG]]
|Mini-AB connector. Board can be powered from port.
|-
|'''13'''
|Stereo In
|
|-
|'''14'''
|Stereo Out
|
|-
|'''15'''
|S-Video
|
|-
|'''16'''
|TWL4030 (Rev A thru C2 inc.)
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.
|-
|'''17'''
|LCD
|only rev C
|-
|'''18'''
|USB power
|
|-
|'''19'''
|Host PHY
|
|-
|'''20'''
|32kHz
|
|-
|'''21'''
|12MHz
|
|-
|'''22'''
|RS232 XVCR
|
|-
|'''23'''
|PWR SW
|
|-
|'''24'''
|VBAT
|
|-
|}

* Board size: 3" x 3" (about 76.2 x 76.2 mm)
* Weight: [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/beagleboard.png ~37g]
* Currently 6 layer PCB; target: 4 layer

'''Bottom of rev B:'''

[[Image:Beagle_bottom.jpg]]

See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.

==Manual==

See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].

==Schematic==

Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.

==Layout==

Layout of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous layouts are also available from the [http://beagleboard.org/hardware/design BeagleBoard.org design page]. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.

==Errata==

# ''Boards revision A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.
# ''Boards revision < A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1 ohm instead of a 1 ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.
# ''Boards revision A only'': User LEDs 0 and 1 are shorted on the layout preventing them from being controlled individually. You need to control both GPIO_149 and GPIO_150 to turn on or off both LEDs. This is fixed in the Rev B boards.
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.
# ''Boards revision A and < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.

For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.

Note: BeagleBoard revision B6 uses different package for U9/U11.

==Clocking==

Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:

* ARM Cortex-A8 processor is currently clocked at 500MHz
* 500MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600MHz is max recommended
* An additional 720MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the Beagleboard C4
* At 600MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600/720MHz is out of spec and no guarantee it will work at all (or not damage itself)

* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:

{| border="1"
||'''ARM'''||'''DSP'''||'''core voltage'''
|-
|720 MHz||520 MHz||1.35V
|-
|600 MHz||430 MHz||1.35V
|-
|550 MHz||400 MHz||1.27V
|-
|500 MHz||360 MHz||1.2V
|}

* For some OMAP3 clock, voltage and power management discussion see [http://focus.ti.com/lit/an/sprt495/sprt495.pdf OMAP3 power management white paper], too.
* The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [http://www.beagleboard.org/irclogs/index.php?date=2009-02-26#T10:44:24].
* There is a thermal monitor in the core, you could use to scale frequency up and down

To set CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:

* The u-boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.

* To set the DSP clock to 430 Mhz use "mw 48004040 0x0009ae0c".

==Power management==

* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8mW sleep for Beagle Board]

Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5 watts idle, however it also uses the same amount under load] (see bottom of that page).

==DLP Pico projector==

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.

It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.

See [http://blog.makezine.com/archive/2009/01/tis_beagleboard_and_dlp_pico_projector.html?CMP=OTC-0D6B48984890 article from Make], too.

DigiKey videos [http://www.youtube.com/watch?v=KBbCdnOj5vg part 1], [http://www.youtube.com/watch?v=zymOmduNWyI part 2] and [http://www.youtube.com/watch?v=Uj19Bi5NYeU part 3].

==Interfacing to Raw LCD Panels==

Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the beagleboard exist:

* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel] workaround method
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap diy HDMI to parallel converter]

=Availability=

BeagleBoard Rev. C3 boards are available from

* [http://www.mouser.com/beagleboard Mouser]
* [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] with part number [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23428-ND 296-23428-ND].

BeagleBoard Rev. C4 boards are available from:

* [http://www.liquidware.com/shop/show/BB-C4/BeagleBoard+C4 Liquidware]

Note: For non-US Digi-Key free shipping orders:

* Click the US flag on the top right corner of [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] BeagleBoard page to come to the international page
* Select ''Order Online'' for your country
* Add quantity ''1'' and part number ''296-23428-ND''
* Click ''Add to order''

When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.

Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.

Note: While you get free shipping, most probably you have to pay tax e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.

Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).

Note: German (Europe) users can order through German shops, too. For higher price, though.
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux] sells BeagleBoard for EUR 159.00 + shipping.
* [http://www.watterott.com/en/BeagleBoard Watterott electronic] sells BeagleBoard for EUR 142,80 + shipping.

See below for ''hardware'' differences of the revisions. There are no ''software'' differences.

==Revision A==

There are some limited early revision Ax prototypes out there used by some hackers hanging around at #beagle channel on irc.freenode.net. See [[BeagleBoard#Errata|errata]] for limitations.

==Revision B==

Revision B is same as revision A, except
* fix for shorted LEDs 0/1
* fix for wrong power jack pinout
* revision B6 uses different package for U9/U11
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.

There are 4 revisions of the B board in the field: B4, B5, B6 and B7.

The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.

==Revision C2==
Revision C2 is same as revision B7 except:
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])
* It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:
** updated ARM Cortex A8 silicon (r1p3) fixing a very rare [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON issue] that has not been seen in real code
* Power measurement feature
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030
* Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])
* Revision detection (to be able to identify C2 board from older boards by software, e.g. for different pin mux)
* 256MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)

Note: Revision C2 is the first production version, and all orders from from Digi-Key are shipped as Rev C2.

==Revision C3==
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.

Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery
* Mounting holes conected to ground
* Slightly improved S-Video

==Revision C4==
Revision C4 boards are the same as Revision C3 except:
* Processor is 720MHz capable OMAP3
* Improved USB Host PHY power rails

==Clones==
===EBVBeagle===
EBV build and sell their own BeagleBoard called [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], see e.g. [http://fl0rian.wordpress.com/2009/03/08/the-other-beagleboard/].
It is actually a BeagleBoard revision C2 with green PCB boxed with some useful accessories. It comes as a quite complete starter kit with AC adapter, USB to Ethernet adapter, MMC card, USB hub and some cables.
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].

===Mini Board===
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a chinese BeagleBoard clone.

===DevKit 8000===
[[DevKit8000]] is a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard).

===IGEPv2===
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.
* 720MHz OMAP3 Processor
* 512MB RAM / 512MB Flash
===SOM3530===
[[SOM3530]] is a chinese BeagleBoard clone [[System-on-Module]],Dimension 40x40x4mm, Maybe the smallest [[OMAP3530]]-based modules in the world! Including 100M high perfomance ethernet I/F

==BeagleBoard-based products==
* [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book], see [http://gigglehd.com/zbxe/hdforum/files/attach/images/899852/493/987/001/always_innovating_touch_book_0011.jpg]

==Beagle case==

*[http://specialcomp.com/beagleboard/ Special Computing acrilyic case]
** [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]
* [http://www.esawdust.com/product/encl-dh-r1/ eSawdust metal case]

=Adapters=

For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].

See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for Beagle Board.

==Expansion boards==
See [[:Category:BeagleBoard_Expansion_Boards]] for more information about expansion boards

[http://www.liquidware.com/shop/show/BB-BT/BeagleTouch BeagleTouch] - A modular "shield" that snaps on top of the Beagle Board and provides a touch-screen OLED interface

[http://www.liquidware.com/shop/show/BB-BJC/BeagleJuice BeagleJuice] - A lithium ion battery module that snaps on the back of the Beagle Board that powers the Beagle Board.

==JTAG==

Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products.
See [[BeagleBoardJTAG]] for more information.

==RS232==

The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.

Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.

==USB-to-Serial Converter==

Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.

==USB==
There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.

===EHCI===
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.

According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5V at 500mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]

'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts are not available, some boards can be repaired by a 22 uF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.

===OTG===
The HS USB OTG ([http://en.wikipedia.org/wiki/USB_On-The-Go OnTheGo]) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.

When using the OTG port in host mode, you must power the BeagleBoard using the +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.

The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a [http://trisoft.de/pics/ZHost.JPG 5-pin USB Mini-A plug] which shorts these pins together in the plug. A [http://en.wikipedia.org/wiki/USB#USB_cables 5-pin USB Mini-B plug] leaves Pin 4 floating. Unfortunately, most USB Mini plugs are unmarked as to whether they are "A" or "B".

You can find "mini A" adapters that have Pin 4 shorted and offer out a full-sized USB A Female jack [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 here.]
<table>
<tr><td>
Since the right cables might be hard to get, you simply can
* short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.
or
* use a "mini B" cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.
</td><td>[[Image:usb_otg.png]]</td></tr></table>
The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5.
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.

==DVI==

DVI-D connection on BeagleBoard uses a [http://en.wikipedia.org/wiki/HDMI HDMI connector]:

''HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.''

BeagleBoard can be connected to a DVI monitor using HDMI female to DVI male cable.

=BootRom=

OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see [http://www.ti.com/litv/pdf/sprufd6a SPRUFD6].

==User button==

With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):

* User button ''not'' pressed: NAND -> USB -> UART -> MMC
* User button ''is'' pressed: USB -> UART -> MMC -> NAND

Technically speaking, the user button configures pin SYS.BOOT[5]. See [http://focus-webapps.ti.com/general/docs/sitesearch/searchsite.tsp?selectedTopic=1653260327&numRecords=25&searchTerm=sprufd6&statusCode=null SPRUFD6] for more details.

==Serial and USB boot==

Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|u-boot env from linux]].

===OMAP U-Boot Utils===

Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide

* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.
* ''ukermit - Download a file from host without using kermit to U-Boot.

See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.

===Serial boot===

Besides Nishanth' ''OMAP U-Boot Utils'', to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there are two older (experimental) tools for UART boot:

* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]
* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)

See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.

===USB boot===

Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:

* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]

See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.

See [[BeagleBoardRecovery#USB_recovery|USB recovery section]] how to use USB boot for board recovery.

==NAND boot==

See [[BeagleBoardNAND|NAND boot]] article.

==MMC/SD boot==

Currently, [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] is the only working way for first board bring up.

===MMC/SD formatting===

As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using e.g. Windows or Linux tools.

'''Windows'''

See ''HP USB Disk Storage Format Tool 2.0.6'' description on [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] page.

'''Linux'''

Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].

===Dual partition card===

You can [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat create a dual-partition card], booting from a FAT partition that can be read by the OMAP3 ROM bootloader and Windows, then utilizing an ext2 partition for the Linux root file system.

To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (e.g. in uboot using ''setenv bootargs''):

console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait

===U-Boot booting===

If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a u-boot prompt after booting beagle board. E.g. (output from terminal program with 115200 8N1):

...40T.........XH.H.U�..Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector

717948 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)

OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)
DRAM: 128 MB
Flash: 0 kB
NAND:256 MiB
In: serial
Out: serial
Err: serial
Audio Tone on Speakers ... complete
OMAP3 beagleboard.org #

Using this u-boot prompt, you now can start kernel uImage stored on MMC card manually:

OMAP3 beagleboard.org # mmc init
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage
OMAP3 beagleboard.org # bootm

If you like to make that happen every boot:

OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv

=Code=

Code and binaries for BeagleBoard are available at various places.

==Binaries==

BeagleBoard pre-built binaries and source code can be found at [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode Beagle source code] and [http://code.google.com/p/beagleboard/downloads/list downloads] page. These are the locations where "official" TI code is available. Please note that this code is mainly for reference and testing. More up to date binaries and code is available by community. Community took (parts) of TI reference code, improves and updates it.

Actually, [http://www.angstrom-distribution.org/node/47 Koen's prebuilt Beagleboard demo images] are up to date binaries including e17 as window manager, the abiword word processor, the gnumeric spreadsheet application, a NEON accelerated mplayer and the popular NEON accelerated omapfbplay which gives you fullscreen 720p decoding. The [http://www.angstrom-distribution.org/demo/beagleboard www.angstrom-distribution.org/demo/beagleboard] directory should contain all the files you need:

* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]

See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.

==Source==

'''Update on April 23 - 2010''': Sources for the X-Loader and U-Boot that ship on the BeagleBoard can be found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/]. The U-Boot version found in that repository supersedes the one found at [http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/ http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/].

Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available.

===X-Loader===

Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by

git clone git://gitorious.org/x-load-omap3/mainline.git xloader
cd xloader/

Build:

make distclean
make omap3530beagle_config
make

Result will be a ~20k sized ''x-load.bin'' in main directory.

===U-Boot===

[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard (except for revision C4; see note below). Get it by:

git clone git://git.denx.de/u-boot.git u-boot-main
cd u-boot-main
git checkout --track -b omap3 origin/master

Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):

make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config
make CROSS_COMPILE=arm-none-linux-gnueabi-

Result will be a ~160k sized ''u-boot.bin'' in main directory.

Note: Due to (patch and binary) size, BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].

Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:

git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3
cd u-boot-omap3
git checkout --track -b omap3-dev origin/omap3-dev

Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]

Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...
get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/
('''Update on April 23 - 2010''': This repository has been superseded by the U-Boot version found at [http://gitorious.org/beagleboard-validation/ http://gitorious.org/beagleboard-validation/])

Note: If you want to activate I2C from the expansion header, modify board/ti/beagle/beagle.h :

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | EN | M4)) /*GPIO_168*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | EN | M4)) /*GPIO_183*/

to

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | DIS | M0)) /*I2C2_SCL*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | DIS | M0)) /*I2C2_SDA*/

===Linux kernel===

[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6
cd linux-omap-2.6

Build:

make distclean
make ARCH=arm omap2plus_defconfig
make ARCH=arm menuconfig # only needed if you want to change the default configuration
make ARCH=arm uImage

The result will be a ''uImage'' in ''arch/arm/boot/'' directory.

If you use the OE toolchain and want to build outside of the OE tree you should do
ARCH=arm
export ARCH
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage
Note: the staging dir in the path is for mkimage. If you've build a kernel before with oe, the program should be there

Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.

===Experimental kernel patches and hacks===

Some beagle developers maintain their own kernel experimental patches and hacks not ready for upstream:

* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches]
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related.
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.

=Compiler=

TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.

==ARM==

There is broad compiler support including gcc - please see [http://www.elinux.org/ARMCompilers ARM Compilers]

==C64x+ DSP==

A free C64x DSP compiler is available as [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html Linux hosted C6x Code Generation Tools] (TMS320C6000 C/C++ CODE GENERATION TOOLS 6.1.3 July 2008).

Note: my.TI account required. You may create an account [https://my.ti.com here]

Note: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.

See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.

=Cortex A8 ARM features =

ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.

It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.

See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an intro into VFP-lite and NEON.

===ARM NEON===

NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:
* 64-bit signed/unsigned
* 32-bit signed/unsigned
* 32-bit single precision floating point
* 16-bit signed/unsigned
* 8-bit signed/unsigned

The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.

The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].

For NEON optimized libraries see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].

NEON is used by various opensource projects:
* [http://www.ffmpeg.org/ ffmpeg] - libavcodec used by mplayer, omapfbplay, and many other linux applications
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
* [http://www.bluez.org/ Bluez] - official Linux Bluetooth stack
* [http://eigen.tuxfamily.org/ Eigen2] - C++ template library for linear algebra (matrix math etc)
* [http://www.webmproject.org/code/ Webm] - Google's new opensource video codec

Compilation tools support for NEON:
* ARM RVDS
* gcc
* [http://blog.llvm.org/2010/04/arm-advanced-simd-neon-intrinsics-and.html LLVM]

=== ARM Cortex-A8 Floating Point ===

There are two types of instructions in the ARM v7 ISA that handle floating point:

1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).
These is used by gcc for C floating point operations on 'float' and 'double' since ANSI C can only describe scalar floating point, where there is only one operation at a time.

2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (2 values in a D-register, or 4 values in a Q-register)
These can be use by gcc when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases the VFPv3 scalar ops will be used.

ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.

On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain 1 cycle/instr throughput (processing 2 single-precision values at once) for consumer multimedia. The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.

If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:
* use gcc with -ftree-vectorize (possibly modify source code to make it vector friendly)
* use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)
* use NEON asm directly

On Cortex-A9, there is a much higher performance floating point unit which can sustain 1 cycle/instr throughput, with low result latencies. OMAP4 uses dual-core Cortex-A9+NEON which gives excellent floating-point performance for both FPU and NEON instructions.

=Board recovery=

If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.

=Development environments=

Instead of just using compiler + editor, you can use complete image create "development tool chains" which integrate compiler, build system, packaging tools etc. in one tool chain.

==OpenEmbedded==

For [http://www.openembedded.org/ OpenEmbedded] (OE), there are some hints how to [http://www.beagleboard.org/irclogs/index.php?date=2008-04-29#T13:06:25 start with OE for BeagleBoard]. See [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]],[[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.

In the OE getting started document, for BeagleBoard replace ''MACHINE = "om-gta01"'' by ''MACHINE = "beagleboard"''. After confirming ''bitbake nano'' works, try ''bitbake console-image''. The first time you run bitbake OE will download all the needed source and build the tool chain. This will take several hours. After all went fine, the output is in ''${OE_ROOT}/tmp/deploy/glibc/images/beagleboard''.

Note: Koen has some BeagleBoard [http://amethyst.openembedded.net/~koen/index.php?path=beagleboard/ source and binary images] built with OE. There, ''Angstrom-console*'' images don't include an X server, you can still use a e.g. DVI-D screen with console, but you won't have a GUI. ''Angstrom-x11*'' images contain an X server.

===One very important note:===

It's important to have an X-Loader on your Beagleboard that uses the uImage on the SD Card that goes with Angstrom. The B6 Beagleboards do not appear to come with such an X-Loader. So you likely will have to upgrade the X-Loader. Here's what to do:
* Make an SD Card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more info on making the SD Card.
* Put the SD Card in the Beagle, and boot up to the U-Boot Prompt.
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section.
* Reboot the Beagle to see that the new X-Loader is properly loaded.

This will update the X-Loader to a newer version that will automatically load uImage from the SD Card when present -- rather than always using the uImage in the Beagleboard NAND.

==Eclipse==
The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a "fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform". The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a "Remote System Explorer" (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the [http://wiki.eclipse.org/DSDP/TM/TCF_FAQ Target Communications Framework (TCF) component]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].

See also [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging)

==Android==
[http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.

There are several resources for Android on OMAP (Beagle) available:

'''OMAPZOOM'''

You can find Android port for OMAP ZOOM architecture on [https://gforge.ti.com/gf/project/omapandroid/ OMAPZoom.org's wiki page on Android].

'''EMBINUX'''

[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX™] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review.

Detailed instructions, for porting Android on Beagle Board, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.

You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on Beagle Board.

'''Android on OMAP wiki'''

Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]]

'''0xdroid'''

[http://gitorious.org/0xdroid 0xdroid], the enhanced version of Android on Beagleboard by [http://0xlab.org 0xlab]. The [http://gitorious.org/0xdroid source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.

The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].

You can watch 0xdroid demo video on Beagle Board:
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]
* [http://www.youtube.com/watch?v=OGpYk1p1UPI 0xdroid demo video (3)]

==Mamona==

[http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support Beagle.

==Ubuntu==

See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.
* [[BeagleBoardLucid]] Details about Ubuntu Lucid on the BeagleBoard.
* [[BeagleBoardUbuntuKernel]] Details about the Ubuntu Kernel on the BeagleBoard.

==Debian ARM==

See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.

==GeeXboX ARM==

See [[GeeXboX|GeeXboX (ARM)]] installation guide how to install GeeXboX on BeagleBoard (including clones).

==Scratchbox==

[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 intro], too.

=Software hints=

This section collects hints, tips & tricks for various software components running on beagle.

==QEMU==

[[Qemu|QEMU]] [http://vm-kernel.org/blog/2008/12/15/linux-is-running-on-qemu-omap3/ supports OMAP3] being able to boot a BeagleBoard Linux kernel.

==Linux hints==

See BeagleBoard [http://code.google.com/p/beagleboard/wiki/LinuxHints Google wiki Linux hints] page (for Linux WTBU (Wireless TI Business Unit) kernel [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode 2.6.22]). Currently featuring:

* Switching video output between DVI-D and S-Video
* Disabling framebuffer blanking
* Listing USB devices

==lmbench==

Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on Beagle.

==Mediaplayer (FFmpeg)==

There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on Beagle. Includes compiler hints and patches.

==Java==

When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)
* Cacao + GNU Classpath (JIT compiler, J2SE-like)
* PhoneME Advanced Foundation (JIT compiler, CDC)

Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].

See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.

OpenEmbedded users can add the [http://evolvis.org/scm/?group_id=11 Jalimo Subversion repository] as an overlay (instructions are in the repository). This will allow them to build OpenJDK packages. Inclusion of these recipes in mainline OpenEmbedded is planned but still ongoing.

The recipes offer the following functionality:

* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)
* OpenJDK + Hotspot (Shark port) (not working yet)

[http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.

People interested in getting this stuff working better should contact people on:
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]

You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].

=Graphics accelerator=

OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from [http://www.imgtec.com/ Imagination Technologies]. [http://www.imgtec.com/powervr/powervr-graphics.asp PowerVR] SGX530 is a new generation of programmable PowerVR graphics and video IP cores. Only the kernel portions of Linux drivers will be open source. The PowerVR folks will provide binary user-space libraries. Using the EMail contact at [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12700&contentId=27458 TIs Mobile Gaming Developers page] there are Linux v2.6 OMAP3430 SDKs for OMAP3 Zoom and SDP supporting OpenGL ES v2.0, OpenGL ES v1.1 and OpenVG 1.0 available.

Tutorial:
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]

Some videos:

* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]
* [http://www.youtube.com/watch?v=cfeqSOYkBJg&feature=player_embedded Video of the Beagle Board turned into a portable battery powered Linux tablet]

=Beginners guide=

You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].

=FAQ=

For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].

=Links=
==Home page==
[http://beagleboard.org/ beagleboard.org] (beagle board home)
* Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''

==Manuals and resources==
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]

==Contact and communication==
* [http://groups.google.com/group/beagleboard Beagle board discussion list]
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]
* [http://beagleboard.blogspot.com/ Beagle board blog]
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]
* Chat:
** [http://beagleboard.org/chat Beagle Board chat]
** IRC: #beagle channel on irc.freenode.net
** [http://www.beagleboard.org/irclogs/index.php IRC archive]
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications
* [http://www.beagleboard.de/ German Beagle Board Forum and Wiki]

==TI resources==
* [http://opensource.ti.com/ TI open source page]
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]
==Articles==
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about Beagle]
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about Beagle Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]

==Books==
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]

==Beagle based training materials==
* http://free-electrons.com/blog/beagle-labs/

==Past Beagle events==
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also beagle board
* [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&t=4094&st=0&sk=t&sd=a&sid=d69cc807569ab41e33f93af698c536b8&start=15#p41549 video]
* LinuxTag, May 28-31, 2008: [http://www.flickr.com/photos/jadon/2551439955/in/pool-beagleboard picture 1] and [http://www.flickr.com/photos/jadon/2535692865/in/pool-beagleboard picture 2]
* [http://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at Beagle. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living beagle] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]
* Free Open "Embedded Linux" Training for Students in India, [http://code.google.com/p/beagleboard/wiki/Trainings?updated=Trainings&ts=1220250913 beagleboard.org Trainings in India], September 20, 2008: [http://www.youtube.com/watch?v=A6FLdmgQlb4&feature=PlayList&p=1BAB6EE9CC7285AD&index=0 video], [http://www.flickr.com/photos/25691331@N04/sets/72157607419766102/ photos] and [http://lakshmansrikanth.blogspot.com/2008/09/linux-embedded.html blog]
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008
* [http://www.mvista.com/vision/ MontaVista Vision 2008 Embedded Linux Developers Conference], San Francisco, California, October 1-3, 2008 : [http://www.mvista.com/download/topic.php?t=18 Video and presentation overview], [http://www.mvista.com/download/fetchdoc.php?docid=323 William Mills' presentation], [http://www.mvista.com/download/fetchdoc.php?docid=333 Jason Kridner's presentation]
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008
* [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008], Hynes Convention Center, Boston, USA, October 26 - October 30, 2008: [http://beagleboard.org/demo/esc Resources]
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009
* [http://www.silica.com/events/seminars/seminar-overview/ti-omp-workshop.html OMAP35x training by Silica], January 21, 2009, Cambridge, UK, ARM Holdings Lecture Theatre. [[RichardB's notes from the seminar]]
* [[BeagleBoard/contest|BeagleBoard contest #2]], unitl February 27, 2009: : Create a cool BeagleBoard application and win a Rev C2!
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 Beagle presentation]
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').
* Thursday, August 27th: [http://wiki.omap.com/index.php/ETechDays_Lightning_Talks ETechDays Lightning Talks]. 15 minute lightning talks via IRC, WebEx or Dial-In.
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])

==Beagle wiki pages==
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has infos about status and usage of open source JTAG software OpenOCD with Beagle
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]
* [[BeagleBoard/video|BeagleBoard video]]
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
* [[BeagleBoard-JP|Japanese translation of this Beagle page]]
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]
* [[Zoom2Beginners|Zoom2 for Beginners]]
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the Beagle Board] from Make:Online
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private Beagle wiki] (please don't add anything there, do it here. It will help to avoid scattering. Thanks!)
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON intro
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html Beagleboard setting date via GPS]
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard
* [[BeagleBoardPWM]] Details about PWM on the BeagleBoard.

==Beagle photos==
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]
==Beagle videos==
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu]
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with beagleboard]
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk Beagleboard LED demo]
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a beagleboard]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector]
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]
* [http://in.youtube.com/watch?v=nADn_vNVEKw Beagle Board booting Android]
* [http://www.youtube.com/watch?v=UHQdUS0i-nw Beagleboard, SGX, and libfreespace demo]

==Beagle manufacturing==
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related Beagle Solder Paste Screening]
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related Beagle Assembly Inspection]
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related Beagle Functional Test]
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related Beagle Reflow]
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related Beagle Board Assembly at Circuitco]
==Fun==
* Enjoy [http://www.beaglegame.com/ BeagleGame]

=Other OMAP boards=

* OMAP 4430 based [[PandaBoard]]
* OMAP-L138 Based [[Hawkboard]]

* OMAP3530 based [http://www.timll.com/chinese/OMAP/DevKit8000.asp DevKit8000], a Chinese BeagleBoard,256MB DDR SDRAM + 256MB NANDFLASH,Fully compatible with BeagleBoard source.

* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]
* OMAP3 OMAP35x based EVM from [http://mistralsolutions.com/products/omap_3evm.php Mistral] and [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html TI] (both are the same)
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion], also sold in North America through [http://www.robotcraft.ca/webshop/index.php?manufacturers_id=21 Robotcraft Systems]
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.
* OMAP35x System-on-Module [[SOM3530]],The smallest(40x40x4mm) OMAP35XX-based System on Module in the world! (It is not-Gumstix Overo is smaller. at 17mm*58mm)
* OMAP35x based [http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm CM-T3530 from CompuLab]

=Subpages=
<splist
parent=
showparent=no
sort=desc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0
/>

PandaBoard

2010-09-30T14:16:50Z

Kaa-ching:

The PandaBoard is an [[OMAP4430]] ([[Cortex]]-A9) based low cost development platform.

= Hardware =

* OMAP4430 Cortex-A9 CPU based open development platform.
''Details coming soon''

= Accessories =

* [[Panda_Bamboo|Bamboo Board]]

[[category:OMAP]]
[[category:omap4430]]
[[category:PandaBoard]]
[[category:Development Boards]]

Barebox

2010-09-20T15:36:23Z

Kaa-ching:

Barebox is an attempt to work around the limitations that U-Boot shows through its age.
Originally dubbed U-Boot v2, it now has a different name because its design goals are different.

[http://www.barebox.org Barebox (U-Boot-v2)]

[http://elinux.org/File:Hauer-U_BootV2.pdf U-Boot-v2 Presentation from CELF Embedded Linux Conference Europe Grenoble, 2009-10-16]

[[Category:Bootloaders]]

Barebox

2010-09-20T15:34:37Z

Kaa-ching: moved U-Boot-v2 to Barebox

[http://www.barebox.org Barebox (U-Boot-v2)]

[http://elinux.org/File:Hauer-U_BootV2.pdf U-Boot-v2 Presentation from CELF Embedded Linux Conference Europe Grenoble, 2009-10-16]

[[Category:Bootloaders]]

U-Boot-v2

2010-09-20T15:34:37Z

Kaa-ching: moved U-Boot-v2 to Barebox

#REDIRECT [[Barebox]]

Barebox

2010-09-20T15:34:03Z

Kaa-ching:

Android Hardware

2010-05-27T15:49:36Z

Kaa-ching:

== Mobile Phones ==
See http://www.androidphones.com/

=== That have shipped ===
* HTC Dream
** Branded as the G1 by T-Mobile
** Google: Android Developer Phone 1 (ADP1) - same hardware as G1, but unlocked.
* HTC G1 V2
* HTC G2, aka HTC Magic
** Google Android dev phone 2 - same hardware as Magic, but unlocked
* HTC Hero
** branded as T-Mobile G2
* HTC Hero for CDMA
** available from Sprint on Oct 11, 2009
* HTC Tatoo - Europe, Oct 2009
** SPECS: 528MHz Qualcomm processor, 512MB ROM and 256MB RAM, 240x320 px (QVGA) 2.8-inch touchscreen, GPS, WiFi, compass and accelerometer.
** HTC's Sense UI in TATTOO: http://www.akihabaranews.com/en/news-18854-TATTOO%2C+HTC%E2%80%99s+Latest+Android+Phone+with+Sense+UI.html
* Samsung Galaxy (in Europe)
* Samsung Behold II
** Samsung's TouchWiz 3D Interface: http://www.akihabaranews.com/en/news-19025-Samsung+Behold+II%2C+TouchWiz+Wonder+for+T-Mobile.html
* Motorola Droid (on Verizon)
** branded as Motorola Milestone in Europe
* Motorola Cliq
** Has "MotoBlur" interface for interacting with social network sites
** [http://www.wired.com/gadgetlab/2009/09/motorola-android/ Wired Article Sep 2009]
* Motorola Sholes ?
* Sony Ericsson XPERIA 10
** http://gizmodo.com/5395712/sony-ericsson-xperia-x10-announced-sonys-first-android-device
* Sony Ericsson X10 Mini
** http://www.sonyericsson.com/cws/companyandpress/aboutus/awards/award/x10miniaward?cc=gb&lc=en

=== Under development ===
* Acer Liquid
** http://www.linuxfordevices.com/c/a/News/Acer-Liquid/
** http://www.akihabaranews.com/en/news-19112-Acer+Finally+Announces+Their+Android+Liquid+Smartphone.html
* HTC Fiesta ?
* LG GW620
** [http://www.engadget.com/2009/09/14/lg-officially-announces-gw620-its-first-android-phone/ Engadget Article Sep 2009]
** [http://www.wired.com/gadgetlab/2009/09/lg-android-phone/ Wired article Sep 2009]
** LG's slide out QWERTY: http://www.akihabaranews.com/en/news-18892-LG-GW620%2C+LG%E2%80%99s+First+Android+Smartphone.html

== Non-phone devices ==
=== That have shipped ===
* Archos Internet tablets
** Archos 5 and Archos 7 Internet tablets - [http://www.linuxfordevices.com/c/a/News/Archos-5-Internet-Tablet/?kc=LNXDEVNL091609 Android tablet plays 720p video] Linux For Devices Article, Sep 2009

* Android handheld game device with Cortex-A8 833Mhz powerful SoC
** ODROID - [http://www.linuxfordevices.com/c/a/News/HardKernel-Odroid/ Hackable Android handheld game device] Linux For Devices Article, Dec 2009

=== Under development ===
* [http://phandroid.com/2009/06/05/android-in-your-car-autolinq-by-continental-ag/ Continental AG car navigation system]

* [http://www.linuxfordevices.com/c/a/News/Marvell-Moby/?kc=LNXDEVNL032410 Marvel pad with targeted $100 price]

* Google TV

[[Category: Android]]

Android Tools

2010-05-01T02:20:20Z

Kaa-ching: document adb a little

Here are some development tools useful for working with Android

== Android SDK ==
=== adb ===
adb is the android debugger - it also doubles as file transfer agent.
The setup consists of an <tt>adbd</tt> on the target in the <tt>/sbin</tt> directory. On the host two programs are run: the <tt>adb</tt> application (in the SDK's <tt>tools</tt> directory) and an adb server, started by the adb application.

For emulators, adb will usually run automagically.

For real boards - with debugging over USB, you might need to do work, as is documented here: http://developer.android.com/guide/developing/device.html#setting-up .

For real boards that do not have a USB connection but have Ethernet instead, you might need to do a few tricks.
* make sure that adbd runs on the board. If it doesn't run, you might want to check the <tt>init.rc</tt> file.
* make sure that the network connection between host and the board is working - test pinging both ways.
* on the host, type the following (and yes, you need to specify the board's IP address on the host):
ADBHOST=<target-ip> tools/adb kill-server
ADBHOST=<target-ip> tools/adb shell
* you should now get a prompt on the board, you can exit the prompt if you want.
* <tt>tools/adb devices</tt> should now list the device.

=== fastboot ===
* Fastboot - [[Android Fastboot]] is a tool to boot and manipulate the partitions on an Android development phone.

* toolchains -
* logging system -
* Emulator - See http://developer.android.com/guide/developing/tools/emulator.html
The emulator is a version of QEMU, which mimics the instruction set of an ARM processor, and
the hardware that one might find on a mobile phone. The emulator runs on an x86 system,
but executes an ARM linux kernel and programs. The flow of control is:
** application ->
** dalvik VM ->
** C/C++ libraries ->
** ARM linux kernel ->
** emulated instructions and hardware (QEMU)->
** C libraries->
** x86 kernel ->
** real hardware

== other tools ==
=== agcc ===
* [http://plausible.org/andy/agcc agcc] - A wrapper tool for compiling native Android apps (linked directly to bionic)
** See http://android-tricks.blogspot.com/2009/02/hello-world-c-program-on-using-android.html
=== bootchart ===
* [[Using Bootchart on Android|bootchart]]

=== busybox ===
Android ships with a utility suite (called 'toolbox') that is not busybox.

You can get a binary busybox for Android [http://benno.id.au/blog/2007/11/14/android-busybox here]
The site includes instructions for easy installation on your device.

=== smem ===
* smem

=== strace ===
* strace
** Statically linked binary available at: http://benno.id.au/blog/2007/11/18/android-runtime-strace
** Instructions for building Android strace - http://discuz-android.blogspot.com/2008/01/create-google-android-strace-tool.html

== Eclipse ==

== Hardware ==
=== Serial Cable for G1 ===
You can build a serial cable to use with the G1, which is helpful to see kernel boot messages
on the serial console.

See http://www.instructables.com/id/Android_G1_Serial_Cable

Back to [[Android Portal]]

[[Category:Android]]

File:ELC-Europe-2010-CfP.v3.png

2010-04-22T22:17:15Z

Kaa-ching: uploaded a new version of "File:ELC-Europe-2010-CfP.v3.png": made background opaque, improved resolution.

PNG of the yellow CfP PDF.

File:ELC-Europe-2010-CfP.v3.pdf

2010-04-22T22:11:26Z

Kaa-ching: PDF file of the Call for Proposals.

PDF file of the Call for Proposals.

File:ELC-Europe-2010-CfP.v3.png

2010-04-22T22:04:29Z

Kaa-ching: PNG of the yellow CfP PDF.

PNG of the yellow CfP PDF.

BeagleBoard

2010-04-19T13:43:57Z

Kaa-ching: /* Android */ fix link for omapzoom.

[[Category: Linux]]
[[Category: OMAP]]
[[Category:Development Boards]]
[[Category: BeagleBoard]]
This page collects information about [http://www.ti.com/ TI's] [http://www.arm.com/ ARM] based [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] [http://beagleboard.org Beagle Board].

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
'''NEWS:'''
* [[BeagleBoard_Trainer|Trainer Boards]] are now available from [http://tincantools.com/product.php?productid=16149&cat=0&page=1&featured TinCanTools]
* [[BeagleBoard_Zippy|Zippy Boards]] are now available from [http://www.sparkfun.com/commerce/product_info.php?products_id=9731 SparkFun]!
* [[BeagleBoard_Zippy2|Zippy2]] 100baseT Expansion boards for the [[BeagleBoard]] are now available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?vendor=0&keywords=zippy2 Digikey]!<br>
</div>
<br>
=Events=
* Meet BeagleBoard at TI booth in June, 9-12th @ Linux Tag, Berlin, Germany, http://www.linuxtag.org/2010/
* See TI BeagleBoard demo @ Embedded World, Nuremberg, Germany, March 2-4, 2010, Hall 11. booth 308
* Each last Saturday of the month, next August 29, 2009: [[BeagleBoard/bangalore user meet|BeagleBoard Bangalore user meeting]] (Beagle Clinic India)
* all over the world 2009: [http://www.ti.com/corp/docs/landing/techday09/index.shtml# TI Technology Days 2009].
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!

<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#ffffcc; align:right; ">
'''NEWS:'''
First person to post a "HowTo" for use with the [http://en.wikipedia.org/wiki/Wii_Remote#Nunchuk Nintendo Wii NunChuk] and Trainer board wins $150 cash

* Must have working code example
* Must have pictures of hardware interface
* Must have complete instructions
</div>
<br>

=Hardware=

The Beagle Board is ''a low-cost, fan-less single-board computer based on TI's OMAP3 device family, with all of the expandability of today's desktop machines, but without the bulk, expense, or noise'' (from [http://beagleboard.org/ beagleboard.org]). It uses a TI [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor (ARM Cortex-A8 superscalar core ~600MHz paired with a TMS320C64x+ DSP ~430MHz and an Imagination SGX 2D/3D graphics processor). See [http://focus.ti.com/docs/prod/folders/print/omap3530.html#features OMAP3530 features] for more processor features. [[BeagleBoard#Availability|Price is USD 149]]. The design goal was to make it as simple and cheap as possible, e.g. not having a LCD added, but letting you connect all add-ons available as cheap external components. See [http://beagleboard.org/brief What is Beagle?] and [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article] for more details.

The videos [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings] and [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu] give you a good intro about what BeagleBoard is about and its capabilities.

==Components==

{|border=0
!Top view of rev B:
!Top view of rev C:
|-
|[[Image:Bb revb top numbered.jpg]]
|[[Image:Bb revc top numbered.jpg]]
|-
|}
{|border=1
!No.
!Name
!Comment
|-
|'''1'''
|[http://www.ti.com/omap35x OMAP3530] processor + 256MB NAND

+ 128MB DDR (rev B)

+ 256MB DDR (rev C)
|PoP: Package-On-Package implementation for Memory Stacking
[http://www.micron.com/products/partdetail?part=MT29C2G24MAKLAJG-6%20IT 256MB NAND/128MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1435-ND DigiKey]

([http://www.micron.com/products/partdetail?part=MT29C4G48MAPLCJI-6%20IT 512MB NAND/256MB Mobile DDR SDRAM] available from [http://www.digikey.com/scripts/US/DKSUS.dll?Detail?name=557-1436-ND DigiKey])

[http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]
|-
|'''2'''
|[http://focus.ti.com/docs/prod/folders/print/tfp410.html DVI chip (TFP410)]
|
|-
|'''3'''
|[[BeagleBoard#DVI|DVI-D]]
|Connection via HDMI connector
|-
|'''4'''
|[[BeagleBoard#JTAG|14-pin JTAG]]
|1.8V only!
|-
|'''5'''
|Expansion connector: I2C, I2S, SPI, MMC/SD
|User must solder desired header into place
|-
|'''6'''
|[[BeagleBoard#User_button|User button]]
|Allows setting boot order.
|-
|'''7'''
| Reset button
|
|-
| '''8'''
|[[BeagleBoard#EHCI|USB 2.0 EHCI HS]]
|Rev A and B: not working, unpopulated

Rev C: populated and working
|-
|'''9'''
|SD/MMC+
| SDHC cards are supported
|-
|'''10'''
|[[BeagleBoard#RS232|RS-232 serial]]
|
|-
|'''11'''
|Alternate power
|normally powered by USB (unmounted on REV Ax boards, see [[BeagleBoard#Errata|errata]])
|-
|'''12'''
|[[BeagleBoard#OTG|USB 2.0 HS OTG]]
|Mini-AB connector. Board can be powered from port.
|-
|'''13'''
|Stereo In
|
|-
|'''14'''
|Stereo Out
|
|-
|'''15'''
|S-Video
|
|-
|'''16'''
|TWL4030 (Rev A thru C2 inc.)
[http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] (Rev C3 onwards)
|Audio CODEC, USB port, power-on reset and power management. The TWL4030 is pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip and was used due to the very limited availability of the TPS65950 in early board revisions.
|-
|'''17'''
|LCD
|only rev C
|-
|'''18'''
|USB power
|
|-
|'''19'''
|Host PHY
|
|-
|'''20'''
|32kHz
|
|-
|'''21'''
|12MHz
|
|-
|'''22'''
|RS232 XVCR
|
|-
|'''23'''
|PWR SW
|
|-
|'''24'''
|VBAT
|
|-
|}

* Board size: 3" x 3" (about 76.2 x 76.2 mm)
* Weight: [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/beagleboard.png ~37g]
* Currently 6 layer PCB; target: 4 layer

'''Bottom of rev B:'''

[[Image:Beagle_bottom.jpg]]

See [http://www.flickr.com/photos/jadon/sets/72157606050144396/ jadonk's photostream] for some more detailed BeagleBoard pictures.

==Manual==

See [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)].

==Schematic==

Schematic of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous are also available from [http://beagleboard.org/hardware/design BeagleBoard.org design page] including in PDF format. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.

==Layout==

Layout of BeagleBoard Rev. C3 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard System Reference Manual (rev. C3.0)]. Rev C3 and previous layouts are also available from the [http://beagleboard.org/hardware/design BeagleBoard.org design page]. Please make sure that you ''read, understand and agree'' [http://groups.google.com/group/beagleboard/msg/ee3e1bc927551ffc Jason's mail] before using this.

==Errata==

# ''Boards revision A only'': The DC power jack pinout is incorrect on the PCB layout. DC_5V and GND are switched on PCB layout. Normally, the power jack has DC_5V on the center pin and GND on the sleeve (see Figure 20 of [http://www.beagleboard.org/uploads/BBSRM_6.pdf Beagle HW manual]). But on revision Ax boards the PCB layout has GND on center and DC_5V on sleeve. For this reason it is currently removed. It will be back on the Rev B board. Workaround is to remove wire connecting the two power pins on revision Ax boards and use external [http://amethyst.openembedded.net/~koen/beagleboard/beagle-power-pads.jpg power supply with switched connector] (do not connect anything to the “?” terminal. USB power will be permanently disabled and the board can only be powered from the 5V.) See [http://www.flickr.com/photos/koenkooi/2512038988/ Koen's Beagleboard powermod picture] with short descriptions, too.
# ''Boards revision < A5 only'': There is excess voltage drop across R6 which is used to measure the current consumption on the board. This needs to be a .1 ohm instead of a 1 ohm resistor (SMD 0805). All revision A5 boards have been updated to .1. You can also just solder in a jumper to J2 bypassing the current read point. This issue can cause issues with the USB host port as the voltage supplied to that port can be too low.
# ''Boards revision A only'': User LEDs 0 and 1 are shorted on the layout preventing them from being controlled individually. You need to control both GPIO_149 and GPIO_150 to turn on or off both LEDs. This is fixed in the Rev B boards.
# ''Boards revision < A5 only'': There is an issue where on some boards the 1.8V has excessive noise on it. This is the result of two incorrect parts L1 and L3 being installed on the board. The inductors that were initially installed in the switchers are 100uH and need to be 1uH. This change will require that the board be returned for update. To check for correct parts, have a look to bottom of BeagleBoard. L1 - L3 are the larger parts there. They all have to be labeled with "102" (== 1uH). If any of these three inductors are labeled with "104" (== 100uH) they are wrong and have to be exchanged.
# ''Boards revision A and B'': USB HOST (EHCI) failures. See [http://code.google.com/p/beagleboard/issues/detail?id=15 issue 15] and [http://code.google.com/p/beagleboard/wiki/USBHostTestREPRODUCE USB host test reproduce]. This is a hardware defect. [http://www.beagleboard.org/irclogs/index.php?date=2008-05-29#T00:27:06 Most probably] Rev. B board does not have the EHCI USB connector mounted. Workaround: Use [[BeagleBoard#OTG|OTG port]] with something like [http://trisoft.de/pics/ZHost.JPG mini A to USB A adapter] instead.
# ''Boards revision A and < B4'': Plugging in a USB OTG cable will prevent Beagle from booting (with git kernel), see [http://code.google.com/p/beagleboard/issues/detail?id=19 issue #19], too. This is due to missing filtering capacitor at USB OTG VBUS. When the kernel driver detects that a USB OTG cable is inserted it enables the charge pump to generate VBUS. With no filtering VBUS looks like any switching regulator output with no filtering -- a huge voltage spike when the switch is on, followed by a rapid decay to a low voltage until the next switch on period. The capacitor is there to store energy between the output switch ON and OFF time, the feedback loop in the regulator does sample the cap voltage. Fix is to piggy-back solder a 0603 2.2uF ceramic capacitor to D3, see [http://www.sakoman.net/omap3/beagle/vbus-mod-d3.jpg VBUS modification D3 picture]. Revision B4 boards and newer have this fix applied. Thanks to [http://groups.google.com/group/beagleboard/msg/eb789e15c99a673d Steve] for debugging this!
# ''Boards revision A and < B5'': There is some issue with 32kHz clock depending on system configuration used to clock some OMAP3 peripherals. From this e.g. GPIOs, GPTIMERs, and USB on Beagle might be affected. See [http://code.google.com/p/beagleboard/issues/detail?id=22 Issue 22]. Symptom from this is that after booting Linux kernel serial console hangs after some time and no serial input/output is possible any more. There is one software workaround and one hardware fix for this: (A) Software workaround: Don't use 32kHz timer to clock Linux, instead use MPU timer. (B) Hardware workaround: Remove [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard capacitor C70], which improves the 32kHz clock quality and avoids hang-up. Note: Revision A boards have capacitor C70 [http://www.flickr.com/photos/25691331@N04/2766671437/in/pool-beagleboard at the same location] as rev. B boards. Note: Board revision >= B5 removes capacitor C70.
# ''Random boards, quite rare, revision < B6'': Some random boards and quite rare, show directly after purchasing broken serial communication from host PC to BeagleBoard. Symptom is that you get a new board, get serial output from BeagleBoard in terminal program, but can't type anything at U-Boot prompt (Note: Don't mix this with errata #7. With errata #7 you are able to use U-Boot normally, but Linux prompt input stops after some time). Most users don't have this issue, though. So, first double check your serial configuration ([[BeagleBoardFAQ#Serial_connection_.231|FAQ1]], [[BeagleBoardFAQ#Serial_connection_.232|FAQ2]] and [[BeagleBoardFAQ#Serial_connection_.233|FAQ3]]). Only if you are really, really sure that anything with your serial connection is fine, consider sending the board back doing a [http://beagleboard.org/support/rma RMA request]. This issue was resolved on revision B6 and later boards.

For additional (software) issues and enhancement requests see [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker], too.

Note: BeagleBoard revision B6 uses different package for U9/U11.

==Clocking==

Some [http://www.beagleboard.org/irclogs/index.php?date=2008-07-08#T21:12:23 notes] about (ARM processor) clock rates at BeagleBoard:

* ARM Cortex-A8 processor is currently clocked at 500MHz
* 500MHz is the default used because it is a balance of performance and longevity
* For OMAP35x 600MHz is max recommended
* An additional 720MHz overdrive is supported only on high-speed grade OMAP3530/25 devices as fitted to the Beagleboard C4
* At 600MHz or higher OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600/720MHz is out of spec and no guarantee it will work at all (or not damage itself)

* Also keep in mind that if you go higher you probably want to increase the core voltage. Some of this is mentioned in tables 3-3, 4-15 and 4-16 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:

{| border="1"
||'''ARM'''||'''DSP'''||'''core voltage'''
|-
|720 MHz||520 MHz||1.35V
|-
|600 MHz||430 MHz||1.35V
|-
|550 MHz||400 MHz||1.27V
|-
|500 MHz||360 MHz||1.2V
|}

* For some OMAP3 clock, voltage and power management discussion see [http://focus.ti.com/lit/an/sprt495/sprt495.pdf OMAP3 power management white paper], too.
* The OMAP3 chip on the Beagle lacks the efuses needed for using the SmartReflex technology, see [http://www.beagleboard.org/irclogs/index.php?date=2009-02-26#T10:44:24].
* There is a thermal monitor in the core, you could use to scale frequency up and down

To set CPU clock to 600 MHz, there are two options. Both '''do not''' adjust the voltage, so the system may become unstable:

* The u-boot command "mw 48004940 0012580c" will temporarily set the CPU clock to 600 MHz (not permanent over reset).
* To permanently set the CPU clock to 600 MHz, include the above command in the "bootcmd" variable or equivalent script.

* To set the DSP clock to 430 Mhz use "mw 48004040 0x0009ae0c".

==Power management==

* Detailed OMAP3 Power Management Information can be found [[OMAP_Power_Management|HERE]]
* Latest Linux kernel power management development for TI OMAP SoCs is maintained in [http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=summary Kevin's linux-omap-pm git tree]
* Russ' Beagle HW modifications resulted in [http://groups.google.com/group/beagleboard/browse_thread/thread/197a8ef6b46cc828 8mW sleep for Beagle Board]

Without PM kernel, the Beagle [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm consumes ~1.5 watts idle, however it also uses the same amount under load] (see bottom of that page).

==DLP Pico projector==

Texas Instruments is developing a Pico Video Projector Kit (PVPK) as a peripheral for the Beagle Board. The stand alone pico projector will support VGA resolution (640 x 480), RGB 888 input through a DVI interface. The physical connector on the projector will be HDMI. See [http://groups.google.com/group/beagleboard/msg/10e218972380ee48 mailing list] and [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector] for more details.

It is available from [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23836-ND DigiKey] for $349.

See [http://blog.makezine.com/archive/2009/01/tis_beagleboard_and_dlp_pico_projector.html?CMP=OTC-0D6B48984890 article from Make], too.

DigiKey videos [http://www.youtube.com/watch?v=KBbCdnOj5vg part 1], [http://www.youtube.com/watch?v=zymOmduNWyI part 2] and [http://www.youtube.com/watch?v=Uj19Bi5NYeU part 3].

==Interfacing to Raw LCD Panels==

Currently on Rev A / B boards there is no direct access to the LCD lines before they enter the DVI framer. The REV C2 provides access to these lines. Several projects to interface an LCD to the beagleboard exist:

* [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article
* [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel] workaround method
* [http://www.harbaum.org/till/dvi2par/index.shtml dvi2par cheap diy HDMI to parallel converter]

=Availability=

BeagleBoards, currently Rev. C3 boards, are available from

* [http://www.mouser.com/beagleboard Mouser]
* [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] with part number [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=296-23428-ND 296-23428-ND].

Note: For non-US Digi-Key free shipping orders:

* Click the US flag on the top right corner of [http://dkc1.digikey.com/us/mkt/beagleboard.html Digi-Key] BeagleBoard page to come to the international page
* Select ''Order Online'' for your country
* Add quantity ''1'' and part number ''296-23428-ND''
* Click ''Add to order''

When ordering over 65 EUR / GBP 50 product (BeagleBoard is above), for Europe the price depends on the actual dollar to EUR/GBP rate. On nov 9, 2008 the price was EUR 124 with free shipping.

Note: Some users report that they got some questions from DigiKey to be answered before board shipping is done.

Note: While you get free shipping, most probably you have to pay tax e.g. ordering from Europe. Users report that they had to pay EUR ~34 - 44 VAT + importing taxes (depending on european country), resulting in EUR 137 - 147 ordering from Europe.

Note: For European users, [http://www.ebv.com/fileadmin/products/Press_Print/Campaigns/2009/Product_Campaigns/Texas_Beagle_Board_englisch.pdf EBV Elektronik] sells its own blue version of the board for 179 EUR, which includes all useful accessories (DVI cable, serial cable, USB 2.0 Ethernet, USB hub, 2 GB MMC, power supply, Linux BSP).

Note: German (Europe) users can order through German shops, too. For higher price, though.
* [http://shop.embedded-projects.net/product_info.php/info/p159_BeagleBoard--OMAP-3-.html Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + shipping.
* [http://www.handheld-linux.com/wiki.php?page=Beagle%20Board Handheld-Linux] sells BeagleBoard for EUR 159.00 + shipping.
* [http://www.watterott.com/en/BeagleBoard Watterott electronic] sells BeagleBoard for EUR 142,80 + shipping.

See below for ''hardware'' differences of the revisions. There are no ''software'' differences.

==Revision A==

There are some limited early revision Ax prototypes out there used by some hackers hanging around at #beagle channel on irc.freenode.net. See [[BeagleBoard#Errata|errata]] for limitations.

==Revision B==

Revision B is same as revision A, except
* fix for shorted LEDs 0/1
* fix for wrong power jack pinout
* revision B6 uses different package for U9/U11
Still has USB HOST (EHCI) failures. USB HOST (EHCI) connector isn't mounted.

There are 4 revisions of the B board in the field: B4, B5, B6 and B7.

The most notable difference is the use of the ES3.0 silicon in B6 and B7, other changes are not relevant to software developers.

==Revision C2==
Revision C2 is same as revision B7 except:
* USB HOST (EHCI) is operational on revision C2, with standard USB A female connector.
* Add interface for raw LCDs ([http://groups.google.com/group/beagleboard/msg/2e82c3ed6061d9d2 mockup])
* It uses updated OMAP3 revision. BeagleBoard revisions B4+B5 uses OMAP3 ES 2.1 (engineering sample), while BeagleBoard revision C2 uses ES 3.0. OMAP3 ES 3.0 fixes minor issues:
** updated ARM Cortex A8 silicon (r1p3) fixing a very rare [http://elinux.org/BeagleBoardFAQ#NEON_performance NEON issue] that has not been seen in real code
* Power measurement feature
* Uses [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] OMAP power controller instead of TWL4030
* Three additional PWM signals on the expansion connector added as pin mux options to existing pins ([http://groups.google.com/group/beagleboard/browse_thread/thread/d5872b7c6d74592c?hl=en# message])
* Revision detection (to be able to identify C2 board from older boards by software, e.g. for different pin mux)
* 256MB RAM ([http://groups.google.com/group/beagleboard/msg/3a38d0f21cefd6b1?hl=en message]) (and still 256MB NAND like rev B)

Note: Revision C2 is the first production version, and all orders from from Digi-Key are shipped as Rev C2.

==Revision C3==
As revision C2 boards are [http://groups.google.com/group/beagleboard/msg/e41d3c97aa7d4951 sold out], revision C3 will ship now.

Revision C3 is same as revision C2 [http://groups.google.com/group/beagleboard/msg/037318fbc44139d5 except]:
* Optional RTC [http://parts.digikey.com/1/parts/1454-battery-lith-coin-3v-12-5mm-vert-vl-1220-vcn.html VL1220 series] backup battery
* Mounting holes conected to ground
* Slightly improved S-Video

==Revision C4==
Revision C4 boards are the same as Revision C3 except:
* Processor is 720MHz capable OMAP3
* Improved USB Host PHY power rails

==Clones==
===EBVBeagle===
EBV build and sell their own BeagleBoard called [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], see e.g. [http://fl0rian.wordpress.com/2009/03/08/the-other-beagleboard/].
It is actually a BeagleBoard revision C2 with green PCB boxed with some useful accessories. It comes as a quite complete starter kit with AC adapter, USB to Ethernet adapter, MMC card, USB hub and some cables.
More information in [http://www.ebv.com/en/press-print/news-pr/details/news//press-releas-54.html official press release].

===Mini Board===
[[Mini_Board|ICETEK-OMAP3530-Mini]] is a chinese BeagleBoard clone.

===DevKit 8000===
[[DevKit8000]] is a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard).

===IGEPv2===
[http://www.igep-platform.com/ IGEPv2 Platform] is a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.
* 720MHz OMAP3 Processor
* 512MB RAM / 512MB Flash
===SOM3530===
[[SOM3530]] is a chinese BeagleBoard clone [[System-on-Module]],Dimension 40x40x4mm, Maybe the smallest [[OMAP3530]]-based modules in the world! Including 100M high perfomance ethernet I/F

==BeagleBoard-based products==
* [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book], see [http://gigglehd.com/zbxe/hdforum/files/attach/images/899852/493/987/001/always_innovating_touch_book_0011.jpg]

==Beagle case==

*[http://specialcomp.com/beagleboard/ Special Computing]
*[http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model]

=Adapters=

For quite detailed information about all BeagleBoard peripherals see [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)].

See [[BeagleBoardPeripherals| BeagleBoard peripherals and adapters page]] for useful add ons for Beagle Board.

==Expansion boards==
* [[BeagleBoardPinMux|Expansion Board Support Information]]
* [[BeagleBoard_Trainer|Trainer Boards]] are now available from [http://tincantools.com/product.php?productid=16149&cat=0&page=1&featured TinCanTools] for $59.00
** I2C interface(+3.3v or +5v selectable)
*** Can be used with the Nintendo Wii NunChuk interface
*** Pin compatible with WiiChuk Adapter
*** WiiChuk Adapter is available from SparkFun
** SPI inteface (+3.3v)
** GPIO's(+3.3v)
** Large prototyping area (0.1" x 0.1" matrix with access to power bus)
** Atmega328 processor (user programmable)
*** Arduino compatible
*** ATmega328 power is +3.3v or +5v selectable
*** Communicate to the ATmega328 via the BeagleBoard's second RS-232 uart
* [[BeagleBoard Zippy]] expansion board is now available from [http://www.tincantools.com/product.php?productid=16147&cat=0&page=1&featured TinCanTools] for $79.00. basic specs are:
** Battery Backed RTC
** Second MMC slot
** 10BaseT Ethernet
** Second RS-232
** +5V level I2C
** AT24 EEPROM
* [https://sourceforge.net/apps/mediawiki/beagleserver/index.php?title=Main_Page BeagleServer expansion board] is an Open Hardware project. Currently a high level design note is available, which describes the components to be used. It aims at the following specifications :
** Aims at transforming a Beagleboard or IGEPv2 into a full-blown home server that could cater to home automation needs
** Compatible with both the Beagleboard and the IGEPv2
** 12V battery powered, or mains-powered (accepts 9 ~ 18V)
** Enough power for an internal 2.5" or 3.5" hard-disk, USB-attached
** +3.3V and +5V I2C; +5V I2C is buffered with a line buffer accepting a larger capacitance which allows I2C devices at distances up to 50m
** I2C to 1-wire hub (using DS2482-800 which is supported by OWFS); plugging in 1-wire devices lights a LED which makes it easy to confirm if a 1-wire device is detected.
** Real time clock with super-capacitor backup
** Internal monitoring of the HW health (power supplies + temperature)
** Some relays
** Ethernet-based console port
** a few other options (RS232 interface with CTS and RTS, SPI port, S-video, additional SD-card)
* [http://www.hy-research.com/beagle_expansion.html HY Research] has some expansion board basics and example.
* [http://www.hervanta.com/stuff/Beaglebot#Expansion_Board Beaglebot] uses a custom extension board.
* [http://beagleboard.org/leopard Leopard Board], a Beagle buddy web camera
* There is also a VGA DB15 adapter board under development for the Rev C2 board. It should be available through a yet to be annnounced outlet.

In Canada, check out [[http://robotcraft.ca RobotCraft]] in London, Ontario for expansion boards.

==JTAG==

Depending on your JTAG tool, you'd need a 14-pin to 20-pin adapter to use an ARM debugger. The 14-pin TI JTAG connector is used on BeagleBoard and is supported by a large number of JTAG emulation products.
See [[BeagleBoardJTAG]] for more information.

==RS232==

The pinout on the beagle board is "AT/Everex" or "IDC10". You can buy [http://www.pccables.com/07120.htm IDC10 to DB9M adapters] in many places as they are commonly used for old PCs. Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available. You can also probably rip one of those cables out of any old desktop computer, where it's being used to support the serial port. Be careful, though -- some of those cables will have that tenth hole filled in so you'd have to snap off the extraneous pin on your BeagleBoard. Keep looking until you find a cable with all 10 holes open.

Depending on your local configuration, you may need a [http://en.wikipedia.org/wiki/Null_modem 9-Pin NullModem] cable to connect BeagleBoard to serial port of your PC. From [http://www.tincantools.com/ TinCanTools] there is a [http://www.tincantools.com/product.php?productid=16144&cat=0&page=1&featured RS-232 DB-9 adapter] and [[media:flyswatter-ti-uart.pdf|adapter schematic]] available.

==USB-to-Serial Converter==

Since many systems no longer come with an actual serial port, you might need to pick up a USB-to-serial converter at your local computer store to connect to your BeagleBoard. Be warned that some of them simply do not work. Many of them are based on the Prolific chip, and require the pl2303 module to be loaded. But even when two converters appear to have exactly the same characteristics as listed in /var/log/messages, if you simply can't get one to work, be ready to try a different one.

==USB==
There are two USB ports on the BeagleBoard, one with an EHCI controller and another with an OTG controller. As of Rev B4, the usb EHCI has been removed because of a hardware defect. Rev C will include USB EHCI working properly.

===EHCI===
The HS ([http://en.wikipedia.org/wiki/USB#USB_signalling HighSpeed]) USB [http://en.wikipedia.org/wiki/EHCI ECHI] controller on OMAP3 on BeagleBoard supports high-speed only. This simplifies the logic on the device. FS/LS (FullSpeed/LowSpeed) devices, such as keyboards and mice, require going through a high-speed USB 2.0 hub.

According to the BeagleBoard System Reference Manual Rev C2, the EHCI port can source 5V at 500mA which is enough to power a hub and several low-power devices. However, this is only true if the BeagleBoard is powered through its power jack from a well-regulated 5V external power supply. If the BeagleBoard is powered through the OTG port, the EHCI port sources an "extremely limited" ampount of power (probably 100mA or so) so you'll need a "self-powered" USB 2.0 hub with its own external power supply. [Reference: Sections 5.6 and 7.2 of the BBSRM Rev C2.2.]

'''Hardware issue on rev C3''' - the EHCI port on some rev C3 boards is unstable and will disconnect hubs/devices. Symptoms are: devices are disconnected from the port and cannot be reconnected without a reboot. It appears the shared 1.8V rail between the OMAP3530 and the power chip was getting noisy. Suggested solution (works on many boards) is adding a 0.22 uF 0805 package SMT capacitor atop the existing cap on C97. If SMT parts are not available, some boards can be repaired by a 0.22 uF through-hole capacitor across GND and VIO_1V8 on the expansion connector. See [http://groups.google.com/group/beagleboard/browse_thread/thread/5b8385f0bb1f63da] for more information.

===OTG===
The HS USB OTG ([http://en.wikipedia.org/wiki/USB_On-The-Go OnTheGo]) controller on OMAP3 on the BeagleBoard does have support for all the USB 2.0 speeds (LS/FS/HS) and can act as either a host or a gadget/device. The HS USB OTG port is used as the default power input for the BeagleBoard. It is possible to boot the BeagleBoard using this USB port.

When using the OTG port in host mode, you must power the BeagleBoard using the +5V power jack. If you connect a USB hub, you'll probably also need external power for the USB hub as well, because according to the Hardware Reference manual the BeagleBoard OTG port only sources 100 mA. This is enough to drive a single low-power device, but probably won't work with multiple devices.

The Linux kernel needs to know you want to use the OTG port in host mode. I believe OTG ports are supposed to figure this out for themselves using the OTG Host Negotiation Protocol, but for now the Linux kernel may need some help. Specifically, Pin 4 (ID) of the OTG connector needs to be shorted to Pin 5 (GND) by using a [http://trisoft.de/pics/ZHost.JPG 5-pin USB Mini-A plug] which shorts these pins together in the plug. A [http://en.wikipedia.org/wiki/USB#USB_cables 5-pin USB Mini-B plug] leaves Pin 4 floating. Unfortunately, most USB Mini plugs are unmarked as to whether they are "A" or "B".

You can find "mini A" adapters that have Pin 4 shorted and offer out a full-sized USB A Female jack [http://www.electronicproductonline.com/catalog/product_info.php?products_id=2043 here.]
<table>
<tr><td>
Since the right cables might be hard to get, you simply can
* short circuit the two pins encircled in red in the image to the right. You can do this by running a wire between the two pins. That at least allows easier undoing the change. Actually you could even have a small switch or so between 4 and 5.
or
* use a "mini B" cable (easier to get) and try the soldering of the two pins at the cable's connector. Depending on the cable it should be possible to open the plastic covering of mini-B port with a sharp-edged knife, then solder the two pins together, close the covering again and use some tape. This leaves the BeagleBoard unmodified.
</td><td>[[Image:usb_otg.png]]</td></tr></table>
The Rev C BeagleBoard has a pair of pads labeled J6 on the back of the board under the OTG connector. Shorting these pads together with a wire or solder blob connects pins 4 and 5.
See Figure 20 in the BeagleBoard System Reference Manual Rev C2.2.

==DVI==

DVI-D connection on BeagleBoard uses a [http://en.wikipedia.org/wiki/HDMI HDMI connector]:

''HDMI is backward-compatible with the single-link Digital Visual Interface carrying digital video (DVI-D or DVI-I, but not DVI-A) used on modern computer monitors and graphics cards. This means that a DVI-D source can drive a HDMI monitor, or vice versa, by means of a suitable adapter or cable, but the audio and remote control features of HDMI will not be available.''

BeagleBoard can be connected to a DVI monitor using HDMI female to DVI male cable.

=BootRom=

OMAP3 on BeagleBoard contains a BootRom. With this, BeagleBoard can boot without any code in permanent storage (NAND) or from peripherals. This is useful for first board bring up or if your BeagleBoard is bricked. For more information about BootRom booting see [http://www.ti.com/litv/pdf/sprufd6a SPRUFD6].

==User button==

With user button on BeagleBoard you can configure boot order. Depending on this button, the order used to scan boot devices is changed. The boot order is (the first is the default boot source):

* User button ''not'' pressed: NAND -> USB -> UART -> MMC
* User button ''is'' pressed: USB -> UART -> MMC -> NAND

Technically speaking, the user button configures pin SYS.BOOT[5]. See [http://focus-webapps.ti.com/general/docs/sitesearch/searchsite.tsp?selectedTopic=1653260327&numRecords=25&searchTerm=sprufd6&statusCode=null SPRUFD6] for more details.

==Serial and USB boot==

Historically, using OMAP3's boot ROM for serial and USB boot, there are several tools around. The newest are Nishanth' ''OMAP U-Boot Utils'', while there are still some older tools for serial boot and USB boot. It is also possible to access the [[u-boot environment variables in linux|u-boot env from linux]].

===OMAP U-Boot Utils===

Nishanth' [http://code.google.com/p/omap-u-boot-utils/ OMAP U-Boot Utils] provide

* ''pserial'' - OMAP specific utility which downloads a file in response to ASIC ID over serial port.
* ''pusb'' - OMAP specific utility which downloads a file in response to ASIC ID over USB connection.
* ''ucmd'' - Send a command to U-Boot and wait till a specific match appears.
* ''ukermit - Download a file from host without using kermit to U-Boot.

See [http://nishanthmenon.blogspot.com/ Nishanth' blog] and [http://groups.google.com/group/beagleboard/browse_thread/thread/c5bfb1b8ed528b52# announce mail], too.

===Serial boot===

Besides Nishanth' ''OMAP U-Boot Utils'', to boot from USB or UART, you need a PC tool which talks with OMAP BootRom and speaks the correct protocol to download ARM target code to BeagleBoard. Currently there are two older (experimental) tools for UART boot:

* [http://omapzoom.org/gf/project/omaptools/wiki PC Serial Boot perl script]
* [http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555 Linux C utility] (not working yet with below target code)

See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.

===USB boot===

Besides Nishanth' ''OMAP U-Boot Utils'', for USB boot, there is currently one (experimental) tool to boot BeagleBoard over USB:

* [http://groups.google.com/group/beagleboard/browse_thread/thread/2b9e99886bb7a747 Linux C utility]

See [http://groups.google.com/group/beagleboard/browse_thread/thread/ae2c601ebe104a4 USB and serial download target code] for some example target code to be downloaded to OMAP3 on BeagleBoard.

See [[BeagleBoardRecovery#USB_recovery|USB recovery section]] how to use USB boot for board recovery.

==NAND boot==

See [[BeagleBoardNAND|NAND boot]] article.

==MMC/SD boot==

Currently, [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] is the only working way for first board bring up.

===MMC/SD formatting===

As described in above MMC/SD boot description, you have to ''create a bootable partition on MMC/SD Card''. This can be done using e.g. Windows or Linux tools.

'''Windows'''

See ''HP USB Disk Storage Format Tool 2.0.6'' description on [http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard boot the BeagleBoard with MMC/SD] page.

'''Linux'''

Please see [http://wiki.omap.com/index.php?title=MMC_Boot_Format OMAP3 MMC Boot Format].

===Dual partition card===

You can [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat create a dual-partition card], booting from a FAT partition that can be read by the OMAP3 ROM bootloader and Windows, then utilizing an ext2 partition for the Linux root file system.

To mount second ext2 partition as root file system (e.g. containing contents of [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode rd-ext2.bin]) use kernel boot arguments (e.g. in uboot using ''setenv bootargs''):

console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait

===U-Boot booting===

If your MMC/SD card formatting is correct and you put [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode MLO, u-boot.bin and uImage] on the card you should get a u-boot prompt after booting beagle board. E.g. (output from terminal program with 115200 8N1):

...40T.........XH.H.U�..Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector

717948 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)

OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)
DRAM: 128 MB
Flash: 0 kB
NAND:256 MiB
In: serial
Out: serial
Err: serial
Audio Tone on Speakers ... complete
OMAP3 beagleboard.org #

Using this u-boot prompt, you now can start kernel uImage stored on MMC card manually:

OMAP3 beagleboard.org # mmc init
OMAP3 beagleboard.org # fatload mmc 0:1 0x80000000 uimage
OMAP3 beagleboard.org # bootm

If you like to make that happen every boot:

OMAP3 beagleboard.org # set bootcmd 'mmc init ; fatload mmc 0:1 0x80000000 uimage ; bootm' ; saveenv

=Code=

Code and binaries for BeagleBoard are available at various places.

==Binaries==

BeagleBoard pre-built binaries and source code can be found at [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode Beagle source code] and [http://code.google.com/p/beagleboard/downloads/list downloads] page. These are the locations where "official" TI code is available. Please note that this code is mainly for reference and testing. More up to date binaries and code is available by community. Community took (parts) of TI reference code, improves and updates it.

Actually, [http://www.angstrom-distribution.org/node/47 Koen's prebuilt Beagleboard demo images] are up to date binaries including e17 as window manager, the abiword word processor, the gnumeric spreadsheet application, a NEON accelerated mplayer and the popular NEON accelerated omapfbplay which gives you fullscreen 720p decoding. The [http://www.angstrom-distribution.org/demo/beagleboard www.angstrom-distribution.org/demo/beagleboard] directory should contain all the files you need:

* [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin u-boot.bin]
* [http://www.angstrom-distribution.org/demo/beagleboard/MLO MLO]
* [http://www.angstrom-distribution.org/demo/beagleboard/uImage uImage]
* [http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090104-beagleboard.rootfs.tar.bz2 rootfs]

See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat beagle wiki] on how to setup your SD card to use all this goodness.

==Source==

Besides above binary and source images (TI's and communities one), for various parts of Beagle software stack there are community supported [http://git.or.cz/ git] repositories available.

===X-Loader===

Steve did some work to consolidate and update X-Loader from various sources and put it in a [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=x-load-omap3.git;a=summary X-Loader git repository]. Get it by

git clone git://gitorious.org/x-load-omap3/mainline.git xloader
cd xloader/

Build:

make distclean
make omap3530beagle_config
make

Result will be a ~20k sized ''x-load.bin'' in main directory.

===U-Boot===

[http://www.denx.de/wiki/U-Boot/WebHome Mainline U-Boot] has good support for BeagleBoard. Get it by:

git clone git://git.denx.de/u-boot.git u-boot-main
cd u-boot-main
git checkout --track -b omap3 origin/master

Build (assuming [[ARMCompilers#Recommendations|Code Sourcery GCC]]):

make CROSS_COMPILE=arm-none-linux-gnueabi- mrproper
make CROSS_COMPILE=arm-none-linux-gnueabi- omap3_beagle_config
make CROSS_COMPILE=arm-none-linux-gnueabi-

Result will be a ~160k sized ''u-boot.bin'' in main directory.

Note: Due to (patch and binary) size, BeagleBoard splash screen was removed from upstream version. If you want it back, use [http://groups.google.com/group/beagleboard/browse_thread/thread/3ad9b803a3418624 U-Boot v1 BeagleBoard splash screen patch].

Note: For experimental U-Boot patches not ready for mainline yet, Steve's [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=summary Beagle U-Boot git repository] is used to test them. Get it by:

git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3
cd u-boot-omap3
git checkout --track -b omap3-dev origin/omap3-dev

Note: For changing the screen resolution there is one option modifying the file in "include/configs/omap3_beagle.h" and adjusting the maximum resolution before compiling as describe in [http://gitorious.org/linux-omap-dss2/linux/blobs/master/Documentation/arm/OMAP/DSS ARM OMAP2/3 Display Subsystem]

Note: For beagleboard revision C4, above sources will not work. USB EHCI does not get powered, hence devices are not detected...
get a patched version of u-boot from http://gitorious.org/beagleboard-default-u-boot/beagle_uboot_revc4/

Note: If you want to activate I2C from the expansion header, modify board/ti/beagle/beagle.h :

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | EN | M4)) /*GPIO_168*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | EN | M4)) /*GPIO_183*/

to

MUX_VAL(CP(I2C2_SCL), (IEN | PTU | DIS | M0)) /*I2C2_SCL*/
MUX_VAL(CP(I2C2_SDA), (IEN | PTU | DIS | M0)) /*I2C2_SDA*/

===Linux kernel===

[http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Git repository] of [http://muru.com/linux/omap/ OMAP Linux kernel] contains Beagle support. Get it by:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git linux-omap-2.6
cd linux-omap-2.6

Build:

make distclean
make omap3_beagle_defconfig
make menuconfig # only needed if you want to change the default configuration
make uImage

The result will be a ''uImage'' in ''arch/arm/boot/'' directory.

If you use the OE toolchain and want to build outside of the OE tree you should do
ARCH=arm
PATH=~/oe/tmp/cross/armv7a/bin:~/oe/tmp/staging/i686-linux/usr/bin:$PATH # add cross tools to your path
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- distclean
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_beagle_defconfig
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- menuconfig # only needed if you want to change the default configuration
make CROSS_COMPILE=arm-angstrom-linux-gnueabi- uImage
Note: the staging dir in the path is for mkimage. If you've build a kernel before with oe, the program should be there

Note: If you are interested in kernel development have a look to [[BeagleBoardLinuxKernel|manually compiling BeagleBoard kernel]], too.

===Experimental kernel patches and hacks===

Some beagle developers maintain their own kernel experimental patches and hacks not ready for upstream:

* [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap Koen's collection of kernels patches for OE] and the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/packages/linux/linux-omap_git.bb list of relevant patches]
* [http://www.sakoman.net/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/test Steve's kernel tree], a clone of main OMAP git with additional patches, mainly beagle audio (ASOC) related.
* [http://git.mansr.com/?p=linux-omap;a=summary Mans' kernel tree], a clone of main OMAP git with additional patches, mainly display & framebuffer related.
* [http://www.bat.org/~tomba/linux-omap.html Tomi's kernel tree], a clone of main OMAP git with display sub-system patches, replacing the entire display driver with one that is the likely direction moving forward.

=Compiler=

TI OMAP3530 processor on BeagleBoard contains an ARM Cortex-A8 general purpose processor and a TMS320C64x+ DSP.

==ARM==

There is broad compiler support including gcc - please see [http://www.elinux.org/ARMCompilers ARM Compilers]

==C64x+ DSP==

A free C64x DSP compiler is available as [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html Linux hosted C6x Code Generation Tools] (TMS320C6000 C/C++ CODE GENERATION TOOLS 6.1.3 July 2008).

Note: my.TI account required. You may create an account [https://my.ti.com here]

Note: Old c6000 Linux compiler available on [ftp://ftp.ti.com/pub/cs/linux_cgt500.tar.gz TI FTP site]. Does NOT support c64x+ core in OMAP3 devices. Not recommended.

You can also utilize the [http://focus.ti.com/dsp/docs/dspsupportaut.tsp?familyId=44&sectionId=3&tabId=416&toolTypeId=30 full-CCS free evaluation tools for 120 days], but they currently require purchase to upgrade to service release 9 to support full JTAG debugging with supported JTAG hardware.

See [[BeagleBoard/DSP_Howto| BeagleBoard DSP howto]] for information about how to use the DSP.

=Cortex A8 ARM features =

ARM Cortex-A8 in OMAP3 is a high performance dual-issue applications processor which reaches a performance of 2.0 DMIPS/MHz (compared to ARM11 at 1.2 DMIPS/MHz). It is ARM v7 architecture, which is fully backwards compatible with application code for previous ARM processors.

It includes a floating point unit (ARM VFPv3 architecture) and the ARM NEON SIMD instruction set.

See [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] article for an intro into VFP-lite and NEON.

===ARM NEON===

NEON is a 64/128-bit wide SIMD vector extension for ARM, which has been architected to be an efficient C compiler target as well as being used from assembly language. It has 32x 64-bit registers (with a dual view as 16x 128-bit registers) which can hold the following datatypes:
* 64-bit signed/unsigned
* 32-bit signed/unsigned
* 32-bit single precision floating point
* 16-bit signed/unsigned
* 8-bit signed/unsigned

The key advantage of NEON is very high performance vector math processing, whilst being easy to program. It is the same thread of control as the ARM (but different instructions), and is supported by the same tools, debuggers and operating systems.

The NEON instruction set is documented in ARM's [http://infocenter.arm.com/help/topic/com.arm.doc.dui0204i/DUI0204I_rvct_assembler_guide.pdf RealView Compilation Tools Assembler Guide].

For NEON optimized libraries see [http://www.us.design-reuse.com/news/18429/aac-mp3-mpeg-4-h-264-fft-openmax-cortex-a8-neon-arm11-processors.html ARM Releases AAC, MP3, MPEG-4, H.264 and FFT OpenMAX DL Libraries, Highly Optimized for Cortex-A8/NEON and ARM11 Processors]. Note: Read the [http://www.arm.com/products/esd/openmax_v7libraries.html EULA].

NEON is currently used by
* ffmpeg - libavcodec used by mplayer, omapfbplay, and many other linux applications
* libpixman - used by X.org and Mozilla & Webkit browsers to render text and graphics
* Bluez - official Linux Bluetooth stack

=== ARM Cortex Floating Point ===

There are two types of instructions in the ARM v7 ISA that handle floating point:

1) '''VFPv3''' Floating point instruction set (used for single/double precision scalar operations).
These is used by gcc for C floating point operations on 'float' and 'double'

2) '''NEON''' [http://www.arm.com/products/multimedia/neon/ NEON] vectorized single precision operations (2 values in a D-register, or 4 values in a Q-register)
These can be use by gcc when -ftree-vectorize is enabled and -mfpu=neon is specified, and the code can be vectorized. In other cases the VFPv3 scalar ops will be used.

ARM Cortex-A processors have separate floating point pipelines that handle these different instructions.

On Cortex-A8, the designers' focus was on the NEON unit performance which can sustain 1 cycle/instr throughput (processing 2 single-precision values at once). The scalar VFPv3 FPU cannot achieve this level of performance (cycle timings are in the Cortex-A8 TRM download), but it is still a lot better than doing floating point using integer instructions.

If you need the highest performance floating point on Cortex-A8, you need to use single precision and ensure the code uses the NEON vectorized instructions:
* use gcc with -ftree-vectorize (possibly modify source code to make it vector friendly)
* use NEON instrinsics (#include <arm_neon.h>, float32x2_t datatype and vmul_f32() etc)
* use NEON asm directly

Keep in mind that mixing NEON and ARM load/stores can sometimes stall significantly. See [http://hardwarebug.org/2008/12/31/arm-neon-memory-hazards/ this link] for more info.

On Cortex-A9, there is a much higher performance floating point unit which can sustain 1 cycle/instr throughput, with low result latencies.

=Board recovery=

If you played e.g. with the contents of the [http://www.sakoman.net/omap3/flash%20procedure.txt NAND], it might happen that the Board doesn't boot any more (without pressing user button) due to broken NAND content. See [[BeagleBoardRecovery|BeagleBoard recovery]] article how to fix this.

=Development environments=

Instead of just using compiler + editor, you can use complete image create "development tool chains" which integrate compiler, build system, packaging tools etc. in one tool chain.

==OpenEmbedded==

For [http://www.openembedded.org/ OpenEmbedded] (OE), there are some hints how to [http://www.beagleboard.org/irclogs/index.php?date=2008-04-29#T13:06:25 start with OE for BeagleBoard]. See [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] and [http://wiki.openembedded.org/index.php/Getting_Started OpenEmbedded getting started] as well.

In the OE getting started document, for BeagleBoard replace ''MACHINE = "om-gta01"'' by ''MACHINE = "beagleboard"''. After confirming ''bitbake nano'' works, try ''bitbake console-image''. The first time you run bitbake OE will download all the needed source and build the tool chain. This will take several hours. After all went fine, the output is in ''${OE_ROOT}/tmp/deploy/glibc/images/beagleboard''.

Note: Koen has some BeagleBoard [http://amethyst.openembedded.net/~koen/index.php?path=beagleboard/ source and binary images] built with OE. There, ''Angstrom-console*'' images don't include an X server, you can still use a e.g. DVI-D screen with console, but you won't have a GUI. ''Angstrom-x11*'' images contain an X server.

===One very important note:===

It's important to have an X-Loader on your Beagleboard that uses the uImage on the SD Card that goes with Angstrom. The B6 Beagleboards do not appear to come with such an X-Loader. So you likely will have to upgrade the X-Loader. Here's what to do:
* Make an SD Card with the [http://www.angstrom-distribution.org/demo/beagleboard Angstrom Demo files]. See the [http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat Beagleboard Wiki Page] for more info on making the SD Card.
* Put the SD Card in the Beagle, and boot up to the U-Boot Prompt.
* Do the first six instructions in the [http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing Flashing Commands with U-Boot] section.
* Reboot the Beagle to see that the new X-Loader is properly loaded.

This will update the X-Loader to a newer version that will automatically load uImage from the SD Card when present -- rather than always using the uImage in the Beagleboard NAND.

==Eclipse==
The Eclipse [http://www.eclipse.org/cdt/ C Development Tools Project] provides a "fully functional C and C++ Integrated Development Environment (IDE) for the Eclipse platform". The Eclipse [http://www.eclipse.org/dsdp/tm/ DSDP Target Managment Project] provides a "Remote System Explorer" (RSE) plugin that simplifies downloading files to the BeagleBoard and editing files on the BeagleBoard within the Eclipse IDE. A Linux Target Agent is available as part of the [http://wiki.eclipse.org/DSDP/TM/TCF_FAQ Target Communications Framework (TCF) component]. Info on how RSE is used for e.g. Gumstix development is described in [http://groups.google.com/group/beagleboard/browse_thread/thread/509831f7c24cb79f# this post].

==Android==
[http://source.android.com Android] platform is a software stack for mobile devices including an operating system, middleware and key applications. Developers can create applications for the platform using the [http://code.google.com/android/ Android SDK]. Applications are written using the Java programming language and run on Dalvik, a custom virtual machine designed for embedded use which runs on top of a Linux kernel.

There are several resources for Android on OMAP (Beagle) available:

'''OMAPZOOM'''

You can find Android port for OMAP ZOOM architecture on [https://gforge.ti.com/gf/project/omapandroid/ OMAPZoom.org's wiki page on Android].

'''EMBINUX'''

[http://beagleboard.org/project/android Beagleboard.org's Android project page] [http://groups.google.com/group/beagleboard/browse_thread/thread/7b422f113ce489b5 announced], the successful porting of Android on Beagle board by [http://embinux.com EMBINUX™] Team. The [http://labs.embinux.org/git/ source code] and [http://www.embinux.com/download_beagle.php binaries] are available for download and review.

Detailed instructions, for porting Android on Beagle Board, are available [http://labs.embinux.org/index.php/Main_Page here]. Current release supports input devices (keyboard/mouse), network and sound.

You can [http://in.youtube.com/watch?v=nADn_vNVEKw watch Android booting] on Beagle Board.

'''Android on OMAP wiki'''

Wiki page for Andorid on OMAP can be found [[Android on OMAP|here]]

'''0xdroid'''

[http://gitorious.org/0xdroid 0xdroid], the enhanced version of Android on Beagleboard by [http://0xlab.org 0xlab]. The [http://gitorious.org/0xdroid source code], [http://downloads.0xlab.org/ pre-built binaries], and [http://code.google.com/p/0xdroid/issues/list issue tracker] are available for review and reference.

The latest development supports OMAP audio, OMAP video overlays, ARM Cortex A8 NEON/Thumb2 performance optimizations, mouse cursor, hot-pluggable USB keyboard & mouse, user-friendly installer for system image, and various Android tweaks. Detailed instructions for 0xdroid are available through [http://code.google.com/p/0xdroid/wiki/MainPage Google Code wiki].

You can [http://www.youtube.com/watch?v=v6wdTOHrwQw watch 0xdroid demo video] on Beagle Board.
* [http://www.youtube.com/watch?v=v6wdTOHrwQw 0xdroid demo video (1)]
* [http://www.youtube.com/watch?v=ol9LWBKXXwQ 0xdroid demo video (2)]

==Mamona==

[http://dev.openbossa.org/trac/mamona/wiki Mamona] is an embedded Linux distribution for ARM EABI. The main goal of the Mamona Project is to offer a completely open source alternative/experimental platform for [http://maemo.org/ Maemo] using only free and open source components. Mamona [http://rsalveti.wordpress.com/2008/09/12/mamona-02-is-out 0.2] [http://franciscoalecrim.com/blog/2008/07/29/mamona-working-with-beagleboard/ supports] [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 OMAP3430 Software Development Platform (SDP)], so you can also use it at Beagle (OMAP3530), too. Work is being done to officially support Beagle.

==Ubuntu==

See [[BeagleBoardUbuntu|Ubuntu (ARM)]] installation guide how to install Ubuntu (ARM) on BeagleBoard.

==Debian ARM==

See [[BeagleBoardDebian|Debian (ARM)]] installation guide how to install Debian (ARM) on BeagleBoard.

==Handhelds Mojo ARM==

See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard. (The Mojo project is no longer active, see the Official Ubuntu ARM-port above instead)

==Scratchbox==

[http://www.scratchbox.org/ Scratchbox] is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. See [http://felipec.wordpress.com/2009/06/07/installing-scratchbox-1-and-2-for-arm-cross-compilation/ Felipe's Scratbox 1 and 2 intro], too.

=Software hints=

This section collects hints, tips & tricks for various software components running on beagle.

==QEMU==

[[Qemu|QEMU]] [http://vm-kernel.org/blog/2008/12/15/linux-is-running-on-qemu-omap3/ supports OMAP3] being able to boot a BeagleBoard Linux kernel.

==Linux hints==

See BeagleBoard [http://code.google.com/p/beagleboard/wiki/LinuxHints Google wiki Linux hints] page (for Linux WTBU (Wireless TI Business Unit) kernel [http://code.google.com/p/beagleboard/wiki/BeagleSourceCode 2.6.22]). Currently featuring:

* Switching video output between DVI-D and S-Video
* Disabling framebuffer blanking
* Listing USB devices

==lmbench==

Avik posted a detailed [http://groups.google.com/group/beagleboard/browse_thread/thread/c8b8f07ce61161a1 step-by-step procedure] to run [http://sourceforge.net/project/showfiles.php?group_id=14418 lmbench] on Beagle.

==Mediaplayer (FFmpeg)==

There is a thread how to get a [http://groups.google.com/group/beagleboard/browse_thread/thread/9b8025fc15120fd9# mediaplayer] with NEON optimization (FFmpeg) to run on Beagle. Includes compiler hints and patches.

==Java==

When using the [[BeagleBoard#OpenEmbedded|OpenEmbedded]]-based Angstrom image you have the following options of Java support:
* JamVM + GNU Classpath (small vm, fast interpreter, J2SE-like)
* Cacao + GNU Classpath (JIT compiler, J2SE-like)
* PhoneME Advanced Foundation (JIT compiler, CDC)

Java support in OpenEmbedded/Angstrom ([http://wiki.openembedded.net/index.php/Java details]) is provided voluntarily through [http://jalimo.org Jalimo].

See a [http://groups.google.com/group/beagleboard/browse_thread/thread/102f627253919783# post at mailing list], too.

OpenEmbedded users can add the [http://evolvis.org/scm/?group_id=11 Jalimo Subversion repository] as an overlay (instructions are in the repository). This will allow them to build OpenJDK packages. Inclusion of these recipes in mainline OpenEmbedded is planned but still ongoing.

The recipes offer the following functionality:

* OpenJDK + Hotspot (Zero port) (all J2SE functionality, including JVMTI, interpreted only)
* OpenJDK + Cacaco (all J2SE library features, missing JVMTI, decent JIT compiler)
* OpenJDK + Hotspot (Shark port) (not working yet)

[http://camswl.com/ Edward Nevill] from ARM Ltd. is working on interpreter optimization in Zero for ARM.

People interested in getting this stuff working better should contact people on:
* [http://evolvis.org/mail/?group_id=11 Jalimo Mailinglist]
* [http://mail.openjdk.java.net/mailman/listinfo/distro-pkg-dev Icedtea Mailinglist]

You should also check out IcedTea's [http://iced-tea.org/wiki/FrequentlyAskedQuestions FAQ].

=Graphics accelerator=

OMAP3530 used on BeagleBoard contains a graphics accelerator (SGX) based on the SGX core from [http://www.imgtec.com/ Imagination Technologies]. [http://www.imgtec.com/powervr/powervr-graphics.asp PowerVR] SGX530 is a new generation of programmable PowerVR graphics and video IP cores. Only the kernel portions of Linux drivers will be open source. The PowerVR folks will provide binary user-space libraries. Using the EMail contact at [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12700&contentId=27458 TIs Mobile Gaming Developers page] there are Linux v2.6 OMAP3430 SDKs for OMAP3 Zoom and SDP supporting OpenGL ES v2.0, OpenGL ES v1.1 and OpenVG 1.0 available.

Tutorial:
* [http://code.google.com/p/beagleboard/wiki/HowtoUseSGXunderAngstrom How to use SGX with Angstrom in OE]

Some videos:

* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]
* [http://www.youtube.com/watch?v=24TXpqa9jG0&feature=related OpenGL ES 2.0 shader effects on OMAP3]
* [http://www.youtube.com/watch?v=-UFUbqoNgs8&feature=related 3D User Interface on OMAP3 Platform]
* [http://www.youtube.com/watch?v=8KcNgeUriqA 3D Mapping using OpenGL ES 2.0 on OMAP3 Platform]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.hitlabnz.org/wiki/EmbeddedAR An Augmented Reality application combining ARToolkit and OpenGL ES 2.0]

=Beginners guide=

You just got your new BeagleBoard, and now? See [[BeagleBoardBeginners|beginners guides]].

=FAQ=

For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].

=Links=
==Home page==
[http://beagleboard.org/ beagleboard.org] (beagle board home)
* Using [http://www.google.de/ Google] you can search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''

==Manuals and resources==
* [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. C2)]
* [http://beagle.s3.amazonaws.com/BBSRM_7_2_0.pdf BeagleBoard HW Reference Manual (rev. B7)]
* [http://www.beagleboard.org/uploads/BBSRM_6.pdf BeagleBoard HW Reference Manual (rev. B6)]
* [http://www.beagleboard.org/uploads/BBSRM_B5.pdf BeagleBoard HW Reference Manual (rev. B5)]
* [http://www.beagleboard.org/uploads/Beagle_HRM_B4.pdf BeagleBoard HW Reference Manual (rev. B4)]
* [http://www.beagleboard.org/uploads/Beagle_HW_Reference_Manual_A_5.pdf BeagleBoard HW Reference Manual (rev. A5)]
* [http://focus.ti.com/docs/prod/folders/print/omap3530.html OMAP3530] processor description and manuals
* [http://code.google.com/p/beagleboard/ Beagle at code.google.com]
* [http://focus.ti.com/dsp/docs/dspsupporttechdocs.tsp?sectionId=3&tabId=409&familyId=1526&documentCategoryId=4&techDoc=4 OMAP3530/25 CBB BSDL Model]
* [http://www.micron.com/products/mcps/beagleboard Micron's multi chip packages (MCPs) for Beagle Board]
* [http://beagleboard.org/resources Beagleboard resources page with hw docs]
* Some [http://www.rasterman.com/ performance comparison] of BeagleBoard Rev. B with some other ARM/PC systems.
* OMAP3 pinmux [http://www.hy-research.com/omap3_pinmux.html setup]
* [http://elinux.org/BeagleBoardPinMux OMAP3 eLinux pinmux page]

==Contact and communication==
* [http://groups.google.com/group/beagleboard Beagle board discussion list]
* [http://code.google.com/p/beagleboard/issues/list Beagle board open point list & issue tracker]
* [http://beagleboard.blogspot.com/ Beagle board blog]
* [http://feeds.feedburner.com/BeagleBoard Beagle board RSS feed]
* Chat:
** [http://beagleboard.org/chat Beagle Board chat]
** IRC: #beagle channel on irc.freenode.net
** [http://www.beagleboard.org/irclogs/index.php IRC archive]
* [http://www.beaglesride.org/ Beagles Ride], a site about building a community around the BeagleBoard focused on in vehicle applications
* [http://www.beagleboard.de/ German Beagle Board Forum and Wiki]

==TI resources==
* [http://opensource.ti.com/ TI open source page]
* [https://community.ti.com/ TI E2E (Engineer-to-Engineer) Community]
* [http://marc.info/?l=linux-omap&m=120761100810527&w=2 DSP Bridge driver for OMAP3 platform]
* [http://lists.arm.linux.org.uk/lurker/message/20080701.142512.5eeff26b.en.html ARMv7 Oprofile support]
* [http://focus.ti.com/pdfs/wtbu/swpu114g.pdf OMAP34xx Wireless Technical Reference Manual] (swpu114g.pdf, 47 MB)
* [http://amethyst.openembedded.net/~koen/index.php?sort=date&order=desc&path=beagleboard/ Koen's (OpenEmbeded) BeagleBoard source and binaries]
* [http://del.icio.us/tag/beagleboard+peripheral+verified Verified peripherals for BeagleBoard]
* [http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt OMAP3430 Linux Power Management presentation]
==Articles==
* [http://linuxdevices.com/news/NS5852740920.html LinuxDevices article about Beagle]
* [http://www.linuxdevices.com/news/NS8479495970.html LinuxDevices article about Digi-Key launch]
* [http://www.linuxdevices.com/news/NS5682470737.html LinuxDevices article about Beagle Rev C, Beagle MID from HY Research, Touch Book and Sponsored Projects Contest]
* [http://www.linuxjournal.com/article/10607 Linuxjournal article on the BeagleBoard]

==Books==
* [[OMAP_and_DaVinci_Software_for_Dummies|OMAP and DaVinci Software for Dummies]]

==Beagle based training materials==
* http://free-electrons.com/blog/beagle-labs/

==Past Beagle events==
* TIDC, February 26-28, 2008: [http://www.beagleboard.org/uploads/tidc_opensource.pdf Slides from TI developer conference (TIDC) open source session], covering also beagle board
* [http://www.lugradio.org/live/USA2008/ LUG RADIO Live USA 2008, April 12-13, 2008]: [http://www.beagleboard.org/uploads/lugradio_20080411.PPT TI/Beagle Presentation] and [http://forums.lugradio.org/viewtopic.php?f=4&t=4094&st=0&sk=t&sd=a&sid=d69cc807569ab41e33f93af698c536b8&start=15#p41549 video]
* LinuxTag, May 28-31, 2008: [http://www.flickr.com/photos/jadon/2551439955/in/pool-beagleboard picture 1] and [http://www.flickr.com/photos/jadon/2535692865/in/pool-beagleboard picture 2]
* [http://lugradio.org/live/UK2008/travel LugRadio Live UK 2008], July 19 - July 20, 2008: [http://www.flickr.com/photos/koenkooi/tags/lugradiolive/ Koen's pictures] showing e.g. [http://www.bigbuckbunny.org/index.php/download/ Big Buck BUNNY] playing at Beagle. [http://linuxoutlaws.com/podcast/48 Interview with Linux Outlaws (52:06)] and the [http://www.youtube.com/watch?v=m9xVbntl-DY video]
* [http://osscamp.in/index.php/OSScamp_Bengaluru_Mobile_2008 OSScamp Bengaluru Mobile 2008], July 19, 2008
* [http://www.linuxworldexpo.com LinuxWorld Conference & Expo], August 4 - August 7, 2008: [http://www.flickr.com/photos/jadon/sets/72157606586084668/ pictures with living beagle] and from [http://www.flickr.com/photos/linuxjournal/2738316951/in/set-72157606634486338/ Linux Journal's photostream]
* BeagleBoard.org event at Jillian's during LinuxWorldExpo, August 5, 2008, 5:30-7:30 pm
* [http://barcamp.pbwiki.com/BarCampHouston3 BarCamp Houston 3], August 9, 2008, 9:00 A.M.: [http://www.flickr.com/photos/jadon/sets/72157606656532041/ pictures]
* NIT Suratkal, India [http://www.nitkieee.com/site/sp-connect2/schedule IEEE SP Connect 2], August 30, 20008
* [http://barcampbangalore.org/wiki/BCB7_Demos BarCamp Bangalore], India, September 13, 2008
* [http://www.ibc.org/ IBC 2008], September 11 - September 16, 2008: [http://www.flickr.com/photos/koenkooi/tags/ibc2008/ pictures]
* Free Open "Embedded Linux" Training for Students in India, [http://code.google.com/p/beagleboard/wiki/Trainings?updated=Trainings&ts=1220250913 beagleboard.org Trainings in India], September 20, 2008: [http://www.youtube.com/watch?v=A6FLdmgQlb4&feature=PlayList&p=1BAB6EE9CC7285AD&index=0 video], [http://www.flickr.com/photos/25691331@N04/sets/72157607419766102/ photos] and [http://lakshmansrikanth.blogspot.com/2008/09/linux-embedded.html blog]
* [http://www.embedded.co.uk/ Embedded Systems Show 2008], Birmingham, UK, October 1-2, 2008
* [http://www.mvista.com/vision/ MontaVista Vision 2008 Embedded Linux Developers Conference], San Francisco, California, October 1-3, 2008 : [http://www.mvista.com/download/topic.php?t=18 Video and presentation overview], [http://www.mvista.com/download/fetchdoc.php?docid=323 William Mills' presentation], [http://www.mvista.com/download/fetchdoc.php?docid=333 Jason Kridner's presentation]
* [http://www.rtcgroup.com/arm/2008/ ARM Developers' Conference], Santa Clara Convention Center, Santa Clara, Calif., USA, October 7-9, 2008
* [http://www.cmp-egevents.com/web/escb Embedded Systems Conference Boston 2008], Hynes Convention Center, Boston, USA, October 26 - October 30, 2008: [http://beagleboard.org/demo/esc Resources]
* [[BeagleBoard/contest|BeagleBoard contest]] #1: Create a cool BeagleBoard application and win a Rev C1! Closed, ran until January 9, 2009
* [http://www.silica.com/events/seminars/seminar-overview/ti-omp-workshop.html OMAP35x training by Silica], January 21, 2009, Cambridge, UK, ARM Holdings Lecture Theatre. [[RichardB's notes from the seminar]]
* [[BeagleBoard/contest|BeagleBoard contest #2]], unitl February 27, 2009: : Create a cool BeagleBoard application and win a Rev C2!
* [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe, March 31st 2009
* SILICA's [http://www.silica.com/events/seminars/seminar-overview/ti-omap-piccolo-poing.html Texas Instruments 2-in-1 Seminar: OMAP & Piccolo], May 13th 2009: Poing (Munich) - Germany
* 24th until 27th June 2009: [http://www.linuxtag.org/2009/en.html Linux Tag Germany] with [http://groups.google.com/group/beagleboard/msg/27fefef5f1d2ef73 TI booth] and [http://www.linuxtag.org/2009/en/program/freies-vortragsprogramm/all-events/details.html?talkid=183 Beagle presentation]
* until 31st July 2009: [http://www.cranessoftware.com/services/training/beagledesigncontest.html BeagleBoard Design Contest INDIA Edition] ([http://beagleboard.blogspot.com/2009/04/beagleboard-design-contest-india.html blog entry])
* TI Technology Day Dallas, Tex. on June 16 will held a [http://www.linuxdevices.com/news/NS5682470737.html BeagleBoard users group meeting] (see section ''Availability'').
* Thursday, August 27th: [http://wiki.omap.com/index.php/ETechDays_Lightning_Talks ETechDays Lightning Talks]. 15 minute lightning talks via IRC, WebEx or Dial-In.
* 22.- 23.08.2009, Sankt Augustin, Germany: [http://www.froscon.de/en/ FrOSCon 2009] ([http://groups.google.com/group/beagleboard/browse_thread/thread/6aee27a7d121f4f4# call for papers])

==Beagle wiki pages==
* [[BeagleBoardBeginners|BeagleBoard beginners guides]]
* [[BeagleBoardAndOpenEmbeddedGit|BeagleBoard and OpenEmbedded Git]] installation guide and [[BeagleBoardOpenEmbeddedDevelopment|OpenEmbedded development]]
* [[BeagleBoardDebian|Debian on BeagleBoard]] usage guide
* [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM) on BeagleBoard]] usage guide (formerly known as Ubuntu (ARM))
* [[BeagleBoardUbuntu|Ubuntu (ARM EABI) distribution at BeagleBoard]]
* [[BeagleBoardRecovery|BeagleBoard recovery]] about fixing boards not booting any more because of broken NAND content
* [[BeagleBoardJTAG|BeagleBoard JTAG]] and [[OMAP3530_ICEPICK|OMAP3530_ICEPICK]] about JTAG on BeagleBoard
* [[BeagleBoardOpenOCD|BeagleBoard OpenOCD]] has infos about status and usage of open source JTAG software OpenOCD with Beagle
* [[BeagleBoardNAND|BeagleBoard NAND boot]] about how to boot BeagleBoard from NAND flash
* [[BeagleBoardPeripherals|BeagleBoard peripherals and adapters page]] about useful BeagleBoard add ons.
* [[Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB|Mount BeagleBoard root file system over NFS via USB]]
* [[BeagleBoardFAQ|BeagleBoard FAQ]]
* [[BeagleBoardSugar|Sugar on BeagleBoard]]
* [[BeagleBoard/DSP_Howto|BeagleBoard DSP howto]]
* [[BeagleBoardRawLCD|Interfacing BeagleBoard to Raw LCD]]
* [[BeagleBoard/gst-openmax|BeagleBoard OpenMAX usage]]
* [[BeagleBoard/video|BeagleBoard video]]
* [[BeagleBoardOpenCV|Using OpenCV computer vision library with BeagleBoard]]
* [[BeagleBoard/James|James]]: Just A Miniature Entertainment System
* [[U-boot_musb_gadget_support|U-boot musb gadget support]]
* [[BeagleBoard-JP|Japanese translation of this Beagle page]]
* [[BeagleEPD|BeagleBoard E-Ink Platform Driver]]
* [[BeagleBoardFedora|Random hacking notes for getting Fedora 10 to kinda work with the BeagleBoard]]
* BeagleBoard specific [[BeagleBoard/GSoC|Google Summer of Code 2009]] page, [[BeagleBoard/Ideas-2009|GSoC project ideas]] and [[BeagleBoard/GSoC/Application|GSoc application]]
* [[BeagleBoard/Poky|Poky]] for BeagleBoard
* [[Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM|Xenarc USB touchscreen for Beagleboard/OMAP3 EVM]]
* [[BeagleBoard/BugAdapter|BeagleBoard Bug Adapter board]]
* [[BeagleBoardDebianWifiInstallInfo|BeagleBoard Debian WiFi install info]]
* [[BeagleBoard/DSP_Clarification|Info about the various Linux DSP systems for OMAP chips]]
* [[BeagleBoardPinMux|BeagleBoard PinMux]]
* [[BeagleBoardLinuxKernel|BeagleBoard Linux kernel manual compile]]
* [http://www.hervanta.com/stuff/Beaglebot Beaglebot]: build an experimental robotics project with Beagle
* [http://code.google.com/p/beagleboard/w/list code.google.com BeagleBoard wiki]
* '''[[BeagleBoard/contest|BeagleBoard contest]]'''
* [http://en.wikipedia.org/wiki/Beagle_Board Wikipedia BeagleBoard page]
* [http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board Android port for BeagleBoard]: Instructions for porting Android on BeagleBoard
* [[BeagleBoard/bangalore_user_meet |BeagleBoard Bangalore User Meet]]
* [[BeagleBoardEclipse|Using Eclipse with Beagle]] (for JTAG debugging)
* [[Zoom2Beginners|Zoom2 for Beginners]]
* [http://wh1t3s.com/2009/05/11/beagleboard-as-usb-mass-storage-device-via-usb-otg/ BeagleBoard as USB Mass Storage Device via USB OTG]
* [http://digitalsurveyinstruments.com/beagleperiphials/solarcomputer/index.htm BeagleBoard as solar powered computer]
* [http://blog.makezine.com/archive/2009/02/blinking_leds_with_the_beagle_board.html Blinking LEDs with the Beagle Board] from Make:Online
* [http://www.crashcourse.ca/wiki/index.php/BeagleBoard Robert's private Beagle wiki] (please don't add anything there, do it here. It will help to avoid scattering. Thanks!)
* [http://felipec.wordpress.com/2009/03/26/omap3-public-dsp-binaries-now-work/ Felipe's blog] about D1 MPEG-4 decoding using less than 15% of CPU with help of DSP
* [http://www.syspire.de/node/3 Embedded Mediacenter] based on BeagleBoard (German)
* [http://pandorawiki.org/Floating_Point_Optimization Floating Point Optimization] with VFP-lite and NEON intro
* [http://particolarmente-urgentissimo.blogspot.com/2009/09/beagleboard-setting-date-via-gps.html Beagleboard setting date via GPS]
* [http://free-electrons.com/blog/beagle-labs/ Complete embedded Linux training labs] on the BeageBoard

==Beagle photos==
* [http://www.flickr.com/groups/beagleboard/pool/ Beagle board pictures at flickr]
* [http://www.flickr.com/photos/32615155@N00/2439256116/ Beagle board and USRP]
* [http://www.flickr.com/photos/nishanthmenon/2438406603/ Modify SDP3430 QUART cable for beagle]
* [http://www.flickr.com/photos/koenkooi/2695061759/ MythTV on Beagle]
==Beagle videos==
* [http://uk.youtube.com/watch?v=fL_XMieanSc Beagle Board Beginnings]
* [http://www.youtube.com/watch?v=cXr-D1wROfQ Beagleboard in the Living Room]
* [http://uk.youtube.com/watch?v=FuVwh_VrIxk Beagle Board 3D, Angstrom, and Ubuntu]
* [http://uk.youtube.com/watch?v=TUYOjRGYeYU testsprite with beagleboard]
* [http://uk.youtube.com/watch?v=9Z4ZTovtFKk Beagleboard LED demo]
* [http://uk.youtube.com/watch?v=R33dzREZGEk LCD2USB attached to a beagleboard]
* [http://www.youtube.com/watch?v=7D3V6BUpGLE Video blending in hardware]
* [http://www.youtube.com/watch?v=-tUBXD-KRp4 Beagle Running Angstrom (VGA) on DLP Pico Projector]
* [http://www.youtube.com/watch?v=3ToYOgP9f9U SGX on Beagle working with Linux 2.6.27]
* Not on Beagle OMAP3530: [http://youtube.com/watch?v=5i9cWOK1spw Ubuntu 7.04 on on OMAP3430 SDP]
* [http://in.youtube.com/watch?v=nADn_vNVEKw Beagle Board booting Android]
* [http://www.youtube.com/watch?v=UHQdUS0i-nw Beagleboard, SGX, and libfreespace demo]

==Beagle manufacturing==
* [http://www.youtube.com/watch?v=C-CwkjT9z_0&feature=related Beagle Solder Paste Screening]
* [http://www.youtube.com/watch?v=9LLjDovIG2M&feature=related Beagle Assembly Inspection]
* [http://www.youtube.com/watch?v=sbOZfBnoVnM&feature=related Beagle Functional Test]
* [http://www.youtube.com/watch?v=cvDtXmJJcEI&feature=related Beagle Reflow]
* [http://www.youtube.com/watch?v=W2o4NTASxN0&feature=related Beagle Board Assembly at Circuitco]
==Fun==
* Enjoy [http://www.beaglegame.com/ BeagleGame]

=Other OMAP boards=

* OMAP3530 based [http://www.timll.com/chinese/OMAP/DevKit8000.asp DevKit8000], a Chinese BeagleBoard,256MB DDR SDRAM + 256MB NANDFLASH,Fully compatible with BeagleBoard source.

* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* OMAP3 OMAP3430 based [https://gforge.ti.com/gf/project/omapzoom/wiki/?pagename=HardwareInformation Zoom MDK], which has been superseded by the [http://www.logicpd.com/products/development-kits/texas-instruments-zoom%E2%84%A2-omap34x-ii-mdp Zoom II], and other [http://www.logicpd.com/products LogicPD kits].
* OMAP3 OMAP3530 based [http://www.openpandora.org/ Pandora]
* OMAP3 OMAP3503 based [http://www.gumstix.net/Overo/cat/Overo/115.html Gumstix Overo]
* OMAP3 OMAP35x based EVM from [http://mistralsolutions.com/products/omap_3evm.php Mistral] and [http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html TI] (both are the same)
* OMAP3 OMAP3430 based [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12013&contentId=28741 Software Development Platform (SDP)]
* OMAP3 OMAP3530 based board from [http://www.magniel.com/omap3.html Magniel Inc.]
* OMAP3 based [http://www.archos.com/products/imt/index.html?country=us&lang=en Archos 5, ARCHOS 5G and ARCHOS 7]
* OMAP3 OMAP35x based [http://www.logicpd.com/products/som/ti/omap35x OMAP35x SOM-LV]
* OMAP3 based [[Mini_Board|ICETEK-OMAP3530-Mini]], a Chinese BeagleBoard clone, with a [[MiniBoardFAQ|FAQ]]
* OMAP3 based [http://www.ebv.com/en/products/categories/details/product/ebvbeagle-board EBVBeagle], a German BeagleBoard clone
* OMAP3530 based [http://www.bsquare.com/products/hardware_solutions/3530.asp BSQUARE’s Dev Kit OMAP3530]
* OMAP3530 based [http://beaversource.oregonstate.edu/projects/cspfl/wiki/CSPFL_Hardware OSWALD]
* OMAP3 BeagleBoard-based [http://www.alwaysinnovating.com/touchbook/ Touch Book]
* OMAP3530 based [http://www.analogue-micro.com/Cobra3530.html Cobra 3530 OMAP3530 module ]
* OMAP3 based [http://www.kwikbyte.com/KBOC.html KwikByte 35XX System Module]
* OMAP3530 based [[DevKit8000]], a Chinese BeagleBoard clone, slightly larger with additional peripherals (e.g. LCD/TSP, Ethernet and keyboard)
* OMAP3530 based [http://www.igep-platform.com/ IGEPv2 Platform], a Spanish BeagleBoard clone, slightly larger, with additional peripherals like e.g. ethernet connector, wifi+bluetooth.
* OMAP35x based [http://www.ultratronik.de/mmi-rechnerplattformen.html MMI4 from Ultratronik]
* OMAP35x based [http://www.technexion.com/index.php/tao-3530 TAO-3530 from TechNexion]
* OMAP35x based [http://www.variscite.com/varomap35xxsbc.html VAR-OM35xxSBC from Variscite]
* OMAP35x based [[EGS3530]],a Chinese BeagleBoard clone from [http://www.ema-tech.com EMA]
* OMAP3 OMAP35x based [http://www.buglabs.net/products BUG] from Bug Labs, Inc.
* OMAP35x System-on-Module [[SOM3530]],The smallest(40x40x4mm) OMAP35XX-based System on Module in the world!

=Subpages=
<splist
parent=
showparent=no
sort=desc
sortby=title
liststyle=ordered
showpath=no
kidsonly=no
debug=0
/>

Android Kernel Features

2010-01-08T13:08:36Z

Kaa-ching: add a pointer to Greg KHs blog where he announces to remove several Android-specific drivers that are discussed on this page.

== List of Kernel features unique to Android ==

=== Important update ===
See [http://www.kroah.com/log/linux/staging-status-12-2009.html Greg KH blog post on -staging for 2.6.33], where he announces to '''remove''' various Android drivers from -staging.

=== Binder ===
* Binder - corba-like IPC
** used instead of SysV IPC for interprocess communication
** The Linux version of Binder was originally derived from a project by PalmSource to implement a CORBA-like message-passing or method invocation system. Documentation on that system is at: http://www.angryredplanet.com/~hackbod/openbinder/docs/html/index.html
** implementation is at: <tt>drivers/android/binder.c</tt>, with include file: <tt>include/linux/binder.h</tt>

=== ashmem ===
* ashmem - Android shared memory
** implementation is in <tt>mm/ashmem.c</tt>

According to the Kconfig help "The ashmem subsystem is a new shared memory allocator,
similar to POSIX SHM but with different behavior and sporting a simpler file-based API."

Apparently it better-supports low memory devices, because it can discard
shared memory units under memory pressure.

To use this, programs open /dev/ashmem, use mmap() on it, and can perform one
or more of the following ioctls:

* ASHMEM_SET_NAME
* ASHMEM_GET_NAME
* ASHMEM_SET_SIZE
* ASHMEM_GET_SIZE
* ASHMEM_SET_PROT_MASK
* ASHMEM_GET_PROT_MASK
* ASHMEM_PIN
* ASHMEM_UNPIN
* ASHMEM_GET_PIN_STATUS
* ASHMEM_PURGE_ALL_CACHES

=== pmem ===
* PMEM - Process memory allocator
** implementation at: <tt>drivers/misc/pmem.c</tt> with include file at: <tt>include/linux/android_pmem.h</tt>
** Brian Swetland says:
<pre>
The pmem driver is used to manage large (1-16+MB) physically contiguous
regions of memory shared between userspace and kernel drivers (dsp, gpu,
etc). It was written specifically to deal with hardware limitations of
the MSM7201A, but could be used for other chipsets as well. For now,
you're safe to turn it off on x86.
</pre>

=== logger ===
* logger - system logging facility
** This is the kernel support for the 'logcat' command
** The kernel driver for the serial devices for logging are in the source code drivers/android/logging.c
** See [[Android logger]] for more information

=== wakelocks ===
* wakelock - used for power management
** Holds machine awake on a per-event basis until wakelock is released
** See [[Android Power Management]] for detailed information

=== oom handling ===
* oom handling modifications
** lowmem notifications
** implementation at: <tt>drivers/misc/lowmemorykiller.c</tt>
** also at: <tt>security/lowmem.c</tt>
** [Need a description of this here]

=== alarm ===
* alarm

=== paranoid network security===
* paranoid network security
** See [[Android_Security#Paranoid_network-ing]]

=== timed gpio ===
Generic gpio is a mechanism to allow programs to access and manipulate gpio registers from user space.

"Timed gpio" appears to be a system to allow for similar gpio manipulation, but with an added capability
to automatically set a value in a gpio after a specified timeout.

On my ADP1, there is a driver at:

I'm not sure who uses this, or how it is used, but this is a directory with the following items:
<pre>
# cd /sys/bus/platform/drivers/timed-gpio
# ls -l
--w------- 1 0 0 4096 Nov 13 02:11 bind
lrwxrwxrwx 1 0 0 0 Nov 13 02:11 timed-gpio -> ../../../../devices/platform/timed-gpio
--w------- 1 0 0 4096 Nov 13 02:11 uevent
--w------- 1 0 0 4096 Nov 13 02:11 unbind
</pre>

Also, there is a device at:
<pre>
# cd /sys/devices/platform/timed-gpio
# ls -lR
.:
lrwxrwxrwx 1 0 0 0 Nov 13 01:34 driver -> ../../../bus/platform/drivers/timed-gpio
-r--r--r-- 1 0 0 4096 Nov 13 01:34 modalias
drwxr-xr-x 2 0 0 0 Nov 13 01:34 power
lrwxrwxrwx 1 0 0 0 Nov 13 01:34 subsystem -> ../../../bus/platform
-rw-r--r-- 1 0 0 4096 Nov 13 01:34 uevent

./power:
-rw-r--r-- 1 0 0 4096 Nov 13 01:34 wakeup
</pre>

Possibly this means that one of the GPIO pins on the ADP1 is tied to a power wakeup event???

=== other kernel changes ===
Here is a miscellaneous list of other kernel changes in the mistral Android kernel:
* switch events - drivers/switch/*
* USB gadget driver for ADB - drivers/usb/gadget/android.c
* yaffs2 flash filesystem
* support in FAT filesystem for FVAT_IOCTL_GET_VOLUME_ID
* RAM console
* and more...

== Kernel configuration options ==
The file [http://android.git.kernel.org/?p=kernel/common.git;a=blob_plain;f=Documentation/android.txt;hb=HEAD Documentation/android.txt] has a list of required configuration options for a kernel to support
an Android system.

== Resources ==
* Peter McDermott's excellent description of his work to port Android to the Nokia N810.
** See http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting-Android-to-a-new-device/
** Also, see his annotated list of modified and added kernel files, at: http://www.linuxfordevices.com/files/misc/porting-android-to-a-new-device-p3.html

* Jollen Chen's excellent presentation on system-level Android features, including an overview of kernel features unique to Android: ''Note: Parts of the presentation are in Chinese''
** http://www.slideshare.net/jollen/android-os-porting-introduction

* Greg KH blogged on -staging for 2.6.33, where he announces to '''remove''' various Android drivers from -staging.
** http://www.kroah.com/log/linux/staging-status-12-2009.html

[[Category:Android]]

Boot Time

2009-08-04T19:49:15Z

Kaa-ching: added 1 second boot video

== Introduction ==
Boot Time includes topics such as measurement, analysis, human factors, initialization techniques, and reduction techniques.
The time that a product takes to boot directly impacts the first perception an end user has of the product.
Regardless of how attractive or well designed a consumer electronic device is, the time required to move the device from off to an interactive, usable state is critical to obtaining a positive end user experience. Turning on a device is Use Case #1.

Booting up a device involves numerous steps and sequences of events. In order to use consistent terminology, the
[[Bootup Time Working Group]] of the CE Linux Forum came up with a list of terms and their widely accepted definitions
for this functionality area. See the following page for these terms:
* [[Boot-up Time Definition Of Terms]]

== Technology/Project Pages ==
The following are individual pages with information about various technologies relevant to improving Boot Time for Linux. Some of these describe local patches available on this site. Others point to projects or patches maintained elsewhere.

=== Measuring Boot-up Time ===
*[[Printk Times]] - simple system for showing timing information for each printk.
*[[Kernel Function Trace]] - system for reporting function timings in the kernel.
*[[Linux Trace Toolkit]] - system for reporting timing data for certain kernel and process events.
*[http://oprofile.sourceforge.net/news/ Oprofile] - system-wide profiler for Linux.
*[[Bootchart]] - a tool for performance analysis and visualization of the Linux boot process. Resource utilization and process information are collected during the user-space portion of the boot process and are later rendered in a PNG, SVG or EPS encoded chart.
*[http://people.redhat.com/berrange/systemtap/bootprobe/ Bootprobe] - a set of [[System Tap]] scripts for analyzing system bootup.
* and, let us not forget: "cat /proc/uptime"
* [[Tims Fastboot Tools#grabserial | grabserial]] - a nice utility from Tim Bird to log and timestamp console output
* [[Tims Fastboot Tools#Tim's quick and dirty process trace|process trace]] - a simple patch from Tim Bird to log exec, fork and exit system calls.
* [[Initcall Debug]] - a kernel command line option to show time taken for initcalls.
* See also: [[Kernel Instrumentation]] which lists some known kernel instrumentation tools. These are of interest for measuring kernel startup time.

=== Technologies and Techniques for Reducing Boot Time ===
==== Bootloader speedups ====
*[[Kernel XIP]] - Allow kernel to be executed in-place in ROM or FLASH.
*[[DMA Copy Of Kernel On Startup]] - Copy kernel from Flash to RAM using DMA
*[[Uncompressed kernel]] - An uncompressed kernel might boot faster
*[[Fast Kernel Decompression]]

==== Kernel speedups ====
*[[Disable Console]] - Avoid overhead of console output during system startup.
*Disable bug and printk - Avoid the overhead of bug and printk. Disadvantage is that you loose a lot of info.
*[[RTC No Sync]] - Avoid delay to synchronize system time with RTC clock edge on startup.
*[[Short IDE Delays]] - Reduce duration of IDE startup delays (this is effective but possibly dangerous).
*[[Hardcode kernel module info]] - Reduce the overhead of loading a module, by hardcoding some information used for loading the relocation information
*[[IDE No Probe]] - Force kernel to observe the ide<x>=noprobe option.
*[[Preset LPJ]] - Allow the use of a preset loops_per_jiffy value.
*[[Asynchronous function calls]] - Allow probing or other functions to proceed in parallel, to overlap time-consuming boot-up activities.
**[[Threaded Device Probing]] - Allow drivers to probe devices in parallel. (not mainlined, now deprecated?)
*[[Reordering of driver initialization]] - Allow driver bus probing to start as soon as possible.
*[[Deferred Initcalls]] - defer non-essential module initialization routines to after primary boot
*NAND ECC improvement - The pre 2.6.28 nand_ecc.c has room for improvement. You can find an improved version in the mtd git at http://git.infradead.org/mtd-2.6.git?a=blob_plain;f=drivers/mtd/nand/nand_ecc.c;hb=HEAD. Documentation for this is in http://git.infradead.org/mtd-2.6.git?a=blob_plain;f=Documentation/mtd/nand_ecc.txt;hb=HEAD. This is only interesting if your system uses software ECC correction.
*Check what kernel memory allocator you use. Slob or slub might be better than slab (which is the default in older kernels)
*If your system does not need it, you can remove SYSFS and even PROCFS from the kernel. In one test removing sysfs saved 20 ms.
*Carefully investigate all kernel configuration options on whether they are applicable or not. Even if you select an option that is not used in the end, it contributes to the kernel size and therefore to the kernel load time (assuming you are not doing kernel XIP). Often this will require some trial and measure! E.g. selecting CONFIG_CC_OPTIMIZE_FOR_SIZE (found under general setup) gave in one case a boot improvement of 20 ms. Not dramamtic, but when reducing boot time every penny counts!
*Moving to a different compiler version might lead to shorter and/or faster code. Most often newer compilers produce better code. You might also want to play with compiler options to see what works best.
* If you use initramfs in your kernel and a compressed kernel it is better to have an uncompressed initramfs image. This is to avoid having to uncompress data twice. A patch for this has been submitted to LKML. See http://lkml.org/lkml/2008/11/22/112

===== File System issues =====
Different file systems have different initialization (mounting) times, for the same data sets. This
is a function of whether meta-data must be read from storage into RAM or not, and what algorithms are
used during the mount procedure.

* [[Filesystem Information]] - has information about boot-up times of various file systems
* [[File Systems]] - has information on various file systems that are interesting for embedded systems. Also includes some improvement suggestions.
* [[Avoid Initramfs]] - explains on why intramfs should be avoided if you want to minimize boot time
* Split partitions. If mounting a file system takes long, you can consider splitting that filesystem in two parts, one with the info that is needed during or immediately after boot, and one which can be mounted later on.
* [[Ramdisks demasked]] - explains why using a ram disk generally results in a longer boot time, not a shorter one.

==== User-space and application speedups ====
* [[Optimize RC Scripts]] - Reduce overhead of running RC scripts
* [[Parallel RC Scripts]] - Run RC scripts in parallel instead of sequentially
* [[Application XIP]] - Allow programs and libraries to be executed in-place in ROM or FLASH
* [[Pre Linking]] - Avoid cost of runtime linking on first program load
* Statically link applications. This avoids the costs of runtime linking. Useful if you have only a few applications. In that case it could also reduce the size of your image as no dynamic libraries are needed
* GNU_HASH: ~ 50% speed improvement in dynamic linking
** See http://sourceware.org/ml/binutils/2006-06/msg00418.html
* [[Application Init Optimizations]] - Improvements in program load and init time via:
** use of mmap vs. read
** control over page mapping characteristics.
* [[Include modules in kernel image]] - Avoid extra overhead of module loading by adding the modules to the kernel image
* Avoid udev, it takes quite some time to populate the /dev directory. In an embedded system it is often known what devices are present and in any case you know what drivers are available, so you know what device entries might be needed in /dev. These should be created statically, not dynamically. mknod is your friend, udev is your enemy.
* If you still like udev and also like fast boot-up's, you might go this way: start your system with udev enabled and make kind of a backup of the created device nodes. Now, modify your init script like this: instead running udev, copy the device nodes that you just made a backup of into the device tree. Now, install the hotplug-daemon like you always do. That trick avoids the device node creation at startup but stills lets your system create device nodes later on.
* If your device has a network connection, preferably use static IP addresses. Getting an address from a DHCP server takes additional time and has extra overhead associated with it.
* Moving to a different compiler version might lead to shorter and/or faster code. Most often newer compilers produce better code. You might also want to play with compiler options to see what works best.
* If possible move from glibc to uClibc. This leads to smaller executables and hence to faster load times.
* library optimiser tool: http://libraryopt.sourceforge.net/ <br/> This will allow you to create an optimised library. As unneeded functions are removed this should lead to a performance gain. Normally there will be library pages which contain unused code (adjacent to code that is used). After optimizing the library this does not occur any more, so less pages are needed and hence less page loads, so some time can be saved.
* Function reordering: http://www.celinux.org/elc08_presentations/DDLink%20FunctionReorder%2008%2004.pdf <br/> This is a technique to rearrange the functions within an executable so they appear in the order they are needed. This improves the load time of the application as all initialization code is grouped into a set of pages, instead of being scattered over a number of pages.

==== Suspend related improvements ====
Another approach to improve boot time is to use a suspend related mechanism. Two approaches are known.
* Using the standard hibernate/resume approach. This is what has been demonstrated by Chan Ju, Park, from Samsung. See sheet 23 and onwards from this [[Media:LinuxBootupTimeReduction4DSC.ppt|PPT]] and section 2.7 of this [http://www.kernel.org/doc/ols/2006/ols2006v2-pages-239-248.pdf paper]. <br /> Issue with this approach is that flash write is much slower than flash read, so the actual creation of the hibernate image might take quite a while.
* Implementing snapshot boot. This is done by Hiroki Kaminaga from Sony and is described at [[Suspend To Disk For ARM|snapshot boot for ARM]] and http://elinux.org/upload/3/37/Snapshot-boot-final.pdf<br />This is similar to hibernate and resume, but the hibernate file is retained and used upon every boot. Disadvantage is that no writable partitions should be mounted at the time of making the snapshot. Otherwise inconsistencies will occur if a partition is modified, while applications in the hibernate file might have information in the snapshot related to the unmodified partition.

==== Miscellaneous topics ====

[[About Compression]] discusses the effects of compression on boot time. This can affect both the kernel boot time as well as user-space startup.

==== Uninvestigated speedups ====

This section is a holding pen for ideas for improvement that are not implemented yet but that could result in a boot time gain. Please leave a note here if you are working on one of these items to avoid duplicate work.

* '''Prepopulated buffer cache''' - As initramfs performs an additional copy of the data the idea is to have a prepopulated buffer cache. A simplistic scenario would allow dumping the buffer cache when the booting is completed and the user applications have initialised. This data then could be used in a subsequent boot to initialize the buffer cache (of course without copying). A possible approach would be to have those data to reside into the kernel image and use them directly. Alternately they could be loaded separately. <br /> Unfortunately my knowledge of the internals in this section is not yet good enough to do a trial implementation.<br /> Caveats:
** is it possible to have the buffer cache split into two different parts, one which is statically allocated, one which is dynamically allocated?
** the pages in the prepopulated buffer cache probably cannot be discarded, so they should be pinned
** apart from the buffer cache data itself also some other variables might need restoring
** a similar approach could also be used for the cached file data.
*'''Dedicated fs''' - currently a lot of abstraction is done in fs to make a nice abstraction allowing easy addition of new filesystems and creating a unified view of those filesystem. While this is pretty neat, the abstraction layers also introduce some overhead. A solution could be to create a dedicated fs system, which supports only one (or maybe 2) filesystems, and eliminates the abstraction overhead. This will give some benefit, but the chance of getting this into the mainline is zero.

== Articles and Presentations ==
* "One Second Linux Boot Demonstration (new version)" ([http://www.youtube.com/watch?v=-l_DSZe8_F8 Youtube video by MontaVista])
* "Tools and Techniques for Reducing Bootup Time" ([[Media:Tools-and-technique-for-reducing-bootup-time.ppt|PPT]] | [[Media:Tools-and-technique-for-reducing-bootup-time.odp|ODP]] | [[Media:Tools-and-technique-for-reducing-bootup-time.pdf|PDF]] | [http://free-electrons.com/pub/video/2008/elce/elce2008-bird-reducing-bootup-time.ogv video])
** Tim Bird has presented at ELC Europe, on November 7, 2008, his latest collection of tips and tricks for reducing bootup time
** [[Tims Fastboot Tools]] has online materials in support of this presentation
* [http://www.mvista.com/download/author.php?a=37 Christopher Hallinan] has done a presentation at the MontaVista Vision conference 2008 on the topic of reducing boot time. Slides available [http://www.mvista.com/download/power/Reducing-boot-time-techniques-for-fast-booting.pdf here]
* [http://lwn.net/Articles/192082/ Optimizing Linker Load Times]
** (introducing various kinds of bootuptime reduction, prelinking, etc.)
* [http://tuxology.net/2008/07/08/benchmarking-boot-latency-on-x86/ Benchmarking boot latency on x86]
** By Gilad Ben-Yossef, July 2008
** A tutorial on using TSC register and the kernel PRINTK_TIMES feature to measure x86 system boot time, including BIOS, bootloader, kernel and time to first user program.
* [http://tree.celinuxforum.org/CelfPubWiki/KoreaTechJamboree3?action=AttachFile&do=get&target=The_Fast_Booting_of_Embedded_Linux.pdf Fast Booting of Embedded Linux]
** By HoJoon Park, Electrons and Telecommunications Research Institute (ETRI), Korea, Presented at the CELF [http://tree.celinuxforum.org/CelfPubWiki/KoreaTechJamboree3 3rd Korean Technical Jamboree], July 2008
** Explains several different reduction techniques used for different phases of bootup time
*Tim Bird's (Sony) survey of boot-up time reduction techniques:
**[http://kernel.org/doc/ols/2004/ols2004v1-pages-79-88.pdf Methods to Improve Boot-up Time in Linux] - Paper prepared for 2004 Ottawa Linux Symposium
**{{pdf|ReducingStartupTime v0.8.pdf|Reducing Startup Time in Embedded Linux Systems}} - December 2003 Presentation describing some existing boot-up time reduction techniques and strategies.
* [http://free-electrons.com/articles/optimizations Embedded Linux optimizations]
** By Free Electrons
** Tutorial to reduce size, RAM, speed, power and cost of a Linux based embedded system]
*Parallelizing Linux Boot on CE Devices
** [http://tree.celinuxforum.org/CelfPubWiki/ELCEurope2007Presentations?action=AttachFile&do=view&target=par.pdf PDF of Presentation]
**[http://free-electrons.com/pub/video/2007/elce/elce-2007-vitaly-wool-parallel-boot.ogg Video of Presentation]
*[http://www.ibm.com/developerworks/linux/library/l-boot-faster/ Parallelize Applications for Faster Linux Boot]
**Authored by M. Tim Jones for IBM Developer Works
**This article shows you options to increase the speed with which Linux boots, including two options for parallelizing the initialization process. It also shows you how to visualize graphically the performance of the boot process.

=== Case Studies ===
* Samsung proof-of-acceptability study for digital still camera: see [[Media:LinuxBootupTimeReduction4DSC.ppt|Boot Up Time Reduction PPT]] and the [http://www.kernel.org/doc/ols/2006/ols2006v2-pages-239-248.pdf paper] describing this.
* [https://docs.blackfin.uclinux.org/doku.php?id=fast_boot_example Boot Linux from Processor Reset into user space in less than 1 Second]
** In this white paper, Robin Getz describes the techniques used to fast-boot a blackfin development board.

=== News ===
* Lineo Solutions announced (Nov. 2008) technology to boot Linux in 2.97 seconds on a low-end system. The system is called "Warp2" and appears to be a form of modified resume (similar to "snapshot boot" mentioned above.
** See http://www.linuxdevices.com/news/NS5185504436.html

== Additional Projects/Mailing Lists/Resources ==
=== Kexec ===
*Kexec is a system which allows a system to be '''rebooted''' without going through BIOS. That is, a Linux kernel can directly boot into another Linux kernel, without going through firmware. See the white paper at: [http://developer.osdl.org/andyp/kexec/whitepaper/kexec.pdf kexec.pdf]
**2004 Kernel Summit presentation: [http://www.xenotime.net/linux/fastboot/fastboot-ks-2004.pdf fastboot.pdf]
**here's another Kexec white paper:[http://www-106.ibm.com/developerworks/linux/library/l-kexec.html?ca=dgr-lnxw04 Reboot Fast]

=== Splash Screen projects ===
* [http://splashy.alioth.debian.org/wiki/ Splashy] - Technology to put up a spalsh screen early in the boot sequence. This is user-space code.
** This seems to be the most current splash screen technology, for major distributions. A framebuffer driver for the kernel is required.
* [http://dev.gentoo.org/~spock/projects/gensplash/ Gentoo Splashscreen] - newer technology to put a splash screen early in the boot sequence
** See the HOWTO at: [http://gentoo-wiki.com/HOWTO_fbsplash HOWTO FBSplash]
* [http://butterfeet.org/?p=8 PSplash] - PSplash is a userspace graphical boot splash screen for mainly embedded Linux devices supporting a 16bpp or 32bpp framebuffer.
* [http://www.bootsplash.org/ bootsplash.org] - put up a splash screen early in boot sequence
** This project requires kernel patches
** This project is now abandoned, and work is being done on Splashy.

=== Others ===

*[http://www.linuxdevices.com/news/NS5907201615.html FSMLabs Fastboot] - press release by FSMLabs about fast booting of their product. Is any of this published?

*[http://tree.celinuxforum.org/CelfPubWiki/ snapshot boot] - a technology uses software resume to boot up the system quickly.

==== Apparently obsolete or abandoned material ====
* [[Image:alert.gif]] ''in progress'' - [[Boot-up Time Reduction Howto]] - this is a project to catalog existing boot-up time reduction techniques.
** Was originally intended to be the authoritative source for bootup time reduction information.
** No one maintains it any more (as of Aug, 2008)
*[[Image:alert.gif]]''no content yet'' - [[Boot-up Time Delay Taxonomy]] - list of delays categorized by boot phase, type and magnitude
** Was to be a survey of common bootup delays found in embedded devices.
** Was never really written.

???
* [[Bootup Time Spec]]
* [[Bootup Time Things To Investigate]]
* [[Bootup Time Working Group]]
* [[Bootup Time Task List]]
* [[Bootup Time Howto Task List]]
* [[Fast Booting Translation]]

== Companies, individuals or projects working on fast booting ==
* Intel - Arjan van de Ven - see http://lwn.net/Articles/299483/
* Tripeaks - see http://www.linuxdevices.com/news/NS8282586707.html
* Lineo Solutions - see http://www.linuxdevices.com/news/NS5185504436.html
* Monta Vista - see http://www.linuxdevices.com/news/NS2560585344.html
* fastboot git tree - see http://lwn.net/Articles/299591/

[[Category:Boot Time]]
[[Category:Bootloader]]

Linux Device Drivers

2009-04-13T23:45:25Z

Kaa-ching: added link to free version of book.

== Linux Device Drivers, Third Edition ==

'''[http://oreilly.com/catalog/9780596005900/ Christopher Jonathan Corbet, Alessandro Rubini, Greg Kroah-Hartman, O'Reilly Media, Inc], ISBN 13: 9780596005900'''

==== First Edition ====

==== Second Edition ====
Adding Jonathan Corbet as author.

Second edition of this book is [http://www.xml.com/ldd/chapter/book/ freely available online].

It details the 2.4 kernel series.

==== Third Edition ====
The third edition, adding Greg Kroah-Hartman as an author discusses driver development for the 2.6.10 kernel.

Therefore, the book by now is significantly out of date, but Jonathan has kept a list of all things changing since then at the [http://lwn.net LWN.net] site: [http://lwn.net/Articles/2.6-kernel-api/ API changes in the 2.6 kernel series].

This book also is [http://lwn.net/Kernel/LDD3/ freely available online]. Please consider buying the "dead tree" version to support the authors.

==== User comments ====

n/a

[[Category:Books]]

Essential Linux Device Drivers

2009-04-13T17:58:31Z

Kaa-ching: fix user: links

== Essential Linux Device Drivers ==

''' Sreekrishnan Venkateswaran, Prentice Hall Open Source Software Development Series, ISBN-10: 0132396556
ISBN-13: 9780132396554, 744 pages '''

This book does a very decent attempt at describing everything you need to know about Linux driver development.

From the Amazon website:
* Addresses drivers discussed in no other book, including drivers for I2C, video, sound, PCMCIA, and different types of flash memory
* Demystifies essential kernel services and facilities, including kernel threads and helper interfaces
* Teaches polling, asynchronous notification, and I/O control
* Introduces the Inter-Integrated Circuit Protocol for embedded Linux drivers
* Covers multimedia device drivers using the Linux-Video subsystem and Linux-Audio framework
* Shows how Linux implements support for wireless technologies such as Bluetooth, Infrared, WiFi, and cellular networking
* Describes the entire driver development lifecycle, through debugging and maintenance
* Includes reference appendixes covering Linux assembly, BIOS calls, and Seq files

Be sure to also visit [http://elinuxdd.com/ the book's homepage] as it contains misc updates, errata, source code, etc...

==== User comments ====
Comment from Alan Cox “Probably the most wide ranging and complete Linux device driver book I’ve read.”.

Comment from [[User:Kaa-ching]]: I really liked the book. It is up-to-date (at least early 2008 it was :-) ) and comprehensive.

Comment from [[User:ThomasPetazzoni]] : This book is a nice addition to the traditional Linux Device Drivers. Not only because it is more up-to-date, but also because it covers a wider range of drivers. However, reading Linux Device Drivers first is probably recommended. In the end, I think both books are very complementary.

See also http://vig.pearsoned.co.uk/catalog/academic/product/0,1144,0132396556,00.html

[[Category:Books]]

Linux Device Drivers

2009-04-13T17:38:54Z

Kaa-ching: add more info.

== Linux Device Drivers, Third Edition ==

'''[http://oreilly.com/catalog/9780596005900/ Christopher Jonathan Corbet, Alessandro Rubini, Greg Kroah-Hartman, O'Reilly Media, Inc], ISBN 13: 9780596005900'''

==== First Edition ====

==== Second Edition ====
Adding Jonathan Corbet as author.

Second edition of this book is [http://www.xml.com/ldd/chapter/book/ freely available online].

It details the 2.4 kernel series.

==== Third Edition ====
The third edition, adding Greg Kroah-Hartman as an author discusses driver development for the 2.6.10 kernel.

Therefore, the book by now is significantly out of date, but Jonathan has kept a list of all things changing since then at the [www.lwn.net LWN.net] site:
* http://lwn.net/Articles/2.6-kernel-api/

==== User comments ====

n/a

[[Category:Books]]