eLinux.org - User contributions [en]

ELC 2011 Presentations

2011-05-04T20:23:52Z

Berkus: reorganize and highlight sessions

Presenters, Demo-ers, Participants:
Thanks very much for your participation in Linux Foundation's [http://events.linuxfoundation.org/events/embedded-linux-conference Embedded Linux Conference 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 send me an e-mail and we'll try to track it down.

== Videos ==

Videos from the conference will be made available at a future date.

== 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'''
|-
| Dirk Hohndel & Richard Purdie
| The Yocto Project
| No slides used.
|-
| Arnd Bergmann (IBM)
| Becoming Part of the Linux Kernel Community
| [[Media:Elc2011_bergmann_keynote.pdf|Elc2011_bergmann_keynote.pdf]]
|-
|
|
|
|}

<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:00am
|-
| Keshava Munegowda (Texas Instruments)
| Power Fail Safe FAT File Systems
| [[Media:Elc2011_munegowda.pdf|Elc2011_munegowda.pdf]]
|-
| Frank Rowand (Sony)
| Identifying Embedded Real-Time Latency Issues: I-Cache and Locks
| [[Media:Elc2011_rowand.pdf|Elc2011_rowand.pdf]]
|-
| Bruno Cardoso Lopes (University of Campinas)
| LLVM, Clang and Embedded Linux Systems
| [[Media:Elc2011_lopes.pdf|Elc2011_lopes.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 11:00am
|-
| Steven Rostedt (Red Hat)
| Kernel Shark Tutorial
| [[Media:Elc2011_rostedt.pdf|Elc2011_rostedt.pdf]]
|-
| Kang Dongwook (ETRI)
| Snapshot Booting on Embedded Linux
| [[Media:Elc2011_kang.pdf|Elc2011_kang.pdf]]
|-
| Khem Raj
| State of OpenEmbedded Internal Toolchain and SDKs
| [[Media:Elc2011_raj_sdk.pdf|Elc2011_raj_sdk.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 1:30pm
|-
| David Rusling (Linaro)
| Linaro: A Year of Change
| [[Media:Linaro_2011_ELC_Talk.odp|Linaro_2011_ELC_Talk.odp]] [[Media:Linaro_2011_ELC_Talk.pdf|Linaro_2011_ELC_Talk.pdf]]
|-
| Hai Shalom (Atheros)
| Control, Recover and Debug Your Embedded Product with PCD
| [[Media:Elc2011_shalom.odp|Elc2011_shalom.odp]]
|-
| Gene Sally
| Zigbee Networking & Linux
|
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 2:30pm
|-
| Xi Wang (Broadcom)
| Solving Real-Time Scheduling Problems with RT_PREEMPT and Deadline-Based Scheduler
| [[Media:Elc2011_xi_rt.pdf|Elc2011_xi_rt.pdf]]
|-
| Mike Anderson (The PTR Group)
| ARM Neon Instruction Set and Why You Should Care
| [[Media:Elc2011_anderson_arm.pdf|Elc2011_anderson_arm.pdf]]
|-
| Darren Hart (Intel)
| Yocto Project: Practical Kernel Development Tutorial
|
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 3:40pm
|-
| Arnd Bergmann (IBM)
| Optimizations for Cheap Flash Media
| [[Media:Elc2011_bergmann.pdf|Elc2011_bergmann.pdf]]
|-
| Wolfram Sang (Pengutronix)
| Developer's Diary: Helping the Process
| [[Media:Elc2011_sang.pdf|Elc2011_sang.pdf]]
|-
| Rajesh Lal (Nokia)
| Fun with QML and JavaScript
| [[Media:Elc2011_lal.pdf|Elc2011_lal.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 1, 4:40pm
|-
| Thomas Gleixner (linutronix)
| RT-Preempt: What's The State and Why There is No Roadmap
| [[Media:Elc2011_gleixner.pdf|Elc2011_gleixner.pdf]]
|-
| Jason Kridner (Texas Instruments)
| High-Level Web Interface to Low-Level Linux I/O on the Beagleboard
| [[Media:Elc2011_kridner.pdf|Elc2011_kridner.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 10:00am
|-
| Paul Mundt (Renesas)
| Working with HardIRQs: Life Beyond Static IRQ Assignments
| [[Media:Elc2011_mundt.pdf|Elc2011_mundt.pdf]]
|-
| Amit Kucheria (Linaro)
| Powerdebugging Inside Linaro
| [[Media:Elc2011_kucheria.odp|Elc2011_kucheria.odp]] [[Media:Elc2011_kucheria.pdf|Elc2011_kucheria.pdf]]
|-
| Mike Anderson (The PTR Group)
| High-Performance Computing using GPUs
| [[Media:Elc2011_anderson_gpu.pdf|Elc2011_anderson_gpu.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 11:00am
|-
| Paul Larson (Linaro)
| Linaro Automated Validation on ARM
| [[Media:ELC2011-Linaro-Validation.pdf|ELC2011-Linaro-Validation.pdf]]
|-
| Dave Stewart (Intel)
| The Yocto Project and its Application Development Toolkit (ADT) - The Answer to Effective Embedded Application Development
| [[Media:ELC_Yocto_ADT_2011_davest.odp|ELC_Yocto_ADT_2011_davest.odp]]
|-
| Damian Hobson Garcia (Igel), Katusya Matsubara, Takanari Hayama, Hisao Munakata
| Integrating a Hardware Video Codec into Android Stagefright using OpenMAX IL
| [[Media:Elc2011_garcia.pdf|Elc2011_garcia.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 1:30pm
|-
| Koen Kooi (Texas Instruments)
| Integrating OpenEmbedded and Yocto
| [[Media:Elc2011_kooi.pdf|Elc2011_kooi.pdf]]
|-
| Mark Gross (Intel)
| How to Power Tune a Device Running on a Linux Kernel for Better Suspend Battery Life
| [[Media:Elc2011_gross.pdf|Elc2011_gross.pdf]]
|-
| Remi Lorriaux (Adeneo Embedded)
| Real-time Audio on Embedded Devices
| [[Media:Elc2011_lorriaux.pdf|Elc2011_lorriaux.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 2:30am
|-
| Magnus Damm
| Runtime PM: Upstream I/O Device Power Management
| [[Media:Elc2011_damm.pdf|Elc2011_damm.pdf]]
|-
| Jesse Barker
| Linux Graphics Meets the ARM Ecosystem
| [[Media:Elc2011_barker.pdf|Elc2011_barker.pdf]]
|-
| David Anders (Texas Instruments)
| Board Bringup: Open Source Hardware and Software Tools
| [[Media:Elc2011_anders.pdf|Elc2011_anders.pdf]] <br> [[Open_tools|Open Tools References]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 2, 3:40pm
|-
| John Williams (PetaLogix)
| Dynamic Co-simulation of FPGA-based Linux Systems-on-Chip
| [[Media:Elc2011_williams.pdf|Elc2011_williams.pdf]]
|-
| Sumit Semwal (Texas Instruments)
| Media Controller Framework (MCF) For OMAP2+ Display Subsystem
| [[Media:Elc2011_semwal.pdf|Elc2011_semwal.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 9:00am
|-
| John Stultz (IBM)
| Android for Servers?
| [[Media:Elc2011_stultz.pdf|Elc2011_stultz.pdf]]
|-
| Anand Gadiyar (Texas Instruments)
| Tools and Techniques for Debugging Embedded Systems
| [[Media:Elc2011_gadiyar.pdf|Elc2011_gadiyar.pdf]]
|-
| Hans Verkuil (Cisco)
| Video4linux: Progress, New videobuf2 Framework and the Future
| [[Media:Elc2011_verkul.odp|Elc2011_verkul.odp]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 10:00am
|-
| Yoshiya Hirase (Nokia)
| Faster Resume For More Energy Savings on MeeGo
| [[Media:Elc2011_hirase.pdf|Elc2011_hirase.pdf]]
|-
| Jake Edge (Linux Weekly News)
| What Embedded Linux Developers Should Know About IPv6
| [[Media:Elc2011_edge.pdf|Elc2011_edge.pdf]]
|-
| Grégoire Gentil (Always Innovating)
| Hot Multi-OS Switch: How to run Ubuntu, ChromiumOS, Android at the Same Time on an Embedded Device
| [[Media:ELC-AlwaysInnovating-Gentil.pdf|ELC-AlwaysInnovating-Gentil.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 11:00am
|-
| Xi Wang (Broadcom)
| Controlling Memory Footprint at All Layers: Linux Kernel, Applications, Libraries and Toolchain
| [[Media:Elc2011_xi_mem.pdf|Elc2011_xi_mem.pdf]]
|-
| Tom Zanussi and Saul Wold
| Building Custom Embedded Images with Yocto
| [[Media:Elc2011_zanussi_wold.odp|Elc2011_zanussi_wold.odp]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 2:30pm
|-
| Philip Balister
| A High Performance Interface Between the OMAP3 and an FPGA
| [[Media:Omap3-fpga.pdf‎|Omap3-fpga.pdf‎]]
|-
| Jean Pihet (NewOldBits.com)
| The Evolution of Tracing and Profiling for Power Management and Accelerators
| [[Media:Elc2011_pihet.pdf|Elc2011_pihet.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 3:40pm
|-
| Elizabeth Flanagan (Intel)
| Delivering Predictability: The Yocto Project Autobuilder, Automated Sanity Testing, License Collection, and Build Statistics Tracking
| [[Media:Elc2011_flanagan.pdf|Elc2011_flanagan.pdf]]
|-
| Mythri pk
| Bringing up HDMI Display for OMAP4 Panda Board - Design, Challenges and Lessons Learned
| [[Media:HDMI_ELC_mythripk.pdf|HDMI_ELC_mythripk.pdf]]
|-
|- bgcolor="#a0c0c0"
| colspan="3" | Day 3, 4:40pm
|-
| Khem Raj
| Debug/Develop uClibc with QEMU
| [[Media:Elc2011_raj_qemu.pdf|Elc2011_raj_qemu.pdf]]
|-
| Guntur Ravi Sankar (Samsung)
| What are and How to find a program's unused DSOs
| [[Media:ELC_2011_Ravi.pdf‎|ELC_2011_Ravi.pdf‎]]
|}

<br />

==Birds of a Feather Session ==
{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Birds-of-a-Feather Sessions'''
|- bgcolor="#c0e0e0"
| align="center" | '''Presenter(s)'''
| align="center" | '''Session Description'''
| align="center" | '''Presentation'''
|-
| Bill Traynor
| elinux.org wiki BOF
| [[Media:Elinux_org_BOF.pdf|Elinux_org_BOF.pdf]]
|-
| Jeff Osier-Mixon (Intel)
| Yocto Project Community BoFs [[Elc2011BoF_YoctoNotes|(Notes)]]
| No slides.
|-
| Luca Coelho (Texas Instruments)
| OpenLink WLAN Hacking Workshop
|[[Media:Openlink-workshop-final.pdf|Openlink Workshop slides (PDF file)]]
|-
| Alison Chaiken (Nokia)
| [[Media:BoFSlides.odp|"MeeGo BoFs: New Linux Platform for Mobile Computing Devices"]] (ODP format)
| [[Media:MeeGoBoFELC2011Slides.pdf|MeeGo BoF Slides (PDF file)]]
|-
| Jason Kridner (Texas Instruments)
| BeagleBoard Hands-On Workshop
|
|-
| Yoshitake Kobayashi (Toshiba)
| Moving Forward: Overcoming Compatibility Issues BoFs
| [[Media:Elc2011_kobayashi.pdf|Elc2011_kobayashi.pdf]]
|}

== 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:ELC]]

File:Elc2010-tracker-talk.pdf

2010-04-13T05:32:03Z

Berkus:

2010-04-13T04:02:00Z

Berkus:

2009-04-07T01:26:32Z

Berkus: fix formatting

Here's a good overview on compiler optimizations:
http://en.wikipedia.org/wiki/Compiler_optimization

Here's some info about GCC optimization techniques:
http://www.redhat.com/software/gnupro/technical/gnupro_gcc.html

Effects of optimization options are explained in [http://www.linuxjournal.com/article/7269 this LJ article].

A note of warning from [http://www.gentoo.org/doc/en/gcc-optimization.xml Gentoo wiki] on optimization flags:

-O3: This is the highest level of optimization possible, and also the riskiest. It will take a longer time to compile your code with this option, and in fact it should not be used system-wide with gcc 4.x. The behavior of gcc has changed significantly since version 3.x. In 3.x, -O3 has been shown to lead to marginally faster execution times over -O2, but this is no longer the case with gcc 4.x. Compiling all your packages with -O3 will result in larger binaries that require more memory, and will significantly increase the odds of compilation failure or unexpected program behavior (including errors). The downsides outweigh the benefits; remember the principle of diminishing returns. Using -O3 is not recommended for gcc 4.x.

In the following [http://gcc.gnu.org/ml/gcc/2004-04/msg01409.html e-mail],
Jim Wilson, who apparently supports gcc, writes:

<pre>
From: Jim Wilson <wilson at specifixinc dot com>
Date: Thu, 29 Apr 2004 15:58:28 -0700
Subject: Re: optimization issue about -O2 and -Os
------------------------------------------------------------
...
The -Os option is buggy. You might want to report a bug into our bugzilla
bug datase. See http://gcc.gnu.org/bugs.html for more info on reporting bugs.

Though the -Os option is based on the -O2 option, it is a different option, that
generates different code, and has different bugs.
</pre>

[[Tim Riker]]: this is a bit overly dramtic. -Os is widely used and widely supported. The link is to a thread about general information and does not refer to any specific bug from what I can see. Try -Os out. If you have issues, try -O2 instead. In general -Os will work. Be very careful in tweaking kernel optimizations. There is kernel code that only works with the existing optimizations.

Compiler Optimization

2009-04-07T01:25:37Z

Berkus: add verbatim excerpt about dangers of -O3

Here's a good overview on compiler optimizations:
http://en.wikipedia.org/wiki/Compiler_optimization

Here's some info about GCC optimization techniques:
http://www.redhat.com/software/gnupro/technical/gnupro_gcc.html

Effects of optimization options are explained in [http://www.linuxjournal.com/article/7269 this LJ article].

A note of warning from [http://www.gentoo.org/doc/en/gcc-optimization.xml Gentoo wiki] on optimization flags:
<pre>
-O3: This is the highest level of optimization possible, and also the riskiest. It will take a longer time to compile your code with this option, and in fact it should not be used system-wide with gcc 4.x. The behavior of gcc has changed significantly since version 3.x. In 3.x, -O3 has been shown to lead to marginally faster execution times over -O2, but this is no longer the case with gcc 4.x. Compiling all your packages with -O3 will result in larger binaries that require more memory, and will significantly increase the odds of compilation failure or unexpected program behavior (including errors). The downsides outweigh the benefits; remember the principle of diminishing returns. Using -O3 is not recommended for gcc 4.x.
</pre>

In the following [http://gcc.gnu.org/ml/gcc/2004-04/msg01409.html e-mail],
Jim Wilson, who apparently supports gcc, writes:

<pre>
From: Jim Wilson <wilson at specifixinc dot com>
Date: Thu, 29 Apr 2004 15:58:28 -0700
Subject: Re: optimization issue about -O2 and -Os
------------------------------------------------------------
...
The -Os option is buggy. You might want to report a bug into our bugzilla
bug datase. See http://gcc.gnu.org/bugs.html for more info on reporting bugs.

Though the -Os option is based on the -O2 option, it is a different option, that
generates different code, and has different bugs.
</pre>

[[Tim Riker]]: this is a bit overly dramtic. -Os is widely used and widely supported. The link is to a thread about general information and does not refer to any specific bug from what I can see. Try -Os out. If you have issues, try -O2 instead. In general -Os will work. Be very careful in tweaking kernel optimizations. There is kernel code that only works with the existing optimizations.

Compiler Optimization

2009-04-07T01:21:01Z

Berkus: add link to -Ox optimizations article

System Size

2009-04-07T01:19:52Z

Berkus: add link to orphaned page

Here are some links to information and projects related to Linux system size.

== Technologies for decreasing system size ==
=== Kernel size reduction ===
==== Configuration Options ====
* [[Kernel Size Tuning Guide]] - document about measuring kernel size and configuring the kernel for smallest size

==== The Linux-tiny patchset ====
* The [[Linux Tiny]] patch set is a collection of patches which can be used to make the Linux kernel consume less space. The long-term goal of the Linux-tiny project is to mainline these patches. Several patches have been mainlined over the last few years, and work continues in this area.

==== Compiler options for reducing kernel size ====
An LWN article talks about three gcc options to shrink the kernel.

[http://lwn.net/Articles/67175/ Shrinking the Kernel with GCC]

The first option is -Os which is already in the tiny kernel patch.

Since version 3.4, gcc offered a -funit-at-a-time option.
This apparently made gcc do a much better job of inlining and dead code removal,
reducing the size of both text and data. It depended on another inlining patch.
According to gcc's manual, this option no longer does anything.

The -fwhole-program --combine option set is equivalent to grouping all source files
and making all variables static. These options are still supported by gcc, but not longer offered in BusyBox
configuration options. What happened?

Another option, -mregparm=3, seems to be x86 specific, it instructs the
compiler to use registers for the first three function arguments. by John Rigby

See [http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html] for all
available optimization switches.
See [[Compiler_Optimization]] for more details on effects of optimization options.

==== Runtime size of kernel ====
Often, the focus of memory size reduction for the kernel is on the size of the
statically compiled image for the kernel. However, the kernel also allocates
memory dynamically when it runs. On loading, the kernel creates several tables
for things like network and file system structures.

Here is a table showing different kernel hash tables, and their approximate
size for a 2.6 kernel. (Table taken from page 25 of
http://logfs.org/~joern/data_structures.pdf )

{| border="1" cellspacing="0" cellpadding="5" align="center"
!Hash Table !!memory < 512MiB RAM !! memory >=512MiB RAM
|-
! !!32b/64b !!32b/64b
|-
|TCP established ||96k/192k ||384k/768k
|-
|TCP bind || 64k/128k || 256k/512k
|-
|IP route cache || 128k/256k || 512k/1M
|-
|Inode-cache || 64k/128k || 64k/128k
|-
|Dentry cache || 32k/64k || 32k/64k
|-
||Total || 384k/768k || 1248k/2496k
|}

=== File system compression ===
For read-only data, it is useful to utilize a compressed file system.
The following are used heavily in embedded systems:
* Cramfs and SquashFS, for block storage.
* JFFS2 and its successor UBIFS, for flash (MTD) storage.

Note that Cramfs and Squashfs, due to their "write-only-once" nature, can also be used on MTD storage.

See the [[File Systems]] page for more information.

=== Shrinking your application ===
==== Compiler options for program size ====
You can use "gcc -Os" to optimize for size.

==== Stripping your program ====
You can use the 'strip' command to eliminate unneeded symbols from your application.
The 'strip' command should be included with your toolchain, and may be architecture-specific.
(I.e. you may need to run it with a toolchain prefix, like "arm-linux-strip")

Note that this makes debugging your application more difficult, because the debug
symbols are no longer available.

By default, strip just removes debug symbols. You can remove everything but the essential
symbols used for dynamic linking. To get the highest savings, use "strip --strip-unneeded <app>"

This can save a lot of space, especially if debug symbols were included in the build.

$ gcc -g hello.c -o hello
$ ls -l hello
-rwxrwxr-x 1 tbird tbird 6143 2009-02-10 09:43 hello
$ strip hello
$ ls -l hello
-rwxrwxr-x 1 tbird tbird 3228 2009-02-10 09:43 hello
$ strip --strip-unneeded hello
$ ls -l hello
-rwxrwxr-x 1 tbird tbird 3228 2009-02-10 09:43 hello

Now, compiles without debug symbols to start with:

$ gcc hello.c -o hello
$ ls -l hello
-rwxrwxr-x 1 tbird tbird 4903 2009-02-10 09:45 hello
$ strip hello
$ ls -l hello
-rwxrwxr-x 1 tbird tbird 3228 2009-02-10 09:45 hello

You can strip both executables as well as shared libraries.

There is a "super-strip" utility, which removes additional material from an ELF executable program (which 'strip'
usually misses). It is available at: http://muppetlabs.com/~breadbox/software/elfkickers.html
''This program appears to be obsolete now. I couldn't get it to compile on Fedora 8''.

Some information about stripping individual sections by hand, using the -R command is available at: http://reverse.lostrealm.com/protect/strip.html

==== Hand-optimizing programs, for size ====
If you are very intent on creating small binaries, you can use some techniques to manually
create the smallest Linux executables possible.

See [http://muppetlabs.com/~breadbox/software/tiny/teensy.html A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux]

=== Library savings ===
==== Use of a smaller libc ====
Glibc is the default C library used for Linux systems. Glibc is about 2 meg. in size. Other C libraries
are also available for Linux, and they offer varying degrees of compatibility and size savings.
In general, uClibc is considered a very good alternative to glibc, for systems where size is an issue.

* [http://uclibc.org/ uClibc] - small footprint but complete C library
* [http://www.fefe.de/dietlibc/ dietlibc] - another library to produce very small statically compiled executables.
* [http://www.kernel.org/pub/linux/libs/klibc/ klibc] - very small library for use in init ram filesystems
* [http://www.eglibc.org/home eglibc] - a version of glibc designed for embedded systems. Reduced footprint is one of the design goals.
* Subset Libc Specification - CELF once considered the possibility of creating a subset libc specification. Some companies have also examined the possibility of modularizing glibc, so that parts of it can be made configurable. Preliminary research indicates that this could be a very difficult thing, since glibc has very messy function interdependencies.

==== Static Linking ====
If your set of applications is small, sometimes it makes more sense to statically link
your applications than to use shared libraries. Shared libraries by default include all
symbols (functions and data structures) for the features a library provides. However, when
you static link a program to a library, only the symbols that are actually referenced
are linked in and included in the program.

==== Library reduction ====
It is possible to reduce the size of shared libraries, by eliminating unused symbols.

MontaVista released a tool for library optimization. This tool scans the entire file system,
and can rebuild the shared libraries for the system, including only the symbols needed for
the set of applications in the indicated file system.

Care needs to be taken with this approach, since it may make it difficult to use add-on
programs or or do in-field upgrades (since symbols required by the new software may not
be present in the optimized libraries). But for some fixed-function devices, this can
reduce your library footprint dramatically.

See http://libraryopt.sourceforge.net/

==== Deferred Library Loading ====
It is possible to reduce the RAM runtime footprint for a product, by lazily loading shared
libraries, and by breaking up library dependencies. Panasonic did some research into
a process called Deferred Library Loading, which they presented at ELC 2007.

See the [http://tree.celinuxforum.org/CelfPubWiki/ELC2007Presentations?action=AttachFile&do=get&target=DefferdDynamicLoading_20070417.pdf Deferred Dynamic Loading] presentation.

=== Execute-in-place ===
You can save RAM memory by using some text or data directly from flash.

==== Kernel XIP ====
By executing the kernel in-place from flash, it is possible to save RAM space.
*see [[Kernel XIP]]

==== Application XIP ====
By executing applications in-place from flash, it is possible to save RAM space.
*see [[Application XIP]]

==== Data Read In Place (DRIP) ====
This is a technique for keeping data in flash, until it is written to, and then
making a RAM page for it.
*see [[Data Read In Place]]

== Size measurement tools and techniques ==
=== Kernel size measurement data ===
* [http://www.selenic.com/bloatwatch/ Bloatwatch] - a kernel size regression analysis tool.
** Bloatwatch provides a great amount of detail, and the ability to compare the size of kernel versions over time.

=== How to measure the kernel image size ===
*to see the size of the major kernel sections (code and data):
:<code><nowiki>size vmlinux */built-in.o</nowiki></code>
<pre><nowiki>
[tbird@crest ebony]$ size vmlinux */built-in.o
text data bss dec hex filename
2921377 369712 132996 3424085 343f55 vmlinux
764472 35692 22768 822932 c8e94 drivers/built-in.o
918344 22364 36824 977532 eea7c fs/built-in.o
18260 1868 1604 21732 54e4 init/built-in.o
39960 864 224 41048 a058 ipc/built-in.o
257292 14656 34516 306464 4ad20 kernel/built-in.o
34728 156 2280 37164 912c lib/built-in.o
182312 2704 736 185752 2d598 mm/built-in.o
620864 20820 26676 668360 a32c8 net/built-in.o
1912 0 0 1912 778 security/built-in.o
133 0 0 133 85 usr/built-in.o
</nowiki></pre>
*to see the size of the largest kernel symbols:
** <code><nowiki>nm --size -r vmlinux</nowiki></code>
<pre><nowiki>
[tbird@crest ebony]$ nm --size -r vmlinux | head -10
00008000 b read_buffers
00004000 b __log_buf
00003100 B ide_hwifs
000024f8 T jffs2_garbage_collect_pass
00002418 T journal_commit_transaction
00002400 b futex_queues
000021a8 t jedec_probe_chip
00002000 b write_buf
00002000 D init_thread_union
00001e6c t tcp_ack
</nowiki></pre>

=== How to measure the memory usage at runtime ===
See [[Runtime Memory Measurement]] for a description of ways to measure runtime memory usage in Linux.

Also, see [[Accurate Memory Measurement]] for a description of techniques (and patches) which can be used to measure the runtime memory more accurately.

=== Linux size increase from 2.4 to 2.6 ===
Linux increased in size by between 10% and 30% from version 2.4 to 2.6. This incremental growth in kernel size has been a big concern by forum members.

Please see the [[Szwg Linux 26Data]] page for supporting data.

=== GCC Code-Size Benchmarking ===
CSiBE is a code size benchmark for the GCC compiler. The primary purpose of CSiBE is to monitor the size of the code generated by GCC. In addition, compilation time and code performance measurements are also provided.

[http://www.inf.u-szeged.hu/csibe/ CSiBE]

== Case Studies ==
* Motorola reduction of system size (presumably for cell phones) using 2.4 Linux: MotSizeReduction.ppt - this is a placeholder for this Powerpoint as it was too big to upload to the wiki. Email btraynor at gmail.com if you need it immediately.

== Other Tidbits on System Size ==
=== Memory leak detection for the kernel ===
Catalin Marinas of ARM has been recently (as of 2.6.17?) been posting a memory leak detector for the Linux kernel. It may get mainlined in the future. Here's a link to the LKML discussions around it: http://lkml.org/lkml/2006/6/11/39

=== How System Size may affect performance ===
It has long been theorized that reducing system size could provide a performance benefit
because it could reduce cache misses. There does not appear to be hard data to support
this theory on Linux, but this has been discussed on the kernel mailing list.

See [http://groups.google.com/group/linux.kernel/msg/e1f9f579a946333e?hl=en& this post by Linus Torvalds]

=== Stripping down the filesystem of a desktop distribution ===
Here is a good document with tips on how to strip out unneeded files from a desktop distribution.
The example distribution used here is Linux From Scratch, but the tips should work with many
distributions.

http://www.linuxfromscratch.org/hints/downloads/files/OLD/stripped-down.txt

[[Category:System Size]]

ARMCompilers

2009-04-07T01:14:42Z

Berkus: /* ARM Cortex Floating Point */

== gcc compiler ==

[http://www.codesourcery.com/ CodeSourcery] [http://www.codesourcery.com/gnu_toolchains/arm/download.html '''ARM GNU/Linux''' tool chain] is the version with the support for the latest ARM architecture. Mainline [http://gcc.gnu.org/ gcc] also has stable ARM support. Enhancements are made in the Codesourcery version first, and are then pushed back to mainline.

[http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 2007q3 version] is recommended. An [http://people.mozilla.com/~vladimir/misc/cs2007q3-armel.tar.gz ARM-native version of CS2007q3 has been built] as well. You can also install a native tool-chain from Angstrom.

Note: A user reports that he found the use of CodeSourcery tool chain version 2007q1-21 and 2008q1-126 as strange. He has been using [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 '''2007q3-51'''] for a couple of months now.

Note: Some users report problems using Linux installer version. If installer doesn't work for you, download tar version (section ''Advanced Packages''), copy extracted ''arm-2007q3'' directory to ''/opt/codesourcery/arm-none-linux-gnueabi/'' and add ''/opt/codesourcery/arm-none-linux-gnueabi/arm-2007q3/bin'' to your path.

* Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3 2007q3] has an issue with -Os option. There is a [http://groups.google.com/group/beagleboard/msg/d4170b16029920ee fix] (needs recompilation)

* Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3? 2008q1] has the following issues:
** Vectorization + NEON is broken
** building static binaries with cortex-a8 flag (or any ARMv7a core) is broken
** some armv6 compilations end in ICE.

* Note: CodeSourcery 2008q3 (now replaced by 2008q3-72) has the following issues:
** [http://hardwarebug.org/2008/10/11/codesourcery-gcc-2008q3-fail/ Broken NEON] support using ''-fmpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -O3''
** [http://www.beagleboard.org/irclogs/index.php?date=2008-10-11#T20:32:17 Miscompiles] U-Boot

* Note: CodeSourcery 2008q3-72 has the following issues:
** See [http://hardwarebug.org/2008/11/28/codesourcery-fails-again/ small problem with vectorization].

Note: If you will use only [[BeagleBoardAndOpenEmbeddedGit|OpenEmbedded (OE)]] to build code for your Beagle, you don't need to download the CodeSourcery compiler. OE builds a cross-compiler from source as part of the bitbake process.

== ARM RVDS compiler ==

ARM has the [http://www.arm.com/products/DevTools/RVDSPro.html Realview Developer Suite], with arguably better code generation than gcc. An [http://www.arm.com/products/DevTools/RVDSEvalCD.html DVD evaluation version] is available (or download via internet by [https://silver.arm.com/login/register.tm registering] followed by [https://silver.arm.com/licensing/autoeval.tm download]).

ARM RVDS tools can be used to generate Linux applications and shared-libraries, by following the [http://infocenter.arm.com/help/topic/com.arm.doc.dai0212a/DAI0212A_building_linux_apps_with_rvct40_and_gnu.pdf Apps Note 212 Building Linux applications using RVCT v4.0 and the GNU Tools and Libraries]

ARM RVDS can also work in [http://www.scratchbox.org/ Scratchbox], by following [http://infocenter.arm.com/help/topic/com.arm.doc.dai0221a/DAI0221A_rvds_compiler_scratchbox.pdf Apps Note 221 RealView Development Suite 4.0 ARM Compiler for Scratchbox]

== 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.

ARMCompilers

2009-04-07T01:10:09Z

Berkus: /* ARM Cortex Floating Point */

== gcc compiler ==

[http://www.codesourcery.com/ CodeSourcery] [http://www.codesourcery.com/gnu_toolchains/arm/download.html '''ARM GNU/Linux''' tool chain] is the version with the support for the latest ARM architecture. Mainline [http://gcc.gnu.org/ gcc] also has stable ARM support. Enhancements are made in the Codesourcery version first, and are then pushed back to mainline.

[http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 2007q3 version] is recommended. An [http://people.mozilla.com/~vladimir/misc/cs2007q3-armel.tar.gz ARM-native version of CS2007q3 has been built] as well. You can also install a native tool-chain from Angstrom.

Note: A user reports that he found the use of CodeSourcery tool chain version 2007q1-21 and 2008q1-126 as strange. He has been using [http://www.codesourcery.com/gnu_toolchains/arm/portal/release313 '''2007q3-51'''] for a couple of months now.

Note: Some users report problems using Linux installer version. If installer doesn't work for you, download tar version (section ''Advanced Packages''), copy extracted ''arm-2007q3'' directory to ''/opt/codesourcery/arm-none-linux-gnueabi/'' and add ''/opt/codesourcery/arm-none-linux-gnueabi/arm-2007q3/bin'' to your path.

* Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3 2007q3] has an issue with -Os option. There is a [http://groups.google.com/group/beagleboard/msg/d4170b16029920ee fix] (needs recompilation)

* Note: CodeSourcery [http://groups.google.com/group/beagleboard/msg/63163389873902c3? 2008q1] has the following issues:
** Vectorization + NEON is broken
** building static binaries with cortex-a8 flag (or any ARMv7a core) is broken
** some armv6 compilations end in ICE.

* Note: CodeSourcery 2008q3 (now replaced by 2008q3-72) has the following issues:
** [http://hardwarebug.org/2008/10/11/codesourcery-gcc-2008q3-fail/ Broken NEON] support using ''-fmpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -O3''
** [http://www.beagleboard.org/irclogs/index.php?date=2008-10-11#T20:32:17 Miscompiles] U-Boot

* Note: CodeSourcery 2008q3-72 has the following issues:
** See [http://hardwarebug.org/2008/11/28/codesourcery-fails-again/ small problem with vectorization].

Note: If you will use only [[BeagleBoardAndOpenEmbeddedGit|OpenEmbedded (OE)]] to build code for your Beagle, you don't need to download the CodeSourcery compiler. OE builds a cross-compiler from source as part of the bitbake process.

== ARM RVDS compiler ==

ARM has the [http://www.arm.com/products/DevTools/RVDSPro.html Realview Developer Suite], with arguably better code generation than gcc. An [http://www.arm.com/products/DevTools/RVDSEvalCD.html DVD evaluation version] is available (or download via internet by [https://silver.arm.com/login/register.tm registering] followed by [https://silver.arm.com/licensing/autoeval.tm download]).

ARM RVDS tools can be used to generate Linux applications and shared-libraries, by following the [http://infocenter.arm.com/help/topic/com.arm.doc.dai0212a/DAI0212A_building_linux_apps_with_rvct40_and_gnu.pdf Apps Note 212 Building Linux applications using RVCT v4.0 and the GNU Tools and Libraries]

ARM RVDS can also work in [http://www.scratchbox.org/ Scratchbox], by following [http://infocenter.arm.com/help/topic/com.arm.doc.dai0221a/DAI0221A_rvds_compiler_scratchbox.pdf Apps Note 221 RealView Development Suite 4.0 ARM Compiler for Scratchbox]

== 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

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

BeagleBoard

2009-04-07T01:04:03Z

Berkus: /* Errata */

[[Category: Linux]]
[[Category: OMAP]]
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].

=Events=
* March 31st 2009 : [http://groups.google.com/group/beagleboard/browse_thread/thread/b15cf8a5797c73a2 Silica - Free TI - ARM OMAP Workshop], Brussels, Europe
* [http://code.google.com/soc/ Google Summer of Code 2009]: [[BeagleBoard/GSoC|BeagleBoard.org specific page]]

=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 it's 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
|Audio CODEC, USB port, power-on reset and power management, pin-compatible with the [http://focus.ti.com/docs/prod/folders/print/tps65950.html TPS65950] chip
|-
|'''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)
* 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 HW Reference Manual (rev. B7.2)].

==Schematic==

Schematic of BeagleBoard Rev. B7 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. B7.2)], from [http://beagleboard.org/hardware/design BeagleBoard.org design page] or in [http://xgoat.com/proj/beagleboard/schematic.pdf 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. B7 is available as part of [http://beagleboard.org/static/BBSRM_latest.pdf BeagleBoard HW Reference Manual (rev. B7.2)] or from [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
* At 600MHz OMAP35x is considered to be 'overdrive' and it does not have the same life expectancy
* Higher than 600MHz 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 table 3-3 of the [http://focus.ti.com/lit/ds/symlink/omap3530.pdf OMAP3530 data sheet]. Some numbers:

{| border="1"
||'''ARM'''||'''DSP'''||'''core voltage'''
|-
|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

See [http://git.mansr.com/?p=u-boot;a=commitdiff;h=045149ea1076575f773079677a3d1b01ff71757c Mans' hack] to configure clock in U-Boot (V1) to 600MHz.

==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. See [[BeagleBoardRawLCD|interfacing to Raw LCD Panels]] article or [http://digitalsurveyinstruments.com/beagleperiphials/hdmi2parallel/doc/index.htm hdmi to parallel]for a workaround method.

=Availability=

BeagleBoards, currently Rev. C2 boards, are available from [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 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: German (Europe) users can order from a German shop, too. For higher price, though. [http://shop.embedded-projects.net/product_info.php?language=en&info=p140 Embedded Projects Shop] sells BeagleBoard for EUR 199.00 + 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.

==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.

==Beagle cases==

Some nice cases for your BeagleBoard are available from [http://specialcomp.com/beagleboard/ Special Computing]. See [http://groups.google.com/group/beagleboard/browse_thread/thread/1c82316019633e51 SketchUp 3D model] if interested in 3D models from Beagle, too.

=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==
* [http://www.tincantools.com/ TinCanTools] is in the process of developing an Expansion-Prototype Board for the BeagleBoard, comments and suggestions are welcome. [[Media:bb-expansion.pdf|Schematic]].
* [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 availble through a yet to be annnounced outlet.

==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.

==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 HS hub.

===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 would let BeagleBoard unmodified.
</td><td>[[Image:usb_otg.png]]</td></tr></table>

==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 the 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 # mmcinit
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 'mmcinit ; 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 Code Sourcery GCC 2007q3):

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

===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

===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.

==Cortex A8 ARM==

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.

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

===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 such to render text and graphics
* Bluez - official Linux Bluetooth stack

==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.

=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.net/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://omapzoom.org/gf/project/omapandroid/wiki/ 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]]

==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.

==Debian ARM==

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

==Handhelds Mojo ARM==

See [[BeagleBoardHandheldsMojo|Handhelds Mojo (ARM)]] (formerly known as Ubuntu (ARM)) installation guide how to install Handhelds Mojo (ARM) port of Ubuntu on BeagleBoard.

=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)

Some guy 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]

=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]

==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

==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]
==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!
==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
* [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

==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]

==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=

* OMAP1 OMAP5912 (ARM9 + C5x DSP) based [[OSK|OSK]] board.
* OMAP3 OMAP3430 based [http://www.logicpd.com/products/devkit/ti/zoom_mobile_development_kit Zoom MDK]
* 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 based [http://www.alwaysinnovating.com/touchbook/ Touch Book]

[[Category:Development Boards]]

User:Berkus

2009-04-06T17:46:08Z

Berkus:

Skype developer (mainly for embedded systems).