http://elinux.org/api.php?action=feedcontributions&user=Dirk&feedformat=atomeLinux.org - User contributions [en]2013-05-19T17:29:25ZUser contributionsMediaWiki 1.21alphahttp://elinux.org/Boot_TimeBoot Time2011-05-04T18:26:35Z<p>Dirk: Link to the patch description</p>
<hr />
<div>== Introduction ==<br />
Boot Time includes topics such as measurement, analysis, human factors, initialization techniques, and reduction techniques.<br />
The time that a product takes to boot directly impacts the first perception an end user has of the product.<br />
Regardless of how attractive or well designed a consumer electronic device is, the time required to move the device from off to an interactive, usable state is critical to obtaining a positive end user experience. Turning on a device is Use Case #1.<br />
<br />
Booting up a device involves numerous steps and sequences of events. In order to use consistent terminology, the<br />
[[Bootup Time Working Group]] of the CE Linux Forum came up with a list of terms and their widely accepted definitions<br />
for this functionality area. See the following page for these terms:<br />
* [[Boot-up Time Definition Of Terms]]<br />
<br />
== Technology/Project Pages ==<br />
The following are individual pages with information about various technologies relevant to improving Boot Time for Linux. Some of these describe local patches available on this site. Others point to projects or patches maintained elsewhere.<br />
<br />
=== Measuring Boot-up Time ===<br />
*[[Printk Times]] - simple system for showing timing information for each printk.<br />
*[[Kernel Function Trace]] - system for reporting function timings in the kernel.<br />
*[[Linux Trace Toolkit]] - system for reporting timing data for certain kernel and process events.<br />
*[http://oprofile.sourceforge.net/news/ Oprofile] - system-wide profiler for Linux.<br />
*[[Bootchart]] - a tool for performance analysis and visualization of the Linux boot process. Resource utilization and process information are collected during the user-space portion of the boot process and are later rendered in a PNG, SVG or EPS encoded chart.<br />
*[http://people.redhat.com/berrange/systemtap/bootprobe/ Bootprobe] - a set of [[System Tap]] scripts for analyzing system bootup.<br />
* and, let us not forget: "cat /proc/uptime"<br />
* [[Tims Fastboot Tools#grabserial | grabserial]] - a nice utility from Tim Bird to log and timestamp console output<br />
* [[Tims Fastboot Tools#Tim's quick and dirty process trace|process trace]] - a simple patch from Tim Bird to log exec, fork and exit system calls.<br />
* [http://pengutronix.de/software/ptx_ts/index_en.html ptx_ts] - Pengutronix' TimeStamper: A small filter prepending timestamps to STDOUT; a bit similar to grabserial but not limited to serial ports<br />
* [[Initcall Debug]] - a kernel command line option to show time taken for initcalls.<br />
* See also: [[Kernel Instrumentation]] which lists some known kernel instrumentation tools. These are of interest for measuring kernel startup time.<br />
<br />
=== Technologies and Techniques for Reducing Boot Time ===<br />
==== Bootloader speedups ====<br />
*[[Kernel XIP]] - Allow kernel to be executed in-place in ROM or FLASH.<br />
*[[DMA Copy Of Kernel On Startup]] - Copy kernel from Flash to RAM using DMA<br />
*[[Uncompressed kernel]] - An uncompressed kernel might boot faster<br />
*[[Fast Kernel Decompression]]<br />
<br />
==== Kernel speedups ====<br />
*[[Disable Console]] - Avoid overhead of console output during system startup.<br />
*Disable bug and printk - Avoid the overhead of bug and printk. Disadvantage is that you loose a lot of info.<br />
*[[RTC No Sync]] - Avoid delay to synchronize system time with RTC clock edge on startup.<br />
*[[Short IDE Delays]] - Reduce duration of IDE startup delays (this is effective but possibly dangerous).<br />
*[[Hardcode kernel module info]] - Reduce the overhead of loading a module, by hardcoding some information used for loading the relocation information<br />
*[[IDE No Probe]] - Force kernel to observe the ide<x>=noprobe option.<br />
*[[Preset LPJ]] - Allow the use of a preset loops_per_jiffy value.<br />
*[[Asynchronous function calls]] - Allow probing or other functions to proceed in parallel, to overlap time-consuming boot-up activities.<br />
**[[Threaded Device Probing]] - Allow drivers to probe devices in parallel. (not mainlined, now deprecated?)<br />
*[[Reordering of driver initialization]] - Allow driver bus probing to start as soon as possible.<br />
*[[Deferred Initcalls]] - defer non-essential module initialization routines to after primary boot<br />
*NAND ECC improvement - The pre 2.6.28 nand_ecc.c has room for improvement. You can find an improved version in the mtd git at http://git.infradead.org/mtd-2.6.git?a=blob_plain;f=drivers/mtd/nand/nand_ecc.c;hb=HEAD. Documentation for this is in http://git.infradead.org/mtd-2.6.git?a=blob_plain;f=Documentation/mtd/nand_ecc.txt;hb=HEAD. This is only interesting if your system uses software ECC correction.<br />
*Check what kernel memory allocator you use. Slob or slub might be better than slab (which is the default in older kernels) <br />
*If your system does not need it, you can remove SYSFS and even PROCFS from the kernel. In one test removing sysfs saved 20 ms.<br />
*Carefully investigate all kernel configuration options on whether they are applicable or not. Even if you select an option that is not used in the end, it contributes to the kernel size and therefore to the kernel load time (assuming you are not doing kernel XIP). Often this will require some trial and measure! E.g. selecting CONFIG_CC_OPTIMIZE_FOR_SIZE (found under general setup) gave in one case a boot improvement of 20 ms. Not dramamtic, but when reducing boot time every penny counts!<br />
*Moving to a different compiler version might lead to shorter and/or faster code. Most often newer compilers produce better code. You might also want to play with compiler options to see what works best.<br />
* If you use initramfs in your kernel and a compressed kernel it is better to have an uncompressed initramfs image. This is to avoid having to uncompress data twice. A patch for this has been submitted to LKML. See http://lkml.org/lkml/2008/11/22/112 <br />
<br />
===== File System issues =====<br />
Different file systems have different initialization (mounting) times, for the same data sets. This<br />
is a function of whether meta-data must be read from storage into RAM or not, and what algorithms are<br />
used during the mount procedure.<br />
<br />
* [[Filesystem Information]] - has information about boot-up times of various file systems<br />
* [[File Systems]] - has information on various file systems that are interesting for embedded systems. Also includes some improvement suggestions.<br />
* [[Avoid Initramfs]] - explains on why intramfs should be avoided if you want to minimize boot time<br />
* Split partitions. If mounting a file system takes long, you can consider splitting that filesystem in two parts, one with the info that is needed during or immediately after boot, and one which can be mounted later on.<br />
* [[Ramdisks demasked]] - explains why using a ram disk generally results in a longer boot time, not a shorter one.<br />
<br />
==== User-space and application speedups ====<br />
* [[Optimize RC Scripts]] - Reduce overhead of running RC scripts<br />
* [[Parallel RC Scripts]] - Run RC scripts in parallel instead of sequentially<br />
* [[Application XIP]] - Allow programs and libraries to be executed in-place in ROM or FLASH<br />
* [[Pre Linking]] - Avoid cost of runtime linking on first program load<br />
* Statically link applications. This avoids the costs of runtime linking. Useful if you have only a few applications. In that case it could also reduce the size of your image as no dynamic libraries are needed<br />
* GNU_HASH: ~ 50% speed improvement in dynamic linking<br />
** See http://sourceware.org/ml/binutils/2006-06/msg00418.html<br />
* [[Application Init Optimizations]] - Improvements in program load and init time via: <br />
** use of mmap vs. read<br />
** control over page mapping characteristics.<br />
* [[Include modules in kernel image]] - Avoid extra overhead of module loading by adding the modules to the kernel image<br />
* Speed up module loading - Use Alessio Igor Bogani's kernel patches to improve module loading time by "[http://marc.info/?l=linux-embedded&m=130296040620175&w=2| Speed up the symbols' resolution process]" ([http://marc.info/?l=linux-kernel&m=130296044420203&w=2| Patch 1], [http://marc.info/?l=linux-embedded&m=130296044420197&w=2| Patch 2], [http://marc.info/?l=linux-embedded&m=130296044420200&w=2| Patch 3], [http://marc.info/?l=linux-kernel&m=130296062420328&w=2| Patch 4], [http://marc.info/?l=linux-embedded&m=130445535913197&w=2| Patch 5]).<br />
* Avoid udev, it takes quite some time to populate the /dev directory. In an embedded system it is often known what devices are present and in any case you know what drivers are available, so you know what device entries might be needed in /dev. These should be created statically, not dynamically. mknod is your friend, udev is your enemy.<br />
* If you still like udev and also like fast boot-up's, you might go this way: start your system with udev enabled and make kind of a backup of the created device nodes. Now, modify your init script like this: instead running udev, copy the device nodes that you just made a backup of into the device tree. Now, install the hotplug-daemon like you always do. That trick avoids the device node creation at startup but stills lets your system create device nodes later on. <br />
* If your device has a network connection, preferably use static IP addresses. Getting an address from a DHCP server takes additional time and has extra overhead associated with it.<br />
* Moving to a different compiler version might lead to shorter and/or faster code. Most often newer compilers produce better code. You might also want to play with compiler options to see what works best.<br />
* If possible move from glibc to uClibc. This leads to smaller executables and hence to faster load times.<br />
* library optimiser tool: http://libraryopt.sourceforge.net/ <br/> This will allow you to create an optimised library. As unneeded functions are removed this should lead to a performance gain. Normally there will be library pages which contain unused code (adjacent to code that is used). After optimizing the library this does not occur any more, so less pages are needed and hence less page loads, so some time can be saved.<br />
* Function reordering: http://www.celinux.org/elc08_presentations/DDLink%20FunctionReorder%2008%2004.pdf <br/> This is a technique to rearrange the functions within an executable so they appear in the order they are needed. This improves the load time of the application as all initialization code is grouped into a set of pages, instead of being scattered over a number of pages.<br />
<br />
==== Suspend related improvements ====<br />
Another approach to improve boot time is to use a suspend related mechanism. Two approaches are known.<br />
* Using the standard hibernate/resume approach. This is what has been demonstrated by Chan Ju, Park, from Samsung. See sheet 23 and onwards from this [[Media:LinuxBootupTimeReduction4DSC.ppt|PPT]] and section 2.7 of this [http://www.kernel.org/doc/ols/2006/ols2006v2-pages-239-248.pdf paper]. <br /> Issue with this approach is that flash write is much slower than flash read, so the actual creation of the hibernate image might take quite a while.<br />
* Implementing snapshot boot. This is done by Hiroki Kaminaga from Sony and is described at [[Suspend To Disk For ARM|snapshot boot for ARM]] and http://elinux.org/upload/3/37/Snapshot-boot-final.pdf<br />This is similar to hibernate and resume, but the hibernate file is retained and used upon every boot. Disadvantage is that no writable partitions should be mounted at the time of making the snapshot. Otherwise inconsistencies will occur if a partition is modified, while applications in the hibernate file might have information in the snapshot related to the unmodified partition.<br />
<br />
==== Miscellaneous topics ====<br />
<br />
[[About Compression]] discusses the effects of compression on boot time. This can affect both the kernel boot time as well as user-space startup.<br />
<br />
==== Uninvestigated speedups ====<br />
<br />
This section is a holding pen for ideas for improvement that are not implemented yet but that could result in a boot time gain. Please leave a note here if you are working on one of these items to avoid duplicate work.<br />
<br />
* '''Prepopulated buffer cache''' - As initramfs performs an additional copy of the data the idea is to have a prepopulated buffer cache. A simplistic scenario would allow dumping the buffer cache when the booting is completed and the user applications have initialised. This data then could be used in a subsequent boot to initialize the buffer cache (of course without copying). A possible approach would be to have those data to reside into the kernel image and use them directly. Alternately they could be loaded separately. <br /> Unfortunately my knowledge of the internals in this section is not yet good enough to do a trial implementation.<br /> Caveats:<br />
** is it possible to have the buffer cache split into two different parts, one which is statically allocated, one which is dynamically allocated?<br />
** the pages in the prepopulated buffer cache probably cannot be discarded, so they should be pinned<br />
** apart from the buffer cache data itself also some other variables might need restoring<br />
** a similar approach could also be used for the cached file data.<br />
*'''Dedicated fs''' - currently a lot of abstraction is done in fs to make a nice abstraction allowing easy addition of new filesystems and creating a unified view of those filesystem. While this is pretty neat, the abstraction layers also introduce some overhead. A solution could be to create a dedicated fs system, which supports only one (or maybe 2) filesystems, and eliminates the abstraction overhead. This will give some benefit, but the chance of getting this into the mainline is zero.<br />
<br />
== Articles and Presentations ==<br />
* "The Right Approach to Boot Time Reduction" - ([http://elinux.org/images/f/f7/RightApproachMinimalBootTimes.pdf Slides] | [http://www.youtube.com/watch?v=ULa4TPy7z0c YouTube Video])<br />
** Andrew Murray has presented at ELC Europe on October 28, 2010 (Free Electrons video [http://free-electrons.com/pub/video/2010/elce/elce2010-murray-boot-time.webm here])<br />
** This included a < 1 second QT cold Linux boot case study for an SH7724 with some additional information about 'function re-ordering' in user-space<br />
** Similar slides with < 1 second case study for OMAP3530EVM can be found [http://www.slideshare.net/andrewmurraympc/t-iswift-boot here]<br />
* "One Second Linux Boot Demonstration (new version)" ([http://www.youtube.com/watch?v=-l_DSZe8_F8 Youtube video by MontaVista])<br />
* "Tools and Techniques for Reducing Bootup Time" ([[Media:Tools-and-technique-for-reducing-bootup-time.ppt|PPT]] | [[Media:Tools-and-technique-for-reducing-bootup-time.odp|ODP]] | [[Media:Tools-and-technique-for-reducing-bootup-time.pdf|PDF]] | [http://free-electrons.com/pub/video/2008/elce/elce2008-bird-reducing-bootup-time.ogv video])<br />
** Tim Bird has presented at ELC Europe, on November 7, 2008, his latest collection of tips and tricks for reducing bootup time<br />
** [[Tims Fastboot Tools]] has online materials in support of this presentation<br />
* [http://www.mvista.com/download/author.php?a=37 Christopher Hallinan] has done a presentation at the MontaVista Vision conference 2008 on the topic of reducing boot time. Slides available [http://www.mvista.com/download/power/Reducing-boot-time-techniques-for-fast-booting.pdf here]<br />
* [http://lwn.net/Articles/192082/ Optimizing Linker Load Times]<br />
** (introducing various kinds of bootuptime reduction, prelinking, etc.)<br />
* [http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Benchmarking-boot-latency-on-x86/ Benchmarking boot latency on x86]<br />
** By Gilad Ben-Yossef, July 2008<br />
** A tutorial on using TSC register and the kernel PRINTK_TIMES feature to measure x86 system boot time, including BIOS, bootloader, kernel and time to first user program.<br />
* [http://tree.celinuxforum.org/CelfPubWiki/KoreaTechJamboree3?action=AttachFile&do=get&target=The_Fast_Booting_of_Embedded_Linux.pdf Fast Booting of Embedded Linux]<br />
** By HoJoon Park, Electrons and Telecommunications Research Institute (ETRI), Korea, Presented at the CELF [http://tree.celinuxforum.org/CelfPubWiki/KoreaTechJamboree3 3rd Korean Technical Jamboree], July 2008<br />
** Explains several different reduction techniques used for different phases of bootup time<br />
*Tim Bird's (Sony) survey of boot-up time reduction techniques:<br />
**[http://kernel.org/doc/ols/2004/ols2004v1-pages-79-88.pdf Methods to Improve Boot-up Time in Linux] - Paper prepared for 2004 Ottawa Linux Symposium<br />
**{{pdf|ReducingStartupTime v0.8.pdf|Reducing Startup Time in Embedded Linux Systems}} - December 2003 Presentation describing some existing boot-up time reduction techniques and strategies.<br />
* [http://free-electrons.com/articles/optimizations Embedded Linux optimizations]<br />
** By Free Electrons<br />
** Tutorial to reduce size, RAM, speed, power and cost of a Linux based embedded system]<br />
*Parallelizing Linux Boot on CE Devices<br />
** [http://tree.celinuxforum.org/CelfPubWiki/ELCEurope2007Presentations?action=AttachFile&do=view&target=par.pdf PDF of Presentation]<br />
**[http://free-electrons.com/pub/video/2007/elce/elce-2007-vitaly-wool-parallel-boot.ogg Video of Presentation]<br />
*[http://www.ibm.com/developerworks/linux/library/l-boot-faster/ Parallelize Applications for Faster Linux Boot]<br />
**Authored by M. Tim Jones for IBM Developer Works<br />
**This article shows you options to increase the speed with which Linux boots, including two options for parallelizing the initialization process. It also shows you how to visualize graphically the performance of the boot process.<br />
<br />
=== Case Studies ===<br />
* [http://www.makelinux.com/emb/fastboot/omap 300 milliseconds from boot loader to shell on ARM with NAND] <br />
* Samsung proof-of-acceptability study for digital still camera: see [[Media:LinuxBootupTimeReduction4DSC.ppt|Boot Up Time Reduction PPT]] and the [http://www.kernel.org/doc/ols/2006/ols2006v2-pages-239-248.pdf paper] describing this.<br />
* [https://docs.blackfin.uclinux.org/doku.php?id=fast_boot_example Boot Linux from Processor Reset into user space in less than 1 Second]<br />
** In this white paper, Robin Getz describes the techniques used to fast-boot a blackfin development board.<br />
* [http://e2e.ti.com/support/embedded/f/354/t/51158.aspx Booting Linux dm365 Network Camera in 3.2 seconds]<br />
* [http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/7616/30088.aspx Boot of kernel and shell in 0.5 sec (not including u-boot and decompression)]<br />
<br />
* [http://www.linuxfordevices.com/c/a/News/Linux-boots-in-297-seconds/ Warp2, Lineo Solutions, 2008. 2.97 sec boot, ARM11, 400MHz]<br />
<br />
== Additional Projects/Mailing Lists/Resources ==<br />
=== Replacements for SysV 'init' ===<br />
The traditional method of starting a Linux system is to use /sbin/init, which<br />
processes the file /etc/inittab. This is an init program which processes a series of actions for different <br />
run-levels and system events (key-combinations and power events).<br />
<br />
See [http://linux.die.net/man/8/init the init(8) man page] and the [http://linux.die.net/man/5/inittab the inittab(5) man page].<br />
<br />
==== busybox init ====<br />
An 'init' applet is often included in [[BusyBox]]<br />
<br />
There used to be (as of 2000) some slight differences in the supported features of the 'inittab' file<br />
between busybox init and full-blown init. However, I don't know (as of 2010) if that's still the case.<br />
(See http://spblinux.de/2.0/doc/init.html for some details)<br />
<br />
Denys Vlasenko, one of the maintainers of busybox has suggested a replacement for traditional init<br />
for that tool called runsv. See http://busybox.net/~vda/init_vs_runsv.html<br />
<br />
==== upstart ====<br />
upstart is the name of a newer Linux desktop systems that provides the program /sbin/init,<br />
but with different operational semantics.<br />
<br />
* Home page: http://upstart.ubuntu.com/<br />
* Wikipedia page: http://en.wikipedia.org/wiki/Upstart<br />
<br />
==== Android init ====<br />
Android 'init' is a custom program for booting the Android system.<br />
<br />
See [[Android_Booting#.27init.27|Android 'init']]<br />
<br />
==== systemd ====<br />
systemd is a new project (as of May 2010) for starting daemons and services on a Linux desktop system<br />
<br />
See http://0pointer.de/blog/projects/systemd.html<br />
<br />
=== Kexec ===<br />
*Kexec is a system which allows a system to be '''rebooted''' without going through BIOS. That is, a Linux kernel can directly boot into another Linux kernel, without going through firmware. See the white paper at: [http://developer.osdl.org/andyp/kexec/whitepaper/kexec.pdf kexec.pdf]<br />
**2004 Kernel Summit presentation: [http://www.xenotime.net/linux/fastboot/fastboot-ks-2004.pdf fastboot.pdf]<br />
**here's another Kexec white paper:[http://www-106.ibm.com/developerworks/linux/library/l-kexec.html?ca=dgr-lnxw04 Reboot Fast]<br />
<br />
=== Splash Screen projects ===<br />
* [http://splashy.alioth.debian.org/wiki/ Splashy] - Technology to put up a spalsh screen early in the boot sequence. This is user-space code.<br />
** This seems to be the most current splash screen technology, for major distributions. A framebuffer driver for the kernel is required.<br />
* [http://dev.gentoo.org/~spock/projects/gensplash/ Gentoo Splashscreen] - newer technology to put a splash screen early in the boot sequence<br />
** See the HOWTO at: [http://gentoo-wiki.com/HOWTO_fbsplash HOWTO FBSplash]<br />
* [http://butterfeet.org/?p=8 PSplash] - PSplash is a userspace graphical boot splash screen for mainly embedded Linux devices supporting a 16bpp or 32bpp framebuffer.<br />
* [http://www.bootsplash.org/ bootsplash.org] - put up a splash screen early in boot sequence<br />
** This project requires kernel patches<br />
** This project is now abandoned, and work is being done on Splashy.<br />
<br />
=== Others ===<br />
<br />
*[http://www.linuxdevices.com/news/NS5907201615.html FSMLabs Fastboot] - press release by FSMLabs about fast booting of their product. Is any of this published?<br />
<br />
*[http://tree.celinuxforum.org/CelfPubWiki/ snapshot boot] - a technology uses software resume to boot up the system quickly.<br />
<br />
==== Apparently obsolete or abandoned material ====<br />
* [[Image:alert.gif]] ''in progress'' - [[Boot-up Time Reduction Howto]] - this is a project to catalog existing boot-up time reduction techniques.<br />
** Was originally intended to be the authoritative source for bootup time reduction information.<br />
** No one maintains it any more (as of Aug, 2008)<br />
*[[Image:alert.gif]]''no content yet'' - [[Boot-up Time Delay Taxonomy]] - list of delays categorized by boot phase, type and magnitude<br />
** Was to be a survey of common bootup delays found in embedded devices.<br />
** Was never really written.<br />
<br />
???<br />
* [[Bootup Time Spec]]<br />
* [[Bootup Time Things To Investigate]]<br />
* [[Bootup Time Working Group]]<br />
* [[Bootup Time Task List]]<br />
* [[Bootup Time Howto Task List]]<br />
* [[Fast Booting Translation]]<br />
<br />
== Companies, individuals or projects working on fast booting ==<br />
* Intel - Arjan van de Ven - see http://lwn.net/Articles/299483/<br />
* Tripeaks - see http://www.linuxdevices.com/news/NS8282586707.html<br />
* Lineo Solutions - see http://www.linuxdevices.com/news/NS5185504436.html<br />
* Monta Vista - see http://www.linuxdevices.com/news/NS2560585344.html<br />
* fastboot git tree - see http://lwn.net/Articles/299591/<br />
* MPC Data SwiftBoot services - http://www.swiftboot.com/<br />
<br />
== Boot time check list ==<br />
<br />
From an [http://www.mail-archive.com/linux-embedded@vger.kernel.org/msg02139.html August 2009 discussion about boot time on ARM devices], several hints and advice regarding boot time optimization are available. While it may repeat a lot of above, below is a check list extracted from this discussion:<br />
<br />
* Is CPU's clock switched to maximum? If the kernel, bootloader or hardware is in charge of setting CPU power and speed scaling, then you should check that it boots with the CPU set at maximum speed instead of slowest. <br />
<br />
* Is your hardware (register) timing configuration of your SoC's memory interfaces (e.g. RAM and NOR/NAND timing) optimized? A lot of vendors ship their hardware with "well, it works, optimize later" settings. What you want is "as fast as possible, but sill stable and reliable" configuration. This might need some hardware knowledge and has to be customized to the individual memory devices used.<br />
<br />
* Does your boot loader uses I- and D-Cache? E.g. U-Boot doesn't enable D-Cache by default on ARM devices, as it needs customized MMU tables to do so.<br />
<br />
* Does kernel copy from permanent storage (e.g. NOR or NAND) to RAM use optimized functions? E.g. DMA, or on ARM at least load/store multiple commands (ldm/stm)?<br />
<br />
* If you use U-Boot's uImage, set "verify=no" in U-Boot to avoid checksum verification.<br />
<br />
* Optimize size of your kernel.<br />
** You might even try some of the embedded system kernel config options that, for example, eliminate all the printk strings, reduce data structures, or eliminate unneeded functionality.<br />
<br />
* How often is kernel (image) data copied? First by boot loader from storage to RAM, then by kernel's uncompressor to it's final destination? Once more? If you use compressed kernel and NOR flash, consider running the uncompressor XIP in NOR flash.<br />
<br />
* If you use compressed kernel, check compression algorithm. zlib is slow on decompression, and lzo is much faster. So if you implement lzo compression, you'll probably speed things up a little as well (check LKML for this). Having no compression at all may also be a good thing to try (see next topic).<br />
<br />
* Check to use uncompressed kernel (depends on your system configuration). Using an uncompressed kernel on a flash-based system may improve boot time. The reason is that compressed kernels are faster only when the throughput to the persistent storage is lower than the decompression throughput, and on typical embedded systems with DMA the throughput to memory outperforms the CPU-based decompression. Of course it depends on a lot of stuff like performance of flash controller, kernel storage filesystem performance, DMA controller performance, cache architecture etc. So it's individual per-system. Example: With using an uncomressed kernel (~2.8MB) uncompressing (running the uncompressor XIP in NOR flash) took ~0.5s longer than copying 2.8MB from flash to RAM.<br />
<br />
* Enable precalculated loops-per-jiffy<br />
<br />
* Enable kernel quiet option<br />
<br />
* If you use UBI: UBI is rather slow in attaching MTD devices. Everything is explained at MTD's [http://www.linux-mtd.infradead.org/doc/ubi.html#L_scalability UBI scalability] and [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_scalability UBI fs scalability] sections. There is not very much you can do to speed it up but implement UBI2. UBIFS would stay intact. There were discussions about this and it does not seem to be impossibly difficult to do UBI2 ([http://www.linux-mtd.infradead.org/faq/ubi.html#L_attach_faster few ideas]).<br />
** In a follow-up e-mail, Sascha Hauer wrote:<br />
<pre> What's interesting about this is that the kernel NAND driver is much slower<br />
than the one in U-Boot. Looking at it it turned out that the kernel<br />
driver uses interrupts to wait for the controller to get ready.<br />
Switching this to polling nearly doubles the NAND performance. UBI<br />
mounts much faster now and this cuts off another few seconds from the<br />
boot process :) <br />
</pre><br />
<br />
* Use static device nodes during boot, and later setup busybox mdev for hotplug.<br />
<br />
* If you have network enabled, there might be some very long timeouts in the network code paths, which appear to be used whether you specify a static address or not. See the definitions of CONF_PRE_OPEN and CON_POST_OPEN in ''net/ipv4/ipconfig.c''. Check [http://patchwork.kernel.org/patch/31678/ ipdelay configuration patch].<br />
<br />
* Parallelize boot process.<br />
<br />
* Disable the option "Set system time from RTC on startup and resume", you can use the command hwclock -s at the of the init instead of slowing down the kernel.<br />
<br />
[[Category:Boot Time]]<br />
[[Category:Bootloader]]</div>Dirkhttp://elinux.org/Boot_TimeBoot Time2011-05-04T18:23:57Z<p>Dirk: Add Alessio Igor Bogani's insmod improving patches</p>
<hr />
<div>== Introduction ==<br />
Boot Time includes topics such as measurement, analysis, human factors, initialization techniques, and reduction techniques.<br />
The time that a product takes to boot directly impacts the first perception an end user has of the product.<br />
Regardless of how attractive or well designed a consumer electronic device is, the time required to move the device from off to an interactive, usable state is critical to obtaining a positive end user experience. Turning on a device is Use Case #1.<br />
<br />
Booting up a device involves numerous steps and sequences of events. In order to use consistent terminology, the<br />
[[Bootup Time Working Group]] of the CE Linux Forum came up with a list of terms and their widely accepted definitions<br />
for this functionality area. See the following page for these terms:<br />
* [[Boot-up Time Definition Of Terms]]<br />
<br />
== Technology/Project Pages ==<br />
The following are individual pages with information about various technologies relevant to improving Boot Time for Linux. Some of these describe local patches available on this site. Others point to projects or patches maintained elsewhere.<br />
<br />
=== Measuring Boot-up Time ===<br />
*[[Printk Times]] - simple system for showing timing information for each printk.<br />
*[[Kernel Function Trace]] - system for reporting function timings in the kernel.<br />
*[[Linux Trace Toolkit]] - system for reporting timing data for certain kernel and process events.<br />
*[http://oprofile.sourceforge.net/news/ Oprofile] - system-wide profiler for Linux.<br />
*[[Bootchart]] - a tool for performance analysis and visualization of the Linux boot process. Resource utilization and process information are collected during the user-space portion of the boot process and are later rendered in a PNG, SVG or EPS encoded chart.<br />
*[http://people.redhat.com/berrange/systemtap/bootprobe/ Bootprobe] - a set of [[System Tap]] scripts for analyzing system bootup.<br />
* and, let us not forget: "cat /proc/uptime"<br />
* [[Tims Fastboot Tools#grabserial | grabserial]] - a nice utility from Tim Bird to log and timestamp console output<br />
* [[Tims Fastboot Tools#Tim's quick and dirty process trace|process trace]] - a simple patch from Tim Bird to log exec, fork and exit system calls.<br />
* [http://pengutronix.de/software/ptx_ts/index_en.html ptx_ts] - Pengutronix' TimeStamper: A small filter prepending timestamps to STDOUT; a bit similar to grabserial but not limited to serial ports<br />
* [[Initcall Debug]] - a kernel command line option to show time taken for initcalls.<br />
* See also: [[Kernel Instrumentation]] which lists some known kernel instrumentation tools. These are of interest for measuring kernel startup time.<br />
<br />
=== Technologies and Techniques for Reducing Boot Time ===<br />
==== Bootloader speedups ====<br />
*[[Kernel XIP]] - Allow kernel to be executed in-place in ROM or FLASH.<br />
*[[DMA Copy Of Kernel On Startup]] - Copy kernel from Flash to RAM using DMA<br />
*[[Uncompressed kernel]] - An uncompressed kernel might boot faster<br />
*[[Fast Kernel Decompression]]<br />
<br />
==== Kernel speedups ====<br />
*[[Disable Console]] - Avoid overhead of console output during system startup.<br />
*Disable bug and printk - Avoid the overhead of bug and printk. Disadvantage is that you loose a lot of info.<br />
*[[RTC No Sync]] - Avoid delay to synchronize system time with RTC clock edge on startup.<br />
*[[Short IDE Delays]] - Reduce duration of IDE startup delays (this is effective but possibly dangerous).<br />
*[[Hardcode kernel module info]] - Reduce the overhead of loading a module, by hardcoding some information used for loading the relocation information<br />
*[[IDE No Probe]] - Force kernel to observe the ide<x>=noprobe option.<br />
*[[Preset LPJ]] - Allow the use of a preset loops_per_jiffy value.<br />
*[[Asynchronous function calls]] - Allow probing or other functions to proceed in parallel, to overlap time-consuming boot-up activities.<br />
**[[Threaded Device Probing]] - Allow drivers to probe devices in parallel. (not mainlined, now deprecated?)<br />
*[[Reordering of driver initialization]] - Allow driver bus probing to start as soon as possible.<br />
*[[Deferred Initcalls]] - defer non-essential module initialization routines to after primary boot<br />
*NAND ECC improvement - The pre 2.6.28 nand_ecc.c has room for improvement. You can find an improved version in the mtd git at http://git.infradead.org/mtd-2.6.git?a=blob_plain;f=drivers/mtd/nand/nand_ecc.c;hb=HEAD. Documentation for this is in http://git.infradead.org/mtd-2.6.git?a=blob_plain;f=Documentation/mtd/nand_ecc.txt;hb=HEAD. This is only interesting if your system uses software ECC correction.<br />
*Check what kernel memory allocator you use. Slob or slub might be better than slab (which is the default in older kernels) <br />
*If your system does not need it, you can remove SYSFS and even PROCFS from the kernel. In one test removing sysfs saved 20 ms.<br />
*Carefully investigate all kernel configuration options on whether they are applicable or not. Even if you select an option that is not used in the end, it contributes to the kernel size and therefore to the kernel load time (assuming you are not doing kernel XIP). Often this will require some trial and measure! E.g. selecting CONFIG_CC_OPTIMIZE_FOR_SIZE (found under general setup) gave in one case a boot improvement of 20 ms. Not dramamtic, but when reducing boot time every penny counts!<br />
*Moving to a different compiler version might lead to shorter and/or faster code. Most often newer compilers produce better code. You might also want to play with compiler options to see what works best.<br />
* If you use initramfs in your kernel and a compressed kernel it is better to have an uncompressed initramfs image. This is to avoid having to uncompress data twice. A patch for this has been submitted to LKML. See http://lkml.org/lkml/2008/11/22/112 <br />
<br />
===== File System issues =====<br />
Different file systems have different initialization (mounting) times, for the same data sets. This<br />
is a function of whether meta-data must be read from storage into RAM or not, and what algorithms are<br />
used during the mount procedure.<br />
<br />
* [[Filesystem Information]] - has information about boot-up times of various file systems<br />
* [[File Systems]] - has information on various file systems that are interesting for embedded systems. Also includes some improvement suggestions.<br />
* [[Avoid Initramfs]] - explains on why intramfs should be avoided if you want to minimize boot time<br />
* Split partitions. If mounting a file system takes long, you can consider splitting that filesystem in two parts, one with the info that is needed during or immediately after boot, and one which can be mounted later on.<br />
* [[Ramdisks demasked]] - explains why using a ram disk generally results in a longer boot time, not a shorter one.<br />
<br />
==== User-space and application speedups ====<br />
* [[Optimize RC Scripts]] - Reduce overhead of running RC scripts<br />
* [[Parallel RC Scripts]] - Run RC scripts in parallel instead of sequentially<br />
* [[Application XIP]] - Allow programs and libraries to be executed in-place in ROM or FLASH<br />
* [[Pre Linking]] - Avoid cost of runtime linking on first program load<br />
* Statically link applications. This avoids the costs of runtime linking. Useful if you have only a few applications. In that case it could also reduce the size of your image as no dynamic libraries are needed<br />
* GNU_HASH: ~ 50% speed improvement in dynamic linking<br />
** See http://sourceware.org/ml/binutils/2006-06/msg00418.html<br />
* [[Application Init Optimizations]] - Improvements in program load and init time via: <br />
** use of mmap vs. read<br />
** control over page mapping characteristics.<br />
* [[Include modules in kernel image]] - Avoid extra overhead of module loading by adding the modules to the kernel image<br />
* Speed up module loading - Use Alessio Igor Bogani's kernel patches to improve module loading time by "Speed up the symbols' resolution process" ([http://marc.info/?l=linux-kernel&m=130296044420203&w=2| Patch 1], [http://marc.info/?l=linux-embedded&m=130296044420197&w=2| Patch 2], [http://marc.info/?l=linux-embedded&m=130296044420200&w=2| Patch 3], [http://marc.info/?l=linux-kernel&m=130296062420328&w=2| Patch 4], [http://marc.info/?l=linux-embedded&m=130445535913197&w=2| Patch 5]).<br />
* Avoid udev, it takes quite some time to populate the /dev directory. In an embedded system it is often known what devices are present and in any case you know what drivers are available, so you know what device entries might be needed in /dev. These should be created statically, not dynamically. mknod is your friend, udev is your enemy.<br />
* If you still like udev and also like fast boot-up's, you might go this way: start your system with udev enabled and make kind of a backup of the created device nodes. Now, modify your init script like this: instead running udev, copy the device nodes that you just made a backup of into the device tree. Now, install the hotplug-daemon like you always do. That trick avoids the device node creation at startup but stills lets your system create device nodes later on. <br />
* If your device has a network connection, preferably use static IP addresses. Getting an address from a DHCP server takes additional time and has extra overhead associated with it.<br />
* Moving to a different compiler version might lead to shorter and/or faster code. Most often newer compilers produce better code. You might also want to play with compiler options to see what works best.<br />
* If possible move from glibc to uClibc. This leads to smaller executables and hence to faster load times.<br />
* library optimiser tool: http://libraryopt.sourceforge.net/ <br/> This will allow you to create an optimised library. As unneeded functions are removed this should lead to a performance gain. Normally there will be library pages which contain unused code (adjacent to code that is used). After optimizing the library this does not occur any more, so less pages are needed and hence less page loads, so some time can be saved.<br />
* Function reordering: http://www.celinux.org/elc08_presentations/DDLink%20FunctionReorder%2008%2004.pdf <br/> This is a technique to rearrange the functions within an executable so they appear in the order they are needed. This improves the load time of the application as all initialization code is grouped into a set of pages, instead of being scattered over a number of pages.<br />
<br />
==== Suspend related improvements ====<br />
Another approach to improve boot time is to use a suspend related mechanism. Two approaches are known.<br />
* Using the standard hibernate/resume approach. This is what has been demonstrated by Chan Ju, Park, from Samsung. See sheet 23 and onwards from this [[Media:LinuxBootupTimeReduction4DSC.ppt|PPT]] and section 2.7 of this [http://www.kernel.org/doc/ols/2006/ols2006v2-pages-239-248.pdf paper]. <br /> Issue with this approach is that flash write is much slower than flash read, so the actual creation of the hibernate image might take quite a while.<br />
* Implementing snapshot boot. This is done by Hiroki Kaminaga from Sony and is described at [[Suspend To Disk For ARM|snapshot boot for ARM]] and http://elinux.org/upload/3/37/Snapshot-boot-final.pdf<br />This is similar to hibernate and resume, but the hibernate file is retained and used upon every boot. Disadvantage is that no writable partitions should be mounted at the time of making the snapshot. Otherwise inconsistencies will occur if a partition is modified, while applications in the hibernate file might have information in the snapshot related to the unmodified partition.<br />
<br />
==== Miscellaneous topics ====<br />
<br />
[[About Compression]] discusses the effects of compression on boot time. This can affect both the kernel boot time as well as user-space startup.<br />
<br />
==== Uninvestigated speedups ====<br />
<br />
This section is a holding pen for ideas for improvement that are not implemented yet but that could result in a boot time gain. Please leave a note here if you are working on one of these items to avoid duplicate work.<br />
<br />
* '''Prepopulated buffer cache''' - As initramfs performs an additional copy of the data the idea is to have a prepopulated buffer cache. A simplistic scenario would allow dumping the buffer cache when the booting is completed and the user applications have initialised. This data then could be used in a subsequent boot to initialize the buffer cache (of course without copying). A possible approach would be to have those data to reside into the kernel image and use them directly. Alternately they could be loaded separately. <br /> Unfortunately my knowledge of the internals in this section is not yet good enough to do a trial implementation.<br /> Caveats:<br />
** is it possible to have the buffer cache split into two different parts, one which is statically allocated, one which is dynamically allocated?<br />
** the pages in the prepopulated buffer cache probably cannot be discarded, so they should be pinned<br />
** apart from the buffer cache data itself also some other variables might need restoring<br />
** a similar approach could also be used for the cached file data.<br />
*'''Dedicated fs''' - currently a lot of abstraction is done in fs to make a nice abstraction allowing easy addition of new filesystems and creating a unified view of those filesystem. While this is pretty neat, the abstraction layers also introduce some overhead. A solution could be to create a dedicated fs system, which supports only one (or maybe 2) filesystems, and eliminates the abstraction overhead. This will give some benefit, but the chance of getting this into the mainline is zero.<br />
<br />
== Articles and Presentations ==<br />
* "The Right Approach to Boot Time Reduction" - ([http://elinux.org/images/f/f7/RightApproachMinimalBootTimes.pdf Slides] | [http://www.youtube.com/watch?v=ULa4TPy7z0c YouTube Video])<br />
** Andrew Murray has presented at ELC Europe on October 28, 2010 (Free Electrons video [http://free-electrons.com/pub/video/2010/elce/elce2010-murray-boot-time.webm here])<br />
** This included a < 1 second QT cold Linux boot case study for an SH7724 with some additional information about 'function re-ordering' in user-space<br />
** Similar slides with < 1 second case study for OMAP3530EVM can be found [http://www.slideshare.net/andrewmurraympc/t-iswift-boot here]<br />
* "One Second Linux Boot Demonstration (new version)" ([http://www.youtube.com/watch?v=-l_DSZe8_F8 Youtube video by MontaVista])<br />
* "Tools and Techniques for Reducing Bootup Time" ([[Media:Tools-and-technique-for-reducing-bootup-time.ppt|PPT]] | [[Media:Tools-and-technique-for-reducing-bootup-time.odp|ODP]] | [[Media:Tools-and-technique-for-reducing-bootup-time.pdf|PDF]] | [http://free-electrons.com/pub/video/2008/elce/elce2008-bird-reducing-bootup-time.ogv video])<br />
** Tim Bird has presented at ELC Europe, on November 7, 2008, his latest collection of tips and tricks for reducing bootup time<br />
** [[Tims Fastboot Tools]] has online materials in support of this presentation<br />
* [http://www.mvista.com/download/author.php?a=37 Christopher Hallinan] has done a presentation at the MontaVista Vision conference 2008 on the topic of reducing boot time. Slides available [http://www.mvista.com/download/power/Reducing-boot-time-techniques-for-fast-booting.pdf here]<br />
* [http://lwn.net/Articles/192082/ Optimizing Linker Load Times]<br />
** (introducing various kinds of bootuptime reduction, prelinking, etc.)<br />
* [http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Benchmarking-boot-latency-on-x86/ Benchmarking boot latency on x86]<br />
** By Gilad Ben-Yossef, July 2008<br />
** A tutorial on using TSC register and the kernel PRINTK_TIMES feature to measure x86 system boot time, including BIOS, bootloader, kernel and time to first user program.<br />
* [http://tree.celinuxforum.org/CelfPubWiki/KoreaTechJamboree3?action=AttachFile&do=get&target=The_Fast_Booting_of_Embedded_Linux.pdf Fast Booting of Embedded Linux]<br />
** By HoJoon Park, Electrons and Telecommunications Research Institute (ETRI), Korea, Presented at the CELF [http://tree.celinuxforum.org/CelfPubWiki/KoreaTechJamboree3 3rd Korean Technical Jamboree], July 2008<br />
** Explains several different reduction techniques used for different phases of bootup time<br />
*Tim Bird's (Sony) survey of boot-up time reduction techniques:<br />
**[http://kernel.org/doc/ols/2004/ols2004v1-pages-79-88.pdf Methods to Improve Boot-up Time in Linux] - Paper prepared for 2004 Ottawa Linux Symposium<br />
**{{pdf|ReducingStartupTime v0.8.pdf|Reducing Startup Time in Embedded Linux Systems}} - December 2003 Presentation describing some existing boot-up time reduction techniques and strategies.<br />
* [http://free-electrons.com/articles/optimizations Embedded Linux optimizations]<br />
** By Free Electrons<br />
** Tutorial to reduce size, RAM, speed, power and cost of a Linux based embedded system]<br />
*Parallelizing Linux Boot on CE Devices<br />
** [http://tree.celinuxforum.org/CelfPubWiki/ELCEurope2007Presentations?action=AttachFile&do=view&target=par.pdf PDF of Presentation]<br />
**[http://free-electrons.com/pub/video/2007/elce/elce-2007-vitaly-wool-parallel-boot.ogg Video of Presentation]<br />
*[http://www.ibm.com/developerworks/linux/library/l-boot-faster/ Parallelize Applications for Faster Linux Boot]<br />
**Authored by M. Tim Jones for IBM Developer Works<br />
**This article shows you options to increase the speed with which Linux boots, including two options for parallelizing the initialization process. It also shows you how to visualize graphically the performance of the boot process.<br />
<br />
=== Case Studies ===<br />
* [http://www.makelinux.com/emb/fastboot/omap 300 milliseconds from boot loader to shell on ARM with NAND] <br />
* Samsung proof-of-acceptability study for digital still camera: see [[Media:LinuxBootupTimeReduction4DSC.ppt|Boot Up Time Reduction PPT]] and the [http://www.kernel.org/doc/ols/2006/ols2006v2-pages-239-248.pdf paper] describing this.<br />
* [https://docs.blackfin.uclinux.org/doku.php?id=fast_boot_example Boot Linux from Processor Reset into user space in less than 1 Second]<br />
** In this white paper, Robin Getz describes the techniques used to fast-boot a blackfin development board.<br />
* [http://e2e.ti.com/support/embedded/f/354/t/51158.aspx Booting Linux dm365 Network Camera in 3.2 seconds]<br />
* [http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/7616/30088.aspx Boot of kernel and shell in 0.5 sec (not including u-boot and decompression)]<br />
<br />
* [http://www.linuxfordevices.com/c/a/News/Linux-boots-in-297-seconds/ Warp2, Lineo Solutions, 2008. 2.97 sec boot, ARM11, 400MHz]<br />
<br />
== Additional Projects/Mailing Lists/Resources ==<br />
=== Replacements for SysV 'init' ===<br />
The traditional method of starting a Linux system is to use /sbin/init, which<br />
processes the file /etc/inittab. This is an init program which processes a series of actions for different <br />
run-levels and system events (key-combinations and power events).<br />
<br />
See [http://linux.die.net/man/8/init the init(8) man page] and the [http://linux.die.net/man/5/inittab the inittab(5) man page].<br />
<br />
==== busybox init ====<br />
An 'init' applet is often included in [[BusyBox]]<br />
<br />
There used to be (as of 2000) some slight differences in the supported features of the 'inittab' file<br />
between busybox init and full-blown init. However, I don't know (as of 2010) if that's still the case.<br />
(See http://spblinux.de/2.0/doc/init.html for some details)<br />
<br />
Denys Vlasenko, one of the maintainers of busybox has suggested a replacement for traditional init<br />
for that tool called runsv. See http://busybox.net/~vda/init_vs_runsv.html<br />
<br />
==== upstart ====<br />
upstart is the name of a newer Linux desktop systems that provides the program /sbin/init,<br />
but with different operational semantics.<br />
<br />
* Home page: http://upstart.ubuntu.com/<br />
* Wikipedia page: http://en.wikipedia.org/wiki/Upstart<br />
<br />
==== Android init ====<br />
Android 'init' is a custom program for booting the Android system.<br />
<br />
See [[Android_Booting#.27init.27|Android 'init']]<br />
<br />
==== systemd ====<br />
systemd is a new project (as of May 2010) for starting daemons and services on a Linux desktop system<br />
<br />
See http://0pointer.de/blog/projects/systemd.html<br />
<br />
=== Kexec ===<br />
*Kexec is a system which allows a system to be '''rebooted''' without going through BIOS. That is, a Linux kernel can directly boot into another Linux kernel, without going through firmware. See the white paper at: [http://developer.osdl.org/andyp/kexec/whitepaper/kexec.pdf kexec.pdf]<br />
**2004 Kernel Summit presentation: [http://www.xenotime.net/linux/fastboot/fastboot-ks-2004.pdf fastboot.pdf]<br />
**here's another Kexec white paper:[http://www-106.ibm.com/developerworks/linux/library/l-kexec.html?ca=dgr-lnxw04 Reboot Fast]<br />
<br />
=== Splash Screen projects ===<br />
* [http://splashy.alioth.debian.org/wiki/ Splashy] - Technology to put up a spalsh screen early in the boot sequence. This is user-space code.<br />
** This seems to be the most current splash screen technology, for major distributions. A framebuffer driver for the kernel is required.<br />
* [http://dev.gentoo.org/~spock/projects/gensplash/ Gentoo Splashscreen] - newer technology to put a splash screen early in the boot sequence<br />
** See the HOWTO at: [http://gentoo-wiki.com/HOWTO_fbsplash HOWTO FBSplash]<br />
* [http://butterfeet.org/?p=8 PSplash] - PSplash is a userspace graphical boot splash screen for mainly embedded Linux devices supporting a 16bpp or 32bpp framebuffer.<br />
* [http://www.bootsplash.org/ bootsplash.org] - put up a splash screen early in boot sequence<br />
** This project requires kernel patches<br />
** This project is now abandoned, and work is being done on Splashy.<br />
<br />
=== Others ===<br />
<br />
*[http://www.linuxdevices.com/news/NS5907201615.html FSMLabs Fastboot] - press release by FSMLabs about fast booting of their product. Is any of this published?<br />
<br />
*[http://tree.celinuxforum.org/CelfPubWiki/ snapshot boot] - a technology uses software resume to boot up the system quickly.<br />
<br />
==== Apparently obsolete or abandoned material ====<br />
* [[Image:alert.gif]] ''in progress'' - [[Boot-up Time Reduction Howto]] - this is a project to catalog existing boot-up time reduction techniques.<br />
** Was originally intended to be the authoritative source for bootup time reduction information.<br />
** No one maintains it any more (as of Aug, 2008)<br />
*[[Image:alert.gif]]''no content yet'' - [[Boot-up Time Delay Taxonomy]] - list of delays categorized by boot phase, type and magnitude<br />
** Was to be a survey of common bootup delays found in embedded devices.<br />
** Was never really written.<br />
<br />
???<br />
* [[Bootup Time Spec]]<br />
* [[Bootup Time Things To Investigate]]<br />
* [[Bootup Time Working Group]]<br />
* [[Bootup Time Task List]]<br />
* [[Bootup Time Howto Task List]]<br />
* [[Fast Booting Translation]]<br />
<br />
== Companies, individuals or projects working on fast booting ==<br />
* Intel - Arjan van de Ven - see http://lwn.net/Articles/299483/<br />
* Tripeaks - see http://www.linuxdevices.com/news/NS8282586707.html<br />
* Lineo Solutions - see http://www.linuxdevices.com/news/NS5185504436.html<br />
* Monta Vista - see http://www.linuxdevices.com/news/NS2560585344.html<br />
* fastboot git tree - see http://lwn.net/Articles/299591/<br />
* MPC Data SwiftBoot services - http://www.swiftboot.com/<br />
<br />
== Boot time check list ==<br />
<br />
From an [http://www.mail-archive.com/linux-embedded@vger.kernel.org/msg02139.html August 2009 discussion about boot time on ARM devices], several hints and advice regarding boot time optimization are available. While it may repeat a lot of above, below is a check list extracted from this discussion:<br />
<br />
* Is CPU's clock switched to maximum? If the kernel, bootloader or hardware is in charge of setting CPU power and speed scaling, then you should check that it boots with the CPU set at maximum speed instead of slowest. <br />
<br />
* Is your hardware (register) timing configuration of your SoC's memory interfaces (e.g. RAM and NOR/NAND timing) optimized? A lot of vendors ship their hardware with "well, it works, optimize later" settings. What you want is "as fast as possible, but sill stable and reliable" configuration. This might need some hardware knowledge and has to be customized to the individual memory devices used.<br />
<br />
* Does your boot loader uses I- and D-Cache? E.g. U-Boot doesn't enable D-Cache by default on ARM devices, as it needs customized MMU tables to do so.<br />
<br />
* Does kernel copy from permanent storage (e.g. NOR or NAND) to RAM use optimized functions? E.g. DMA, or on ARM at least load/store multiple commands (ldm/stm)?<br />
<br />
* If you use U-Boot's uImage, set "verify=no" in U-Boot to avoid checksum verification.<br />
<br />
* Optimize size of your kernel.<br />
** You might even try some of the embedded system kernel config options that, for example, eliminate all the printk strings, reduce data structures, or eliminate unneeded functionality.<br />
<br />
* How often is kernel (image) data copied? First by boot loader from storage to RAM, then by kernel's uncompressor to it's final destination? Once more? If you use compressed kernel and NOR flash, consider running the uncompressor XIP in NOR flash.<br />
<br />
* If you use compressed kernel, check compression algorithm. zlib is slow on decompression, and lzo is much faster. So if you implement lzo compression, you'll probably speed things up a little as well (check LKML for this). Having no compression at all may also be a good thing to try (see next topic).<br />
<br />
* Check to use uncompressed kernel (depends on your system configuration). Using an uncompressed kernel on a flash-based system may improve boot time. The reason is that compressed kernels are faster only when the throughput to the persistent storage is lower than the decompression throughput, and on typical embedded systems with DMA the throughput to memory outperforms the CPU-based decompression. Of course it depends on a lot of stuff like performance of flash controller, kernel storage filesystem performance, DMA controller performance, cache architecture etc. So it's individual per-system. Example: With using an uncomressed kernel (~2.8MB) uncompressing (running the uncompressor XIP in NOR flash) took ~0.5s longer than copying 2.8MB from flash to RAM.<br />
<br />
* Enable precalculated loops-per-jiffy<br />
<br />
* Enable kernel quiet option<br />
<br />
* If you use UBI: UBI is rather slow in attaching MTD devices. Everything is explained at MTD's [http://www.linux-mtd.infradead.org/doc/ubi.html#L_scalability UBI scalability] and [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_scalability UBI fs scalability] sections. There is not very much you can do to speed it up but implement UBI2. UBIFS would stay intact. There were discussions about this and it does not seem to be impossibly difficult to do UBI2 ([http://www.linux-mtd.infradead.org/faq/ubi.html#L_attach_faster few ideas]).<br />
** In a follow-up e-mail, Sascha Hauer wrote:<br />
<pre> What's interesting about this is that the kernel NAND driver is much slower<br />
than the one in U-Boot. Looking at it it turned out that the kernel<br />
driver uses interrupts to wait for the controller to get ready.<br />
Switching this to polling nearly doubles the NAND performance. UBI<br />
mounts much faster now and this cuts off another few seconds from the<br />
boot process :) <br />
</pre><br />
<br />
* Use static device nodes during boot, and later setup busybox mdev for hotplug.<br />
<br />
* If you have network enabled, there might be some very long timeouts in the network code paths, which appear to be used whether you specify a static address or not. See the definitions of CONF_PRE_OPEN and CON_POST_OPEN in ''net/ipv4/ipconfig.c''. Check [http://patchwork.kernel.org/patch/31678/ ipdelay configuration patch].<br />
<br />
* Parallelize boot process.<br />
<br />
* Disable the option "Set system time from RTC on startup and resume", you can use the command hwclock -s at the of the init instead of slowing down the kernel.<br />
<br />
[[Category:Boot Time]]<br />
[[Category:Bootloader]]</div>Dirkhttp://elinux.org/BeagleBoardOpenOCDBeagleBoardOpenOCD2010-04-02T09:43:30Z<p>Dirk: Fix formatting errors</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page is about how to use open source [http://openocd.berlios.de/web/ OpenOCD] [http://en.wikipedia.org/wiki/JTAG JTAG] software with [[BeagleBoard|BeagleBoard]]. With this, it will be possible to have OMAP3 JTAG debug using cheap [[BeagleBoardJTAG|JTAG hardware]], e.g. [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]].<br />
<br />
'''As of September 2009, OpenOCD has basic support for OMAP3 and [[BeagleBoardOpenOCD#Cortex_A8_support|ARM Cortex A8]] on Beagle Board. Cortex A8 support is in early alpha stage, a lot is still missing. But e.g. processor halt, resume, step, breakpoints and ARM disassembly of non-Cache and non-MMU (e.g. U-Boot) applications seem to work.<br />
<br />
Status:<br />
<br />
* You need at least OpenOCD revision '''2770''' ([[BeagleBoardOpenOCD#Build_OpenOCD|using git]]). With this revision you will have basic access to OMAP3 and Cortex A8 can be basically controlled. This does mean, that OpenOCD is able to configure scan chain correctly to [[OMAP3530_ICEPICK#ICEPICK_infos|access ARM TAP]] ("JTAG controller"), explore CoreSight AccessPoints and halt, resume, step, breakpoints and ARM disassembly on Cortex A8.<br />
* Recent status as of '''September 2009''':<br />
** OpenOCD >= 2770 can and halt, resume, step, breakpoints and ARM disassembly Cortex A8 (ARM) processor on Beagle.<br />
** This works for non-MMU and non-Cache applications (e.g U-Boot).<br />
** [https://lists.berlios.de/pipermail/openocd-development/2009-August/010184.html Linux debugging doesn't work yet].<br />
<br />
<br />
=Hardware=<br />
<br />
To be able to use OpenOCD with OMAP3 based BeagleBoard, make sure that your JTAG Dongle supports:<br />
<br />
* 1.8V devices. Many JTAG dongles are 3.3V only! '''Verify that your dongle supports 1.8V!''' Else the dongle will overpowering the input to OMAP3 and may cause damage.<br />
* Your JTAG dongle is able to switch [[BeagleBoardJTAG#Beagle_JTAG_connection|EMU0 & EMU1 pins high]].<br />
<br />
Flyswatter dongle supports both requirements. If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way. In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).<br />
<br />
=Build OpenOCD=<br />
<br />
[http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD OpenOCD build instructions] describe how to build [http://openocd.berlios.de/web/ OpenOCD]. For questions you can use [https://lists.berlios.de/mailman/listinfo/openocd-development OpenOCD Mailing list].<br />
<br />
Get OpenOCD code via git:<br />
<br />
> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd openocd<br />
<br />
For Flyswatter you additionally need [http://www.ftdichip.com/Drivers/D2XX.htm libftd2xx] or [http://www.intra2net.com/de/produkte/opensource/ftdi/ libFTDI]. While libFTDI is available in source, libftd2xx is supposed to be 50% [http://www.beagleboard.org/irclogs/index.php?date=2008-10-16#T16:06:22 faster] than libFTDI. The libtfd2xx binaries are available booth as shared library or linkable archive.<br />
<br />
If you downloaded OpenOCD git and have libftd2xx or libFTDI, build OpenOCD (assuming you extracted/built FTDI library already):<br />
<br />
> cd openocd<br />
> ./bootstrap<br />
> ./configure --enable-ft2232_ftd2xx --with-ftd2xx-linux-tardir=<path_to>/libftd2xx0.4.16 --prefix=/home/user/bin/openOCD<br />
''or'' (depending which FTDI library you use, see above)<br />
> ./configure --enable-ft2232_libftdi --prefix=/home/user/bin/openOCD<br />
> make<br />
> make install<br />
<br />
When compiling the doc directory You get an error:<br />
openocd.texi:12: @include `version.texi': No such file or directory.<br />
It is possible to avoid by making version.texi. <br />
<br />
> cat doc/version.texi<br />
@set UPDATED 20 January 2009<br />
@set UPDATED-MONTH January 2009<br />
@set EDITION 0.1.0<br />
@set VERSION 0.1.0<br />
<br />
'''Note''': By default (make & make install) only .info documentation is installed. You can get PDF or HTML documentation by<br />
<br />
make pdf<br />
<br />
or<br />
<br />
make html<br />
<br />
Resulting documentation can be found in openocd/doc, then.<br />
<br />
'''Note''': If you like to save some disk space and don't plan to debug OpenOCD binary itself, you can strip this (remove unneeded debug symbols):<br />
<br />
> cd <openocd_install_dir>/bin<br />
> strip openocd<br />
<br />
(e.g. with OpenOCD 1.0 this reduced binary size from ~3MB to ~700kB)<br />
<br />
'''Note''': If you don't have libftdi in standard path, you might like to extend library search path:<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path_to>/lib<br />
<br />
if you e.g. get<br />
<br />
> ./openocd<br />
./openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory<br />
<br />
=Starting OpenOCD=<br />
<br />
OpenOCD runtime is controlled by several [http://openocd.berlios.de/doc/html/index.html#toc_Config-File-Guidelines configuration files]. OpenOCD comes with basic configuration files for BeagleBoard (''board/ti_beagleboard.cfg'') and OMAP3 (''target/omap3530.cfg'').<br />
<br />
Assuming that you use Flyswatter and it is switched on (attached to USB), you can now start OpenOCD with:<br />
<br />
openocd -s <path_to_config_files> // e.g. <path_of_openocd_install_dir>/lib/openocd<br />
-f <path_to_jtag_interface><br />
-f <path_to_beagle_config><br />
<br />
This should result in<br />
<br />
> '''openocd -s lib/openocd/ -f interface/flyswatter.cfg -f board/ti_beagleboard.cfg'''<br />
Open On-Chip Debugger 0.5.0-dev-00141-g33e5dd1 (2010-04-02-11:14)<br />
Licensed under GNU GPL v2<br />
For bug reports, read<br />
http://openocd.berlios.de/doc/doxygen/bugs.html<br />
RCLK - adaptive<br />
Warn : omap3530.dsp: huge IR length 38<br />
RCLK - adaptive<br />
trst_only separate trst_push_pull<br />
Info : RCLK (adaptive clock speed) not supported - fallback to 1000 kHz<br />
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
Info : JTAG tap: omap3530.dap enabled<br />
Info : omap3530.cpu: hardware has 6 breakpoints, 2 watchpoints<br />
<br />
This shows that your (Flyswatter) JTAG dongle basically works and that you are able to see OMAP3 JRC. OpenOCD now runs as daemon.<br />
<br />
=Controlling OpenOCD=<br />
<br />
Once OpenOCD runs as [http://openocd.berlios.de/doc/html/Running.html#Running daemon] like above, you can connect using ''telnet'' or ''GDB''<br />
<br />
==telnet==<br />
<br />
Connect to OpenOCD daemon. Assuming you do it on your local machine, open a second terminal window and do (assuming port 4444 as configured in above openocd.cfg):<br />
<br />
> '''telnet localhost 4444'''<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> <br />
<br />
This should give you<br />
<br />
Info: accepting 'telnet' connection from 0<br />
<br />
in window where OpenOCD daemon is started.<br />
<br />
At OpenOCDs telnet prompt you can now issue OpenOCD commands. E.g. ''help'' should result in<br />
<br />
> '''help''' <br />
bp list or set breakpoint [<address> <length> [hw]]<br />
cpu <name> - prints out target options and a comment <br />
on CPU which matches name <br />
debug_level adjust debug level <0-3> <br />
drscan execute DR scan <device> <num_bits> <value> <br />
<num_bits1> <value2> ... <br />
dump_image dump_image <file> <address> <size> <br />
exit exit telnet session <br />
fast fast <enable/disable> - place at beginning of <br />
config files. Sets defaults to fast and dangerous.<br />
<br />
fast_load loads active fast load image to current target - <br />
mainly for profiling purposes <br />
fast_load_image same args as load_image, image stored in memory - <br />
mainly for profiling purposes <br />
find <file> - print full path to file according to <br />
OpenOCD search rules <br />
flush_count returns number of times the JTAG queue has been <br />
flushed <br />
ft2232_device_desc the USB device description of the FTDI FT2232 <br />
device <br />
ft2232_latency set the FT2232 latency timer to a new value <br />
ft2232_layout the layout of the FT2232 GPIO signals used to <br />
control output-enables and reset signals <br />
ft2232_serial the serial number of the FTDI FT2232 device <br />
ft2232_vid_pid the vendor ID and product ID of the FTDI FT2232 <br />
device <br />
gdb_breakpoint_override hard/soft/disable - force breakpoint type for gdb <br />
'break' commands. <br />
gdb_detach resume/reset/halt/nothing - specify behavior when <br />
GDB detaches from the target <br />
gdb_flash_program enable or disable flash program <br />
gdb_memory_map enable or disable memory map <br />
gdb_port daemon configuration command gdb_port <br />
gdb_report_data_abort enable or disable reporting data aborts <br />
halt halt target <br />
help Tcl implementation of help command <br />
init initializes target and servers - nop on subsequent <br />
invocations <br />
interface try to configure interface <br />
interface_list list all built-in interfaces <br />
irscan execute IR scan <device> <instr> [dev2] [instr2] <br />
... <br />
jtag perform jtag tap actions <br />
jtag_device (DEPRECATED) jtag_device <ir_length> <ir_expected> <br />
<ir_mask> <br />
jtag_khz set maximum jtag speed (if supported); parameter <br />
is maximum khz, or 0 for adaptive clocking (RTCK). <br />
<br />
jtag_nsrst_delay jtag_nsrst_delay <ms> - delay after deasserting <br />
srst in ms <br />
jtag_ntrst_delay jtag_ntrst_delay <ms> - delay after deasserting <br />
trst in ms <br />
jtag_rclk fallback_speed_khz - set JTAG speed to RCLK or use <br />
fallback speed <br />
jtag_reset toggle reset lines <trst> <srst> <br />
jtag_speed (DEPRECATED) set jtag speed (if supported) <br />
load_image load_image <file> <address> <br />
['bin'|'ihex'|'elf'|'s19'] [min_address] <br />
[max_length] <br />
log_output redirect logging to <file> (default: stderr) <br />
mdb display memory bytes <addr> [count] <br />
mdh display memory half-words <addr> [count] <br />
mdw display memory words <addr> [count] <br />
mwb write memory byte <addr> <value> [count] <br />
mwh write memory half-word <addr> <value> [count] <br />
mww write memory word <addr> <value> [count] <br />
ocd_array2mem convert a TCL array to memory locations and write <br />
the values <ARRAYNAME> <WIDTH = 32/16/8> <br />
<ADDRESS> <COUNT> <br />
ocd_flash_banks return information about the flash banks <br />
ocd_mem2array read memory and return as a TCL array for script <br />
processing <ARRAYNAME> <WIDTH = 32/16/8> <ADDRESS> <br />
<COUNT> <br />
pathmove move JTAG to state1 then to state2, state3, etc. <br />
<state1>,<state2>,<stat3>... <br />
poll poll target state <br />
power_restore Overridable procedure run when power restore is <br />
detected. Runs 'reset init' by default. <br />
production <serialnumber> - Runs production procedure. Throws <br />
exception if procedure failed. Prints progress <br />
messages. Implement this procedure in the target <br />
script. <br />
production Runs test procedure. Throws exception if procedure <br />
failed. Prints progress messages. Implement in <br />
target script. <br />
production_info Displays information on production procedure for <br />
target script. Implement this procedure in target <br />
script. <br />
profile profiling samples the CPU PC <br />
rbp remove breakpoint <address> <br />
reg display or set a register <br />
reset reset target [run | halt | init] - default is run <br />
reset_config [none/trst_only/srst_only/trst_and_srst] <br />
[srst_pulls_trst/trst_pulls_srst] <br />
[combined/separate] <br />
[trst_push_pull/trst_open_drain] <br />
[srst_push_pull/srst_open_drain] <br />
resume resume target [addr] <br />
runtest move to Run-Test/Idle, and execute <num_cycles> <br />
rwp remove watchpoint <address> <br />
scan_chain print current scan chain configuration <br />
script <filename> - filename of OpenOCD script (tcl) to <br />
run <br />
shutdown shut the server down <br />
sleep <n> [busy] - sleep for n milliseconds. "busy" <br />
means busy wait <br />
soft_reset_halt halt the target and do a soft reset <br />
srst_deasserted Overridable procedure run when srst deassert is <br />
detected. Runs 'reset init' by default. <br />
step step one instruction from current PC or [addr] <br />
svf run svf <file> <br />
target configure target <br />
targets change the current command line target (one <br />
parameter) or lists targets (with no parameter) <br />
tcl_port port on which to listen for incoming TCL syntax <br />
telnet_port port on which to listen for incoming telnet <br />
connections <br />
test_image test_image <file> [offset] [type] <br />
tms_sequence choose short(default) or long tms_sequence <short <br />
| long> <br />
verify_image verify_image <file> [offset] [type] <br />
verify_ircapture verify value captured during Capture-IR <enable |<br />
disable><br />
verify_jtag verify value capture <enable | disable><br />
version show OpenOCD version<br />
virt2phys translate a virtual address into a physical<br />
address<br />
wait_halt wait for target halt [time (s)]<br />
wp list or set watchpoint [<address> <length> <r/w/a><br />
[value] [mask]]<br />
xsvf run xsvf <file> [virt2] [quiet]<br />
armv4_5 core_state display/change ARM core state <arm | thumb><br />
armv4_5 disassemble disassemble instructions <address> [<count><br />
['thumb']]<br />
armv4_5 reg display ARM core registers<br />
cortex_a8 cache_info display information about target caches<br />
dap apid return id reg from AP [num], default currently<br />
selected AP<br />
dap apsel select a different AP [num] (default 0)<br />
dap baseaddr return debug base address from AP [num], default<br />
currently selected AP<br />
dap info dap info for ap [num], default currently selected<br />
AP<br />
dap memaccess set/get number of extra tck for mem-ap memory bus<br />
access [0-255]<br />
flash bank flash bank <driver> <base> <size> <chip_width><br />
<bus_width> <target> [driver_options ...]<br />
mflash bank mflash bank <soc> <base> <RST pin> <target #><br />
nand device<br />
pld device<br />
target_request debugmsgs enable/disable reception of debug messages from<br />
target<br />
trace history display trace history, ['clear'] history or set<br />
[size]<br />
trace point display trace points, ['clear'] list of trace<br />
points, or add new tracepoint at [address]<br />
<br />
==Example session==<br />
<br />
Now, we can try to basically halt and resume OMAP3 (assuming U-Boot is running at U-Boot's prompt):<br />
<br />
> '''reset halt'''<br />
RCLK not supported - fallback to 1000 kHz<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG tap: omap3530.dap enabled<br />
omap3530.cpu: ran after reset and before halt ...<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
cpsr: 0x800001d3 pc: 0x40202994<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''scan_chain'''<br />
TapName Enabled IdCode Expected IrLen IrCap IrMask<br />
-- ------------------- -------- ---------- ---------- ----- ----- ------<br />
0 omap3530.dsp n 0x00000000 0x00000000 38 0x25 0x3f<br />
1 omap3530.dap Y 0x00000000 0x0b6d602f 4 0x01 0x0f<br />
2 omap3530.jrc Y 0x0b7ae02f 0x0b7ae02f 6 0x01 0x3f<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''halt'''<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''reg''' <br />
===== ARM registers <br />
(0) r0 (/32): 0x49020000 (dirty) <br />
(1) r1 (/32): 0x00000003 <br />
(2) r2 (/32): 0x00000001 <br />
(3) r3 (/32): 0x00000060 <br />
(4) r4 (/32): 0x00000055 <br />
(5) r5 (/32): 0x80EAC204 <br />
(6) r6 (/32): 0x80EAC204<br />
(7) r7 (/32): 0x80EA7985<br />
(8) r8 (/32): 0x80E3FFDC<br />
(9) r9 (/32): 0x00000002<br />
(10) r10 (/32): 0x00000018<br />
(11) r11 (/32): 0x00000000<br />
(12) r12 (/32): 0x00000000<br />
(13) sp_usr (/32)<br />
(14) lr_usr (/32)<br />
(15) pc (/32): 0x80E87F1C<br />
(16) r8_fiq (/32)<br />
(17) r9_fiq (/32)<br />
(18) r10_fiq (/32)<br />
(19) r11_fiq (/32)<br />
(20) r12_fiq (/32)<br />
(21) sp_fiq (/32)<br />
(22) lr_fiq (/32)<br />
(23) sp_irq (/32)<br />
(24) lr_irq (/32)<br />
(25) sp_svc (/32): 0x80E3FE80<br />
(26) lr_svc (/32): 0x80E87D7C<br />
(27) sp_abt (/32)<br />
(28) lr_abt (/32)<br />
(29) sp_und (/32)<br />
(30) lr_und (/32)<br />
(31) cpsr (/32): 0x400001D3<br />
(32) spsr_fiq (/32)<br />
(33) spsr_irq (/32)<br />
(34) spsr_svc (/32)<br />
(35) spsr_abt (/32)<br />
(36) spsr_und (/32)<br />
(37) sp_mon (/32)<br />
(38) lr_mon (/32)<br />
(39) spsr_mon (/32)<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''soft_reset_halt'''<br />
requesting target halt and executing a soft reset<br />
Target omap3.cpu does not support soft_reset_halt<br />
<br />
> '''cortex_a8 cache_info'''<br />
cache type: 0x0, unified cache<br />
D-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
I-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
<br />
> '''halt''' <br />
target state: halted <br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88158<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''arm disassemble 0x80e88158 10'''<br />
0x80e88158 0xe3130001 TST r3, #0x1<br />
0x80e8815c 0x0afffffc BEQ 0x80e88154<br />
0x80e88160 0xe5d00000 LDRB r0, [r0]<br />
0x80e88164 0xe12fff1e BX r14<br />
0x80e88168 0xe5d00014 LDRB r0, [r0, #0x14]<br />
0x80e8816c 0xe2000001 AND r0, r0, #0x1<br />
0x80e88170 0xe12fff1e BX r14<br />
0x80e88174 0xe1a02001 MOV r2, r1<br />
0x80e88178 0xe1a01000 MOV r1, r0<br />
0x80e8817c 0xe59f0000 LDR r0, [r15]<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e8815c<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88154<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp 0x80e88160 4 hw'''<br />
breakpoint set at 0x80e88160<br />
<br />
> '''resume'''<br />
<br />
''... type anything in U-Boot until breakpoint is hit ...''<br />
<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x000001d3 pc: 0x80e88160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp'''<br />
0x80e88160, 0x4, 1<br />
<br />
> '''rbp 0x80e88160'''<br />
<br />
> '''resume'''<br />
<br />
=GDB ARM=<br />
<br />
To [[DebuggingTheLinuxKernelUsingGdb|debug]] an ARM target with GNU debugger ([[GDB|GDB]]), you need a GDB understanding ARM processor. If your ARM cross compilation tool chain doesn't include a GDB, you can easily build it your self.<br />
<br />
==Build==<br />
<br />
* Download latest [http://www.gnu.org/software/gdb/download/ GDB sources]. [http://openocd.berlios.de/doc/GDB-and-OpenOCD.html#GDB-and-OpenOCD OpenOCD docu] recommends to use GDB 6.7 or newer. Here, we use GDB 6.8 which is the recent version while writing this.<br />
<br />
* Extract, configure and build GDB for ARM. Afterwards remove temporary stuff. Options are:<br />
** <path_where_ARM_gdb_shall_be_installed_to> : Directory where you want to install the resulting tool to. E.g. /home/user/arm-gdb/<br />
** <ARM_toolchain_prefix> : The prefix of your ARM GCC toolchain, e.g. ''arm-linux'' or ''arm-none-linux-gnueabi'' ([[BeagleBoard#Cortex_A8_ARM|CodeSourcery tool chain]]).<br />
<br />
> tar xfj gdb-6.8.tar.bz2<br />
> mkdir build-gdb<br />
> cd build-gdb/<br />
build-gdb > ../gdb-6.8/configure --prefix=<path_where_ARM_gdb_shall_be_installed_to> --target=<ARM_toolchain_prefix> i686-pc-linux-gnu<br />
build-gdb > make -j4<br />
build-gdb > make install<br />
build-gdb > cd ..<br />
> rm -rf gdb-6.8 build-gdb<br />
> export PATH=$PATH:<path_where_ARM_gdb_shall_be_installed_to>/bin<br />
<br />
Test:<br />
<br />
bin> ./arm-none-linux-gnueabi-gdb<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
(gdb)<br />
<br />
==Example session==<br />
<br />
To use gdb, you have to connect to running OpenOCD using remote command. E.g.:<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
<br />
(gdb) '''target remote localhost:3333'''<br />
Remote debugging using localhost:3333<br />
0x00000000 in ?? () <br />
(gdb) '''monitor omap3_dbginit''' <br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080 <br />
SWJ-DP STICKY ERROR <br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080 <br />
TargetName Type Endian TapName State <br />
-- ------------------ ---------- ------ ------------------ ------------ <br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown <br />
0x54011314 00000003 .... <br />
0x54011314 00000001 .... <br />
<br />
(gdb) '''monitor scan_chain''' <br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr <br />
---|--------------------|---------|------------|------------|------|------|------|--------- <br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a <br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
(gdb) '''info registers'''<br />
r0 0x0 0<br />
r1 0x60a 1546<br />
r2 0x80000100 2147483904<br />
r3 0x706 1798 <br />
r4 0xc00081b8 3221258680<br />
r5 0x0 0 <br />
r6 0x80026960 2147641696<br />
r7 0xc00081b8 3221258680<br />
r8 0x0 0 <br />
r9 0x411fc082 1092599938<br />
r10 0x800268f8 2147641592<br />
r11 0xf731c8f9 4147235065<br />
r12 0x80796ae0 2155440864<br />
sp 0x8051a900 0x8051a900<br />
lr 0x80008018 2147516440<br />
pc 0x8000815c 0x8000815c<br />
fps 0x0 0 <br />
cpsr 0x0 0 <br />
<br />
(gdb) '''p/x $pc''' <br />
$2 = 0x8000815c <br />
<br />
(gdb) '''x/i $pc''' <br />
0x8000815c: nop (mov r0,r0)<br />
<br />
(gdb) '''x'''<br />
0x80008160: b 0x8000815c<br />
<br />
==LED blink example==<br />
<br />
Magnus Lundin has a simple standalone LED blink test program which can be used for tests.<br />
<br />
* [http://github.com/mlu/cortal_dendrites/tree/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink LED blink] test program.<br />
* [http://github.com/mlu/cortal_dendrites/blob/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink/README README]<br />
* Example .gdbinit file:<br />
<br />
echo *** Executing .gdbint to set up the environment for debugging gdb:\n<br />
<br />
# This connects to OpenOcd at localhost:3333<br />
target remote localhost:3333<br />
<br />
# omap3_dbginit must be run in OpenOCD after every reset<br />
monitor omap3_dbginit<br />
<br />
# Stop core<br />
monitor halt<br />
<br />
echo *** Environment ready, now load and start executeable:\n<br />
<br />
# Load the program executable called "LEDblink"<br />
load LEDblink<br />
<br />
# Load the symbols for the program.<br />
symbol-file LEDblink<br />
<br />
# Set a breakpoint at main().<br />
b main<br />
<br />
# Run to the breakpoint.<br />
cont<br />
<br />
Clone the code by git, goto ''cortex_a8/standalone/LEDblink'' directory, build the example using provided Makefile and then in that directory start gdb (so that above .gdbinit is executed):<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
*** Executing .gdbint to set up the environment for debugging gdb:<br />
0x00000000 in ?? ()<br />
The target may not be able to correctly handle a memory-write-packet-size<br />
of 1024 bytes. Change the packet size? (y or n) [answered Y; input not from terminal]<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x600001d3 pc: 0x80008160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
*** Environment ready, now load and start executeable:<br />
Loading section .text, size 0xe0 lma 0x82000000<br />
Start address 0x82000000, load size 224<br />
Transfer rate: 4 KB/sec, 224 bytes/write.<br />
Current language: auto; currently asm<br />
Breakpoint 1 at 0x8200003c: file LEDblink.c, line 22.<br />
<br />
Breakpoint 1, main () at LEDblink.c:22<br />
22 LEDbrightness++;<br />
Current language: auto; currently c<br />
<br />
(gdb) '''cont'''<br />
<br />
This should let Beagle's LEDs blink.<br />
<br />
=Development internals=<br />
<br />
The sections below give some datails if you are interested in developing OpenOCD for OMAP3 and Cortex A8 used on Beagle. If you like to help to improve OpenOCD support for Beagle, this might help you.<br />
<br />
==Introduction==<br />
<br />
Magnus Lundin wrote a very nice [http://arttools.blogspot.com/2009/09/debugging-on-cortex-a8-system.html introduction] on the basic Cortex A8 (OMAP3) debug architecture.<br />
<br />
==Cortex A8 support==<br />
<br />
As mentioned above, OpenOCD has initial experimental Cortex A8 support. Rick Altherr wrote (thanks!) a [https://lists.berlios.de/pipermail/openocd-development/2009-April/005273.html nice intro] how to help with Cortex A8 support for OpenOCD:<br />
<br />
''The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c Cortex-M3 support] is very similar to Cortex-A8 up to a certain layer. The ARM debug interface is designed as a set of layers that build on each other and can do automatic discovery. The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_swjdp.c cortex-swjdp] support in OpenOCD is a good start, but it assumes which AHB and APB ports are available. The first item would be to verify the cortex-swjdp portion against the documents for the CoreSight debug interface.''<br />
<br />
''To really get started, familiarize yourself with the following docs:''<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0031a/index.html ARM IHI 0031A] (ARM Debug Interface v5)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0029b/index.html ARM IHI 0029B] (CoreSight v1.0)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0316d/DDI0316D_dap_lite_trm.pdf ARM DDI 0316D] (CoreSight DAP-Lite)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf ARM DDI 0314F] (CoreSight Components TRM)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf ARM DDI 0344H] (Cortex-A8 TRM, primarily chapter 12)''<br />
<br />
''These should be listed in the right order for getting up to speed. Basically the Cortex-A8 debug registers are accessed externally via CoreSight. CoreSight is an implementation of the ARM Debug Interface v5.''<br />
<br />
''The cortex-swjdp implementation in OpenOCD deals with CoreSight but makes some assumptions about which CoreSight components are available. For Cortex-A8, that will likely need to change a bit as the set of components will be different.''<br />
<br />
''After cortex-swjdp is patched to handle the new components, a cortex-a8 target implementation can be started by using the cortex-swjdp layer to access the various debug registers and memory locations.''<br />
<br />
For discussion about this, see [https://lists.berlios.de/pipermail/openocd-development/2009-March/005097.html mail #1], [https://lists.berlios.de/pipermail/openocd-development/2009-March/005099.html mail #2] and [https://lists.berlios.de/pipermail/openocd-development/2009-March/005117.html mail #3].<br />
<br />
Note: With revision ~1570 the cortex-swjdp module in OpenOCD has been renamed to arm_adi_v5 and updated to remove all dependencies on Cortex-M3 specific features and as far as possible only use the ARM Debug Interface v5 features. The Cortex-M3 specifics has been moved to cortex_m3 module. This is a step in preparing OpenOCD for full Cortex-A8 support. <br />
<br />
Using recent OpenOCD versions, you can examine CoreSight APs: <br />
<br />
<pre><br />
> version <br />
Open On-Chip Debugger 0.3.0-in-development (2009-08-30-19:54) svn:2643M<br />
<br />
> omap3_dbginit<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> scan_chain<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> dap apsel 0<br />
ap 0 selected, identification register 0x14770001<br />
<br />
> dap info 0<br />
ap identification register 0x14770001<br />
Type is mem-ap AHB <br />
ap debugbase 0xffffffff <br />
No ROM table present <br />
<br />
> dap info 1<br />
ap identification register 0x04770002<br />
Type is mem-ap APB <br />
ap debugbase 0x80000000 <br />
ROM table in legacy format<br />
CID3 0xb1, CID2 0x5, CID1 0x10, CID0, 0xd<br />
MEMTYPE system memory not present. Dedicated debug bus<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21 <br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
ROMTABLE[0xc] = 0xd4013002 <br />
Component not present <br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
ROMTABLE[0x20] = 0x0<br />
End of ROM table<br />
<br />
> dap apsel 1<br />
ap 1 selected, identification register 0x04770002<br />
<br />
> dap apsel 2<br />
ap 2 selected, identification register 0x14760010<br />
<br />
> dap info 2<br />
ap identification register 0x14760010<br />
Type is jtag-ap<br />
ap debugbase 0x00000000<br />
No ROM table present<br />
<br />
> dap apsel 3<br />
ap 3 selected, identification register 0x00000000<br />
<br />
> dap info 3<br />
ap identification register 0x00000000<br />
No AP found at this apsel 0x3<br />
No ROM table present<br />
<br />
><br />
</pre><br />
<br />
==ROMTable==<br />
<br />
To interpret content of above ROMTable, have a look to<br />
<br />
* [http://www.ti.com/litv/pdf/spruf98b OMAP35x Technical Reference Manual (Rev. B)] (spruf98b.pdf, 39622 Kbytes), Table 5-105<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf CoreSight Components TRM] (ARM DDI 0314F), Table 2-3<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] (ARM DDI 0344H)<br />
<br />
With this, we get (first three entries are in the MPU SS Module, address range 0x54010000 - 0x54018000, part number is given by PID1[3-0] and PID0[7-0]):<br />
<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21<br />
<br />
* Part number is 0x921: ETM module. See [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] chapter 14.<br />
<br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
<br />
* Part number is 0xC08: This is the [[BeagleBoardOpenOCD#Debug_Register_Interface|Debug Register Interface]]. See table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].<br />
<br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
<br />
* Part number 0x113: This is ????<br />
<br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
<br />
* Part number 0x912: TPIU Module. <br />
<br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
<br />
* Part number 0x907: ETB Module.<br />
<br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
<br />
* Part number 0x343: DAP CTL Module.<br />
<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
<br />
* Part number 0x120: SDTI Module.<br />
<br />
==Debug Register Interface==<br />
<br />
With above info about debug register interface and table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] we are able to access this interface using OpenOCDs ''mdw'' command:<br />
<br />
> omap3.cpu mdw 0x54011000<br />
0x54011000 15141012<br />
<br />
This is the debug ID register. See table 12-11 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM]:<br />
<br />
{|border=1<br />
!Bits<br />
!Field<br />
!Value & Function<br />
|-<br />
|[31-28]<br />
|WRP<br />
|0x1 -> 2 WRPs are implemented<br />
|-<br />
|[27-24]<br />
|BRP<br />
|0x5 -> 6 BRPs are implemented<br />
|-<br />
|[23-20]<br />
|Context<br />
|0x1 -> 2 BRPs have context ID capability<br />
|-<br />
|[19-16]<br />
|Debug architecture version<br />
|0x4 -> ARMv7 debug<br />
|-<br />
|[12]<br />
|security<br />
|0x1 -> Security extensions implemented<br />
|-<br />
|[7-4]<br />
|variant<br />
|0x1<br />
|-<br />
|[3-0]<br />
|revision<br />
|0x2 <br />
|-<br />
|}<br />
<br />
> omap3.cpu mdw 0x54011FF0<br />
0x54011ff0 0000000d<br />
> omap3.cpu mdw 0x54011FF4<br />
0x54011ff4 00000090<br />
> omap3.cpu mdw 0x54011FF8<br />
0x54011ff8 00000005<br />
> omap3.cpu mdw 0x54011FFC<br />
0x54011ffc 000000b1<br />
<br />
These are the component identification registers. See table 12-51 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].</div>Dirkhttp://elinux.org/BeagleBoardOpenOCDBeagleBoardOpenOCD2010-04-02T09:42:38Z<p>Dirk: Update example session</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page is about how to use open source [http://openocd.berlios.de/web/ OpenOCD] [http://en.wikipedia.org/wiki/JTAG JTAG] software with [[BeagleBoard|BeagleBoard]]. With this, it will be possible to have OMAP3 JTAG debug using cheap [[BeagleBoardJTAG|JTAG hardware]], e.g. [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]].<br />
<br />
'''As of September 2009, OpenOCD has basic support for OMAP3 and [[BeagleBoardOpenOCD#Cortex_A8_support|ARM Cortex A8]] on Beagle Board. Cortex A8 support is in early alpha stage, a lot is still missing. But e.g. processor halt, resume, step, breakpoints and ARM disassembly of non-Cache and non-MMU (e.g. U-Boot) applications seem to work.<br />
<br />
Status:<br />
<br />
* You need at least OpenOCD revision '''2770''' ([[BeagleBoardOpenOCD#Build_OpenOCD|using git]]). With this revision you will have basic access to OMAP3 and Cortex A8 can be basically controlled. This does mean, that OpenOCD is able to configure scan chain correctly to [[OMAP3530_ICEPICK#ICEPICK_infos|access ARM TAP]] ("JTAG controller"), explore CoreSight AccessPoints and halt, resume, step, breakpoints and ARM disassembly on Cortex A8.<br />
* Recent status as of '''September 2009''':<br />
** OpenOCD >= 2770 can and halt, resume, step, breakpoints and ARM disassembly Cortex A8 (ARM) processor on Beagle.<br />
** This works for non-MMU and non-Cache applications (e.g U-Boot).<br />
** [https://lists.berlios.de/pipermail/openocd-development/2009-August/010184.html Linux debugging doesn't work yet].<br />
<br />
<br />
=Hardware=<br />
<br />
To be able to use OpenOCD with OMAP3 based BeagleBoard, make sure that your JTAG Dongle supports:<br />
<br />
* 1.8V devices. Many JTAG dongles are 3.3V only! '''Verify that your dongle supports 1.8V!''' Else the dongle will overpowering the input to OMAP3 and may cause damage.<br />
* Your JTAG dongle is able to switch [[BeagleBoardJTAG#Beagle_JTAG_connection|EMU0 & EMU1 pins high]].<br />
<br />
Flyswatter dongle supports both requirements. If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way. In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).<br />
<br />
=Build OpenOCD=<br />
<br />
[http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD OpenOCD build instructions] describe how to build [http://openocd.berlios.de/web/ OpenOCD]. For questions you can use [https://lists.berlios.de/mailman/listinfo/openocd-development OpenOCD Mailing list].<br />
<br />
Get OpenOCD code via git:<br />
<br />
> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd openocd<br />
<br />
For Flyswatter you additionally need [http://www.ftdichip.com/Drivers/D2XX.htm libftd2xx] or [http://www.intra2net.com/de/produkte/opensource/ftdi/ libFTDI]. While libFTDI is available in source, libftd2xx is supposed to be 50% [http://www.beagleboard.org/irclogs/index.php?date=2008-10-16#T16:06:22 faster] than libFTDI. The libtfd2xx binaries are available booth as shared library or linkable archive.<br />
<br />
If you downloaded OpenOCD git and have libftd2xx or libFTDI, build OpenOCD (assuming you extracted/built FTDI library already):<br />
<br />
> cd openocd<br />
> ./bootstrap<br />
> ./configure --enable-ft2232_ftd2xx --with-ftd2xx-linux-tardir=<path_to>/libftd2xx0.4.16 --prefix=/home/user/bin/openOCD<br />
''or'' (depending which FTDI library you use, see above)<br />
> ./configure --enable-ft2232_libftdi --prefix=/home/user/bin/openOCD<br />
> make<br />
> make install<br />
<br />
When compiling the doc directory You get an error:<br />
openocd.texi:12: @include `version.texi': No such file or directory.<br />
It is possible to avoid by making version.texi. <br />
<br />
> cat doc/version.texi<br />
@set UPDATED 20 January 2009<br />
@set UPDATED-MONTH January 2009<br />
@set EDITION 0.1.0<br />
@set VERSION 0.1.0<br />
<br />
'''Note''': By default (make & make install) only .info documentation is installed. You can get PDF or HTML documentation by<br />
<br />
make pdf<br />
<br />
or<br />
<br />
make html<br />
<br />
Resulting documentation can be found in openocd/doc, then.<br />
<br />
'''Note''': If you like to save some disk space and don't plan to debug OpenOCD binary itself, you can strip this (remove unneeded debug symbols):<br />
<br />
> cd <openocd_install_dir>/bin<br />
> strip openocd<br />
<br />
(e.g. with OpenOCD 1.0 this reduced binary size from ~3MB to ~700kB)<br />
<br />
'''Note''': If you don't have libftdi in standard path, you might like to extend library search path:<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path_to>/lib<br />
<br />
if you e.g. get<br />
<br />
> ./openocd<br />
./openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory<br />
<br />
=Starting OpenOCD=<br />
<br />
OpenOCD runtime is controlled by several [http://openocd.berlios.de/doc/html/index.html#toc_Config-File-Guidelines configuration files]. OpenOCD comes with basic configuration files for BeagleBoard (''board/ti_beagleboard.cfg'') and OMAP3 (''target/omap3530.cfg'').<br />
<br />
Assuming that you use Flyswatter and it is switched on (attached to USB), you can now start OpenOCD with:<br />
<br />
openocd -s <path_to_config_files> // e.g. <path_of_openocd_install_dir>/lib/openocd<br />
-f <path_to_jtag_interface><br />
-f <path_to_beagle_config><br />
<br />
This should result in<br />
<br />
> '''openocd -s lib/openocd/ -f interface/flyswatter.cfg -f board/ti_beagleboard.cfg'''<br />
Open On-Chip Debugger 0.5.0-dev-00141-g33e5dd1 (2010-04-02-11:14)<br />
Licensed under GNU GPL v2<br />
For bug reports, read<br />
http://openocd.berlios.de/doc/doxygen/bugs.html<br />
RCLK - adaptive<br />
Warn : omap3530.dsp: huge IR length 38<br />
RCLK - adaptive<br />
trst_only separate trst_push_pull<br />
Info : RCLK (adaptive clock speed) not supported - fallback to 1000 kHz<br />
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
Info : JTAG tap: omap3530.dap enabled<br />
Info : omap3530.cpu: hardware has 6 breakpoints, 2 watchpoints<br />
<br />
This shows that your (Flyswatter) JTAG dongle basically works and that you are able to see OMAP3 JRC. OpenOCD now runs as daemon.<br />
<br />
=Controlling OpenOCD=<br />
<br />
Once OpenOCD runs as [http://openocd.berlios.de/doc/html/Running.html#Running daemon] like above, you can connect using ''telnet'' or ''GDB''<br />
<br />
==telnet==<br />
<br />
Connect to OpenOCD daemon. Assuming you do it on your local machine, open a second terminal window and do (assuming port 4444 as configured in above openocd.cfg):<br />
<br />
> '''telnet localhost 4444'''<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> <br />
<br />
This should give you<br />
<br />
Info: accepting 'telnet' connection from 0<br />
<br />
in window where OpenOCD daemon is started.<br />
<br />
At OpenOCDs telnet prompt you can now issue OpenOCD commands. E.g. ''help'' should result in<br />
<br />
> '''help''' <br />
bp list or set breakpoint [<address> <length> [hw]]<br />
cpu <name> - prints out target options and a comment <br />
on CPU which matches name <br />
debug_level adjust debug level <0-3> <br />
drscan execute DR scan <device> <num_bits> <value> <br />
<num_bits1> <value2> ... <br />
dump_image dump_image <file> <address> <size> <br />
exit exit telnet session <br />
fast fast <enable/disable> - place at beginning of <br />
config files. Sets defaults to fast and dangerous.<br />
<br />
fast_load loads active fast load image to current target - <br />
mainly for profiling purposes <br />
fast_load_image same args as load_image, image stored in memory - <br />
mainly for profiling purposes <br />
find <file> - print full path to file according to <br />
OpenOCD search rules <br />
flush_count returns number of times the JTAG queue has been <br />
flushed <br />
ft2232_device_desc the USB device description of the FTDI FT2232 <br />
device <br />
ft2232_latency set the FT2232 latency timer to a new value <br />
ft2232_layout the layout of the FT2232 GPIO signals used to <br />
control output-enables and reset signals <br />
ft2232_serial the serial number of the FTDI FT2232 device <br />
ft2232_vid_pid the vendor ID and product ID of the FTDI FT2232 <br />
device <br />
gdb_breakpoint_override hard/soft/disable - force breakpoint type for gdb <br />
'break' commands. <br />
gdb_detach resume/reset/halt/nothing - specify behavior when <br />
GDB detaches from the target <br />
gdb_flash_program enable or disable flash program <br />
gdb_memory_map enable or disable memory map <br />
gdb_port daemon configuration command gdb_port <br />
gdb_report_data_abort enable or disable reporting data aborts <br />
halt halt target <br />
help Tcl implementation of help command <br />
init initializes target and servers - nop on subsequent <br />
invocations <br />
interface try to configure interface <br />
interface_list list all built-in interfaces <br />
irscan execute IR scan <device> <instr> [dev2] [instr2] <br />
... <br />
jtag perform jtag tap actions <br />
jtag_device (DEPRECATED) jtag_device <ir_length> <ir_expected> <br />
<ir_mask> <br />
jtag_khz set maximum jtag speed (if supported); parameter <br />
is maximum khz, or 0 for adaptive clocking (RTCK). <br />
<br />
jtag_nsrst_delay jtag_nsrst_delay <ms> - delay after deasserting <br />
srst in ms <br />
jtag_ntrst_delay jtag_ntrst_delay <ms> - delay after deasserting <br />
trst in ms <br />
jtag_rclk fallback_speed_khz - set JTAG speed to RCLK or use <br />
fallback speed <br />
jtag_reset toggle reset lines <trst> <srst> <br />
jtag_speed (DEPRECATED) set jtag speed (if supported) <br />
load_image load_image <file> <address> <br />
['bin'|'ihex'|'elf'|'s19'] [min_address] <br />
[max_length] <br />
log_output redirect logging to <file> (default: stderr) <br />
mdb display memory bytes <addr> [count] <br />
mdh display memory half-words <addr> [count] <br />
mdw display memory words <addr> [count] <br />
mwb write memory byte <addr> <value> [count] <br />
mwh write memory half-word <addr> <value> [count] <br />
mww write memory word <addr> <value> [count] <br />
ocd_array2mem convert a TCL array to memory locations and write <br />
the values <ARRAYNAME> <WIDTH = 32/16/8> <br />
<ADDRESS> <COUNT> <br />
ocd_flash_banks return information about the flash banks <br />
ocd_mem2array read memory and return as a TCL array for script <br />
processing <ARRAYNAME> <WIDTH = 32/16/8> <ADDRESS> <br />
<COUNT> <br />
pathmove move JTAG to state1 then to state2, state3, etc. <br />
<state1>,<state2>,<stat3>... <br />
poll poll target state <br />
power_restore Overridable procedure run when power restore is <br />
detected. Runs 'reset init' by default. <br />
production <serialnumber> - Runs production procedure. Throws <br />
exception if procedure failed. Prints progress <br />
messages. Implement this procedure in the target <br />
script. <br />
production Runs test procedure. Throws exception if procedure <br />
failed. Prints progress messages. Implement in <br />
target script. <br />
production_info Displays information on production procedure for <br />
target script. Implement this procedure in target <br />
script. <br />
profile profiling samples the CPU PC <br />
rbp remove breakpoint <address> <br />
reg display or set a register <br />
reset reset target [run | halt | init] - default is run <br />
reset_config [none/trst_only/srst_only/trst_and_srst] <br />
[srst_pulls_trst/trst_pulls_srst] <br />
[combined/separate] <br />
[trst_push_pull/trst_open_drain] <br />
[srst_push_pull/srst_open_drain] <br />
resume resume target [addr] <br />
runtest move to Run-Test/Idle, and execute <num_cycles> <br />
rwp remove watchpoint <address> <br />
scan_chain print current scan chain configuration <br />
script <filename> - filename of OpenOCD script (tcl) to <br />
run <br />
shutdown shut the server down <br />
sleep <n> [busy] - sleep for n milliseconds. "busy" <br />
means busy wait <br />
soft_reset_halt halt the target and do a soft reset <br />
srst_deasserted Overridable procedure run when srst deassert is <br />
detected. Runs 'reset init' by default. <br />
step step one instruction from current PC or [addr] <br />
svf run svf <file> <br />
target configure target <br />
targets change the current command line target (one <br />
parameter) or lists targets (with no parameter) <br />
tcl_port port on which to listen for incoming TCL syntax <br />
telnet_port port on which to listen for incoming telnet <br />
connections <br />
test_image test_image <file> [offset] [type] <br />
tms_sequence choose short(default) or long tms_sequence <short <br />
| long> <br />
verify_image verify_image <file> [offset] [type] <br />
verify_ircapture verify value captured during Capture-IR <enable |<br />
disable><br />
verify_jtag verify value capture <enable | disable><br />
version show OpenOCD version<br />
virt2phys translate a virtual address into a physical<br />
address<br />
wait_halt wait for target halt [time (s)]<br />
wp list or set watchpoint [<address> <length> <r/w/a><br />
[value] [mask]]<br />
xsvf run xsvf <file> [virt2] [quiet]<br />
armv4_5 core_state display/change ARM core state <arm | thumb><br />
armv4_5 disassemble disassemble instructions <address> [<count><br />
['thumb']]<br />
armv4_5 reg display ARM core registers<br />
cortex_a8 cache_info display information about target caches<br />
dap apid return id reg from AP [num], default currently<br />
selected AP<br />
dap apsel select a different AP [num] (default 0)<br />
dap baseaddr return debug base address from AP [num], default<br />
currently selected AP<br />
dap info dap info for ap [num], default currently selected<br />
AP<br />
dap memaccess set/get number of extra tck for mem-ap memory bus<br />
access [0-255]<br />
flash bank flash bank <driver> <base> <size> <chip_width><br />
<bus_width> <target> [driver_options ...]<br />
mflash bank mflash bank <soc> <base> <RST pin> <target #><br />
nand device<br />
pld device<br />
target_request debugmsgs enable/disable reception of debug messages from<br />
target<br />
trace history display trace history, ['clear'] history or set<br />
[size]<br />
trace point display trace points, ['clear'] list of trace<br />
points, or add new tracepoint at [address]<br />
<br />
==Example session==<br />
<br />
Now, we can try to basically halt and resume OMAP3 (assuming U-Boot is running at U-Boot's prompt):<br />
<br />
> '''reset halt'''<br />
RCLK not supported - fallback to 1000 kHz<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG tap: omap3530.dap enabled<br />
omap3530.cpu: ran after reset and before halt ...<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
cpsr: 0x800001d3 pc: 0x40202994<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''scan_chain'''<br />
TapName Enabled IdCode Expected IrLen IrCap IrMask<br />
-- ------------------- -------- ---------- ---------- ----- ----- ------<br />
0 omap3530.dsp n 0x00000000 0x00000000 38 0x25 0x3f<br />
1 omap3530.dap Y 0x00000000 0x0b6d602f 4 0x01 0x0f<br />
2 omap3530.jrc Y 0x0b7ae02f 0x0b7ae02f 6 0x01 0x3f<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''halt'''<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> reg <br />
===== ARM registers <br />
(0) r0 (/32): 0x49020000 (dirty) <br />
(1) r1 (/32): 0x00000003 <br />
(2) r2 (/32): 0x00000001 <br />
(3) r3 (/32): 0x00000060 <br />
(4) r4 (/32): 0x00000055 <br />
(5) r5 (/32): 0x80EAC204 <br />
(6) r6 (/32): 0x80EAC204<br />
(7) r7 (/32): 0x80EA7985<br />
(8) r8 (/32): 0x80E3FFDC<br />
(9) r9 (/32): 0x00000002<br />
(10) r10 (/32): 0x00000018<br />
(11) r11 (/32): 0x00000000<br />
(12) r12 (/32): 0x00000000<br />
(13) sp_usr (/32)<br />
(14) lr_usr (/32)<br />
(15) pc (/32): 0x80E87F1C<br />
(16) r8_fiq (/32)<br />
(17) r9_fiq (/32)<br />
(18) r10_fiq (/32)<br />
(19) r11_fiq (/32)<br />
(20) r12_fiq (/32)<br />
(21) sp_fiq (/32)<br />
(22) lr_fiq (/32)<br />
(23) sp_irq (/32)<br />
(24) lr_irq (/32)<br />
(25) sp_svc (/32): 0x80E3FE80<br />
(26) lr_svc (/32): 0x80E87D7C<br />
(27) sp_abt (/32)<br />
(28) lr_abt (/32)<br />
(29) sp_und (/32)<br />
(30) lr_und (/32)<br />
(31) cpsr (/32): 0x400001D3<br />
(32) spsr_fiq (/32)<br />
(33) spsr_irq (/32)<br />
(34) spsr_svc (/32)<br />
(35) spsr_abt (/32)<br />
(36) spsr_und (/32)<br />
(37) sp_mon (/32)<br />
(38) lr_mon (/32)<br />
(39) spsr_mon (/32)<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''soft_reset_halt'''<br />
requesting target halt and executing a soft reset<br />
Target omap3.cpu does not support soft_reset_halt<br />
<br />
> '''cortex_a8 cache_info'''<br />
cache type: 0x0, unified cache<br />
D-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
I-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
<br />
> '''halt''' <br />
target state: halted <br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88158<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''arm disassemble 0x80e88158 10'''<br />
0x80e88158 0xe3130001 TST r3, #0x1<br />
0x80e8815c 0x0afffffc BEQ 0x80e88154<br />
0x80e88160 0xe5d00000 LDRB r0, [r0]<br />
0x80e88164 0xe12fff1e BX r14<br />
0x80e88168 0xe5d00014 LDRB r0, [r0, #0x14]<br />
0x80e8816c 0xe2000001 AND r0, r0, #0x1<br />
0x80e88170 0xe12fff1e BX r14<br />
0x80e88174 0xe1a02001 MOV r2, r1<br />
0x80e88178 0xe1a01000 MOV r1, r0<br />
0x80e8817c 0xe59f0000 LDR r0, [r15]<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e8815c<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88154<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp 0x80e88160 4 hw'''<br />
breakpoint set at 0x80e88160<br />
<br />
> '''resume'''<br />
<br />
''... type anything in U-Boot until breakpoint is hit ...''<br />
<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x000001d3 pc: 0x80e88160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp'''<br />
0x80e88160, 0x4, 1<br />
<br />
> '''rbp 0x80e88160'''<br />
<br />
> '''resume'''<br />
<br />
=GDB ARM=<br />
<br />
To [[DebuggingTheLinuxKernelUsingGdb|debug]] an ARM target with GNU debugger ([[GDB|GDB]]), you need a GDB understanding ARM processor. If your ARM cross compilation tool chain doesn't include a GDB, you can easily build it your self.<br />
<br />
==Build==<br />
<br />
* Download latest [http://www.gnu.org/software/gdb/download/ GDB sources]. [http://openocd.berlios.de/doc/GDB-and-OpenOCD.html#GDB-and-OpenOCD OpenOCD docu] recommends to use GDB 6.7 or newer. Here, we use GDB 6.8 which is the recent version while writing this.<br />
<br />
* Extract, configure and build GDB for ARM. Afterwards remove temporary stuff. Options are:<br />
** <path_where_ARM_gdb_shall_be_installed_to> : Directory where you want to install the resulting tool to. E.g. /home/user/arm-gdb/<br />
** <ARM_toolchain_prefix> : The prefix of your ARM GCC toolchain, e.g. ''arm-linux'' or ''arm-none-linux-gnueabi'' ([[BeagleBoard#Cortex_A8_ARM|CodeSourcery tool chain]]).<br />
<br />
> tar xfj gdb-6.8.tar.bz2<br />
> mkdir build-gdb<br />
> cd build-gdb/<br />
build-gdb > ../gdb-6.8/configure --prefix=<path_where_ARM_gdb_shall_be_installed_to> --target=<ARM_toolchain_prefix> i686-pc-linux-gnu<br />
build-gdb > make -j4<br />
build-gdb > make install<br />
build-gdb > cd ..<br />
> rm -rf gdb-6.8 build-gdb<br />
> export PATH=$PATH:<path_where_ARM_gdb_shall_be_installed_to>/bin<br />
<br />
Test:<br />
<br />
bin> ./arm-none-linux-gnueabi-gdb<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
(gdb)<br />
<br />
==Example session==<br />
<br />
To use gdb, you have to connect to running OpenOCD using remote command. E.g.:<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
<br />
(gdb) '''target remote localhost:3333'''<br />
Remote debugging using localhost:3333<br />
0x00000000 in ?? () <br />
(gdb) '''monitor omap3_dbginit''' <br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080 <br />
SWJ-DP STICKY ERROR <br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080 <br />
TargetName Type Endian TapName State <br />
-- ------------------ ---------- ------ ------------------ ------------ <br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown <br />
0x54011314 00000003 .... <br />
0x54011314 00000001 .... <br />
<br />
(gdb) '''monitor scan_chain''' <br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr <br />
---|--------------------|---------|------------|------------|------|------|------|--------- <br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a <br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
(gdb) '''info registers'''<br />
r0 0x0 0<br />
r1 0x60a 1546<br />
r2 0x80000100 2147483904<br />
r3 0x706 1798 <br />
r4 0xc00081b8 3221258680<br />
r5 0x0 0 <br />
r6 0x80026960 2147641696<br />
r7 0xc00081b8 3221258680<br />
r8 0x0 0 <br />
r9 0x411fc082 1092599938<br />
r10 0x800268f8 2147641592<br />
r11 0xf731c8f9 4147235065<br />
r12 0x80796ae0 2155440864<br />
sp 0x8051a900 0x8051a900<br />
lr 0x80008018 2147516440<br />
pc 0x8000815c 0x8000815c<br />
fps 0x0 0 <br />
cpsr 0x0 0 <br />
<br />
(gdb) '''p/x $pc''' <br />
$2 = 0x8000815c <br />
<br />
(gdb) '''x/i $pc''' <br />
0x8000815c: nop (mov r0,r0)<br />
<br />
(gdb) '''x'''<br />
0x80008160: b 0x8000815c<br />
<br />
==LED blink example==<br />
<br />
Magnus Lundin has a simple standalone LED blink test program which can be used for tests.<br />
<br />
* [http://github.com/mlu/cortal_dendrites/tree/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink LED blink] test program.<br />
* [http://github.com/mlu/cortal_dendrites/blob/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink/README README]<br />
* Example .gdbinit file:<br />
<br />
echo *** Executing .gdbint to set up the environment for debugging gdb:\n<br />
<br />
# This connects to OpenOcd at localhost:3333<br />
target remote localhost:3333<br />
<br />
# omap3_dbginit must be run in OpenOCD after every reset<br />
monitor omap3_dbginit<br />
<br />
# Stop core<br />
monitor halt<br />
<br />
echo *** Environment ready, now load and start executeable:\n<br />
<br />
# Load the program executable called "LEDblink"<br />
load LEDblink<br />
<br />
# Load the symbols for the program.<br />
symbol-file LEDblink<br />
<br />
# Set a breakpoint at main().<br />
b main<br />
<br />
# Run to the breakpoint.<br />
cont<br />
<br />
Clone the code by git, goto ''cortex_a8/standalone/LEDblink'' directory, build the example using provided Makefile and then in that directory start gdb (so that above .gdbinit is executed):<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
*** Executing .gdbint to set up the environment for debugging gdb:<br />
0x00000000 in ?? ()<br />
The target may not be able to correctly handle a memory-write-packet-size<br />
of 1024 bytes. Change the packet size? (y or n) [answered Y; input not from terminal]<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x600001d3 pc: 0x80008160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
*** Environment ready, now load and start executeable:<br />
Loading section .text, size 0xe0 lma 0x82000000<br />
Start address 0x82000000, load size 224<br />
Transfer rate: 4 KB/sec, 224 bytes/write.<br />
Current language: auto; currently asm<br />
Breakpoint 1 at 0x8200003c: file LEDblink.c, line 22.<br />
<br />
Breakpoint 1, main () at LEDblink.c:22<br />
22 LEDbrightness++;<br />
Current language: auto; currently c<br />
<br />
(gdb) '''cont'''<br />
<br />
This should let Beagle's LEDs blink.<br />
<br />
=Development internals=<br />
<br />
The sections below give some datails if you are interested in developing OpenOCD for OMAP3 and Cortex A8 used on Beagle. If you like to help to improve OpenOCD support for Beagle, this might help you.<br />
<br />
==Introduction==<br />
<br />
Magnus Lundin wrote a very nice [http://arttools.blogspot.com/2009/09/debugging-on-cortex-a8-system.html introduction] on the basic Cortex A8 (OMAP3) debug architecture.<br />
<br />
==Cortex A8 support==<br />
<br />
As mentioned above, OpenOCD has initial experimental Cortex A8 support. Rick Altherr wrote (thanks!) a [https://lists.berlios.de/pipermail/openocd-development/2009-April/005273.html nice intro] how to help with Cortex A8 support for OpenOCD:<br />
<br />
''The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c Cortex-M3 support] is very similar to Cortex-A8 up to a certain layer. The ARM debug interface is designed as a set of layers that build on each other and can do automatic discovery. The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_swjdp.c cortex-swjdp] support in OpenOCD is a good start, but it assumes which AHB and APB ports are available. The first item would be to verify the cortex-swjdp portion against the documents for the CoreSight debug interface.''<br />
<br />
''To really get started, familiarize yourself with the following docs:''<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0031a/index.html ARM IHI 0031A] (ARM Debug Interface v5)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0029b/index.html ARM IHI 0029B] (CoreSight v1.0)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0316d/DDI0316D_dap_lite_trm.pdf ARM DDI 0316D] (CoreSight DAP-Lite)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf ARM DDI 0314F] (CoreSight Components TRM)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf ARM DDI 0344H] (Cortex-A8 TRM, primarily chapter 12)''<br />
<br />
''These should be listed in the right order for getting up to speed. Basically the Cortex-A8 debug registers are accessed externally via CoreSight. CoreSight is an implementation of the ARM Debug Interface v5.''<br />
<br />
''The cortex-swjdp implementation in OpenOCD deals with CoreSight but makes some assumptions about which CoreSight components are available. For Cortex-A8, that will likely need to change a bit as the set of components will be different.''<br />
<br />
''After cortex-swjdp is patched to handle the new components, a cortex-a8 target implementation can be started by using the cortex-swjdp layer to access the various debug registers and memory locations.''<br />
<br />
For discussion about this, see [https://lists.berlios.de/pipermail/openocd-development/2009-March/005097.html mail #1], [https://lists.berlios.de/pipermail/openocd-development/2009-March/005099.html mail #2] and [https://lists.berlios.de/pipermail/openocd-development/2009-March/005117.html mail #3].<br />
<br />
Note: With revision ~1570 the cortex-swjdp module in OpenOCD has been renamed to arm_adi_v5 and updated to remove all dependencies on Cortex-M3 specific features and as far as possible only use the ARM Debug Interface v5 features. The Cortex-M3 specifics has been moved to cortex_m3 module. This is a step in preparing OpenOCD for full Cortex-A8 support. <br />
<br />
Using recent OpenOCD versions, you can examine CoreSight APs: <br />
<br />
<pre><br />
> version <br />
Open On-Chip Debugger 0.3.0-in-development (2009-08-30-19:54) svn:2643M<br />
<br />
> omap3_dbginit<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> scan_chain<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> dap apsel 0<br />
ap 0 selected, identification register 0x14770001<br />
<br />
> dap info 0<br />
ap identification register 0x14770001<br />
Type is mem-ap AHB <br />
ap debugbase 0xffffffff <br />
No ROM table present <br />
<br />
> dap info 1<br />
ap identification register 0x04770002<br />
Type is mem-ap APB <br />
ap debugbase 0x80000000 <br />
ROM table in legacy format<br />
CID3 0xb1, CID2 0x5, CID1 0x10, CID0, 0xd<br />
MEMTYPE system memory not present. Dedicated debug bus<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21 <br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
ROMTABLE[0xc] = 0xd4013002 <br />
Component not present <br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
ROMTABLE[0x20] = 0x0<br />
End of ROM table<br />
<br />
> dap apsel 1<br />
ap 1 selected, identification register 0x04770002<br />
<br />
> dap apsel 2<br />
ap 2 selected, identification register 0x14760010<br />
<br />
> dap info 2<br />
ap identification register 0x14760010<br />
Type is jtag-ap<br />
ap debugbase 0x00000000<br />
No ROM table present<br />
<br />
> dap apsel 3<br />
ap 3 selected, identification register 0x00000000<br />
<br />
> dap info 3<br />
ap identification register 0x00000000<br />
No AP found at this apsel 0x3<br />
No ROM table present<br />
<br />
><br />
</pre><br />
<br />
==ROMTable==<br />
<br />
To interpret content of above ROMTable, have a look to<br />
<br />
* [http://www.ti.com/litv/pdf/spruf98b OMAP35x Technical Reference Manual (Rev. B)] (spruf98b.pdf, 39622 Kbytes), Table 5-105<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf CoreSight Components TRM] (ARM DDI 0314F), Table 2-3<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] (ARM DDI 0344H)<br />
<br />
With this, we get (first three entries are in the MPU SS Module, address range 0x54010000 - 0x54018000, part number is given by PID1[3-0] and PID0[7-0]):<br />
<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21<br />
<br />
* Part number is 0x921: ETM module. See [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] chapter 14.<br />
<br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
<br />
* Part number is 0xC08: This is the [[BeagleBoardOpenOCD#Debug_Register_Interface|Debug Register Interface]]. See table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].<br />
<br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
<br />
* Part number 0x113: This is ????<br />
<br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
<br />
* Part number 0x912: TPIU Module. <br />
<br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
<br />
* Part number 0x907: ETB Module.<br />
<br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
<br />
* Part number 0x343: DAP CTL Module.<br />
<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
<br />
* Part number 0x120: SDTI Module.<br />
<br />
==Debug Register Interface==<br />
<br />
With above info about debug register interface and table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] we are able to access this interface using OpenOCDs ''mdw'' command:<br />
<br />
> omap3.cpu mdw 0x54011000<br />
0x54011000 15141012<br />
<br />
This is the debug ID register. See table 12-11 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM]:<br />
<br />
{|border=1<br />
!Bits<br />
!Field<br />
!Value & Function<br />
|-<br />
|[31-28]<br />
|WRP<br />
|0x1 -> 2 WRPs are implemented<br />
|-<br />
|[27-24]<br />
|BRP<br />
|0x5 -> 6 BRPs are implemented<br />
|-<br />
|[23-20]<br />
|Context<br />
|0x1 -> 2 BRPs have context ID capability<br />
|-<br />
|[19-16]<br />
|Debug architecture version<br />
|0x4 -> ARMv7 debug<br />
|-<br />
|[12]<br />
|security<br />
|0x1 -> Security extensions implemented<br />
|-<br />
|[7-4]<br />
|variant<br />
|0x1<br />
|-<br />
|[3-0]<br />
|revision<br />
|0x2 <br />
|-<br />
|}<br />
<br />
> omap3.cpu mdw 0x54011FF0<br />
0x54011ff0 0000000d<br />
> omap3.cpu mdw 0x54011FF4<br />
0x54011ff4 00000090<br />
> omap3.cpu mdw 0x54011FF8<br />
0x54011ff8 00000005<br />
> omap3.cpu mdw 0x54011FFC<br />
0x54011ffc 000000b1<br />
<br />
These are the component identification registers. See table 12-51 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].</div>Dirkhttp://elinux.org/BeagleBoardOpenOCDBeagleBoardOpenOCD2010-04-02T09:24:41Z<p>Dirk: Update output and fix typo</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page is about how to use open source [http://openocd.berlios.de/web/ OpenOCD] [http://en.wikipedia.org/wiki/JTAG JTAG] software with [[BeagleBoard|BeagleBoard]]. With this, it will be possible to have OMAP3 JTAG debug using cheap [[BeagleBoardJTAG|JTAG hardware]], e.g. [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]].<br />
<br />
'''As of September 2009, OpenOCD has basic support for OMAP3 and [[BeagleBoardOpenOCD#Cortex_A8_support|ARM Cortex A8]] on Beagle Board. Cortex A8 support is in early alpha stage, a lot is still missing. But e.g. processor halt, resume, step, breakpoints and ARM disassembly of non-Cache and non-MMU (e.g. U-Boot) applications seem to work.<br />
<br />
Status:<br />
<br />
* You need at least OpenOCD revision '''2770''' ([[BeagleBoardOpenOCD#Build_OpenOCD|using git]]). With this revision you will have basic access to OMAP3 and Cortex A8 can be basically controlled. This does mean, that OpenOCD is able to configure scan chain correctly to [[OMAP3530_ICEPICK#ICEPICK_infos|access ARM TAP]] ("JTAG controller"), explore CoreSight AccessPoints and halt, resume, step, breakpoints and ARM disassembly on Cortex A8.<br />
* Recent status as of '''September 2009''':<br />
** OpenOCD >= 2770 can and halt, resume, step, breakpoints and ARM disassembly Cortex A8 (ARM) processor on Beagle.<br />
** This works for non-MMU and non-Cache applications (e.g U-Boot).<br />
** [https://lists.berlios.de/pipermail/openocd-development/2009-August/010184.html Linux debugging doesn't work yet].<br />
<br />
<br />
=Hardware=<br />
<br />
To be able to use OpenOCD with OMAP3 based BeagleBoard, make sure that your JTAG Dongle supports:<br />
<br />
* 1.8V devices. Many JTAG dongles are 3.3V only! '''Verify that your dongle supports 1.8V!''' Else the dongle will overpowering the input to OMAP3 and may cause damage.<br />
* Your JTAG dongle is able to switch [[BeagleBoardJTAG#Beagle_JTAG_connection|EMU0 & EMU1 pins high]].<br />
<br />
Flyswatter dongle supports both requirements. If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way. In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).<br />
<br />
=Build OpenOCD=<br />
<br />
[http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD OpenOCD build instructions] describe how to build [http://openocd.berlios.de/web/ OpenOCD]. For questions you can use [https://lists.berlios.de/mailman/listinfo/openocd-development OpenOCD Mailing list].<br />
<br />
Get OpenOCD code via git:<br />
<br />
> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd openocd<br />
<br />
For Flyswatter you additionally need [http://www.ftdichip.com/Drivers/D2XX.htm libftd2xx] or [http://www.intra2net.com/de/produkte/opensource/ftdi/ libFTDI]. While libFTDI is available in source, libftd2xx is supposed to be 50% [http://www.beagleboard.org/irclogs/index.php?date=2008-10-16#T16:06:22 faster] than libFTDI. The libtfd2xx binaries are available booth as shared library or linkable archive.<br />
<br />
If you downloaded OpenOCD git and have libftd2xx or libFTDI, build OpenOCD (assuming you extracted/built FTDI library already):<br />
<br />
> cd openocd<br />
> ./bootstrap<br />
> ./configure --enable-ft2232_ftd2xx --with-ftd2xx-linux-tardir=<path_to>/libftd2xx0.4.16 --prefix=/home/user/bin/openOCD<br />
''or'' (depending which FTDI library you use, see above)<br />
> ./configure --enable-ft2232_libftdi --prefix=/home/user/bin/openOCD<br />
> make<br />
> make install<br />
<br />
When compiling the doc directory You get an error:<br />
openocd.texi:12: @include `version.texi': No such file or directory.<br />
It is possible to avoid by making version.texi. <br />
<br />
> cat doc/version.texi<br />
@set UPDATED 20 January 2009<br />
@set UPDATED-MONTH January 2009<br />
@set EDITION 0.1.0<br />
@set VERSION 0.1.0<br />
<br />
'''Note''': By default (make & make install) only .info documentation is installed. You can get PDF or HTML documentation by<br />
<br />
make pdf<br />
<br />
or<br />
<br />
make html<br />
<br />
Resulting documentation can be found in openocd/doc, then.<br />
<br />
'''Note''': If you like to save some disk space and don't plan to debug OpenOCD binary itself, you can strip this (remove unneeded debug symbols):<br />
<br />
> cd <openocd_install_dir>/bin<br />
> strip openocd<br />
<br />
(e.g. with OpenOCD 1.0 this reduced binary size from ~3MB to ~700kB)<br />
<br />
'''Note''': If you don't have libftdi in standard path, you might like to extend library search path:<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path_to>/lib<br />
<br />
if you e.g. get<br />
<br />
> ./openocd<br />
./openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory<br />
<br />
=Starting OpenOCD=<br />
<br />
OpenOCD runtime is controlled by several [http://openocd.berlios.de/doc/html/index.html#toc_Config-File-Guidelines configuration files]. OpenOCD comes with basic configuration files for BeagleBoard (''board/ti_beagleboard.cfg'') and OMAP3 (''target/omap3530.cfg'').<br />
<br />
Assuming that you use Flyswatter and it is switched on (attached to USB), you can now start OpenOCD with:<br />
<br />
openocd -s <path_to_config_files> // e.g. <path_of_openocd_install_dir>/lib/openocd<br />
-f <path_to_jtag_interface><br />
-f <path_to_beagle_config><br />
<br />
This should result in<br />
<br />
> '''openocd -s lib/openocd/ -f interface/flyswatter.cfg -f board/ti_beagleboard.cfg'''<br />
Open On-Chip Debugger 0.5.0-dev-00141-g33e5dd1 (2010-04-02-11:14)<br />
Licensed under GNU GPL v2<br />
For bug reports, read<br />
http://openocd.berlios.de/doc/doxygen/bugs.html<br />
RCLK - adaptive<br />
Warn : omap3530.dsp: huge IR length 38<br />
RCLK - adaptive<br />
trst_only separate trst_push_pull<br />
Info : RCLK (adaptive clock speed) not supported - fallback to 1000 kHz<br />
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
Info : JTAG tap: omap3530.dap enabled<br />
Info : omap3530.cpu: hardware has 6 breakpoints, 2 watchpoints<br />
<br />
This shows that your (Flyswatter) JTAG dongle basically works and that you are able to see OMAP3 JRC. OpenOCD now runs as daemon.<br />
<br />
=Controlling OpenOCD=<br />
<br />
Once OpenOCD runs as [http://openocd.berlios.de/doc/html/Running.html#Running daemon] like above, you can connect using ''telnet'' or ''GDB''<br />
<br />
==telnet==<br />
<br />
Connect to OpenOCD daemon. Assuming you do it on your local machine, open a second terminal window and do (assuming port 4444 as configured in above openocd.cfg):<br />
<br />
> '''telnet localhost 4444'''<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> <br />
<br />
This should give you<br />
<br />
Info: accepting 'telnet' connection from 0<br />
<br />
in window where OpenOCD daemon is started.<br />
<br />
At OpenOCDs telnet prompt you can now issue OpenOCD commands. E.g. ''help'' should result in<br />
<br />
> '''help''' <br />
bp list or set breakpoint [<address> <length> [hw]]<br />
cpu <name> - prints out target options and a comment <br />
on CPU which matches name <br />
debug_level adjust debug level <0-3> <br />
drscan execute DR scan <device> <num_bits> <value> <br />
<num_bits1> <value2> ... <br />
dump_image dump_image <file> <address> <size> <br />
exit exit telnet session <br />
fast fast <enable/disable> - place at beginning of <br />
config files. Sets defaults to fast and dangerous.<br />
<br />
fast_load loads active fast load image to current target - <br />
mainly for profiling purposes <br />
fast_load_image same args as load_image, image stored in memory - <br />
mainly for profiling purposes <br />
find <file> - print full path to file according to <br />
OpenOCD search rules <br />
flush_count returns number of times the JTAG queue has been <br />
flushed <br />
ft2232_device_desc the USB device description of the FTDI FT2232 <br />
device <br />
ft2232_latency set the FT2232 latency timer to a new value <br />
ft2232_layout the layout of the FT2232 GPIO signals used to <br />
control output-enables and reset signals <br />
ft2232_serial the serial number of the FTDI FT2232 device <br />
ft2232_vid_pid the vendor ID and product ID of the FTDI FT2232 <br />
device <br />
gdb_breakpoint_override hard/soft/disable - force breakpoint type for gdb <br />
'break' commands. <br />
gdb_detach resume/reset/halt/nothing - specify behavior when <br />
GDB detaches from the target <br />
gdb_flash_program enable or disable flash program <br />
gdb_memory_map enable or disable memory map <br />
gdb_port daemon configuration command gdb_port <br />
gdb_report_data_abort enable or disable reporting data aborts <br />
halt halt target <br />
help Tcl implementation of help command <br />
init initializes target and servers - nop on subsequent <br />
invocations <br />
interface try to configure interface <br />
interface_list list all built-in interfaces <br />
irscan execute IR scan <device> <instr> [dev2] [instr2] <br />
... <br />
jtag perform jtag tap actions <br />
jtag_device (DEPRECATED) jtag_device <ir_length> <ir_expected> <br />
<ir_mask> <br />
jtag_khz set maximum jtag speed (if supported); parameter <br />
is maximum khz, or 0 for adaptive clocking (RTCK). <br />
<br />
jtag_nsrst_delay jtag_nsrst_delay <ms> - delay after deasserting <br />
srst in ms <br />
jtag_ntrst_delay jtag_ntrst_delay <ms> - delay after deasserting <br />
trst in ms <br />
jtag_rclk fallback_speed_khz - set JTAG speed to RCLK or use <br />
fallback speed <br />
jtag_reset toggle reset lines <trst> <srst> <br />
jtag_speed (DEPRECATED) set jtag speed (if supported) <br />
load_image load_image <file> <address> <br />
['bin'|'ihex'|'elf'|'s19'] [min_address] <br />
[max_length] <br />
log_output redirect logging to <file> (default: stderr) <br />
mdb display memory bytes <addr> [count] <br />
mdh display memory half-words <addr> [count] <br />
mdw display memory words <addr> [count] <br />
mwb write memory byte <addr> <value> [count] <br />
mwh write memory half-word <addr> <value> [count] <br />
mww write memory word <addr> <value> [count] <br />
ocd_array2mem convert a TCL array to memory locations and write <br />
the values <ARRAYNAME> <WIDTH = 32/16/8> <br />
<ADDRESS> <COUNT> <br />
ocd_flash_banks return information about the flash banks <br />
ocd_mem2array read memory and return as a TCL array for script <br />
processing <ARRAYNAME> <WIDTH = 32/16/8> <ADDRESS> <br />
<COUNT> <br />
pathmove move JTAG to state1 then to state2, state3, etc. <br />
<state1>,<state2>,<stat3>... <br />
poll poll target state <br />
power_restore Overridable procedure run when power restore is <br />
detected. Runs 'reset init' by default. <br />
production <serialnumber> - Runs production procedure. Throws <br />
exception if procedure failed. Prints progress <br />
messages. Implement this procedure in the target <br />
script. <br />
production Runs test procedure. Throws exception if procedure <br />
failed. Prints progress messages. Implement in <br />
target script. <br />
production_info Displays information on production procedure for <br />
target script. Implement this procedure in target <br />
script. <br />
profile profiling samples the CPU PC <br />
rbp remove breakpoint <address> <br />
reg display or set a register <br />
reset reset target [run | halt | init] - default is run <br />
reset_config [none/trst_only/srst_only/trst_and_srst] <br />
[srst_pulls_trst/trst_pulls_srst] <br />
[combined/separate] <br />
[trst_push_pull/trst_open_drain] <br />
[srst_push_pull/srst_open_drain] <br />
resume resume target [addr] <br />
runtest move to Run-Test/Idle, and execute <num_cycles> <br />
rwp remove watchpoint <address> <br />
scan_chain print current scan chain configuration <br />
script <filename> - filename of OpenOCD script (tcl) to <br />
run <br />
shutdown shut the server down <br />
sleep <n> [busy] - sleep for n milliseconds. "busy" <br />
means busy wait <br />
soft_reset_halt halt the target and do a soft reset <br />
srst_deasserted Overridable procedure run when srst deassert is <br />
detected. Runs 'reset init' by default. <br />
step step one instruction from current PC or [addr] <br />
svf run svf <file> <br />
target configure target <br />
targets change the current command line target (one <br />
parameter) or lists targets (with no parameter) <br />
tcl_port port on which to listen for incoming TCL syntax <br />
telnet_port port on which to listen for incoming telnet <br />
connections <br />
test_image test_image <file> [offset] [type] <br />
tms_sequence choose short(default) or long tms_sequence <short <br />
| long> <br />
verify_image verify_image <file> [offset] [type] <br />
verify_ircapture verify value captured during Capture-IR <enable |<br />
disable><br />
verify_jtag verify value capture <enable | disable><br />
version show OpenOCD version<br />
virt2phys translate a virtual address into a physical<br />
address<br />
wait_halt wait for target halt [time (s)]<br />
wp list or set watchpoint [<address> <length> <r/w/a><br />
[value] [mask]]<br />
xsvf run xsvf <file> [virt2] [quiet]<br />
armv4_5 core_state display/change ARM core state <arm | thumb><br />
armv4_5 disassemble disassemble instructions <address> [<count><br />
['thumb']]<br />
armv4_5 reg display ARM core registers<br />
cortex_a8 cache_info display information about target caches<br />
dap apid return id reg from AP [num], default currently<br />
selected AP<br />
dap apsel select a different AP [num] (default 0)<br />
dap baseaddr return debug base address from AP [num], default<br />
currently selected AP<br />
dap info dap info for ap [num], default currently selected<br />
AP<br />
dap memaccess set/get number of extra tck for mem-ap memory bus<br />
access [0-255]<br />
flash bank flash bank <driver> <base> <size> <chip_width><br />
<bus_width> <target> [driver_options ...]<br />
mflash bank mflash bank <soc> <base> <RST pin> <target #><br />
nand device<br />
pld device<br />
target_request debugmsgs enable/disable reception of debug messages from<br />
target<br />
trace history display trace history, ['clear'] history or set<br />
[size]<br />
trace point display trace points, ['clear'] list of trace<br />
points, or add new tracepoint at [address]<br />
<br />
==Example session==<br />
<br />
Now, we can try to basically halt and resume OMAP3 (assuming U-Boot is running at U-Boot's prompt):<br />
<br />
> '''omap3_dbginit'''<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> '''scan_chain'''<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> '''halt'''<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''soft_reset_halt'''<br />
requesting target halt and executing a soft reset<br />
Target omap3.cpu does not support soft_reset_halt<br />
<br />
> '''cortex_a8 cache_info'''<br />
cache type: 0x0, unified cache<br />
D-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
I-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
<br />
> '''halt''' <br />
target state: halted <br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88158<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''armv4_5 disassemble 0x80e88158 10'''<br />
0x80e88158 0xe3130001 TST r3, #0x1<br />
0x80e8815c 0x0afffffc BEQ 0x80e88154<br />
0x80e88160 0xe5d00000 LDRB r0, [r0]<br />
0x80e88164 0xe12fff1e BX r14<br />
0x80e88168 0xe5d00014 LDRB r0, [r0, #0x14]<br />
0x80e8816c 0xe2000001 AND r0, r0, #0x1<br />
0x80e88170 0xe12fff1e BX r14<br />
0x80e88174 0xe1a02001 MOV r2, r1<br />
0x80e88178 0xe1a01000 MOV r1, r0<br />
0x80e8817c 0xe59f0000 LDR r0, [r15]<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e8815c<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88154<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp 0x80e88160 4 hw'''<br />
breakpoint set at 0x80e88160<br />
<br />
> '''resume'''<br />
<br />
''... type anything in U-Boot until breakpoint is hit ...''<br />
<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x000001d3 pc: 0x80e88160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp'''<br />
0x80e88160, 0x4, 1<br />
<br />
> '''rbp 0x80e88160'''<br />
<br />
> '''resume'''<br />
<br />
=GDB ARM=<br />
<br />
To [[DebuggingTheLinuxKernelUsingGdb|debug]] an ARM target with GNU debugger ([[GDB|GDB]]), you need a GDB understanding ARM processor. If your ARM cross compilation tool chain doesn't include a GDB, you can easily build it your self.<br />
<br />
==Build==<br />
<br />
* Download latest [http://www.gnu.org/software/gdb/download/ GDB sources]. [http://openocd.berlios.de/doc/GDB-and-OpenOCD.html#GDB-and-OpenOCD OpenOCD docu] recommends to use GDB 6.7 or newer. Here, we use GDB 6.8 which is the recent version while writing this.<br />
<br />
* Extract, configure and build GDB for ARM. Afterwards remove temporary stuff. Options are:<br />
** <path_where_ARM_gdb_shall_be_installed_to> : Directory where you want to install the resulting tool to. E.g. /home/user/arm-gdb/<br />
** <ARM_toolchain_prefix> : The prefix of your ARM GCC toolchain, e.g. ''arm-linux'' or ''arm-none-linux-gnueabi'' ([[BeagleBoard#Cortex_A8_ARM|CodeSourcery tool chain]]).<br />
<br />
> tar xfj gdb-6.8.tar.bz2<br />
> mkdir build-gdb<br />
> cd build-gdb/<br />
build-gdb > ../gdb-6.8/configure --prefix=<path_where_ARM_gdb_shall_be_installed_to> --target=<ARM_toolchain_prefix> i686-pc-linux-gnu<br />
build-gdb > make -j4<br />
build-gdb > make install<br />
build-gdb > cd ..<br />
> rm -rf gdb-6.8 build-gdb<br />
> export PATH=$PATH:<path_where_ARM_gdb_shall_be_installed_to>/bin<br />
<br />
Test:<br />
<br />
bin> ./arm-none-linux-gnueabi-gdb<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
(gdb)<br />
<br />
==Example session==<br />
<br />
To use gdb, you have to connect to running OpenOCD using remote command. E.g.:<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
<br />
(gdb) '''target remote localhost:3333'''<br />
Remote debugging using localhost:3333<br />
0x00000000 in ?? () <br />
(gdb) '''monitor omap3_dbginit''' <br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080 <br />
SWJ-DP STICKY ERROR <br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080 <br />
TargetName Type Endian TapName State <br />
-- ------------------ ---------- ------ ------------------ ------------ <br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown <br />
0x54011314 00000003 .... <br />
0x54011314 00000001 .... <br />
<br />
(gdb) '''monitor scan_chain''' <br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr <br />
---|--------------------|---------|------------|------------|------|------|------|--------- <br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a <br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
(gdb) '''info registers'''<br />
r0 0x0 0<br />
r1 0x60a 1546<br />
r2 0x80000100 2147483904<br />
r3 0x706 1798 <br />
r4 0xc00081b8 3221258680<br />
r5 0x0 0 <br />
r6 0x80026960 2147641696<br />
r7 0xc00081b8 3221258680<br />
r8 0x0 0 <br />
r9 0x411fc082 1092599938<br />
r10 0x800268f8 2147641592<br />
r11 0xf731c8f9 4147235065<br />
r12 0x80796ae0 2155440864<br />
sp 0x8051a900 0x8051a900<br />
lr 0x80008018 2147516440<br />
pc 0x8000815c 0x8000815c<br />
fps 0x0 0 <br />
cpsr 0x0 0 <br />
<br />
(gdb) '''p/x $pc''' <br />
$2 = 0x8000815c <br />
<br />
(gdb) '''x/i $pc''' <br />
0x8000815c: nop (mov r0,r0)<br />
<br />
(gdb) '''x'''<br />
0x80008160: b 0x8000815c<br />
<br />
==LED blink example==<br />
<br />
Magnus Lundin has a simple standalone LED blink test program which can be used for tests.<br />
<br />
* [http://github.com/mlu/cortal_dendrites/tree/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink LED blink] test program.<br />
* [http://github.com/mlu/cortal_dendrites/blob/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink/README README]<br />
* Example .gdbinit file:<br />
<br />
echo *** Executing .gdbint to set up the environment for debugging gdb:\n<br />
<br />
# This connects to OpenOcd at localhost:3333<br />
target remote localhost:3333<br />
<br />
# omap3_dbginit must be run in OpenOCD after every reset<br />
monitor omap3_dbginit<br />
<br />
# Stop core<br />
monitor halt<br />
<br />
echo *** Environment ready, now load and start executeable:\n<br />
<br />
# Load the program executable called "LEDblink"<br />
load LEDblink<br />
<br />
# Load the symbols for the program.<br />
symbol-file LEDblink<br />
<br />
# Set a breakpoint at main().<br />
b main<br />
<br />
# Run to the breakpoint.<br />
cont<br />
<br />
Clone the code by git, goto ''cortex_a8/standalone/LEDblink'' directory, build the example using provided Makefile and then in that directory start gdb (so that above .gdbinit is executed):<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
*** Executing .gdbint to set up the environment for debugging gdb:<br />
0x00000000 in ?? ()<br />
The target may not be able to correctly handle a memory-write-packet-size<br />
of 1024 bytes. Change the packet size? (y or n) [answered Y; input not from terminal]<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x600001d3 pc: 0x80008160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
*** Environment ready, now load and start executeable:<br />
Loading section .text, size 0xe0 lma 0x82000000<br />
Start address 0x82000000, load size 224<br />
Transfer rate: 4 KB/sec, 224 bytes/write.<br />
Current language: auto; currently asm<br />
Breakpoint 1 at 0x8200003c: file LEDblink.c, line 22.<br />
<br />
Breakpoint 1, main () at LEDblink.c:22<br />
22 LEDbrightness++;<br />
Current language: auto; currently c<br />
<br />
(gdb) '''cont'''<br />
<br />
This should let Beagle's LEDs blink.<br />
<br />
=Development internals=<br />
<br />
The sections below give some datails if you are interested in developing OpenOCD for OMAP3 and Cortex A8 used on Beagle. If you like to help to improve OpenOCD support for Beagle, this might help you.<br />
<br />
==Introduction==<br />
<br />
Magnus Lundin wrote a very nice [http://arttools.blogspot.com/2009/09/debugging-on-cortex-a8-system.html introduction] on the basic Cortex A8 (OMAP3) debug architecture.<br />
<br />
==Cortex A8 support==<br />
<br />
As mentioned above, OpenOCD has initial experimental Cortex A8 support. Rick Altherr wrote (thanks!) a [https://lists.berlios.de/pipermail/openocd-development/2009-April/005273.html nice intro] how to help with Cortex A8 support for OpenOCD:<br />
<br />
''The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c Cortex-M3 support] is very similar to Cortex-A8 up to a certain layer. The ARM debug interface is designed as a set of layers that build on each other and can do automatic discovery. The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_swjdp.c cortex-swjdp] support in OpenOCD is a good start, but it assumes which AHB and APB ports are available. The first item would be to verify the cortex-swjdp portion against the documents for the CoreSight debug interface.''<br />
<br />
''To really get started, familiarize yourself with the following docs:''<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0031a/index.html ARM IHI 0031A] (ARM Debug Interface v5)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0029b/index.html ARM IHI 0029B] (CoreSight v1.0)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0316d/DDI0316D_dap_lite_trm.pdf ARM DDI 0316D] (CoreSight DAP-Lite)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf ARM DDI 0314F] (CoreSight Components TRM)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf ARM DDI 0344H] (Cortex-A8 TRM, primarily chapter 12)''<br />
<br />
''These should be listed in the right order for getting up to speed. Basically the Cortex-A8 debug registers are accessed externally via CoreSight. CoreSight is an implementation of the ARM Debug Interface v5.''<br />
<br />
''The cortex-swjdp implementation in OpenOCD deals with CoreSight but makes some assumptions about which CoreSight components are available. For Cortex-A8, that will likely need to change a bit as the set of components will be different.''<br />
<br />
''After cortex-swjdp is patched to handle the new components, a cortex-a8 target implementation can be started by using the cortex-swjdp layer to access the various debug registers and memory locations.''<br />
<br />
For discussion about this, see [https://lists.berlios.de/pipermail/openocd-development/2009-March/005097.html mail #1], [https://lists.berlios.de/pipermail/openocd-development/2009-March/005099.html mail #2] and [https://lists.berlios.de/pipermail/openocd-development/2009-March/005117.html mail #3].<br />
<br />
Note: With revision ~1570 the cortex-swjdp module in OpenOCD has been renamed to arm_adi_v5 and updated to remove all dependencies on Cortex-M3 specific features and as far as possible only use the ARM Debug Interface v5 features. The Cortex-M3 specifics has been moved to cortex_m3 module. This is a step in preparing OpenOCD for full Cortex-A8 support. <br />
<br />
Using recent OpenOCD versions, you can examine CoreSight APs: <br />
<br />
<pre><br />
> version <br />
Open On-Chip Debugger 0.3.0-in-development (2009-08-30-19:54) svn:2643M<br />
<br />
> omap3_dbginit<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> scan_chain<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> dap apsel 0<br />
ap 0 selected, identification register 0x14770001<br />
<br />
> dap info 0<br />
ap identification register 0x14770001<br />
Type is mem-ap AHB <br />
ap debugbase 0xffffffff <br />
No ROM table present <br />
<br />
> dap info 1<br />
ap identification register 0x04770002<br />
Type is mem-ap APB <br />
ap debugbase 0x80000000 <br />
ROM table in legacy format<br />
CID3 0xb1, CID2 0x5, CID1 0x10, CID0, 0xd<br />
MEMTYPE system memory not present. Dedicated debug bus<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21 <br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
ROMTABLE[0xc] = 0xd4013002 <br />
Component not present <br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
ROMTABLE[0x20] = 0x0<br />
End of ROM table<br />
<br />
> dap apsel 1<br />
ap 1 selected, identification register 0x04770002<br />
<br />
> dap apsel 2<br />
ap 2 selected, identification register 0x14760010<br />
<br />
> dap info 2<br />
ap identification register 0x14760010<br />
Type is jtag-ap<br />
ap debugbase 0x00000000<br />
No ROM table present<br />
<br />
> dap apsel 3<br />
ap 3 selected, identification register 0x00000000<br />
<br />
> dap info 3<br />
ap identification register 0x00000000<br />
No AP found at this apsel 0x3<br />
No ROM table present<br />
<br />
><br />
</pre><br />
<br />
==ROMTable==<br />
<br />
To interpret content of above ROMTable, have a look to<br />
<br />
* [http://www.ti.com/litv/pdf/spruf98b OMAP35x Technical Reference Manual (Rev. B)] (spruf98b.pdf, 39622 Kbytes), Table 5-105<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf CoreSight Components TRM] (ARM DDI 0314F), Table 2-3<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] (ARM DDI 0344H)<br />
<br />
With this, we get (first three entries are in the MPU SS Module, address range 0x54010000 - 0x54018000, part number is given by PID1[3-0] and PID0[7-0]):<br />
<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21<br />
<br />
* Part number is 0x921: ETM module. See [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] chapter 14.<br />
<br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
<br />
* Part number is 0xC08: This is the [[BeagleBoardOpenOCD#Debug_Register_Interface|Debug Register Interface]]. See table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].<br />
<br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
<br />
* Part number 0x113: This is ????<br />
<br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
<br />
* Part number 0x912: TPIU Module. <br />
<br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
<br />
* Part number 0x907: ETB Module.<br />
<br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
<br />
* Part number 0x343: DAP CTL Module.<br />
<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
<br />
* Part number 0x120: SDTI Module.<br />
<br />
==Debug Register Interface==<br />
<br />
With above info about debug register interface and table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] we are able to access this interface using OpenOCDs ''mdw'' command:<br />
<br />
> omap3.cpu mdw 0x54011000<br />
0x54011000 15141012<br />
<br />
This is the debug ID register. See table 12-11 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM]:<br />
<br />
{|border=1<br />
!Bits<br />
!Field<br />
!Value & Function<br />
|-<br />
|[31-28]<br />
|WRP<br />
|0x1 -> 2 WRPs are implemented<br />
|-<br />
|[27-24]<br />
|BRP<br />
|0x5 -> 6 BRPs are implemented<br />
|-<br />
|[23-20]<br />
|Context<br />
|0x1 -> 2 BRPs have context ID capability<br />
|-<br />
|[19-16]<br />
|Debug architecture version<br />
|0x4 -> ARMv7 debug<br />
|-<br />
|[12]<br />
|security<br />
|0x1 -> Security extensions implemented<br />
|-<br />
|[7-4]<br />
|variant<br />
|0x1<br />
|-<br />
|[3-0]<br />
|revision<br />
|0x2 <br />
|-<br />
|}<br />
<br />
> omap3.cpu mdw 0x54011FF0<br />
0x54011ff0 0000000d<br />
> omap3.cpu mdw 0x54011FF4<br />
0x54011ff4 00000090<br />
> omap3.cpu mdw 0x54011FF8<br />
0x54011ff8 00000005<br />
> omap3.cpu mdw 0x54011FFC<br />
0x54011ffc 000000b1<br />
<br />
These are the component identification registers. See table 12-51 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].</div>Dirkhttp://elinux.org/BeagleBoardOpenOCDBeagleBoardOpenOCD2010-04-02T09:09:47Z<p>Dirk: svn -> git</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page is about how to use open source [http://openocd.berlios.de/web/ OpenOCD] [http://en.wikipedia.org/wiki/JTAG JTAG] software with [[BeagleBoard|BeagleBoard]]. With this, it will be possible to have OMAP3 JTAG debug using cheap [[BeagleBoardJTAG|JTAG hardware]], e.g. [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]].<br />
<br />
'''As of September 2009, OpenOCD has basic support for OMAP3 and [[BeagleBoardOpenOCD#Cortex_A8_support|ARM Cortex A8]] on Beagle Board. Cortex A8 support is in early alpha stage, a lot is still missing. But e.g. processor halt, resume, step, breakpoints and ARM disassembly of non-Cache and non-MMU (e.g. U-Boot) applications seem to work.<br />
<br />
Status:<br />
<br />
* You need at least OpenOCD revision '''2770''' ([[BeagleBoardOpenOCD#Build_OpenOCD|using git]]). With this revision you will have basic access to OMAP3 and Cortex A8 can be basically controlled. This does mean, that OpenOCD is able to configure scan chain correctly to [[OMAP3530_ICEPICK#ICEPICK_infos|access ARM TAP]] ("JTAG controller"), explore CoreSight AccessPoints and halt, resume, step, breakpoints and ARM disassembly on Cortex A8.<br />
* Recent status as of '''September 2009''':<br />
** OpenOCD >= 2770 can and halt, resume, step, breakpoints and ARM disassembly Cortex A8 (ARM) processor on Beagle.<br />
** This works for non-MMU and non-Cache applications (e.g U-Boot).<br />
** [https://lists.berlios.de/pipermail/openocd-development/2009-August/010184.html Linux debugging doesn't work yet].<br />
<br />
<br />
=Hardware=<br />
<br />
To be able to use OpenOCD with OMAP3 based BeagleBoard, make sure that your JTAG Dongle supports:<br />
<br />
* 1.8V devices. Many JTAG dongles are 3.3V only! '''Verify that your dongle supports 1.8V!''' Else the dongle will overpowering the input to OMAP3 and may cause damage.<br />
* Your JTAG dongle is able to switch [[BeagleBoardJTAG#Beagle_JTAG_connection|EMU0 & EMU1 pins high]].<br />
<br />
Flyswatter dongle supports both requirements. If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way. In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).<br />
<br />
=Build OpenOCD=<br />
<br />
[http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD OpenOCD build instructions] describe how to build [http://openocd.berlios.de/web/ OpenOCD]. For questions you can use [https://lists.berlios.de/mailman/listinfo/openocd-development OpenOCD Mailing list].<br />
<br />
Get OpenOCD code via git:<br />
<br />
> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd openocd<br />
<br />
For Flyswatter you additionally need [http://www.ftdichip.com/Drivers/D2XX.htm libftd2xx] or [http://www.intra2net.com/de/produkte/opensource/ftdi/ libFTDI]. While libFTDI is available in source, libftd2xx is supposed to be 50% [http://www.beagleboard.org/irclogs/index.php?date=2008-10-16#T16:06:22 faster] than libFTDI. The libtfd2xx binaries are available booth as shared library or linkable archive.<br />
<br />
If you downloaded OpenOCD git and have libftd2xx or libFTDI, build OpenOCD (assuming you extracted/built FTDI library already):<br />
<br />
> cd openocd<br />
> ./bootstrap<br />
> ./configure --enable-ft2232_ftd2xx --with-ftd2xx-linux-tardir=<path_to>/libftd2xx0.4.16 --prefix=/home/user/bin/openOCD<br />
''or'' (depending which FTDI library you use, see above)<br />
> ./configure --enable-ft2232_libftdi --prefix=/home/user/bin/openOCD<br />
> make<br />
> make install<br />
<br />
When compiling the doc directory You get an error:<br />
openocd.texi:12: @include `version.texi': No such file or directory.<br />
It is possible to avoid by making version.texi. <br />
<br />
> cat doc/version.texi<br />
@set UPDATED 20 January 2009<br />
@set UPDATED-MONTH January 2009<br />
@set EDITION 0.1.0<br />
@set VERSION 0.1.0<br />
<br />
'''Note''': By default (make & make install) only .info documentation is installed. You can get PDF or HTML documentation by<br />
<br />
make pdf<br />
<br />
or<br />
<br />
make html<br />
<br />
Resulting documentation can be found in openocd/doc, then.<br />
<br />
'''Note''': If you like to save some disk space and don't plan to debug OpenOCD binary itself, you can strip this (remove unneeded debug symbols):<br />
<br />
> cd <openocd_install_dir>/bin<br />
> strip openocd<br />
<br />
(e.g. with OpenOCD 1.0 this reduced binary size from ~3MB to ~700kB)<br />
<br />
'''Note''': If you don't have libftdi in standard path, you might like to extend library search path:<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path_to>/lib<br />
<br />
if you e.g. get<br />
<br />
> ./openocd<br />
./openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory<br />
<br />
=Starting OpenOCD=<br />
<br />
OpenOCD runtime is controlled by several [http://openocd.berlios.de/doc/html/index.html#toc_Config-File-Guidelines configuration files]. OpenOCD comes with basic configuration files for BeagleBoard (''board/ti_beagleboard.cfg'') and OMAP3 (''target/omap3530.cfg'').<br />
<br />
Assuming that you use Flyswatter and it is switched on (attached to USB), you can now start OpenOCD with:<br />
<br />
openocd -s <path_to_config_files> // e.g. <path_of_openocd_install_dir>/lib/openocd<br />
-f <path_to_jtag_interface><br />
-f <path_to_beagle_config><br />
<br />
This should result in<br />
<br />
> '''openocd -s lib/openocd/ -f interface/flyswatter.cfg -f board/ti_beagleboard.cfg'''<br />
Open On-Chip Debugger 0.3.0-in-development (2009-09-29-16:28) svn:2770<br />
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $<br />
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS<br />
RCLK - adaptive <br />
Warn : huge IR length 38 <br />
Info : RCLK (adaptive clock speed) not supported - fallback to 6000 kHz<br />
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
<br />
This shows that your (Flyswatter) JTAG dongle basically works and that you are able to see OMAP3 JRC. OpenOCD now runs as deamon.<br />
<br />
=Controlling OpenOCD=<br />
<br />
Once OpenOCD runs as [http://openocd.berlios.de/doc/html/Running.html#Running daemon] like above, you can connect using ''telnet'' or ''GDB''<br />
<br />
==telnet==<br />
<br />
Connect to OpenOCD daemon. Assuming you do it on your local machine, open a second terminal window and do (assuming port 4444 as configured in above openocd.cfg):<br />
<br />
> '''telnet localhost 4444'''<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> <br />
<br />
This should give you<br />
<br />
Info: accepting 'telnet' connection from 0<br />
<br />
in window where OpenOCD daemon is started.<br />
<br />
At OpenOCDs telnet prompt you can now issue OpenOCD commands. E.g. ''help'' should result in<br />
<br />
> '''help''' <br />
bp list or set breakpoint [<address> <length> [hw]]<br />
cpu <name> - prints out target options and a comment <br />
on CPU which matches name <br />
debug_level adjust debug level <0-3> <br />
drscan execute DR scan <device> <num_bits> <value> <br />
<num_bits1> <value2> ... <br />
dump_image dump_image <file> <address> <size> <br />
exit exit telnet session <br />
fast fast <enable/disable> - place at beginning of <br />
config files. Sets defaults to fast and dangerous.<br />
<br />
fast_load loads active fast load image to current target - <br />
mainly for profiling purposes <br />
fast_load_image same args as load_image, image stored in memory - <br />
mainly for profiling purposes <br />
find <file> - print full path to file according to <br />
OpenOCD search rules <br />
flush_count returns number of times the JTAG queue has been <br />
flushed <br />
ft2232_device_desc the USB device description of the FTDI FT2232 <br />
device <br />
ft2232_latency set the FT2232 latency timer to a new value <br />
ft2232_layout the layout of the FT2232 GPIO signals used to <br />
control output-enables and reset signals <br />
ft2232_serial the serial number of the FTDI FT2232 device <br />
ft2232_vid_pid the vendor ID and product ID of the FTDI FT2232 <br />
device <br />
gdb_breakpoint_override hard/soft/disable - force breakpoint type for gdb <br />
'break' commands. <br />
gdb_detach resume/reset/halt/nothing - specify behavior when <br />
GDB detaches from the target <br />
gdb_flash_program enable or disable flash program <br />
gdb_memory_map enable or disable memory map <br />
gdb_port daemon configuration command gdb_port <br />
gdb_report_data_abort enable or disable reporting data aborts <br />
halt halt target <br />
help Tcl implementation of help command <br />
init initializes target and servers - nop on subsequent <br />
invocations <br />
interface try to configure interface <br />
interface_list list all built-in interfaces <br />
irscan execute IR scan <device> <instr> [dev2] [instr2] <br />
... <br />
jtag perform jtag tap actions <br />
jtag_device (DEPRECATED) jtag_device <ir_length> <ir_expected> <br />
<ir_mask> <br />
jtag_khz set maximum jtag speed (if supported); parameter <br />
is maximum khz, or 0 for adaptive clocking (RTCK). <br />
<br />
jtag_nsrst_delay jtag_nsrst_delay <ms> - delay after deasserting <br />
srst in ms <br />
jtag_ntrst_delay jtag_ntrst_delay <ms> - delay after deasserting <br />
trst in ms <br />
jtag_rclk fallback_speed_khz - set JTAG speed to RCLK or use <br />
fallback speed <br />
jtag_reset toggle reset lines <trst> <srst> <br />
jtag_speed (DEPRECATED) set jtag speed (if supported) <br />
load_image load_image <file> <address> <br />
['bin'|'ihex'|'elf'|'s19'] [min_address] <br />
[max_length] <br />
log_output redirect logging to <file> (default: stderr) <br />
mdb display memory bytes <addr> [count] <br />
mdh display memory half-words <addr> [count] <br />
mdw display memory words <addr> [count] <br />
mwb write memory byte <addr> <value> [count] <br />
mwh write memory half-word <addr> <value> [count] <br />
mww write memory word <addr> <value> [count] <br />
ocd_array2mem convert a TCL array to memory locations and write <br />
the values <ARRAYNAME> <WIDTH = 32/16/8> <br />
<ADDRESS> <COUNT> <br />
ocd_flash_banks return information about the flash banks <br />
ocd_mem2array read memory and return as a TCL array for script <br />
processing <ARRAYNAME> <WIDTH = 32/16/8> <ADDRESS> <br />
<COUNT> <br />
pathmove move JTAG to state1 then to state2, state3, etc. <br />
<state1>,<state2>,<stat3>... <br />
poll poll target state <br />
power_restore Overridable procedure run when power restore is <br />
detected. Runs 'reset init' by default. <br />
production <serialnumber> - Runs production procedure. Throws <br />
exception if procedure failed. Prints progress <br />
messages. Implement this procedure in the target <br />
script. <br />
production Runs test procedure. Throws exception if procedure <br />
failed. Prints progress messages. Implement in <br />
target script. <br />
production_info Displays information on production procedure for <br />
target script. Implement this procedure in target <br />
script. <br />
profile profiling samples the CPU PC <br />
rbp remove breakpoint <address> <br />
reg display or set a register <br />
reset reset target [run | halt | init] - default is run <br />
reset_config [none/trst_only/srst_only/trst_and_srst] <br />
[srst_pulls_trst/trst_pulls_srst] <br />
[combined/separate] <br />
[trst_push_pull/trst_open_drain] <br />
[srst_push_pull/srst_open_drain] <br />
resume resume target [addr] <br />
runtest move to Run-Test/Idle, and execute <num_cycles> <br />
rwp remove watchpoint <address> <br />
scan_chain print current scan chain configuration <br />
script <filename> - filename of OpenOCD script (tcl) to <br />
run <br />
shutdown shut the server down <br />
sleep <n> [busy] - sleep for n milliseconds. "busy" <br />
means busy wait <br />
soft_reset_halt halt the target and do a soft reset <br />
srst_deasserted Overridable procedure run when srst deassert is <br />
detected. Runs 'reset init' by default. <br />
step step one instruction from current PC or [addr] <br />
svf run svf <file> <br />
target configure target <br />
targets change the current command line target (one <br />
parameter) or lists targets (with no parameter) <br />
tcl_port port on which to listen for incoming TCL syntax <br />
telnet_port port on which to listen for incoming telnet <br />
connections <br />
test_image test_image <file> [offset] [type] <br />
tms_sequence choose short(default) or long tms_sequence <short <br />
| long> <br />
verify_image verify_image <file> [offset] [type] <br />
verify_ircapture verify value captured during Capture-IR <enable |<br />
disable><br />
verify_jtag verify value capture <enable | disable><br />
version show OpenOCD version<br />
virt2phys translate a virtual address into a physical<br />
address<br />
wait_halt wait for target halt [time (s)]<br />
wp list or set watchpoint [<address> <length> <r/w/a><br />
[value] [mask]]<br />
xsvf run xsvf <file> [virt2] [quiet]<br />
armv4_5 core_state display/change ARM core state <arm | thumb><br />
armv4_5 disassemble disassemble instructions <address> [<count><br />
['thumb']]<br />
armv4_5 reg display ARM core registers<br />
cortex_a8 cache_info display information about target caches<br />
dap apid return id reg from AP [num], default currently<br />
selected AP<br />
dap apsel select a different AP [num] (default 0)<br />
dap baseaddr return debug base address from AP [num], default<br />
currently selected AP<br />
dap info dap info for ap [num], default currently selected<br />
AP<br />
dap memaccess set/get number of extra tck for mem-ap memory bus<br />
access [0-255]<br />
flash bank flash bank <driver> <base> <size> <chip_width><br />
<bus_width> <target> [driver_options ...]<br />
mflash bank mflash bank <soc> <base> <RST pin> <target #><br />
nand device<br />
pld device<br />
target_request debugmsgs enable/disable reception of debug messages from<br />
target<br />
trace history display trace history, ['clear'] history or set<br />
[size]<br />
trace point display trace points, ['clear'] list of trace<br />
points, or add new tracepoint at [address]<br />
<br />
==Example session==<br />
<br />
Now, we can try to basically halt and resume OMAP3 (assuming U-Boot is running at U-Boot's prompt):<br />
<br />
> '''omap3_dbginit'''<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> '''scan_chain'''<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> '''halt'''<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''soft_reset_halt'''<br />
requesting target halt and executing a soft reset<br />
Target omap3.cpu does not support soft_reset_halt<br />
<br />
> '''cortex_a8 cache_info'''<br />
cache type: 0x0, unified cache<br />
D-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
I-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
<br />
> '''halt''' <br />
target state: halted <br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88158<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''armv4_5 disassemble 0x80e88158 10'''<br />
0x80e88158 0xe3130001 TST r3, #0x1<br />
0x80e8815c 0x0afffffc BEQ 0x80e88154<br />
0x80e88160 0xe5d00000 LDRB r0, [r0]<br />
0x80e88164 0xe12fff1e BX r14<br />
0x80e88168 0xe5d00014 LDRB r0, [r0, #0x14]<br />
0x80e8816c 0xe2000001 AND r0, r0, #0x1<br />
0x80e88170 0xe12fff1e BX r14<br />
0x80e88174 0xe1a02001 MOV r2, r1<br />
0x80e88178 0xe1a01000 MOV r1, r0<br />
0x80e8817c 0xe59f0000 LDR r0, [r15]<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e8815c<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88154<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp 0x80e88160 4 hw'''<br />
breakpoint set at 0x80e88160<br />
<br />
> '''resume'''<br />
<br />
''... type anything in U-Boot until breakpoint is hit ...''<br />
<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x000001d3 pc: 0x80e88160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp'''<br />
0x80e88160, 0x4, 1<br />
<br />
> '''rbp 0x80e88160'''<br />
<br />
> '''resume'''<br />
<br />
=GDB ARM=<br />
<br />
To [[DebuggingTheLinuxKernelUsingGdb|debug]] an ARM target with GNU debugger ([[GDB|GDB]]), you need a GDB understanding ARM processor. If your ARM cross compilation tool chain doesn't include a GDB, you can easily build it your self.<br />
<br />
==Build==<br />
<br />
* Download latest [http://www.gnu.org/software/gdb/download/ GDB sources]. [http://openocd.berlios.de/doc/GDB-and-OpenOCD.html#GDB-and-OpenOCD OpenOCD docu] recommends to use GDB 6.7 or newer. Here, we use GDB 6.8 which is the recent version while writing this.<br />
<br />
* Extract, configure and build GDB for ARM. Afterwards remove temporary stuff. Options are:<br />
** <path_where_ARM_gdb_shall_be_installed_to> : Directory where you want to install the resulting tool to. E.g. /home/user/arm-gdb/<br />
** <ARM_toolchain_prefix> : The prefix of your ARM GCC toolchain, e.g. ''arm-linux'' or ''arm-none-linux-gnueabi'' ([[BeagleBoard#Cortex_A8_ARM|CodeSourcery tool chain]]).<br />
<br />
> tar xfj gdb-6.8.tar.bz2<br />
> mkdir build-gdb<br />
> cd build-gdb/<br />
build-gdb > ../gdb-6.8/configure --prefix=<path_where_ARM_gdb_shall_be_installed_to> --target=<ARM_toolchain_prefix> i686-pc-linux-gnu<br />
build-gdb > make -j4<br />
build-gdb > make install<br />
build-gdb > cd ..<br />
> rm -rf gdb-6.8 build-gdb<br />
> export PATH=$PATH:<path_where_ARM_gdb_shall_be_installed_to>/bin<br />
<br />
Test:<br />
<br />
bin> ./arm-none-linux-gnueabi-gdb<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
(gdb)<br />
<br />
==Example session==<br />
<br />
To use gdb, you have to connect to running OpenOCD using remote command. E.g.:<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
<br />
(gdb) '''target remote localhost:3333'''<br />
Remote debugging using localhost:3333<br />
0x00000000 in ?? () <br />
(gdb) '''monitor omap3_dbginit''' <br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080 <br />
SWJ-DP STICKY ERROR <br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080 <br />
TargetName Type Endian TapName State <br />
-- ------------------ ---------- ------ ------------------ ------------ <br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown <br />
0x54011314 00000003 .... <br />
0x54011314 00000001 .... <br />
<br />
(gdb) '''monitor scan_chain''' <br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr <br />
---|--------------------|---------|------------|------------|------|------|------|--------- <br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a <br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
(gdb) '''info registers'''<br />
r0 0x0 0<br />
r1 0x60a 1546<br />
r2 0x80000100 2147483904<br />
r3 0x706 1798 <br />
r4 0xc00081b8 3221258680<br />
r5 0x0 0 <br />
r6 0x80026960 2147641696<br />
r7 0xc00081b8 3221258680<br />
r8 0x0 0 <br />
r9 0x411fc082 1092599938<br />
r10 0x800268f8 2147641592<br />
r11 0xf731c8f9 4147235065<br />
r12 0x80796ae0 2155440864<br />
sp 0x8051a900 0x8051a900<br />
lr 0x80008018 2147516440<br />
pc 0x8000815c 0x8000815c<br />
fps 0x0 0 <br />
cpsr 0x0 0 <br />
<br />
(gdb) '''p/x $pc''' <br />
$2 = 0x8000815c <br />
<br />
(gdb) '''x/i $pc''' <br />
0x8000815c: nop (mov r0,r0)<br />
<br />
(gdb) '''x'''<br />
0x80008160: b 0x8000815c<br />
<br />
==LED blink example==<br />
<br />
Magnus Lundin has a simple standalone LED blink test program which can be used for tests.<br />
<br />
* [http://github.com/mlu/cortal_dendrites/tree/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink LED blink] test program.<br />
* [http://github.com/mlu/cortal_dendrites/blob/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink/README README]<br />
* Example .gdbinit file:<br />
<br />
echo *** Executing .gdbint to set up the environment for debugging gdb:\n<br />
<br />
# This connects to OpenOcd at localhost:3333<br />
target remote localhost:3333<br />
<br />
# omap3_dbginit must be run in OpenOCD after every reset<br />
monitor omap3_dbginit<br />
<br />
# Stop core<br />
monitor halt<br />
<br />
echo *** Environment ready, now load and start executeable:\n<br />
<br />
# Load the program executable called "LEDblink"<br />
load LEDblink<br />
<br />
# Load the symbols for the program.<br />
symbol-file LEDblink<br />
<br />
# Set a breakpoint at main().<br />
b main<br />
<br />
# Run to the breakpoint.<br />
cont<br />
<br />
Clone the code by git, goto ''cortex_a8/standalone/LEDblink'' directory, build the example using provided Makefile and then in that directory start gdb (so that above .gdbinit is executed):<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
*** Executing .gdbint to set up the environment for debugging gdb:<br />
0x00000000 in ?? ()<br />
The target may not be able to correctly handle a memory-write-packet-size<br />
of 1024 bytes. Change the packet size? (y or n) [answered Y; input not from terminal]<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x600001d3 pc: 0x80008160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
*** Environment ready, now load and start executeable:<br />
Loading section .text, size 0xe0 lma 0x82000000<br />
Start address 0x82000000, load size 224<br />
Transfer rate: 4 KB/sec, 224 bytes/write.<br />
Current language: auto; currently asm<br />
Breakpoint 1 at 0x8200003c: file LEDblink.c, line 22.<br />
<br />
Breakpoint 1, main () at LEDblink.c:22<br />
22 LEDbrightness++;<br />
Current language: auto; currently c<br />
<br />
(gdb) '''cont'''<br />
<br />
This should let Beagle's LEDs blink.<br />
<br />
=Development internals=<br />
<br />
The sections below give some datails if you are interested in developing OpenOCD for OMAP3 and Cortex A8 used on Beagle. If you like to help to improve OpenOCD support for Beagle, this might help you.<br />
<br />
==Introduction==<br />
<br />
Magnus Lundin wrote a very nice [http://arttools.blogspot.com/2009/09/debugging-on-cortex-a8-system.html introduction] on the basic Cortex A8 (OMAP3) debug architecture.<br />
<br />
==Cortex A8 support==<br />
<br />
As mentioned above, OpenOCD has initial experimental Cortex A8 support. Rick Altherr wrote (thanks!) a [https://lists.berlios.de/pipermail/openocd-development/2009-April/005273.html nice intro] how to help with Cortex A8 support for OpenOCD:<br />
<br />
''The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c Cortex-M3 support] is very similar to Cortex-A8 up to a certain layer. The ARM debug interface is designed as a set of layers that build on each other and can do automatic discovery. The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_swjdp.c cortex-swjdp] support in OpenOCD is a good start, but it assumes which AHB and APB ports are available. The first item would be to verify the cortex-swjdp portion against the documents for the CoreSight debug interface.''<br />
<br />
''To really get started, familiarize yourself with the following docs:''<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0031a/index.html ARM IHI 0031A] (ARM Debug Interface v5)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0029b/index.html ARM IHI 0029B] (CoreSight v1.0)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0316d/DDI0316D_dap_lite_trm.pdf ARM DDI 0316D] (CoreSight DAP-Lite)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf ARM DDI 0314F] (CoreSight Components TRM)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf ARM DDI 0344H] (Cortex-A8 TRM, primarily chapter 12)''<br />
<br />
''These should be listed in the right order for getting up to speed. Basically the Cortex-A8 debug registers are accessed externally via CoreSight. CoreSight is an implementation of the ARM Debug Interface v5.''<br />
<br />
''The cortex-swjdp implementation in OpenOCD deals with CoreSight but makes some assumptions about which CoreSight components are available. For Cortex-A8, that will likely need to change a bit as the set of components will be different.''<br />
<br />
''After cortex-swjdp is patched to handle the new components, a cortex-a8 target implementation can be started by using the cortex-swjdp layer to access the various debug registers and memory locations.''<br />
<br />
For discussion about this, see [https://lists.berlios.de/pipermail/openocd-development/2009-March/005097.html mail #1], [https://lists.berlios.de/pipermail/openocd-development/2009-March/005099.html mail #2] and [https://lists.berlios.de/pipermail/openocd-development/2009-March/005117.html mail #3].<br />
<br />
Note: With revision ~1570 the cortex-swjdp module in OpenOCD has been renamed to arm_adi_v5 and updated to remove all dependencies on Cortex-M3 specific features and as far as possible only use the ARM Debug Interface v5 features. The Cortex-M3 specifics has been moved to cortex_m3 module. This is a step in preparing OpenOCD for full Cortex-A8 support. <br />
<br />
Using recent OpenOCD versions, you can examine CoreSight APs: <br />
<br />
<pre><br />
> version <br />
Open On-Chip Debugger 0.3.0-in-development (2009-08-30-19:54) svn:2643M<br />
<br />
> omap3_dbginit<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> scan_chain<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> dap apsel 0<br />
ap 0 selected, identification register 0x14770001<br />
<br />
> dap info 0<br />
ap identification register 0x14770001<br />
Type is mem-ap AHB <br />
ap debugbase 0xffffffff <br />
No ROM table present <br />
<br />
> dap info 1<br />
ap identification register 0x04770002<br />
Type is mem-ap APB <br />
ap debugbase 0x80000000 <br />
ROM table in legacy format<br />
CID3 0xb1, CID2 0x5, CID1 0x10, CID0, 0xd<br />
MEMTYPE system memory not present. Dedicated debug bus<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21 <br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
ROMTABLE[0xc] = 0xd4013002 <br />
Component not present <br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
ROMTABLE[0x20] = 0x0<br />
End of ROM table<br />
<br />
> dap apsel 1<br />
ap 1 selected, identification register 0x04770002<br />
<br />
> dap apsel 2<br />
ap 2 selected, identification register 0x14760010<br />
<br />
> dap info 2<br />
ap identification register 0x14760010<br />
Type is jtag-ap<br />
ap debugbase 0x00000000<br />
No ROM table present<br />
<br />
> dap apsel 3<br />
ap 3 selected, identification register 0x00000000<br />
<br />
> dap info 3<br />
ap identification register 0x00000000<br />
No AP found at this apsel 0x3<br />
No ROM table present<br />
<br />
><br />
</pre><br />
<br />
==ROMTable==<br />
<br />
To interpret content of above ROMTable, have a look to<br />
<br />
* [http://www.ti.com/litv/pdf/spruf98b OMAP35x Technical Reference Manual (Rev. B)] (spruf98b.pdf, 39622 Kbytes), Table 5-105<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf CoreSight Components TRM] (ARM DDI 0314F), Table 2-3<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] (ARM DDI 0344H)<br />
<br />
With this, we get (first three entries are in the MPU SS Module, address range 0x54010000 - 0x54018000, part number is given by PID1[3-0] and PID0[7-0]):<br />
<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21<br />
<br />
* Part number is 0x921: ETM module. See [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] chapter 14.<br />
<br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
<br />
* Part number is 0xC08: This is the [[BeagleBoardOpenOCD#Debug_Register_Interface|Debug Register Interface]]. See table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].<br />
<br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
<br />
* Part number 0x113: This is ????<br />
<br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
<br />
* Part number 0x912: TPIU Module. <br />
<br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
<br />
* Part number 0x907: ETB Module.<br />
<br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
<br />
* Part number 0x343: DAP CTL Module.<br />
<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
<br />
* Part number 0x120: SDTI Module.<br />
<br />
==Debug Register Interface==<br />
<br />
With above info about debug register interface and table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] we are able to access this interface using OpenOCDs ''mdw'' command:<br />
<br />
> omap3.cpu mdw 0x54011000<br />
0x54011000 15141012<br />
<br />
This is the debug ID register. See table 12-11 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM]:<br />
<br />
{|border=1<br />
!Bits<br />
!Field<br />
!Value & Function<br />
|-<br />
|[31-28]<br />
|WRP<br />
|0x1 -> 2 WRPs are implemented<br />
|-<br />
|[27-24]<br />
|BRP<br />
|0x5 -> 6 BRPs are implemented<br />
|-<br />
|[23-20]<br />
|Context<br />
|0x1 -> 2 BRPs have context ID capability<br />
|-<br />
|[19-16]<br />
|Debug architecture version<br />
|0x4 -> ARMv7 debug<br />
|-<br />
|[12]<br />
|security<br />
|0x1 -> Security extensions implemented<br />
|-<br />
|[7-4]<br />
|variant<br />
|0x1<br />
|-<br />
|[3-0]<br />
|revision<br />
|0x2 <br />
|-<br />
|}<br />
<br />
> omap3.cpu mdw 0x54011FF0<br />
0x54011ff0 0000000d<br />
> omap3.cpu mdw 0x54011FF4<br />
0x54011ff4 00000090<br />
> omap3.cpu mdw 0x54011FF8<br />
0x54011ff8 00000005<br />
> omap3.cpu mdw 0x54011FFC<br />
0x54011ffc 000000b1<br />
<br />
These are the component identification registers. See table 12-51 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].</div>Dirkhttp://elinux.org/BeagleBoardOpenOCDBeagleBoardOpenOCD2010-04-02T09:05:28Z<p>Dirk: OpenOCD is uses git since some month</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
This page is about how to use open source [http://openocd.berlios.de/web/ OpenOCD] [http://en.wikipedia.org/wiki/JTAG JTAG] software with [[BeagleBoard|BeagleBoard]]. With this, it will be possible to have OMAP3 JTAG debug using cheap [[BeagleBoardJTAG|JTAG hardware]], e.g. [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]].<br />
<br />
'''As of September 2009, OpenOCD has basic support for OMAP3 and [[BeagleBoardOpenOCD#Cortex_A8_support|ARM Cortex A8]] on Beagle Board. Cortex A8 support is in early alpha stage, a lot is still missing. But e.g. processor halt, resume, step, breakpoints and ARM disassembly of non-Cache and non-MMU (e.g. U-Boot) applications seem to work.<br />
<br />
Status:<br />
<br />
* You need at least OpenOCD revision '''2770''' ([[BeagleBoardOpenOCD#Build_OpenOCD|using git]]). With this revision you will have basic access to OMAP3 and Cortex A8 can be basically controlled. This does mean, that OpenOCD is able to configure scan chain correctly to [[OMAP3530_ICEPICK#ICEPICK_infos|access ARM TAP]] ("JTAG controller"), explore CoreSight AccessPoints and halt, resume, step, breakpoints and ARM disassembly on Cortex A8.<br />
* Recent status as of '''September 2009''':<br />
** OpenOCD >= 2770 can and halt, resume, step, breakpoints and ARM disassembly Cortex A8 (ARM) processor on Beagle.<br />
** This works for non-MMU and non-Cache applications (e.g U-Boot).<br />
** [https://lists.berlios.de/pipermail/openocd-development/2009-August/010184.html Linux debugging doesn't work yet].<br />
<br />
<br />
=Hardware=<br />
<br />
To be able to use OpenOCD with OMAP3 based BeagleBoard, make sure that your JTAG Dongle supports:<br />
<br />
* 1.8V devices. Many JTAG dongles are 3.3V only! '''Verify that your dongle supports 1.8V!''' Else the dongle will overpowering the input to OMAP3 and may cause damage.<br />
* Your JTAG dongle is able to switch [[BeagleBoardJTAG#Beagle_JTAG_connection|EMU0 & EMU1 pins high]].<br />
<br />
Flyswatter dongle supports both requirements. If you use [http://tincantools.com/product.php?productid=16144 BeagleBoard Adapter Kit] with [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]], make sure you plug the JTAG adapter the correct way. There are several possible ways, though. See [http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 connection picture] how to do it the right way. In contrast to the picture EMU0 & EMU1 jumpers at JTAG adapter should be both at 1-2 position (touching J2).<br />
<br />
=Build OpenOCD=<br />
<br />
[http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD OpenOCD build instructions] describe how to build [http://openocd.berlios.de/web/ OpenOCD]. For questions you can use [https://lists.berlios.de/mailman/listinfo/openocd-development OpenOCD Mailing list].<br />
<br />
Get OpenOCD code via git:<br />
<br />
> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd<br />
<br />
For Flyswatter you additionally need [http://www.ftdichip.com/Drivers/D2XX.htm libftd2xx] or [http://www.intra2net.com/de/produkte/opensource/ftdi/ libFTDI]. While libFTDI is available in source, libftd2xx is supposed to be 50% [http://www.beagleboard.org/irclogs/index.php?date=2008-10-16#T16:06:22 faster] than libFTDI. The libtfd2xx binaries are available booth as shared library or linkable archive.<br />
<br />
If you downloaded OpenOCD svn and have libftd2xx or libFTDI, build OpenOCD (assuming you extracted/built FTDI library already):<br />
<br />
> cd openocd<br />
> ./bootstrap<br />
> ./configure --enable-ft2232_ftd2xx --with-ftd2xx-linux-tardir=<path_to>/libftd2xx0.4.16 --prefix=/home/user/bin/openOCD<br />
''or'' (depending which FTDI library you use, see above)<br />
> ./configure --enable-ft2232_libftdi --prefix=/home/user/bin/openOCD<br />
> make<br />
> make install<br />
<br />
When compiling the doc directory You get an error:<br />
openocd.texi:12: @include `version.texi': No such file or directory.<br />
It is possible to avoid by making version.texi. <br />
<br />
> cat doc/version.texi<br />
@set UPDATED 20 January 2009<br />
@set UPDATED-MONTH January 2009<br />
@set EDITION 0.1.0<br />
@set VERSION 0.1.0<br />
<br />
'''Note''': By default (make & make install) only .info documentation is installed. You can get PDF or HTML documentation by<br />
<br />
make pdf<br />
<br />
or<br />
<br />
make html<br />
<br />
Resulting documentation can be found in openocd/doc, then.<br />
<br />
'''Note''': If you like to save some disk space and don't plan to debug OpenOCD binary itself, you can strip this (remove unneeded debug symbols):<br />
<br />
> cd <openocd_install_dir>/bin<br />
> strip openocd<br />
<br />
(e.g. with OpenOCD 1.0 this reduced binary size from ~3MB to ~700kB)<br />
<br />
'''Note''': If you don't have libftdi in standard path, you might like to extend library search path:<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path_to>/lib<br />
<br />
if you e.g. get<br />
<br />
> ./openocd<br />
./openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory<br />
<br />
=Starting OpenOCD=<br />
<br />
OpenOCD runtime is controlled by several [http://openocd.berlios.de/doc/html/index.html#toc_Config-File-Guidelines configuration files]. OpenOCD comes with basic configuration files for BeagleBoard (''board/ti_beagleboard.cfg'') and OMAP3 (''target/omap3530.cfg'').<br />
<br />
Assuming that you use Flyswatter and it is switched on (attached to USB), you can now start OpenOCD with:<br />
<br />
openocd -s <path_to_config_files> // e.g. <path_of_openocd_install_dir>/lib/openocd<br />
-f <path_to_jtag_interface><br />
-f <path_to_beagle_config><br />
<br />
This should result in<br />
<br />
> '''openocd -s lib/openocd/ -f interface/flyswatter.cfg -f board/ti_beagleboard.cfg'''<br />
Open On-Chip Debugger 0.3.0-in-development (2009-09-29-16:28) svn:2770<br />
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $<br />
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS<br />
RCLK - adaptive <br />
Warn : huge IR length 38 <br />
Info : RCLK (adaptive clock speed) not supported - fallback to 6000 kHz<br />
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
<br />
This shows that your (Flyswatter) JTAG dongle basically works and that you are able to see OMAP3 JRC. OpenOCD now runs as deamon.<br />
<br />
=Controlling OpenOCD=<br />
<br />
Once OpenOCD runs as [http://openocd.berlios.de/doc/html/Running.html#Running daemon] like above, you can connect using ''telnet'' or ''GDB''<br />
<br />
==telnet==<br />
<br />
Connect to OpenOCD daemon. Assuming you do it on your local machine, open a second terminal window and do (assuming port 4444 as configured in above openocd.cfg):<br />
<br />
> '''telnet localhost 4444'''<br />
Trying 127.0.0.1...<br />
Connected to localhost.<br />
Escape character is '^]'.<br />
Open On-Chip Debugger<br />
> <br />
<br />
This should give you<br />
<br />
Info: accepting 'telnet' connection from 0<br />
<br />
in window where OpenOCD daemon is started.<br />
<br />
At OpenOCDs telnet prompt you can now issue OpenOCD commands. E.g. ''help'' should result in<br />
<br />
> '''help''' <br />
bp list or set breakpoint [<address> <length> [hw]]<br />
cpu <name> - prints out target options and a comment <br />
on CPU which matches name <br />
debug_level adjust debug level <0-3> <br />
drscan execute DR scan <device> <num_bits> <value> <br />
<num_bits1> <value2> ... <br />
dump_image dump_image <file> <address> <size> <br />
exit exit telnet session <br />
fast fast <enable/disable> - place at beginning of <br />
config files. Sets defaults to fast and dangerous.<br />
<br />
fast_load loads active fast load image to current target - <br />
mainly for profiling purposes <br />
fast_load_image same args as load_image, image stored in memory - <br />
mainly for profiling purposes <br />
find <file> - print full path to file according to <br />
OpenOCD search rules <br />
flush_count returns number of times the JTAG queue has been <br />
flushed <br />
ft2232_device_desc the USB device description of the FTDI FT2232 <br />
device <br />
ft2232_latency set the FT2232 latency timer to a new value <br />
ft2232_layout the layout of the FT2232 GPIO signals used to <br />
control output-enables and reset signals <br />
ft2232_serial the serial number of the FTDI FT2232 device <br />
ft2232_vid_pid the vendor ID and product ID of the FTDI FT2232 <br />
device <br />
gdb_breakpoint_override hard/soft/disable - force breakpoint type for gdb <br />
'break' commands. <br />
gdb_detach resume/reset/halt/nothing - specify behavior when <br />
GDB detaches from the target <br />
gdb_flash_program enable or disable flash program <br />
gdb_memory_map enable or disable memory map <br />
gdb_port daemon configuration command gdb_port <br />
gdb_report_data_abort enable or disable reporting data aborts <br />
halt halt target <br />
help Tcl implementation of help command <br />
init initializes target and servers - nop on subsequent <br />
invocations <br />
interface try to configure interface <br />
interface_list list all built-in interfaces <br />
irscan execute IR scan <device> <instr> [dev2] [instr2] <br />
... <br />
jtag perform jtag tap actions <br />
jtag_device (DEPRECATED) jtag_device <ir_length> <ir_expected> <br />
<ir_mask> <br />
jtag_khz set maximum jtag speed (if supported); parameter <br />
is maximum khz, or 0 for adaptive clocking (RTCK). <br />
<br />
jtag_nsrst_delay jtag_nsrst_delay <ms> - delay after deasserting <br />
srst in ms <br />
jtag_ntrst_delay jtag_ntrst_delay <ms> - delay after deasserting <br />
trst in ms <br />
jtag_rclk fallback_speed_khz - set JTAG speed to RCLK or use <br />
fallback speed <br />
jtag_reset toggle reset lines <trst> <srst> <br />
jtag_speed (DEPRECATED) set jtag speed (if supported) <br />
load_image load_image <file> <address> <br />
['bin'|'ihex'|'elf'|'s19'] [min_address] <br />
[max_length] <br />
log_output redirect logging to <file> (default: stderr) <br />
mdb display memory bytes <addr> [count] <br />
mdh display memory half-words <addr> [count] <br />
mdw display memory words <addr> [count] <br />
mwb write memory byte <addr> <value> [count] <br />
mwh write memory half-word <addr> <value> [count] <br />
mww write memory word <addr> <value> [count] <br />
ocd_array2mem convert a TCL array to memory locations and write <br />
the values <ARRAYNAME> <WIDTH = 32/16/8> <br />
<ADDRESS> <COUNT> <br />
ocd_flash_banks return information about the flash banks <br />
ocd_mem2array read memory and return as a TCL array for script <br />
processing <ARRAYNAME> <WIDTH = 32/16/8> <ADDRESS> <br />
<COUNT> <br />
pathmove move JTAG to state1 then to state2, state3, etc. <br />
<state1>,<state2>,<stat3>... <br />
poll poll target state <br />
power_restore Overridable procedure run when power restore is <br />
detected. Runs 'reset init' by default. <br />
production <serialnumber> - Runs production procedure. Throws <br />
exception if procedure failed. Prints progress <br />
messages. Implement this procedure in the target <br />
script. <br />
production Runs test procedure. Throws exception if procedure <br />
failed. Prints progress messages. Implement in <br />
target script. <br />
production_info Displays information on production procedure for <br />
target script. Implement this procedure in target <br />
script. <br />
profile profiling samples the CPU PC <br />
rbp remove breakpoint <address> <br />
reg display or set a register <br />
reset reset target [run | halt | init] - default is run <br />
reset_config [none/trst_only/srst_only/trst_and_srst] <br />
[srst_pulls_trst/trst_pulls_srst] <br />
[combined/separate] <br />
[trst_push_pull/trst_open_drain] <br />
[srst_push_pull/srst_open_drain] <br />
resume resume target [addr] <br />
runtest move to Run-Test/Idle, and execute <num_cycles> <br />
rwp remove watchpoint <address> <br />
scan_chain print current scan chain configuration <br />
script <filename> - filename of OpenOCD script (tcl) to <br />
run <br />
shutdown shut the server down <br />
sleep <n> [busy] - sleep for n milliseconds. "busy" <br />
means busy wait <br />
soft_reset_halt halt the target and do a soft reset <br />
srst_deasserted Overridable procedure run when srst deassert is <br />
detected. Runs 'reset init' by default. <br />
step step one instruction from current PC or [addr] <br />
svf run svf <file> <br />
target configure target <br />
targets change the current command line target (one <br />
parameter) or lists targets (with no parameter) <br />
tcl_port port on which to listen for incoming TCL syntax <br />
telnet_port port on which to listen for incoming telnet <br />
connections <br />
test_image test_image <file> [offset] [type] <br />
tms_sequence choose short(default) or long tms_sequence <short <br />
| long> <br />
verify_image verify_image <file> [offset] [type] <br />
verify_ircapture verify value captured during Capture-IR <enable |<br />
disable><br />
verify_jtag verify value capture <enable | disable><br />
version show OpenOCD version<br />
virt2phys translate a virtual address into a physical<br />
address<br />
wait_halt wait for target halt [time (s)]<br />
wp list or set watchpoint [<address> <length> <r/w/a><br />
[value] [mask]]<br />
xsvf run xsvf <file> [virt2] [quiet]<br />
armv4_5 core_state display/change ARM core state <arm | thumb><br />
armv4_5 disassemble disassemble instructions <address> [<count><br />
['thumb']]<br />
armv4_5 reg display ARM core registers<br />
cortex_a8 cache_info display information about target caches<br />
dap apid return id reg from AP [num], default currently<br />
selected AP<br />
dap apsel select a different AP [num] (default 0)<br />
dap baseaddr return debug base address from AP [num], default<br />
currently selected AP<br />
dap info dap info for ap [num], default currently selected<br />
AP<br />
dap memaccess set/get number of extra tck for mem-ap memory bus<br />
access [0-255]<br />
flash bank flash bank <driver> <base> <size> <chip_width><br />
<bus_width> <target> [driver_options ...]<br />
mflash bank mflash bank <soc> <base> <RST pin> <target #><br />
nand device<br />
pld device<br />
target_request debugmsgs enable/disable reception of debug messages from<br />
target<br />
trace history display trace history, ['clear'] history or set<br />
[size]<br />
trace point display trace points, ['clear'] list of trace<br />
points, or add new tracepoint at [address]<br />
<br />
==Example session==<br />
<br />
Now, we can try to basically halt and resume OMAP3 (assuming U-Boot is running at U-Boot's prompt):<br />
<br />
> '''omap3_dbginit'''<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> '''scan_chain'''<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> '''halt'''<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e87dcc<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''resume'''<br />
<br />
> '''poll'''<br />
background polling: on<br />
TAP: omap3530.dap (enabled)<br />
target state: running<br />
<br />
> '''soft_reset_halt'''<br />
requesting target halt and executing a soft reset<br />
Target omap3.cpu does not support soft_reset_halt<br />
<br />
> '''cortex_a8 cache_info'''<br />
cache type: 0x0, unified cache<br />
D-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
I-Cache: linelen 8, associativity 2, nsets 64, cachesize 0x400<br />
<br />
> '''halt''' <br />
target state: halted <br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88158<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''armv4_5 disassemble 0x80e88158 10'''<br />
0x80e88158 0xe3130001 TST r3, #0x1<br />
0x80e8815c 0x0afffffc BEQ 0x80e88154<br />
0x80e88160 0xe5d00000 LDRB r0, [r0]<br />
0x80e88164 0xe12fff1e BX r14<br />
0x80e88168 0xe5d00014 LDRB r0, [r0, #0x14]<br />
0x80e8816c 0xe2000001 AND r0, r0, #0x1<br />
0x80e88170 0xe12fff1e BX r14<br />
0x80e88174 0xe1a02001 MOV r2, r1<br />
0x80e88178 0xe1a01000 MOV r1, r0<br />
0x80e8817c 0xe59f0000 LDR r0, [r15]<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e8815c<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''step'''<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x400001d3 pc: 0x80e88154<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp 0x80e88160 4 hw'''<br />
breakpoint set at 0x80e88160<br />
<br />
> '''resume'''<br />
<br />
''... type anything in U-Boot until breakpoint is hit ...''<br />
<br />
target state: halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
spsr_svc: 0x000001d3 pc: 0x80e88160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
<br />
> '''bp'''<br />
0x80e88160, 0x4, 1<br />
<br />
> '''rbp 0x80e88160'''<br />
<br />
> '''resume'''<br />
<br />
=GDB ARM=<br />
<br />
To [[DebuggingTheLinuxKernelUsingGdb|debug]] an ARM target with GNU debugger ([[GDB|GDB]]), you need a GDB understanding ARM processor. If your ARM cross compilation tool chain doesn't include a GDB, you can easily build it your self.<br />
<br />
==Build==<br />
<br />
* Download latest [http://www.gnu.org/software/gdb/download/ GDB sources]. [http://openocd.berlios.de/doc/GDB-and-OpenOCD.html#GDB-and-OpenOCD OpenOCD docu] recommends to use GDB 6.7 or newer. Here, we use GDB 6.8 which is the recent version while writing this.<br />
<br />
* Extract, configure and build GDB for ARM. Afterwards remove temporary stuff. Options are:<br />
** <path_where_ARM_gdb_shall_be_installed_to> : Directory where you want to install the resulting tool to. E.g. /home/user/arm-gdb/<br />
** <ARM_toolchain_prefix> : The prefix of your ARM GCC toolchain, e.g. ''arm-linux'' or ''arm-none-linux-gnueabi'' ([[BeagleBoard#Cortex_A8_ARM|CodeSourcery tool chain]]).<br />
<br />
> tar xfj gdb-6.8.tar.bz2<br />
> mkdir build-gdb<br />
> cd build-gdb/<br />
build-gdb > ../gdb-6.8/configure --prefix=<path_where_ARM_gdb_shall_be_installed_to> --target=<ARM_toolchain_prefix> i686-pc-linux-gnu<br />
build-gdb > make -j4<br />
build-gdb > make install<br />
build-gdb > cd ..<br />
> rm -rf gdb-6.8 build-gdb<br />
> export PATH=$PATH:<path_where_ARM_gdb_shall_be_installed_to>/bin<br />
<br />
Test:<br />
<br />
bin> ./arm-none-linux-gnueabi-gdb<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
(gdb)<br />
<br />
==Example session==<br />
<br />
To use gdb, you have to connect to running OpenOCD using remote command. E.g.:<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
<br />
(gdb) '''target remote localhost:3333'''<br />
Remote debugging using localhost:3333<br />
0x00000000 in ?? () <br />
(gdb) '''monitor omap3_dbginit''' <br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080 <br />
SWJ-DP STICKY ERROR <br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080 <br />
TargetName Type Endian TapName State <br />
-- ------------------ ---------- ------ ------------------ ------------ <br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown <br />
0x54011314 00000003 .... <br />
0x54011314 00000001 .... <br />
<br />
(gdb) '''monitor scan_chain''' <br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr <br />
---|--------------------|---------|------------|------------|------|------|------|--------- <br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a <br />
2 | omap3530.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
(gdb) '''info registers'''<br />
r0 0x0 0<br />
r1 0x60a 1546<br />
r2 0x80000100 2147483904<br />
r3 0x706 1798 <br />
r4 0xc00081b8 3221258680<br />
r5 0x0 0 <br />
r6 0x80026960 2147641696<br />
r7 0xc00081b8 3221258680<br />
r8 0x0 0 <br />
r9 0x411fc082 1092599938<br />
r10 0x800268f8 2147641592<br />
r11 0xf731c8f9 4147235065<br />
r12 0x80796ae0 2155440864<br />
sp 0x8051a900 0x8051a900<br />
lr 0x80008018 2147516440<br />
pc 0x8000815c 0x8000815c<br />
fps 0x0 0 <br />
cpsr 0x0 0 <br />
<br />
(gdb) '''p/x $pc''' <br />
$2 = 0x8000815c <br />
<br />
(gdb) '''x/i $pc''' <br />
0x8000815c: nop (mov r0,r0)<br />
<br />
(gdb) '''x'''<br />
0x80008160: b 0x8000815c<br />
<br />
==LED blink example==<br />
<br />
Magnus Lundin has a simple standalone LED blink test program which can be used for tests.<br />
<br />
* [http://github.com/mlu/cortal_dendrites/tree/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink LED blink] test program.<br />
* [http://github.com/mlu/cortal_dendrites/blob/6ed04b7e838981f594eb6b701a17c220fff952dd/cortex_a8/standalone/LEDblink/README README]<br />
* Example .gdbinit file:<br />
<br />
echo *** Executing .gdbint to set up the environment for debugging gdb:\n<br />
<br />
# This connects to OpenOcd at localhost:3333<br />
target remote localhost:3333<br />
<br />
# omap3_dbginit must be run in OpenOCD after every reset<br />
monitor omap3_dbginit<br />
<br />
# Stop core<br />
monitor halt<br />
<br />
echo *** Environment ready, now load and start executeable:\n<br />
<br />
# Load the program executable called "LEDblink"<br />
load LEDblink<br />
<br />
# Load the symbols for the program.<br />
symbol-file LEDblink<br />
<br />
# Set a breakpoint at main().<br />
b main<br />
<br />
# Run to the breakpoint.<br />
cont<br />
<br />
Clone the code by git, goto ''cortex_a8/standalone/LEDblink'' directory, build the example using provided Makefile and then in that directory start gdb (so that above .gdbinit is executed):<br />
<br />
> '''arm-none-linux-gnueabi-gdb'''<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi".<br />
*** Executing .gdbint to set up the environment for debugging gdb:<br />
0x00000000 in ?? ()<br />
The target may not be able to correctly handle a memory-write-packet-size<br />
of 1024 bytes. Change the packet size? (y or n) [answered Y; input not from terminal]<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
target state: halted<br />
target halted in ARM state due to debug-request, current mode: Supervisor<br />
spsr_svc: 0x600001d3 pc: 0x80008160<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
*** Environment ready, now load and start executeable:<br />
Loading section .text, size 0xe0 lma 0x82000000<br />
Start address 0x82000000, load size 224<br />
Transfer rate: 4 KB/sec, 224 bytes/write.<br />
Current language: auto; currently asm<br />
Breakpoint 1 at 0x8200003c: file LEDblink.c, line 22.<br />
<br />
Breakpoint 1, main () at LEDblink.c:22<br />
22 LEDbrightness++;<br />
Current language: auto; currently c<br />
<br />
(gdb) '''cont'''<br />
<br />
This should let Beagle's LEDs blink.<br />
<br />
=Development internals=<br />
<br />
The sections below give some datails if you are interested in developing OpenOCD for OMAP3 and Cortex A8 used on Beagle. If you like to help to improve OpenOCD support for Beagle, this might help you.<br />
<br />
==Introduction==<br />
<br />
Magnus Lundin wrote a very nice [http://arttools.blogspot.com/2009/09/debugging-on-cortex-a8-system.html introduction] on the basic Cortex A8 (OMAP3) debug architecture.<br />
<br />
==Cortex A8 support==<br />
<br />
As mentioned above, OpenOCD has initial experimental Cortex A8 support. Rick Altherr wrote (thanks!) a [https://lists.berlios.de/pipermail/openocd-development/2009-April/005273.html nice intro] how to help with Cortex A8 support for OpenOCD:<br />
<br />
''The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_m3.c Cortex-M3 support] is very similar to Cortex-A8 up to a certain layer. The ARM debug interface is designed as a set of layers that build on each other and can do automatic discovery. The [http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/cortex_swjdp.c cortex-swjdp] support in OpenOCD is a good start, but it assumes which AHB and APB ports are available. The first item would be to verify the cortex-swjdp portion against the documents for the CoreSight debug interface.''<br />
<br />
''To really get started, familiarize yourself with the following docs:''<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0031a/index.html ARM IHI 0031A] (ARM Debug Interface v5)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ihi0029b/index.html ARM IHI 0029B] (CoreSight v1.0)'' - only available to registered ARM customers<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0316d/DDI0316D_dap_lite_trm.pdf ARM DDI 0316D] (CoreSight DAP-Lite)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf ARM DDI 0314F] (CoreSight Components TRM)''<br />
* ''[http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf ARM DDI 0344H] (Cortex-A8 TRM, primarily chapter 12)''<br />
<br />
''These should be listed in the right order for getting up to speed. Basically the Cortex-A8 debug registers are accessed externally via CoreSight. CoreSight is an implementation of the ARM Debug Interface v5.''<br />
<br />
''The cortex-swjdp implementation in OpenOCD deals with CoreSight but makes some assumptions about which CoreSight components are available. For Cortex-A8, that will likely need to change a bit as the set of components will be different.''<br />
<br />
''After cortex-swjdp is patched to handle the new components, a cortex-a8 target implementation can be started by using the cortex-swjdp layer to access the various debug registers and memory locations.''<br />
<br />
For discussion about this, see [https://lists.berlios.de/pipermail/openocd-development/2009-March/005097.html mail #1], [https://lists.berlios.de/pipermail/openocd-development/2009-March/005099.html mail #2] and [https://lists.berlios.de/pipermail/openocd-development/2009-March/005117.html mail #3].<br />
<br />
Note: With revision ~1570 the cortex-swjdp module in OpenOCD has been renamed to arm_adi_v5 and updated to remove all dependencies on Cortex-M3 specific features and as far as possible only use the ARM Debug Interface v5 features. The Cortex-M3 specifics has been moved to cortex_m3 module. This is a step in preparing OpenOCD for full Cortex-A8 support. <br />
<br />
Using recent OpenOCD versions, you can examine CoreSight APs: <br />
<br />
<pre><br />
> version <br />
Open On-Chip Debugger 0.3.0-in-development (2009-08-30-19:54) svn:2643M<br />
<br />
> omap3_dbginit<br />
JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part: 0xb7ae, ver: 0x0)<br />
JTAG Tap/device matched<br />
AHBAP Cached values: dp_select 0x10, ap_csw 0xa2000002, ap_tar 0x54011080<br />
SWJ-DP STICKY ERROR<br />
Read MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011080<br />
TargetName Type Endian TapName State<br />
-- ------------------ ---------- ------ ------------------ ------------<br />
0* omap3.cpu cortex_a8 little omap3530.dap unknown<br />
0x54011314 00000003 ....<br />
0x54011314 00000001 ....<br />
<br />
> scan_chain<br />
TapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr<br />
---|--------------------|---------|------------|------------|------|------|------|---------<br />
0 | omap3530.dsp | n | 0x00000000 | 0x00000000 | 0x26 | 0x25 | 0x3f | 0xffffffff<br />
1 | omap3530.dap | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x0f | 0x0a<br />
2 | omap3530.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 | 0x01 | 0x3f | 0x3f<br />
<br />
> dap apsel 0<br />
ap 0 selected, identification register 0x14770001<br />
<br />
> dap info 0<br />
ap identification register 0x14770001<br />
Type is mem-ap AHB <br />
ap debugbase 0xffffffff <br />
No ROM table present <br />
<br />
> dap info 1<br />
ap identification register 0x04770002<br />
Type is mem-ap APB <br />
ap debugbase 0x80000000 <br />
ROM table in legacy format<br />
CID3 0xb1, CID2 0x5, CID1 0x10, CID0, 0xd<br />
MEMTYPE system memory not present. Dedicated debug bus<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21 <br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
ROMTABLE[0xc] = 0xd4013002 <br />
Component not present <br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
ROMTABLE[0x20] = 0x0<br />
End of ROM table<br />
<br />
> dap apsel 1<br />
ap 1 selected, identification register 0x04770002<br />
<br />
> dap apsel 2<br />
ap 2 selected, identification register 0x14760010<br />
<br />
> dap info 2<br />
ap identification register 0x14760010<br />
Type is jtag-ap<br />
ap debugbase 0x00000000<br />
No ROM table present<br />
<br />
> dap apsel 3<br />
ap 3 selected, identification register 0x00000000<br />
<br />
> dap info 3<br />
ap identification register 0x00000000<br />
No AP found at this apsel 0x3<br />
No ROM table present<br />
<br />
><br />
</pre><br />
<br />
==ROMTable==<br />
<br />
To interpret content of above ROMTable, have a look to<br />
<br />
* [http://www.ti.com/litv/pdf/spruf98b OMAP35x Technical Reference Manual (Rev. B)] (spruf98b.pdf, 39622 Kbytes), Table 5-105<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0314f/DDI0314F_coresight_component_trm.pdf CoreSight Components TRM] (ARM DDI 0314F), Table 2-3<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] (ARM DDI 0344H)<br />
<br />
With this, we get (first three entries are in the MPU SS Module, address range 0x54010000 - 0x54018000, part number is given by PID1[3-0] and PID0[7-0]):<br />
<br />
ROMTABLE[0x0] = 0xd4010003 <br />
Component base address 0x54010000, pid4 0x4, start address 0x54010000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21<br />
<br />
* Part number is 0x921: ETM module. See [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] chapter 14.<br />
<br />
ROMTABLE[0x4] = 0xd4011003 <br />
Component base address 0x54011000, pid4 0x4, start address 0x54011000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8 <br />
<br />
* Part number is 0xC08: This is the [[BeagleBoardOpenOCD#Debug_Register_Interface|Debug Register Interface]]. See table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].<br />
<br />
ROMTABLE[0x8] = 0xd4012003 <br />
Component base address 0x54012000, pid4 0x0, start address 0x54012000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13 <br />
<br />
* Part number 0x113: This is ????<br />
<br />
ROMTABLE[0x10] = 0xd4019003 <br />
Component base address 0x54019000, pid4 0x4, start address 0x54019000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12 <br />
<br />
* Part number 0x912: TPIU Module. <br />
<br />
ROMTABLE[0x14] = 0xd401b003 <br />
Component base address 0x5401b000, pid4 0x4, start address 0x5401b000<br />
Component cid1 0x90, class is CoreSight component <br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd <br />
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7 <br />
<br />
* Part number 0x907: ETB Module.<br />
<br />
ROMTABLE[0x18] = 0xd401d003 <br />
Component base address 0x5401d000, pid4 0x0, start address 0x5401d000<br />
Component cid1 0xf0, class is Non standard layout<br />
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd<br />
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43<br />
<br />
* Part number 0x343: DAP CTL Module.<br />
<br />
ROMTABLE[0x1c] = 0xd4500003<br />
Component base address 0x54500000, pid4 0x0, start address 0x54500000<br />
Component cid1 0x90, class is CoreSight component<br />
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd<br />
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20<br />
<br />
* Part number 0x120: SDTI Module.<br />
<br />
==Debug Register Interface==<br />
<br />
With above info about debug register interface and table 12-3 in the [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM] we are able to access this interface using OpenOCDs ''mdw'' command:<br />
<br />
> omap3.cpu mdw 0x54011000<br />
0x54011000 15141012<br />
<br />
This is the debug ID register. See table 12-11 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM]:<br />
<br />
{|border=1<br />
!Bits<br />
!Field<br />
!Value & Function<br />
|-<br />
|[31-28]<br />
|WRP<br />
|0x1 -> 2 WRPs are implemented<br />
|-<br />
|[27-24]<br />
|BRP<br />
|0x5 -> 6 BRPs are implemented<br />
|-<br />
|[23-20]<br />
|Context<br />
|0x1 -> 2 BRPs have context ID capability<br />
|-<br />
|[19-16]<br />
|Debug architecture version<br />
|0x4 -> ARMv7 debug<br />
|-<br />
|[12]<br />
|security<br />
|0x1 -> Security extensions implemented<br />
|-<br />
|[7-4]<br />
|variant<br />
|0x1<br />
|-<br />
|[3-0]<br />
|revision<br />
|0x2 <br />
|-<br />
|}<br />
<br />
> omap3.cpu mdw 0x54011FF0<br />
0x54011ff0 0000000d<br />
> omap3.cpu mdw 0x54011FF4<br />
0x54011ff4 00000090<br />
> omap3.cpu mdw 0x54011FF8<br />
0x54011ff8 00000005<br />
> omap3.cpu mdw 0x54011FFC<br />
0x54011ffc 000000b1<br />
<br />
These are the component identification registers. See table 12-51 of [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344h/DDI0344H_cortex_a8_r3p0_trm.pdf Cortex-A8 TRM].</div>Dirkhttp://elinux.org/BeagleBoard/contestBeagleBoard/contest2010-01-21T16:26:44Z<p>Dirk: Vote</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Image:beagle_first_place.png|thumb|right]]<br />
==Contest Announcements==<br />
===Sponsored Project Program===<br />
The [[BeagleBoard]] Software Design Contest has now been replaced with the [[BeagleBoard/contest#Contest_projects| BeagleBoard Sponsored Projects Program]] (formerly known as contest #3). The biggest difference is that we'll be giving 2 boards per week to projects as they are '''[[BeagleBoard/contest#Approved_projects|approved]]''', rather than waiting until they are completed. Also, successfully completed projects may be rewarded with higher-end BeagleBoard-derived systems, such as a [http://gumstix.com/store/catalog/product_info.php?products_id=229 Gumstix Palo43] or a [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book] (BeagleBoard based). You are encouraged to make your entries [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|now]].<br />
<br />
If your project is listed as a winner and you haven't received your board, check with ''beagleship at list.ti.com''.<br />
<br />
===Contest #2===<br />
<br />
''Contest #2 is finished. See [[BeagleBoard/contest#Winners_2|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html contest #2]. This contest is about giving away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to the winner and another one to the runner-up. [[BeagleBoard/contest#Judges|Judges]] will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, February 27, 2009 (afternoon) <br />
* '''Voting goes over weekend, end: Sunday, March 1, 2009 (afternoon)'''<br />
* Shipping board to winner: Monday, March 2, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get before this revision is publically available by DigiKey (~end of March 2009).<br />
</font><br />
<br />
===Contest #1===<br />
<br />
''Contest #1 is finished. See [[BeagleBoard/contest#Winners|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, January 9, 2009 (afternoon) <br />
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)<br />
* Shipping board to winner: Monday, January 12, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).<br />
</font><br />
<br />
==Project ideas==<br />
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:<br />
* Stable musb<br />
** ISOCH support<br />
** High-speed USB TV tuner support<br />
** Hot-plug support for OTG (host and client)<br />
* USB Digital TV tuner (either ATSC or DVB-T)<br />
** Hauppauge HVR950 suggested as reference<br />
* Projection TV coupled with the Pico<br />
* Audio record<br />
* Latest kernel version<br />
* USB camera support<br />
** gspca driver - need to validate with multiple cameras<br />
** <font color="#C0C0C0">UVC driver (I understood from Koen this is working)</font><br />
* Fixing bugs listed on code.google.com<br />
* Android port and various applications<br />
* <font color="#C0C0C0">EHCI support (done)</font><br />
* <font color="#C0C0C0">USB support in u-boot (partially done by first contest, but still needs work)</font><br />
* <font color="#C0C0C0">Consumer IR remote control via LIRC (already in feed; do 'opkg lirc')</font><br />
<br />
See also [[BeagleBoard/Ideas-2009]] for more ideas.<br />
<br />
==Contest projects==<br />
Please add your project you like to participate at Sponsored Projects Program (contest #3) to [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|Sponsored Projects Program projects]]. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1.1").<br />
<br />
===Sponsored Projects Program (Contest #3) projects===<br />
<br />
If you like to join Sponsored Projects Program (contest #3), please add your project here the same way like done for contest #1 and #2 below. If you participated already previous contests, please copy your project description to this contest, again. This will let everybody know that the project is still alive and that you want to participate Sponsored Projects Program.<br />
<br />
====Approved projects====<br />
From the project proposals, [[BeagleBoard/contest#Sponsored_Project_Program|approved projects]] will get a BeagleBoard Rev C at the '''beginning''' of their project to help them execute:<br />
<br />
{|border=1<br />
!Project<br />
!Approved<br />
!Comment<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Gregoire<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Revolt 2405|Revolt 2405]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Gentoo Linux ARMv7 support|Gentoo Linux ARMv7 support]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Accelerated_USB_Graphics_Adapter|Accelerated USB Graphics Adapter]]</font><br />
|<font color="#C0C0C0">Week 21</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#picoFlamingo|picoFlamingo]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle Synth |Beagle Synth]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#USB Scope |USB Scope]]</font><br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Irrlicht|Irrlicht]]<br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleHam|BeagleHam]]</font><br />
|<font color="#C0C0C0">Week 24</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Apertus_open_source.2Fhardware_cinema_camera|Apertus Digital Cinema Camera ]]<br />
|<font color="#C0C0C0">Week 25</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Handheld_Lab|Handheld Lab]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TCF_Agent_Port|TCF Agent Port]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Traveler|Beagle-Traveler]]</font><br />
|<font color="#C0C0C0">Week 27</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#OMAP Emulator|OMAP Emulator]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TUD:OS_on_Beagleboard|TUD:OS on Beagleboard]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#QEMUonARM|QEMUonARM]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#EGLIBC|EGLIBC Support]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#RT-Beagle|RT-Beagle]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ONAS|ONAS]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Math-NEON|Math-NEON]]<br />
|<font color="#C0C0C0">Week 32<br />
|<font color="#C0C0C0">5 votes<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Happiness_Device_for_Cerebral_Palsy_Kids|Device for Cerebral Palsy Kids]]</font><br />
|<font color="#C0C0C0">Week 32</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Turk|Turk Platform]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#hApplause|hApplause]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#eLazarillo|eLazarillo]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">1 vote</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#PREEMPT_RT|PREEMPT_RT]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#HDDM|HDDM]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleVision|BeagleVision]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#DJ Audio / Video Mixer|DJ Audio / Video Mixer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#schooldog|An individual lowcost schoolcomputer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Disko|Disko - UI Application Framework]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ESITeam|ESITeam]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#DVB-T_Receiver|DVB-T_Receiver]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">8 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#UPnP.2FDLNA_AV_client_renderer_and_transcoding_server|UPnP/DLNA AV client renderer and transcoding server]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Speed-Reader|Speed-Reader]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Arduino_hybrid_robot|Beagle-Arduino hybrid robot]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#XBMC_ARM_Port|XBMC Arm Port]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#GuideBeagle:_Portable_monocular_SLAM_system|Portable monocular SLAM system]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#MythBeagle|MythBeagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeaglePod|BeaglePod]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle_SecMon|Beagle SecMon]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Touchscreen_LCD_support| Touchscreen LCD support]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FMframe |FMframe]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleSCI |BeagleSCI]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Pictouch|Pictouch]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Fotogenic |Fotogenic]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyGTee|MyGTee handheld]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Tourister_using_Hand_Gestures_and_HMD_on_Beagleboard|Beagle Tourister]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Medical Notebook|Medical Notebook]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#miniECG|miniECG]]<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#remoteBillBoard|Remote Bill Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleWacom|Wacom Tablet driver for Beagle Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleLAB|BeagleLAB]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FETCH|FETCH]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#PupLC|PupLC]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#ArchMobile:_ArchLinux_ARM_Port|ArchMobile]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Homebrew_SmartPhone|Homebrew SmartPhone]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagleboard_Carputer|Beagleboard Carputer]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#AutoRobo|AutoRobo]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Walker|Beagle-Walker]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyoVox|MyoVox]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Eye|Beagle-Eye]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MART|MART]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#CamCast|CamCast]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#PortablePlateRec|PortablePlateRec]]<br />
|<br />
|<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Digital_Multimedia_Frame|Digital Multimedia frame]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#.28Speech.29_Scrambler_Beagle| (Speech) Scrambler Beagle]]<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Utility|Beagle Utility]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
Rule: In each week, each judge has two points (two "1") to enter for his favorite project. The two projects with the most votes will be approved. The plan is to have final decision every Friday morning.<br />
<br />
==== Revolt 2405====<br />
<font color="#C0C0C0"><br />
* '''Title''': Revolt 2405<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Revolt2405/<br />
* '''Short project description''': First mission of a first person shooter style game using Ogre3D.<br />
* '''Homepage''': http://www.dcbcyber.com/revolt2405/wordpress<br />
* '''Expected results''': Expected results would be to have a playable game demo using Ogre3D for rendering. There will be sound and music. For controls I want to have the option of using keyboard and mouse or using controls like those found on hand held gaming devices. We would also like to have this playable on a small LCD as well as on a monitor connected to the DVI port.<br />
* '''Contact''': n2vdy at yahoo dot com or dbatzle at dcbcyber dot com<br />
</font><br />
==== Touchscreen LCD support ====<br />
<br />
* '''Title''': Touchscreen LCD support <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': The project will add the touch screen support to Beagle board<br />
The following are the components that i am planning of using<br />
:*The LCD breakout board is http://www.sparkfun.com/commerce/product_info.php?products_id=8600<br />
:*The touch screen is http://www.sparkfun.com/commerce/product_info.php?products_id=8977<br />
:*The touch screen connector is http://www.sparkfun.com/commerce/product_info.php?products_id=9104<br />
<br />
Another option is buying a full LCD with touch screen option<br />
:*The product link is http://www.sparkfun.com/commerce/product_info.php?products_id=257.<br />
:*I would create a system and hardware like this video http://www.youtube.com/watch?v=foWnDZ3eQto&feature=related<br />
<br />
* '''Homepage''': http://pradheeptce.googlepages.com/ yet to be fully completed.<br />
<br />
* '''Expected results''': <br />
**Linux driver to add LCD with touch screen support<br />
**The breakout board(preferably single layered as it can be created at home)gerber for attaching with beagle which will be created using FreePcb(www.freepcb.com).You can see the photos of my RFID Based Access Control system project there.<br />
**Wiki page to describe the entire development method<br />
* '''Contact''': pradheep_sh[at]tce[.]edu<br />
<br />
==== Gentoo Linux ARMv7 support ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Official Gentoo Linux ARMv7 support<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Gentoo/<br />
* '''Short project description''': Build ARMv7 optimized packages and stages for Gentoo Linux created officially by Gentoo developers.<br />
* '''Description''': The project is for providing official support for ARMv7-based devices like the Beagleboard, we will provide stages and packages optimized for ARMv7 processors so any owner of an ARMv7 device can get an optimized system. At the moment Gentoo only provides and supports ARMv4 and ARMv5TE, therefore we would like to expand our official support to the more powerful ARMv7 subarchitecture.<br />
* '''Homepage''': http://www.gentoo.org/proj/en/base/embedded/ http://www.gentoo.org/doc/en/handbook/handbook-arm.xml http://www.gentoo.org/proj/en/base/embedded/handbook/<br />
* '''Expected results''': <br />
**Allow Gentoo users to have ARMv7 optimized stages and packages.<br />
**Document the installation on the provided boards.<br />
* '''Contact''': armin76[at]gentoo[.]org , solar[at]gentoo[.]org<br />
</font><br />
==== TUD:OS on Beagleboard ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TUD:OS on Beagleboard <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/TUD%3AOS+on+the+Beagleboard/]<br />
* '''Short project description''': Port the L4-Microkernel based TUD:OS Operating System to the Beagleboard<br />
* '''Homepage''': will follow<br />
* '''Description''': <br />
** '''What the heck?''' The TUD:OS operating system is a L4 microkernel based operating system, with good real-time and security properties, developed at the TU Dresden. <br />
** '''Microkernel-based''': The microkernel approach allows it to to reduce the trusted computing base (the amount of code that has to be trusted) by running small trusted applications side by side with non-trusted applications, all as unprivileged user mode applications. Further, it is possible to run real-time applications side-by side with non real-time applications. Also device driver run in user-mode and thus a crash of a device driver will not lead to an whole system crash and in the best case the driver can be restarted and the system will keep on running.<br />
** '''Familiar Environment''': While offering the above mentioned vantages, TUD:OS still offers a familiar environment by the possibility to run one or more instances of L4Linux. L4Linux is a Linux port the Fiasco microkernel which is binary compatible to native Linux but runs in deprivilieged usermode.<br />
** '''What do we get from this project?''' ''Briefly: A fundament to build embedded [realtime] systems [with a exceptionally small trusted computing base].'' Further a possibility to run multiple virtualized linux instances on the beagleboard. A good documentation how to build such systems. And last but not least a (hopefully cool ;) demo showing that it acutally works , perhaps like the one found at [http://demo.tudos.org demo.tudos.org] (somewhat outdated). <br />
*'''Contact:''' dvogt[at]os[.]inf[.]tu-dresden[.]de ([[User:Dvogt|Dvogt]])<br />
</font><br />
==== picoFlamingo ====<br />
<font color="#C0C0C0"><br />
* '''Title''': picoFlamingo <br />
* '''beagleboard.org project''': http://beagleboard.org/project/picoFlamingo/<br />
* '''Short project description''': A portable presentation system for the BeagleBoard and the picoDLP projector<br />
* '''Homepage''': http://papermint-designs.com/picoflamingo<br />
* '''Expected results''': <br />
** An application to perform presentations including 3D elements.<br />
** A basic hardware specification for a portable presentation system.<br />
** A remote interface for wireless control of the presentation.<br />
** A demonstration of the possibilities provided by the BeagleBoard, the OMAP 3 platform and the picoDLP.<br />
** Hopefully a lightweight 3D render engine for OpenGL ES 2.0.<br />
** A lot of fun!!!... <br />
* '''Contact''': dmo[at]papermint-designs[.]com<br />
</font><br />
==== Accelerated USB Graphics Adapter ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Accelerated USB Graphics Adapter <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': USB-attached Graphics Card supporting OpenGL acceleration for XFree86<br />
* '''Homepage''': http://www.employees.org/~mschulma/beagleboard/cerberus/<br />
* '''Expected results''': <br />
** Use the Beagleboard to attach another monitor to a PC running Linux, and run a graphics intensive application on the expanded virtual desktop without slowing the main CPU.<br />
* '''Contact''': mschulma [at] employees [dot ] org<br />
</font><br />
==== Apertus open source/hardware cinema camera ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Apertus Digital Cinema Camera<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Apertus/<br />
* '''Short project description''': A digital camera controler for an Elphel open hardware camera. The beagle board will be used as a realtime viewfinder unit and hardware camera control.<br />
* '''Homepage''': http://cinema.elphel.com<br />
* '''Expected results''': We intend on creating a community driven open source cinematic HD camera for a professional environment. <br />
The image is provided by an Elphel camera (elphel.com, open source camera). A beagle board would be connected to an elphel camera using ethernet. The beagle board runs a lightweight UI that allows user to view the live feed from the camera on an external display (dvi or s-video). It also allows to trigger recording and change camera settings using a user interface. The user interface is software based (on screen) + hardware based using buttons and knobs if possible (I2C interface of the beagle board would be used). This project will take 2-6 months to have visible results. The feasibility of this project has been discussed on the Beagle Board group, with positive answers (cfr. http://groups.google.fr/group/beagleboard/browse_thread/thread/6c55a10dd598bb6/e946107bd0a807b8#e946107bd0a807b8 )<br />
* '''Contact''': philippe dot jadin at gmail dot com<br />
</font><br />
==== FMframe ====<br />
<br />
* '''Title''': FMframe<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': FMframe is a picture frame application coupled with an rss news reader and clock/alarm functionality<br />
* '''Homepage''': not yet; in a few days I will try to come up with a website with some preliminary screenshots.<br />
* '''Expected results''': Plan is to make a picture frame application. Hardwarewise the beagle will connect to a DVI display. Softwarewise it will be a picture frame optionally with a clock on top of the photo (either a big semi-transparent clock in the center or a smaller clock in the corner). There will also be an alarm function which can play a preselected mp3 file when the alarm time is reached. Apart from showing pictures the frame can also show news from a user definable rss feed (e.g. cnn.com), Normally this will be in a ticker-tape at the bottom of the picture. When the user presses a button when a specific topic is shown the full message pops up. Probably there will be dedicated provisions for weather, giving the weather forecast if desired (in a style as done by the google weather widget). When waking up the frame can show the weather with the scrolling news or (user selectable) just a list of headlines. When the alarm is switched off the display acts like a regular photo frame again.<br>User interaction will be through a remote control. Alternate inputs could be touch screen (if I get access to an affordable one) or keyboard (less convenient but it does allow people without IR receiver to control the device.<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
<br />
==== BeagleSCI ====<br />
<br />
* '''Title''': BeagleSCI<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': BeagleSCI aims to use the BeagleBoard as a platform for scientific computation and instrumentation (SCI).<br />
* '''Homepage''': http://sourceforge.net/projects/beaglesci/<br />
* '''Expected results''': As a start, the initial goal would be to use the BeagleBoard as a logger of a seismometer. This would involve interfacing a 12-bit ADC chip and writing a driver for it. Data read from the instrument can be displayed by the BeagleBoard through a monitor or send the data to a remote computer via RS-232/RS-485.<br />
* '''Contact''': sherdon dot uy at gmail dot com<br />
<br />
==== Pictouch====<br />
<br />
* '''Title''': Pictouch<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Mobile and Projected Touch user interface<br />
* '''Homepage''': not yet<br />
* '''Expected results''': The goal is to build a new Tactile Interface system based on beagleboard and the DLP picoprojector. Currently, the project make the use of JavaFX to support Multi-Touch (and Multi-User) and of 2 basic webcam, in order to build a low cost gesture recognition system.In the classical case of use, the interface is projected onto a classical table.Users interact directly with their fingers on the projected interface.<br />
<br />
* '''Contact''': maxired at gmail dot com<br />
<br />
==== Fotogenic ====<br />
<br />
* '''Title''': Fotogenic<br />
* '''beagleboard.org project''': not yet - but project is already in progress<br />
* '''Short project description''': Bring network connectivity to plain old vanilla picture frames<br />
* '''Homepage''': www.sourceforge.net/projects/fotogenic<br />
* '''Expected results''': This project brings wired, WiFi and bluetooth connectivity and management to plain old picture frames. The project selects pictures from your photo database, resizes them for the picture frame's native resolution, embellishes them with web and home automation information sources before presenting them to the photo frame by making the BeagleBoard appear to be a USB pendrive...! Right click a photo on your laptop and select "Show on picture frame now!". Manage many photo frames centrally and much much more... Includes "wave gesture" interface to wave over picture frame for next photo... Also works with Eye-Fi SD memory cards to make photos appear on photoframe moments after taken...!!<br />
* '''Contact''': horse_dung at hotmail dot com<br />
<br />
==== Beagle Synth ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Synth<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-synth/<br />
* '''Short project description''': DSP MIDI synthesizer based around the beagleboard<br />
* '''Homepage''': http://code.google.com/p/beagle-synth/<br />
* '''Expected results''': Initially a basic MIDI controllable subtractive synth with 3 oscillators, low pass, high pass, and band pass filters, 2 envelope generators, and 2 LFO's. From there the intention is to add some type of control surface (either physical controls or perhaps a touch screen), some effects (phaser, distortion, reverb), and perhaps other types of synthesis options (FM, additive, maybe some type of patchibility). The result will be a fully featured MIDI instrument comparable to many commercial synths. This project is to be a learning experience with the intention of exploring using DSP for music synthesis. As of now this project is in the concept phase and is still in need of hardware for implementation.<br />
* '''Contact''': dpanseri [at] gmail [dot] com<br />
</font><br />
==== USB Scope ====<br />
<font color="#C0C0C0"><br />
* '''Title''': USB Scope<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': USB diagnostics to aid driver development for USB devices<br />
* '''Homepage''': none yet<br />
* '''Expected results''': This project will use the BeagleBoard as a USB proxy between any USB device and a host computer connected via the OTG port. This will allow the BeagleBoard to snoop, compare and modify USB traffic which can assist both commercial and open source development of drivers and diagnosis of issues. Other ideas could be examined such as a USB-TCP/IP-USB proxy to remotely connect USB devices. Open or free software equivalents exist, but hardware monitoring devices only exist as expensive commercial products. <br />
* '''Contact''': horse_dung at hotmail dot com<br />
</font><br />
==== Irrlicht ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Irrlicht<br />
* '''beagleboard.org project''': no<br />
* '''Short project description''': A fully-featured 3D render engine with ogl-es 1.x and 2.x support<br />
* '''Homepage''': http://irrlicht.sourceforge.net<br />
* '''Expected results''': <br />
** Hardware optimized core routines for optimal OMAP support<br />
** Support of ogl-es 2.x (the 1.x driver is reportedly running on the board)<br />
** Full framerate (60FPS) rendering of q3 alike scenes<br />
** The engine also offers SW rendering, allowing to target for other OMAPs as well, but would require more tweaking in the render optimizations<br />
** We can port one of the demo apps from our apps contest to show the full applicability <br />
* '''Contact''': hybrid[at]users[.]sourceforge[.]net<br />
</font><br />
==== BeagleHam ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleHam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleham/<br />
* '''Short project description''': Bringing the BeagleBoard to the world of Amateur Radio.<br />
* '''Homepage''': None at this time.<br />
* '''Expected results''': <br />
** AX.25 Packet support, enabling full APRS support (operating as tracker, fill-in or permanent digipeater, and KISS TNC).<br />
** Encode and decode of HF digital modes, using DSP functionality where possible:<br />
*** BPSK, QPSK 31/63/125/250<br />
*** Olivia<br />
*** WSPR/MEPT<br />
*** MT-63<br />
*** DominoEX<br />
*** RTTY<br />
*** Throb<br />
** CW encode and decode<br />
** Capability to display on small (sub-6-inch) screens for mobile and field use<br />
* '''Contact''': xunil at xunil dot net<br />
</font><br />
==== TCF Agent Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TCF Agent Port<br />
* '''beagleboard.org project''': http://beagleboard.org/project/TCF+agent+port/<br />
* '''Short project description''': Support remote debugging and run control by porting the Eclipse Target Communication Framework (TCF) Agent to beagleboard+Ångström<br />
* '''Homepage''': Not yet<br />
* '''Expected results''': <br />
** A working port of the TCF "Reference implementation of a target agent" to BB/Ångström<br />
** screenshots and information on the TCF: http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Project.html<br />
** TCF agent running on a beagle board would provide the host computer following capabilities (see link above for details):<br />
*** Run control of userspace processes and threads<br />
*** Breakpoints<br />
*** Registers<br />
*** Stack traces<br />
*** Memory access<br />
*** Processes - list, start, stop, attach and debug.<br />
*** Sys monitor - CPU and memory utilization info<br />
*** File System - browsing and copying files<br />
<br />
* '''Contact''': terrella at terrella dot mobi<br />
</font><br />
<br />
==== RT-Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Real-Time patch for the beagleboard<br />
* '''beagleboard.org project''': http://beagleboard.org/project/omap-rt-patch/<br />
* '''Short project description''': Porting the linux rt patch to the omap linux kernel and providing testing applications. This project is developed at the INSA of Rennes (Engineer school in FRANCE) to allow next year Real Time course to be run on the BeagleBoard.<br />
* '''Homepage''': http://sourceforge.net/projects/linux-omap-rt-p/<br />
* '''Expected results''': <br />
** Porting the linux real-time patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) to the linux omap kernel and providing recipes for openembedded allowing to build the patched kernel.<br />
** Providing testing applications allowing to evaluate the real-time behavior of the platform<br />
** Providing applications that could be used for teaching purposes<br />
* '''Current Results''':<br />
** patch-2.6.29.5-rt21 was modified to successfully patch linux-omap-2.6.29 (modified patch available through project page).<br />
** kernel compile and boots with minor error concerning two IRQs (72,73) <br />
* '''Contact''': piat_jonathan[at]users[.]sourceforge[.]net<br />
</font><br />
==== MyGTee ====<br />
<br />
* '''Title''': MyGTee <br />
* '''beagleboard.org project''': http://beagleboard.org/project/MyGTee/<br />
* '''Short project description''': A handheld device exploiting all the OMAP3530 capabilities<br />
* '''Homepage''': http://enco2009.webs.com/<br />
* '''Expected results''': I stage: building a prototype hopefully based on the BeagleBoard; II stage: the actual handheld that may allow for further software opensource development<br />
* '''Contact''': doctorc[at]o2[.]pl<br />
<br />
==== ONAS ====<br />
<font color="#C0C0C0"><br />
* '''Title''': ONAS<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ONAS/<br />
* '''Short project description''': An open source NAS<br />
* '''Homepage''': http://code.google.com/p/onas/<br />
* '''Expected results''': Development of a full featured NAS running Linux <br />
* '''Contact''': electrogeek[at]wp[.]pl<br />
</font><br />
==== Handheld Lab ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Handheld Lab<br />
* '''beagleboard.org project''': http://beagleboard.org/project/handheld_lab/<br />
* '''Short project description''': The goal of this project is to create a little, yet powerful, handheld laboratory with as much functions as possible. It will be easy of use thanks to the integrated LCD touchscreen and nice GUI.<br />
* '''Homepage''': http://www.mipixel.com/handheld-lab<br />
* '''Expected results''': First result will be working LCD showing oscilloscope. After this spectrum analyzer and logic analyzer. All this stuff will need extra electronics.<br />
* '''Contact''': fran[at]mipixel[.]com<br />
</font><br />
====Beagle Tourister using Hand Gestures and HMD on Beagleboard ====<br />
* '''Title''': Travel Buddy using Hand Gestures and HMD on Beagleboard <br />
* '''beagleboard.org project''': http://beagleboard.org/project/travelbuddy/<br />
* '''Short project description''': A device which will assist a traveller/tourist giving them mobile computing power and the following features: <br />
*1) A Compact HMD (Head mountable device) instead of the conventional projector (Problem of Projection Surface while on the move) <br />
*2) Use of standard cam for Image processing i.e recognising simple hand gestures to interact with the GUI seen in the HMD <br />
*3) Scanning of images (street name plates/hotel names/landmarks/book titles as indicated by user) to provide useful feedback data(directions/reviews/record *videos/take pictures/information) <br />
*4) Mode for Speech2text and text2speech conversion for inter-language communication. <br />
* '''Homepage''': Under Construction <br />
* '''Expected results''':<br />
*1) V-NAV: Virtual Navigator - Streaming Google Street View data according to your current location <br />
*2) ULA: Universal Language Assistant: Scan any text by positioning your fingers and the the scanned text is translated to your default language.<br />
*3) Say goodbye to the camera/ cell phone/tourguide/maps. Good platform for further expansion to include newer features. <br />
*4) Virtual Reality Mapping to the Real World: Overlay of relevant information on the on the HMD.<br />
* '''Contact''': sisilmet2000 at gmail dot com , dhairyadand at gmail dot com <br />
<br />
==== Happiness Device for Cerebral Palsy Kids ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Happiness Device for Cerebral Palsy Kids<br />
* '''beagleboard.org project''': http://beagleboard.org/project/HappyCP/<br />
* '''Project description''':<br />
It is an attempt to bridge the gap in communication between those affected by cerebral palsy and those not. The focus of the problem has been on facilitating communication in the emotional domain since this remains a completely unaddressed area. It is possible that some of the ensuing product functions will additionally facilitate communication problems in the physical domain, as well as be physically therapeutic for the cerebral palsy child in the manner of a comfort blanket. The basis of the product is an Emotional Language Protocol (elp) that works as its interface and is driven by four concurrently acting features - color, shape, motion and sound - corresponding to the sensory modes of the visual, the tactile and the aural. The interaction itself is facilitated by touch of varying intensities including pressing, thumping, squeezing, turning and, of course, by touching. Those not affected by cerebral palsy may additionally use speech along with touch. The interplay of this interface and interaction allows the cerebral palsy child to express his different needs and emotions to another person cerebral palsy or otherwise.Also, the device's mobile connectivity allows its users to communicate with someone far away<br />
* '''Homepage''': http://www.dhairyadand.com/Home/jellow<br />
* '''Expected results''': I have uploaded the basic designs at the above link to the homepage. The device is circular in nature with a touch screen where an interactive interface is used to display icons, objects, photos and other sharable action oriented stuff. The device has exchangable memory sticks which allow two or more device's to get connected and hence facilitating interactions. The result is to get a cerebral palsy kid out of his isolated environment, motivate him to communicate by making a device which will show him the joy of communicating.<br />
* '''Contact''': dhairya AT cyber DOT law DOT harvard DOT edu<br />
</font><br />
==== UPnP/DLNA AV client renderer and transcoding server ====<br />
<font color="#C0C0C0"><br />
* '''Title''': UPnP/DLNA AV client renderer and transcoding server <br />
* '''beagleboard.org project''': http://beagleboard.org/project/UPnP_AV_MediaServer/<br />
* '''Project description''':<br />
Enable the beagleboard as a fully featured UPnP AV rendering client, and as a UPnP AV (transcoding!) server. <br />
<br />
Work will be based upon vlc+djmount (for client side) and fuppes (for server side). Server side transcoding to be hardware assisted via hardware DSP codecs. Initial target for the transcoding server on beagleboard is to drive the Neuros OSD (an underpowered DM320-based device). <br />
<br />
* '''Homepage''': Will be an extension and complement to my work on the DM320-based Nueros OSD: http://osd.oddren.com<br />
* '''Expected results''': Beagleboard can act as either as rendering UPnP client, or as a transcoding UPnP server to drive weaker client devices like the Neuros OSD with their preferred streaming format.<br />
* '''Contact''': bmcarnes_beagleboard AT oddren DOT com<br />
</font><br />
==== Beagle-Traveler====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Traveler<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-traveler/<br />
* '''Short project description''': Automotive media and vehicle management controller. Comparable to BeaglesRide.org (no activity).<br />
* '''Homepage''': http://beagletraveler.wordpress.com<br />
* '''Expected results''': intergrate major automotive subsystem management and communications. Improved vehicle notification of subsystems status'. <br />
* '''Contact''': wheeler dawt larry (at) gmail dawt com<br />
**Please send sponsored information and project questions to the email address above.<br />
</font><br />
==== OMAP Emulator====<br />
<font color="#C0C0C0"><br />
* '''Title''': OMAP Emulator<br />
* '''beagleboard.org project''': http://beagleboard.org/project/OMAP+Emulator/<br />
* '''Short project description''': Emulator for rapid prototyping<br />
* '''Homepage''': no homepage yet<br />
* '''Expected results''': Open source implementation of an IDE environment for rapid code development and testing<br />
* '''Contact''': hwtester (at) myway (dot) com<br />
</font><br />
==== eLazarillo====<br />
<font color="#C0C0C0"><br />
[[File:Elazarillo.png|thumb|300px|eLazarillo sketch]]<br />
* '''Title''': eLazarillo (electronic helper for blind persons)<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': Gadget designed for blind persons or with vision problems. <br />
* '''Homepage''': http://elazarillo.blogspot.com/<br />
* '''Full description''':<br />
Lazarillo is a spanish word that means "blind person's guide" and this is the objetive of this project. This gadget will have features like reading non-braille books, assist to blind persons to get places like markets, drugstores, etc. (based on previous GPS tagged places and using google maps). Other functionalities will be spoken weather information, personal calendar, function keys, etc.<br />
<br />
The gadget will be voice controlled, will need GPS, 3G modem, camera and battery. Size will be 4x5 inches (approx.).<br />
<br />
* '''Expected results''': Open source hardware and software platform for blind persons gadgets. My device will have most of the above described.<br />
* '''Contact''': villanuevaborrego (at) gmail (dot) com<br />
</font><br />
<br />
==== QEMUonARM ====<br />
<font color="#C0C0C0"><br />
* '''Title''': QEMUonARM<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': QEMU on ARM. <br />
* '''Homepage''': http://elinux.org/QEMUonARM<br />
* '''Full description''':<br />
This project aims at resurrect and improve QEMU on ARM hosts.<br />
For more information: http://www.qemu.org<br />
* '''Expected results''': Demonstrate user mode and system mode examples, such as running some simple Linux applications or booting an i386 OS. If there's enough interest, making Wine and QEMU work together might be considered.<br />
* '''Contact''': laurent.desnogues (at) gmail (dot) com<br />
</font><br />
<br />
==== Math-NEON ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Math-NEON<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Math-Neon/<br />
* '''Short project description''': NEON optimized cmath like library <br />
* '''Homepage''': http://code.google.com/p/math-neon/<br />
* '''Full description''': <br />
This project aims to overcome the shortcomings of the VFP-lite based cmath implementation. It is targeted at games and other high performance low accuracy applications. The project will consist of C functions, for PC development, which mirror (as near as possible) the hand optimized NEON assembly routines. In order to gain the best performance i will make use of the NEON Unit's Integer and Floating point pipelines in conjunction with minimizing branches (where they cannot be precalculated on the ARM) and creating new algorithms. <br />
* '''Expected results''': Fast approximate implementations of trigonometric, exponential, logarithmic and power functions for use with future Beagleboard / Cortex A8 based projects. <br />
* '''Contact''': lachlan.ts (at) gmail (dot) com<br />
</font><br />
==== Medical Notebook ====<br />
* '''Title''': Medical Notebook<br />
* '''beagleboard.org project''': yet to register<br />
* '''Short project description''': The Ultimate Notebook for Hospitals<br />
* '''Homepage''': coming soon...<br />
* '''Full description''': <br />
A handheld device to improve hospital functionality/efficiency. To add intelligence to the mundane hospital softwares. <br />
Features are:<br />
<br />
View and Update Patient status, medical history, medication details, appointments, billing - stored as a database in central server.<br />
<br />
Touchscreen with handwriting recognition & hand support pad for data entry.<br />
<br />
Light Weight < 1kg<br />
<br />
VoIP, video conferencing/recording for consulting other doctors <br />
<br />
Wifi, bluetooth & ethernet support <br />
<br />
Docking station for charging<br />
<br />
Support for usb keyboard & mouse on docking station<br />
<br />
* '''Expected results''': <br />
<br />
1) Driver for touch pen tablet with support for hand writing recognition<br />
2) Porting of VoIP software for beagleboard (H.323 ???)<br />
3) Video conferencing software for beagleboard<br />
4) WiFi ?& bluetooth support on beagle board<br />
5) Speech recogntion software for beagleboard<br />
6) Entry of beagle board based products to hospital autmation market<br />
7) Improved, efficient & intelligent patient care in hospitals<br />
<br />
* '''Contact''': noorshaheen.m.n (at) gmail (dot) com<br />
<br />
==== EGLIBC ====<br />
<font color="#C0C0C0"><br />
* '''Title''': EGLIBC support<br />
* '''beagleboard.org project''':<br />
* '''Short project description''': Use EGLIBC as system library for beagleboard project in OpenEmbedded.<br />
* '''Homepage''': www.eglibc.org<br />
* '''Expected results''': EGLIBC becomes the default system library on the distribution and can be used instead of glibc<br />
with the newly added configurability support to selec/deselect features. I would also like to make it compile as pure thumb2<br />
code.<br />
* '''Contact''': raj[.]khem[at]gmail[.]com<br />
</font><br />
==== miniECG ====<br />
* '''Title''': miniECG<br />
* '''beagleboard.org project''': http://beagleboard.org/project/miniECG/<br />
* '''Short project description''': Little device that cares for heart when heart patients are busy carrying out their duties<br />
* '''Homepage''': http://code.google.com/p/miniecg/<br />
* '''Full description''': <br />
miniECG is a wearable device that monitors ECG signal, processes it and can transmit it over wireless internet connection to doctors clinic. It has following features are:<br />
(all the hardware components required are available through digikey.com including LCD and touch screen)<br />
<br />
1) It has touch screen that enable user to give commands like store, display old ECG data, transmit, etc. Device also has a LCD display which is used to display ECG waveform.<br />
<br />
2) A tiny server runs on device that enables doctor to login to device any time he wants and extract patients ECG data. The device is connected to internet through wireless USB dongle. <br />
<br />
3) DSP core does the job of compressing ECG signal, doing PCA (principal component analysis) on ECG signal, detect QRS, measuring heart beats and digital filtering.<br />
<br />
4) DSP along with Cortex A8 runs algorithm that determines critical state of heart by doing feature extraction over ECG signals. It also does PCA over set of stored ECG signal to obtain information about any substantial drift in normal functionality of heart. <br />
<br />
5) Wireless USB dongle provides connectivity to internet and data is transmitted over internet as per schedule programmed into the device. ECG signal can also be streamed over internet using this dongle. <br />
<br />
6) Keyboard & mouse (USB) interface is provided for more flexibility and quick access. LCD monitor interface is also be provided. Key-board, mouse and LCD monitor interface will work only when device is powered by adaptor. For device powered by battery only input option is touch screen and only output option is LCD display.<br />
<br />
7) Device also has small software support to give reminder on when to consume which drug. The prescription of drug and its timing information is feed in as per doctors advice. (keyboard and mouse interface with miniECG can be of great advantage here)<br />
<br />
8) USB memory devices will be used to store ECG data.<br />
<br />
9) miniECG will be dual powered. It can be powered by adaptor as well as with rechargeable battery. <br />
<br />
Website link has block diagram of miniECG and also picture of ECG pre-amplifier which is already designed. In future all the source codes will be uploaded on the link as and when available.<br />
<br />
* '''Expected results''': a) Ability to login from remote PC onto miniECG and read data b) Should be able to send stored data or stream live ECG signal over internet c) Robust interface of LCD & touch screen with controller d) Data storage and retrieval from USB storage device e) Successful implementation of DSP algorithms for feature extraction, PCA, QRS detection, filtering and compression. f) As the whole device is battery powered, software & driver which are very specific to the desired application should only be installed & made working. Thus providing a low power system architecture. <br />
<br />
* '''Future Work''': Once the desire basic funtions of ECG storing, retrieval and transmitting is meet, miniECG can be programmed into miniPA (mini personal assistance) mainly targeting senior citizens. miniPA will have much advanced features that can help them elderly person in their day-to-day activity.<br />
* '''Contact''': mehta.nandish (at) gmail (dot) com<br />
<br />
<br />
==== remoteBillBoard ====<br />
* '''Title''': Remote Bill Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/remoteBillBoard/<br />
* '''Short project description''': Video bill boards, remotely controlled via web over a 3G modem<br />
* '''Homepage''': http://www.greensoftware.net/remoteBillBoard<br />
* '''Full description''': <br />
Play HD video on billboards, remotely manage the billboards, upload new advertisements, remove old ones etc..<br />
<br />
<br />
* '''Expected results''': <br />
a) 3g modem support, so flexiblity.<br />
b) a full working web based system<br />
<br />
* '''Future Work''':<br />
a) a more advanced desktop application to replaced the web based solution.<br />
<br />
* '''Contact''': ahmad.mushtaq (at) gmail (dot) com<br />
<br />
<br />
==== Turk ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Turk Platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Turk/<br />
* '''Short project description''': A wireless dynamically-mappable interface platform for small devices<br />
* '''Homepage''': http://www.turkinnovations.com/<br />
* '''Full Description''': Turk will be an open-source wireless interface platform that allows interfacing of small wireless (Zigbee or Wi-Fi enabled) devices through a dynamic mapping framework and web interface. Developers can implement their device's protocol easily through small user-space drivers called 'Gadgets' and host them on our server. The platform is then capable of automatically downloading and starting appropriate gadgets for new devices that are compatible with the basic Turk protocol. Gadgets reveal their services to the user and other gadgets through our growing library of data endpoint types (such as colors, URLs, booleans, xml strings) and user controls (like sliders, switches and color pickers), and can then be connected to each other through a themable web interface.<br />
<br />
* '''Expected results''': <br />
**A platform that allows developers to write simple user-space drivers that expose interfaces through XML-RPC<br />
**A web interface and remote configuration capabilities through a central server. <br />
**A simple and well-tested protocol and driver for a kernel-managed point-to-multipoint Zigbee network. <br />
**More hardware connectivity besides the Wi-Fi and Zigbee interfaces will hopefully be developed by collaborating with other beagleboard projects and developers.<br />
* '''Contact''': rob.odwyer [at] turkinnovations [dot] com<br />
</font><br />
==== BeagleWacom ====<br />
* '''Title''': Wacom Tablet driver for Beagle Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-wacom/<br />
* '''Short project description''': Linux drivers of wacom tablet ported for Beagle Board<br />
* '''Homepage''': <br />
* '''Full Description''': beagle-wacom will be port of linux drivers for configuring & running wacom tablets with the beagle board. The idea is to have support for wacom-components, so that they can be used by OEMs of beagleboard based products using linux as their OS<br />
<br />
* '''Expected results''': <br />
**easy integration of wacom tablet with Beagle Board. <br />
**OEMs of beagleboard based products using linux as their OS can integrate wacom-components in their product with minimal fuss<br />
* '''Contact''': najath [at] gmail [dot] com<br />
<br />
<br />
====hApplause====<br />
<font color="#C0C0C0"><br />
* '''Title''': hApplause<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Hardware Platform that You can use to play with Audio Synthesis<br />
* '''Homepage''': not yet<br />
* '''Description''': ''hApplause'' will be multi-functional flexible audio hardware platform. The goal is to make a tool that can allow to develop audio software and hardware (e.g. DSP synthesizers, FX units, hardware expansion boards, etc.). The concept is inspired by [http://www.chameleon.synth.net/ Chameleon] and [http://www.ucapps.de/ MIDIbox]. ''BeagleBoard'' will give ''Chameleon'' like software flexibility while planed hardware with ''Expansion Interface'' and ''Audio Multiplexer'' will give ''MIDIbox'' like hardware flexibility.<br />
*; Hardware features<br />
*: Audio Stereo In/Out<br />
*: MIDI In/Out/Thru<br />
*: General purpose USB port - function depends on user application<br />
*: General purpose SD/MMC Card (e.g. for user data storage) - function depends on user application<br />
*: Front panel interface (1U rack version) with:<br />
*:* LCD<br />
*:* Volume potentiometer<br />
*:* Headphones jack<br />
*:* Power switch with LED indicator<br />
*:* programmable rotary encoders (5 are planed)<br />
*:* programmable buttons and LEDs (12 are planed)<br />
*: Expansion Interface with audio signal buses (1-4 planed, depends on final implementation) and data/command bus (I2C and/or CAN)<br />
*: Audio Multiplexer for flexible routing of audio signal between ''BeagleBoard'', ''Audio In/Out'' and ''Expansion Interface''<br />
*: USB and RS232C for developers<br />
*; Software features<br />
*: All hardware will be fully accessible from ''BeagleBoard'' by API<br />
*: hApplause OS is planed (abstract layer over hardware, user program loading, self configuration on power on)<br />
* '''Expected results''':<br />
*# 19" 1U rackmount unit ready to play with.<br />
*# Libs and additional software for developers (at least API for hApplause's hardware)<br />
*# Example implementation of software synth<br />
*# Single size eurocard unit for 3U rack, like in [http://www.doepfer.de/a100e.htm Doepfer A-100 System] modules<br />
* '''Contact''': tawezik at gmail dot com<br />
</font><br />
==== BeagleLAB====<br />
* '''Title''': BeagleLAB<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleLAB/<br />
* '''Short project description''': BeagleLAB is an Embedded developer's workbench comprising of must-have hardware/software utilities.<br />
* '''Homepage''': http://code.google.com/p/beaglelab/<br />
* '''Expected results''': <br />
:* A PC free host providing a development environment based on beagle board (running ubuntu 9.04 or later)<br />
:* Host environment with software applications and hardware interfaces to substitute oscilloscope, multimeter & logic analyzers<br />
:* GNOME widgets (software apps) & Linux device drivers for capturing data,storing,comparing and visualization<br />
:* Legacy ports like the serial, parallel ports for device interfacing and control<br />
:* Making an embedded developer's life easier and workbench neater<br />
* '''Contact''': amarendermail[at]gmail[dot]com and saurabhg84[at]gmail[dot]com<br />
<br />
====PREEMPT_RT====<br />
<font color="#C0C0C0"><br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
</font><br />
<br />
====HDDM====<br />
<font color="#C0C0C0"><br />
* '''Title''': HDDM<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/HDDM/]<br />
* '''Short project description''': A multimedia system based on OMAP and linux.<br />
* '''Homepage''': Under construction<br />
* '''Expected results''': Beagleboard as a control center for home theatre system<br />
* '''Contact''': grover.ankur (at) gmail (dot) com<br />
<br />
Note from Dirk: Please see [http://www.syspire.de/node/3 Embedded Mediacenter], too (sorry, German only, use Google translate if needed).<br />
</font><br />
====BeagleVision====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleVision<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beaglevision/<br />
* '''Short project description''': An efficient object recognition framework <br />
* '''Homepage''': http://code.google.com/p/beaglevision/<br />
* '''Description''': BeagleVision will be a fast object recognition framework. The aim of the project is to have a hardware optimized implementation (utilising the DSP and NEON) of state-of-the-art local feature detectors and descriptors on the Beagle Board. BeagleVision will include [http://www.cs.bris.ac.uk/Publications/pub_master.jsp?id=2001018 our recent work] on efficient feature detectors and descriptors, other well-known algorithms (e.g. FAST corner detector and SURF), and efficient matching algorithms for very large datasets (>1M images).<br />
* '''Expected results''':<br />
:* An open source library for developers (a project hosted on code.google.com)<br />
:* A sample application for building recognition in a city scale dataset, to show how: to add new images to the dataset, to use it for location based services, and how to reduce the search time if a GPS is available to get geolocations<br />
:* A wiki for interested developers<br />
:* Reporting the running times of new algorithms on OMAP (as a benchmark) in scientific publications<br />
* '''Contact''': m.ebrahimi at ieee dot org<br />
</font><br />
====Beagle-Arduino hybrid robot====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Arduino hybrid robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Beagle-Arduino+hybrid+robot/<br />
* '''Short project description''': A robot using a Beagleboard for high-level processing and Arduino for low-level control<br />
* '''Homepage''': http://mechomaniac.com/robots<br />
* '''Description''': The Beagle-Arduino robot will use a Beagleboard for high-level robot functions:<br />
** image processing<br />
** artificial intelligence<br />
** speech synthesis<br />
** voice recognition<br />
** internet connectivity<br />
And an Arduino for low-level functions:<br />
** motor / servo control<br />
** sensor input & output<br />
** battery monitoring<br />
The two microcontrollers will be connected by USB, along with a USB webcam mounted on a servo pan/tilt mechanism, and a USB wifi dongle for internet connectivity. Basic tank treads will provide movement, possible being replaced by servo-based legs for a humanoid or dog form.<br />
* '''Expected results''':<br />
:* Easy physical interfacing to the Beagle without having to design and build special expansion boards<br />
:* Image processing using OpenCV with a USB webcam<br />
:* Speech synthesis and voice recognition<br />
* '''Contact''': tim at mechomaniac dot com<br />
</font><br />
<br />
====DJ Audio / Video Mixer====<br />
<font color="#C0C0C0"><br />
* '''Title''': DJ Audio / Video Mixer* '''Contact''': <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/djvideomixer/]<br />
* '''Description''': This is a small, Touch LCD controlled DJ Mixer, which not only is great as a nightclub tool for playing audio -not only reproducing music, actually '''''playing''''' with it-, but also has high end video playback capabilities, thus making it an all-round experience both for the DJ and the audience. It will bring all the experience of professional DJ mixers to users, while being portable, and which when coupled with either a normal projector, or even better, with a PicoProjector, makes a whole experience for audio and video playback in Discos, Bars, Lounges, to mention just a few possible applications. You can even use for your own parties, and it will rock!<br />
* '''Homepage''': [http://code.google.com/p/djvideomixer/]<br />
* '''Expected results''': <br />
** Audio playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Video playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Audio/Video synchronization, allowing song change, video change, etc.<br />
** High end, professional DJ-Mixer audio effects.<br />
** User interface based on LCD and with touchscreen capabilities.<br />
* '''Contact''': jaime_dot_aranguren_at_ieee_dot_org<br />
</font><br />
====schooldog====<br />
<font color="#C0C0C0"><br />
* '''Title''': schooldog<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/schooldog/]<br />
* '''Description''': The purpose is to make an ''off the shelf'' low cost schoolcomputer that can be used on various levels of education. It will be small so students can take it with them and the school just has to provide for input / output items. This way even people that cannot afford laptops can participate in the digital era or schools can provide a robust and good machine for studypurposes.<br />
* '''Homepage''': [http://schooldog.wickedmind.net]<br />
* '''Expected results''': <br />
** Educational linuxbased OS, from USB sticks and SD Cards.<br />
** more general use of BeagleBoard and more public awareness for the powerful small computer.<br />
** Affordable,individual and steady study enviroment<br />
<br />
* '''Contact''': wickedmind<br />
</font><br />
====Disko====<br />
<font color="#C0C0C0"><br />
[[File:Disko_logo.png|thumb|200px|UI Application Framework]]<br />
* '''Title''': Disko - UI Application Framework<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Disko/<br />
* '''Short project description''': Disko is a Linux-based toolkit to build touchscreen- and remote-controllable ui applications. It contains native OMAP framebuffer support and the media content is DSP-accelerated by GStreamer (TI-Codecs).<br />
* '''Homepage''': http://diskohq.org<br />
<br />
* '''Expected results''': Expected result is broad support of Disko by developers of user interfaces and applications for embedded devices.<br />
** SIP - IP telephony support delivered by pjsip and minisip <br />
** Gstreamer - to add an alternative to the xine library and to add the TI Codecs supplied for the DSP.<br />
** Webkit - the great embedded browser OWB of Pleyo (planned for Disko 1.7)<br />
** SVG - at least one SVG engine to have an alternative to Flash. Initial work has already been done at MadButterfly (planned for Disko 1.7) <br />
* '''Contact''': gmadaus [at] berlinux-solutions dot de or mspringer [at] berlinux-solutions dot de<br />
</font><br />
====FETCH====<br />
* '''Title''': FETCH - FPGA enabled Tool Contol Host<br />
* '''beagleboard.org project''': http://beagleboard.org/project/FETCH<br />
* '''Homepage''': http://code.google.com/p/fetch/<br />
* '''Short project description''': A host with a web interface for easy configuration and control of connected tools. The device may also be controlled through a PSTN network using DTMF tones. The BeagleBoard will act as the main server and will also be the host interface for the connected FPGA for the purpose of evaluating the IPs developed on the FPGA.<br />
* '''description : Phase 1 '''<br />
***1) Server capability -- all services (except VNC) to be launched through inetd so that they are started on an on-demand basis. <br />
***-- http server for configuration pages <br />
***-- ssh server (the ssh suite in particular including scp etc.. so that an ftp server can be avoided) for remote login. <br />
***-- bootp server for bootstaping machines on my home network. <br />
***-- VNC for GUI sessions :) <br />
***-- CUPS for network printing <br />
***-- NetHack server :D <br />
***2) Tool Control <br />
***-- The term "Tool Control" here refers to automation of connected tools and Phase 1 of the project will demonstrate this by automation in home (eg. computer, printer, scanner on/off --> (the contoller board with the relays is complete :) ), these devices may be contolled over the internet or PSTN network ) The system will also be hooked to the home electrical network that will enable control over home appliances. A special mode called " Home Alone" will switch on/off lights randomly when no one is at home to give the illusion that the house is occupied ( and hence protect from thefts ;) ). The current relay boards developed use a UART (for RS232 protocol) for control of the equipment but it is planned to use the CAN interface (under developement ) so that longer distances can be covered. <br />
***3) The BeagleBoard will act as a host interfacefor a Nexys2 Xilinx FPGA board and will be used to evaluate the IPs deployed on it. This feature is sort of a tester for the FPGA. <br />
**'''Phase 2 ''' ( only after Phase 1 is completely functional :) ) <br />
***1) CAN interface for the controller nodes replacing the RS232 connections<br />
***2) mgetty (for faxes) and asterisk (VOIP) may be added to the server.<br />
* ''' Contact : ''' akshat dot g dot gupta [at] gmail dot com<br />
<br />
==== ESITeam====<br />
<font color="#C0C0C0"><br />
* '''Title''': ESITeam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ESITeam/<br />
* '''Short project description''': It's a robotic soccer team with vision and intelligence distributed through the use of wireless communication (Zigbee) between robots and PC.<br />
* '''Expected results''': The expected results would have a running and competitive team for the RoboCup's championship this year.<br />
<br />
* '''Contact''': registrosvmora at gmail dot com<br />
</font><br />
==== PupLC====<br />
* '''Title''': PupLC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/PupLC/<br />
* '''Short project description''':Open source control of PLC operated equipment.<br />
* '''Homepage''': No homepage yet<br />
* '''Expected results''': <br />
:*PupLC will be an open source PLC controller. The user will be able to control the PLC's autonomously or by direct control. The direct method will allow the user to change equipment status using a touch screen lcd. The PupLC will control all aspects of the operating equipmet (ie. setpoints, red-hand settings, shutdowns, etc.) Additionally, 24-hours of accumulated system data will be saved to disk and can be accessed via ftp for analysis off-site.<br />
* '''Contact''': alcpo729[at]tds[dot]net<br />
<br />
====Speed-Reader====<br />
<font color="#C0C0C0"><br />
* '''Title''': Speed-Reader<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Speed-Reader/<br />
* '''Short project description''': Speed-Reader is an audio book reader that gives the listener control of the speaker rate.<br />
* '''Homepage''': http://www.nerd1951.com/?page_id=72<br />
* '''Description''': Speed reader allows an audio book to be played back with faster or slower speaker rates. A user interface gives the listener realtime control of the speaker rate. Speed-Reader uses digital speech signal processing to accomplish low distortion timescale modification of speech in real time. Timescale modification of speech is accomplished by selectively repeating segments of speech to slow down the speaker rate or deleting selected speech segments to speed up the speaker rate. Digital signal processing is used to determine which speech segments are candidates for repetition or deletion.<br />
* '''Expected results''':<br />
***--Realtime (during playback) timescale modification of digitized speech using the C64++ DSP<br />
***--Initially read digitized speech from the SD card interface<br />
***--Audio output using the Beagleboard stereo out<br />
***--Initially user interface provided via RS-232 interface<br />
* '''Contact''': harvey dot sugar at nerd1951 dot com<br />
</font><br />
<br />
====DVB-T Receiver====<br />
<font color="#C0C0C0"><br />
* '''Title''': DVB-T Receiver<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': The DVB-T Receiver project aims to implement a fully tunable DVB-T Receiver on the Beagle Board.<br />
* '''Homepage''': Will be launched in the near future (at blog.arsln.org)<br />
* '''Description''': The DVB-T receiver is a senior graduation project that has to be completed in one year (until Summer 2010). It will be a fully tunable DVB-T receiver. It will compatible to receive digital terrestrial TV & radio stations. The goal is to show the capabilities of the Beagle Board and build a DVB-T system from the scratch. The input will be through a ADC daughter-board that is plugged to the USB port. The output will be via the USB port(for portable devices i.e Netbook) or DVI-D. <br />
* '''Expected results''':<br />
***--Capturing broadcast signals(DVB-T) and convert them to discrete time signals<br />
***--Demodulate and encode the incoming signal<br />
***--Video output using the Beagleboard's DVI-D port or via the USB port for portable devices<br />
* '''Contact''': ftharsln at gmail dot com , sulaya05 at gmail dot com<br />
</font><br />
<br />
====ArchMobile: ArchLinux ARM Port====<br />
<br />
* '''Title''': ArchMobile<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/AM/ AM]<br />
* '''Short project description''': ARM Port of the x86-Linux Distribution ArchLinux<br />
* '''Homepage''': [http://www.archmobile.org ArchMobile]<br />
* '''Expected results''': Fully working ArchLinux with X and all other features.<br />
* '''Contact''': rotter.manuel@gmail.com or naeg on Freenode<br />
<br />
==== MythBeagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': MythBeagle<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': MythBeagle aims at bringing MythTV to the beagle; both frontend and backend, including plugins (as far as possible)<br />
* '''Homepage''': not yet; <br />
* '''Expected results''': <br />
** OE recipes for mythtv 0.22, mythplugins 0.22 and whatever might be needed to get things going (including bringing required recipes to the latest version where needed/possible)<br />
** An image for SD card to allow easy install, or a script or recipe to allow easy installation<br />
** some additional configuration notes (configuring MythTV is somewhat a pain...)<br />
** setup should also allow using the beagle only as frontend or backend<br />
* '''Status''': mysql5 recipe has been created (mythtv 0.22 won't use mysql4); recipes for mythtv are there, except for mythweb, documentation/installation work has started;<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
</font><br />
<br />
==== Homebrew SmartPhone ====<br />
<br />
* '''Title''': HomeBrewSmartPhone<br />
* '''beagleboard.org project''': http://code.google.com/p/hbpd<br />
* '''Short project description''': HomeBrewSmartPhone is a project to use the beagleboard to create a community-buildable mobile phone that is powerful enough to also run as a Desktop PC.<br />
* '''Homepage''': http://lkcl.net/reports/hbp <br />
* '''Expected results''': <br />
*** A device capable of Digital Voice as well as Data / Internet Access.<br />
*** A device capable of shutting down into low-power mode and successfully resuming on incoming calls.<br />
*** RF-protected audio circuits that don't have howling feedback from the 3G/GSM Radio module.<br />
*** Full disclosure of all build components (schematics, BOM) under free software licenses.<br />
*** Full documentation of all hardware interconnections<br />
*** Creation of a <b>basic</b> demonstration image that will allow other software developers to participate very early on<br />
*** Addition to the http://handhelds.org site for developers to create GUI-based distros<br />
* '''Contact''': lkcl@lkcl.net or use http://lkcl.net contact box<br />
<br />
==== XBMC ARM Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': XBMC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/XBMC/<br />
* '''Short project description''': XBMC Is a full-feature home-theater application that works on a variety of platforms and operating systems<br />
* '''Homepage''': http://xbmc.org<br />
* '''Expected results''': <br />
*** Feature parity with XBMC x86 and ppc<br />
*** Usage of OpenGL ES 2.0<br />
* '''Contact''': Cory Fields: theuni @at@ xbmc .dot. org<br />
</font><br />
<br />
==== Beagleboard Carputer ====<br />
<br />
* '''Title''': Beagleboard Carputer<br />
* '''beagleboard.org project''': http://beagleboard.org/project/bbcarputer<br />
* '''Short project description''': The Beagleboard Carputer aims to create a fully-integrated system that will feature touchscreen LCD, Bluetooth and USB connectivity, GPS Navigation, Phone features, Wifi, Voice recognition, Multimedia entertainment.<br />
* '''Homepage''': http://bbcarputer.codeplex.com<br />
* '''Expected results''': Provide a fully-integrated system that will feature:<br />
*** 7in touchscreen LCD<br />
*** Wireless connectivity<br />
*** Usb connectivity<br />
*** GPS Navigation<br />
*** Phone features<br />
*** Voice recognition<br />
*** Multimedia entertainment<br />
*** Opensource Application Suite<br />
*** Games<br />
* '''Contact''': Joey Mar Antonio: joeymar.antonio @at@ awsol-i .dot. com<br />
<br />
==== GuideBeagle: Portable monocular SLAM system ====<br />
<font color="#C0C0C0"><br />
* '''Title''': GuideBeagle<br />
* '''beagleboard.org project''': Not yet available.<br />
* '''Short project description''': GuideBeagle is a portable localization and mapping system based on monocular vision. Such a system can be used, among other things, to build:<br />
:*Interactive visitor guidance systems for museums and stores.<br />
:*Artificial Reality tools and games.<br />
:*Mobile robot control systems.<br />
:*Surveillance and security related applications.<br />
:In other words: it solves a Simultaneous Localization and Mapping (SLAM) problem using a single camera as sensor, working on-line, and producing maps with high-level geometrical information (i.e. not just simple punctual visual landmarks on space). It will be based on recent research on the fields of Computer Vision and Mobile Robotics.<br />
* '''Homepage''': http://sites.google.com/site/guidebeagle (This page will be enhanced uninterruptedly.)<br />
* '''Expected results''': <br />
**Mapping --- The final system will allow an user to move by an environment like an office or a small apartment and build a map of it similar to a 3D model with planes and textures, as used in Computer Graphics.<br />
**Localization --- After a map is built, the user can move around the environment, and the system will interactively estimate the geometric location of the camera and the direction it is heading, based on images continuously obtained from the camera.<br />
**Image processing --- Building this system will require the coding of image processing tools that may be useful to many other image processing applications based on the Beagle Board. Some examples are feature detectors and descriptors, edge detectors, template matching by normalized cross-correlation and the Discrete Fourier Transform.<br />
* '''Contact''': nwerneck@gmail.com or nwerneck@usp.br<br />
</font><br />
<br />
==== AutoRobo ====<br />
<br />
* '''Title''': Development of an autonomous robotics platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/autorobo/<br />
* '''Short project description''': Design, prototype and develop an autonomous aerial vehicle system around BeagleBoard, allowing experimentation with real-time control and computer vision algorithms.<br />
* '''Philosophy''':<br />
:* make robotics and embedded control accessible and fun<br />
:* stimulate cross-field learning and collaboration<br />
:* leverage modularity and reuse to get more done, quicker <br />
* '''Technical goals''':<br />
:* develop generalised physics model for eg computing optimal PID controlled motor outputs<br />
:* decouple high-update-rate sensors from lower-rate output control<br />
:* employ OpenCV for visual tracking/SLAM/feature detection<br />
:* build lean tracked (land) vehicle<br />
:* build lean quad-rotor (air) vehicle<br />
:* use a shared, modular code-base and electronics platform (Beagle and IGEPv2) <br />
* '''Homepage''': http://code.google.com/p/autorobo/<br />
* '''Expected results''': Initial bringup of a tracked vehicle via dual-motor controller via Beagle's PWM outputs. Utilisation of 3-axis accelerometer and 3-axis gryo via I2C and/or SPI buses, enabling more advanced control<br />
* '''Contact''': ''daniel (dot) blueman (at) gmail (dot) com''<br />
<br />
==== Beagle-Walker ====<br />
<br />
* '''Title''': Design of a automatic dog-walker robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleWalker/<br />
* '''Short project description''': Develop an autonomous dog-walker robot<br />
* '''Homepage''': http://code.google.com/p/beaglewalker/<br />
* '''Expected results''': <br />
**The main goal of the system is analyze the feedback between the dog and the robot to track where the dog is going and where the robot should go.<br />
**Let the dog walk only in places previously programmed by the dog's owner making use of basic SLAM algorithms. <br />
**avoid any obstacles/vehicles.<br />
* '''Contact''': ''darthdj at gmail dot com''<br />
<br />
==== nullDC / Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nullDC<br />
* '''Expected results''': For the contest: A working build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
</font><br />
<br />
==== MyoVox ====<br />
* '''Title''': MyoVox<br />
* '''beagleboard.org project''': <br />
* '''Short project description''': <br />
* '''Homepage''': <br />
* '''Expected results''': <br />
* '''Contact''': smcgill3 [at] seas[.]upenn [.] edu<br />
<br />
==== Beagle-Eye ====<br />
<br />
* '''Title''': Beagle-Eye<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle-Eye/ Beagle-Eye]<br />
* '''Short project description''': A beagle-eyed guide for the visually challenged.<br />
<br />
* ''' Hardware''':<br />
** A pair of calibrated USB cameras, mounted on the user's shoulders, such that the combined field of view covers at least 180 degrees.<br />
** One or more linear actuators connected through RS-232, situated on one of the user's limbs.<br />
** Stereo headphones.<br />
** USB GPS Dongle.<br />
<br />
* '''Description''':<br />
** Low frame rate real-time video is used to guide the user towards a specified destination.<br />
** The GPS provides coarse location.<br />
** The stereo camera setup provides a wide field of view, along with coarse depth information.<br />
** Map information, combined with real time video is used to esimate location and orientation more accurately.<br />
** Simple object recognition techniques are employed to recognize parts of the environment.<br />
** The audio setup and the actuator(s) are used either in tandem or interchangeably to guide the user. This can be customized as required. Some possibilities include:<br />
*** A short periodic 3D sound generated to indicate the direction in which the user is to walk.<br />
*** The user is alerted about approaching obstacles by firing the actuator at a frequency inversely proportional to the distance to the obstacle. This distance can be computed using depth information computed from pairs of images.<br />
*** Information about the environment, such as "Pedestrian Crossing in 20m" can be relayed through audio.<br />
<br />
* '''Possible Enhancements''':<br />
** More comprehensive localization techniques, such as SLAM, can be used to improve the accuracy of the system. This will also open doors to indoor navigation, where the GPS fails.<br />
** Detection, segmentation and recognition of text (such as signboards and street names) in the environment will ensure less errors in navigation.<br />
<br />
* '''Expected Results''':<br />
** A navigation tool for the visually challenged, using audio and linear actuators to communicate with the user.<br />
<br />
* '''Contact''': leatherbrain at gmail dot com<br />
<br />
==== BeaglePod ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeaglePod<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglepod/]<br />
* '''Short project description''': BeaglePod is an IPod plug-in replacement for car stereo's that are IPod Ready. The BeaglePod uses gstreamer as an audio/video player and is controlled via the car stereo head unit using Apple Accessory Protocol. <br />
* '''Description''': The BeaglePod is an audio/video player for cars equipped with "IPod Ready" stereos. Using the Apple Accessory Protocol the car stereo is used to select and control the playback of media on the BeaglePod. Adding a video monitor the BeaglePod can also become a video player running all the audio through the car stereo with full pause, play, stop control using the car's stereo head unit. Using a software implementation of the Apple Accessory Protocol the BeaglePod is connected to the car stereo via a USB->TTL cable.<br />
* '''Expected Results''':<br />
** Play audio/video media files from the Beagleboard using the car stero to control playback and track selection.<br />
** Audio will playback through car's exist speaker.<br />
** With gstreamer dsp support HD playback of video with in car lcd.<br />
* '''Contact''': velorider [X] publicemail [X] us<br />
</font><br />
<br />
==== MART ====<br />
* '''Title''': Autonomous modular robot<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': Build an autonomous robot to enter the Eurobot 2010 competition<br />
* '''Homepage''': (only in Czech) http://eurobot.matfyz.info/<br />
* '''Full Description''': Goal of this project is to build an autonomous modular robot, that will be able to compete in the Eurobot competition. This project includes following:<br />
<br />
** '''HW''':<br />
** Custom beagle daughter-card (including kernel driver patches):<br />
*** CAN (Controller area network) able to sustain 1Mbit/s, using embedded cortex-m3 controller<br />
*** Battery backed up RTC<br />
*** Dual power - battery and/or adapter, with battery management (current consumption sensing and charging) <br />
*** Second serial and i2c headers<br />
*** (optional) Ethernet controller 10/100Mbit<br />
** Custom motor, servo and stepper motor drivers and IO boards<br />
*** everything connected through CAN<br />
<br />
** '''SW''':<br />
** Modular architecture, for simple modification<br />
** OpenCV integration for play field object identification<br />
** optimalizations for NEON (and DSP)<br />
<br />
* '''Contact''': Michal dot Demin at Gmail dot Com<br />
<br />
==== CamCast ====<br />
* '''Title''': Webcam broadcast server/relay<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/CamCast/]<br />
* '''Short project description''': Webcam broadcast platform for USB webcams<br />
* '''Homepage''': <br />
* '''Full Description''': The goal of this project is to utilize the beagleboard as a low cost platform for webcam video feeds.<br />
Server capability:<br />
<br />
** Broadcast webcam feeds for directly connected USB webcams<br />
** Relay webcam feeds from other servers, typically connected over wi-fi<br />
** Decimate MJPEG streams to match bandwidth limits<br />
** Monitor and control streams via HTTP<br />
** Advertise HTTP services locally via Zeroconf<br />
<br />
The beagleboard will require a functional Linux gspca driver for all USB webcams in use as well as USB wi-fi for remote service. Linux Zeroconf service must also be included.<br />
<br />
* '''Contact''': spiderkarma at gmail dot com<br />
<br />
====Beagle SecMon====<br />
<font color="#C0C0C0"><br />
* '''Title''' : Beagle Security Monitoring over Web <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle+SecMon/ BeagleSecMon]<br />
* '''Short project description''': This project proposes to control and transmit audio and video from a remote place using the beagleboard as a webserver.<br />
* '''Expected results''': The system will control one or more digital cameras with pan, tilt and zoom functions, and microphones. Besides, it can be configured to send information to a pre registered cell phone when movement is detected. Also, audio and video can be accessed using internet from any place.<br />
* '''Contact''': cborges at ifsc dot edu dot br====<br />
</font><br />
<br />
====PortablePlateRec====<br />
<br />
* '''Title''' : Beagle Portable Plate Recognition <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/PortablePlateRec/ PortablePlateRec] <br />
* '''Short project description''': A portable system for automatic number plate recognition (ANPR) using BeagleBoard.<br />
* '''Expected results''': The goal of this project is to develop a portable system for automatic number plate recognition (ANPR) using BeagleBoard. It includes the following:<br />
** receiving images from a camera;<br />
** applying signal processing algorithms for plate localization, orientation and sizing, image normalization, and character segmentation;<br />
** optical character recognition (for instance, Tesseract);<br />
** possible access to a database to check the plate against law infringements.<br />
<br />
* '''Contact''': fpacheco at ml1 dot net<br />
<br />
====Digital Multimedia Frame====<br />
<br />
* '''Title''' : Digital Multimedia Frame<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a photo, video and music application who use a touchscreen display<br />
* '''Expected results''': The goal of this project is to get photo, video, music from memory card or from a network. <br />
<br />
** Scan network to multimedia file. <br />
** Create automatically a slideshow when we are in photo mode.<br />
** Create automatically a music list.<br />
** Play video<br />
** Add basic operation available for picture (rotate, resize...)<br />
** touch screen will be used to simplify action.<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
====Beagle Utility====<br />
<br />
* '''Title''' : Beagle Utility<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a box with lcd screen to be able to encrypt, format, wipe, clone, find virus, search rootkit .... a hd or memory card. A menu with different operation is displayed to user.<br />
* '''Expected results''': The goal of this project is to be able to do some operation on harddriver, memory card <br />
<br />
** Encrypt <br />
** Format<br />
** Wipe<br />
** Clone<br />
** find virus<br />
** Rootkit<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
===Contest #2 projects===<br />
<br />
Please don't add new projects, contest #2 is closed.<br />
==== James ====<br />
1st [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/James James]<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. <br />
* '''Expected results''': Updated recipes for all relevant packages on OpenEmbedded. A script to install the needed packages to an Angstrom image (generated by Koen's generator) and documentation on how to configure things.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
</font><br />
====BeagleEPD====<br />
2nd [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': E-Ink Interface Board and Driver for beagleboard<br />
* '''Homepage''': [http://elinux.org/BeagleEPD BeagleEPD]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleepd/<br />
* '''Short project description''': This project aims to interface an E-Ink display directly with a beagleboard. This is done by creating an interface board that is connected to the Beagleboard expansion header and converts the relevant gpio signals into the levels appropriate for interfacing with the E-Ink display controller. The second part is to write a driver which is a port of am300epd.c from mach-pxa to mach-omap in order to support the E-Ink broadsheet framebuffer driver directly on beagleboard. All of this results in making it possible to connect any E-Ink display controller to a Beagleboard (via the expansion header) and to then treat any E-Ink display as another framebuffer.<br />
* '''Expected results''': Schematic for interface PCB between Beagleboard and E-Ink display controller board. A beagleepd.c mach-omap driver that will setup and control the IO pins appropriately.<br />
* '''Contact''': jayakumar at IRC (freenode, oftc) or jayakumar.lkml@gmail.com<br />
</font><br />
==== nullDC / Beagle ====<br />
<br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with newly added support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nulldc_beagle<br />
* '''Expected results''': For the contest: A WIP (but working) build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
===Contest #1 projects===<br />
<br />
====qemu-omap3====<br />
<br />
* '''Title''': support beagle board emulation in qemu<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]<br />
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.<br />
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]<br />
* '''Expected results''':<br />
** booting linux kernel and rootfs from nand and mmc image<br />
** Wiki page how to run qemu-omap3 for beagle board<br />
* '''Submission''':<br />
** http://code.google.com/p/qemu-omap3/wiki/UserManual<br />
* '''Contact''': yajin AT vm-kernel.org<br />
<br />
====openGPS====<br />
<br />
* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites. <br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** development of a display app with moving map capabilities<br />
** development of a user interface for handheld apps<br />
** integration with suitable LCD display<br />
** interface to map files on SD card<br />
** Wiki page on GPS receiver functions and features<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====Beagle Conference System====<br />
<br />
* '''Title''': Use beagle to come up with a conferencing system for home users<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]<br />
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.<br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.<br />
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).<br />
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.<br />
** The software shall also provide for ways to chat (text) with the users.<br />
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====BeagleRC====<br />
<br />
* '''Title''': Use a beagle board to drive a remote controlled car.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos. <br />
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml<br />
* '''Expected results''':<br />
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.<br />
* '''Contact''': code at chrisd dot info<br />
<br />
====PREEMPT_RT====<br />
<br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
<br />
====USB Support in U-boot ====<br />
2nd [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.<br />
* Homepage: [[U-boot musb gadget support]]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/<br />
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).<br />
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.<br />
* '''Contact''': ddompe at IRC<br />
</font><br />
<br />
==== James ====<br />
<br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': To be Added...<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html<br />
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
<br />
====BeagleBot====<br />
1st [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Board powered robot<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]<br />
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...<br />
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]<br />
* '''Expected results''':<br />
** Partly autonomous robot<br />
** PC controlling of the robot<br />
* '''Contact''': antti at hervanta.com<br />
</font><br />
<br />
====Android Cupcake for BeagleBoard====<br />
<br />
* '''Title''': Android Cupcake for BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]<br />
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard. <br />
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]<br />
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====FreeBSD port to BeagleBoard====<br />
<br />
* '''Title''' : A port of FreeBSD-arm to the BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]<br />
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.<br />
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.<br />
* '''Contact''': AsqYzeron====FreeBSD port to BeagleBoard====<br />
<br />
==Judging==<br />
<br />
===Judges===<br />
* Jason Kridner (jkridner)<br />
* Koen Kooi (koen)<br />
* Dirk Behme (dirk2)<br />
* Steve Sakoman (sakoman)<br />
* Hunyue Yau (ds2)<br />
* Mans Rullgard (mru)<br />
* Gregoire Gentil (gregoiregentil)<br />
<br />
===Past Judges===<br />
* Robert Kuhn (robertk)<br />
<br />
===Rules===<br />
* Judges cannot participate in the contest.<br />
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.<br />
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.<br />
* All voting will be public and logged on this page.<br />
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.<br />
* To follow up on shipping details, contact ''beagleship at list.ti.com''.<br />
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.<br />
<br />
===Criteria===<br />
* All new content must be open source as determined by the OSI.<br />
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.<br />
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]<br />
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.<br />
* "Wow" or "coolness" factor from usefulness/user experience point of view<br />
* Overall quality of the submission<br />
* Technical complexity<br />
** "Coolness" of the technical solution, even if it isn't useful for all the masses<br />
** Amount of work needed, i.e. x hours or x days?<br />
* Angstrom recipe for image<br />
* Documentation for the demo<br />
* Running power consumption<br />
* Use of DSP and SGX<br />
* Ease of use<br />
<br />
===Contest #1===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-01-11<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]<br />
|3<br />
|<br />
|3<br />
|2<br />
|<br />
|3<br />
|2<br />
!13<br />
|-<br />
|[[BeagleBoard/contest#openGPS|openGPS]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]<br />
|1<br />
|<br />
|<br />
|1<br />
|3<br />
|<br />
|2<br />
!7<br />
|-<br />
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]<br />
|<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
!5<br />
|-<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
!17<br />
|-<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|2<br />
|2<br />
|3<br />
|4<br />
|3<br />
|4<br />
|3<br />
!21<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|<br />
|3<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!4<br />
|-<br />
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!3<br />
|-<br />
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|1<br />
|Monday, January 12, 2009<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|-<br />
|}<br />
:Congratulations ;-) [[User:RobertK|RobertK]] 11:30, 12 January 2009 (UTC)<br />
<br />
There is a nice [http://www.linuxdevices.com/news/NS6362979448.html LinuxDevices.com BeagleBot cruises on Linux] article about contest #1 winner, too.<br />
<br />
===Contest #2===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-03-01<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|6<br />
|7<br />
|5<br />
|7<br />
|3<br />
|5<br />
|<br />
!33<br />
|-<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|3<br />
|3<br />
|2<br />
|3<br />
|5<br />
|3<br />
|<br />
!19<br />
|-<br />
|[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]<br />
|1<br />
|<br />
|3<br />
|<br />
|2<br />
|2<br />
|<br />
!8<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|2<br />
|Monday, March 2, 2009 <br />
|[[BeagleBoard/contest#James|James]]<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|-<br />
|}<br />
<br />
==Other background==<br />
<br />
==Contest #1==<br />
<br />
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58<br />
<br />
==Contest #2==<br />
<br />
* [http://www.beagleboard.org/irclogs/index.php?date=2009-02-13#T15:35:43 IRC Log of discussion]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/661879a591dc396d Announcement at mailing list]<br />
* [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html Blog announcement]</div>Dirkhttp://elinux.org/BeagleBoard/contestBeagleBoard/contest2010-01-21T16:23:54Z<p>Dirk: Reformat approved project</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Image:beagle_first_place.png|thumb|right]]<br />
==Contest Announcements==<br />
===Sponsored Project Program===<br />
The [[BeagleBoard]] Software Design Contest has now been replaced with the [[BeagleBoard/contest#Contest_projects| BeagleBoard Sponsored Projects Program]] (formerly known as contest #3). The biggest difference is that we'll be giving 2 boards per week to projects as they are '''[[BeagleBoard/contest#Approved_projects|approved]]''', rather than waiting until they are completed. Also, successfully completed projects may be rewarded with higher-end BeagleBoard-derived systems, such as a [http://gumstix.com/store/catalog/product_info.php?products_id=229 Gumstix Palo43] or a [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book] (BeagleBoard based). You are encouraged to make your entries [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|now]].<br />
<br />
If your project is listed as a winner and you haven't received your board, check with ''beagleship at list.ti.com''.<br />
<br />
===Contest #2===<br />
<br />
''Contest #2 is finished. See [[BeagleBoard/contest#Winners_2|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html contest #2]. This contest is about giving away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to the winner and another one to the runner-up. [[BeagleBoard/contest#Judges|Judges]] will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, February 27, 2009 (afternoon) <br />
* '''Voting goes over weekend, end: Sunday, March 1, 2009 (afternoon)'''<br />
* Shipping board to winner: Monday, March 2, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get before this revision is publically available by DigiKey (~end of March 2009).<br />
</font><br />
<br />
===Contest #1===<br />
<br />
''Contest #1 is finished. See [[BeagleBoard/contest#Winners|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, January 9, 2009 (afternoon) <br />
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)<br />
* Shipping board to winner: Monday, January 12, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).<br />
</font><br />
<br />
==Project ideas==<br />
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:<br />
* Stable musb<br />
** ISOCH support<br />
** High-speed USB TV tuner support<br />
** Hot-plug support for OTG (host and client)<br />
* USB Digital TV tuner (either ATSC or DVB-T)<br />
** Hauppauge HVR950 suggested as reference<br />
* Projection TV coupled with the Pico<br />
* Audio record<br />
* Latest kernel version<br />
* USB camera support<br />
** gspca driver - need to validate with multiple cameras<br />
** <font color="#C0C0C0">UVC driver (I understood from Koen this is working)</font><br />
* Fixing bugs listed on code.google.com<br />
* Android port and various applications<br />
* <font color="#C0C0C0">EHCI support (done)</font><br />
* <font color="#C0C0C0">USB support in u-boot (partially done by first contest, but still needs work)</font><br />
* <font color="#C0C0C0">Consumer IR remote control via LIRC (already in feed; do 'opkg lirc')</font><br />
<br />
See also [[BeagleBoard/Ideas-2009]] for more ideas.<br />
<br />
==Contest projects==<br />
Please add your project you like to participate at Sponsored Projects Program (contest #3) to [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|Sponsored Projects Program projects]]. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1.1").<br />
<br />
===Sponsored Projects Program (Contest #3) projects===<br />
<br />
If you like to join Sponsored Projects Program (contest #3), please add your project here the same way like done for contest #1 and #2 below. If you participated already previous contests, please copy your project description to this contest, again. This will let everybody know that the project is still alive and that you want to participate Sponsored Projects Program.<br />
<br />
====Approved projects====<br />
From the project proposals, [[BeagleBoard/contest#Sponsored_Project_Program|approved projects]] will get a BeagleBoard Rev C at the '''beginning''' of their project to help them execute:<br />
<br />
{|border=1<br />
!Project<br />
!Approved<br />
!Comment<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Gregoire<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Revolt 2405|Revolt 2405]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Gentoo Linux ARMv7 support|Gentoo Linux ARMv7 support]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Accelerated_USB_Graphics_Adapter|Accelerated USB Graphics Adapter]]</font><br />
|<font color="#C0C0C0">Week 21</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#picoFlamingo|picoFlamingo]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle Synth |Beagle Synth]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#USB Scope |USB Scope]]</font><br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Irrlicht|Irrlicht]]<br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleHam|BeagleHam]]</font><br />
|<font color="#C0C0C0">Week 24</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Apertus_open_source.2Fhardware_cinema_camera|Apertus Digital Cinema Camera ]]<br />
|<font color="#C0C0C0">Week 25</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Handheld_Lab|Handheld Lab]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TCF_Agent_Port|TCF Agent Port]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Traveler|Beagle-Traveler]]</font><br />
|<font color="#C0C0C0">Week 27</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#OMAP Emulator|OMAP Emulator]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TUD:OS_on_Beagleboard|TUD:OS on Beagleboard]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#QEMUonARM|QEMUonARM]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#EGLIBC|EGLIBC Support]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#RT-Beagle|RT-Beagle]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ONAS|ONAS]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Math-NEON|Math-NEON]]<br />
|<font color="#C0C0C0">Week 32<br />
|<font color="#C0C0C0">5 votes<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Happiness_Device_for_Cerebral_Palsy_Kids|Device for Cerebral Palsy Kids]]</font><br />
|<font color="#C0C0C0">Week 32</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Turk|Turk Platform]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#hApplause|hApplause]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#eLazarillo|eLazarillo]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">1 vote</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#PREEMPT_RT|PREEMPT_RT]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#HDDM|HDDM]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleVision|BeagleVision]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#DJ Audio / Video Mixer|DJ Audio / Video Mixer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#schooldog|An individual lowcost schoolcomputer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Disko|Disko - UI Application Framework]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ESITeam|ESITeam]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#DVB-T_Receiver|DVB-T_Receiver]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">8 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#UPnP.2FDLNA_AV_client_renderer_and_transcoding_server|UPnP/DLNA AV client renderer and transcoding server]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Speed-Reader|Speed-Reader]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Arduino_hybrid_robot|Beagle-Arduino hybrid robot]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#XBMC_ARM_Port|XBMC Arm Port]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#GuideBeagle:_Portable_monocular_SLAM_system|Portable monocular SLAM system]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#MythBeagle|MythBeagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeaglePod|BeaglePod]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle_SecMon|Beagle SecMon]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Touchscreen_LCD_support| Touchscreen LCD support]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FMframe |FMframe]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleSCI |BeagleSCI]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Pictouch|Pictouch]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Fotogenic |Fotogenic]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyGTee|MyGTee handheld]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Tourister_using_Hand_Gestures_and_HMD_on_Beagleboard|Beagle Tourister]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Medical Notebook|Medical Notebook]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#miniECG|miniECG]]<br />
|<br />
|<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#remoteBillBoard|Remote Bill Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleWacom|Wacom Tablet driver for Beagle Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleLAB|BeagleLAB]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FETCH|FETCH]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#PupLC|PupLC]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#ArchMobile:_ArchLinux_ARM_Port|ArchMobile]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Homebrew_SmartPhone|Homebrew SmartPhone]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagleboard_Carputer|Beagleboard Carputer]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#AutoRobo|AutoRobo]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Walker|Beagle-Walker]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyoVox|MyoVox]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Eye|Beagle-Eye]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MART|MART]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#CamCast|CamCast]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#PortablePlateRec|PortablePlateRec]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Digital_Multimedia_Frame|Digital Multimedia frame]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#.28Speech.29_Scrambler_Beagle| (Speech) Scrambler Beagle]]<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Utility|Beagle Utility]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
Rule: In each week, each judge has two points (two "1") to enter for his favorite project. The two projects with the most votes will be approved. The plan is to have final decision every Friday morning.<br />
<br />
==== Revolt 2405====<br />
<font color="#C0C0C0"><br />
* '''Title''': Revolt 2405<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Revolt2405/<br />
* '''Short project description''': First mission of a first person shooter style game using Ogre3D.<br />
* '''Homepage''': http://www.dcbcyber.com/revolt2405/wordpress<br />
* '''Expected results''': Expected results would be to have a playable game demo using Ogre3D for rendering. There will be sound and music. For controls I want to have the option of using keyboard and mouse or using controls like those found on hand held gaming devices. We would also like to have this playable on a small LCD as well as on a monitor connected to the DVI port.<br />
* '''Contact''': n2vdy at yahoo dot com or dbatzle at dcbcyber dot com<br />
</font><br />
==== Touchscreen LCD support ====<br />
<br />
* '''Title''': Touchscreen LCD support <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': The project will add the touch screen support to Beagle board<br />
The following are the components that i am planning of using<br />
:*The LCD breakout board is http://www.sparkfun.com/commerce/product_info.php?products_id=8600<br />
:*The touch screen is http://www.sparkfun.com/commerce/product_info.php?products_id=8977<br />
:*The touch screen connector is http://www.sparkfun.com/commerce/product_info.php?products_id=9104<br />
<br />
Another option is buying a full LCD with touch screen option<br />
:*The product link is http://www.sparkfun.com/commerce/product_info.php?products_id=257.<br />
:*I would create a system and hardware like this video http://www.youtube.com/watch?v=foWnDZ3eQto&feature=related<br />
<br />
* '''Homepage''': http://pradheeptce.googlepages.com/ yet to be fully completed.<br />
<br />
* '''Expected results''': <br />
**Linux driver to add LCD with touch screen support<br />
**The breakout board(preferably single layered as it can be created at home)gerber for attaching with beagle which will be created using FreePcb(www.freepcb.com).You can see the photos of my RFID Based Access Control system project there.<br />
**Wiki page to describe the entire development method<br />
* '''Contact''': pradheep_sh[at]tce[.]edu<br />
<br />
==== Gentoo Linux ARMv7 support ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Official Gentoo Linux ARMv7 support<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Gentoo/<br />
* '''Short project description''': Build ARMv7 optimized packages and stages for Gentoo Linux created officially by Gentoo developers.<br />
* '''Description''': The project is for providing official support for ARMv7-based devices like the Beagleboard, we will provide stages and packages optimized for ARMv7 processors so any owner of an ARMv7 device can get an optimized system. At the moment Gentoo only provides and supports ARMv4 and ARMv5TE, therefore we would like to expand our official support to the more powerful ARMv7 subarchitecture.<br />
* '''Homepage''': http://www.gentoo.org/proj/en/base/embedded/ http://www.gentoo.org/doc/en/handbook/handbook-arm.xml http://www.gentoo.org/proj/en/base/embedded/handbook/<br />
* '''Expected results''': <br />
**Allow Gentoo users to have ARMv7 optimized stages and packages.<br />
**Document the installation on the provided boards.<br />
* '''Contact''': armin76[at]gentoo[.]org , solar[at]gentoo[.]org<br />
</font><br />
==== TUD:OS on Beagleboard ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TUD:OS on Beagleboard <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/TUD%3AOS+on+the+Beagleboard/]<br />
* '''Short project description''': Port the L4-Microkernel based TUD:OS Operating System to the Beagleboard<br />
* '''Homepage''': will follow<br />
* '''Description''': <br />
** '''What the heck?''' The TUD:OS operating system is a L4 microkernel based operating system, with good real-time and security properties, developed at the TU Dresden. <br />
** '''Microkernel-based''': The microkernel approach allows it to to reduce the trusted computing base (the amount of code that has to be trusted) by running small trusted applications side by side with non-trusted applications, all as unprivileged user mode applications. Further, it is possible to run real-time applications side-by side with non real-time applications. Also device driver run in user-mode and thus a crash of a device driver will not lead to an whole system crash and in the best case the driver can be restarted and the system will keep on running.<br />
** '''Familiar Environment''': While offering the above mentioned vantages, TUD:OS still offers a familiar environment by the possibility to run one or more instances of L4Linux. L4Linux is a Linux port the Fiasco microkernel which is binary compatible to native Linux but runs in deprivilieged usermode.<br />
** '''What do we get from this project?''' ''Briefly: A fundament to build embedded [realtime] systems [with a exceptionally small trusted computing base].'' Further a possibility to run multiple virtualized linux instances on the beagleboard. A good documentation how to build such systems. And last but not least a (hopefully cool ;) demo showing that it acutally works , perhaps like the one found at [http://demo.tudos.org demo.tudos.org] (somewhat outdated). <br />
*'''Contact:''' dvogt[at]os[.]inf[.]tu-dresden[.]de ([[User:Dvogt|Dvogt]])<br />
</font><br />
==== picoFlamingo ====<br />
<font color="#C0C0C0"><br />
* '''Title''': picoFlamingo <br />
* '''beagleboard.org project''': http://beagleboard.org/project/picoFlamingo/<br />
* '''Short project description''': A portable presentation system for the BeagleBoard and the picoDLP projector<br />
* '''Homepage''': http://papermint-designs.com/picoflamingo<br />
* '''Expected results''': <br />
** An application to perform presentations including 3D elements.<br />
** A basic hardware specification for a portable presentation system.<br />
** A remote interface for wireless control of the presentation.<br />
** A demonstration of the possibilities provided by the BeagleBoard, the OMAP 3 platform and the picoDLP.<br />
** Hopefully a lightweight 3D render engine for OpenGL ES 2.0.<br />
** A lot of fun!!!... <br />
* '''Contact''': dmo[at]papermint-designs[.]com<br />
</font><br />
==== Accelerated USB Graphics Adapter ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Accelerated USB Graphics Adapter <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': USB-attached Graphics Card supporting OpenGL acceleration for XFree86<br />
* '''Homepage''': http://www.employees.org/~mschulma/beagleboard/cerberus/<br />
* '''Expected results''': <br />
** Use the Beagleboard to attach another monitor to a PC running Linux, and run a graphics intensive application on the expanded virtual desktop without slowing the main CPU.<br />
* '''Contact''': mschulma [at] employees [dot ] org<br />
</font><br />
==== Apertus open source/hardware cinema camera ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Apertus Digital Cinema Camera<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Apertus/<br />
* '''Short project description''': A digital camera controler for an Elphel open hardware camera. The beagle board will be used as a realtime viewfinder unit and hardware camera control.<br />
* '''Homepage''': http://cinema.elphel.com<br />
* '''Expected results''': We intend on creating a community driven open source cinematic HD camera for a professional environment. <br />
The image is provided by an Elphel camera (elphel.com, open source camera). A beagle board would be connected to an elphel camera using ethernet. The beagle board runs a lightweight UI that allows user to view the live feed from the camera on an external display (dvi or s-video). It also allows to trigger recording and change camera settings using a user interface. The user interface is software based (on screen) + hardware based using buttons and knobs if possible (I2C interface of the beagle board would be used). This project will take 2-6 months to have visible results. The feasibility of this project has been discussed on the Beagle Board group, with positive answers (cfr. http://groups.google.fr/group/beagleboard/browse_thread/thread/6c55a10dd598bb6/e946107bd0a807b8#e946107bd0a807b8 )<br />
* '''Contact''': philippe dot jadin at gmail dot com<br />
</font><br />
==== FMframe ====<br />
<br />
* '''Title''': FMframe<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': FMframe is a picture frame application coupled with an rss news reader and clock/alarm functionality<br />
* '''Homepage''': not yet; in a few days I will try to come up with a website with some preliminary screenshots.<br />
* '''Expected results''': Plan is to make a picture frame application. Hardwarewise the beagle will connect to a DVI display. Softwarewise it will be a picture frame optionally with a clock on top of the photo (either a big semi-transparent clock in the center or a smaller clock in the corner). There will also be an alarm function which can play a preselected mp3 file when the alarm time is reached. Apart from showing pictures the frame can also show news from a user definable rss feed (e.g. cnn.com), Normally this will be in a ticker-tape at the bottom of the picture. When the user presses a button when a specific topic is shown the full message pops up. Probably there will be dedicated provisions for weather, giving the weather forecast if desired (in a style as done by the google weather widget). When waking up the frame can show the weather with the scrolling news or (user selectable) just a list of headlines. When the alarm is switched off the display acts like a regular photo frame again.<br>User interaction will be through a remote control. Alternate inputs could be touch screen (if I get access to an affordable one) or keyboard (less convenient but it does allow people without IR receiver to control the device.<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
<br />
==== BeagleSCI ====<br />
<br />
* '''Title''': BeagleSCI<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': BeagleSCI aims to use the BeagleBoard as a platform for scientific computation and instrumentation (SCI).<br />
* '''Homepage''': http://sourceforge.net/projects/beaglesci/<br />
* '''Expected results''': As a start, the initial goal would be to use the BeagleBoard as a logger of a seismometer. This would involve interfacing a 12-bit ADC chip and writing a driver for it. Data read from the instrument can be displayed by the BeagleBoard through a monitor or send the data to a remote computer via RS-232/RS-485.<br />
* '''Contact''': sherdon dot uy at gmail dot com<br />
<br />
==== Pictouch====<br />
<br />
* '''Title''': Pictouch<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Mobile and Projected Touch user interface<br />
* '''Homepage''': not yet<br />
* '''Expected results''': The goal is to build a new Tactile Interface system based on beagleboard and the DLP picoprojector. Currently, the project make the use of JavaFX to support Multi-Touch (and Multi-User) and of 2 basic webcam, in order to build a low cost gesture recognition system.In the classical case of use, the interface is projected onto a classical table.Users interact directly with their fingers on the projected interface.<br />
<br />
* '''Contact''': maxired at gmail dot com<br />
<br />
==== Fotogenic ====<br />
<br />
* '''Title''': Fotogenic<br />
* '''beagleboard.org project''': not yet - but project is already in progress<br />
* '''Short project description''': Bring network connectivity to plain old vanilla picture frames<br />
* '''Homepage''': www.sourceforge.net/projects/fotogenic<br />
* '''Expected results''': This project brings wired, WiFi and bluetooth connectivity and management to plain old picture frames. The project selects pictures from your photo database, resizes them for the picture frame's native resolution, embellishes them with web and home automation information sources before presenting them to the photo frame by making the BeagleBoard appear to be a USB pendrive...! Right click a photo on your laptop and select "Show on picture frame now!". Manage many photo frames centrally and much much more... Includes "wave gesture" interface to wave over picture frame for next photo... Also works with Eye-Fi SD memory cards to make photos appear on photoframe moments after taken...!!<br />
* '''Contact''': horse_dung at hotmail dot com<br />
<br />
==== Beagle Synth ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Synth<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-synth/<br />
* '''Short project description''': DSP MIDI synthesizer based around the beagleboard<br />
* '''Homepage''': http://code.google.com/p/beagle-synth/<br />
* '''Expected results''': Initially a basic MIDI controllable subtractive synth with 3 oscillators, low pass, high pass, and band pass filters, 2 envelope generators, and 2 LFO's. From there the intention is to add some type of control surface (either physical controls or perhaps a touch screen), some effects (phaser, distortion, reverb), and perhaps other types of synthesis options (FM, additive, maybe some type of patchibility). The result will be a fully featured MIDI instrument comparable to many commercial synths. This project is to be a learning experience with the intention of exploring using DSP for music synthesis. As of now this project is in the concept phase and is still in need of hardware for implementation.<br />
* '''Contact''': dpanseri [at] gmail [dot] com<br />
</font><br />
==== USB Scope ====<br />
<font color="#C0C0C0"><br />
* '''Title''': USB Scope<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': USB diagnostics to aid driver development for USB devices<br />
* '''Homepage''': none yet<br />
* '''Expected results''': This project will use the BeagleBoard as a USB proxy between any USB device and a host computer connected via the OTG port. This will allow the BeagleBoard to snoop, compare and modify USB traffic which can assist both commercial and open source development of drivers and diagnosis of issues. Other ideas could be examined such as a USB-TCP/IP-USB proxy to remotely connect USB devices. Open or free software equivalents exist, but hardware monitoring devices only exist as expensive commercial products. <br />
* '''Contact''': horse_dung at hotmail dot com<br />
</font><br />
==== Irrlicht ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Irrlicht<br />
* '''beagleboard.org project''': no<br />
* '''Short project description''': A fully-featured 3D render engine with ogl-es 1.x and 2.x support<br />
* '''Homepage''': http://irrlicht.sourceforge.net<br />
* '''Expected results''': <br />
** Hardware optimized core routines for optimal OMAP support<br />
** Support of ogl-es 2.x (the 1.x driver is reportedly running on the board)<br />
** Full framerate (60FPS) rendering of q3 alike scenes<br />
** The engine also offers SW rendering, allowing to target for other OMAPs as well, but would require more tweaking in the render optimizations<br />
** We can port one of the demo apps from our apps contest to show the full applicability <br />
* '''Contact''': hybrid[at]users[.]sourceforge[.]net<br />
</font><br />
==== BeagleHam ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleHam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleham/<br />
* '''Short project description''': Bringing the BeagleBoard to the world of Amateur Radio.<br />
* '''Homepage''': None at this time.<br />
* '''Expected results''': <br />
** AX.25 Packet support, enabling full APRS support (operating as tracker, fill-in or permanent digipeater, and KISS TNC).<br />
** Encode and decode of HF digital modes, using DSP functionality where possible:<br />
*** BPSK, QPSK 31/63/125/250<br />
*** Olivia<br />
*** WSPR/MEPT<br />
*** MT-63<br />
*** DominoEX<br />
*** RTTY<br />
*** Throb<br />
** CW encode and decode<br />
** Capability to display on small (sub-6-inch) screens for mobile and field use<br />
* '''Contact''': xunil at xunil dot net<br />
</font><br />
==== TCF Agent Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TCF Agent Port<br />
* '''beagleboard.org project''': http://beagleboard.org/project/TCF+agent+port/<br />
* '''Short project description''': Support remote debugging and run control by porting the Eclipse Target Communication Framework (TCF) Agent to beagleboard+Ångström<br />
* '''Homepage''': Not yet<br />
* '''Expected results''': <br />
** A working port of the TCF "Reference implementation of a target agent" to BB/Ångström<br />
** screenshots and information on the TCF: http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Project.html<br />
** TCF agent running on a beagle board would provide the host computer following capabilities (see link above for details):<br />
*** Run control of userspace processes and threads<br />
*** Breakpoints<br />
*** Registers<br />
*** Stack traces<br />
*** Memory access<br />
*** Processes - list, start, stop, attach and debug.<br />
*** Sys monitor - CPU and memory utilization info<br />
*** File System - browsing and copying files<br />
<br />
* '''Contact''': terrella at terrella dot mobi<br />
</font><br />
<br />
==== RT-Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Real-Time patch for the beagleboard<br />
* '''beagleboard.org project''': http://beagleboard.org/project/omap-rt-patch/<br />
* '''Short project description''': Porting the linux rt patch to the omap linux kernel and providing testing applications. This project is developed at the INSA of Rennes (Engineer school in FRANCE) to allow next year Real Time course to be run on the BeagleBoard.<br />
* '''Homepage''': http://sourceforge.net/projects/linux-omap-rt-p/<br />
* '''Expected results''': <br />
** Porting the linux real-time patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) to the linux omap kernel and providing recipes for openembedded allowing to build the patched kernel.<br />
** Providing testing applications allowing to evaluate the real-time behavior of the platform<br />
** Providing applications that could be used for teaching purposes<br />
* '''Current Results''':<br />
** patch-2.6.29.5-rt21 was modified to successfully patch linux-omap-2.6.29 (modified patch available through project page).<br />
** kernel compile and boots with minor error concerning two IRQs (72,73) <br />
* '''Contact''': piat_jonathan[at]users[.]sourceforge[.]net<br />
</font><br />
==== MyGTee ====<br />
<br />
* '''Title''': MyGTee <br />
* '''beagleboard.org project''': http://beagleboard.org/project/MyGTee/<br />
* '''Short project description''': A handheld device exploiting all the OMAP3530 capabilities<br />
* '''Homepage''': http://enco2009.webs.com/<br />
* '''Expected results''': I stage: building a prototype hopefully based on the BeagleBoard; II stage: the actual handheld that may allow for further software opensource development<br />
* '''Contact''': doctorc[at]o2[.]pl<br />
<br />
==== ONAS ====<br />
<font color="#C0C0C0"><br />
* '''Title''': ONAS<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ONAS/<br />
* '''Short project description''': An open source NAS<br />
* '''Homepage''': http://code.google.com/p/onas/<br />
* '''Expected results''': Development of a full featured NAS running Linux <br />
* '''Contact''': electrogeek[at]wp[.]pl<br />
</font><br />
==== Handheld Lab ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Handheld Lab<br />
* '''beagleboard.org project''': http://beagleboard.org/project/handheld_lab/<br />
* '''Short project description''': The goal of this project is to create a little, yet powerful, handheld laboratory with as much functions as possible. It will be easy of use thanks to the integrated LCD touchscreen and nice GUI.<br />
* '''Homepage''': http://www.mipixel.com/handheld-lab<br />
* '''Expected results''': First result will be working LCD showing oscilloscope. After this spectrum analyzer and logic analyzer. All this stuff will need extra electronics.<br />
* '''Contact''': fran[at]mipixel[.]com<br />
</font><br />
====Beagle Tourister using Hand Gestures and HMD on Beagleboard ====<br />
* '''Title''': Travel Buddy using Hand Gestures and HMD on Beagleboard <br />
* '''beagleboard.org project''': http://beagleboard.org/project/travelbuddy/<br />
* '''Short project description''': A device which will assist a traveller/tourist giving them mobile computing power and the following features: <br />
*1) A Compact HMD (Head mountable device) instead of the conventional projector (Problem of Projection Surface while on the move) <br />
*2) Use of standard cam for Image processing i.e recognising simple hand gestures to interact with the GUI seen in the HMD <br />
*3) Scanning of images (street name plates/hotel names/landmarks/book titles as indicated by user) to provide useful feedback data(directions/reviews/record *videos/take pictures/information) <br />
*4) Mode for Speech2text and text2speech conversion for inter-language communication. <br />
* '''Homepage''': Under Construction <br />
* '''Expected results''':<br />
*1) V-NAV: Virtual Navigator - Streaming Google Street View data according to your current location <br />
*2) ULA: Universal Language Assistant: Scan any text by positioning your fingers and the the scanned text is translated to your default language.<br />
*3) Say goodbye to the camera/ cell phone/tourguide/maps. Good platform for further expansion to include newer features. <br />
*4) Virtual Reality Mapping to the Real World: Overlay of relevant information on the on the HMD.<br />
* '''Contact''': sisilmet2000 at gmail dot com , dhairyadand at gmail dot com <br />
<br />
==== Happiness Device for Cerebral Palsy Kids ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Happiness Device for Cerebral Palsy Kids<br />
* '''beagleboard.org project''': http://beagleboard.org/project/HappyCP/<br />
* '''Project description''':<br />
It is an attempt to bridge the gap in communication between those affected by cerebral palsy and those not. The focus of the problem has been on facilitating communication in the emotional domain since this remains a completely unaddressed area. It is possible that some of the ensuing product functions will additionally facilitate communication problems in the physical domain, as well as be physically therapeutic for the cerebral palsy child in the manner of a comfort blanket. The basis of the product is an Emotional Language Protocol (elp) that works as its interface and is driven by four concurrently acting features - color, shape, motion and sound - corresponding to the sensory modes of the visual, the tactile and the aural. The interaction itself is facilitated by touch of varying intensities including pressing, thumping, squeezing, turning and, of course, by touching. Those not affected by cerebral palsy may additionally use speech along with touch. The interplay of this interface and interaction allows the cerebral palsy child to express his different needs and emotions to another person cerebral palsy or otherwise.Also, the device's mobile connectivity allows its users to communicate with someone far away<br />
* '''Homepage''': http://www.dhairyadand.com/Home/jellow<br />
* '''Expected results''': I have uploaded the basic designs at the above link to the homepage. The device is circular in nature with a touch screen where an interactive interface is used to display icons, objects, photos and other sharable action oriented stuff. The device has exchangable memory sticks which allow two or more device's to get connected and hence facilitating interactions. The result is to get a cerebral palsy kid out of his isolated environment, motivate him to communicate by making a device which will show him the joy of communicating.<br />
* '''Contact''': dhairya AT cyber DOT law DOT harvard DOT edu<br />
</font><br />
==== UPnP/DLNA AV client renderer and transcoding server ====<br />
<font color="#C0C0C0"><br />
* '''Title''': UPnP/DLNA AV client renderer and transcoding server <br />
* '''beagleboard.org project''': http://beagleboard.org/project/UPnP_AV_MediaServer/<br />
* '''Project description''':<br />
Enable the beagleboard as a fully featured UPnP AV rendering client, and as a UPnP AV (transcoding!) server. <br />
<br />
Work will be based upon vlc+djmount (for client side) and fuppes (for server side). Server side transcoding to be hardware assisted via hardware DSP codecs. Initial target for the transcoding server on beagleboard is to drive the Neuros OSD (an underpowered DM320-based device). <br />
<br />
* '''Homepage''': Will be an extension and complement to my work on the DM320-based Nueros OSD: http://osd.oddren.com<br />
* '''Expected results''': Beagleboard can act as either as rendering UPnP client, or as a transcoding UPnP server to drive weaker client devices like the Neuros OSD with their preferred streaming format.<br />
* '''Contact''': bmcarnes_beagleboard AT oddren DOT com<br />
</font><br />
==== Beagle-Traveler====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Traveler<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-traveler/<br />
* '''Short project description''': Automotive media and vehicle management controller. Comparable to BeaglesRide.org (no activity).<br />
* '''Homepage''': http://beagletraveler.wordpress.com<br />
* '''Expected results''': intergrate major automotive subsystem management and communications. Improved vehicle notification of subsystems status'. <br />
* '''Contact''': wheeler dawt larry (at) gmail dawt com<br />
**Please send sponsored information and project questions to the email address above.<br />
</font><br />
==== OMAP Emulator====<br />
<font color="#C0C0C0"><br />
* '''Title''': OMAP Emulator<br />
* '''beagleboard.org project''': http://beagleboard.org/project/OMAP+Emulator/<br />
* '''Short project description''': Emulator for rapid prototyping<br />
* '''Homepage''': no homepage yet<br />
* '''Expected results''': Open source implementation of an IDE environment for rapid code development and testing<br />
* '''Contact''': hwtester (at) myway (dot) com<br />
</font><br />
==== eLazarillo====<br />
<font color="#C0C0C0"><br />
[[File:Elazarillo.png|thumb|300px|eLazarillo sketch]]<br />
* '''Title''': eLazarillo (electronic helper for blind persons)<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': Gadget designed for blind persons or with vision problems. <br />
* '''Homepage''': http://elazarillo.blogspot.com/<br />
* '''Full description''':<br />
Lazarillo is a spanish word that means "blind person's guide" and this is the objetive of this project. This gadget will have features like reading non-braille books, assist to blind persons to get places like markets, drugstores, etc. (based on previous GPS tagged places and using google maps). Other functionalities will be spoken weather information, personal calendar, function keys, etc.<br />
<br />
The gadget will be voice controlled, will need GPS, 3G modem, camera and battery. Size will be 4x5 inches (approx.).<br />
<br />
* '''Expected results''': Open source hardware and software platform for blind persons gadgets. My device will have most of the above described.<br />
* '''Contact''': villanuevaborrego (at) gmail (dot) com<br />
</font><br />
<br />
==== QEMUonARM ====<br />
<font color="#C0C0C0"><br />
* '''Title''': QEMUonARM<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': QEMU on ARM. <br />
* '''Homepage''': http://elinux.org/QEMUonARM<br />
* '''Full description''':<br />
This project aims at resurrect and improve QEMU on ARM hosts.<br />
For more information: http://www.qemu.org<br />
* '''Expected results''': Demonstrate user mode and system mode examples, such as running some simple Linux applications or booting an i386 OS. If there's enough interest, making Wine and QEMU work together might be considered.<br />
* '''Contact''': laurent.desnogues (at) gmail (dot) com<br />
</font><br />
<br />
==== Math-NEON ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Math-NEON<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Math-Neon/<br />
* '''Short project description''': NEON optimized cmath like library <br />
* '''Homepage''': http://code.google.com/p/math-neon/<br />
* '''Full description''': <br />
This project aims to overcome the shortcomings of the VFP-lite based cmath implementation. It is targeted at games and other high performance low accuracy applications. The project will consist of C functions, for PC development, which mirror (as near as possible) the hand optimized NEON assembly routines. In order to gain the best performance i will make use of the NEON Unit's Integer and Floating point pipelines in conjunction with minimizing branches (where they cannot be precalculated on the ARM) and creating new algorithms. <br />
* '''Expected results''': Fast approximate implementations of trigonometric, exponential, logarithmic and power functions for use with future Beagleboard / Cortex A8 based projects. <br />
* '''Contact''': lachlan.ts (at) gmail (dot) com<br />
</font><br />
==== Medical Notebook ====<br />
* '''Title''': Medical Notebook<br />
* '''beagleboard.org project''': yet to register<br />
* '''Short project description''': The Ultimate Notebook for Hospitals<br />
* '''Homepage''': coming soon...<br />
* '''Full description''': <br />
A handheld device to improve hospital functionality/efficiency. To add intelligence to the mundane hospital softwares. <br />
Features are:<br />
<br />
View and Update Patient status, medical history, medication details, appointments, billing - stored as a database in central server.<br />
<br />
Touchscreen with handwriting recognition & hand support pad for data entry.<br />
<br />
Light Weight < 1kg<br />
<br />
VoIP, video conferencing/recording for consulting other doctors <br />
<br />
Wifi, bluetooth & ethernet support <br />
<br />
Docking station for charging<br />
<br />
Support for usb keyboard & mouse on docking station<br />
<br />
* '''Expected results''': <br />
<br />
1) Driver for touch pen tablet with support for hand writing recognition<br />
2) Porting of VoIP software for beagleboard (H.323 ???)<br />
3) Video conferencing software for beagleboard<br />
4) WiFi ?& bluetooth support on beagle board<br />
5) Speech recogntion software for beagleboard<br />
6) Entry of beagle board based products to hospital autmation market<br />
7) Improved, efficient & intelligent patient care in hospitals<br />
<br />
* '''Contact''': noorshaheen.m.n (at) gmail (dot) com<br />
<br />
==== EGLIBC ====<br />
<font color="#C0C0C0"><br />
* '''Title''': EGLIBC support<br />
* '''beagleboard.org project''':<br />
* '''Short project description''': Use EGLIBC as system library for beagleboard project in OpenEmbedded.<br />
* '''Homepage''': www.eglibc.org<br />
* '''Expected results''': EGLIBC becomes the default system library on the distribution and can be used instead of glibc<br />
with the newly added configurability support to selec/deselect features. I would also like to make it compile as pure thumb2<br />
code.<br />
* '''Contact''': raj[.]khem[at]gmail[.]com<br />
</font><br />
==== miniECG ====<br />
* '''Title''': miniECG<br />
* '''beagleboard.org project''': http://beagleboard.org/project/miniECG/<br />
* '''Short project description''': Little device that cares for heart when heart patients are busy carrying out their duties<br />
* '''Homepage''': http://code.google.com/p/miniecg/<br />
* '''Full description''': <br />
miniECG is a wearable device that monitors ECG signal, processes it and can transmit it over wireless internet connection to doctors clinic. It has following features are:<br />
(all the hardware components required are available through digikey.com including LCD and touch screen)<br />
<br />
1) It has touch screen that enable user to give commands like store, display old ECG data, transmit, etc. Device also has a LCD display which is used to display ECG waveform.<br />
<br />
2) A tiny server runs on device that enables doctor to login to device any time he wants and extract patients ECG data. The device is connected to internet through wireless USB dongle. <br />
<br />
3) DSP core does the job of compressing ECG signal, doing PCA (principal component analysis) on ECG signal, detect QRS, measuring heart beats and digital filtering.<br />
<br />
4) DSP along with Cortex A8 runs algorithm that determines critical state of heart by doing feature extraction over ECG signals. It also does PCA over set of stored ECG signal to obtain information about any substantial drift in normal functionality of heart. <br />
<br />
5) Wireless USB dongle provides connectivity to internet and data is transmitted over internet as per schedule programmed into the device. ECG signal can also be streamed over internet using this dongle. <br />
<br />
6) Keyboard & mouse (USB) interface is provided for more flexibility and quick access. LCD monitor interface is also be provided. Key-board, mouse and LCD monitor interface will work only when device is powered by adaptor. For device powered by battery only input option is touch screen and only output option is LCD display.<br />
<br />
7) Device also has small software support to give reminder on when to consume which drug. The prescription of drug and its timing information is feed in as per doctors advice. (keyboard and mouse interface with miniECG can be of great advantage here)<br />
<br />
8) USB memory devices will be used to store ECG data.<br />
<br />
9) miniECG will be dual powered. It can be powered by adaptor as well as with rechargeable battery. <br />
<br />
Website link has block diagram of miniECG and also picture of ECG pre-amplifier which is already designed. In future all the source codes will be uploaded on the link as and when available.<br />
<br />
* '''Expected results''': a) Ability to login from remote PC onto miniECG and read data b) Should be able to send stored data or stream live ECG signal over internet c) Robust interface of LCD & touch screen with controller d) Data storage and retrieval from USB storage device e) Successful implementation of DSP algorithms for feature extraction, PCA, QRS detection, filtering and compression. f) As the whole device is battery powered, software & driver which are very specific to the desired application should only be installed & made working. Thus providing a low power system architecture. <br />
<br />
* '''Future Work''': Once the desire basic funtions of ECG storing, retrieval and transmitting is meet, miniECG can be programmed into miniPA (mini personal assistance) mainly targeting senior citizens. miniPA will have much advanced features that can help them elderly person in their day-to-day activity.<br />
* '''Contact''': mehta.nandish (at) gmail (dot) com<br />
<br />
<br />
==== remoteBillBoard ====<br />
* '''Title''': Remote Bill Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/remoteBillBoard/<br />
* '''Short project description''': Video bill boards, remotely controlled via web over a 3G modem<br />
* '''Homepage''': http://www.greensoftware.net/remoteBillBoard<br />
* '''Full description''': <br />
Play HD video on billboards, remotely manage the billboards, upload new advertisements, remove old ones etc..<br />
<br />
<br />
* '''Expected results''': <br />
a) 3g modem support, so flexiblity.<br />
b) a full working web based system<br />
<br />
* '''Future Work''':<br />
a) a more advanced desktop application to replaced the web based solution.<br />
<br />
* '''Contact''': ahmad.mushtaq (at) gmail (dot) com<br />
<br />
<br />
==== Turk ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Turk Platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Turk/<br />
* '''Short project description''': A wireless dynamically-mappable interface platform for small devices<br />
* '''Homepage''': http://www.turkinnovations.com/<br />
* '''Full Description''': Turk will be an open-source wireless interface platform that allows interfacing of small wireless (Zigbee or Wi-Fi enabled) devices through a dynamic mapping framework and web interface. Developers can implement their device's protocol easily through small user-space drivers called 'Gadgets' and host them on our server. The platform is then capable of automatically downloading and starting appropriate gadgets for new devices that are compatible with the basic Turk protocol. Gadgets reveal their services to the user and other gadgets through our growing library of data endpoint types (such as colors, URLs, booleans, xml strings) and user controls (like sliders, switches and color pickers), and can then be connected to each other through a themable web interface.<br />
<br />
* '''Expected results''': <br />
**A platform that allows developers to write simple user-space drivers that expose interfaces through XML-RPC<br />
**A web interface and remote configuration capabilities through a central server. <br />
**A simple and well-tested protocol and driver for a kernel-managed point-to-multipoint Zigbee network. <br />
**More hardware connectivity besides the Wi-Fi and Zigbee interfaces will hopefully be developed by collaborating with other beagleboard projects and developers.<br />
* '''Contact''': rob.odwyer [at] turkinnovations [dot] com<br />
</font><br />
==== BeagleWacom ====<br />
* '''Title''': Wacom Tablet driver for Beagle Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-wacom/<br />
* '''Short project description''': Linux drivers of wacom tablet ported for Beagle Board<br />
* '''Homepage''': <br />
* '''Full Description''': beagle-wacom will be port of linux drivers for configuring & running wacom tablets with the beagle board. The idea is to have support for wacom-components, so that they can be used by OEMs of beagleboard based products using linux as their OS<br />
<br />
* '''Expected results''': <br />
**easy integration of wacom tablet with Beagle Board. <br />
**OEMs of beagleboard based products using linux as their OS can integrate wacom-components in their product with minimal fuss<br />
* '''Contact''': najath [at] gmail [dot] com<br />
<br />
<br />
====hApplause====<br />
<font color="#C0C0C0"><br />
* '''Title''': hApplause<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Hardware Platform that You can use to play with Audio Synthesis<br />
* '''Homepage''': not yet<br />
* '''Description''': ''hApplause'' will be multi-functional flexible audio hardware platform. The goal is to make a tool that can allow to develop audio software and hardware (e.g. DSP synthesizers, FX units, hardware expansion boards, etc.). The concept is inspired by [http://www.chameleon.synth.net/ Chameleon] and [http://www.ucapps.de/ MIDIbox]. ''BeagleBoard'' will give ''Chameleon'' like software flexibility while planed hardware with ''Expansion Interface'' and ''Audio Multiplexer'' will give ''MIDIbox'' like hardware flexibility.<br />
*; Hardware features<br />
*: Audio Stereo In/Out<br />
*: MIDI In/Out/Thru<br />
*: General purpose USB port - function depends on user application<br />
*: General purpose SD/MMC Card (e.g. for user data storage) - function depends on user application<br />
*: Front panel interface (1U rack version) with:<br />
*:* LCD<br />
*:* Volume potentiometer<br />
*:* Headphones jack<br />
*:* Power switch with LED indicator<br />
*:* programmable rotary encoders (5 are planed)<br />
*:* programmable buttons and LEDs (12 are planed)<br />
*: Expansion Interface with audio signal buses (1-4 planed, depends on final implementation) and data/command bus (I2C and/or CAN)<br />
*: Audio Multiplexer for flexible routing of audio signal between ''BeagleBoard'', ''Audio In/Out'' and ''Expansion Interface''<br />
*: USB and RS232C for developers<br />
*; Software features<br />
*: All hardware will be fully accessible from ''BeagleBoard'' by API<br />
*: hApplause OS is planed (abstract layer over hardware, user program loading, self configuration on power on)<br />
* '''Expected results''':<br />
*# 19" 1U rackmount unit ready to play with.<br />
*# Libs and additional software for developers (at least API for hApplause's hardware)<br />
*# Example implementation of software synth<br />
*# Single size eurocard unit for 3U rack, like in [http://www.doepfer.de/a100e.htm Doepfer A-100 System] modules<br />
* '''Contact''': tawezik at gmail dot com<br />
</font><br />
==== BeagleLAB====<br />
* '''Title''': BeagleLAB<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleLAB/<br />
* '''Short project description''': BeagleLAB is an Embedded developer's workbench comprising of must-have hardware/software utilities.<br />
* '''Homepage''': http://code.google.com/p/beaglelab/<br />
* '''Expected results''': <br />
:* A PC free host providing a development environment based on beagle board (running ubuntu 9.04 or later)<br />
:* Host environment with software applications and hardware interfaces to substitute oscilloscope, multimeter & logic analyzers<br />
:* GNOME widgets (software apps) & Linux device drivers for capturing data,storing,comparing and visualization<br />
:* Legacy ports like the serial, parallel ports for device interfacing and control<br />
:* Making an embedded developer's life easier and workbench neater<br />
* '''Contact''': amarendermail[at]gmail[dot]com and saurabhg84[at]gmail[dot]com<br />
<br />
====PREEMPT_RT====<br />
<font color="#C0C0C0"><br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
</font><br />
<br />
====HDDM====<br />
<font color="#C0C0C0"><br />
* '''Title''': HDDM<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/HDDM/]<br />
* '''Short project description''': A multimedia system based on OMAP and linux.<br />
* '''Homepage''': Under construction<br />
* '''Expected results''': Beagleboard as a control center for home theatre system<br />
* '''Contact''': grover.ankur (at) gmail (dot) com<br />
<br />
Note from Dirk: Please see [http://www.syspire.de/node/3 Embedded Mediacenter], too (sorry, German only, use Google translate if needed).<br />
</font><br />
====BeagleVision====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleVision<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beaglevision/<br />
* '''Short project description''': An efficient object recognition framework <br />
* '''Homepage''': http://code.google.com/p/beaglevision/<br />
* '''Description''': BeagleVision will be a fast object recognition framework. The aim of the project is to have a hardware optimized implementation (utilising the DSP and NEON) of state-of-the-art local feature detectors and descriptors on the Beagle Board. BeagleVision will include [http://www.cs.bris.ac.uk/Publications/pub_master.jsp?id=2001018 our recent work] on efficient feature detectors and descriptors, other well-known algorithms (e.g. FAST corner detector and SURF), and efficient matching algorithms for very large datasets (>1M images).<br />
* '''Expected results''':<br />
:* An open source library for developers (a project hosted on code.google.com)<br />
:* A sample application for building recognition in a city scale dataset, to show how: to add new images to the dataset, to use it for location based services, and how to reduce the search time if a GPS is available to get geolocations<br />
:* A wiki for interested developers<br />
:* Reporting the running times of new algorithms on OMAP (as a benchmark) in scientific publications<br />
* '''Contact''': m.ebrahimi at ieee dot org<br />
</font><br />
====Beagle-Arduino hybrid robot====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Arduino hybrid robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Beagle-Arduino+hybrid+robot/<br />
* '''Short project description''': A robot using a Beagleboard for high-level processing and Arduino for low-level control<br />
* '''Homepage''': http://mechomaniac.com/robots<br />
* '''Description''': The Beagle-Arduino robot will use a Beagleboard for high-level robot functions:<br />
** image processing<br />
** artificial intelligence<br />
** speech synthesis<br />
** voice recognition<br />
** internet connectivity<br />
And an Arduino for low-level functions:<br />
** motor / servo control<br />
** sensor input & output<br />
** battery monitoring<br />
The two microcontrollers will be connected by USB, along with a USB webcam mounted on a servo pan/tilt mechanism, and a USB wifi dongle for internet connectivity. Basic tank treads will provide movement, possible being replaced by servo-based legs for a humanoid or dog form.<br />
* '''Expected results''':<br />
:* Easy physical interfacing to the Beagle without having to design and build special expansion boards<br />
:* Image processing using OpenCV with a USB webcam<br />
:* Speech synthesis and voice recognition<br />
* '''Contact''': tim at mechomaniac dot com<br />
</font><br />
<br />
====DJ Audio / Video Mixer====<br />
<font color="#C0C0C0"><br />
* '''Title''': DJ Audio / Video Mixer* '''Contact''': <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/djvideomixer/]<br />
* '''Description''': This is a small, Touch LCD controlled DJ Mixer, which not only is great as a nightclub tool for playing audio -not only reproducing music, actually '''''playing''''' with it-, but also has high end video playback capabilities, thus making it an all-round experience both for the DJ and the audience. It will bring all the experience of professional DJ mixers to users, while being portable, and which when coupled with either a normal projector, or even better, with a PicoProjector, makes a whole experience for audio and video playback in Discos, Bars, Lounges, to mention just a few possible applications. You can even use for your own parties, and it will rock!<br />
* '''Homepage''': [http://code.google.com/p/djvideomixer/]<br />
* '''Expected results''': <br />
** Audio playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Video playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Audio/Video synchronization, allowing song change, video change, etc.<br />
** High end, professional DJ-Mixer audio effects.<br />
** User interface based on LCD and with touchscreen capabilities.<br />
* '''Contact''': jaime_dot_aranguren_at_ieee_dot_org<br />
</font><br />
====schooldog====<br />
<font color="#C0C0C0"><br />
* '''Title''': schooldog<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/schooldog/]<br />
* '''Description''': The purpose is to make an ''off the shelf'' low cost schoolcomputer that can be used on various levels of education. It will be small so students can take it with them and the school just has to provide for input / output items. This way even people that cannot afford laptops can participate in the digital era or schools can provide a robust and good machine for studypurposes.<br />
* '''Homepage''': [http://schooldog.wickedmind.net]<br />
* '''Expected results''': <br />
** Educational linuxbased OS, from USB sticks and SD Cards.<br />
** more general use of BeagleBoard and more public awareness for the powerful small computer.<br />
** Affordable,individual and steady study enviroment<br />
<br />
* '''Contact''': wickedmind<br />
</font><br />
====Disko====<br />
<font color="#C0C0C0"><br />
[[File:Disko_logo.png|thumb|200px|UI Application Framework]]<br />
* '''Title''': Disko - UI Application Framework<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Disko/<br />
* '''Short project description''': Disko is a Linux-based toolkit to build touchscreen- and remote-controllable ui applications. It contains native OMAP framebuffer support and the media content is DSP-accelerated by GStreamer (TI-Codecs).<br />
* '''Homepage''': http://diskohq.org<br />
<br />
* '''Expected results''': Expected result is broad support of Disko by developers of user interfaces and applications for embedded devices.<br />
** SIP - IP telephony support delivered by pjsip and minisip <br />
** Gstreamer - to add an alternative to the xine library and to add the TI Codecs supplied for the DSP.<br />
** Webkit - the great embedded browser OWB of Pleyo (planned for Disko 1.7)<br />
** SVG - at least one SVG engine to have an alternative to Flash. Initial work has already been done at MadButterfly (planned for Disko 1.7) <br />
* '''Contact''': gmadaus [at] berlinux-solutions dot de or mspringer [at] berlinux-solutions dot de<br />
</font><br />
====FETCH====<br />
* '''Title''': FETCH - FPGA enabled Tool Contol Host<br />
* '''beagleboard.org project''': http://beagleboard.org/project/FETCH<br />
* '''Homepage''': http://code.google.com/p/fetch/<br />
* '''Short project description''': A host with a web interface for easy configuration and control of connected tools. The device may also be controlled through a PSTN network using DTMF tones. The BeagleBoard will act as the main server and will also be the host interface for the connected FPGA for the purpose of evaluating the IPs developed on the FPGA.<br />
* '''description : Phase 1 '''<br />
***1) Server capability -- all services (except VNC) to be launched through inetd so that they are started on an on-demand basis. <br />
***-- http server for configuration pages <br />
***-- ssh server (the ssh suite in particular including scp etc.. so that an ftp server can be avoided) for remote login. <br />
***-- bootp server for bootstaping machines on my home network. <br />
***-- VNC for GUI sessions :) <br />
***-- CUPS for network printing <br />
***-- NetHack server :D <br />
***2) Tool Control <br />
***-- The term "Tool Control" here refers to automation of connected tools and Phase 1 of the project will demonstrate this by automation in home (eg. computer, printer, scanner on/off --> (the contoller board with the relays is complete :) ), these devices may be contolled over the internet or PSTN network ) The system will also be hooked to the home electrical network that will enable control over home appliances. A special mode called " Home Alone" will switch on/off lights randomly when no one is at home to give the illusion that the house is occupied ( and hence protect from thefts ;) ). The current relay boards developed use a UART (for RS232 protocol) for control of the equipment but it is planned to use the CAN interface (under developement ) so that longer distances can be covered. <br />
***3) The BeagleBoard will act as a host interfacefor a Nexys2 Xilinx FPGA board and will be used to evaluate the IPs deployed on it. This feature is sort of a tester for the FPGA. <br />
**'''Phase 2 ''' ( only after Phase 1 is completely functional :) ) <br />
***1) CAN interface for the controller nodes replacing the RS232 connections<br />
***2) mgetty (for faxes) and asterisk (VOIP) may be added to the server.<br />
* ''' Contact : ''' akshat dot g dot gupta [at] gmail dot com<br />
<br />
==== ESITeam====<br />
<font color="#C0C0C0"><br />
* '''Title''': ESITeam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ESITeam/<br />
* '''Short project description''': It's a robotic soccer team with vision and intelligence distributed through the use of wireless communication (Zigbee) between robots and PC.<br />
* '''Expected results''': The expected results would have a running and competitive team for the RoboCup's championship this year.<br />
<br />
* '''Contact''': registrosvmora at gmail dot com<br />
</font><br />
==== PupLC====<br />
* '''Title''': PupLC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/PupLC/<br />
* '''Short project description''':Open source control of PLC operated equipment.<br />
* '''Homepage''': No homepage yet<br />
* '''Expected results''': <br />
:*PupLC will be an open source PLC controller. The user will be able to control the PLC's autonomously or by direct control. The direct method will allow the user to change equipment status using a touch screen lcd. The PupLC will control all aspects of the operating equipmet (ie. setpoints, red-hand settings, shutdowns, etc.) Additionally, 24-hours of accumulated system data will be saved to disk and can be accessed via ftp for analysis off-site.<br />
* '''Contact''': alcpo729[at]tds[dot]net<br />
<br />
====Speed-Reader====<br />
<font color="#C0C0C0"><br />
* '''Title''': Speed-Reader<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Speed-Reader/<br />
* '''Short project description''': Speed-Reader is an audio book reader that gives the listener control of the speaker rate.<br />
* '''Homepage''': http://www.nerd1951.com/?page_id=72<br />
* '''Description''': Speed reader allows an audio book to be played back with faster or slower speaker rates. A user interface gives the listener realtime control of the speaker rate. Speed-Reader uses digital speech signal processing to accomplish low distortion timescale modification of speech in real time. Timescale modification of speech is accomplished by selectively repeating segments of speech to slow down the speaker rate or deleting selected speech segments to speed up the speaker rate. Digital signal processing is used to determine which speech segments are candidates for repetition or deletion.<br />
* '''Expected results''':<br />
***--Realtime (during playback) timescale modification of digitized speech using the C64++ DSP<br />
***--Initially read digitized speech from the SD card interface<br />
***--Audio output using the Beagleboard stereo out<br />
***--Initially user interface provided via RS-232 interface<br />
* '''Contact''': harvey dot sugar at nerd1951 dot com<br />
</font><br />
<br />
====DVB-T Receiver====<br />
<font color="#C0C0C0"><br />
* '''Title''': DVB-T Receiver<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': The DVB-T Receiver project aims to implement a fully tunable DVB-T Receiver on the Beagle Board.<br />
* '''Homepage''': Will be launched in the near future (at blog.arsln.org)<br />
* '''Description''': The DVB-T receiver is a senior graduation project that has to be completed in one year (until Summer 2010). It will be a fully tunable DVB-T receiver. It will compatible to receive digital terrestrial TV & radio stations. The goal is to show the capabilities of the Beagle Board and build a DVB-T system from the scratch. The input will be through a ADC daughter-board that is plugged to the USB port. The output will be via the USB port(for portable devices i.e Netbook) or DVI-D. <br />
* '''Expected results''':<br />
***--Capturing broadcast signals(DVB-T) and convert them to discrete time signals<br />
***--Demodulate and encode the incoming signal<br />
***--Video output using the Beagleboard's DVI-D port or via the USB port for portable devices<br />
* '''Contact''': ftharsln at gmail dot com , sulaya05 at gmail dot com<br />
</font><br />
<br />
====ArchMobile: ArchLinux ARM Port====<br />
<br />
* '''Title''': ArchMobile<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/AM/ AM]<br />
* '''Short project description''': ARM Port of the x86-Linux Distribution ArchLinux<br />
* '''Homepage''': [http://www.archmobile.org ArchMobile]<br />
* '''Expected results''': Fully working ArchLinux with X and all other features.<br />
* '''Contact''': rotter.manuel@gmail.com or naeg on Freenode<br />
<br />
==== MythBeagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': MythBeagle<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': MythBeagle aims at bringing MythTV to the beagle; both frontend and backend, including plugins (as far as possible)<br />
* '''Homepage''': not yet; <br />
* '''Expected results''': <br />
** OE recipes for mythtv 0.22, mythplugins 0.22 and whatever might be needed to get things going (including bringing required recipes to the latest version where needed/possible)<br />
** An image for SD card to allow easy install, or a script or recipe to allow easy installation<br />
** some additional configuration notes (configuring MythTV is somewhat a pain...)<br />
** setup should also allow using the beagle only as frontend or backend<br />
* '''Status''': mysql5 recipe has been created (mythtv 0.22 won't use mysql4); recipes for mythtv are there, except for mythweb, documentation/installation work has started;<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
</font><br />
<br />
==== Homebrew SmartPhone ====<br />
<br />
* '''Title''': HomeBrewSmartPhone<br />
* '''beagleboard.org project''': http://code.google.com/p/hbpd<br />
* '''Short project description''': HomeBrewSmartPhone is a project to use the beagleboard to create a community-buildable mobile phone that is powerful enough to also run as a Desktop PC.<br />
* '''Homepage''': http://lkcl.net/reports/hbp <br />
* '''Expected results''': <br />
*** A device capable of Digital Voice as well as Data / Internet Access.<br />
*** A device capable of shutting down into low-power mode and successfully resuming on incoming calls.<br />
*** RF-protected audio circuits that don't have howling feedback from the 3G/GSM Radio module.<br />
*** Full disclosure of all build components (schematics, BOM) under free software licenses.<br />
*** Full documentation of all hardware interconnections<br />
*** Creation of a <b>basic</b> demonstration image that will allow other software developers to participate very early on<br />
*** Addition to the http://handhelds.org site for developers to create GUI-based distros<br />
* '''Contact''': lkcl@lkcl.net or use http://lkcl.net contact box<br />
<br />
==== XBMC ARM Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': XBMC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/XBMC/<br />
* '''Short project description''': XBMC Is a full-feature home-theater application that works on a variety of platforms and operating systems<br />
* '''Homepage''': http://xbmc.org<br />
* '''Expected results''': <br />
*** Feature parity with XBMC x86 and ppc<br />
*** Usage of OpenGL ES 2.0<br />
* '''Contact''': Cory Fields: theuni @at@ xbmc .dot. org<br />
</font><br />
<br />
==== Beagleboard Carputer ====<br />
<br />
* '''Title''': Beagleboard Carputer<br />
* '''beagleboard.org project''': http://beagleboard.org/project/bbcarputer<br />
* '''Short project description''': The Beagleboard Carputer aims to create a fully-integrated system that will feature touchscreen LCD, Bluetooth and USB connectivity, GPS Navigation, Phone features, Wifi, Voice recognition, Multimedia entertainment.<br />
* '''Homepage''': http://bbcarputer.codeplex.com<br />
* '''Expected results''': Provide a fully-integrated system that will feature:<br />
*** 7in touchscreen LCD<br />
*** Wireless connectivity<br />
*** Usb connectivity<br />
*** GPS Navigation<br />
*** Phone features<br />
*** Voice recognition<br />
*** Multimedia entertainment<br />
*** Opensource Application Suite<br />
*** Games<br />
* '''Contact''': Joey Mar Antonio: joeymar.antonio @at@ awsol-i .dot. com<br />
<br />
==== GuideBeagle: Portable monocular SLAM system ====<br />
<font color="#C0C0C0"><br />
* '''Title''': GuideBeagle<br />
* '''beagleboard.org project''': Not yet available.<br />
* '''Short project description''': GuideBeagle is a portable localization and mapping system based on monocular vision. Such a system can be used, among other things, to build:<br />
:*Interactive visitor guidance systems for museums and stores.<br />
:*Artificial Reality tools and games.<br />
:*Mobile robot control systems.<br />
:*Surveillance and security related applications.<br />
:In other words: it solves a Simultaneous Localization and Mapping (SLAM) problem using a single camera as sensor, working on-line, and producing maps with high-level geometrical information (i.e. not just simple punctual visual landmarks on space). It will be based on recent research on the fields of Computer Vision and Mobile Robotics.<br />
* '''Homepage''': http://sites.google.com/site/guidebeagle (This page will be enhanced uninterruptedly.)<br />
* '''Expected results''': <br />
**Mapping --- The final system will allow an user to move by an environment like an office or a small apartment and build a map of it similar to a 3D model with planes and textures, as used in Computer Graphics.<br />
**Localization --- After a map is built, the user can move around the environment, and the system will interactively estimate the geometric location of the camera and the direction it is heading, based on images continuously obtained from the camera.<br />
**Image processing --- Building this system will require the coding of image processing tools that may be useful to many other image processing applications based on the Beagle Board. Some examples are feature detectors and descriptors, edge detectors, template matching by normalized cross-correlation and the Discrete Fourier Transform.<br />
* '''Contact''': nwerneck@gmail.com or nwerneck@usp.br<br />
</font><br />
<br />
==== AutoRobo ====<br />
<br />
* '''Title''': Development of an autonomous robotics platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/autorobo/<br />
* '''Short project description''': Design, prototype and develop an autonomous aerial vehicle system around BeagleBoard, allowing experimentation with real-time control and computer vision algorithms.<br />
* '''Philosophy''':<br />
:* make robotics and embedded control accessible and fun<br />
:* stimulate cross-field learning and collaboration<br />
:* leverage modularity and reuse to get more done, quicker <br />
* '''Technical goals''':<br />
:* develop generalised physics model for eg computing optimal PID controlled motor outputs<br />
:* decouple high-update-rate sensors from lower-rate output control<br />
:* employ OpenCV for visual tracking/SLAM/feature detection<br />
:* build lean tracked (land) vehicle<br />
:* build lean quad-rotor (air) vehicle<br />
:* use a shared, modular code-base and electronics platform (Beagle and IGEPv2) <br />
* '''Homepage''': http://code.google.com/p/autorobo/<br />
* '''Expected results''': Initial bringup of a tracked vehicle via dual-motor controller via Beagle's PWM outputs. Utilisation of 3-axis accelerometer and 3-axis gryo via I2C and/or SPI buses, enabling more advanced control<br />
* '''Contact''': ''daniel (dot) blueman (at) gmail (dot) com''<br />
<br />
==== Beagle-Walker ====<br />
<br />
* '''Title''': Design of a automatic dog-walker robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleWalker/<br />
* '''Short project description''': Develop an autonomous dog-walker robot<br />
* '''Homepage''': http://code.google.com/p/beaglewalker/<br />
* '''Expected results''': <br />
**The main goal of the system is analyze the feedback between the dog and the robot to track where the dog is going and where the robot should go.<br />
**Let the dog walk only in places previously programmed by the dog's owner making use of basic SLAM algorithms. <br />
**avoid any obstacles/vehicles.<br />
* '''Contact''': ''darthdj at gmail dot com''<br />
<br />
==== nullDC / Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nullDC<br />
* '''Expected results''': For the contest: A working build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
</font><br />
<br />
==== MyoVox ====<br />
* '''Title''': MyoVox<br />
* '''beagleboard.org project''': <br />
* '''Short project description''': <br />
* '''Homepage''': <br />
* '''Expected results''': <br />
* '''Contact''': smcgill3 [at] seas[.]upenn [.] edu<br />
<br />
==== Beagle-Eye ====<br />
<br />
* '''Title''': Beagle-Eye<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle-Eye/ Beagle-Eye]<br />
* '''Short project description''': A beagle-eyed guide for the visually challenged.<br />
<br />
* ''' Hardware''':<br />
** A pair of calibrated USB cameras, mounted on the user's shoulders, such that the combined field of view covers at least 180 degrees.<br />
** One or more linear actuators connected through RS-232, situated on one of the user's limbs.<br />
** Stereo headphones.<br />
** USB GPS Dongle.<br />
<br />
* '''Description''':<br />
** Low frame rate real-time video is used to guide the user towards a specified destination.<br />
** The GPS provides coarse location.<br />
** The stereo camera setup provides a wide field of view, along with coarse depth information.<br />
** Map information, combined with real time video is used to esimate location and orientation more accurately.<br />
** Simple object recognition techniques are employed to recognize parts of the environment.<br />
** The audio setup and the actuator(s) are used either in tandem or interchangeably to guide the user. This can be customized as required. Some possibilities include:<br />
*** A short periodic 3D sound generated to indicate the direction in which the user is to walk.<br />
*** The user is alerted about approaching obstacles by firing the actuator at a frequency inversely proportional to the distance to the obstacle. This distance can be computed using depth information computed from pairs of images.<br />
*** Information about the environment, such as "Pedestrian Crossing in 20m" can be relayed through audio.<br />
<br />
* '''Possible Enhancements''':<br />
** More comprehensive localization techniques, such as SLAM, can be used to improve the accuracy of the system. This will also open doors to indoor navigation, where the GPS fails.<br />
** Detection, segmentation and recognition of text (such as signboards and street names) in the environment will ensure less errors in navigation.<br />
<br />
* '''Expected Results''':<br />
** A navigation tool for the visually challenged, using audio and linear actuators to communicate with the user.<br />
<br />
* '''Contact''': leatherbrain at gmail dot com<br />
<br />
==== BeaglePod ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeaglePod<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglepod/]<br />
* '''Short project description''': BeaglePod is an IPod plug-in replacement for car stereo's that are IPod Ready. The BeaglePod uses gstreamer as an audio/video player and is controlled via the car stereo head unit using Apple Accessory Protocol. <br />
* '''Description''': The BeaglePod is an audio/video player for cars equipped with "IPod Ready" stereos. Using the Apple Accessory Protocol the car stereo is used to select and control the playback of media on the BeaglePod. Adding a video monitor the BeaglePod can also become a video player running all the audio through the car stereo with full pause, play, stop control using the car's stereo head unit. Using a software implementation of the Apple Accessory Protocol the BeaglePod is connected to the car stereo via a USB->TTL cable.<br />
* '''Expected Results''':<br />
** Play audio/video media files from the Beagleboard using the car stero to control playback and track selection.<br />
** Audio will playback through car's exist speaker.<br />
** With gstreamer dsp support HD playback of video with in car lcd.<br />
* '''Contact''': velorider [X] publicemail [X] us<br />
</font><br />
<br />
==== MART ====<br />
* '''Title''': Autonomous modular robot<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': Build an autonomous robot to enter the Eurobot 2010 competition<br />
* '''Homepage''': (only in Czech) http://eurobot.matfyz.info/<br />
* '''Full Description''': Goal of this project is to build an autonomous modular robot, that will be able to compete in the Eurobot competition. This project includes following:<br />
<br />
** '''HW''':<br />
** Custom beagle daughter-card (including kernel driver patches):<br />
*** CAN (Controller area network) able to sustain 1Mbit/s, using embedded cortex-m3 controller<br />
*** Battery backed up RTC<br />
*** Dual power - battery and/or adapter, with battery management (current consumption sensing and charging) <br />
*** Second serial and i2c headers<br />
*** (optional) Ethernet controller 10/100Mbit<br />
** Custom motor, servo and stepper motor drivers and IO boards<br />
*** everything connected through CAN<br />
<br />
** '''SW''':<br />
** Modular architecture, for simple modification<br />
** OpenCV integration for play field object identification<br />
** optimalizations for NEON (and DSP)<br />
<br />
* '''Contact''': Michal dot Demin at Gmail dot Com<br />
<br />
==== CamCast ====<br />
* '''Title''': Webcam broadcast server/relay<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/CamCast/]<br />
* '''Short project description''': Webcam broadcast platform for USB webcams<br />
* '''Homepage''': <br />
* '''Full Description''': The goal of this project is to utilize the beagleboard as a low cost platform for webcam video feeds.<br />
Server capability:<br />
<br />
** Broadcast webcam feeds for directly connected USB webcams<br />
** Relay webcam feeds from other servers, typically connected over wi-fi<br />
** Decimate MJPEG streams to match bandwidth limits<br />
** Monitor and control streams via HTTP<br />
** Advertise HTTP services locally via Zeroconf<br />
<br />
The beagleboard will require a functional Linux gspca driver for all USB webcams in use as well as USB wi-fi for remote service. Linux Zeroconf service must also be included.<br />
<br />
* '''Contact''': spiderkarma at gmail dot com<br />
<br />
====Beagle SecMon====<br />
<font color="#C0C0C0"><br />
* '''Title''' : Beagle Security Monitoring over Web <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle+SecMon/ BeagleSecMon]<br />
* '''Short project description''': This project proposes to control and transmit audio and video from a remote place using the beagleboard as a webserver.<br />
* '''Expected results''': The system will control one or more digital cameras with pan, tilt and zoom functions, and microphones. Besides, it can be configured to send information to a pre registered cell phone when movement is detected. Also, audio and video can be accessed using internet from any place.<br />
* '''Contact''': cborges at ifsc dot edu dot br====<br />
</font><br />
<br />
====PortablePlateRec====<br />
<br />
* '''Title''' : Beagle Portable Plate Recognition <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/PortablePlateRec/ PortablePlateRec] <br />
* '''Short project description''': A portable system for automatic number plate recognition (ANPR) using BeagleBoard.<br />
* '''Expected results''': The goal of this project is to develop a portable system for automatic number plate recognition (ANPR) using BeagleBoard. It includes the following:<br />
** receiving images from a camera;<br />
** applying signal processing algorithms for plate localization, orientation and sizing, image normalization, and character segmentation;<br />
** optical character recognition (for instance, Tesseract);<br />
** possible access to a database to check the plate against law infringements.<br />
<br />
* '''Contact''': fpacheco at ml1 dot net<br />
<br />
====Digital Multimedia Frame====<br />
<br />
* '''Title''' : Digital Multimedia Frame<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a photo, video and music application who use a touchscreen display<br />
* '''Expected results''': The goal of this project is to get photo, video, music from memory card or from a network. <br />
<br />
** Scan network to multimedia file. <br />
** Create automatically a slideshow when we are in photo mode.<br />
** Create automatically a music list.<br />
** Play video<br />
** Add basic operation available for picture (rotate, resize...)<br />
** touch screen will be used to simplify action.<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
====Beagle Utility====<br />
<br />
* '''Title''' : Beagle Utility<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a box with lcd screen to be able to encrypt, format, wipe, clone, find virus, search rootkit .... a hd or memory card. A menu with different operation is displayed to user.<br />
* '''Expected results''': The goal of this project is to be able to do some operation on harddriver, memory card <br />
<br />
** Encrypt <br />
** Format<br />
** Wipe<br />
** Clone<br />
** find virus<br />
** Rootkit<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
===Contest #2 projects===<br />
<br />
Please don't add new projects, contest #2 is closed.<br />
==== James ====<br />
1st [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/James James]<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. <br />
* '''Expected results''': Updated recipes for all relevant packages on OpenEmbedded. A script to install the needed packages to an Angstrom image (generated by Koen's generator) and documentation on how to configure things.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
</font><br />
====BeagleEPD====<br />
2nd [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': E-Ink Interface Board and Driver for beagleboard<br />
* '''Homepage''': [http://elinux.org/BeagleEPD BeagleEPD]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleepd/<br />
* '''Short project description''': This project aims to interface an E-Ink display directly with a beagleboard. This is done by creating an interface board that is connected to the Beagleboard expansion header and converts the relevant gpio signals into the levels appropriate for interfacing with the E-Ink display controller. The second part is to write a driver which is a port of am300epd.c from mach-pxa to mach-omap in order to support the E-Ink broadsheet framebuffer driver directly on beagleboard. All of this results in making it possible to connect any E-Ink display controller to a Beagleboard (via the expansion header) and to then treat any E-Ink display as another framebuffer.<br />
* '''Expected results''': Schematic for interface PCB between Beagleboard and E-Ink display controller board. A beagleepd.c mach-omap driver that will setup and control the IO pins appropriately.<br />
* '''Contact''': jayakumar at IRC (freenode, oftc) or jayakumar.lkml@gmail.com<br />
</font><br />
==== nullDC / Beagle ====<br />
<br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with newly added support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nulldc_beagle<br />
* '''Expected results''': For the contest: A WIP (but working) build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
===Contest #1 projects===<br />
<br />
====qemu-omap3====<br />
<br />
* '''Title''': support beagle board emulation in qemu<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]<br />
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.<br />
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]<br />
* '''Expected results''':<br />
** booting linux kernel and rootfs from nand and mmc image<br />
** Wiki page how to run qemu-omap3 for beagle board<br />
* '''Submission''':<br />
** http://code.google.com/p/qemu-omap3/wiki/UserManual<br />
* '''Contact''': yajin AT vm-kernel.org<br />
<br />
====openGPS====<br />
<br />
* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites. <br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** development of a display app with moving map capabilities<br />
** development of a user interface for handheld apps<br />
** integration with suitable LCD display<br />
** interface to map files on SD card<br />
** Wiki page on GPS receiver functions and features<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====Beagle Conference System====<br />
<br />
* '''Title''': Use beagle to come up with a conferencing system for home users<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]<br />
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.<br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.<br />
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).<br />
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.<br />
** The software shall also provide for ways to chat (text) with the users.<br />
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====BeagleRC====<br />
<br />
* '''Title''': Use a beagle board to drive a remote controlled car.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos. <br />
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml<br />
* '''Expected results''':<br />
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.<br />
* '''Contact''': code at chrisd dot info<br />
<br />
====PREEMPT_RT====<br />
<br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
<br />
====USB Support in U-boot ====<br />
2nd [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.<br />
* Homepage: [[U-boot musb gadget support]]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/<br />
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).<br />
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.<br />
* '''Contact''': ddompe at IRC<br />
</font><br />
<br />
==== James ====<br />
<br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': To be Added...<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html<br />
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
<br />
====BeagleBot====<br />
1st [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Board powered robot<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]<br />
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...<br />
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]<br />
* '''Expected results''':<br />
** Partly autonomous robot<br />
** PC controlling of the robot<br />
* '''Contact''': antti at hervanta.com<br />
</font><br />
<br />
====Android Cupcake for BeagleBoard====<br />
<br />
* '''Title''': Android Cupcake for BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]<br />
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard. <br />
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]<br />
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====FreeBSD port to BeagleBoard====<br />
<br />
* '''Title''' : A port of FreeBSD-arm to the BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]<br />
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.<br />
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.<br />
* '''Contact''': AsqYzeron====FreeBSD port to BeagleBoard====<br />
<br />
==Judging==<br />
<br />
===Judges===<br />
* Jason Kridner (jkridner)<br />
* Koen Kooi (koen)<br />
* Dirk Behme (dirk2)<br />
* Steve Sakoman (sakoman)<br />
* Hunyue Yau (ds2)<br />
* Mans Rullgard (mru)<br />
* Gregoire Gentil (gregoiregentil)<br />
<br />
===Past Judges===<br />
* Robert Kuhn (robertk)<br />
<br />
===Rules===<br />
* Judges cannot participate in the contest.<br />
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.<br />
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.<br />
* All voting will be public and logged on this page.<br />
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.<br />
* To follow up on shipping details, contact ''beagleship at list.ti.com''.<br />
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.<br />
<br />
===Criteria===<br />
* All new content must be open source as determined by the OSI.<br />
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.<br />
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]<br />
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.<br />
* "Wow" or "coolness" factor from usefulness/user experience point of view<br />
* Overall quality of the submission<br />
* Technical complexity<br />
** "Coolness" of the technical solution, even if it isn't useful for all the masses<br />
** Amount of work needed, i.e. x hours or x days?<br />
* Angstrom recipe for image<br />
* Documentation for the demo<br />
* Running power consumption<br />
* Use of DSP and SGX<br />
* Ease of use<br />
<br />
===Contest #1===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-01-11<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]<br />
|3<br />
|<br />
|3<br />
|2<br />
|<br />
|3<br />
|2<br />
!13<br />
|-<br />
|[[BeagleBoard/contest#openGPS|openGPS]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]<br />
|1<br />
|<br />
|<br />
|1<br />
|3<br />
|<br />
|2<br />
!7<br />
|-<br />
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]<br />
|<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
!5<br />
|-<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
!17<br />
|-<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|2<br />
|2<br />
|3<br />
|4<br />
|3<br />
|4<br />
|3<br />
!21<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|<br />
|3<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!4<br />
|-<br />
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!3<br />
|-<br />
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|1<br />
|Monday, January 12, 2009<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|-<br />
|}<br />
:Congratulations ;-) [[User:RobertK|RobertK]] 11:30, 12 January 2009 (UTC)<br />
<br />
There is a nice [http://www.linuxdevices.com/news/NS6362979448.html LinuxDevices.com BeagleBot cruises on Linux] article about contest #1 winner, too.<br />
<br />
===Contest #2===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-03-01<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|6<br />
|7<br />
|5<br />
|7<br />
|3<br />
|5<br />
|<br />
!33<br />
|-<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|3<br />
|3<br />
|2<br />
|3<br />
|5<br />
|3<br />
|<br />
!19<br />
|-<br />
|[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]<br />
|1<br />
|<br />
|3<br />
|<br />
|2<br />
|2<br />
|<br />
!8<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|2<br />
|Monday, March 2, 2009 <br />
|[[BeagleBoard/contest#James|James]]<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|-<br />
|}<br />
<br />
==Other background==<br />
<br />
==Contest #1==<br />
<br />
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58<br />
<br />
==Contest #2==<br />
<br />
* [http://www.beagleboard.org/irclogs/index.php?date=2009-02-13#T15:35:43 IRC Log of discussion]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/661879a591dc396d Announcement at mailing list]<br />
* [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html Blog announcement]</div>Dirkhttp://elinux.org/BeagleBoard/contestBeagleBoard/contest2010-01-21T16:23:16Z<p>Dirk: Reformat approved project</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Image:beagle_first_place.png|thumb|right]]<br />
==Contest Announcements==<br />
===Sponsored Project Program===<br />
The [[BeagleBoard]] Software Design Contest has now been replaced with the [[BeagleBoard/contest#Contest_projects| BeagleBoard Sponsored Projects Program]] (formerly known as contest #3). The biggest difference is that we'll be giving 2 boards per week to projects as they are '''[[BeagleBoard/contest#Approved_projects|approved]]''', rather than waiting until they are completed. Also, successfully completed projects may be rewarded with higher-end BeagleBoard-derived systems, such as a [http://gumstix.com/store/catalog/product_info.php?products_id=229 Gumstix Palo43] or a [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book] (BeagleBoard based). You are encouraged to make your entries [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|now]].<br />
<br />
If your project is listed as a winner and you haven't received your board, check with ''beagleship at list.ti.com''.<br />
<br />
===Contest #2===<br />
<br />
''Contest #2 is finished. See [[BeagleBoard/contest#Winners_2|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html contest #2]. This contest is about giving away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to the winner and another one to the runner-up. [[BeagleBoard/contest#Judges|Judges]] will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, February 27, 2009 (afternoon) <br />
* '''Voting goes over weekend, end: Sunday, March 1, 2009 (afternoon)'''<br />
* Shipping board to winner: Monday, March 2, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get before this revision is publically available by DigiKey (~end of March 2009).<br />
</font><br />
<br />
===Contest #1===<br />
<br />
''Contest #1 is finished. See [[BeagleBoard/contest#Winners|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, January 9, 2009 (afternoon) <br />
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)<br />
* Shipping board to winner: Monday, January 12, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).<br />
</font><br />
<br />
==Project ideas==<br />
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:<br />
* Stable musb<br />
** ISOCH support<br />
** High-speed USB TV tuner support<br />
** Hot-plug support for OTG (host and client)<br />
* USB Digital TV tuner (either ATSC or DVB-T)<br />
** Hauppauge HVR950 suggested as reference<br />
* Projection TV coupled with the Pico<br />
* Audio record<br />
* Latest kernel version<br />
* USB camera support<br />
** gspca driver - need to validate with multiple cameras<br />
** <font color="#C0C0C0">UVC driver (I understood from Koen this is working)</font><br />
* Fixing bugs listed on code.google.com<br />
* Android port and various applications<br />
* <font color="#C0C0C0">EHCI support (done)</font><br />
* <font color="#C0C0C0">USB support in u-boot (partially done by first contest, but still needs work)</font><br />
* <font color="#C0C0C0">Consumer IR remote control via LIRC (already in feed; do 'opkg lirc')</font><br />
<br />
See also [[BeagleBoard/Ideas-2009]] for more ideas.<br />
<br />
==Contest projects==<br />
Please add your project you like to participate at Sponsored Projects Program (contest #3) to [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|Sponsored Projects Program projects]]. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1.1").<br />
<br />
===Sponsored Projects Program (Contest #3) projects===<br />
<br />
If you like to join Sponsored Projects Program (contest #3), please add your project here the same way like done for contest #1 and #2 below. If you participated already previous contests, please copy your project description to this contest, again. This will let everybody know that the project is still alive and that you want to participate Sponsored Projects Program.<br />
<br />
====Approved projects====<br />
From the project proposals, [[BeagleBoard/contest#Sponsored_Project_Program|approved projects]] will get a BeagleBoard Rev C at the '''beginning''' of their project to help them execute:<br />
<br />
{|border=1<br />
!Project<br />
!Approved<br />
!Comment<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Gregoire<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Revolt 2405|Revolt 2405]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Gentoo Linux ARMv7 support|Gentoo Linux ARMv7 support]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Accelerated_USB_Graphics_Adapter|Accelerated USB Graphics Adapter]]</font><br />
|<font color="#C0C0C0">Week 21</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#picoFlamingo|picoFlamingo]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle Synth |Beagle Synth]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#USB Scope |USB Scope]]</font><br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Irrlicht|Irrlicht]]<br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleHam|BeagleHam]]</font><br />
|<font color="#C0C0C0">Week 24</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Apertus_open_source.2Fhardware_cinema_camera|Apertus Digital Cinema Camera ]]<br />
|<font color="#C0C0C0">Week 25</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Handheld_Lab|Handheld Lab]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TCF_Agent_Port|TCF Agent Port]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Traveler|Beagle-Traveler]]</font><br />
|<font color="#C0C0C0">Week 27</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#OMAP Emulator|OMAP Emulator]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TUD:OS_on_Beagleboard|TUD:OS on Beagleboard]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#QEMUonARM|QEMUonARM]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#EGLIBC|EGLIBC Support]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#RT-Beagle|RT-Beagle]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ONAS|ONAS]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Math-NEON|Math-NEON]]<br />
|<font color="#C0C0C0">Week 32<br />
|<font color="#C0C0C0">5 votes<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Happiness_Device_for_Cerebral_Palsy_Kids|Device for Cerebral Palsy Kids]]</font><br />
|<font color="#C0C0C0">Week 32</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Turk|Turk Platform]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#hApplause|hApplause]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#eLazarillo|eLazarillo]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">1 vote</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#PREEMPT_RT|PREEMPT_RT]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#HDDM|HDDM]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleVision|BeagleVision]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#DJ Audio / Video Mixer|DJ Audio / Video Mixer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#schooldog|An individual lowcost schoolcomputer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Disko|Disko - UI Application Framework]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ESITeam|ESITeam]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#DVB-T_Receiver|DVB-T_Receiver]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">8 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#UPnP.2FDLNA_AV_client_renderer_and_transcoding_server|UPnP/DLNA AV client renderer and transcoding server]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Speed-Reader|Speed-Reader]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Arduino_hybrid_robot|Beagle-Arduino hybrid robot]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#XBMC_ARM_Port|XBMC Arm Port]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#GuideBeagle:_Portable_monocular_SLAM_system|Portable monocular SLAM system]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#MythBeagle|MythBeagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeaglePod|BeaglePod]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle_SecMon|Beagle SecMon]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Touchscreen_LCD_support| Touchscreen LCD support]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FMframe |FMframe]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleSCI |BeagleSCI]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Pictouch|Pictouch]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Fotogenic |Fotogenic]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyGTee|MyGTee handheld]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Tourister_using_Hand_Gestures_and_HMD_on_Beagleboard|Beagle Tourister]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Medical Notebook|Medical Notebook]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#miniECG|miniECG]]<br />
|<br />
|<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#remoteBillBoard|Remote Bill Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleWacom|Wacom Tablet driver for Beagle Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleLAB|BeagleLAB]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FETCH|FETCH]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#PupLC|PupLC]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#ArchMobile:_ArchLinux_ARM_Port|ArchMobile]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Homebrew_SmartPhone|Homebrew SmartPhone]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagleboard_Carputer|Beagleboard Carputer]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#AutoRobo|AutoRobo]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Walker|Beagle-Walker]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyoVox|MyoVox]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Eye|Beagle-Eye]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MART|MART]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#CamCast|CamCast]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#PortablePlateRec|PortablePlateRec]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Digital_Multimedia_Frame|Digital Multimedia frame]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#.28Speech.29_Scrambler_Beagle| (Speech) Scrambler Beagle]]<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Utility|Beagle Utility]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
Rule: In each week, each judge has two points (two "1") to enter for his favorite project. The two projects with the most votes will be approved. The plan is to have final decision every Friday morning.<br />
<br />
==== Revolt 2405====<br />
<font color="#C0C0C0"><br />
* '''Title''': Revolt 2405<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Revolt2405/<br />
* '''Short project description''': First mission of a first person shooter style game using Ogre3D.<br />
* '''Homepage''': http://www.dcbcyber.com/revolt2405/wordpress<br />
* '''Expected results''': Expected results would be to have a playable game demo using Ogre3D for rendering. There will be sound and music. For controls I want to have the option of using keyboard and mouse or using controls like those found on hand held gaming devices. We would also like to have this playable on a small LCD as well as on a monitor connected to the DVI port.<br />
* '''Contact''': n2vdy at yahoo dot com or dbatzle at dcbcyber dot com<br />
</font><br />
==== Touchscreen LCD support ====<br />
<br />
* '''Title''': Touchscreen LCD support <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': The project will add the touch screen support to Beagle board<br />
The following are the components that i am planning of using<br />
:*The LCD breakout board is http://www.sparkfun.com/commerce/product_info.php?products_id=8600<br />
:*The touch screen is http://www.sparkfun.com/commerce/product_info.php?products_id=8977<br />
:*The touch screen connector is http://www.sparkfun.com/commerce/product_info.php?products_id=9104<br />
<br />
Another option is buying a full LCD with touch screen option<br />
:*The product link is http://www.sparkfun.com/commerce/product_info.php?products_id=257.<br />
:*I would create a system and hardware like this video http://www.youtube.com/watch?v=foWnDZ3eQto&feature=related<br />
<br />
* '''Homepage''': http://pradheeptce.googlepages.com/ yet to be fully completed.<br />
<br />
* '''Expected results''': <br />
**Linux driver to add LCD with touch screen support<br />
**The breakout board(preferably single layered as it can be created at home)gerber for attaching with beagle which will be created using FreePcb(www.freepcb.com).You can see the photos of my RFID Based Access Control system project there.<br />
**Wiki page to describe the entire development method<br />
* '''Contact''': pradheep_sh[at]tce[.]edu<br />
<br />
==== Gentoo Linux ARMv7 support ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Official Gentoo Linux ARMv7 support<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Gentoo/<br />
* '''Short project description''': Build ARMv7 optimized packages and stages for Gentoo Linux created officially by Gentoo developers.<br />
* '''Description''': The project is for providing official support for ARMv7-based devices like the Beagleboard, we will provide stages and packages optimized for ARMv7 processors so any owner of an ARMv7 device can get an optimized system. At the moment Gentoo only provides and supports ARMv4 and ARMv5TE, therefore we would like to expand our official support to the more powerful ARMv7 subarchitecture.<br />
* '''Homepage''': http://www.gentoo.org/proj/en/base/embedded/ http://www.gentoo.org/doc/en/handbook/handbook-arm.xml http://www.gentoo.org/proj/en/base/embedded/handbook/<br />
* '''Expected results''': <br />
**Allow Gentoo users to have ARMv7 optimized stages and packages.<br />
**Document the installation on the provided boards.<br />
* '''Contact''': armin76[at]gentoo[.]org , solar[at]gentoo[.]org<br />
</font><br />
==== TUD:OS on Beagleboard ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TUD:OS on Beagleboard <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/TUD%3AOS+on+the+Beagleboard/]<br />
* '''Short project description''': Port the L4-Microkernel based TUD:OS Operating System to the Beagleboard<br />
* '''Homepage''': will follow<br />
* '''Description''': <br />
** '''What the heck?''' The TUD:OS operating system is a L4 microkernel based operating system, with good real-time and security properties, developed at the TU Dresden. <br />
** '''Microkernel-based''': The microkernel approach allows it to to reduce the trusted computing base (the amount of code that has to be trusted) by running small trusted applications side by side with non-trusted applications, all as unprivileged user mode applications. Further, it is possible to run real-time applications side-by side with non real-time applications. Also device driver run in user-mode and thus a crash of a device driver will not lead to an whole system crash and in the best case the driver can be restarted and the system will keep on running.<br />
** '''Familiar Environment''': While offering the above mentioned vantages, TUD:OS still offers a familiar environment by the possibility to run one or more instances of L4Linux. L4Linux is a Linux port the Fiasco microkernel which is binary compatible to native Linux but runs in deprivilieged usermode.<br />
** '''What do we get from this project?''' ''Briefly: A fundament to build embedded [realtime] systems [with a exceptionally small trusted computing base].'' Further a possibility to run multiple virtualized linux instances on the beagleboard. A good documentation how to build such systems. And last but not least a (hopefully cool ;) demo showing that it acutally works , perhaps like the one found at [http://demo.tudos.org demo.tudos.org] (somewhat outdated). <br />
*'''Contact:''' dvogt[at]os[.]inf[.]tu-dresden[.]de ([[User:Dvogt|Dvogt]])<br />
</font><br />
==== picoFlamingo ====<br />
<font color="#C0C0C0"><br />
* '''Title''': picoFlamingo <br />
* '''beagleboard.org project''': http://beagleboard.org/project/picoFlamingo/<br />
* '''Short project description''': A portable presentation system for the BeagleBoard and the picoDLP projector<br />
* '''Homepage''': http://papermint-designs.com/picoflamingo<br />
* '''Expected results''': <br />
** An application to perform presentations including 3D elements.<br />
** A basic hardware specification for a portable presentation system.<br />
** A remote interface for wireless control of the presentation.<br />
** A demonstration of the possibilities provided by the BeagleBoard, the OMAP 3 platform and the picoDLP.<br />
** Hopefully a lightweight 3D render engine for OpenGL ES 2.0.<br />
** A lot of fun!!!... <br />
* '''Contact''': dmo[at]papermint-designs[.]com<br />
</font><br />
==== Accelerated USB Graphics Adapter ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Accelerated USB Graphics Adapter <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': USB-attached Graphics Card supporting OpenGL acceleration for XFree86<br />
* '''Homepage''': http://www.employees.org/~mschulma/beagleboard/cerberus/<br />
* '''Expected results''': <br />
** Use the Beagleboard to attach another monitor to a PC running Linux, and run a graphics intensive application on the expanded virtual desktop without slowing the main CPU.<br />
* '''Contact''': mschulma [at] employees [dot ] org<br />
</font><br />
==== Apertus open source/hardware cinema camera ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Apertus Digital Cinema Camera<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Apertus/<br />
* '''Short project description''': A digital camera controler for an Elphel open hardware camera. The beagle board will be used as a realtime viewfinder unit and hardware camera control.<br />
* '''Homepage''': http://cinema.elphel.com<br />
* '''Expected results''': We intend on creating a community driven open source cinematic HD camera for a professional environment. <br />
The image is provided by an Elphel camera (elphel.com, open source camera). A beagle board would be connected to an elphel camera using ethernet. The beagle board runs a lightweight UI that allows user to view the live feed from the camera on an external display (dvi or s-video). It also allows to trigger recording and change camera settings using a user interface. The user interface is software based (on screen) + hardware based using buttons and knobs if possible (I2C interface of the beagle board would be used). This project will take 2-6 months to have visible results. The feasibility of this project has been discussed on the Beagle Board group, with positive answers (cfr. http://groups.google.fr/group/beagleboard/browse_thread/thread/6c55a10dd598bb6/e946107bd0a807b8#e946107bd0a807b8 )<br />
* '''Contact''': philippe dot jadin at gmail dot com<br />
</font><br />
==== FMframe ====<br />
<br />
* '''Title''': FMframe<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': FMframe is a picture frame application coupled with an rss news reader and clock/alarm functionality<br />
* '''Homepage''': not yet; in a few days I will try to come up with a website with some preliminary screenshots.<br />
* '''Expected results''': Plan is to make a picture frame application. Hardwarewise the beagle will connect to a DVI display. Softwarewise it will be a picture frame optionally with a clock on top of the photo (either a big semi-transparent clock in the center or a smaller clock in the corner). There will also be an alarm function which can play a preselected mp3 file when the alarm time is reached. Apart from showing pictures the frame can also show news from a user definable rss feed (e.g. cnn.com), Normally this will be in a ticker-tape at the bottom of the picture. When the user presses a button when a specific topic is shown the full message pops up. Probably there will be dedicated provisions for weather, giving the weather forecast if desired (in a style as done by the google weather widget). When waking up the frame can show the weather with the scrolling news or (user selectable) just a list of headlines. When the alarm is switched off the display acts like a regular photo frame again.<br>User interaction will be through a remote control. Alternate inputs could be touch screen (if I get access to an affordable one) or keyboard (less convenient but it does allow people without IR receiver to control the device.<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
<br />
==== BeagleSCI ====<br />
<br />
* '''Title''': BeagleSCI<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': BeagleSCI aims to use the BeagleBoard as a platform for scientific computation and instrumentation (SCI).<br />
* '''Homepage''': http://sourceforge.net/projects/beaglesci/<br />
* '''Expected results''': As a start, the initial goal would be to use the BeagleBoard as a logger of a seismometer. This would involve interfacing a 12-bit ADC chip and writing a driver for it. Data read from the instrument can be displayed by the BeagleBoard through a monitor or send the data to a remote computer via RS-232/RS-485.<br />
* '''Contact''': sherdon dot uy at gmail dot com<br />
<br />
==== Pictouch====<br />
<br />
* '''Title''': Pictouch<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Mobile and Projected Touch user interface<br />
* '''Homepage''': not yet<br />
* '''Expected results''': The goal is to build a new Tactile Interface system based on beagleboard and the DLP picoprojector. Currently, the project make the use of JavaFX to support Multi-Touch (and Multi-User) and of 2 basic webcam, in order to build a low cost gesture recognition system.In the classical case of use, the interface is projected onto a classical table.Users interact directly with their fingers on the projected interface.<br />
<br />
* '''Contact''': maxired at gmail dot com<br />
<br />
==== Fotogenic ====<br />
<br />
* '''Title''': Fotogenic<br />
* '''beagleboard.org project''': not yet - but project is already in progress<br />
* '''Short project description''': Bring network connectivity to plain old vanilla picture frames<br />
* '''Homepage''': www.sourceforge.net/projects/fotogenic<br />
* '''Expected results''': This project brings wired, WiFi and bluetooth connectivity and management to plain old picture frames. The project selects pictures from your photo database, resizes them for the picture frame's native resolution, embellishes them with web and home automation information sources before presenting them to the photo frame by making the BeagleBoard appear to be a USB pendrive...! Right click a photo on your laptop and select "Show on picture frame now!". Manage many photo frames centrally and much much more... Includes "wave gesture" interface to wave over picture frame for next photo... Also works with Eye-Fi SD memory cards to make photos appear on photoframe moments after taken...!!<br />
* '''Contact''': horse_dung at hotmail dot com<br />
<br />
==== Beagle Synth ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Synth<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-synth/<br />
* '''Short project description''': DSP MIDI synthesizer based around the beagleboard<br />
* '''Homepage''': http://code.google.com/p/beagle-synth/<br />
* '''Expected results''': Initially a basic MIDI controllable subtractive synth with 3 oscillators, low pass, high pass, and band pass filters, 2 envelope generators, and 2 LFO's. From there the intention is to add some type of control surface (either physical controls or perhaps a touch screen), some effects (phaser, distortion, reverb), and perhaps other types of synthesis options (FM, additive, maybe some type of patchibility). The result will be a fully featured MIDI instrument comparable to many commercial synths. This project is to be a learning experience with the intention of exploring using DSP for music synthesis. As of now this project is in the concept phase and is still in need of hardware for implementation.<br />
* '''Contact''': dpanseri [at] gmail [dot] com<br />
</font><br />
==== USB Scope ====<br />
<font color="#C0C0C0"><br />
* '''Title''': USB Scope<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': USB diagnostics to aid driver development for USB devices<br />
* '''Homepage''': none yet<br />
* '''Expected results''': This project will use the BeagleBoard as a USB proxy between any USB device and a host computer connected via the OTG port. This will allow the BeagleBoard to snoop, compare and modify USB traffic which can assist both commercial and open source development of drivers and diagnosis of issues. Other ideas could be examined such as a USB-TCP/IP-USB proxy to remotely connect USB devices. Open or free software equivalents exist, but hardware monitoring devices only exist as expensive commercial products. <br />
* '''Contact''': horse_dung at hotmail dot com<br />
</font><br />
==== Irrlicht ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Irrlicht<br />
* '''beagleboard.org project''': no<br />
* '''Short project description''': A fully-featured 3D render engine with ogl-es 1.x and 2.x support<br />
* '''Homepage''': http://irrlicht.sourceforge.net<br />
* '''Expected results''': <br />
** Hardware optimized core routines for optimal OMAP support<br />
** Support of ogl-es 2.x (the 1.x driver is reportedly running on the board)<br />
** Full framerate (60FPS) rendering of q3 alike scenes<br />
** The engine also offers SW rendering, allowing to target for other OMAPs as well, but would require more tweaking in the render optimizations<br />
** We can port one of the demo apps from our apps contest to show the full applicability <br />
* '''Contact''': hybrid[at]users[.]sourceforge[.]net<br />
</font><br />
==== BeagleHam ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleHam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleham/<br />
* '''Short project description''': Bringing the BeagleBoard to the world of Amateur Radio.<br />
* '''Homepage''': None at this time.<br />
* '''Expected results''': <br />
** AX.25 Packet support, enabling full APRS support (operating as tracker, fill-in or permanent digipeater, and KISS TNC).<br />
** Encode and decode of HF digital modes, using DSP functionality where possible:<br />
*** BPSK, QPSK 31/63/125/250<br />
*** Olivia<br />
*** WSPR/MEPT<br />
*** MT-63<br />
*** DominoEX<br />
*** RTTY<br />
*** Throb<br />
** CW encode and decode<br />
** Capability to display on small (sub-6-inch) screens for mobile and field use<br />
* '''Contact''': xunil at xunil dot net<br />
</font><br />
==== TCF Agent Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TCF Agent Port<br />
* '''beagleboard.org project''': http://beagleboard.org/project/TCF+agent+port/<br />
* '''Short project description''': Support remote debugging and run control by porting the Eclipse Target Communication Framework (TCF) Agent to beagleboard+Ångström<br />
* '''Homepage''': Not yet<br />
* '''Expected results''': <br />
** A working port of the TCF "Reference implementation of a target agent" to BB/Ångström<br />
** screenshots and information on the TCF: http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Project.html<br />
** TCF agent running on a beagle board would provide the host computer following capabilities (see link above for details):<br />
*** Run control of userspace processes and threads<br />
*** Breakpoints<br />
*** Registers<br />
*** Stack traces<br />
*** Memory access<br />
*** Processes - list, start, stop, attach and debug.<br />
*** Sys monitor - CPU and memory utilization info<br />
*** File System - browsing and copying files<br />
<br />
* '''Contact''': terrella at terrella dot mobi<br />
</font><br />
<br />
==== RT-Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Real-Time patch for the beagleboard<br />
* '''beagleboard.org project''': http://beagleboard.org/project/omap-rt-patch/<br />
* '''Short project description''': Porting the linux rt patch to the omap linux kernel and providing testing applications. This project is developed at the INSA of Rennes (Engineer school in FRANCE) to allow next year Real Time course to be run on the BeagleBoard.<br />
* '''Homepage''': http://sourceforge.net/projects/linux-omap-rt-p/<br />
* '''Expected results''': <br />
** Porting the linux real-time patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) to the linux omap kernel and providing recipes for openembedded allowing to build the patched kernel.<br />
** Providing testing applications allowing to evaluate the real-time behavior of the platform<br />
** Providing applications that could be used for teaching purposes<br />
* '''Current Results''':<br />
** patch-2.6.29.5-rt21 was modified to successfully patch linux-omap-2.6.29 (modified patch available through project page).<br />
** kernel compile and boots with minor error concerning two IRQs (72,73) <br />
* '''Contact''': piat_jonathan[at]users[.]sourceforge[.]net<br />
</font><br />
==== MyGTee ====<br />
<br />
* '''Title''': MyGTee <br />
* '''beagleboard.org project''': http://beagleboard.org/project/MyGTee/<br />
* '''Short project description''': A handheld device exploiting all the OMAP3530 capabilities<br />
* '''Homepage''': http://enco2009.webs.com/<br />
* '''Expected results''': I stage: building a prototype hopefully based on the BeagleBoard; II stage: the actual handheld that may allow for further software opensource development<br />
* '''Contact''': doctorc[at]o2[.]pl<br />
<br />
==== ONAS ====<br />
<font color="#C0C0C0"><br />
* '''Title''': ONAS<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ONAS/<br />
* '''Short project description''': An open source NAS<br />
* '''Homepage''': http://code.google.com/p/onas/<br />
* '''Expected results''': Development of a full featured NAS running Linux <br />
* '''Contact''': electrogeek[at]wp[.]pl<br />
</font><br />
==== Handheld Lab ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Handheld Lab<br />
* '''beagleboard.org project''': http://beagleboard.org/project/handheld_lab/<br />
* '''Short project description''': The goal of this project is to create a little, yet powerful, handheld laboratory with as much functions as possible. It will be easy of use thanks to the integrated LCD touchscreen and nice GUI.<br />
* '''Homepage''': http://www.mipixel.com/handheld-lab<br />
* '''Expected results''': First result will be working LCD showing oscilloscope. After this spectrum analyzer and logic analyzer. All this stuff will need extra electronics.<br />
* '''Contact''': fran[at]mipixel[.]com<br />
</font><br />
====Beagle Tourister using Hand Gestures and HMD on Beagleboard ====<br />
* '''Title''': Travel Buddy using Hand Gestures and HMD on Beagleboard <br />
* '''beagleboard.org project''': http://beagleboard.org/project/travelbuddy/<br />
* '''Short project description''': A device which will assist a traveller/tourist giving them mobile computing power and the following features: <br />
*1) A Compact HMD (Head mountable device) instead of the conventional projector (Problem of Projection Surface while on the move) <br />
*2) Use of standard cam for Image processing i.e recognising simple hand gestures to interact with the GUI seen in the HMD <br />
*3) Scanning of images (street name plates/hotel names/landmarks/book titles as indicated by user) to provide useful feedback data(directions/reviews/record *videos/take pictures/information) <br />
*4) Mode for Speech2text and text2speech conversion for inter-language communication. <br />
* '''Homepage''': Under Construction <br />
* '''Expected results''':<br />
*1) V-NAV: Virtual Navigator - Streaming Google Street View data according to your current location <br />
*2) ULA: Universal Language Assistant: Scan any text by positioning your fingers and the the scanned text is translated to your default language.<br />
*3) Say goodbye to the camera/ cell phone/tourguide/maps. Good platform for further expansion to include newer features. <br />
*4) Virtual Reality Mapping to the Real World: Overlay of relevant information on the on the HMD.<br />
* '''Contact''': sisilmet2000 at gmail dot com , dhairyadand at gmail dot com <br />
<br />
==== Happiness Device for Cerebral Palsy Kids ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Happiness Device for Cerebral Palsy Kids<br />
* '''beagleboard.org project''': http://beagleboard.org/project/HappyCP/<br />
* '''Project description''':<br />
It is an attempt to bridge the gap in communication between those affected by cerebral palsy and those not. The focus of the problem has been on facilitating communication in the emotional domain since this remains a completely unaddressed area. It is possible that some of the ensuing product functions will additionally facilitate communication problems in the physical domain, as well as be physically therapeutic for the cerebral palsy child in the manner of a comfort blanket. The basis of the product is an Emotional Language Protocol (elp) that works as its interface and is driven by four concurrently acting features - color, shape, motion and sound - corresponding to the sensory modes of the visual, the tactile and the aural. The interaction itself is facilitated by touch of varying intensities including pressing, thumping, squeezing, turning and, of course, by touching. Those not affected by cerebral palsy may additionally use speech along with touch. The interplay of this interface and interaction allows the cerebral palsy child to express his different needs and emotions to another person cerebral palsy or otherwise.Also, the device's mobile connectivity allows its users to communicate with someone far away<br />
* '''Homepage''': http://www.dhairyadand.com/Home/jellow<br />
* '''Expected results''': I have uploaded the basic designs at the above link to the homepage. The device is circular in nature with a touch screen where an interactive interface is used to display icons, objects, photos and other sharable action oriented stuff. The device has exchangable memory sticks which allow two or more device's to get connected and hence facilitating interactions. The result is to get a cerebral palsy kid out of his isolated environment, motivate him to communicate by making a device which will show him the joy of communicating.<br />
* '''Contact''': dhairya AT cyber DOT law DOT harvard DOT edu<br />
</font><br />
==== UPnP/DLNA AV client renderer and transcoding server ====<br />
<font color="#C0C0C0"><br />
* '''Title''': UPnP/DLNA AV client renderer and transcoding server <br />
* '''beagleboard.org project''': http://beagleboard.org/project/UPnP_AV_MediaServer/<br />
* '''Project description''':<br />
Enable the beagleboard as a fully featured UPnP AV rendering client, and as a UPnP AV (transcoding!) server. <br />
<br />
Work will be based upon vlc+djmount (for client side) and fuppes (for server side). Server side transcoding to be hardware assisted via hardware DSP codecs. Initial target for the transcoding server on beagleboard is to drive the Neuros OSD (an underpowered DM320-based device). <br />
<br />
* '''Homepage''': Will be an extension and complement to my work on the DM320-based Nueros OSD: http://osd.oddren.com<br />
* '''Expected results''': Beagleboard can act as either as rendering UPnP client, or as a transcoding UPnP server to drive weaker client devices like the Neuros OSD with their preferred streaming format.<br />
* '''Contact''': bmcarnes_beagleboard AT oddren DOT com<br />
</font><br />
==== Beagle-Traveler====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Traveler<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-traveler/<br />
* '''Short project description''': Automotive media and vehicle management controller. Comparable to BeaglesRide.org (no activity).<br />
* '''Homepage''': http://beagletraveler.wordpress.com<br />
* '''Expected results''': intergrate major automotive subsystem management and communications. Improved vehicle notification of subsystems status'. <br />
* '''Contact''': wheeler dawt larry (at) gmail dawt com<br />
**Please send sponsored information and project questions to the email address above.<br />
</font><br />
==== OMAP Emulator====<br />
<font color="#C0C0C0"><br />
* '''Title''': OMAP Emulator<br />
* '''beagleboard.org project''': http://beagleboard.org/project/OMAP+Emulator/<br />
* '''Short project description''': Emulator for rapid prototyping<br />
* '''Homepage''': no homepage yet<br />
* '''Expected results''': Open source implementation of an IDE environment for rapid code development and testing<br />
* '''Contact''': hwtester (at) myway (dot) com<br />
</font><br />
==== eLazarillo====<br />
<font color="#C0C0C0"><br />
[[File:Elazarillo.png|thumb|300px|eLazarillo sketch]]<br />
* '''Title''': eLazarillo (electronic helper for blind persons)<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': Gadget designed for blind persons or with vision problems. <br />
* '''Homepage''': http://elazarillo.blogspot.com/<br />
* '''Full description''':<br />
Lazarillo is a spanish word that means "blind person's guide" and this is the objetive of this project. This gadget will have features like reading non-braille books, assist to blind persons to get places like markets, drugstores, etc. (based on previous GPS tagged places and using google maps). Other functionalities will be spoken weather information, personal calendar, function keys, etc.<br />
<br />
The gadget will be voice controlled, will need GPS, 3G modem, camera and battery. Size will be 4x5 inches (approx.).<br />
<br />
* '''Expected results''': Open source hardware and software platform for blind persons gadgets. My device will have most of the above described.<br />
* '''Contact''': villanuevaborrego (at) gmail (dot) com<br />
</font><br />
<br />
==== QEMUonARM ====<br />
<font color="#C0C0C0"><br />
* '''Title''': QEMUonARM<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': QEMU on ARM. <br />
* '''Homepage''': http://elinux.org/QEMUonARM<br />
* '''Full description''':<br />
This project aims at resurrect and improve QEMU on ARM hosts.<br />
For more information: http://www.qemu.org<br />
* '''Expected results''': Demonstrate user mode and system mode examples, such as running some simple Linux applications or booting an i386 OS. If there's enough interest, making Wine and QEMU work together might be considered.<br />
* '''Contact''': laurent.desnogues (at) gmail (dot) com<br />
</font><br />
<br />
==== Math-NEON ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Math-NEON<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Math-Neon/<br />
* '''Short project description''': NEON optimized cmath like library <br />
* '''Homepage''': http://code.google.com/p/math-neon/<br />
* '''Full description''': <br />
This project aims to overcome the shortcomings of the VFP-lite based cmath implementation. It is targeted at games and other high performance low accuracy applications. The project will consist of C functions, for PC development, which mirror (as near as possible) the hand optimized NEON assembly routines. In order to gain the best performance i will make use of the NEON Unit's Integer and Floating point pipelines in conjunction with minimizing branches (where they cannot be precalculated on the ARM) and creating new algorithms. <br />
* '''Expected results''': Fast approximate implementations of trigonometric, exponential, logarithmic and power functions for use with future Beagleboard / Cortex A8 based projects. <br />
* '''Contact''': lachlan.ts (at) gmail (dot) com<br />
</font><br />
==== Medical Notebook ====<br />
* '''Title''': Medical Notebook<br />
* '''beagleboard.org project''': yet to register<br />
* '''Short project description''': The Ultimate Notebook for Hospitals<br />
* '''Homepage''': coming soon...<br />
* '''Full description''': <br />
A handheld device to improve hospital functionality/efficiency. To add intelligence to the mundane hospital softwares. <br />
Features are:<br />
<br />
View and Update Patient status, medical history, medication details, appointments, billing - stored as a database in central server.<br />
<br />
Touchscreen with handwriting recognition & hand support pad for data entry.<br />
<br />
Light Weight < 1kg<br />
<br />
VoIP, video conferencing/recording for consulting other doctors <br />
<br />
Wifi, bluetooth & ethernet support <br />
<br />
Docking station for charging<br />
<br />
Support for usb keyboard & mouse on docking station<br />
<br />
* '''Expected results''': <br />
<br />
1) Driver for touch pen tablet with support for hand writing recognition<br />
2) Porting of VoIP software for beagleboard (H.323 ???)<br />
3) Video conferencing software for beagleboard<br />
4) WiFi ?& bluetooth support on beagle board<br />
5) Speech recogntion software for beagleboard<br />
6) Entry of beagle board based products to hospital autmation market<br />
7) Improved, efficient & intelligent patient care in hospitals<br />
<br />
* '''Contact''': noorshaheen.m.n (at) gmail (dot) com<br />
<br />
==== EGLIBC ====<br />
<font color="#C0C0C0"><br />
* '''Title''': EGLIBC support<br />
* '''beagleboard.org project''':<br />
* '''Short project description''': Use EGLIBC as system library for beagleboard project in OpenEmbedded.<br />
* '''Homepage''': www.eglibc.org<br />
* '''Expected results''': EGLIBC becomes the default system library on the distribution and can be used instead of glibc<br />
with the newly added configurability support to selec/deselect features. I would also like to make it compile as pure thumb2<br />
code.<br />
* '''Contact''': raj[.]khem[at]gmail[.]com<br />
</font><br />
==== miniECG ====<br />
* '''Title''': miniECG<br />
* '''beagleboard.org project''': http://beagleboard.org/project/miniECG/<br />
* '''Short project description''': Little device that cares for heart when heart patients are busy carrying out their duties<br />
* '''Homepage''': http://code.google.com/p/miniecg/<br />
* '''Full description''': <br />
miniECG is a wearable device that monitors ECG signal, processes it and can transmit it over wireless internet connection to doctors clinic. It has following features are:<br />
(all the hardware components required are available through digikey.com including LCD and touch screen)<br />
<br />
1) It has touch screen that enable user to give commands like store, display old ECG data, transmit, etc. Device also has a LCD display which is used to display ECG waveform.<br />
<br />
2) A tiny server runs on device that enables doctor to login to device any time he wants and extract patients ECG data. The device is connected to internet through wireless USB dongle. <br />
<br />
3) DSP core does the job of compressing ECG signal, doing PCA (principal component analysis) on ECG signal, detect QRS, measuring heart beats and digital filtering.<br />
<br />
4) DSP along with Cortex A8 runs algorithm that determines critical state of heart by doing feature extraction over ECG signals. It also does PCA over set of stored ECG signal to obtain information about any substantial drift in normal functionality of heart. <br />
<br />
5) Wireless USB dongle provides connectivity to internet and data is transmitted over internet as per schedule programmed into the device. ECG signal can also be streamed over internet using this dongle. <br />
<br />
6) Keyboard & mouse (USB) interface is provided for more flexibility and quick access. LCD monitor interface is also be provided. Key-board, mouse and LCD monitor interface will work only when device is powered by adaptor. For device powered by battery only input option is touch screen and only output option is LCD display.<br />
<br />
7) Device also has small software support to give reminder on when to consume which drug. The prescription of drug and its timing information is feed in as per doctors advice. (keyboard and mouse interface with miniECG can be of great advantage here)<br />
<br />
8) USB memory devices will be used to store ECG data.<br />
<br />
9) miniECG will be dual powered. It can be powered by adaptor as well as with rechargeable battery. <br />
<br />
Website link has block diagram of miniECG and also picture of ECG pre-amplifier which is already designed. In future all the source codes will be uploaded on the link as and when available.<br />
<br />
* '''Expected results''': a) Ability to login from remote PC onto miniECG and read data b) Should be able to send stored data or stream live ECG signal over internet c) Robust interface of LCD & touch screen with controller d) Data storage and retrieval from USB storage device e) Successful implementation of DSP algorithms for feature extraction, PCA, QRS detection, filtering and compression. f) As the whole device is battery powered, software & driver which are very specific to the desired application should only be installed & made working. Thus providing a low power system architecture. <br />
<br />
* '''Future Work''': Once the desire basic funtions of ECG storing, retrieval and transmitting is meet, miniECG can be programmed into miniPA (mini personal assistance) mainly targeting senior citizens. miniPA will have much advanced features that can help them elderly person in their day-to-day activity.<br />
* '''Contact''': mehta.nandish (at) gmail (dot) com<br />
<br />
<br />
==== remoteBillBoard ====<br />
* '''Title''': Remote Bill Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/remoteBillBoard/<br />
* '''Short project description''': Video bill boards, remotely controlled via web over a 3G modem<br />
* '''Homepage''': http://www.greensoftware.net/remoteBillBoard<br />
* '''Full description''': <br />
Play HD video on billboards, remotely manage the billboards, upload new advertisements, remove old ones etc..<br />
<br />
<br />
* '''Expected results''': <br />
a) 3g modem support, so flexiblity.<br />
b) a full working web based system<br />
<br />
* '''Future Work''':<br />
a) a more advanced desktop application to replaced the web based solution.<br />
<br />
* '''Contact''': ahmad.mushtaq (at) gmail (dot) com<br />
<br />
<br />
==== Turk ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Turk Platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Turk/<br />
* '''Short project description''': A wireless dynamically-mappable interface platform for small devices<br />
* '''Homepage''': http://www.turkinnovations.com/<br />
* '''Full Description''': Turk will be an open-source wireless interface platform that allows interfacing of small wireless (Zigbee or Wi-Fi enabled) devices through a dynamic mapping framework and web interface. Developers can implement their device's protocol easily through small user-space drivers called 'Gadgets' and host them on our server. The platform is then capable of automatically downloading and starting appropriate gadgets for new devices that are compatible with the basic Turk protocol. Gadgets reveal their services to the user and other gadgets through our growing library of data endpoint types (such as colors, URLs, booleans, xml strings) and user controls (like sliders, switches and color pickers), and can then be connected to each other through a themable web interface.<br />
<br />
* '''Expected results''': <br />
**A platform that allows developers to write simple user-space drivers that expose interfaces through XML-RPC<br />
**A web interface and remote configuration capabilities through a central server. <br />
**A simple and well-tested protocol and driver for a kernel-managed point-to-multipoint Zigbee network. <br />
**More hardware connectivity besides the Wi-Fi and Zigbee interfaces will hopefully be developed by collaborating with other beagleboard projects and developers.<br />
* '''Contact''': rob.odwyer [at] turkinnovations [dot] com<br />
</font><br />
==== BeagleWacom ====<br />
* '''Title''': Wacom Tablet driver for Beagle Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-wacom/<br />
* '''Short project description''': Linux drivers of wacom tablet ported for Beagle Board<br />
* '''Homepage''': <br />
* '''Full Description''': beagle-wacom will be port of linux drivers for configuring & running wacom tablets with the beagle board. The idea is to have support for wacom-components, so that they can be used by OEMs of beagleboard based products using linux as their OS<br />
<br />
* '''Expected results''': <br />
**easy integration of wacom tablet with Beagle Board. <br />
**OEMs of beagleboard based products using linux as their OS can integrate wacom-components in their product with minimal fuss<br />
* '''Contact''': najath [at] gmail [dot] com<br />
<br />
<br />
====hApplause====<br />
<font color="#C0C0C0"><br />
* '''Title''': hApplause<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Hardware Platform that You can use to play with Audio Synthesis<br />
* '''Homepage''': not yet<br />
* '''Description''': ''hApplause'' will be multi-functional flexible audio hardware platform. The goal is to make a tool that can allow to develop audio software and hardware (e.g. DSP synthesizers, FX units, hardware expansion boards, etc.). The concept is inspired by [http://www.chameleon.synth.net/ Chameleon] and [http://www.ucapps.de/ MIDIbox]. ''BeagleBoard'' will give ''Chameleon'' like software flexibility while planed hardware with ''Expansion Interface'' and ''Audio Multiplexer'' will give ''MIDIbox'' like hardware flexibility.<br />
*; Hardware features<br />
*: Audio Stereo In/Out<br />
*: MIDI In/Out/Thru<br />
*: General purpose USB port - function depends on user application<br />
*: General purpose SD/MMC Card (e.g. for user data storage) - function depends on user application<br />
*: Front panel interface (1U rack version) with:<br />
*:* LCD<br />
*:* Volume potentiometer<br />
*:* Headphones jack<br />
*:* Power switch with LED indicator<br />
*:* programmable rotary encoders (5 are planed)<br />
*:* programmable buttons and LEDs (12 are planed)<br />
*: Expansion Interface with audio signal buses (1-4 planed, depends on final implementation) and data/command bus (I2C and/or CAN)<br />
*: Audio Multiplexer for flexible routing of audio signal between ''BeagleBoard'', ''Audio In/Out'' and ''Expansion Interface''<br />
*: USB and RS232C for developers<br />
*; Software features<br />
*: All hardware will be fully accessible from ''BeagleBoard'' by API<br />
*: hApplause OS is planed (abstract layer over hardware, user program loading, self configuration on power on)<br />
* '''Expected results''':<br />
*# 19" 1U rackmount unit ready to play with.<br />
*# Libs and additional software for developers (at least API for hApplause's hardware)<br />
*# Example implementation of software synth<br />
*# Single size eurocard unit for 3U rack, like in [http://www.doepfer.de/a100e.htm Doepfer A-100 System] modules<br />
* '''Contact''': tawezik at gmail dot com<br />
</font><br />
==== BeagleLAB====<br />
* '''Title''': BeagleLAB<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleLAB/<br />
* '''Short project description''': BeagleLAB is an Embedded developer's workbench comprising of must-have hardware/software utilities.<br />
* '''Homepage''': http://code.google.com/p/beaglelab/<br />
* '''Expected results''': <br />
:* A PC free host providing a development environment based on beagle board (running ubuntu 9.04 or later)<br />
:* Host environment with software applications and hardware interfaces to substitute oscilloscope, multimeter & logic analyzers<br />
:* GNOME widgets (software apps) & Linux device drivers for capturing data,storing,comparing and visualization<br />
:* Legacy ports like the serial, parallel ports for device interfacing and control<br />
:* Making an embedded developer's life easier and workbench neater<br />
* '''Contact''': amarendermail[at]gmail[dot]com and saurabhg84[at]gmail[dot]com<br />
<br />
====PREEMPT_RT====<br />
<font color="#C0C0C0"><br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
</font><br />
<br />
====HDDM====<br />
<font color="#C0C0C0"><br />
* '''Title''': HDDM<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/HDDM/]<br />
* '''Short project description''': A multimedia system based on OMAP and linux.<br />
* '''Homepage''': Under construction<br />
* '''Expected results''': Beagleboard as a control center for home theatre system<br />
* '''Contact''': grover.ankur (at) gmail (dot) com<br />
<br />
Note from Dirk: Please see [http://www.syspire.de/node/3 Embedded Mediacenter], too (sorry, German only, use Google translate if needed).<br />
</font><br />
====BeagleVision====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleVision<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beaglevision/<br />
* '''Short project description''': An efficient object recognition framework <br />
* '''Homepage''': http://code.google.com/p/beaglevision/<br />
* '''Description''': BeagleVision will be a fast object recognition framework. The aim of the project is to have a hardware optimized implementation (utilising the DSP and NEON) of state-of-the-art local feature detectors and descriptors on the Beagle Board. BeagleVision will include [http://www.cs.bris.ac.uk/Publications/pub_master.jsp?id=2001018 our recent work] on efficient feature detectors and descriptors, other well-known algorithms (e.g. FAST corner detector and SURF), and efficient matching algorithms for very large datasets (>1M images).<br />
* '''Expected results''':<br />
:* An open source library for developers (a project hosted on code.google.com)<br />
:* A sample application for building recognition in a city scale dataset, to show how: to add new images to the dataset, to use it for location based services, and how to reduce the search time if a GPS is available to get geolocations<br />
:* A wiki for interested developers<br />
:* Reporting the running times of new algorithms on OMAP (as a benchmark) in scientific publications<br />
* '''Contact''': m.ebrahimi at ieee dot org<br />
</font><br />
====Beagle-Arduino hybrid robot====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Arduino hybrid robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Beagle-Arduino+hybrid+robot/<br />
* '''Short project description''': A robot using a Beagleboard for high-level processing and Arduino for low-level control<br />
* '''Homepage''': http://mechomaniac.com/robots<br />
* '''Description''': The Beagle-Arduino robot will use a Beagleboard for high-level robot functions:<br />
** image processing<br />
** artificial intelligence<br />
** speech synthesis<br />
** voice recognition<br />
** internet connectivity<br />
And an Arduino for low-level functions:<br />
** motor / servo control<br />
** sensor input & output<br />
** battery monitoring<br />
The two microcontrollers will be connected by USB, along with a USB webcam mounted on a servo pan/tilt mechanism, and a USB wifi dongle for internet connectivity. Basic tank treads will provide movement, possible being replaced by servo-based legs for a humanoid or dog form.<br />
* '''Expected results''':<br />
:* Easy physical interfacing to the Beagle without having to design and build special expansion boards<br />
:* Image processing using OpenCV with a USB webcam<br />
:* Speech synthesis and voice recognition<br />
* '''Contact''': tim at mechomaniac dot com<br />
</font><br />
<br />
====DJ Audio / Video Mixer====<br />
<font color="#C0C0C0"><br />
* '''Title''': DJ Audio / Video Mixer* '''Contact''': <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/djvideomixer/]<br />
* '''Description''': This is a small, Touch LCD controlled DJ Mixer, which not only is great as a nightclub tool for playing audio -not only reproducing music, actually '''''playing''''' with it-, but also has high end video playback capabilities, thus making it an all-round experience both for the DJ and the audience. It will bring all the experience of professional DJ mixers to users, while being portable, and which when coupled with either a normal projector, or even better, with a PicoProjector, makes a whole experience for audio and video playback in Discos, Bars, Lounges, to mention just a few possible applications. You can even use for your own parties, and it will rock!<br />
* '''Homepage''': [http://code.google.com/p/djvideomixer/]<br />
* '''Expected results''': <br />
** Audio playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Video playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Audio/Video synchronization, allowing song change, video change, etc.<br />
** High end, professional DJ-Mixer audio effects.<br />
** User interface based on LCD and with touchscreen capabilities.<br />
* '''Contact''': jaime_dot_aranguren_at_ieee_dot_org<br />
</font><br />
====schooldog====<br />
<font color="#C0C0C0"><br />
* '''Title''': schooldog<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/schooldog/]<br />
* '''Description''': The purpose is to make an ''off the shelf'' low cost schoolcomputer that can be used on various levels of education. It will be small so students can take it with them and the school just has to provide for input / output items. This way even people that cannot afford laptops can participate in the digital era or schools can provide a robust and good machine for studypurposes.<br />
* '''Homepage''': [http://schooldog.wickedmind.net]<br />
* '''Expected results''': <br />
** Educational linuxbased OS, from USB sticks and SD Cards.<br />
** more general use of BeagleBoard and more public awareness for the powerful small computer.<br />
** Affordable,individual and steady study enviroment<br />
<br />
* '''Contact''': wickedmind<br />
</font><br />
====Disko====<br />
<font color="#C0C0C0"><br />
[[File:Disko_logo.png|thumb|200px|UI Application Framework]]<br />
* '''Title''': Disko - UI Application Framework<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Disko/<br />
* '''Short project description''': Disko is a Linux-based toolkit to build touchscreen- and remote-controllable ui applications. It contains native OMAP framebuffer support and the media content is DSP-accelerated by GStreamer (TI-Codecs).<br />
* '''Homepage''': http://diskohq.org<br />
<br />
* '''Expected results''': Expected result is broad support of Disko by developers of user interfaces and applications for embedded devices.<br />
** SIP - IP telephony support delivered by pjsip and minisip <br />
** Gstreamer - to add an alternative to the xine library and to add the TI Codecs supplied for the DSP.<br />
** Webkit - the great embedded browser OWB of Pleyo (planned for Disko 1.7)<br />
** SVG - at least one SVG engine to have an alternative to Flash. Initial work has already been done at MadButterfly (planned for Disko 1.7) <br />
* '''Contact''': gmadaus [at] berlinux-solutions dot de or mspringer [at] berlinux-solutions dot de<br />
</font><br />
====FETCH====<br />
* '''Title''': FETCH - FPGA enabled Tool Contol Host<br />
* '''beagleboard.org project''': http://beagleboard.org/project/FETCH<br />
* '''Homepage''': http://code.google.com/p/fetch/<br />
* '''Short project description''': A host with a web interface for easy configuration and control of connected tools. The device may also be controlled through a PSTN network using DTMF tones. The BeagleBoard will act as the main server and will also be the host interface for the connected FPGA for the purpose of evaluating the IPs developed on the FPGA.<br />
* '''description : Phase 1 '''<br />
***1) Server capability -- all services (except VNC) to be launched through inetd so that they are started on an on-demand basis. <br />
***-- http server for configuration pages <br />
***-- ssh server (the ssh suite in particular including scp etc.. so that an ftp server can be avoided) for remote login. <br />
***-- bootp server for bootstaping machines on my home network. <br />
***-- VNC for GUI sessions :) <br />
***-- CUPS for network printing <br />
***-- NetHack server :D <br />
***2) Tool Control <br />
***-- The term "Tool Control" here refers to automation of connected tools and Phase 1 of the project will demonstrate this by automation in home (eg. computer, printer, scanner on/off --> (the contoller board with the relays is complete :) ), these devices may be contolled over the internet or PSTN network ) The system will also be hooked to the home electrical network that will enable control over home appliances. A special mode called " Home Alone" will switch on/off lights randomly when no one is at home to give the illusion that the house is occupied ( and hence protect from thefts ;) ). The current relay boards developed use a UART (for RS232 protocol) for control of the equipment but it is planned to use the CAN interface (under developement ) so that longer distances can be covered. <br />
***3) The BeagleBoard will act as a host interfacefor a Nexys2 Xilinx FPGA board and will be used to evaluate the IPs deployed on it. This feature is sort of a tester for the FPGA. <br />
**'''Phase 2 ''' ( only after Phase 1 is completely functional :) ) <br />
***1) CAN interface for the controller nodes replacing the RS232 connections<br />
***2) mgetty (for faxes) and asterisk (VOIP) may be added to the server.<br />
* ''' Contact : ''' akshat dot g dot gupta [at] gmail dot com<br />
<br />
==== ESITeam====<br />
<font color="#C0C0C0"><br />
* '''Title''': ESITeam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ESITeam/<br />
* '''Short project description''': It's a robotic soccer team with vision and intelligence distributed through the use of wireless communication (Zigbee) between robots and PC.<br />
* '''Expected results''': The expected results would have a running and competitive team for the RoboCup's championship this year.<br />
<br />
* '''Contact''': registrosvmora at gmail dot com<br />
</font><br />
==== PupLC====<br />
* '''Title''': PupLC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/PupLC/<br />
* '''Short project description''':Open source control of PLC operated equipment.<br />
* '''Homepage''': No homepage yet<br />
* '''Expected results''': <br />
:*PupLC will be an open source PLC controller. The user will be able to control the PLC's autonomously or by direct control. The direct method will allow the user to change equipment status using a touch screen lcd. The PupLC will control all aspects of the operating equipmet (ie. setpoints, red-hand settings, shutdowns, etc.) Additionally, 24-hours of accumulated system data will be saved to disk and can be accessed via ftp for analysis off-site.<br />
* '''Contact''': alcpo729[at]tds[dot]net<br />
<br />
====Speed-Reader====<br />
<font color="#C0C0C0"><br />
* '''Title''': Speed-Reader<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Speed-Reader/<br />
* '''Short project description''': Speed-Reader is an audio book reader that gives the listener control of the speaker rate.<br />
* '''Homepage''': http://www.nerd1951.com/?page_id=72<br />
* '''Description''': Speed reader allows an audio book to be played back with faster or slower speaker rates. A user interface gives the listener realtime control of the speaker rate. Speed-Reader uses digital speech signal processing to accomplish low distortion timescale modification of speech in real time. Timescale modification of speech is accomplished by selectively repeating segments of speech to slow down the speaker rate or deleting selected speech segments to speed up the speaker rate. Digital signal processing is used to determine which speech segments are candidates for repetition or deletion.<br />
* '''Expected results''':<br />
***--Realtime (during playback) timescale modification of digitized speech using the C64++ DSP<br />
***--Initially read digitized speech from the SD card interface<br />
***--Audio output using the Beagleboard stereo out<br />
***--Initially user interface provided via RS-232 interface<br />
* '''Contact''': harvey dot sugar at nerd1951 dot com<br />
</font><br />
<br />
====DVB-T Receiver====<br />
<font color="#C0C0C0"><br />
* '''Title''': DVB-T Receiver<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': The DVB-T Receiver project aims to implement a fully tunable DVB-T Receiver on the Beagle Board.<br />
* '''Homepage''': Will be launched in the near future (at blog.arsln.org)<br />
* '''Description''': The DVB-T receiver is a senior graduation project that has to be completed in one year (until Summer 2010). It will be a fully tunable DVB-T receiver. It will compatible to receive digital terrestrial TV & radio stations. The goal is to show the capabilities of the Beagle Board and build a DVB-T system from the scratch. The input will be through a ADC daughter-board that is plugged to the USB port. The output will be via the USB port(for portable devices i.e Netbook) or DVI-D. <br />
* '''Expected results''':<br />
***--Capturing broadcast signals(DVB-T) and convert them to discrete time signals<br />
***--Demodulate and encode the incoming signal<br />
***--Video output using the Beagleboard's DVI-D port or via the USB port for portable devices<br />
* '''Contact''': ftharsln at gmail dot com , sulaya05 at gmail dot com<br />
</font><br />
<br />
====ArchMobile: ArchLinux ARM Port====<br />
<br />
* '''Title''': ArchMobile<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/AM/ AM]<br />
* '''Short project description''': ARM Port of the x86-Linux Distribution ArchLinux<br />
* '''Homepage''': [http://www.archmobile.org ArchMobile]<br />
* '''Expected results''': Fully working ArchLinux with X and all other features.<br />
* '''Contact''': rotter.manuel@gmail.com or naeg on Freenode<br />
<br />
==== MythBeagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': MythBeagle<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': MythBeagle aims at bringing MythTV to the beagle; both frontend and backend, including plugins (as far as possible)<br />
* '''Homepage''': not yet; <br />
* '''Expected results''': <br />
** OE recipes for mythtv 0.22, mythplugins 0.22 and whatever might be needed to get things going (including bringing required recipes to the latest version where needed/possible)<br />
** An image for SD card to allow easy install, or a script or recipe to allow easy installation<br />
** some additional configuration notes (configuring MythTV is somewhat a pain...)<br />
** setup should also allow using the beagle only as frontend or backend<br />
* '''Status''': mysql5 recipe has been created (mythtv 0.22 won't use mysql4); recipes for mythtv are there, except for mythweb, documentation/installation work has started;<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
</font><br />
<br />
==== Homebrew SmartPhone ====<br />
<br />
* '''Title''': HomeBrewSmartPhone<br />
* '''beagleboard.org project''': http://code.google.com/p/hbpd<br />
* '''Short project description''': HomeBrewSmartPhone is a project to use the beagleboard to create a community-buildable mobile phone that is powerful enough to also run as a Desktop PC.<br />
* '''Homepage''': http://lkcl.net/reports/hbp <br />
* '''Expected results''': <br />
*** A device capable of Digital Voice as well as Data / Internet Access.<br />
*** A device capable of shutting down into low-power mode and successfully resuming on incoming calls.<br />
*** RF-protected audio circuits that don't have howling feedback from the 3G/GSM Radio module.<br />
*** Full disclosure of all build components (schematics, BOM) under free software licenses.<br />
*** Full documentation of all hardware interconnections<br />
*** Creation of a <b>basic</b> demonstration image that will allow other software developers to participate very early on<br />
*** Addition to the http://handhelds.org site for developers to create GUI-based distros<br />
* '''Contact''': lkcl@lkcl.net or use http://lkcl.net contact box<br />
<br />
==== XBMC ARM Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': XBMC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/XBMC/<br />
* '''Short project description''': XBMC Is a full-feature home-theater application that works on a variety of platforms and operating systems<br />
* '''Homepage''': http://xbmc.org<br />
* '''Expected results''': <br />
*** Feature parity with XBMC x86 and ppc<br />
*** Usage of OpenGL ES 2.0<br />
* '''Contact''': Cory Fields: theuni @at@ xbmc .dot. org<br />
</font><br />
<br />
==== Beagleboard Carputer ====<br />
<br />
* '''Title''': Beagleboard Carputer<br />
* '''beagleboard.org project''': http://beagleboard.org/project/bbcarputer<br />
* '''Short project description''': The Beagleboard Carputer aims to create a fully-integrated system that will feature touchscreen LCD, Bluetooth and USB connectivity, GPS Navigation, Phone features, Wifi, Voice recognition, Multimedia entertainment.<br />
* '''Homepage''': http://bbcarputer.codeplex.com<br />
* '''Expected results''': Provide a fully-integrated system that will feature:<br />
*** 7in touchscreen LCD<br />
*** Wireless connectivity<br />
*** Usb connectivity<br />
*** GPS Navigation<br />
*** Phone features<br />
*** Voice recognition<br />
*** Multimedia entertainment<br />
*** Opensource Application Suite<br />
*** Games<br />
* '''Contact''': Joey Mar Antonio: joeymar.antonio @at@ awsol-i .dot. com<br />
<br />
==== GuideBeagle: Portable monocular SLAM system ====<br />
<font color="#C0C0C0"><br />
* '''Title''': GuideBeagle<br />
* '''beagleboard.org project''': Not yet available.<br />
* '''Short project description''': GuideBeagle is a portable localization and mapping system based on monocular vision. Such a system can be used, among other things, to build:<br />
:*Interactive visitor guidance systems for museums and stores.<br />
:*Artificial Reality tools and games.<br />
:*Mobile robot control systems.<br />
:*Surveillance and security related applications.<br />
:In other words: it solves a Simultaneous Localization and Mapping (SLAM) problem using a single camera as sensor, working on-line, and producing maps with high-level geometrical information (i.e. not just simple punctual visual landmarks on space). It will be based on recent research on the fields of Computer Vision and Mobile Robotics.<br />
* '''Homepage''': http://sites.google.com/site/guidebeagle (This page will be enhanced uninterruptedly.)<br />
* '''Expected results''': <br />
**Mapping --- The final system will allow an user to move by an environment like an office or a small apartment and build a map of it similar to a 3D model with planes and textures, as used in Computer Graphics.<br />
**Localization --- After a map is built, the user can move around the environment, and the system will interactively estimate the geometric location of the camera and the direction it is heading, based on images continuously obtained from the camera.<br />
**Image processing --- Building this system will require the coding of image processing tools that may be useful to many other image processing applications based on the Beagle Board. Some examples are feature detectors and descriptors, edge detectors, template matching by normalized cross-correlation and the Discrete Fourier Transform.<br />
* '''Contact''': nwerneck@gmail.com or nwerneck@usp.br<br />
</font><br />
<br />
==== AutoRobo ====<br />
<br />
* '''Title''': Development of an autonomous robotics platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/autorobo/<br />
* '''Short project description''': Design, prototype and develop an autonomous aerial vehicle system around BeagleBoard, allowing experimentation with real-time control and computer vision algorithms.<br />
* '''Philosophy''':<br />
:* make robotics and embedded control accessible and fun<br />
:* stimulate cross-field learning and collaboration<br />
:* leverage modularity and reuse to get more done, quicker <br />
* '''Technical goals''':<br />
:* develop generalised physics model for eg computing optimal PID controlled motor outputs<br />
:* decouple high-update-rate sensors from lower-rate output control<br />
:* employ OpenCV for visual tracking/SLAM/feature detection<br />
:* build lean tracked (land) vehicle<br />
:* build lean quad-rotor (air) vehicle<br />
:* use a shared, modular code-base and electronics platform (Beagle and IGEPv2) <br />
* '''Homepage''': http://code.google.com/p/autorobo/<br />
* '''Expected results''': Initial bringup of a tracked vehicle via dual-motor controller via Beagle's PWM outputs. Utilisation of 3-axis accelerometer and 3-axis gryo via I2C and/or SPI buses, enabling more advanced control<br />
* '''Contact''': ''daniel (dot) blueman (at) gmail (dot) com''<br />
<br />
==== Beagle-Walker ====<br />
<br />
* '''Title''': Design of a automatic dog-walker robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleWalker/<br />
* '''Short project description''': Develop an autonomous dog-walker robot<br />
* '''Homepage''': http://code.google.com/p/beaglewalker/<br />
* '''Expected results''': <br />
**The main goal of the system is analyze the feedback between the dog and the robot to track where the dog is going and where the robot should go.<br />
**Let the dog walk only in places previously programmed by the dog's owner making use of basic SLAM algorithms. <br />
**avoid any obstacles/vehicles.<br />
* '''Contact''': ''darthdj at gmail dot com''<br />
<br />
==== nullDC / Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nullDC<br />
* '''Expected results''': For the contest: A working build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
</font><br />
<br />
==== MyoVox ====<br />
* '''Title''': MyoVox<br />
* '''beagleboard.org project''': <br />
* '''Short project description''': <br />
* '''Homepage''': <br />
* '''Expected results''': <br />
* '''Contact''': smcgill3 [at] seas[.]upenn [.] edu<br />
<br />
==== Beagle-Eye ====<br />
<br />
* '''Title''': Beagle-Eye<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle-Eye/ Beagle-Eye]<br />
* '''Short project description''': A beagle-eyed guide for the visually challenged.<br />
<br />
* ''' Hardware''':<br />
** A pair of calibrated USB cameras, mounted on the user's shoulders, such that the combined field of view covers at least 180 degrees.<br />
** One or more linear actuators connected through RS-232, situated on one of the user's limbs.<br />
** Stereo headphones.<br />
** USB GPS Dongle.<br />
<br />
* '''Description''':<br />
** Low frame rate real-time video is used to guide the user towards a specified destination.<br />
** The GPS provides coarse location.<br />
** The stereo camera setup provides a wide field of view, along with coarse depth information.<br />
** Map information, combined with real time video is used to esimate location and orientation more accurately.<br />
** Simple object recognition techniques are employed to recognize parts of the environment.<br />
** The audio setup and the actuator(s) are used either in tandem or interchangeably to guide the user. This can be customized as required. Some possibilities include:<br />
*** A short periodic 3D sound generated to indicate the direction in which the user is to walk.<br />
*** The user is alerted about approaching obstacles by firing the actuator at a frequency inversely proportional to the distance to the obstacle. This distance can be computed using depth information computed from pairs of images.<br />
*** Information about the environment, such as "Pedestrian Crossing in 20m" can be relayed through audio.<br />
<br />
* '''Possible Enhancements''':<br />
** More comprehensive localization techniques, such as SLAM, can be used to improve the accuracy of the system. This will also open doors to indoor navigation, where the GPS fails.<br />
** Detection, segmentation and recognition of text (such as signboards and street names) in the environment will ensure less errors in navigation.<br />
<br />
* '''Expected Results''':<br />
** A navigation tool for the visually challenged, using audio and linear actuators to communicate with the user.<br />
<br />
* '''Contact''': leatherbrain at gmail dot com<br />
<br />
==== BeaglePod ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeaglePod<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglepod/]<br />
* '''Short project description''': BeaglePod is an IPod plug-in replacement for car stereo's that are IPod Ready. The BeaglePod uses gstreamer as an audio/video player and is controlled via the car stereo head unit using Apple Accessory Protocol. <br />
* '''Description''': The BeaglePod is an audio/video player for cars equipped with "IPod Ready" stereos. Using the Apple Accessory Protocol the car stereo is used to select and control the playback of media on the BeaglePod. Adding a video monitor the BeaglePod can also become a video player running all the audio through the car stereo with full pause, play, stop control using the car's stereo head unit. Using a software implementation of the Apple Accessory Protocol the BeaglePod is connected to the car stereo via a USB->TTL cable.<br />
* '''Expected Results''':<br />
** Play audio/video media files from the Beagleboard using the car stero to control playback and track selection.<br />
** Audio will playback through car's exist speaker.<br />
** With gstreamer dsp support HD playback of video with in car lcd.<br />
* '''Contact''': velorider [X] publicemail [X] us<br />
</font><br />
<br />
==== MART ====<br />
* '''Title''': Autonomous modular robot<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': Build an autonomous robot to enter the Eurobot 2010 competition<br />
* '''Homepage''': (only in Czech) http://eurobot.matfyz.info/<br />
* '''Full Description''': Goal of this project is to build an autonomous modular robot, that will be able to compete in the Eurobot competition. This project includes following:<br />
<br />
** '''HW''':<br />
** Custom beagle daughter-card (including kernel driver patches):<br />
*** CAN (Controller area network) able to sustain 1Mbit/s, using embedded cortex-m3 controller<br />
*** Battery backed up RTC<br />
*** Dual power - battery and/or adapter, with battery management (current consumption sensing and charging) <br />
*** Second serial and i2c headers<br />
*** (optional) Ethernet controller 10/100Mbit<br />
** Custom motor, servo and stepper motor drivers and IO boards<br />
*** everything connected through CAN<br />
<br />
** '''SW''':<br />
** Modular architecture, for simple modification<br />
** OpenCV integration for play field object identification<br />
** optimalizations for NEON (and DSP)<br />
<br />
* '''Contact''': Michal dot Demin at Gmail dot Com<br />
<br />
==== CamCast ====<br />
* '''Title''': Webcam broadcast server/relay<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/CamCast/]<br />
* '''Short project description''': Webcam broadcast platform for USB webcams<br />
* '''Homepage''': <br />
* '''Full Description''': The goal of this project is to utilize the beagleboard as a low cost platform for webcam video feeds.<br />
Server capability:<br />
<br />
** Broadcast webcam feeds for directly connected USB webcams<br />
** Relay webcam feeds from other servers, typically connected over wi-fi<br />
** Decimate MJPEG streams to match bandwidth limits<br />
** Monitor and control streams via HTTP<br />
** Advertise HTTP services locally via Zeroconf<br />
<br />
The beagleboard will require a functional Linux gspca driver for all USB webcams in use as well as USB wi-fi for remote service. Linux Zeroconf service must also be included.<br />
<br />
* '''Contact''': spiderkarma at gmail dot com<br />
<br />
====Beagle SecMon====<br />
<br />
* '''Title''' : Beagle Security Monitoring over Web <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle+SecMon/ BeagleSecMon]<br />
* '''Short project description''': This project proposes to control and transmit audio and video from a remote place using the beagleboard as a webserver.<br />
* '''Expected results''': The system will control one or more digital cameras with pan, tilt and zoom functions, and microphones. Besides, it can be configured to send information to a pre registered cell phone when movement is detected. Also, audio and video can be accessed using internet from any place.<br />
* '''Contact''': cborges at ifsc dot edu dot br====<br />
<br />
====PortablePlateRec====<br />
<br />
* '''Title''' : Beagle Portable Plate Recognition <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/PortablePlateRec/ PortablePlateRec] <br />
* '''Short project description''': A portable system for automatic number plate recognition (ANPR) using BeagleBoard.<br />
* '''Expected results''': The goal of this project is to develop a portable system for automatic number plate recognition (ANPR) using BeagleBoard. It includes the following:<br />
** receiving images from a camera;<br />
** applying signal processing algorithms for plate localization, orientation and sizing, image normalization, and character segmentation;<br />
** optical character recognition (for instance, Tesseract);<br />
** possible access to a database to check the plate against law infringements.<br />
<br />
* '''Contact''': fpacheco at ml1 dot net<br />
<br />
====Digital Multimedia Frame====<br />
<br />
* '''Title''' : Digital Multimedia Frame<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a photo, video and music application who use a touchscreen display<br />
* '''Expected results''': The goal of this project is to get photo, video, music from memory card or from a network. <br />
<br />
** Scan network to multimedia file. <br />
** Create automatically a slideshow when we are in photo mode.<br />
** Create automatically a music list.<br />
** Play video<br />
** Add basic operation available for picture (rotate, resize...)<br />
** touch screen will be used to simplify action.<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
====Beagle Utility====<br />
<br />
* '''Title''' : Beagle Utility<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a box with lcd screen to be able to encrypt, format, wipe, clone, find virus, search rootkit .... a hd or memory card. A menu with different operation is displayed to user.<br />
* '''Expected results''': The goal of this project is to be able to do some operation on harddriver, memory card <br />
<br />
** Encrypt <br />
** Format<br />
** Wipe<br />
** Clone<br />
** find virus<br />
** Rootkit<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
===Contest #2 projects===<br />
<br />
Please don't add new projects, contest #2 is closed.<br />
==== James ====<br />
1st [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/James James]<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. <br />
* '''Expected results''': Updated recipes for all relevant packages on OpenEmbedded. A script to install the needed packages to an Angstrom image (generated by Koen's generator) and documentation on how to configure things.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
</font><br />
====BeagleEPD====<br />
2nd [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': E-Ink Interface Board and Driver for beagleboard<br />
* '''Homepage''': [http://elinux.org/BeagleEPD BeagleEPD]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleepd/<br />
* '''Short project description''': This project aims to interface an E-Ink display directly with a beagleboard. This is done by creating an interface board that is connected to the Beagleboard expansion header and converts the relevant gpio signals into the levels appropriate for interfacing with the E-Ink display controller. The second part is to write a driver which is a port of am300epd.c from mach-pxa to mach-omap in order to support the E-Ink broadsheet framebuffer driver directly on beagleboard. All of this results in making it possible to connect any E-Ink display controller to a Beagleboard (via the expansion header) and to then treat any E-Ink display as another framebuffer.<br />
* '''Expected results''': Schematic for interface PCB between Beagleboard and E-Ink display controller board. A beagleepd.c mach-omap driver that will setup and control the IO pins appropriately.<br />
* '''Contact''': jayakumar at IRC (freenode, oftc) or jayakumar.lkml@gmail.com<br />
</font><br />
==== nullDC / Beagle ====<br />
<br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with newly added support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nulldc_beagle<br />
* '''Expected results''': For the contest: A WIP (but working) build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
===Contest #1 projects===<br />
<br />
====qemu-omap3====<br />
<br />
* '''Title''': support beagle board emulation in qemu<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]<br />
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.<br />
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]<br />
* '''Expected results''':<br />
** booting linux kernel and rootfs from nand and mmc image<br />
** Wiki page how to run qemu-omap3 for beagle board<br />
* '''Submission''':<br />
** http://code.google.com/p/qemu-omap3/wiki/UserManual<br />
* '''Contact''': yajin AT vm-kernel.org<br />
<br />
====openGPS====<br />
<br />
* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites. <br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** development of a display app with moving map capabilities<br />
** development of a user interface for handheld apps<br />
** integration with suitable LCD display<br />
** interface to map files on SD card<br />
** Wiki page on GPS receiver functions and features<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====Beagle Conference System====<br />
<br />
* '''Title''': Use beagle to come up with a conferencing system for home users<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]<br />
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.<br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.<br />
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).<br />
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.<br />
** The software shall also provide for ways to chat (text) with the users.<br />
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====BeagleRC====<br />
<br />
* '''Title''': Use a beagle board to drive a remote controlled car.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos. <br />
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml<br />
* '''Expected results''':<br />
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.<br />
* '''Contact''': code at chrisd dot info<br />
<br />
====PREEMPT_RT====<br />
<br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
<br />
====USB Support in U-boot ====<br />
2nd [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.<br />
* Homepage: [[U-boot musb gadget support]]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/<br />
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).<br />
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.<br />
* '''Contact''': ddompe at IRC<br />
</font><br />
<br />
==== James ====<br />
<br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': To be Added...<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html<br />
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
<br />
====BeagleBot====<br />
1st [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Board powered robot<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]<br />
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...<br />
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]<br />
* '''Expected results''':<br />
** Partly autonomous robot<br />
** PC controlling of the robot<br />
* '''Contact''': antti at hervanta.com<br />
</font><br />
<br />
====Android Cupcake for BeagleBoard====<br />
<br />
* '''Title''': Android Cupcake for BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]<br />
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard. <br />
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]<br />
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====FreeBSD port to BeagleBoard====<br />
<br />
* '''Title''' : A port of FreeBSD-arm to the BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]<br />
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.<br />
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.<br />
* '''Contact''': AsqYzeron====FreeBSD port to BeagleBoard====<br />
<br />
==Judging==<br />
<br />
===Judges===<br />
* Jason Kridner (jkridner)<br />
* Koen Kooi (koen)<br />
* Dirk Behme (dirk2)<br />
* Steve Sakoman (sakoman)<br />
* Hunyue Yau (ds2)<br />
* Mans Rullgard (mru)<br />
* Gregoire Gentil (gregoiregentil)<br />
<br />
===Past Judges===<br />
* Robert Kuhn (robertk)<br />
<br />
===Rules===<br />
* Judges cannot participate in the contest.<br />
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.<br />
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.<br />
* All voting will be public and logged on this page.<br />
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.<br />
* To follow up on shipping details, contact ''beagleship at list.ti.com''.<br />
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.<br />
<br />
===Criteria===<br />
* All new content must be open source as determined by the OSI.<br />
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.<br />
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]<br />
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.<br />
* "Wow" or "coolness" factor from usefulness/user experience point of view<br />
* Overall quality of the submission<br />
* Technical complexity<br />
** "Coolness" of the technical solution, even if it isn't useful for all the masses<br />
** Amount of work needed, i.e. x hours or x days?<br />
* Angstrom recipe for image<br />
* Documentation for the demo<br />
* Running power consumption<br />
* Use of DSP and SGX<br />
* Ease of use<br />
<br />
===Contest #1===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-01-11<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]<br />
|3<br />
|<br />
|3<br />
|2<br />
|<br />
|3<br />
|2<br />
!13<br />
|-<br />
|[[BeagleBoard/contest#openGPS|openGPS]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]<br />
|1<br />
|<br />
|<br />
|1<br />
|3<br />
|<br />
|2<br />
!7<br />
|-<br />
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]<br />
|<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
!5<br />
|-<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
!17<br />
|-<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|2<br />
|2<br />
|3<br />
|4<br />
|3<br />
|4<br />
|3<br />
!21<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|<br />
|3<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!4<br />
|-<br />
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!3<br />
|-<br />
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|1<br />
|Monday, January 12, 2009<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|-<br />
|}<br />
:Congratulations ;-) [[User:RobertK|RobertK]] 11:30, 12 January 2009 (UTC)<br />
<br />
There is a nice [http://www.linuxdevices.com/news/NS6362979448.html LinuxDevices.com BeagleBot cruises on Linux] article about contest #1 winner, too.<br />
<br />
===Contest #2===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-03-01<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|6<br />
|7<br />
|5<br />
|7<br />
|3<br />
|5<br />
|<br />
!33<br />
|-<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|3<br />
|3<br />
|2<br />
|3<br />
|5<br />
|3<br />
|<br />
!19<br />
|-<br />
|[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]<br />
|1<br />
|<br />
|3<br />
|<br />
|2<br />
|2<br />
|<br />
!8<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|2<br />
|Monday, March 2, 2009 <br />
|[[BeagleBoard/contest#James|James]]<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|-<br />
|}<br />
<br />
==Other background==<br />
<br />
==Contest #1==<br />
<br />
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58<br />
<br />
==Contest #2==<br />
<br />
* [http://www.beagleboard.org/irclogs/index.php?date=2009-02-13#T15:35:43 IRC Log of discussion]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/661879a591dc396d Announcement at mailing list]<br />
* [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html Blog announcement]</div>Dirkhttp://elinux.org/BeagleBoard/contestBeagleBoard/contest2010-01-21T16:22:04Z<p>Dirk: Add new project to voting table</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Image:beagle_first_place.png|thumb|right]]<br />
==Contest Announcements==<br />
===Sponsored Project Program===<br />
The [[BeagleBoard]] Software Design Contest has now been replaced with the [[BeagleBoard/contest#Contest_projects| BeagleBoard Sponsored Projects Program]] (formerly known as contest #3). The biggest difference is that we'll be giving 2 boards per week to projects as they are '''[[BeagleBoard/contest#Approved_projects|approved]]''', rather than waiting until they are completed. Also, successfully completed projects may be rewarded with higher-end BeagleBoard-derived systems, such as a [http://gumstix.com/store/catalog/product_info.php?products_id=229 Gumstix Palo43] or a [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book] (BeagleBoard based). You are encouraged to make your entries [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|now]].<br />
<br />
If your project is listed as a winner and you haven't received your board, check with ''beagleship at list.ti.com''.<br />
<br />
===Contest #2===<br />
<br />
''Contest #2 is finished. See [[BeagleBoard/contest#Winners_2|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html contest #2]. This contest is about giving away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to the winner and another one to the runner-up. [[BeagleBoard/contest#Judges|Judges]] will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, February 27, 2009 (afternoon) <br />
* '''Voting goes over weekend, end: Sunday, March 1, 2009 (afternoon)'''<br />
* Shipping board to winner: Monday, March 2, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get before this revision is publically available by DigiKey (~end of March 2009).<br />
</font><br />
<br />
===Contest #1===<br />
<br />
''Contest #1 is finished. See [[BeagleBoard/contest#Winners|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, January 9, 2009 (afternoon) <br />
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)<br />
* Shipping board to winner: Monday, January 12, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).<br />
</font><br />
<br />
==Project ideas==<br />
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:<br />
* Stable musb<br />
** ISOCH support<br />
** High-speed USB TV tuner support<br />
** Hot-plug support for OTG (host and client)<br />
* USB Digital TV tuner (either ATSC or DVB-T)<br />
** Hauppauge HVR950 suggested as reference<br />
* Projection TV coupled with the Pico<br />
* Audio record<br />
* Latest kernel version<br />
* USB camera support<br />
** gspca driver - need to validate with multiple cameras<br />
** <font color="#C0C0C0">UVC driver (I understood from Koen this is working)</font><br />
* Fixing bugs listed on code.google.com<br />
* Android port and various applications<br />
* <font color="#C0C0C0">EHCI support (done)</font><br />
* <font color="#C0C0C0">USB support in u-boot (partially done by first contest, but still needs work)</font><br />
* <font color="#C0C0C0">Consumer IR remote control via LIRC (already in feed; do 'opkg lirc')</font><br />
<br />
See also [[BeagleBoard/Ideas-2009]] for more ideas.<br />
<br />
==Contest projects==<br />
Please add your project you like to participate at Sponsored Projects Program (contest #3) to [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|Sponsored Projects Program projects]]. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1.1").<br />
<br />
===Sponsored Projects Program (Contest #3) projects===<br />
<br />
If you like to join Sponsored Projects Program (contest #3), please add your project here the same way like done for contest #1 and #2 below. If you participated already previous contests, please copy your project description to this contest, again. This will let everybody know that the project is still alive and that you want to participate Sponsored Projects Program.<br />
<br />
====Approved projects====<br />
From the project proposals, [[BeagleBoard/contest#Sponsored_Project_Program|approved projects]] will get a BeagleBoard Rev C at the '''beginning''' of their project to help them execute:<br />
<br />
{|border=1<br />
!Project<br />
!Approved<br />
!Comment<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Gregoire<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Revolt 2405|Revolt 2405]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Gentoo Linux ARMv7 support|Gentoo Linux ARMv7 support]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Accelerated_USB_Graphics_Adapter|Accelerated USB Graphics Adapter]]</font><br />
|<font color="#C0C0C0">Week 21</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#picoFlamingo|picoFlamingo]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle Synth |Beagle Synth]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#USB Scope |USB Scope]]</font><br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Irrlicht|Irrlicht]]<br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleHam|BeagleHam]]</font><br />
|<font color="#C0C0C0">Week 24</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Apertus_open_source.2Fhardware_cinema_camera|Apertus Digital Cinema Camera ]]<br />
|<font color="#C0C0C0">Week 25</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Handheld_Lab|Handheld Lab]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TCF_Agent_Port|TCF Agent Port]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Traveler|Beagle-Traveler]]</font><br />
|<font color="#C0C0C0">Week 27</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#OMAP Emulator|OMAP Emulator]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TUD:OS_on_Beagleboard|TUD:OS on Beagleboard]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#QEMUonARM|QEMUonARM]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#EGLIBC|EGLIBC Support]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#RT-Beagle|RT-Beagle]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ONAS|ONAS]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Math-NEON|Math-NEON]]<br />
|<font color="#C0C0C0">Week 32<br />
|<font color="#C0C0C0">5 votes<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Happiness_Device_for_Cerebral_Palsy_Kids|Device for Cerebral Palsy Kids]]</font><br />
|<font color="#C0C0C0">Week 32</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Turk|Turk Platform]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#hApplause|hApplause]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#eLazarillo|eLazarillo]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">1 vote</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#PREEMPT_RT|PREEMPT_RT]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#HDDM|HDDM]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleVision|BeagleVision]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#DJ Audio / Video Mixer|DJ Audio / Video Mixer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#schooldog|An individual lowcost schoolcomputer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Disko|Disko - UI Application Framework]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ESITeam|ESITeam]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#DVB-T_Receiver|DVB-T_Receiver]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">8 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#UPnP.2FDLNA_AV_client_renderer_and_transcoding_server|UPnP/DLNA AV client renderer and transcoding server]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Speed-Reader|Speed-Reader]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Arduino_hybrid_robot|Beagle-Arduino hybrid robot]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#XBMC_ARM_Port|XBMC Arm Port]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#GuideBeagle:_Portable_monocular_SLAM_system|Portable monocular SLAM system]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#MythBeagle|MythBeagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeaglePod|BeaglePod]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle_SecMon|Beagle SecMon]]</font><br />
|<font color="#C0C0C0">2010 - Week 3</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Touchscreen_LCD_support| Touchscreen LCD support]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FMframe |FMframe]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleSCI |BeagleSCI]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Pictouch|Pictouch]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Fotogenic |Fotogenic]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyGTee|MyGTee handheld]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Tourister_using_Hand_Gestures_and_HMD_on_Beagleboard|Beagle Tourister]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Medical Notebook|Medical Notebook]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#miniECG|miniECG]]<br />
|<br />
|<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#remoteBillBoard|Remote Bill Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleWacom|Wacom Tablet driver for Beagle Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleLAB|BeagleLAB]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FETCH|FETCH]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#PupLC|PupLC]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#ArchMobile:_ArchLinux_ARM_Port|ArchMobile]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Homebrew_SmartPhone|Homebrew SmartPhone]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagleboard_Carputer|Beagleboard Carputer]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#AutoRobo|AutoRobo]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Walker|Beagle-Walker]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyoVox|MyoVox]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Eye|Beagle-Eye]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MART|MART]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#CamCast|CamCast]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#PortablePlateRec|PortablePlateRec]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Digital_Multimedia_Frame|Digital Multimedia frame]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#.28Speech.29_Scrambler_Beagle| (Speech) Scrambler Beagle]]<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Utility|Beagle Utility]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
Rule: In each week, each judge has two points (two "1") to enter for his favorite project. The two projects with the most votes will be approved. The plan is to have final decision every Friday morning.<br />
<br />
==== Revolt 2405====<br />
<font color="#C0C0C0"><br />
* '''Title''': Revolt 2405<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Revolt2405/<br />
* '''Short project description''': First mission of a first person shooter style game using Ogre3D.<br />
* '''Homepage''': http://www.dcbcyber.com/revolt2405/wordpress<br />
* '''Expected results''': Expected results would be to have a playable game demo using Ogre3D for rendering. There will be sound and music. For controls I want to have the option of using keyboard and mouse or using controls like those found on hand held gaming devices. We would also like to have this playable on a small LCD as well as on a monitor connected to the DVI port.<br />
* '''Contact''': n2vdy at yahoo dot com or dbatzle at dcbcyber dot com<br />
</font><br />
==== Touchscreen LCD support ====<br />
<br />
* '''Title''': Touchscreen LCD support <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': The project will add the touch screen support to Beagle board<br />
The following are the components that i am planning of using<br />
:*The LCD breakout board is http://www.sparkfun.com/commerce/product_info.php?products_id=8600<br />
:*The touch screen is http://www.sparkfun.com/commerce/product_info.php?products_id=8977<br />
:*The touch screen connector is http://www.sparkfun.com/commerce/product_info.php?products_id=9104<br />
<br />
Another option is buying a full LCD with touch screen option<br />
:*The product link is http://www.sparkfun.com/commerce/product_info.php?products_id=257.<br />
:*I would create a system and hardware like this video http://www.youtube.com/watch?v=foWnDZ3eQto&feature=related<br />
<br />
* '''Homepage''': http://pradheeptce.googlepages.com/ yet to be fully completed.<br />
<br />
* '''Expected results''': <br />
**Linux driver to add LCD with touch screen support<br />
**The breakout board(preferably single layered as it can be created at home)gerber for attaching with beagle which will be created using FreePcb(www.freepcb.com).You can see the photos of my RFID Based Access Control system project there.<br />
**Wiki page to describe the entire development method<br />
* '''Contact''': pradheep_sh[at]tce[.]edu<br />
<br />
==== Gentoo Linux ARMv7 support ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Official Gentoo Linux ARMv7 support<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Gentoo/<br />
* '''Short project description''': Build ARMv7 optimized packages and stages for Gentoo Linux created officially by Gentoo developers.<br />
* '''Description''': The project is for providing official support for ARMv7-based devices like the Beagleboard, we will provide stages and packages optimized for ARMv7 processors so any owner of an ARMv7 device can get an optimized system. At the moment Gentoo only provides and supports ARMv4 and ARMv5TE, therefore we would like to expand our official support to the more powerful ARMv7 subarchitecture.<br />
* '''Homepage''': http://www.gentoo.org/proj/en/base/embedded/ http://www.gentoo.org/doc/en/handbook/handbook-arm.xml http://www.gentoo.org/proj/en/base/embedded/handbook/<br />
* '''Expected results''': <br />
**Allow Gentoo users to have ARMv7 optimized stages and packages.<br />
**Document the installation on the provided boards.<br />
* '''Contact''': armin76[at]gentoo[.]org , solar[at]gentoo[.]org<br />
</font><br />
==== TUD:OS on Beagleboard ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TUD:OS on Beagleboard <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/TUD%3AOS+on+the+Beagleboard/]<br />
* '''Short project description''': Port the L4-Microkernel based TUD:OS Operating System to the Beagleboard<br />
* '''Homepage''': will follow<br />
* '''Description''': <br />
** '''What the heck?''' The TUD:OS operating system is a L4 microkernel based operating system, with good real-time and security properties, developed at the TU Dresden. <br />
** '''Microkernel-based''': The microkernel approach allows it to to reduce the trusted computing base (the amount of code that has to be trusted) by running small trusted applications side by side with non-trusted applications, all as unprivileged user mode applications. Further, it is possible to run real-time applications side-by side with non real-time applications. Also device driver run in user-mode and thus a crash of a device driver will not lead to an whole system crash and in the best case the driver can be restarted and the system will keep on running.<br />
** '''Familiar Environment''': While offering the above mentioned vantages, TUD:OS still offers a familiar environment by the possibility to run one or more instances of L4Linux. L4Linux is a Linux port the Fiasco microkernel which is binary compatible to native Linux but runs in deprivilieged usermode.<br />
** '''What do we get from this project?''' ''Briefly: A fundament to build embedded [realtime] systems [with a exceptionally small trusted computing base].'' Further a possibility to run multiple virtualized linux instances on the beagleboard. A good documentation how to build such systems. And last but not least a (hopefully cool ;) demo showing that it acutally works , perhaps like the one found at [http://demo.tudos.org demo.tudos.org] (somewhat outdated). <br />
*'''Contact:''' dvogt[at]os[.]inf[.]tu-dresden[.]de ([[User:Dvogt|Dvogt]])<br />
</font><br />
==== picoFlamingo ====<br />
<font color="#C0C0C0"><br />
* '''Title''': picoFlamingo <br />
* '''beagleboard.org project''': http://beagleboard.org/project/picoFlamingo/<br />
* '''Short project description''': A portable presentation system for the BeagleBoard and the picoDLP projector<br />
* '''Homepage''': http://papermint-designs.com/picoflamingo<br />
* '''Expected results''': <br />
** An application to perform presentations including 3D elements.<br />
** A basic hardware specification for a portable presentation system.<br />
** A remote interface for wireless control of the presentation.<br />
** A demonstration of the possibilities provided by the BeagleBoard, the OMAP 3 platform and the picoDLP.<br />
** Hopefully a lightweight 3D render engine for OpenGL ES 2.0.<br />
** A lot of fun!!!... <br />
* '''Contact''': dmo[at]papermint-designs[.]com<br />
</font><br />
==== Accelerated USB Graphics Adapter ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Accelerated USB Graphics Adapter <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': USB-attached Graphics Card supporting OpenGL acceleration for XFree86<br />
* '''Homepage''': http://www.employees.org/~mschulma/beagleboard/cerberus/<br />
* '''Expected results''': <br />
** Use the Beagleboard to attach another monitor to a PC running Linux, and run a graphics intensive application on the expanded virtual desktop without slowing the main CPU.<br />
* '''Contact''': mschulma [at] employees [dot ] org<br />
</font><br />
==== Apertus open source/hardware cinema camera ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Apertus Digital Cinema Camera<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Apertus/<br />
* '''Short project description''': A digital camera controler for an Elphel open hardware camera. The beagle board will be used as a realtime viewfinder unit and hardware camera control.<br />
* '''Homepage''': http://cinema.elphel.com<br />
* '''Expected results''': We intend on creating a community driven open source cinematic HD camera for a professional environment. <br />
The image is provided by an Elphel camera (elphel.com, open source camera). A beagle board would be connected to an elphel camera using ethernet. The beagle board runs a lightweight UI that allows user to view the live feed from the camera on an external display (dvi or s-video). It also allows to trigger recording and change camera settings using a user interface. The user interface is software based (on screen) + hardware based using buttons and knobs if possible (I2C interface of the beagle board would be used). This project will take 2-6 months to have visible results. The feasibility of this project has been discussed on the Beagle Board group, with positive answers (cfr. http://groups.google.fr/group/beagleboard/browse_thread/thread/6c55a10dd598bb6/e946107bd0a807b8#e946107bd0a807b8 )<br />
* '''Contact''': philippe dot jadin at gmail dot com<br />
</font><br />
==== FMframe ====<br />
<br />
* '''Title''': FMframe<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': FMframe is a picture frame application coupled with an rss news reader and clock/alarm functionality<br />
* '''Homepage''': not yet; in a few days I will try to come up with a website with some preliminary screenshots.<br />
* '''Expected results''': Plan is to make a picture frame application. Hardwarewise the beagle will connect to a DVI display. Softwarewise it will be a picture frame optionally with a clock on top of the photo (either a big semi-transparent clock in the center or a smaller clock in the corner). There will also be an alarm function which can play a preselected mp3 file when the alarm time is reached. Apart from showing pictures the frame can also show news from a user definable rss feed (e.g. cnn.com), Normally this will be in a ticker-tape at the bottom of the picture. When the user presses a button when a specific topic is shown the full message pops up. Probably there will be dedicated provisions for weather, giving the weather forecast if desired (in a style as done by the google weather widget). When waking up the frame can show the weather with the scrolling news or (user selectable) just a list of headlines. When the alarm is switched off the display acts like a regular photo frame again.<br>User interaction will be through a remote control. Alternate inputs could be touch screen (if I get access to an affordable one) or keyboard (less convenient but it does allow people without IR receiver to control the device.<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
<br />
==== BeagleSCI ====<br />
<br />
* '''Title''': BeagleSCI<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': BeagleSCI aims to use the BeagleBoard as a platform for scientific computation and instrumentation (SCI).<br />
* '''Homepage''': http://sourceforge.net/projects/beaglesci/<br />
* '''Expected results''': As a start, the initial goal would be to use the BeagleBoard as a logger of a seismometer. This would involve interfacing a 12-bit ADC chip and writing a driver for it. Data read from the instrument can be displayed by the BeagleBoard through a monitor or send the data to a remote computer via RS-232/RS-485.<br />
* '''Contact''': sherdon dot uy at gmail dot com<br />
<br />
==== Pictouch====<br />
<br />
* '''Title''': Pictouch<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Mobile and Projected Touch user interface<br />
* '''Homepage''': not yet<br />
* '''Expected results''': The goal is to build a new Tactile Interface system based on beagleboard and the DLP picoprojector. Currently, the project make the use of JavaFX to support Multi-Touch (and Multi-User) and of 2 basic webcam, in order to build a low cost gesture recognition system.In the classical case of use, the interface is projected onto a classical table.Users interact directly with their fingers on the projected interface.<br />
<br />
* '''Contact''': maxired at gmail dot com<br />
<br />
==== Fotogenic ====<br />
<br />
* '''Title''': Fotogenic<br />
* '''beagleboard.org project''': not yet - but project is already in progress<br />
* '''Short project description''': Bring network connectivity to plain old vanilla picture frames<br />
* '''Homepage''': www.sourceforge.net/projects/fotogenic<br />
* '''Expected results''': This project brings wired, WiFi and bluetooth connectivity and management to plain old picture frames. The project selects pictures from your photo database, resizes them for the picture frame's native resolution, embellishes them with web and home automation information sources before presenting them to the photo frame by making the BeagleBoard appear to be a USB pendrive...! Right click a photo on your laptop and select "Show on picture frame now!". Manage many photo frames centrally and much much more... Includes "wave gesture" interface to wave over picture frame for next photo... Also works with Eye-Fi SD memory cards to make photos appear on photoframe moments after taken...!!<br />
* '''Contact''': horse_dung at hotmail dot com<br />
<br />
==== Beagle Synth ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Synth<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-synth/<br />
* '''Short project description''': DSP MIDI synthesizer based around the beagleboard<br />
* '''Homepage''': http://code.google.com/p/beagle-synth/<br />
* '''Expected results''': Initially a basic MIDI controllable subtractive synth with 3 oscillators, low pass, high pass, and band pass filters, 2 envelope generators, and 2 LFO's. From there the intention is to add some type of control surface (either physical controls or perhaps a touch screen), some effects (phaser, distortion, reverb), and perhaps other types of synthesis options (FM, additive, maybe some type of patchibility). The result will be a fully featured MIDI instrument comparable to many commercial synths. This project is to be a learning experience with the intention of exploring using DSP for music synthesis. As of now this project is in the concept phase and is still in need of hardware for implementation.<br />
* '''Contact''': dpanseri [at] gmail [dot] com<br />
</font><br />
==== USB Scope ====<br />
<font color="#C0C0C0"><br />
* '''Title''': USB Scope<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': USB diagnostics to aid driver development for USB devices<br />
* '''Homepage''': none yet<br />
* '''Expected results''': This project will use the BeagleBoard as a USB proxy between any USB device and a host computer connected via the OTG port. This will allow the BeagleBoard to snoop, compare and modify USB traffic which can assist both commercial and open source development of drivers and diagnosis of issues. Other ideas could be examined such as a USB-TCP/IP-USB proxy to remotely connect USB devices. Open or free software equivalents exist, but hardware monitoring devices only exist as expensive commercial products. <br />
* '''Contact''': horse_dung at hotmail dot com<br />
</font><br />
==== Irrlicht ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Irrlicht<br />
* '''beagleboard.org project''': no<br />
* '''Short project description''': A fully-featured 3D render engine with ogl-es 1.x and 2.x support<br />
* '''Homepage''': http://irrlicht.sourceforge.net<br />
* '''Expected results''': <br />
** Hardware optimized core routines for optimal OMAP support<br />
** Support of ogl-es 2.x (the 1.x driver is reportedly running on the board)<br />
** Full framerate (60FPS) rendering of q3 alike scenes<br />
** The engine also offers SW rendering, allowing to target for other OMAPs as well, but would require more tweaking in the render optimizations<br />
** We can port one of the demo apps from our apps contest to show the full applicability <br />
* '''Contact''': hybrid[at]users[.]sourceforge[.]net<br />
</font><br />
==== BeagleHam ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleHam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleham/<br />
* '''Short project description''': Bringing the BeagleBoard to the world of Amateur Radio.<br />
* '''Homepage''': None at this time.<br />
* '''Expected results''': <br />
** AX.25 Packet support, enabling full APRS support (operating as tracker, fill-in or permanent digipeater, and KISS TNC).<br />
** Encode and decode of HF digital modes, using DSP functionality where possible:<br />
*** BPSK, QPSK 31/63/125/250<br />
*** Olivia<br />
*** WSPR/MEPT<br />
*** MT-63<br />
*** DominoEX<br />
*** RTTY<br />
*** Throb<br />
** CW encode and decode<br />
** Capability to display on small (sub-6-inch) screens for mobile and field use<br />
* '''Contact''': xunil at xunil dot net<br />
</font><br />
==== TCF Agent Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TCF Agent Port<br />
* '''beagleboard.org project''': http://beagleboard.org/project/TCF+agent+port/<br />
* '''Short project description''': Support remote debugging and run control by porting the Eclipse Target Communication Framework (TCF) Agent to beagleboard+Ångström<br />
* '''Homepage''': Not yet<br />
* '''Expected results''': <br />
** A working port of the TCF "Reference implementation of a target agent" to BB/Ångström<br />
** screenshots and information on the TCF: http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Project.html<br />
** TCF agent running on a beagle board would provide the host computer following capabilities (see link above for details):<br />
*** Run control of userspace processes and threads<br />
*** Breakpoints<br />
*** Registers<br />
*** Stack traces<br />
*** Memory access<br />
*** Processes - list, start, stop, attach and debug.<br />
*** Sys monitor - CPU and memory utilization info<br />
*** File System - browsing and copying files<br />
<br />
* '''Contact''': terrella at terrella dot mobi<br />
</font><br />
<br />
==== RT-Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Real-Time patch for the beagleboard<br />
* '''beagleboard.org project''': http://beagleboard.org/project/omap-rt-patch/<br />
* '''Short project description''': Porting the linux rt patch to the omap linux kernel and providing testing applications. This project is developed at the INSA of Rennes (Engineer school in FRANCE) to allow next year Real Time course to be run on the BeagleBoard.<br />
* '''Homepage''': http://sourceforge.net/projects/linux-omap-rt-p/<br />
* '''Expected results''': <br />
** Porting the linux real-time patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) to the linux omap kernel and providing recipes for openembedded allowing to build the patched kernel.<br />
** Providing testing applications allowing to evaluate the real-time behavior of the platform<br />
** Providing applications that could be used for teaching purposes<br />
* '''Current Results''':<br />
** patch-2.6.29.5-rt21 was modified to successfully patch linux-omap-2.6.29 (modified patch available through project page).<br />
** kernel compile and boots with minor error concerning two IRQs (72,73) <br />
* '''Contact''': piat_jonathan[at]users[.]sourceforge[.]net<br />
</font><br />
==== MyGTee ====<br />
<br />
* '''Title''': MyGTee <br />
* '''beagleboard.org project''': http://beagleboard.org/project/MyGTee/<br />
* '''Short project description''': A handheld device exploiting all the OMAP3530 capabilities<br />
* '''Homepage''': http://enco2009.webs.com/<br />
* '''Expected results''': I stage: building a prototype hopefully based on the BeagleBoard; II stage: the actual handheld that may allow for further software opensource development<br />
* '''Contact''': doctorc[at]o2[.]pl<br />
<br />
==== ONAS ====<br />
<font color="#C0C0C0"><br />
* '''Title''': ONAS<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ONAS/<br />
* '''Short project description''': An open source NAS<br />
* '''Homepage''': http://code.google.com/p/onas/<br />
* '''Expected results''': Development of a full featured NAS running Linux <br />
* '''Contact''': electrogeek[at]wp[.]pl<br />
</font><br />
==== Handheld Lab ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Handheld Lab<br />
* '''beagleboard.org project''': http://beagleboard.org/project/handheld_lab/<br />
* '''Short project description''': The goal of this project is to create a little, yet powerful, handheld laboratory with as much functions as possible. It will be easy of use thanks to the integrated LCD touchscreen and nice GUI.<br />
* '''Homepage''': http://www.mipixel.com/handheld-lab<br />
* '''Expected results''': First result will be working LCD showing oscilloscope. After this spectrum analyzer and logic analyzer. All this stuff will need extra electronics.<br />
* '''Contact''': fran[at]mipixel[.]com<br />
</font><br />
====Beagle Tourister using Hand Gestures and HMD on Beagleboard ====<br />
* '''Title''': Travel Buddy using Hand Gestures and HMD on Beagleboard <br />
* '''beagleboard.org project''': http://beagleboard.org/project/travelbuddy/<br />
* '''Short project description''': A device which will assist a traveller/tourist giving them mobile computing power and the following features: <br />
*1) A Compact HMD (Head mountable device) instead of the conventional projector (Problem of Projection Surface while on the move) <br />
*2) Use of standard cam for Image processing i.e recognising simple hand gestures to interact with the GUI seen in the HMD <br />
*3) Scanning of images (street name plates/hotel names/landmarks/book titles as indicated by user) to provide useful feedback data(directions/reviews/record *videos/take pictures/information) <br />
*4) Mode for Speech2text and text2speech conversion for inter-language communication. <br />
* '''Homepage''': Under Construction <br />
* '''Expected results''':<br />
*1) V-NAV: Virtual Navigator - Streaming Google Street View data according to your current location <br />
*2) ULA: Universal Language Assistant: Scan any text by positioning your fingers and the the scanned text is translated to your default language.<br />
*3) Say goodbye to the camera/ cell phone/tourguide/maps. Good platform for further expansion to include newer features. <br />
*4) Virtual Reality Mapping to the Real World: Overlay of relevant information on the on the HMD.<br />
* '''Contact''': sisilmet2000 at gmail dot com , dhairyadand at gmail dot com <br />
<br />
==== Happiness Device for Cerebral Palsy Kids ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Happiness Device for Cerebral Palsy Kids<br />
* '''beagleboard.org project''': http://beagleboard.org/project/HappyCP/<br />
* '''Project description''':<br />
It is an attempt to bridge the gap in communication between those affected by cerebral palsy and those not. The focus of the problem has been on facilitating communication in the emotional domain since this remains a completely unaddressed area. It is possible that some of the ensuing product functions will additionally facilitate communication problems in the physical domain, as well as be physically therapeutic for the cerebral palsy child in the manner of a comfort blanket. The basis of the product is an Emotional Language Protocol (elp) that works as its interface and is driven by four concurrently acting features - color, shape, motion and sound - corresponding to the sensory modes of the visual, the tactile and the aural. The interaction itself is facilitated by touch of varying intensities including pressing, thumping, squeezing, turning and, of course, by touching. Those not affected by cerebral palsy may additionally use speech along with touch. The interplay of this interface and interaction allows the cerebral palsy child to express his different needs and emotions to another person cerebral palsy or otherwise.Also, the device's mobile connectivity allows its users to communicate with someone far away<br />
* '''Homepage''': http://www.dhairyadand.com/Home/jellow<br />
* '''Expected results''': I have uploaded the basic designs at the above link to the homepage. The device is circular in nature with a touch screen where an interactive interface is used to display icons, objects, photos and other sharable action oriented stuff. The device has exchangable memory sticks which allow two or more device's to get connected and hence facilitating interactions. The result is to get a cerebral palsy kid out of his isolated environment, motivate him to communicate by making a device which will show him the joy of communicating.<br />
* '''Contact''': dhairya AT cyber DOT law DOT harvard DOT edu<br />
</font><br />
==== UPnP/DLNA AV client renderer and transcoding server ====<br />
<font color="#C0C0C0"><br />
* '''Title''': UPnP/DLNA AV client renderer and transcoding server <br />
* '''beagleboard.org project''': http://beagleboard.org/project/UPnP_AV_MediaServer/<br />
* '''Project description''':<br />
Enable the beagleboard as a fully featured UPnP AV rendering client, and as a UPnP AV (transcoding!) server. <br />
<br />
Work will be based upon vlc+djmount (for client side) and fuppes (for server side). Server side transcoding to be hardware assisted via hardware DSP codecs. Initial target for the transcoding server on beagleboard is to drive the Neuros OSD (an underpowered DM320-based device). <br />
<br />
* '''Homepage''': Will be an extension and complement to my work on the DM320-based Nueros OSD: http://osd.oddren.com<br />
* '''Expected results''': Beagleboard can act as either as rendering UPnP client, or as a transcoding UPnP server to drive weaker client devices like the Neuros OSD with their preferred streaming format.<br />
* '''Contact''': bmcarnes_beagleboard AT oddren DOT com<br />
</font><br />
==== Beagle-Traveler====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Traveler<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-traveler/<br />
* '''Short project description''': Automotive media and vehicle management controller. Comparable to BeaglesRide.org (no activity).<br />
* '''Homepage''': http://beagletraveler.wordpress.com<br />
* '''Expected results''': intergrate major automotive subsystem management and communications. Improved vehicle notification of subsystems status'. <br />
* '''Contact''': wheeler dawt larry (at) gmail dawt com<br />
**Please send sponsored information and project questions to the email address above.<br />
</font><br />
==== OMAP Emulator====<br />
<font color="#C0C0C0"><br />
* '''Title''': OMAP Emulator<br />
* '''beagleboard.org project''': http://beagleboard.org/project/OMAP+Emulator/<br />
* '''Short project description''': Emulator for rapid prototyping<br />
* '''Homepage''': no homepage yet<br />
* '''Expected results''': Open source implementation of an IDE environment for rapid code development and testing<br />
* '''Contact''': hwtester (at) myway (dot) com<br />
</font><br />
==== eLazarillo====<br />
<font color="#C0C0C0"><br />
[[File:Elazarillo.png|thumb|300px|eLazarillo sketch]]<br />
* '''Title''': eLazarillo (electronic helper for blind persons)<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': Gadget designed for blind persons or with vision problems. <br />
* '''Homepage''': http://elazarillo.blogspot.com/<br />
* '''Full description''':<br />
Lazarillo is a spanish word that means "blind person's guide" and this is the objetive of this project. This gadget will have features like reading non-braille books, assist to blind persons to get places like markets, drugstores, etc. (based on previous GPS tagged places and using google maps). Other functionalities will be spoken weather information, personal calendar, function keys, etc.<br />
<br />
The gadget will be voice controlled, will need GPS, 3G modem, camera and battery. Size will be 4x5 inches (approx.).<br />
<br />
* '''Expected results''': Open source hardware and software platform for blind persons gadgets. My device will have most of the above described.<br />
* '''Contact''': villanuevaborrego (at) gmail (dot) com<br />
</font><br />
<br />
==== QEMUonARM ====<br />
<font color="#C0C0C0"><br />
* '''Title''': QEMUonARM<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': QEMU on ARM. <br />
* '''Homepage''': http://elinux.org/QEMUonARM<br />
* '''Full description''':<br />
This project aims at resurrect and improve QEMU on ARM hosts.<br />
For more information: http://www.qemu.org<br />
* '''Expected results''': Demonstrate user mode and system mode examples, such as running some simple Linux applications or booting an i386 OS. If there's enough interest, making Wine and QEMU work together might be considered.<br />
* '''Contact''': laurent.desnogues (at) gmail (dot) com<br />
</font><br />
<br />
==== Math-NEON ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Math-NEON<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Math-Neon/<br />
* '''Short project description''': NEON optimized cmath like library <br />
* '''Homepage''': http://code.google.com/p/math-neon/<br />
* '''Full description''': <br />
This project aims to overcome the shortcomings of the VFP-lite based cmath implementation. It is targeted at games and other high performance low accuracy applications. The project will consist of C functions, for PC development, which mirror (as near as possible) the hand optimized NEON assembly routines. In order to gain the best performance i will make use of the NEON Unit's Integer and Floating point pipelines in conjunction with minimizing branches (where they cannot be precalculated on the ARM) and creating new algorithms. <br />
* '''Expected results''': Fast approximate implementations of trigonometric, exponential, logarithmic and power functions for use with future Beagleboard / Cortex A8 based projects. <br />
* '''Contact''': lachlan.ts (at) gmail (dot) com<br />
</font><br />
==== Medical Notebook ====<br />
* '''Title''': Medical Notebook<br />
* '''beagleboard.org project''': yet to register<br />
* '''Short project description''': The Ultimate Notebook for Hospitals<br />
* '''Homepage''': coming soon...<br />
* '''Full description''': <br />
A handheld device to improve hospital functionality/efficiency. To add intelligence to the mundane hospital softwares. <br />
Features are:<br />
<br />
View and Update Patient status, medical history, medication details, appointments, billing - stored as a database in central server.<br />
<br />
Touchscreen with handwriting recognition & hand support pad for data entry.<br />
<br />
Light Weight < 1kg<br />
<br />
VoIP, video conferencing/recording for consulting other doctors <br />
<br />
Wifi, bluetooth & ethernet support <br />
<br />
Docking station for charging<br />
<br />
Support for usb keyboard & mouse on docking station<br />
<br />
* '''Expected results''': <br />
<br />
1) Driver for touch pen tablet with support for hand writing recognition<br />
2) Porting of VoIP software for beagleboard (H.323 ???)<br />
3) Video conferencing software for beagleboard<br />
4) WiFi ?& bluetooth support on beagle board<br />
5) Speech recogntion software for beagleboard<br />
6) Entry of beagle board based products to hospital autmation market<br />
7) Improved, efficient & intelligent patient care in hospitals<br />
<br />
* '''Contact''': noorshaheen.m.n (at) gmail (dot) com<br />
<br />
==== EGLIBC ====<br />
<font color="#C0C0C0"><br />
* '''Title''': EGLIBC support<br />
* '''beagleboard.org project''':<br />
* '''Short project description''': Use EGLIBC as system library for beagleboard project in OpenEmbedded.<br />
* '''Homepage''': www.eglibc.org<br />
* '''Expected results''': EGLIBC becomes the default system library on the distribution and can be used instead of glibc<br />
with the newly added configurability support to selec/deselect features. I would also like to make it compile as pure thumb2<br />
code.<br />
* '''Contact''': raj[.]khem[at]gmail[.]com<br />
</font><br />
==== miniECG ====<br />
* '''Title''': miniECG<br />
* '''beagleboard.org project''': http://beagleboard.org/project/miniECG/<br />
* '''Short project description''': Little device that cares for heart when heart patients are busy carrying out their duties<br />
* '''Homepage''': http://code.google.com/p/miniecg/<br />
* '''Full description''': <br />
miniECG is a wearable device that monitors ECG signal, processes it and can transmit it over wireless internet connection to doctors clinic. It has following features are:<br />
(all the hardware components required are available through digikey.com including LCD and touch screen)<br />
<br />
1) It has touch screen that enable user to give commands like store, display old ECG data, transmit, etc. Device also has a LCD display which is used to display ECG waveform.<br />
<br />
2) A tiny server runs on device that enables doctor to login to device any time he wants and extract patients ECG data. The device is connected to internet through wireless USB dongle. <br />
<br />
3) DSP core does the job of compressing ECG signal, doing PCA (principal component analysis) on ECG signal, detect QRS, measuring heart beats and digital filtering.<br />
<br />
4) DSP along with Cortex A8 runs algorithm that determines critical state of heart by doing feature extraction over ECG signals. It also does PCA over set of stored ECG signal to obtain information about any substantial drift in normal functionality of heart. <br />
<br />
5) Wireless USB dongle provides connectivity to internet and data is transmitted over internet as per schedule programmed into the device. ECG signal can also be streamed over internet using this dongle. <br />
<br />
6) Keyboard & mouse (USB) interface is provided for more flexibility and quick access. LCD monitor interface is also be provided. Key-board, mouse and LCD monitor interface will work only when device is powered by adaptor. For device powered by battery only input option is touch screen and only output option is LCD display.<br />
<br />
7) Device also has small software support to give reminder on when to consume which drug. The prescription of drug and its timing information is feed in as per doctors advice. (keyboard and mouse interface with miniECG can be of great advantage here)<br />
<br />
8) USB memory devices will be used to store ECG data.<br />
<br />
9) miniECG will be dual powered. It can be powered by adaptor as well as with rechargeable battery. <br />
<br />
Website link has block diagram of miniECG and also picture of ECG pre-amplifier which is already designed. In future all the source codes will be uploaded on the link as and when available.<br />
<br />
* '''Expected results''': a) Ability to login from remote PC onto miniECG and read data b) Should be able to send stored data or stream live ECG signal over internet c) Robust interface of LCD & touch screen with controller d) Data storage and retrieval from USB storage device e) Successful implementation of DSP algorithms for feature extraction, PCA, QRS detection, filtering and compression. f) As the whole device is battery powered, software & driver which are very specific to the desired application should only be installed & made working. Thus providing a low power system architecture. <br />
<br />
* '''Future Work''': Once the desire basic funtions of ECG storing, retrieval and transmitting is meet, miniECG can be programmed into miniPA (mini personal assistance) mainly targeting senior citizens. miniPA will have much advanced features that can help them elderly person in their day-to-day activity.<br />
* '''Contact''': mehta.nandish (at) gmail (dot) com<br />
<br />
<br />
==== remoteBillBoard ====<br />
* '''Title''': Remote Bill Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/remoteBillBoard/<br />
* '''Short project description''': Video bill boards, remotely controlled via web over a 3G modem<br />
* '''Homepage''': http://www.greensoftware.net/remoteBillBoard<br />
* '''Full description''': <br />
Play HD video on billboards, remotely manage the billboards, upload new advertisements, remove old ones etc..<br />
<br />
<br />
* '''Expected results''': <br />
a) 3g modem support, so flexiblity.<br />
b) a full working web based system<br />
<br />
* '''Future Work''':<br />
a) a more advanced desktop application to replaced the web based solution.<br />
<br />
* '''Contact''': ahmad.mushtaq (at) gmail (dot) com<br />
<br />
<br />
==== Turk ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Turk Platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Turk/<br />
* '''Short project description''': A wireless dynamically-mappable interface platform for small devices<br />
* '''Homepage''': http://www.turkinnovations.com/<br />
* '''Full Description''': Turk will be an open-source wireless interface platform that allows interfacing of small wireless (Zigbee or Wi-Fi enabled) devices through a dynamic mapping framework and web interface. Developers can implement their device's protocol easily through small user-space drivers called 'Gadgets' and host them on our server. The platform is then capable of automatically downloading and starting appropriate gadgets for new devices that are compatible with the basic Turk protocol. Gadgets reveal their services to the user and other gadgets through our growing library of data endpoint types (such as colors, URLs, booleans, xml strings) and user controls (like sliders, switches and color pickers), and can then be connected to each other through a themable web interface.<br />
<br />
* '''Expected results''': <br />
**A platform that allows developers to write simple user-space drivers that expose interfaces through XML-RPC<br />
**A web interface and remote configuration capabilities through a central server. <br />
**A simple and well-tested protocol and driver for a kernel-managed point-to-multipoint Zigbee network. <br />
**More hardware connectivity besides the Wi-Fi and Zigbee interfaces will hopefully be developed by collaborating with other beagleboard projects and developers.<br />
* '''Contact''': rob.odwyer [at] turkinnovations [dot] com<br />
</font><br />
==== BeagleWacom ====<br />
* '''Title''': Wacom Tablet driver for Beagle Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-wacom/<br />
* '''Short project description''': Linux drivers of wacom tablet ported for Beagle Board<br />
* '''Homepage''': <br />
* '''Full Description''': beagle-wacom will be port of linux drivers for configuring & running wacom tablets with the beagle board. The idea is to have support for wacom-components, so that they can be used by OEMs of beagleboard based products using linux as their OS<br />
<br />
* '''Expected results''': <br />
**easy integration of wacom tablet with Beagle Board. <br />
**OEMs of beagleboard based products using linux as their OS can integrate wacom-components in their product with minimal fuss<br />
* '''Contact''': najath [at] gmail [dot] com<br />
<br />
<br />
====hApplause====<br />
<font color="#C0C0C0"><br />
* '''Title''': hApplause<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Hardware Platform that You can use to play with Audio Synthesis<br />
* '''Homepage''': not yet<br />
* '''Description''': ''hApplause'' will be multi-functional flexible audio hardware platform. The goal is to make a tool that can allow to develop audio software and hardware (e.g. DSP synthesizers, FX units, hardware expansion boards, etc.). The concept is inspired by [http://www.chameleon.synth.net/ Chameleon] and [http://www.ucapps.de/ MIDIbox]. ''BeagleBoard'' will give ''Chameleon'' like software flexibility while planed hardware with ''Expansion Interface'' and ''Audio Multiplexer'' will give ''MIDIbox'' like hardware flexibility.<br />
*; Hardware features<br />
*: Audio Stereo In/Out<br />
*: MIDI In/Out/Thru<br />
*: General purpose USB port - function depends on user application<br />
*: General purpose SD/MMC Card (e.g. for user data storage) - function depends on user application<br />
*: Front panel interface (1U rack version) with:<br />
*:* LCD<br />
*:* Volume potentiometer<br />
*:* Headphones jack<br />
*:* Power switch with LED indicator<br />
*:* programmable rotary encoders (5 are planed)<br />
*:* programmable buttons and LEDs (12 are planed)<br />
*: Expansion Interface with audio signal buses (1-4 planed, depends on final implementation) and data/command bus (I2C and/or CAN)<br />
*: Audio Multiplexer for flexible routing of audio signal between ''BeagleBoard'', ''Audio In/Out'' and ''Expansion Interface''<br />
*: USB and RS232C for developers<br />
*; Software features<br />
*: All hardware will be fully accessible from ''BeagleBoard'' by API<br />
*: hApplause OS is planed (abstract layer over hardware, user program loading, self configuration on power on)<br />
* '''Expected results''':<br />
*# 19" 1U rackmount unit ready to play with.<br />
*# Libs and additional software for developers (at least API for hApplause's hardware)<br />
*# Example implementation of software synth<br />
*# Single size eurocard unit for 3U rack, like in [http://www.doepfer.de/a100e.htm Doepfer A-100 System] modules<br />
* '''Contact''': tawezik at gmail dot com<br />
</font><br />
==== BeagleLAB====<br />
* '''Title''': BeagleLAB<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleLAB/<br />
* '''Short project description''': BeagleLAB is an Embedded developer's workbench comprising of must-have hardware/software utilities.<br />
* '''Homepage''': http://code.google.com/p/beaglelab/<br />
* '''Expected results''': <br />
:* A PC free host providing a development environment based on beagle board (running ubuntu 9.04 or later)<br />
:* Host environment with software applications and hardware interfaces to substitute oscilloscope, multimeter & logic analyzers<br />
:* GNOME widgets (software apps) & Linux device drivers for capturing data,storing,comparing and visualization<br />
:* Legacy ports like the serial, parallel ports for device interfacing and control<br />
:* Making an embedded developer's life easier and workbench neater<br />
* '''Contact''': amarendermail[at]gmail[dot]com and saurabhg84[at]gmail[dot]com<br />
<br />
====PREEMPT_RT====<br />
<font color="#C0C0C0"><br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
</font><br />
<br />
====HDDM====<br />
<font color="#C0C0C0"><br />
* '''Title''': HDDM<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/HDDM/]<br />
* '''Short project description''': A multimedia system based on OMAP and linux.<br />
* '''Homepage''': Under construction<br />
* '''Expected results''': Beagleboard as a control center for home theatre system<br />
* '''Contact''': grover.ankur (at) gmail (dot) com<br />
<br />
Note from Dirk: Please see [http://www.syspire.de/node/3 Embedded Mediacenter], too (sorry, German only, use Google translate if needed).<br />
</font><br />
====BeagleVision====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleVision<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beaglevision/<br />
* '''Short project description''': An efficient object recognition framework <br />
* '''Homepage''': http://code.google.com/p/beaglevision/<br />
* '''Description''': BeagleVision will be a fast object recognition framework. The aim of the project is to have a hardware optimized implementation (utilising the DSP and NEON) of state-of-the-art local feature detectors and descriptors on the Beagle Board. BeagleVision will include [http://www.cs.bris.ac.uk/Publications/pub_master.jsp?id=2001018 our recent work] on efficient feature detectors and descriptors, other well-known algorithms (e.g. FAST corner detector and SURF), and efficient matching algorithms for very large datasets (>1M images).<br />
* '''Expected results''':<br />
:* An open source library for developers (a project hosted on code.google.com)<br />
:* A sample application for building recognition in a city scale dataset, to show how: to add new images to the dataset, to use it for location based services, and how to reduce the search time if a GPS is available to get geolocations<br />
:* A wiki for interested developers<br />
:* Reporting the running times of new algorithms on OMAP (as a benchmark) in scientific publications<br />
* '''Contact''': m.ebrahimi at ieee dot org<br />
</font><br />
====Beagle-Arduino hybrid robot====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Arduino hybrid robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Beagle-Arduino+hybrid+robot/<br />
* '''Short project description''': A robot using a Beagleboard for high-level processing and Arduino for low-level control<br />
* '''Homepage''': http://mechomaniac.com/robots<br />
* '''Description''': The Beagle-Arduino robot will use a Beagleboard for high-level robot functions:<br />
** image processing<br />
** artificial intelligence<br />
** speech synthesis<br />
** voice recognition<br />
** internet connectivity<br />
And an Arduino for low-level functions:<br />
** motor / servo control<br />
** sensor input & output<br />
** battery monitoring<br />
The two microcontrollers will be connected by USB, along with a USB webcam mounted on a servo pan/tilt mechanism, and a USB wifi dongle for internet connectivity. Basic tank treads will provide movement, possible being replaced by servo-based legs for a humanoid or dog form.<br />
* '''Expected results''':<br />
:* Easy physical interfacing to the Beagle without having to design and build special expansion boards<br />
:* Image processing using OpenCV with a USB webcam<br />
:* Speech synthesis and voice recognition<br />
* '''Contact''': tim at mechomaniac dot com<br />
</font><br />
<br />
====DJ Audio / Video Mixer====<br />
<font color="#C0C0C0"><br />
* '''Title''': DJ Audio / Video Mixer* '''Contact''': <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/djvideomixer/]<br />
* '''Description''': This is a small, Touch LCD controlled DJ Mixer, which not only is great as a nightclub tool for playing audio -not only reproducing music, actually '''''playing''''' with it-, but also has high end video playback capabilities, thus making it an all-round experience both for the DJ and the audience. It will bring all the experience of professional DJ mixers to users, while being portable, and which when coupled with either a normal projector, or even better, with a PicoProjector, makes a whole experience for audio and video playback in Discos, Bars, Lounges, to mention just a few possible applications. You can even use for your own parties, and it will rock!<br />
* '''Homepage''': [http://code.google.com/p/djvideomixer/]<br />
* '''Expected results''': <br />
** Audio playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Video playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Audio/Video synchronization, allowing song change, video change, etc.<br />
** High end, professional DJ-Mixer audio effects.<br />
** User interface based on LCD and with touchscreen capabilities.<br />
* '''Contact''': jaime_dot_aranguren_at_ieee_dot_org<br />
</font><br />
====schooldog====<br />
<font color="#C0C0C0"><br />
* '''Title''': schooldog<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/schooldog/]<br />
* '''Description''': The purpose is to make an ''off the shelf'' low cost schoolcomputer that can be used on various levels of education. It will be small so students can take it with them and the school just has to provide for input / output items. This way even people that cannot afford laptops can participate in the digital era or schools can provide a robust and good machine for studypurposes.<br />
* '''Homepage''': [http://schooldog.wickedmind.net]<br />
* '''Expected results''': <br />
** Educational linuxbased OS, from USB sticks and SD Cards.<br />
** more general use of BeagleBoard and more public awareness for the powerful small computer.<br />
** Affordable,individual and steady study enviroment<br />
<br />
* '''Contact''': wickedmind<br />
</font><br />
====Disko====<br />
<font color="#C0C0C0"><br />
[[File:Disko_logo.png|thumb|200px|UI Application Framework]]<br />
* '''Title''': Disko - UI Application Framework<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Disko/<br />
* '''Short project description''': Disko is a Linux-based toolkit to build touchscreen- and remote-controllable ui applications. It contains native OMAP framebuffer support and the media content is DSP-accelerated by GStreamer (TI-Codecs).<br />
* '''Homepage''': http://diskohq.org<br />
<br />
* '''Expected results''': Expected result is broad support of Disko by developers of user interfaces and applications for embedded devices.<br />
** SIP - IP telephony support delivered by pjsip and minisip <br />
** Gstreamer - to add an alternative to the xine library and to add the TI Codecs supplied for the DSP.<br />
** Webkit - the great embedded browser OWB of Pleyo (planned for Disko 1.7)<br />
** SVG - at least one SVG engine to have an alternative to Flash. Initial work has already been done at MadButterfly (planned for Disko 1.7) <br />
* '''Contact''': gmadaus [at] berlinux-solutions dot de or mspringer [at] berlinux-solutions dot de<br />
</font><br />
====FETCH====<br />
* '''Title''': FETCH - FPGA enabled Tool Contol Host<br />
* '''beagleboard.org project''': http://beagleboard.org/project/FETCH<br />
* '''Homepage''': http://code.google.com/p/fetch/<br />
* '''Short project description''': A host with a web interface for easy configuration and control of connected tools. The device may also be controlled through a PSTN network using DTMF tones. The BeagleBoard will act as the main server and will also be the host interface for the connected FPGA for the purpose of evaluating the IPs developed on the FPGA.<br />
* '''description : Phase 1 '''<br />
***1) Server capability -- all services (except VNC) to be launched through inetd so that they are started on an on-demand basis. <br />
***-- http server for configuration pages <br />
***-- ssh server (the ssh suite in particular including scp etc.. so that an ftp server can be avoided) for remote login. <br />
***-- bootp server for bootstaping machines on my home network. <br />
***-- VNC for GUI sessions :) <br />
***-- CUPS for network printing <br />
***-- NetHack server :D <br />
***2) Tool Control <br />
***-- The term "Tool Control" here refers to automation of connected tools and Phase 1 of the project will demonstrate this by automation in home (eg. computer, printer, scanner on/off --> (the contoller board with the relays is complete :) ), these devices may be contolled over the internet or PSTN network ) The system will also be hooked to the home electrical network that will enable control over home appliances. A special mode called " Home Alone" will switch on/off lights randomly when no one is at home to give the illusion that the house is occupied ( and hence protect from thefts ;) ). The current relay boards developed use a UART (for RS232 protocol) for control of the equipment but it is planned to use the CAN interface (under developement ) so that longer distances can be covered. <br />
***3) The BeagleBoard will act as a host interfacefor a Nexys2 Xilinx FPGA board and will be used to evaluate the IPs deployed on it. This feature is sort of a tester for the FPGA. <br />
**'''Phase 2 ''' ( only after Phase 1 is completely functional :) ) <br />
***1) CAN interface for the controller nodes replacing the RS232 connections<br />
***2) mgetty (for faxes) and asterisk (VOIP) may be added to the server.<br />
* ''' Contact : ''' akshat dot g dot gupta [at] gmail dot com<br />
<br />
==== ESITeam====<br />
<font color="#C0C0C0"><br />
* '''Title''': ESITeam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ESITeam/<br />
* '''Short project description''': It's a robotic soccer team with vision and intelligence distributed through the use of wireless communication (Zigbee) between robots and PC.<br />
* '''Expected results''': The expected results would have a running and competitive team for the RoboCup's championship this year.<br />
<br />
* '''Contact''': registrosvmora at gmail dot com<br />
</font><br />
==== PupLC====<br />
* '''Title''': PupLC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/PupLC/<br />
* '''Short project description''':Open source control of PLC operated equipment.<br />
* '''Homepage''': No homepage yet<br />
* '''Expected results''': <br />
:*PupLC will be an open source PLC controller. The user will be able to control the PLC's autonomously or by direct control. The direct method will allow the user to change equipment status using a touch screen lcd. The PupLC will control all aspects of the operating equipmet (ie. setpoints, red-hand settings, shutdowns, etc.) Additionally, 24-hours of accumulated system data will be saved to disk and can be accessed via ftp for analysis off-site.<br />
* '''Contact''': alcpo729[at]tds[dot]net<br />
<br />
====Speed-Reader====<br />
<font color="#C0C0C0"><br />
* '''Title''': Speed-Reader<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Speed-Reader/<br />
* '''Short project description''': Speed-Reader is an audio book reader that gives the listener control of the speaker rate.<br />
* '''Homepage''': http://www.nerd1951.com/?page_id=72<br />
* '''Description''': Speed reader allows an audio book to be played back with faster or slower speaker rates. A user interface gives the listener realtime control of the speaker rate. Speed-Reader uses digital speech signal processing to accomplish low distortion timescale modification of speech in real time. Timescale modification of speech is accomplished by selectively repeating segments of speech to slow down the speaker rate or deleting selected speech segments to speed up the speaker rate. Digital signal processing is used to determine which speech segments are candidates for repetition or deletion.<br />
* '''Expected results''':<br />
***--Realtime (during playback) timescale modification of digitized speech using the C64++ DSP<br />
***--Initially read digitized speech from the SD card interface<br />
***--Audio output using the Beagleboard stereo out<br />
***--Initially user interface provided via RS-232 interface<br />
* '''Contact''': harvey dot sugar at nerd1951 dot com<br />
</font><br />
<br />
====DVB-T Receiver====<br />
<font color="#C0C0C0"><br />
* '''Title''': DVB-T Receiver<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': The DVB-T Receiver project aims to implement a fully tunable DVB-T Receiver on the Beagle Board.<br />
* '''Homepage''': Will be launched in the near future (at blog.arsln.org)<br />
* '''Description''': The DVB-T receiver is a senior graduation project that has to be completed in one year (until Summer 2010). It will be a fully tunable DVB-T receiver. It will compatible to receive digital terrestrial TV & radio stations. The goal is to show the capabilities of the Beagle Board and build a DVB-T system from the scratch. The input will be through a ADC daughter-board that is plugged to the USB port. The output will be via the USB port(for portable devices i.e Netbook) or DVI-D. <br />
* '''Expected results''':<br />
***--Capturing broadcast signals(DVB-T) and convert them to discrete time signals<br />
***--Demodulate and encode the incoming signal<br />
***--Video output using the Beagleboard's DVI-D port or via the USB port for portable devices<br />
* '''Contact''': ftharsln at gmail dot com , sulaya05 at gmail dot com<br />
</font><br />
<br />
====ArchMobile: ArchLinux ARM Port====<br />
<br />
* '''Title''': ArchMobile<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/AM/ AM]<br />
* '''Short project description''': ARM Port of the x86-Linux Distribution ArchLinux<br />
* '''Homepage''': [http://www.archmobile.org ArchMobile]<br />
* '''Expected results''': Fully working ArchLinux with X and all other features.<br />
* '''Contact''': rotter.manuel@gmail.com or naeg on Freenode<br />
<br />
==== MythBeagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': MythBeagle<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': MythBeagle aims at bringing MythTV to the beagle; both frontend and backend, including plugins (as far as possible)<br />
* '''Homepage''': not yet; <br />
* '''Expected results''': <br />
** OE recipes for mythtv 0.22, mythplugins 0.22 and whatever might be needed to get things going (including bringing required recipes to the latest version where needed/possible)<br />
** An image for SD card to allow easy install, or a script or recipe to allow easy installation<br />
** some additional configuration notes (configuring MythTV is somewhat a pain...)<br />
** setup should also allow using the beagle only as frontend or backend<br />
* '''Status''': mysql5 recipe has been created (mythtv 0.22 won't use mysql4); recipes for mythtv are there, except for mythweb, documentation/installation work has started;<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
</font><br />
<br />
==== Homebrew SmartPhone ====<br />
<br />
* '''Title''': HomeBrewSmartPhone<br />
* '''beagleboard.org project''': http://code.google.com/p/hbpd<br />
* '''Short project description''': HomeBrewSmartPhone is a project to use the beagleboard to create a community-buildable mobile phone that is powerful enough to also run as a Desktop PC.<br />
* '''Homepage''': http://lkcl.net/reports/hbp <br />
* '''Expected results''': <br />
*** A device capable of Digital Voice as well as Data / Internet Access.<br />
*** A device capable of shutting down into low-power mode and successfully resuming on incoming calls.<br />
*** RF-protected audio circuits that don't have howling feedback from the 3G/GSM Radio module.<br />
*** Full disclosure of all build components (schematics, BOM) under free software licenses.<br />
*** Full documentation of all hardware interconnections<br />
*** Creation of a <b>basic</b> demonstration image that will allow other software developers to participate very early on<br />
*** Addition to the http://handhelds.org site for developers to create GUI-based distros<br />
* '''Contact''': lkcl@lkcl.net or use http://lkcl.net contact box<br />
<br />
==== XBMC ARM Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': XBMC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/XBMC/<br />
* '''Short project description''': XBMC Is a full-feature home-theater application that works on a variety of platforms and operating systems<br />
* '''Homepage''': http://xbmc.org<br />
* '''Expected results''': <br />
*** Feature parity with XBMC x86 and ppc<br />
*** Usage of OpenGL ES 2.0<br />
* '''Contact''': Cory Fields: theuni @at@ xbmc .dot. org<br />
</font><br />
<br />
==== Beagleboard Carputer ====<br />
<br />
* '''Title''': Beagleboard Carputer<br />
* '''beagleboard.org project''': http://beagleboard.org/project/bbcarputer<br />
* '''Short project description''': The Beagleboard Carputer aims to create a fully-integrated system that will feature touchscreen LCD, Bluetooth and USB connectivity, GPS Navigation, Phone features, Wifi, Voice recognition, Multimedia entertainment.<br />
* '''Homepage''': http://bbcarputer.codeplex.com<br />
* '''Expected results''': Provide a fully-integrated system that will feature:<br />
*** 7in touchscreen LCD<br />
*** Wireless connectivity<br />
*** Usb connectivity<br />
*** GPS Navigation<br />
*** Phone features<br />
*** Voice recognition<br />
*** Multimedia entertainment<br />
*** Opensource Application Suite<br />
*** Games<br />
* '''Contact''': Joey Mar Antonio: joeymar.antonio @at@ awsol-i .dot. com<br />
<br />
==== GuideBeagle: Portable monocular SLAM system ====<br />
<font color="#C0C0C0"><br />
* '''Title''': GuideBeagle<br />
* '''beagleboard.org project''': Not yet available.<br />
* '''Short project description''': GuideBeagle is a portable localization and mapping system based on monocular vision. Such a system can be used, among other things, to build:<br />
:*Interactive visitor guidance systems for museums and stores.<br />
:*Artificial Reality tools and games.<br />
:*Mobile robot control systems.<br />
:*Surveillance and security related applications.<br />
:In other words: it solves a Simultaneous Localization and Mapping (SLAM) problem using a single camera as sensor, working on-line, and producing maps with high-level geometrical information (i.e. not just simple punctual visual landmarks on space). It will be based on recent research on the fields of Computer Vision and Mobile Robotics.<br />
* '''Homepage''': http://sites.google.com/site/guidebeagle (This page will be enhanced uninterruptedly.)<br />
* '''Expected results''': <br />
**Mapping --- The final system will allow an user to move by an environment like an office or a small apartment and build a map of it similar to a 3D model with planes and textures, as used in Computer Graphics.<br />
**Localization --- After a map is built, the user can move around the environment, and the system will interactively estimate the geometric location of the camera and the direction it is heading, based on images continuously obtained from the camera.<br />
**Image processing --- Building this system will require the coding of image processing tools that may be useful to many other image processing applications based on the Beagle Board. Some examples are feature detectors and descriptors, edge detectors, template matching by normalized cross-correlation and the Discrete Fourier Transform.<br />
* '''Contact''': nwerneck@gmail.com or nwerneck@usp.br<br />
</font><br />
<br />
==== AutoRobo ====<br />
<br />
* '''Title''': Development of an autonomous robotics platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/autorobo/<br />
* '''Short project description''': Design, prototype and develop an autonomous aerial vehicle system around BeagleBoard, allowing experimentation with real-time control and computer vision algorithms.<br />
* '''Philosophy''':<br />
:* make robotics and embedded control accessible and fun<br />
:* stimulate cross-field learning and collaboration<br />
:* leverage modularity and reuse to get more done, quicker <br />
* '''Technical goals''':<br />
:* develop generalised physics model for eg computing optimal PID controlled motor outputs<br />
:* decouple high-update-rate sensors from lower-rate output control<br />
:* employ OpenCV for visual tracking/SLAM/feature detection<br />
:* build lean tracked (land) vehicle<br />
:* build lean quad-rotor (air) vehicle<br />
:* use a shared, modular code-base and electronics platform (Beagle and IGEPv2) <br />
* '''Homepage''': http://code.google.com/p/autorobo/<br />
* '''Expected results''': Initial bringup of a tracked vehicle via dual-motor controller via Beagle's PWM outputs. Utilisation of 3-axis accelerometer and 3-axis gryo via I2C and/or SPI buses, enabling more advanced control<br />
* '''Contact''': ''daniel (dot) blueman (at) gmail (dot) com''<br />
<br />
==== Beagle-Walker ====<br />
<br />
* '''Title''': Design of a automatic dog-walker robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleWalker/<br />
* '''Short project description''': Develop an autonomous dog-walker robot<br />
* '''Homepage''': http://code.google.com/p/beaglewalker/<br />
* '''Expected results''': <br />
**The main goal of the system is analyze the feedback between the dog and the robot to track where the dog is going and where the robot should go.<br />
**Let the dog walk only in places previously programmed by the dog's owner making use of basic SLAM algorithms. <br />
**avoid any obstacles/vehicles.<br />
* '''Contact''': ''darthdj at gmail dot com''<br />
<br />
==== nullDC / Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nullDC<br />
* '''Expected results''': For the contest: A working build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
</font><br />
<br />
==== MyoVox ====<br />
* '''Title''': MyoVox<br />
* '''beagleboard.org project''': <br />
* '''Short project description''': <br />
* '''Homepage''': <br />
* '''Expected results''': <br />
* '''Contact''': smcgill3 [at] seas[.]upenn [.] edu<br />
<br />
==== Beagle-Eye ====<br />
<br />
* '''Title''': Beagle-Eye<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle-Eye/ Beagle-Eye]<br />
* '''Short project description''': A beagle-eyed guide for the visually challenged.<br />
<br />
* ''' Hardware''':<br />
** A pair of calibrated USB cameras, mounted on the user's shoulders, such that the combined field of view covers at least 180 degrees.<br />
** One or more linear actuators connected through RS-232, situated on one of the user's limbs.<br />
** Stereo headphones.<br />
** USB GPS Dongle.<br />
<br />
* '''Description''':<br />
** Low frame rate real-time video is used to guide the user towards a specified destination.<br />
** The GPS provides coarse location.<br />
** The stereo camera setup provides a wide field of view, along with coarse depth information.<br />
** Map information, combined with real time video is used to esimate location and orientation more accurately.<br />
** Simple object recognition techniques are employed to recognize parts of the environment.<br />
** The audio setup and the actuator(s) are used either in tandem or interchangeably to guide the user. This can be customized as required. Some possibilities include:<br />
*** A short periodic 3D sound generated to indicate the direction in which the user is to walk.<br />
*** The user is alerted about approaching obstacles by firing the actuator at a frequency inversely proportional to the distance to the obstacle. This distance can be computed using depth information computed from pairs of images.<br />
*** Information about the environment, such as "Pedestrian Crossing in 20m" can be relayed through audio.<br />
<br />
* '''Possible Enhancements''':<br />
** More comprehensive localization techniques, such as SLAM, can be used to improve the accuracy of the system. This will also open doors to indoor navigation, where the GPS fails.<br />
** Detection, segmentation and recognition of text (such as signboards and street names) in the environment will ensure less errors in navigation.<br />
<br />
* '''Expected Results''':<br />
** A navigation tool for the visually challenged, using audio and linear actuators to communicate with the user.<br />
<br />
* '''Contact''': leatherbrain at gmail dot com<br />
<br />
==== BeaglePod ====<br />
<br />
* '''Title''': BeaglePod<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglepod/]<br />
* '''Short project description''': BeaglePod is an IPod plug-in replacement for car stereo's that are IPod Ready. The BeaglePod uses gstreamer as an audio/video player and is controlled via the car stereo head unit using Apple Accessory Protocol. <br />
* '''Description''': The BeaglePod is an audio/video player for cars equipped with "IPod Ready" stereos. Using the Apple Accessory Protocol the car stereo is used to select and control the playback of media on the BeaglePod. Adding a video monitor the BeaglePod can also become a video player running all the audio through the car stereo with full pause, play, stop control using the car's stereo head unit. Using a software implementation of the Apple Accessory Protocol the BeaglePod is connected to the car stereo via a USB->TTL cable.<br />
* '''Expected Results''':<br />
** Play audio/video media files from the Beagleboard using the car stero to control playback and track selection.<br />
** Audio will playback through car's exist speaker.<br />
** With gstreamer dsp support HD playback of video with in car lcd.<br />
* '''Contact''': velorider [X] publicemail [X] us<br />
<br />
==== MART ====<br />
* '''Title''': Autonomous modular robot<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': Build an autonomous robot to enter the Eurobot 2010 competition<br />
* '''Homepage''': (only in Czech) http://eurobot.matfyz.info/<br />
* '''Full Description''': Goal of this project is to build an autonomous modular robot, that will be able to compete in the Eurobot competition. This project includes following:<br />
<br />
** '''HW''':<br />
** Custom beagle daughter-card (including kernel driver patches):<br />
*** CAN (Controller area network) able to sustain 1Mbit/s, using embedded cortex-m3 controller<br />
*** Battery backed up RTC<br />
*** Dual power - battery and/or adapter, with battery management (current consumption sensing and charging) <br />
*** Second serial and i2c headers<br />
*** (optional) Ethernet controller 10/100Mbit<br />
** Custom motor, servo and stepper motor drivers and IO boards<br />
*** everything connected through CAN<br />
<br />
** '''SW''':<br />
** Modular architecture, for simple modification<br />
** OpenCV integration for play field object identification<br />
** optimalizations for NEON (and DSP)<br />
<br />
* '''Contact''': Michal dot Demin at Gmail dot Com<br />
<br />
==== CamCast ====<br />
* '''Title''': Webcam broadcast server/relay<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/CamCast/]<br />
* '''Short project description''': Webcam broadcast platform for USB webcams<br />
* '''Homepage''': <br />
* '''Full Description''': The goal of this project is to utilize the beagleboard as a low cost platform for webcam video feeds.<br />
Server capability:<br />
<br />
** Broadcast webcam feeds for directly connected USB webcams<br />
** Relay webcam feeds from other servers, typically connected over wi-fi<br />
** Decimate MJPEG streams to match bandwidth limits<br />
** Monitor and control streams via HTTP<br />
** Advertise HTTP services locally via Zeroconf<br />
<br />
The beagleboard will require a functional Linux gspca driver for all USB webcams in use as well as USB wi-fi for remote service. Linux Zeroconf service must also be included.<br />
<br />
* '''Contact''': spiderkarma at gmail dot com<br />
<br />
====Beagle SecMon====<br />
<br />
* '''Title''' : Beagle Security Monitoring over Web <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle+SecMon/ BeagleSecMon]<br />
* '''Short project description''': This project proposes to control and transmit audio and video from a remote place using the beagleboard as a webserver.<br />
* '''Expected results''': The system will control one or more digital cameras with pan, tilt and zoom functions, and microphones. Besides, it can be configured to send information to a pre registered cell phone when movement is detected. Also, audio and video can be accessed using internet from any place.<br />
* '''Contact''': cborges at ifsc dot edu dot br====<br />
<br />
====PortablePlateRec====<br />
<br />
* '''Title''' : Beagle Portable Plate Recognition <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/PortablePlateRec/ PortablePlateRec] <br />
* '''Short project description''': A portable system for automatic number plate recognition (ANPR) using BeagleBoard.<br />
* '''Expected results''': The goal of this project is to develop a portable system for automatic number plate recognition (ANPR) using BeagleBoard. It includes the following:<br />
** receiving images from a camera;<br />
** applying signal processing algorithms for plate localization, orientation and sizing, image normalization, and character segmentation;<br />
** optical character recognition (for instance, Tesseract);<br />
** possible access to a database to check the plate against law infringements.<br />
<br />
* '''Contact''': fpacheco at ml1 dot net<br />
<br />
====Digital Multimedia Frame====<br />
<br />
* '''Title''' : Digital Multimedia Frame<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a photo, video and music application who use a touchscreen display<br />
* '''Expected results''': The goal of this project is to get photo, video, music from memory card or from a network. <br />
<br />
** Scan network to multimedia file. <br />
** Create automatically a slideshow when we are in photo mode.<br />
** Create automatically a music list.<br />
** Play video<br />
** Add basic operation available for picture (rotate, resize...)<br />
** touch screen will be used to simplify action.<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
====Beagle Utility====<br />
<br />
* '''Title''' : Beagle Utility<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a box with lcd screen to be able to encrypt, format, wipe, clone, find virus, search rootkit .... a hd or memory card. A menu with different operation is displayed to user.<br />
* '''Expected results''': The goal of this project is to be able to do some operation on harddriver, memory card <br />
<br />
** Encrypt <br />
** Format<br />
** Wipe<br />
** Clone<br />
** find virus<br />
** Rootkit<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
===Contest #2 projects===<br />
<br />
Please don't add new projects, contest #2 is closed.<br />
==== James ====<br />
1st [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/James James]<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. <br />
* '''Expected results''': Updated recipes for all relevant packages on OpenEmbedded. A script to install the needed packages to an Angstrom image (generated by Koen's generator) and documentation on how to configure things.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
</font><br />
====BeagleEPD====<br />
2nd [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': E-Ink Interface Board and Driver for beagleboard<br />
* '''Homepage''': [http://elinux.org/BeagleEPD BeagleEPD]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleepd/<br />
* '''Short project description''': This project aims to interface an E-Ink display directly with a beagleboard. This is done by creating an interface board that is connected to the Beagleboard expansion header and converts the relevant gpio signals into the levels appropriate for interfacing with the E-Ink display controller. The second part is to write a driver which is a port of am300epd.c from mach-pxa to mach-omap in order to support the E-Ink broadsheet framebuffer driver directly on beagleboard. All of this results in making it possible to connect any E-Ink display controller to a Beagleboard (via the expansion header) and to then treat any E-Ink display as another framebuffer.<br />
* '''Expected results''': Schematic for interface PCB between Beagleboard and E-Ink display controller board. A beagleepd.c mach-omap driver that will setup and control the IO pins appropriately.<br />
* '''Contact''': jayakumar at IRC (freenode, oftc) or jayakumar.lkml@gmail.com<br />
</font><br />
==== nullDC / Beagle ====<br />
<br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with newly added support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nulldc_beagle<br />
* '''Expected results''': For the contest: A WIP (but working) build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
===Contest #1 projects===<br />
<br />
====qemu-omap3====<br />
<br />
* '''Title''': support beagle board emulation in qemu<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]<br />
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.<br />
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]<br />
* '''Expected results''':<br />
** booting linux kernel and rootfs from nand and mmc image<br />
** Wiki page how to run qemu-omap3 for beagle board<br />
* '''Submission''':<br />
** http://code.google.com/p/qemu-omap3/wiki/UserManual<br />
* '''Contact''': yajin AT vm-kernel.org<br />
<br />
====openGPS====<br />
<br />
* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites. <br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** development of a display app with moving map capabilities<br />
** development of a user interface for handheld apps<br />
** integration with suitable LCD display<br />
** interface to map files on SD card<br />
** Wiki page on GPS receiver functions and features<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====Beagle Conference System====<br />
<br />
* '''Title''': Use beagle to come up with a conferencing system for home users<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]<br />
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.<br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.<br />
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).<br />
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.<br />
** The software shall also provide for ways to chat (text) with the users.<br />
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====BeagleRC====<br />
<br />
* '''Title''': Use a beagle board to drive a remote controlled car.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos. <br />
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml<br />
* '''Expected results''':<br />
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.<br />
* '''Contact''': code at chrisd dot info<br />
<br />
====PREEMPT_RT====<br />
<br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
<br />
====USB Support in U-boot ====<br />
2nd [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.<br />
* Homepage: [[U-boot musb gadget support]]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/<br />
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).<br />
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.<br />
* '''Contact''': ddompe at IRC<br />
</font><br />
<br />
==== James ====<br />
<br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': To be Added...<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html<br />
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
<br />
====BeagleBot====<br />
1st [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Board powered robot<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]<br />
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...<br />
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]<br />
* '''Expected results''':<br />
** Partly autonomous robot<br />
** PC controlling of the robot<br />
* '''Contact''': antti at hervanta.com<br />
</font><br />
<br />
====Android Cupcake for BeagleBoard====<br />
<br />
* '''Title''': Android Cupcake for BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]<br />
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard. <br />
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]<br />
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====FreeBSD port to BeagleBoard====<br />
<br />
* '''Title''' : A port of FreeBSD-arm to the BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]<br />
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.<br />
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.<br />
* '''Contact''': AsqYzeron====FreeBSD port to BeagleBoard====<br />
<br />
==Judging==<br />
<br />
===Judges===<br />
* Jason Kridner (jkridner)<br />
* Koen Kooi (koen)<br />
* Dirk Behme (dirk2)<br />
* Steve Sakoman (sakoman)<br />
* Hunyue Yau (ds2)<br />
* Mans Rullgard (mru)<br />
* Gregoire Gentil (gregoiregentil)<br />
<br />
===Past Judges===<br />
* Robert Kuhn (robertk)<br />
<br />
===Rules===<br />
* Judges cannot participate in the contest.<br />
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.<br />
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.<br />
* All voting will be public and logged on this page.<br />
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.<br />
* To follow up on shipping details, contact ''beagleship at list.ti.com''.<br />
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.<br />
<br />
===Criteria===<br />
* All new content must be open source as determined by the OSI.<br />
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.<br />
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]<br />
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.<br />
* "Wow" or "coolness" factor from usefulness/user experience point of view<br />
* Overall quality of the submission<br />
* Technical complexity<br />
** "Coolness" of the technical solution, even if it isn't useful for all the masses<br />
** Amount of work needed, i.e. x hours or x days?<br />
* Angstrom recipe for image<br />
* Documentation for the demo<br />
* Running power consumption<br />
* Use of DSP and SGX<br />
* Ease of use<br />
<br />
===Contest #1===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-01-11<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]<br />
|3<br />
|<br />
|3<br />
|2<br />
|<br />
|3<br />
|2<br />
!13<br />
|-<br />
|[[BeagleBoard/contest#openGPS|openGPS]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]<br />
|1<br />
|<br />
|<br />
|1<br />
|3<br />
|<br />
|2<br />
!7<br />
|-<br />
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]<br />
|<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
!5<br />
|-<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
!17<br />
|-<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|2<br />
|2<br />
|3<br />
|4<br />
|3<br />
|4<br />
|3<br />
!21<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|<br />
|3<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!4<br />
|-<br />
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!3<br />
|-<br />
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|1<br />
|Monday, January 12, 2009<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|-<br />
|}<br />
:Congratulations ;-) [[User:RobertK|RobertK]] 11:30, 12 January 2009 (UTC)<br />
<br />
There is a nice [http://www.linuxdevices.com/news/NS6362979448.html LinuxDevices.com BeagleBot cruises on Linux] article about contest #1 winner, too.<br />
<br />
===Contest #2===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-03-01<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|6<br />
|7<br />
|5<br />
|7<br />
|3<br />
|5<br />
|<br />
!33<br />
|-<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|3<br />
|3<br />
|2<br />
|3<br />
|5<br />
|3<br />
|<br />
!19<br />
|-<br />
|[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]<br />
|1<br />
|<br />
|3<br />
|<br />
|2<br />
|2<br />
|<br />
!8<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|2<br />
|Monday, March 2, 2009 <br />
|[[BeagleBoard/contest#James|James]]<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|-<br />
|}<br />
<br />
==Other background==<br />
<br />
==Contest #1==<br />
<br />
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58<br />
<br />
==Contest #2==<br />
<br />
* [http://www.beagleboard.org/irclogs/index.php?date=2009-02-13#T15:35:43 IRC Log of discussion]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/661879a591dc396d Announcement at mailing list]<br />
* [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html Blog announcement]</div>Dirkhttp://elinux.org/BeagleBoard/contestBeagleBoard/contest2010-01-17T09:59:19Z<p>Dirk: Vote</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Image:beagle_first_place.png|thumb|right]]<br />
==Contest Announcements==<br />
===Sponsored Project Program===<br />
The [[BeagleBoard]] Software Design Contest has now been replaced with the [[BeagleBoard/contest#Contest_projects| BeagleBoard Sponsored Projects Program]] (formerly known as contest #3). The biggest difference is that we'll be giving 2 boards per week to projects as they are '''[[BeagleBoard/contest#Approved_projects|approved]]''', rather than waiting until they are completed. Also, successfully completed projects may be rewarded with higher-end BeagleBoard-derived systems, such as a [http://gumstix.com/store/catalog/product_info.php?products_id=229 Gumstix Palo43] or a [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book] (BeagleBoard based). You are encouraged to make your entries [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|now]].<br />
<br />
If your project is listed as a winner and you haven't received your board, check with ''beagleship at list.ti.com''.<br />
<br />
===Contest #2===<br />
<br />
''Contest #2 is finished. See [[BeagleBoard/contest#Winners_2|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html contest #2]. This contest is about giving away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to the winner and another one to the runner-up. [[BeagleBoard/contest#Judges|Judges]] will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, February 27, 2009 (afternoon) <br />
* '''Voting goes over weekend, end: Sunday, March 1, 2009 (afternoon)'''<br />
* Shipping board to winner: Monday, March 2, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get before this revision is publically available by DigiKey (~end of March 2009).<br />
</font><br />
<br />
===Contest #1===<br />
<br />
''Contest #1 is finished. See [[BeagleBoard/contest#Winners|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, January 9, 2009 (afternoon) <br />
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)<br />
* Shipping board to winner: Monday, January 12, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).<br />
</font><br />
<br />
==Project ideas==<br />
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:<br />
* Stable musb<br />
** ISOCH support<br />
** High-speed USB TV tuner support<br />
** Hot-plug support for OTG (host and client)<br />
* USB Digital TV tuner (either ATSC or DVB-T)<br />
** Hauppauge HVR950 suggested as reference<br />
* Projection TV coupled with the Pico<br />
* Audio record<br />
* Latest kernel version<br />
* USB camera support<br />
** gspca driver - need to validate with multiple cameras<br />
** <font color="#C0C0C0">UVC driver (I understood from Koen this is working)</font><br />
* Fixing bugs listed on code.google.com<br />
* Android port and various applications<br />
* <font color="#C0C0C0">EHCI support (done)</font><br />
* <font color="#C0C0C0">USB support in u-boot (partially done by first contest, but still needs work)</font><br />
* <font color="#C0C0C0">Consumer IR remote control via LIRC (already in feed; do 'opkg lirc')</font><br />
<br />
See also [[BeagleBoard/Ideas-2009]] for more ideas.<br />
<br />
==Contest projects==<br />
Please add your project you like to participate at Sponsored Projects Program (contest #3) to [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|Sponsored Projects Program projects]]. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1.1").<br />
<br />
===Sponsored Projects Program (Contest #3) projects===<br />
<br />
If you like to join Sponsored Projects Program (contest #3), please add your project here the same way like done for contest #1 and #2 below. If you participated already previous contests, please copy your project description to this contest, again. This will let everybody know that the project is still alive and that you want to participate Sponsored Projects Program.<br />
<br />
====Approved projects====<br />
From the project proposals, [[BeagleBoard/contest#Sponsored_Project_Program|approved projects]] will get a BeagleBoard Rev C at the '''beginning''' of their project to help them execute:<br />
<br />
{|border=1<br />
!Project<br />
!Approved<br />
!Comment<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Gregoire<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Revolt 2405|Revolt 2405]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Gentoo Linux ARMv7 support|Gentoo Linux ARMv7 support]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Accelerated_USB_Graphics_Adapter|Accelerated USB Graphics Adapter]]</font><br />
|<font color="#C0C0C0">Week 21</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#picoFlamingo|picoFlamingo]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle Synth |Beagle Synth]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#USB Scope |USB Scope]]</font><br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Irrlicht|Irrlicht]]<br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleHam|BeagleHam]]</font><br />
|<font color="#C0C0C0">Week 24</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Apertus_open_source.2Fhardware_cinema_camera|Apertus Digital Cinema Camera ]]<br />
|<font color="#C0C0C0">Week 25</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Handheld_Lab|Handheld Lab]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TCF_Agent_Port|TCF Agent Port]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Traveler|Beagle-Traveler]]</font><br />
|<font color="#C0C0C0">Week 27</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#OMAP Emulator|OMAP Emulator]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TUD:OS_on_Beagleboard|TUD:OS on Beagleboard]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#QEMUonARM|QEMUonARM]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#EGLIBC|EGLIBC Support]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#RT-Beagle|RT-Beagle]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ONAS|ONAS]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Math-NEON|Math-NEON]]<br />
|<font color="#C0C0C0">Week 32<br />
|<font color="#C0C0C0">5 votes<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Happiness_Device_for_Cerebral_Palsy_Kids|Device for Cerebral Palsy Kids]]</font><br />
|<font color="#C0C0C0">Week 32</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Turk|Turk Platform]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#hApplause|hApplause]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#eLazarillo|eLazarillo]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">1 vote</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#PREEMPT_RT|PREEMPT_RT]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#HDDM|HDDM]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleVision|BeagleVision]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#DJ Audio / Video Mixer|DJ Audio / Video Mixer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#schooldog|An individual lowcost schoolcomputer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Disko|Disko - UI Application Framework]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ESITeam|ESITeam]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#DVB-T_Receiver|DVB-T_Receiver]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">8 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#UPnP.2FDLNA_AV_client_renderer_and_transcoding_server|UPnP/DLNA AV client renderer and transcoding server]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Speed-Reader|Speed-Reader]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Arduino_hybrid_robot|Beagle-Arduino hybrid robot]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#XBMC_ARM_Port|XBMC Arm Port]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#GuideBeagle:_Portable_monocular_SLAM_system|Portable monocular SLAM system]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#MythBeagle|MythBeagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Touchscreen_LCD_support| Touchscreen LCD support]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FMframe |FMframe]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleSCI |BeagleSCI]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Pictouch|Pictouch]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Fotogenic |Fotogenic]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyGTee|MyGTee handheld]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Tourister_using_Hand_Gestures_and_HMD_on_Beagleboard|Beagle Tourister]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Medical Notebook|Medical Notebook]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#miniECG|miniECG]]<br />
|<br />
|<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#remoteBillBoard|Remote Bill Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleWacom|Wacom Tablet driver for Beagle Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleLAB|BeagleLAB]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FETCH|FETCH]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#PupLC|PupLC]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#ArchMobile:_ArchLinux_ARM_Port|ArchMobile]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
||[[BeagleBoard/contest#Homebrew_SmartPhone|Homebrew SmartPhone]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagleboard_Carputer|Beagleboard Carputer]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#AutoRobo|AutoRobo]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Walker|Beagle-Walker]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyoVox|MyoVox]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle-Eye|Beagle-Eye]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeaglePod|BeaglePod]]<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|1<br />
|<br />
|1<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MART|MART]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#CamCast|CamCast]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_SecMon|Beagle SecMon]]<br />
|<br />
|<br />
|<br />
|<br />
|1<br />
|1<br />
|<br />
|1<br />
|<br />
|-<br />
|[[BeagleBoard/contest#PortablePlateRec|PortablePlateRec]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Digital_Multimedia_Frame|Digital Multimedia frame]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#.28Speech.29_Scrambler_Beagle| (Speech) Scrambler Beagle]]<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
Rule: In each week, each judge has two points (two "1") to enter for his favorite project. The two projects with the most votes will be approved. The plan is to have final decision every Friday morning.<br />
<br />
==== Revolt 2405====<br />
<font color="#C0C0C0"><br />
* '''Title''': Revolt 2405<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Revolt2405/<br />
* '''Short project description''': First mission of a first person shooter style game using Ogre3D.<br />
* '''Homepage''': http://www.dcbcyber.com/revolt2405/wordpress<br />
* '''Expected results''': Expected results would be to have a playable game demo using Ogre3D for rendering. There will be sound and music. For controls I want to have the option of using keyboard and mouse or using controls like those found on hand held gaming devices. We would also like to have this playable on a small LCD as well as on a monitor connected to the DVI port.<br />
* '''Contact''': n2vdy at yahoo dot com or dbatzle at dcbcyber dot com<br />
</font><br />
==== Touchscreen LCD support ====<br />
<br />
* '''Title''': Touchscreen LCD support <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': The project will add the touch screen support to Beagle board<br />
The following are the components that i am planning of using<br />
:*The LCD breakout board is http://www.sparkfun.com/commerce/product_info.php?products_id=8600<br />
:*The touch screen is http://www.sparkfun.com/commerce/product_info.php?products_id=8977<br />
:*The touch screen connector is http://www.sparkfun.com/commerce/product_info.php?products_id=9104<br />
<br />
Another option is buying a full LCD with touch screen option<br />
:*The product link is http://www.sparkfun.com/commerce/product_info.php?products_id=257.<br />
:*I would create a system and hardware like this video http://www.youtube.com/watch?v=foWnDZ3eQto&feature=related<br />
<br />
* '''Homepage''': http://pradheeptce.googlepages.com/ yet to be fully completed.<br />
<br />
* '''Expected results''': <br />
**Linux driver to add LCD with touch screen support<br />
**The breakout board(preferably single layered as it can be created at home)gerber for attaching with beagle which will be created using FreePcb(www.freepcb.com).You can see the photos of my RFID Based Access Control system project there.<br />
**Wiki page to describe the entire development method<br />
* '''Contact''': pradheep_sh[at]tce[.]edu<br />
<br />
==== Gentoo Linux ARMv7 support ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Official Gentoo Linux ARMv7 support<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Gentoo/<br />
* '''Short project description''': Build ARMv7 optimized packages and stages for Gentoo Linux created officially by Gentoo developers.<br />
* '''Description''': The project is for providing official support for ARMv7-based devices like the Beagleboard, we will provide stages and packages optimized for ARMv7 processors so any owner of an ARMv7 device can get an optimized system. At the moment Gentoo only provides and supports ARMv4 and ARMv5TE, therefore we would like to expand our official support to the more powerful ARMv7 subarchitecture.<br />
* '''Homepage''': http://www.gentoo.org/proj/en/base/embedded/ http://www.gentoo.org/doc/en/handbook/handbook-arm.xml http://www.gentoo.org/proj/en/base/embedded/handbook/<br />
* '''Expected results''': <br />
**Allow Gentoo users to have ARMv7 optimized stages and packages.<br />
**Document the installation on the provided boards.<br />
* '''Contact''': armin76[at]gentoo[.]org , solar[at]gentoo[.]org<br />
</font><br />
==== TUD:OS on Beagleboard ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TUD:OS on Beagleboard <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/TUD%3AOS+on+the+Beagleboard/]<br />
* '''Short project description''': Port the L4-Microkernel based TUD:OS Operating System to the Beagleboard<br />
* '''Homepage''': will follow<br />
* '''Description''': <br />
** '''What the heck?''' The TUD:OS operating system is a L4 microkernel based operating system, with good real-time and security properties, developed at the TU Dresden. <br />
** '''Microkernel-based''': The microkernel approach allows it to to reduce the trusted computing base (the amount of code that has to be trusted) by running small trusted applications side by side with non-trusted applications, all as unprivileged user mode applications. Further, it is possible to run real-time applications side-by side with non real-time applications. Also device driver run in user-mode and thus a crash of a device driver will not lead to an whole system crash and in the best case the driver can be restarted and the system will keep on running.<br />
** '''Familiar Environment''': While offering the above mentioned vantages, TUD:OS still offers a familiar environment by the possibility to run one or more instances of L4Linux. L4Linux is a Linux port the Fiasco microkernel which is binary compatible to native Linux but runs in deprivilieged usermode.<br />
** '''What do we get from this project?''' ''Briefly: A fundament to build embedded [realtime] systems [with a exceptionally small trusted computing base].'' Further a possibility to run multiple virtualized linux instances on the beagleboard. A good documentation how to build such systems. And last but not least a (hopefully cool ;) demo showing that it acutally works , perhaps like the one found at [http://demo.tudos.org demo.tudos.org] (somewhat outdated). <br />
*'''Contact:''' dvogt[at]os[.]inf[.]tu-dresden[.]de ([[User:Dvogt|Dvogt]])<br />
</font><br />
==== picoFlamingo ====<br />
<font color="#C0C0C0"><br />
* '''Title''': picoFlamingo <br />
* '''beagleboard.org project''': http://beagleboard.org/project/picoFlamingo/<br />
* '''Short project description''': A portable presentation system for the BeagleBoard and the picoDLP projector<br />
* '''Homepage''': http://papermint-designs.com/picoflamingo<br />
* '''Expected results''': <br />
** An application to perform presentations including 3D elements.<br />
** A basic hardware specification for a portable presentation system.<br />
** A remote interface for wireless control of the presentation.<br />
** A demonstration of the possibilities provided by the BeagleBoard, the OMAP 3 platform and the picoDLP.<br />
** Hopefully a lightweight 3D render engine for OpenGL ES 2.0.<br />
** A lot of fun!!!... <br />
* '''Contact''': dmo[at]papermint-designs[.]com<br />
</font><br />
==== Accelerated USB Graphics Adapter ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Accelerated USB Graphics Adapter <br />
* '''beagleboard.org project''': Add link<br />
* '''Short project description''': USB-attached Graphics Card supporting OpenGL acceleration for XFree86<br />
* '''Homepage''': http://www.employees.org/~mschulma/beagleboard/cerberus/<br />
* '''Expected results''': <br />
** Use the Beagleboard to attach another monitor to a PC running Linux, and run a graphics intensive application on the expanded virtual desktop without slowing the main CPU.<br />
* '''Contact''': mschulma [at] employees [dot ] org<br />
</font><br />
==== Apertus open source/hardware cinema camera ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Apertus Digital Cinema Camera<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Apertus/<br />
* '''Short project description''': A digital camera controler for an Elphel open hardware camera. The beagle board will be used as a realtime viewfinder unit and hardware camera control.<br />
* '''Homepage''': http://cinema.elphel.com<br />
* '''Expected results''': We intend on creating a community driven open source cinematic HD camera for a professional environment. <br />
The image is provided by an Elphel camera (elphel.com, open source camera). A beagle board would be connected to an elphel camera using ethernet. The beagle board runs a lightweight UI that allows user to view the live feed from the camera on an external display (dvi or s-video). It also allows to trigger recording and change camera settings using a user interface. The user interface is software based (on screen) + hardware based using buttons and knobs if possible (I2C interface of the beagle board would be used). This project will take 2-6 months to have visible results. The feasibility of this project has been discussed on the Beagle Board group, with positive answers (cfr. http://groups.google.fr/group/beagleboard/browse_thread/thread/6c55a10dd598bb6/e946107bd0a807b8#e946107bd0a807b8 )<br />
* '''Contact''': philippe dot jadin at gmail dot com<br />
</font><br />
==== FMframe ====<br />
<br />
* '''Title''': FMframe<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': FMframe is a picture frame application coupled with an rss news reader and clock/alarm functionality<br />
* '''Homepage''': not yet; in a few days I will try to come up with a website with some preliminary screenshots.<br />
* '''Expected results''': Plan is to make a picture frame application. Hardwarewise the beagle will connect to a DVI display. Softwarewise it will be a picture frame optionally with a clock on top of the photo (either a big semi-transparent clock in the center or a smaller clock in the corner). There will also be an alarm function which can play a preselected mp3 file when the alarm time is reached. Apart from showing pictures the frame can also show news from a user definable rss feed (e.g. cnn.com), Normally this will be in a ticker-tape at the bottom of the picture. When the user presses a button when a specific topic is shown the full message pops up. Probably there will be dedicated provisions for weather, giving the weather forecast if desired (in a style as done by the google weather widget). When waking up the frame can show the weather with the scrolling news or (user selectable) just a list of headlines. When the alarm is switched off the display acts like a regular photo frame again.<br>User interaction will be through a remote control. Alternate inputs could be touch screen (if I get access to an affordable one) or keyboard (less convenient but it does allow people without IR receiver to control the device.<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
<br />
==== BeagleSCI ====<br />
<br />
* '''Title''': BeagleSCI<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': BeagleSCI aims to use the BeagleBoard as a platform for scientific computation and instrumentation (SCI).<br />
* '''Homepage''': http://sourceforge.net/projects/beaglesci/<br />
* '''Expected results''': As a start, the initial goal would be to use the BeagleBoard as a logger of a seismometer. This would involve interfacing a 12-bit ADC chip and writing a driver for it. Data read from the instrument can be displayed by the BeagleBoard through a monitor or send the data to a remote computer via RS-232/RS-485.<br />
* '''Contact''': sherdon dot uy at gmail dot com<br />
<br />
==== Pictouch====<br />
<br />
* '''Title''': Pictouch<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Mobile and Projected Touch user interface<br />
* '''Homepage''': not yet<br />
* '''Expected results''': The goal is to build a new Tactile Interface system based on beagleboard and the DLP picoprojector. Currently, the project make the use of JavaFX to support Multi-Touch (and Multi-User) and of 2 basic webcam, in order to build a low cost gesture recognition system.In the classical case of use, the interface is projected onto a classical table.Users interact directly with their fingers on the projected interface.<br />
<br />
* '''Contact''': maxired at gmail dot com<br />
<br />
==== Fotogenic ====<br />
<br />
* '''Title''': Fotogenic<br />
* '''beagleboard.org project''': not yet - but project is already in progress<br />
* '''Short project description''': Bring network connectivity to plain old vanilla picture frames<br />
* '''Homepage''': www.sourceforge.net/projects/fotogenic<br />
* '''Expected results''': This project brings wired, WiFi and bluetooth connectivity and management to plain old picture frames. The project selects pictures from your photo database, resizes them for the picture frame's native resolution, embellishes them with web and home automation information sources before presenting them to the photo frame by making the BeagleBoard appear to be a USB pendrive...! Right click a photo on your laptop and select "Show on picture frame now!". Manage many photo frames centrally and much much more... Includes "wave gesture" interface to wave over picture frame for next photo... Also works with Eye-Fi SD memory cards to make photos appear on photoframe moments after taken...!!<br />
* '''Contact''': horse_dung at hotmail dot com<br />
<br />
==== Beagle Synth ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Synth<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-synth/<br />
* '''Short project description''': DSP MIDI synthesizer based around the beagleboard<br />
* '''Homepage''': http://code.google.com/p/beagle-synth/<br />
* '''Expected results''': Initially a basic MIDI controllable subtractive synth with 3 oscillators, low pass, high pass, and band pass filters, 2 envelope generators, and 2 LFO's. From there the intention is to add some type of control surface (either physical controls or perhaps a touch screen), some effects (phaser, distortion, reverb), and perhaps other types of synthesis options (FM, additive, maybe some type of patchibility). The result will be a fully featured MIDI instrument comparable to many commercial synths. This project is to be a learning experience with the intention of exploring using DSP for music synthesis. As of now this project is in the concept phase and is still in need of hardware for implementation.<br />
* '''Contact''': dpanseri [at] gmail [dot] com<br />
</font><br />
==== USB Scope ====<br />
<font color="#C0C0C0"><br />
* '''Title''': USB Scope<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': USB diagnostics to aid driver development for USB devices<br />
* '''Homepage''': none yet<br />
* '''Expected results''': This project will use the BeagleBoard as a USB proxy between any USB device and a host computer connected via the OTG port. This will allow the BeagleBoard to snoop, compare and modify USB traffic which can assist both commercial and open source development of drivers and diagnosis of issues. Other ideas could be examined such as a USB-TCP/IP-USB proxy to remotely connect USB devices. Open or free software equivalents exist, but hardware monitoring devices only exist as expensive commercial products. <br />
* '''Contact''': horse_dung at hotmail dot com<br />
</font><br />
==== Irrlicht ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Irrlicht<br />
* '''beagleboard.org project''': no<br />
* '''Short project description''': A fully-featured 3D render engine with ogl-es 1.x and 2.x support<br />
* '''Homepage''': http://irrlicht.sourceforge.net<br />
* '''Expected results''': <br />
** Hardware optimized core routines for optimal OMAP support<br />
** Support of ogl-es 2.x (the 1.x driver is reportedly running on the board)<br />
** Full framerate (60FPS) rendering of q3 alike scenes<br />
** The engine also offers SW rendering, allowing to target for other OMAPs as well, but would require more tweaking in the render optimizations<br />
** We can port one of the demo apps from our apps contest to show the full applicability <br />
* '''Contact''': hybrid[at]users[.]sourceforge[.]net<br />
</font><br />
==== BeagleHam ====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleHam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleham/<br />
* '''Short project description''': Bringing the BeagleBoard to the world of Amateur Radio.<br />
* '''Homepage''': None at this time.<br />
* '''Expected results''': <br />
** AX.25 Packet support, enabling full APRS support (operating as tracker, fill-in or permanent digipeater, and KISS TNC).<br />
** Encode and decode of HF digital modes, using DSP functionality where possible:<br />
*** BPSK, QPSK 31/63/125/250<br />
*** Olivia<br />
*** WSPR/MEPT<br />
*** MT-63<br />
*** DominoEX<br />
*** RTTY<br />
*** Throb<br />
** CW encode and decode<br />
** Capability to display on small (sub-6-inch) screens for mobile and field use<br />
* '''Contact''': xunil at xunil dot net<br />
</font><br />
==== TCF Agent Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': TCF Agent Port<br />
* '''beagleboard.org project''': http://beagleboard.org/project/TCF+agent+port/<br />
* '''Short project description''': Support remote debugging and run control by porting the Eclipse Target Communication Framework (TCF) Agent to beagleboard+Ångström<br />
* '''Homepage''': Not yet<br />
* '''Expected results''': <br />
** A working port of the TCF "Reference implementation of a target agent" to BB/Ångström<br />
** screenshots and information on the TCF: http://dsdp.eclipse.org/dsdp/tm/tcf/docs/TCF%20Project.html<br />
** TCF agent running on a beagle board would provide the host computer following capabilities (see link above for details):<br />
*** Run control of userspace processes and threads<br />
*** Breakpoints<br />
*** Registers<br />
*** Stack traces<br />
*** Memory access<br />
*** Processes - list, start, stop, attach and debug.<br />
*** Sys monitor - CPU and memory utilization info<br />
*** File System - browsing and copying files<br />
<br />
* '''Contact''': terrella at terrella dot mobi<br />
</font><br />
<br />
==== RT-Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Real-Time patch for the beagleboard<br />
* '''beagleboard.org project''': http://beagleboard.org/project/omap-rt-patch/<br />
* '''Short project description''': Porting the linux rt patch to the omap linux kernel and providing testing applications. This project is developed at the INSA of Rennes (Engineer school in FRANCE) to allow next year Real Time course to be run on the BeagleBoard.<br />
* '''Homepage''': http://sourceforge.net/projects/linux-omap-rt-p/<br />
* '''Expected results''': <br />
** Porting the linux real-time patch (http://www.kernel.org/pub/linux/kernel/projects/rt/) to the linux omap kernel and providing recipes for openembedded allowing to build the patched kernel.<br />
** Providing testing applications allowing to evaluate the real-time behavior of the platform<br />
** Providing applications that could be used for teaching purposes<br />
* '''Current Results''':<br />
** patch-2.6.29.5-rt21 was modified to successfully patch linux-omap-2.6.29 (modified patch available through project page).<br />
** kernel compile and boots with minor error concerning two IRQs (72,73) <br />
* '''Contact''': piat_jonathan[at]users[.]sourceforge[.]net<br />
</font><br />
==== MyGTee ====<br />
<br />
* '''Title''': MyGTee <br />
* '''beagleboard.org project''': http://beagleboard.org/project/MyGTee/<br />
* '''Short project description''': A handheld device exploiting all the OMAP3530 capabilities<br />
* '''Homepage''': http://enco2009.webs.com/<br />
* '''Expected results''': I stage: building a prototype hopefully based on the BeagleBoard; II stage: the actual handheld that may allow for further software opensource development<br />
* '''Contact''': doctorc[at]o2[.]pl<br />
<br />
==== ONAS ====<br />
<font color="#C0C0C0"><br />
* '''Title''': ONAS<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ONAS/<br />
* '''Short project description''': An open source NAS<br />
* '''Homepage''': http://code.google.com/p/onas/<br />
* '''Expected results''': Development of a full featured NAS running Linux <br />
* '''Contact''': electrogeek[at]wp[.]pl<br />
</font><br />
==== Handheld Lab ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Handheld Lab<br />
* '''beagleboard.org project''': http://beagleboard.org/project/handheld_lab/<br />
* '''Short project description''': The goal of this project is to create a little, yet powerful, handheld laboratory with as much functions as possible. It will be easy of use thanks to the integrated LCD touchscreen and nice GUI.<br />
* '''Homepage''': http://www.mipixel.com/handheld-lab<br />
* '''Expected results''': First result will be working LCD showing oscilloscope. After this spectrum analyzer and logic analyzer. All this stuff will need extra electronics.<br />
* '''Contact''': fran[at]mipixel[.]com<br />
</font><br />
====Beagle Tourister using Hand Gestures and HMD on Beagleboard ====<br />
* '''Title''': Travel Buddy using Hand Gestures and HMD on Beagleboard <br />
* '''beagleboard.org project''': http://beagleboard.org/project/travelbuddy/<br />
* '''Short project description''': A device which will assist a traveller/tourist giving them mobile computing power and the following features: <br />
*1) A Compact HMD (Head mountable device) instead of the conventional projector (Problem of Projection Surface while on the move) <br />
*2) Use of standard cam for Image processing i.e recognising simple hand gestures to interact with the GUI seen in the HMD <br />
*3) Scanning of images (street name plates/hotel names/landmarks/book titles as indicated by user) to provide useful feedback data(directions/reviews/record *videos/take pictures/information) <br />
*4) Mode for Speech2text and text2speech conversion for inter-language communication. <br />
* '''Homepage''': Under Construction <br />
* '''Expected results''':<br />
*1) V-NAV: Virtual Navigator - Streaming Google Street View data according to your current location <br />
*2) ULA: Universal Language Assistant: Scan any text by positioning your fingers and the the scanned text is translated to your default language.<br />
*3) Say goodbye to the camera/ cell phone/tourguide/maps. Good platform for further expansion to include newer features. <br />
*4) Virtual Reality Mapping to the Real World: Overlay of relevant information on the on the HMD.<br />
* '''Contact''': sisilmet2000 at gmail dot com , dhairyadand at gmail dot com <br />
<br />
==== Happiness Device for Cerebral Palsy Kids ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Happiness Device for Cerebral Palsy Kids<br />
* '''beagleboard.org project''': http://beagleboard.org/project/HappyCP/<br />
* '''Project description''':<br />
It is an attempt to bridge the gap in communication between those affected by cerebral palsy and those not. The focus of the problem has been on facilitating communication in the emotional domain since this remains a completely unaddressed area. It is possible that some of the ensuing product functions will additionally facilitate communication problems in the physical domain, as well as be physically therapeutic for the cerebral palsy child in the manner of a comfort blanket. The basis of the product is an Emotional Language Protocol (elp) that works as its interface and is driven by four concurrently acting features - color, shape, motion and sound - corresponding to the sensory modes of the visual, the tactile and the aural. The interaction itself is facilitated by touch of varying intensities including pressing, thumping, squeezing, turning and, of course, by touching. Those not affected by cerebral palsy may additionally use speech along with touch. The interplay of this interface and interaction allows the cerebral palsy child to express his different needs and emotions to another person cerebral palsy or otherwise.Also, the device's mobile connectivity allows its users to communicate with someone far away<br />
* '''Homepage''': http://www.dhairyadand.com/Home/jellow<br />
* '''Expected results''': I have uploaded the basic designs at the above link to the homepage. The device is circular in nature with a touch screen where an interactive interface is used to display icons, objects, photos and other sharable action oriented stuff. The device has exchangable memory sticks which allow two or more device's to get connected and hence facilitating interactions. The result is to get a cerebral palsy kid out of his isolated environment, motivate him to communicate by making a device which will show him the joy of communicating.<br />
* '''Contact''': dhairya AT cyber DOT law DOT harvard DOT edu<br />
</font><br />
==== UPnP/DLNA AV client renderer and transcoding server ====<br />
<font color="#C0C0C0"><br />
* '''Title''': UPnP/DLNA AV client renderer and transcoding server <br />
* '''beagleboard.org project''': http://beagleboard.org/project/UPnP_AV_MediaServer/<br />
* '''Project description''':<br />
Enable the beagleboard as a fully featured UPnP AV rendering client, and as a UPnP AV (transcoding!) server. <br />
<br />
Work will be based upon vlc+djmount (for client side) and fuppes (for server side). Server side transcoding to be hardware assisted via hardware DSP codecs. Initial target for the transcoding server on beagleboard is to drive the Neuros OSD (an underpowered DM320-based device). <br />
<br />
* '''Homepage''': Will be an extension and complement to my work on the DM320-based Nueros OSD: http://osd.oddren.com<br />
* '''Expected results''': Beagleboard can act as either as rendering UPnP client, or as a transcoding UPnP server to drive weaker client devices like the Neuros OSD with their preferred streaming format.<br />
* '''Contact''': bmcarnes_beagleboard AT oddren DOT com<br />
</font><br />
==== Beagle-Traveler====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Traveler<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-traveler/<br />
* '''Short project description''': Automotive media and vehicle management controller. Comparable to BeaglesRide.org (no activity).<br />
* '''Homepage''': http://beagletraveler.wordpress.com<br />
* '''Expected results''': intergrate major automotive subsystem management and communications. Improved vehicle notification of subsystems status'. <br />
* '''Contact''': wheeler dawt larry (at) gmail dawt com<br />
**Please send sponsored information and project questions to the email address above.<br />
</font><br />
==== OMAP Emulator====<br />
<font color="#C0C0C0"><br />
* '''Title''': OMAP Emulator<br />
* '''beagleboard.org project''': http://beagleboard.org/project/OMAP+Emulator/<br />
* '''Short project description''': Emulator for rapid prototyping<br />
* '''Homepage''': no homepage yet<br />
* '''Expected results''': Open source implementation of an IDE environment for rapid code development and testing<br />
* '''Contact''': hwtester (at) myway (dot) com<br />
</font><br />
==== eLazarillo====<br />
<font color="#C0C0C0"><br />
[[File:Elazarillo.png|thumb|300px|eLazarillo sketch]]<br />
* '''Title''': eLazarillo (electronic helper for blind persons)<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': Gadget designed for blind persons or with vision problems. <br />
* '''Homepage''': http://elazarillo.blogspot.com/<br />
* '''Full description''':<br />
Lazarillo is a spanish word that means "blind person's guide" and this is the objetive of this project. This gadget will have features like reading non-braille books, assist to blind persons to get places like markets, drugstores, etc. (based on previous GPS tagged places and using google maps). Other functionalities will be spoken weather information, personal calendar, function keys, etc.<br />
<br />
The gadget will be voice controlled, will need GPS, 3G modem, camera and battery. Size will be 4x5 inches (approx.).<br />
<br />
* '''Expected results''': Open source hardware and software platform for blind persons gadgets. My device will have most of the above described.<br />
* '''Contact''': villanuevaborrego (at) gmail (dot) com<br />
</font><br />
<br />
==== QEMUonARM ====<br />
<font color="#C0C0C0"><br />
* '''Title''': QEMUonARM<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': QEMU on ARM. <br />
* '''Homepage''': http://elinux.org/QEMUonARM<br />
* '''Full description''':<br />
This project aims at resurrect and improve QEMU on ARM hosts.<br />
For more information: http://www.qemu.org<br />
* '''Expected results''': Demonstrate user mode and system mode examples, such as running some simple Linux applications or booting an i386 OS. If there's enough interest, making Wine and QEMU work together might be considered.<br />
* '''Contact''': laurent.desnogues (at) gmail (dot) com<br />
</font><br />
<br />
==== Math-NEON ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Math-NEON<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Math-Neon/<br />
* '''Short project description''': NEON optimized cmath like library <br />
* '''Homepage''': http://code.google.com/p/math-neon/<br />
* '''Full description''': <br />
This project aims to overcome the shortcomings of the VFP-lite based cmath implementation. It is targeted at games and other high performance low accuracy applications. The project will consist of C functions, for PC development, which mirror (as near as possible) the hand optimized NEON assembly routines. In order to gain the best performance i will make use of the NEON Unit's Integer and Floating point pipelines in conjunction with minimizing branches (where they cannot be precalculated on the ARM) and creating new algorithms. <br />
* '''Expected results''': Fast approximate implementations of trigonometric, exponential, logarithmic and power functions for use with future Beagleboard / Cortex A8 based projects. <br />
* '''Contact''': lachlan.ts (at) gmail (dot) com<br />
</font><br />
==== Medical Notebook ====<br />
* '''Title''': Medical Notebook<br />
* '''beagleboard.org project''': yet to register<br />
* '''Short project description''': The Ultimate Notebook for Hospitals<br />
* '''Homepage''': coming soon...<br />
* '''Full description''': <br />
A handheld device to improve hospital functionality/efficiency. To add intelligence to the mundane hospital softwares. <br />
Features are:<br />
<br />
View and Update Patient status, medical history, medication details, appointments, billing - stored as a database in central server.<br />
<br />
Touchscreen with handwriting recognition & hand support pad for data entry.<br />
<br />
Light Weight < 1kg<br />
<br />
VoIP, video conferencing/recording for consulting other doctors <br />
<br />
Wifi, bluetooth & ethernet support <br />
<br />
Docking station for charging<br />
<br />
Support for usb keyboard & mouse on docking station<br />
<br />
* '''Expected results''': <br />
<br />
1) Driver for touch pen tablet with support for hand writing recognition<br />
2) Porting of VoIP software for beagleboard (H.323 ???)<br />
3) Video conferencing software for beagleboard<br />
4) WiFi ?& bluetooth support on beagle board<br />
5) Speech recogntion software for beagleboard<br />
6) Entry of beagle board based products to hospital autmation market<br />
7) Improved, efficient & intelligent patient care in hospitals<br />
<br />
* '''Contact''': noorshaheen.m.n (at) gmail (dot) com<br />
<br />
==== EGLIBC ====<br />
<font color="#C0C0C0"><br />
* '''Title''': EGLIBC support<br />
* '''beagleboard.org project''':<br />
* '''Short project description''': Use EGLIBC as system library for beagleboard project in OpenEmbedded.<br />
* '''Homepage''': www.eglibc.org<br />
* '''Expected results''': EGLIBC becomes the default system library on the distribution and can be used instead of glibc<br />
with the newly added configurability support to selec/deselect features. I would also like to make it compile as pure thumb2<br />
code.<br />
* '''Contact''': raj[.]khem[at]gmail[.]com<br />
</font><br />
==== miniECG ====<br />
* '''Title''': miniECG<br />
* '''beagleboard.org project''': http://beagleboard.org/project/miniECG/<br />
* '''Short project description''': Little device that cares for heart when heart patients are busy carrying out their duties<br />
* '''Homepage''': http://code.google.com/p/miniecg/<br />
* '''Full description''': <br />
miniECG is a wearable device that monitors ECG signal, processes it and can transmit it over wireless internet connection to doctors clinic. It has following features are:<br />
(all the hardware components required are available through digikey.com including LCD and touch screen)<br />
<br />
1) It has touch screen that enable user to give commands like store, display old ECG data, transmit, etc. Device also has a LCD display which is used to display ECG waveform.<br />
<br />
2) A tiny server runs on device that enables doctor to login to device any time he wants and extract patients ECG data. The device is connected to internet through wireless USB dongle. <br />
<br />
3) DSP core does the job of compressing ECG signal, doing PCA (principal component analysis) on ECG signal, detect QRS, measuring heart beats and digital filtering.<br />
<br />
4) DSP along with Cortex A8 runs algorithm that determines critical state of heart by doing feature extraction over ECG signals. It also does PCA over set of stored ECG signal to obtain information about any substantial drift in normal functionality of heart. <br />
<br />
5) Wireless USB dongle provides connectivity to internet and data is transmitted over internet as per schedule programmed into the device. ECG signal can also be streamed over internet using this dongle. <br />
<br />
6) Keyboard & mouse (USB) interface is provided for more flexibility and quick access. LCD monitor interface is also be provided. Key-board, mouse and LCD monitor interface will work only when device is powered by adaptor. For device powered by battery only input option is touch screen and only output option is LCD display.<br />
<br />
7) Device also has small software support to give reminder on when to consume which drug. The prescription of drug and its timing information is feed in as per doctors advice. (keyboard and mouse interface with miniECG can be of great advantage here)<br />
<br />
8) USB memory devices will be used to store ECG data.<br />
<br />
9) miniECG will be dual powered. It can be powered by adaptor as well as with rechargeable battery. <br />
<br />
Website link has block diagram of miniECG and also picture of ECG pre-amplifier which is already designed. In future all the source codes will be uploaded on the link as and when available.<br />
<br />
* '''Expected results''': a) Ability to login from remote PC onto miniECG and read data b) Should be able to send stored data or stream live ECG signal over internet c) Robust interface of LCD & touch screen with controller d) Data storage and retrieval from USB storage device e) Successful implementation of DSP algorithms for feature extraction, PCA, QRS detection, filtering and compression. f) As the whole device is battery powered, software & driver which are very specific to the desired application should only be installed & made working. Thus providing a low power system architecture. <br />
<br />
* '''Future Work''': Once the desire basic funtions of ECG storing, retrieval and transmitting is meet, miniECG can be programmed into miniPA (mini personal assistance) mainly targeting senior citizens. miniPA will have much advanced features that can help them elderly person in their day-to-day activity.<br />
* '''Contact''': mehta.nandish (at) gmail (dot) com<br />
<br />
<br />
==== remoteBillBoard ====<br />
* '''Title''': Remote Bill Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/remoteBillBoard/<br />
* '''Short project description''': Video bill boards, remotely controlled via web over a 3G modem<br />
* '''Homepage''': http://www.greensoftware.net/remoteBillBoard<br />
* '''Full description''': <br />
Play HD video on billboards, remotely manage the billboards, upload new advertisements, remove old ones etc..<br />
<br />
<br />
* '''Expected results''': <br />
a) 3g modem support, so flexiblity.<br />
b) a full working web based system<br />
<br />
* '''Future Work''':<br />
a) a more advanced desktop application to replaced the web based solution.<br />
<br />
* '''Contact''': ahmad.mushtaq (at) gmail (dot) com<br />
<br />
<br />
==== Turk ====<br />
<font color="#C0C0C0"><br />
* '''Title''': Turk Platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Turk/<br />
* '''Short project description''': A wireless dynamically-mappable interface platform for small devices<br />
* '''Homepage''': http://www.turkinnovations.com/<br />
* '''Full Description''': Turk will be an open-source wireless interface platform that allows interfacing of small wireless (Zigbee or Wi-Fi enabled) devices through a dynamic mapping framework and web interface. Developers can implement their device's protocol easily through small user-space drivers called 'Gadgets' and host them on our server. The platform is then capable of automatically downloading and starting appropriate gadgets for new devices that are compatible with the basic Turk protocol. Gadgets reveal their services to the user and other gadgets through our growing library of data endpoint types (such as colors, URLs, booleans, xml strings) and user controls (like sliders, switches and color pickers), and can then be connected to each other through a themable web interface.<br />
<br />
* '''Expected results''': <br />
**A platform that allows developers to write simple user-space drivers that expose interfaces through XML-RPC<br />
**A web interface and remote configuration capabilities through a central server. <br />
**A simple and well-tested protocol and driver for a kernel-managed point-to-multipoint Zigbee network. <br />
**More hardware connectivity besides the Wi-Fi and Zigbee interfaces will hopefully be developed by collaborating with other beagleboard projects and developers.<br />
* '''Contact''': rob.odwyer [at] turkinnovations [dot] com<br />
</font><br />
==== BeagleWacom ====<br />
* '''Title''': Wacom Tablet driver for Beagle Board<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagle-wacom/<br />
* '''Short project description''': Linux drivers of wacom tablet ported for Beagle Board<br />
* '''Homepage''': <br />
* '''Full Description''': beagle-wacom will be port of linux drivers for configuring & running wacom tablets with the beagle board. The idea is to have support for wacom-components, so that they can be used by OEMs of beagleboard based products using linux as their OS<br />
<br />
* '''Expected results''': <br />
**easy integration of wacom tablet with Beagle Board. <br />
**OEMs of beagleboard based products using linux as their OS can integrate wacom-components in their product with minimal fuss<br />
* '''Contact''': najath [at] gmail [dot] com<br />
<br />
<br />
====hApplause====<br />
<font color="#C0C0C0"><br />
* '''Title''': hApplause<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': A Hardware Platform that You can use to play with Audio Synthesis<br />
* '''Homepage''': not yet<br />
* '''Description''': ''hApplause'' will be multi-functional flexible audio hardware platform. The goal is to make a tool that can allow to develop audio software and hardware (e.g. DSP synthesizers, FX units, hardware expansion boards, etc.). The concept is inspired by [http://www.chameleon.synth.net/ Chameleon] and [http://www.ucapps.de/ MIDIbox]. ''BeagleBoard'' will give ''Chameleon'' like software flexibility while planed hardware with ''Expansion Interface'' and ''Audio Multiplexer'' will give ''MIDIbox'' like hardware flexibility.<br />
*; Hardware features<br />
*: Audio Stereo In/Out<br />
*: MIDI In/Out/Thru<br />
*: General purpose USB port - function depends on user application<br />
*: General purpose SD/MMC Card (e.g. for user data storage) - function depends on user application<br />
*: Front panel interface (1U rack version) with:<br />
*:* LCD<br />
*:* Volume potentiometer<br />
*:* Headphones jack<br />
*:* Power switch with LED indicator<br />
*:* programmable rotary encoders (5 are planed)<br />
*:* programmable buttons and LEDs (12 are planed)<br />
*: Expansion Interface with audio signal buses (1-4 planed, depends on final implementation) and data/command bus (I2C and/or CAN)<br />
*: Audio Multiplexer for flexible routing of audio signal between ''BeagleBoard'', ''Audio In/Out'' and ''Expansion Interface''<br />
*: USB and RS232C for developers<br />
*; Software features<br />
*: All hardware will be fully accessible from ''BeagleBoard'' by API<br />
*: hApplause OS is planed (abstract layer over hardware, user program loading, self configuration on power on)<br />
* '''Expected results''':<br />
*# 19" 1U rackmount unit ready to play with.<br />
*# Libs and additional software for developers (at least API for hApplause's hardware)<br />
*# Example implementation of software synth<br />
*# Single size eurocard unit for 3U rack, like in [http://www.doepfer.de/a100e.htm Doepfer A-100 System] modules<br />
* '''Contact''': tawezik at gmail dot com<br />
</font><br />
==== BeagleLAB====<br />
* '''Title''': BeagleLAB<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleLAB/<br />
* '''Short project description''': BeagleLAB is an Embedded developer's workbench comprising of must-have hardware/software utilities.<br />
* '''Homepage''': http://code.google.com/p/beaglelab/<br />
* '''Expected results''': <br />
:* A PC free host providing a development environment based on beagle board (running ubuntu 9.04 or later)<br />
:* Host environment with software applications and hardware interfaces to substitute oscilloscope, multimeter & logic analyzers<br />
:* GNOME widgets (software apps) & Linux device drivers for capturing data,storing,comparing and visualization<br />
:* Legacy ports like the serial, parallel ports for device interfacing and control<br />
:* Making an embedded developer's life easier and workbench neater<br />
* '''Contact''': amarendermail[at]gmail[dot]com and saurabhg84[at]gmail[dot]com<br />
<br />
====PREEMPT_RT====<br />
<font color="#C0C0C0"><br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
</font><br />
<br />
====HDDM====<br />
<font color="#C0C0C0"><br />
* '''Title''': HDDM<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/HDDM/]<br />
* '''Short project description''': A multimedia system based on OMAP and linux.<br />
* '''Homepage''': Under construction<br />
* '''Expected results''': Beagleboard as a control center for home theatre system<br />
* '''Contact''': grover.ankur (at) gmail (dot) com<br />
<br />
Note from Dirk: Please see [http://www.syspire.de/node/3 Embedded Mediacenter], too (sorry, German only, use Google translate if needed).<br />
</font><br />
====BeagleVision====<br />
<font color="#C0C0C0"><br />
* '''Title''': BeagleVision<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beaglevision/<br />
* '''Short project description''': An efficient object recognition framework <br />
* '''Homepage''': http://code.google.com/p/beaglevision/<br />
* '''Description''': BeagleVision will be a fast object recognition framework. The aim of the project is to have a hardware optimized implementation (utilising the DSP and NEON) of state-of-the-art local feature detectors and descriptors on the Beagle Board. BeagleVision will include [http://www.cs.bris.ac.uk/Publications/pub_master.jsp?id=2001018 our recent work] on efficient feature detectors and descriptors, other well-known algorithms (e.g. FAST corner detector and SURF), and efficient matching algorithms for very large datasets (>1M images).<br />
* '''Expected results''':<br />
:* An open source library for developers (a project hosted on code.google.com)<br />
:* A sample application for building recognition in a city scale dataset, to show how: to add new images to the dataset, to use it for location based services, and how to reduce the search time if a GPS is available to get geolocations<br />
:* A wiki for interested developers<br />
:* Reporting the running times of new algorithms on OMAP (as a benchmark) in scientific publications<br />
* '''Contact''': m.ebrahimi at ieee dot org<br />
</font><br />
====Beagle-Arduino hybrid robot====<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle-Arduino hybrid robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Beagle-Arduino+hybrid+robot/<br />
* '''Short project description''': A robot using a Beagleboard for high-level processing and Arduino for low-level control<br />
* '''Homepage''': http://mechomaniac.com/robots<br />
* '''Description''': The Beagle-Arduino robot will use a Beagleboard for high-level robot functions:<br />
** image processing<br />
** artificial intelligence<br />
** speech synthesis<br />
** voice recognition<br />
** internet connectivity<br />
And an Arduino for low-level functions:<br />
** motor / servo control<br />
** sensor input & output<br />
** battery monitoring<br />
The two microcontrollers will be connected by USB, along with a USB webcam mounted on a servo pan/tilt mechanism, and a USB wifi dongle for internet connectivity. Basic tank treads will provide movement, possible being replaced by servo-based legs for a humanoid or dog form.<br />
* '''Expected results''':<br />
:* Easy physical interfacing to the Beagle without having to design and build special expansion boards<br />
:* Image processing using OpenCV with a USB webcam<br />
:* Speech synthesis and voice recognition<br />
* '''Contact''': tim at mechomaniac dot com<br />
</font><br />
<br />
====DJ Audio / Video Mixer====<br />
<font color="#C0C0C0"><br />
* '''Title''': DJ Audio / Video Mixer* '''Contact''': <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/djvideomixer/]<br />
* '''Description''': This is a small, Touch LCD controlled DJ Mixer, which not only is great as a nightclub tool for playing audio -not only reproducing music, actually '''''playing''''' with it-, but also has high end video playback capabilities, thus making it an all-round experience both for the DJ and the audience. It will bring all the experience of professional DJ mixers to users, while being portable, and which when coupled with either a normal projector, or even better, with a PicoProjector, makes a whole experience for audio and video playback in Discos, Bars, Lounges, to mention just a few possible applications. You can even use for your own parties, and it will rock!<br />
* '''Homepage''': [http://code.google.com/p/djvideomixer/]<br />
* '''Expected results''': <br />
** Audio playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Video playback on BeagleBoard, from USB sticks and SD Cards.<br />
** Audio/Video synchronization, allowing song change, video change, etc.<br />
** High end, professional DJ-Mixer audio effects.<br />
** User interface based on LCD and with touchscreen capabilities.<br />
* '''Contact''': jaime_dot_aranguren_at_ieee_dot_org<br />
</font><br />
====schooldog====<br />
<font color="#C0C0C0"><br />
* '''Title''': schooldog<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/schooldog/]<br />
* '''Description''': The purpose is to make an ''off the shelf'' low cost schoolcomputer that can be used on various levels of education. It will be small so students can take it with them and the school just has to provide for input / output items. This way even people that cannot afford laptops can participate in the digital era or schools can provide a robust and good machine for studypurposes.<br />
* '''Homepage''': [http://schooldog.wickedmind.net]<br />
* '''Expected results''': <br />
** Educational linuxbased OS, from USB sticks and SD Cards.<br />
** more general use of BeagleBoard and more public awareness for the powerful small computer.<br />
** Affordable,individual and steady study enviroment<br />
<br />
* '''Contact''': wickedmind<br />
</font><br />
====Disko====<br />
<font color="#C0C0C0"><br />
[[File:Disko_logo.png|thumb|200px|UI Application Framework]]<br />
* '''Title''': Disko - UI Application Framework<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Disko/<br />
* '''Short project description''': Disko is a Linux-based toolkit to build touchscreen- and remote-controllable ui applications. It contains native OMAP framebuffer support and the media content is DSP-accelerated by GStreamer (TI-Codecs).<br />
* '''Homepage''': http://diskohq.org<br />
<br />
* '''Expected results''': Expected result is broad support of Disko by developers of user interfaces and applications for embedded devices.<br />
** SIP - IP telephony support delivered by pjsip and minisip <br />
** Gstreamer - to add an alternative to the xine library and to add the TI Codecs supplied for the DSP.<br />
** Webkit - the great embedded browser OWB of Pleyo (planned for Disko 1.7)<br />
** SVG - at least one SVG engine to have an alternative to Flash. Initial work has already been done at MadButterfly (planned for Disko 1.7) <br />
* '''Contact''': gmadaus [at] berlinux-solutions dot de or mspringer [at] berlinux-solutions dot de<br />
</font><br />
====FETCH====<br />
* '''Title''': FETCH - FPGA enabled Tool Contol Host<br />
* '''beagleboard.org project''': http://beagleboard.org/project/FETCH<br />
* '''Homepage''': http://code.google.com/p/fetch/<br />
* '''Short project description''': A host with a web interface for easy configuration and control of connected tools. The device may also be controlled through a PSTN network using DTMF tones. The BeagleBoard will act as the main server and will also be the host interface for the connected FPGA for the purpose of evaluating the IPs developed on the FPGA.<br />
* '''description : Phase 1 '''<br />
***1) Server capability -- all services (except VNC) to be launched through inetd so that they are started on an on-demand basis. <br />
***-- http server for configuration pages <br />
***-- ssh server (the ssh suite in particular including scp etc.. so that an ftp server can be avoided) for remote login. <br />
***-- bootp server for bootstaping machines on my home network. <br />
***-- VNC for GUI sessions :) <br />
***-- CUPS for network printing <br />
***-- NetHack server :D <br />
***2) Tool Control <br />
***-- The term "Tool Control" here refers to automation of connected tools and Phase 1 of the project will demonstrate this by automation in home (eg. computer, printer, scanner on/off --> (the contoller board with the relays is complete :) ), these devices may be contolled over the internet or PSTN network ) The system will also be hooked to the home electrical network that will enable control over home appliances. A special mode called " Home Alone" will switch on/off lights randomly when no one is at home to give the illusion that the house is occupied ( and hence protect from thefts ;) ). The current relay boards developed use a UART (for RS232 protocol) for control of the equipment but it is planned to use the CAN interface (under developement ) so that longer distances can be covered. <br />
***3) The BeagleBoard will act as a host interfacefor a Nexys2 Xilinx FPGA board and will be used to evaluate the IPs deployed on it. This feature is sort of a tester for the FPGA. <br />
**'''Phase 2 ''' ( only after Phase 1 is completely functional :) ) <br />
***1) CAN interface for the controller nodes replacing the RS232 connections<br />
***2) mgetty (for faxes) and asterisk (VOIP) may be added to the server.<br />
* ''' Contact : ''' akshat dot g dot gupta [at] gmail dot com<br />
<br />
==== ESITeam====<br />
<font color="#C0C0C0"><br />
* '''Title''': ESITeam<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ESITeam/<br />
* '''Short project description''': It's a robotic soccer team with vision and intelligence distributed through the use of wireless communication (Zigbee) between robots and PC.<br />
* '''Expected results''': The expected results would have a running and competitive team for the RoboCup's championship this year.<br />
<br />
* '''Contact''': registrosvmora at gmail dot com<br />
</font><br />
==== PupLC====<br />
* '''Title''': PupLC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/PupLC/<br />
* '''Short project description''':Open source control of PLC operated equipment.<br />
* '''Homepage''': No homepage yet<br />
* '''Expected results''': <br />
:*PupLC will be an open source PLC controller. The user will be able to control the PLC's autonomously or by direct control. The direct method will allow the user to change equipment status using a touch screen lcd. The PupLC will control all aspects of the operating equipmet (ie. setpoints, red-hand settings, shutdowns, etc.) Additionally, 24-hours of accumulated system data will be saved to disk and can be accessed via ftp for analysis off-site.<br />
* '''Contact''': alcpo729[at]tds[dot]net<br />
<br />
====Speed-Reader====<br />
<font color="#C0C0C0"><br />
* '''Title''': Speed-Reader<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Speed-Reader/<br />
* '''Short project description''': Speed-Reader is an audio book reader that gives the listener control of the speaker rate.<br />
* '''Homepage''': http://www.nerd1951.com/?page_id=72<br />
* '''Description''': Speed reader allows an audio book to be played back with faster or slower speaker rates. A user interface gives the listener realtime control of the speaker rate. Speed-Reader uses digital speech signal processing to accomplish low distortion timescale modification of speech in real time. Timescale modification of speech is accomplished by selectively repeating segments of speech to slow down the speaker rate or deleting selected speech segments to speed up the speaker rate. Digital signal processing is used to determine which speech segments are candidates for repetition or deletion.<br />
* '''Expected results''':<br />
***--Realtime (during playback) timescale modification of digitized speech using the C64++ DSP<br />
***--Initially read digitized speech from the SD card interface<br />
***--Audio output using the Beagleboard stereo out<br />
***--Initially user interface provided via RS-232 interface<br />
* '''Contact''': harvey dot sugar at nerd1951 dot com<br />
</font><br />
<br />
====DVB-T Receiver====<br />
<font color="#C0C0C0"><br />
* '''Title''': DVB-T Receiver<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': The DVB-T Receiver project aims to implement a fully tunable DVB-T Receiver on the Beagle Board.<br />
* '''Homepage''': Will be launched in the near future (at blog.arsln.org)<br />
* '''Description''': The DVB-T receiver is a senior graduation project that has to be completed in one year (until Summer 2010). It will be a fully tunable DVB-T receiver. It will compatible to receive digital terrestrial TV & radio stations. The goal is to show the capabilities of the Beagle Board and build a DVB-T system from the scratch. The input will be through a ADC daughter-board that is plugged to the USB port. The output will be via the USB port(for portable devices i.e Netbook) or DVI-D. <br />
* '''Expected results''':<br />
***--Capturing broadcast signals(DVB-T) and convert them to discrete time signals<br />
***--Demodulate and encode the incoming signal<br />
***--Video output using the Beagleboard's DVI-D port or via the USB port for portable devices<br />
* '''Contact''': ftharsln at gmail dot com , sulaya05 at gmail dot com<br />
</font><br />
<br />
====ArchMobile: ArchLinux ARM Port====<br />
<br />
* '''Title''': ArchMobile<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/AM/ AM]<br />
* '''Short project description''': ARM Port of the x86-Linux Distribution ArchLinux<br />
* '''Homepage''': [http://www.archmobile.org ArchMobile]<br />
* '''Expected results''': Fully working ArchLinux with X and all other features.<br />
* '''Contact''': rotter.manuel@gmail.com or naeg on Freenode<br />
<br />
==== MythBeagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': MythBeagle<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': MythBeagle aims at bringing MythTV to the beagle; both frontend and backend, including plugins (as far as possible)<br />
* '''Homepage''': not yet; <br />
* '''Expected results''': <br />
** OE recipes for mythtv 0.22, mythplugins 0.22 and whatever might be needed to get things going (including bringing required recipes to the latest version where needed/possible)<br />
** An image for SD card to allow easy install, or a script or recipe to allow easy installation<br />
** some additional configuration notes (configuring MythTV is somewhat a pain...)<br />
** setup should also allow using the beagle only as frontend or backend<br />
* '''Status''': mysql5 recipe has been created (mythtv 0.22 won't use mysql4); recipes for mythtv are there, except for mythweb, documentation/installation work has started;<br />
* '''Contact''': fransmeulenbroeks at gmail dot com<br />
</font><br />
<br />
==== Homebrew SmartPhone ====<br />
<br />
* '''Title''': HomeBrewSmartPhone<br />
* '''beagleboard.org project''': http://code.google.com/p/hbpd<br />
* '''Short project description''': HomeBrewSmartPhone is a project to use the beagleboard to create a community-buildable mobile phone that is powerful enough to also run as a Desktop PC.<br />
* '''Homepage''': http://lkcl.net/reports/hbp <br />
* '''Expected results''': <br />
*** A device capable of Digital Voice as well as Data / Internet Access.<br />
*** A device capable of shutting down into low-power mode and successfully resuming on incoming calls.<br />
*** RF-protected audio circuits that don't have howling feedback from the 3G/GSM Radio module.<br />
*** Full disclosure of all build components (schematics, BOM) under free software licenses.<br />
*** Full documentation of all hardware interconnections<br />
*** Creation of a <b>basic</b> demonstration image that will allow other software developers to participate very early on<br />
*** Addition to the http://handhelds.org site for developers to create GUI-based distros<br />
* '''Contact''': lkcl@lkcl.net or use http://lkcl.net contact box<br />
<br />
==== XBMC ARM Port ====<br />
<font color="#C0C0C0"><br />
* '''Title''': XBMC<br />
* '''beagleboard.org project''': http://beagleboard.org/project/XBMC/<br />
* '''Short project description''': XBMC Is a full-feature home-theater application that works on a variety of platforms and operating systems<br />
* '''Homepage''': http://xbmc.org<br />
* '''Expected results''': <br />
*** Feature parity with XBMC x86 and ppc<br />
*** Usage of OpenGL ES 2.0<br />
* '''Contact''': Cory Fields: theuni @at@ xbmc .dot. org<br />
</font><br />
<br />
==== Beagleboard Carputer ====<br />
<br />
* '''Title''': Beagleboard Carputer<br />
* '''beagleboard.org project''': http://beagleboard.org/project/bbcarputer<br />
* '''Short project description''': The Beagleboard Carputer aims to create a fully-integrated system that will feature touchscreen LCD, Bluetooth and USB connectivity, GPS Navigation, Phone features, Wifi, Voice recognition, Multimedia entertainment.<br />
* '''Homepage''': http://bbcarputer.codeplex.com<br />
* '''Expected results''': Provide a fully-integrated system that will feature:<br />
*** 7in touchscreen LCD<br />
*** Wireless connectivity<br />
*** Usb connectivity<br />
*** GPS Navigation<br />
*** Phone features<br />
*** Voice recognition<br />
*** Multimedia entertainment<br />
*** Opensource Application Suite<br />
*** Games<br />
* '''Contact''': Joey Mar Antonio: joeymar.antonio @at@ awsol-i .dot. com<br />
<br />
==== GuideBeagle: Portable monocular SLAM system ====<br />
<font color="#C0C0C0"><br />
* '''Title''': GuideBeagle<br />
* '''beagleboard.org project''': Not yet available.<br />
* '''Short project description''': GuideBeagle is a portable localization and mapping system based on monocular vision. Such a system can be used, among other things, to build:<br />
:*Interactive visitor guidance systems for museums and stores.<br />
:*Artificial Reality tools and games.<br />
:*Mobile robot control systems.<br />
:*Surveillance and security related applications.<br />
:In other words: it solves a Simultaneous Localization and Mapping (SLAM) problem using a single camera as sensor, working on-line, and producing maps with high-level geometrical information (i.e. not just simple punctual visual landmarks on space). It will be based on recent research on the fields of Computer Vision and Mobile Robotics.<br />
* '''Homepage''': http://sites.google.com/site/guidebeagle (This page will be enhanced uninterruptedly.)<br />
* '''Expected results''': <br />
**Mapping --- The final system will allow an user to move by an environment like an office or a small apartment and build a map of it similar to a 3D model with planes and textures, as used in Computer Graphics.<br />
**Localization --- After a map is built, the user can move around the environment, and the system will interactively estimate the geometric location of the camera and the direction it is heading, based on images continuously obtained from the camera.<br />
**Image processing --- Building this system will require the coding of image processing tools that may be useful to many other image processing applications based on the Beagle Board. Some examples are feature detectors and descriptors, edge detectors, template matching by normalized cross-correlation and the Discrete Fourier Transform.<br />
* '''Contact''': nwerneck@gmail.com or nwerneck@usp.br<br />
</font><br />
<br />
==== AutoRobo ====<br />
<br />
* '''Title''': Development of an autonomous robotics platform<br />
* '''beagleboard.org project''': http://beagleboard.org/project/autorobo/<br />
* '''Short project description''': Design, prototype and develop an autonomous aerial vehicle system around BeagleBoard, allowing experimentation with real-time control and computer vision algorithms.<br />
* '''Philosophy''':<br />
:* make robotics and embedded control accessible and fun<br />
:* stimulate cross-field learning and collaboration<br />
:* leverage modularity and reuse to get more done, quicker <br />
* '''Technical goals''':<br />
:* develop generalised physics model for eg computing optimal PID controlled motor outputs<br />
:* decouple high-update-rate sensors from lower-rate output control<br />
:* employ OpenCV for visual tracking/SLAM/feature detection<br />
:* build lean tracked (land) vehicle<br />
:* build lean quad-rotor (air) vehicle<br />
:* use a shared, modular code-base and electronics platform (Beagle and IGEPv2) <br />
* '''Homepage''': http://code.google.com/p/autorobo/<br />
* '''Expected results''': Initial bringup of a tracked vehicle via dual-motor controller via Beagle's PWM outputs. Utilisation of 3-axis accelerometer and 3-axis gryo via I2C and/or SPI buses, enabling more advanced control<br />
* '''Contact''': ''daniel (dot) blueman (at) gmail (dot) com''<br />
<br />
==== Beagle-Walker ====<br />
<br />
* '''Title''': Design of a automatic dog-walker robot<br />
* '''beagleboard.org project''': http://beagleboard.org/project/BeagleWalker/<br />
* '''Short project description''': Develop an autonomous dog-walker robot<br />
* '''Homepage''': http://code.google.com/p/beaglewalker/<br />
* '''Expected results''': <br />
**The main goal of the system is analyze the feedback between the dog and the robot to track where the dog is going and where the robot should go.<br />
**Let the dog walk only in places previously programmed by the dog's owner making use of basic SLAM algorithms. <br />
**avoid any obstacles/vehicles.<br />
* '''Contact''': ''darthdj at gmail dot com''<br />
<br />
==== nullDC / Beagle ====<br />
<font color="#C0C0C0"><br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nullDC<br />
* '''Expected results''': For the contest: A working build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
</font><br />
<br />
==== MyoVox ====<br />
* '''Title''': MyoVox<br />
* '''beagleboard.org project''': <br />
* '''Short project description''': <br />
* '''Homepage''': <br />
* '''Expected results''': <br />
* '''Contact''': smcgill3 [at] seas[.]upenn [.] edu<br />
<br />
==== Beagle-Eye ====<br />
<br />
* '''Title''': Beagle-Eye<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle-Eye/ Beagle-Eye]<br />
* '''Short project description''': A beagle-eyed guide for the visually challenged.<br />
<br />
* ''' Hardware''':<br />
** A pair of calibrated USB cameras, mounted on the user's shoulders, such that the combined field of view covers at least 180 degrees.<br />
** One or more linear actuators connected through RS-232, situated on one of the user's limbs.<br />
** Stereo headphones.<br />
** USB GPS Dongle.<br />
<br />
* '''Description''':<br />
** Low frame rate real-time video is used to guide the user towards a specified destination.<br />
** The GPS provides coarse location.<br />
** The stereo camera setup provides a wide field of view, along with coarse depth information.<br />
** Map information, combined with real time video is used to esimate location and orientation more accurately.<br />
** Simple object recognition techniques are employed to recognize parts of the environment.<br />
** The audio setup and the actuator(s) are used either in tandem or interchangeably to guide the user. This can be customized as required. Some possibilities include:<br />
*** A short periodic 3D sound generated to indicate the direction in which the user is to walk.<br />
*** The user is alerted about approaching obstacles by firing the actuator at a frequency inversely proportional to the distance to the obstacle. This distance can be computed using depth information computed from pairs of images.<br />
*** Information about the environment, such as "Pedestrian Crossing in 20m" can be relayed through audio.<br />
<br />
* '''Possible Enhancements''':<br />
** More comprehensive localization techniques, such as SLAM, can be used to improve the accuracy of the system. This will also open doors to indoor navigation, where the GPS fails.<br />
** Detection, segmentation and recognition of text (such as signboards and street names) in the environment will ensure less errors in navigation.<br />
<br />
* '''Expected Results''':<br />
** A navigation tool for the visually challenged, using audio and linear actuators to communicate with the user.<br />
<br />
* '''Contact''': leatherbrain at gmail dot com<br />
<br />
==== BeaglePod ====<br />
<br />
* '''Title''': BeaglePod<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglepod/]<br />
* '''Short project description''': BeaglePod is an IPod plug-in replacement for car stereo's that are IPod Ready. The BeaglePod uses gstreamer as an audio/video player and is controlled via the car stereo head unit using Apple Accessory Protocol. <br />
* '''Description''': The BeaglePod is an audio/video player for cars equipped with "IPod Ready" stereos. Using the Apple Accessory Protocol the car stereo is used to select and control the playback of media on the BeaglePod. Adding a video monitor the BeaglePod can also become a video player running all the audio through the car stereo with full pause, play, stop control using the car's stereo head unit. Using a software implementation of the Apple Accessory Protocol the BeaglePod is connected to the car stereo via a USB->TTL cable.<br />
* '''Expected Results''':<br />
** Play audio/video media files from the Beagleboard using the car stero to control playback and track selection.<br />
** Audio will playback through car's exist speaker.<br />
** With gstreamer dsp support HD playback of video with in car lcd.<br />
* '''Contact''': velorider [X] publicemail [X] us<br />
<br />
==== MART ====<br />
* '''Title''': Autonomous modular robot<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': Build an autonomous robot to enter the Eurobot 2010 competition<br />
* '''Homepage''': (only in Czech) http://eurobot.matfyz.info/<br />
* '''Full Description''': Goal of this project is to build an autonomous modular robot, that will be able to compete in the Eurobot competition. This project includes following:<br />
<br />
** '''HW''':<br />
** Custom beagle daughter-card (including kernel driver patches):<br />
*** CAN (Controller area network) able to sustain 1Mbit/s, using embedded cortex-m3 controller<br />
*** Battery backed up RTC<br />
*** Dual power - battery and/or adapter, with battery management (current consumption sensing and charging) <br />
*** Second serial and i2c headers<br />
*** (optional) Ethernet controller 10/100Mbit<br />
** Custom motor, servo and stepper motor drivers and IO boards<br />
*** everything connected through CAN<br />
<br />
** '''SW''':<br />
** Modular architecture, for simple modification<br />
** OpenCV integration for play field object identification<br />
** optimalizations for NEON (and DSP)<br />
<br />
* '''Contact''': Michal dot Demin at Gmail dot Com<br />
<br />
==== CamCast ====<br />
* '''Title''': Webcam broadcast server/relay<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/CamCast/]<br />
* '''Short project description''': Webcam broadcast platform for USB webcams<br />
* '''Homepage''': <br />
* '''Full Description''': The goal of this project is to utilize the beagleboard as a low cost platform for webcam video feeds.<br />
Server capability:<br />
<br />
** Broadcast webcam feeds for directly connected USB webcams<br />
** Relay webcam feeds from other servers, typically connected over wi-fi<br />
** Decimate MJPEG streams to match bandwidth limits<br />
** Monitor and control streams via HTTP<br />
** Advertise HTTP services locally via Zeroconf<br />
<br />
The beagleboard will require a functional Linux gspca driver for all USB webcams in use as well as USB wi-fi for remote service. Linux Zeroconf service must also be included.<br />
<br />
* '''Contact''': spiderkarma at gmail dot com<br />
<br />
====Beagle SecMon====<br />
<br />
* '''Title''' : Beagle Security Monitoring over Web <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/Beagle+SecMon/ BeagleSecMon]<br />
* '''Short project description''': This project proposes to control and transmit audio and video from a remote place using the beagleboard as a webserver.<br />
* '''Expected results''': The system will control one or more digital cameras with pan, tilt and zoom functions, and microphones. Besides, it can be configured to send information to a pre registered cell phone when movement is detected. Also, audio and video can be accessed using internet from any place.<br />
* '''Contact''': cborges at ifsc dot edu dot br====<br />
<br />
====PortablePlateRec====<br />
<br />
* '''Title''' : Beagle Portable Plate Recognition <br />
* '''beagleboard.org project''': [http://beagleboard.org/project/PortablePlateRec/ PortablePlateRec] <br />
* '''Short project description''': A portable system for automatic number plate recognition (ANPR) using BeagleBoard.<br />
* '''Expected results''': The goal of this project is to develop a portable system for automatic number plate recognition (ANPR) using BeagleBoard. It includes the following:<br />
** receiving images from a camera;<br />
** applying signal processing algorithms for plate localization, orientation and sizing, image normalization, and character segmentation;<br />
** optical character recognition (for instance, Tesseract);<br />
** possible access to a database to check the plate against law infringements.<br />
<br />
* '''Contact''': fpacheco at ml1 dot net<br />
<br />
====Digital Multimedia Frame====<br />
<br />
* '''Title''' : Digital Multimedia Frame<br />
* '''beagleboard.org project''': not yet<br />
* '''Short project description''': It's a photo, video and music application who use a touchscreen display<br />
* '''Expected results''': The goal of this project is to get photo, video, music from memory card or from a network. <br />
<br />
** Scan network to multimedia file. <br />
** Create automatically a slideshow when we are in photo mode.<br />
** Create automatically a music list.<br />
** Play video<br />
** Add basic operation available for picture (rotate, resize...)<br />
** touch screen will be used to simplify action.<br />
<br />
* '''Contact''': collinm at laboiteaprog dot com<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
===Contest #2 projects===<br />
<br />
Please don't add new projects, contest #2 is closed.<br />
==== James ====<br />
1st [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/James James]<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. <br />
* '''Expected results''': Updated recipes for all relevant packages on OpenEmbedded. A script to install the needed packages to an Angstrom image (generated by Koen's generator) and documentation on how to configure things.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
</font><br />
====BeagleEPD====<br />
2nd [[BeagleBoard/contest#Winners_2|winner]] of contest #2<br />
<font color="#C0C0C0"><br />
* '''Title''': E-Ink Interface Board and Driver for beagleboard<br />
* '''Homepage''': [http://elinux.org/BeagleEPD BeagleEPD]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/beagleepd/<br />
* '''Short project description''': This project aims to interface an E-Ink display directly with a beagleboard. This is done by creating an interface board that is connected to the Beagleboard expansion header and converts the relevant gpio signals into the levels appropriate for interfacing with the E-Ink display controller. The second part is to write a driver which is a port of am300epd.c from mach-pxa to mach-omap in order to support the E-Ink broadsheet framebuffer driver directly on beagleboard. All of this results in making it possible to connect any E-Ink display controller to a Beagleboard (via the expansion header) and to then treat any E-Ink display as another framebuffer.<br />
* '''Expected results''': Schematic for interface PCB between Beagleboard and E-Ink display controller board. A beagleepd.c mach-omap driver that will setup and control the IO pins appropriately.<br />
* '''Contact''': jayakumar at IRC (freenode, oftc) or jayakumar.lkml@gmail.com<br />
</font><br />
==== nullDC / Beagle ====<br />
<br />
* '''Title''': nullDC_Beagle - Full SEGA Dreamcast emulator, with newly added support for Beagle.<br />
* '''beagleboard.org project''': http://beagleboard.org/project/nullDC_Beagle/<br />
* '''Short project description''': Full featured emulator for SEGA Dreamcast, Naomi and Sammy Atomiswave. Supports full hardware emulation, debugger (x86 only), VMU/Memory packs, state saves and much more. <br />
* '''Homepage''': http://www.emudev.org/nulldc_beagle<br />
* '''Expected results''': For the contest: A WIP (but working) build of the emulator to show full utilization of the beagles hardware capabilities, including emulation of a 200mhz RISC processor (Hitachi SuperSH4), a 33mhz ARM7tdmi with full AICA DSP emulated on the C64x DSP, and utilisation of the PowerVR SGX hardware to emulate the Dreamcast's PowerVR CLX2 chip-set. It is expected all of the hardware will be at near 100% utilisation.<br />
* '''Contact''': ZeZu [at] emudev [.] org<br />
<br />
==== (Speech) Scrambler Beagle ====<br />
<br />
* '''Title''': (Speech) Scrambler Beagle<br />
* '''beagleboard.org project''': http://beagleboard.org/project/ScramblerBeagle/<br />
* '''Short project description''': A speech scrambler developed on Beagleboard for scrambling analog audio I/O (in "speech domain"). By scrambling means: processing it digitally using commonly used Cryptography Algorithm (AES, 3DES etc) and or other "unique-your-own-algorithm"<br />
* '''Homepage''': http://dago.posterous.com/<br />
* '''Expected results''': Full (digital) data processing of speech data acquired from analog I/O.The data processing involves: 1. Speech Coding, we will use LPC 10; 2. Modulation, QPSK will be there as the prototype; 3. Encryption -- AES 128 comes into mind. <br />
* '''Contact''': dio[dot]rahman[at]gmail.com<br />
<br />
===Contest #1 projects===<br />
<br />
====qemu-omap3====<br />
<br />
* '''Title''': support beagle board emulation in qemu<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/qemu-omap3/ qemu-omap3]<br />
* '''Short project description''': Qemu-omap3 is an opensource project which adds omap3 related devices emulation into qemu. Beagle board is the primary devices to emulate.<br />
* '''Homepage''': [http://code.google.com/p/qemu-omap3/ qemu omap3 emulation support]<br />
* '''Expected results''':<br />
** booting linux kernel and rootfs from nand and mmc image<br />
** Wiki page how to run qemu-omap3 for beagle board<br />
* '''Submission''':<br />
** http://code.google.com/p/qemu-omap3/wiki/UserManual<br />
* '''Contact''': yajin AT vm-kernel.org<br />
<br />
====openGPS====<br />
<br />
* '''Title''': develop open source software to use BeagleBoard as a handheld GPS receiver<br />
* '''beagleboard.org project''': none yet<br />
* '''Short project description''': openGPS is a project to use a basic processing platform with open source software to develop a handheld GPS receiver. Using any of a number of available map data bases, such as Open Street Maps, a handheld GPS receiver would provide new capabilities that are not currently found in commercial receivers. In addition it would provide a platform for a number of customizations and expansion of capabilites. <br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** development of a display app with moving map capabilities<br />
** development of a user interface for handheld apps<br />
** integration with suitable LCD display<br />
** interface to map files on SD card<br />
** Wiki page on GPS receiver functions and features<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====Beagle Conference System====<br />
<br />
* '''Title''': Use beagle to come up with a conferencing system for home users<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/BeagleConf/ BeagleConf]<br />
* '''Short project description''': This is a project that aims at bringing conferencing into the drawing rooms of users' homes. The idea is to use beagle, interface it with a webcam, internet (through ethernet/ wifi), usb bluetooth (to interface a integrated keyboard/ mouse), audio in and out of beagle interfaced with a microphone and the speakers of the tv (in the living room of the user), and use a conferencing software like Ekiga (or probably Skype?). The device should be extremely affordable (low cost), to bring conferencing to homes of common users.<br />
* '''Homepage''': none yet<br />
* '''Expected results''':<br />
** A 'complete' home conferencing system would include the 'unit' and a keyboard with an integrated mouse. The 'unit' shall consist of beagle, with interfaces exposed for USB webcam, audio in for microphone, audio out to connect to the TV, ethernet interface or another USB port for USB wifi and another USB port for bluetooth.<br />
** When the system is turned on, users shall be presented with a list of contacts that they could dial (probably a customized interface of Ekiga).<br />
** The software shall provide the users, the capability to add/ modify/ delete users and their contact details.<br />
** The software shall also provide for ways to chat (text) with the users.<br />
** The software shall be capable of running through a demo for the users which includes instructions for set up and usage.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====BeagleRC====<br />
<br />
* '''Title''': Use a beagle board to drive a remote controlled car.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Connect servos to the beagle board expansion header, 802.11g wireless to the use port, and use joystick on a host to remotely control the servos. <br />
* '''Homepage''': http://chrisd.info/portfolio/indexbeaglerc.shtml<br />
* '''Expected results''':<br />
** Ability to control a RC car using only a beagle board and servos, this will work with both nitro and electric cars with mechanical speed controllers.<br />
* '''Contact''': code at chrisd dot info<br />
<br />
====PREEMPT_RT====<br />
<br />
Linux Hard Real-Time (PREEMPT_RT) demo<br />
<br />
* '''Title''': Test hard real-time (-rt) Linux kernel 2.6.31 on the Beagle, report and fix -rt related bugs, create real-time applications demo using OpenEmbedded / Ångström.<br />
* '''beagleboard.org project''': None<br />
* '''Short project description''': Make sure the TI OMAP device drivers are -rt safe; Build a typical real-time user land set of applications (Ångström based).<br />
* '''Homepage''': http://www.sidebranch.com/<br />
* '''Expected results''': hard sub 300 microseconds (us) scheduling latency for real-time class user space applications (targetting multimedia).<br />
** Real-time scheduled media playback. Less or no frame skips on video. Latency reports.<br />
* '''Contact''': likewise IRC<br />
<br />
====USB Support in U-boot ====<br />
2nd [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Add MUSB gadget support for OMAP3 to u-boot.<br />
* Homepage: [[U-boot musb gadget support]]<br />
* '''beagleboard.org project''': http://beagleboard.org/project/Uboot+USB+gadget/<br />
* '''Short project description''': Currently people require an extra serial adaptor to interact with u-boot, adding USB gadget support to u-boot enables the use of serial console, saving costs and troubles to BeagleBoard users. This enables as well the future application of the DFU patches to power fast software downloads without requiring MMC (but the DFU patches are a different can of worms to be accepted on mainstream u-boot).<br />
* '''Expected results''': U-boot patch against u-boot omap3 git tree that enables booting beagleboard and appear as an USB serial adaptor (CDC class, so it can be used in Linux/OS x without major problems), and the modified .inf file for windows.<br />
* '''Contact''': ddompe at IRC<br />
</font><br />
<br />
==== James ====<br />
<br />
* '''Title''': James - Just A Miniature Entertainment System<br />
* '''beagleboard.org project''': To be Added...<br />
* '''Short project description''': James is a home server system aiming at video recording (PVR), storage and playback, but also offering other common home functions, e.g. in the areas of security and IP telephony. <br />
* '''Homepage''': For now [[BeagleBoard/James]]. For the PVR part there is information and a demo through http://www.dse.nl/~meulenbr/pvr/pvr.html<br />
* '''Expected results''': For the contest: the proposal on [[BeagleBoard/James]] and the demo on http://www.dse.nl/~meulenbr/pvr/pvr.html. For the future: a flexible system providing the functionality as described in the proposal.<br />
* '''Contact''': fransmeulenbroeks on gmail<br />
<br />
====BeagleBot====<br />
1st [[BeagleBoard/contest#Winners|winner]] of contest #1<br />
<font color="#C0C0C0"><br />
* '''Title''': Beagle Board powered robot<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beaglebot/ beaglebot]<br />
* '''Short project description''': BeagleBot is a Beagle powered robot. It has few servos, ultrasonic ranger, webcam, wlan...<br />
* '''Homepage''': [http://www.hervanta.com/stuff/Beaglebot BeagleBot homepage]<br />
* '''Expected results''':<br />
** Partly autonomous robot<br />
** PC controlling of the robot<br />
* '''Contact''': antti at hervanta.com<br />
</font><br />
<br />
====Android Cupcake for BeagleBoard====<br />
<br />
* '''Title''': Android Cupcake for BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/beagledroid beagledroid]<br />
* '''Short project description''': This is a port of the post-1.0 Cupcake version of Android to the BeagleBoard. <br />
* '''Homepage''': For now, you can download the images from [http://www.nthcode.com/download/sd.img.gz here] and instructions from [http://www.nthcode.com/download/readme.txt here]<br />
* '''Expected results''': Android boots, runs, can browse the Internet, etc. No sound, though.<br />
* '''Contact''': ''Please add (obfuscated) mail address or Beagle IRC nick''<br />
<br />
====FreeBSD port to BeagleBoard====<br />
<br />
* '''Title''' : A port of FreeBSD-arm to the BeagleBoard<br />
* '''beagleboard.org project''': [http://beagleboard.org/project/freebsd-bgb/ freebsd-bgb]<br />
* '''Short project description''': This is a port of the FreeBSD operating system to the BeagleBoard, as the first platform for supporting Omap on the OS.<br />
* '''Expected results''': FreeBSD boots and can be used through a serial console + port of a (USB?) ethernet controller driver for NFS boot.<br />
* '''Contact''': AsqYzeron====FreeBSD port to BeagleBoard====<br />
<br />
==Judging==<br />
<br />
===Judges===<br />
* Jason Kridner (jkridner)<br />
* Koen Kooi (koen)<br />
* Dirk Behme (dirk2)<br />
* Steve Sakoman (sakoman)<br />
* Hunyue Yau (ds2)<br />
* Mans Rullgard (mru)<br />
* Gregoire Gentil (gregoiregentil)<br />
<br />
===Past Judges===<br />
* Robert Kuhn (robertk)<br />
<br />
===Rules===<br />
* Judges cannot participate in the contest.<br />
* The ruling of the judges is final. Jason Kridner will determine when the ruling of the judges has been provided.<br />
* Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins.<br />
* All voting will be public and logged on this page.<br />
* Jason Kridner will be responsible for getting the boards to the winner and runner-up. Recipients must meet US export control requirements.<br />
* To follow up on shipping details, contact ''beagleship at list.ti.com''.<br />
* Individuals are limited to a single entry, but may include as many demonstrations as desired within that entry.<br />
<br />
===Criteria===<br />
* All new content must be open source as determined by the OSI.<br />
* Submission should be in the form of an easy-to-use image/archive provided via a webpage.<br />
** <1GB 'dd' image for an SD card is recommended. [http://www.beagleboard.org/~arago/mksdimg.txt Instructions]<br />
** Alternatives allowed, such as [http://labs.embinux.org/android-porting-on-beagle.html Android on Beagle], as long as instructions are provided.<br />
* "Wow" or "coolness" factor from usefulness/user experience point of view<br />
* Overall quality of the submission<br />
* Technical complexity<br />
** "Coolness" of the technical solution, even if it isn't useful for all the masses<br />
** Amount of work needed, i.e. x hours or x days?<br />
* Angstrom recipe for image<br />
* Documentation for the demo<br />
* Running power consumption<br />
* Use of DSP and SGX<br />
* Ease of use<br />
<br />
===Contest #1===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-01-11<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#qemu-omap3|qemu-omap3]]<br />
|3<br />
|<br />
|3<br />
|2<br />
|<br />
|3<br />
|2<br />
!13<br />
|-<br />
|[[BeagleBoard/contest#openGPS|openGPS]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Conference_System|Beagle ConfSys]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|[[BeagleBoard/contest#BeagleRC|BeagleRC]]<br />
|1<br />
|<br />
|<br />
|1<br />
|3<br />
|<br />
|2<br />
!7<br />
|-<br />
|[[BeagleBoard/contest#Linux_Hard_Real-Time_.28PREEMPT_RT.29_demo|RT demo]]<br />
|<br />
|2<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
!5<br />
|-<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
|3<br />
|2<br />
!17<br />
|-<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|2<br />
|2<br />
|3<br />
|4<br />
|3<br />
|4<br />
|3<br />
!21<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|<br />
|3<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!4<br />
|-<br />
|[[BeagleBoard/contest#Android_Cupcake_for_BeagleBoard|Android]]<br />
|2<br />
|<br />
|<br />
|<br />
|1<br />
|<br />
|<br />
!3<br />
|-<br />
|[[BeagleBoard/contest#FreeBSD_port_to_BeagleBoard|FreeBSD port]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
!<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|1<br />
|Monday, January 12, 2009<br />
|[[BeagleBoard/contest#BeagleBot|BeagleBot]]<br />
|[[BeagleBoard/contest#USB_Support_in_U-boot|MUSB for U-Boot]]<br />
|-<br />
|}<br />
:Congratulations ;-) [[User:RobertK|RobertK]] 11:30, 12 January 2009 (UTC)<br />
<br />
There is a nice [http://www.linuxdevices.com/news/NS6362979448.html LinuxDevices.com BeagleBot cruises on Linux] article about contest #1 winner, too.<br />
<br />
===Contest #2===<br />
<br />
====Points====<br />
<br />
Each judge will have 10 points to divide (integrally) as they see fit. The project with the most points wins. Points:<br />
<br />
{|border=1<br />
| 2009-03-01<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Robert<br />
|'''Sum points'''<br />
|-<br />
|[[BeagleBoard/contest#James|James]]<br />
|6<br />
|7<br />
|5<br />
|7<br />
|3<br />
|5<br />
|<br />
!33<br />
|-<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|3<br />
|3<br />
|2<br />
|3<br />
|5<br />
|3<br />
|<br />
!19<br />
|-<br />
|[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]<br />
|1<br />
|<br />
|3<br />
|<br />
|2<br />
|2<br />
|<br />
!8<br />
|-<br />
|}<br />
<br />
====Winners====<br />
<br />
{|border=1<br />
!Contest<br />
!Date<br />
!Winner<br />
!Runner-up<br />
|-<br />
|2<br />
|Monday, March 2, 2009 <br />
|[[BeagleBoard/contest#James|James]]<br />
|[[BeagleBoard/contest#BeagleEPD|BeagleEPD]]<br />
|-<br />
|}<br />
<br />
==Other background==<br />
<br />
==Contest #1==<br />
<br />
* IRC Log of discussion: http://www.beagleboard.org/irclogs/index.php?date=2008-12-18#T18:40:58<br />
<br />
==Contest #2==<br />
<br />
* [http://www.beagleboard.org/irclogs/index.php?date=2009-02-13#T15:35:43 IRC Log of discussion]<br />
* [http://groups.google.com/group/beagleboard/browse_thread/thread/661879a591dc396d Announcement at mailing list]<br />
* [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html Blog announcement]</div>Dirkhttp://elinux.org/BeagleBoard/contestBeagleBoard/contest2010-01-17T09:57:45Z<p>Dirk: Reformat approved project</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Image:beagle_first_place.png|thumb|right]]<br />
==Contest Announcements==<br />
===Sponsored Project Program===<br />
The [[BeagleBoard]] Software Design Contest has now been replaced with the [[BeagleBoard/contest#Contest_projects| BeagleBoard Sponsored Projects Program]] (formerly known as contest #3). The biggest difference is that we'll be giving 2 boards per week to projects as they are '''[[BeagleBoard/contest#Approved_projects|approved]]''', rather than waiting until they are completed. Also, successfully completed projects may be rewarded with higher-end BeagleBoard-derived systems, such as a [http://gumstix.com/store/catalog/product_info.php?products_id=229 Gumstix Palo43] or a [http://www.alwaysinnovating.com/touchbook/ Always Innovating Touch Book] (BeagleBoard based). You are encouraged to make your entries [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|now]].<br />
<br />
If your project is listed as a winner and you haven't received your board, check with ''beagleship at list.ti.com''.<br />
<br />
===Contest #2===<br />
<br />
''Contest #2 is finished. See [[BeagleBoard/contest#Winners_2|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] [http://beagleboard.blogspot.com/2009/02/software-design-contest-2-in-3d.html contest #2]. This contest is about giving away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to the winner and another one to the runner-up. [[BeagleBoard/contest#Judges|Judges]] will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, February 27, 2009 (afternoon) <br />
* '''Voting goes over weekend, end: Sunday, March 1, 2009 (afternoon)'''<br />
* Shipping board to winner: Monday, March 2, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get before this revision is publically available by DigiKey (~end of March 2009).<br />
</font><br />
<br />
===Contest #1===<br />
<br />
''Contest #1 is finished. See [[BeagleBoard/contest#Winners|winners]].''<br />
<br />
<font color="#C0C0C0"><br />
Welcome to [[BeagleBoard]] contest #1. This contest is about give-away one BeagleBoard Rev [[BeagleBoard#Revision_C2|C2]] to winner and another to the runner-up. Judges will determine criteria and won't be eligible for winning the contest. Schedule:<br />
<br />
* Final project updates: Friday, January 9, 2009 (afternoon) <br />
* Voting goes over weekend, end: Sunday, January 11, 2009 (afternoon)<br />
* Shipping board to winner: Monday, January 12, 2009<br />
<br />
BeagleBoard revision C2 will have working USB HOST (EHCI) and newest OMAP3 silicon revision. By this contest you will get it ~2 month before this revision is publically available by DigiKey (~March 2009).<br />
</font><br />
<br />
==Project ideas==<br />
Here are some ideas which projects would be nice to be done by this contest. But don't hesitate to add your cool project [[BeagleBoard/contest#Contest_projects|below]] even if it doesn't match any of these ideas:<br />
* Stable musb<br />
** ISOCH support<br />
** High-speed USB TV tuner support<br />
** Hot-plug support for OTG (host and client)<br />
* USB Digital TV tuner (either ATSC or DVB-T)<br />
** Hauppauge HVR950 suggested as reference<br />
* Projection TV coupled with the Pico<br />
* Audio record<br />
* Latest kernel version<br />
* USB camera support<br />
** gspca driver - need to validate with multiple cameras<br />
** <font color="#C0C0C0">UVC driver (I understood from Koen this is working)</font><br />
* Fixing bugs listed on code.google.com<br />
* Android port and various applications<br />
* <font color="#C0C0C0">EHCI support (done)</font><br />
* <font color="#C0C0C0">USB support in u-boot (partially done by first contest, but still needs work)</font><br />
* <font color="#C0C0C0">Consumer IR remote control via LIRC (already in feed; do 'opkg lirc')</font><br />
<br />
See also [[BeagleBoard/Ideas-2009]] for more ideas.<br />
<br />
==Contest projects==<br />
Please add your project you like to participate at Sponsored Projects Program (contest #3) to [[BeagleBoard/contest#Sponsored_Projects_Program_.28Contest_.233.29_projects|Sponsored Projects Program projects]]. Please add the project to [http://beagleboard.org/project beagleboard.org projects], too. If you add a new project here, please append it at the end of list below. Then we can rely on numbering if talking about projects (e.g. "I like project 3.1.1").<br />
<br />
===Sponsored Projects Program (Contest #3) projects===<br />
<br />
If you like to join Sponsored Projects Program (contest #3), please add your project here the same way like done for contest #1 and #2 below. If you participated already previous contests, please copy your project description to this contest, again. This will let everybody know that the project is still alive and that you want to participate Sponsored Projects Program.<br />
<br />
====Approved projects====<br />
From the project proposals, [[BeagleBoard/contest#Sponsored_Project_Program|approved projects]] will get a BeagleBoard Rev C at the '''beginning''' of their project to help them execute:<br />
<br />
{|border=1<br />
!Project<br />
!Approved<br />
!Comment<br />
!Jason<br />
!Koen<br />
!Dirk<br />
!Steve<br />
!Hunyue<br />
!Mans<br />
!Gregoire<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Revolt 2405|Revolt 2405]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Gentoo Linux ARMv7 support|Gentoo Linux ARMv7 support]]</font><br />
|<font color="#C0C0C0">Week 19</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Accelerated_USB_Graphics_Adapter|Accelerated USB Graphics Adapter]]</font><br />
|<font color="#C0C0C0">Week 21</font><br />
|<font color="#C0C0C0">5 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#picoFlamingo|picoFlamingo]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle Synth |Beagle Synth]]</font><br />
|<font color="#C0C0C0">Week 22</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#USB Scope |USB Scope]]</font><br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Irrlicht|Irrlicht]]<br />
|<font color="#C0C0C0">Week 23</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleHam|BeagleHam]]</font><br />
|<font color="#C0C0C0">Week 24</font><br />
|<font color="#C0C0C0">6 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Apertus_open_source.2Fhardware_cinema_camera|Apertus Digital Cinema Camera ]]<br />
|<font color="#C0C0C0">Week 25</font><br />
|<font color="#C0C0C0">4 points</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Handheld_Lab|Handheld Lab]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TCF_Agent_Port|TCF Agent Port]]</font><br />
|<font color="#C0C0C0">Week 26</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Traveler|Beagle-Traveler]]</font><br />
|<font color="#C0C0C0">Week 27</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#OMAP Emulator|OMAP Emulator]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#TUD:OS_on_Beagleboard|TUD:OS on Beagleboard]]</font><br />
|<font color="#C0C0C0">Week 28</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#QEMUonARM|QEMUonARM]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#EGLIBC|EGLIBC Support]]</font><br />
|<font color="#C0C0C0">Week 29</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#RT-Beagle|RT-Beagle]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ONAS|ONAS]]</font><br />
|<font color="#C0C0C0">Week 30</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Math-NEON|Math-NEON]]<br />
|<font color="#C0C0C0">Week 32<br />
|<font color="#C0C0C0">5 votes<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Happiness_Device_for_Cerebral_Palsy_Kids|Device for Cerebral Palsy Kids]]</font><br />
|<font color="#C0C0C0">Week 32</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Turk|Turk Platform]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#hApplause|hApplause]]</font><br />
|<font color="#C0C0C0">Week 33</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#eLazarillo|eLazarillo]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">1 vote</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#PREEMPT_RT|PREEMPT_RT]]</font><br />
|<font color="#C0C0C0">Week 35</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#HDDM|HDDM]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#BeagleVision|BeagleVision]]</font><br />
|<font color="#C0C0C0">Week 37</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#DJ Audio / Video Mixer|DJ Audio / Video Mixer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">5 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#schooldog|An individual lowcost schoolcomputer]]</font><br />
|<font color="#C0C0C0">Week 39</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Disko|Disko - UI Application Framework]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#ESITeam|ESITeam]]</font><br />
|<font color="#C0C0C0">Week 42</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#DVB-T_Receiver|DVB-T_Receiver]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">8 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#UPnP.2FDLNA_AV_client_renderer_and_transcoding_server|UPnP/DLNA AV client renderer and transcoding server]]</font><br />
|<font color="#C0C0C0">Week 43</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Speed-Reader|Speed-Reader]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#Beagle-Arduino_hybrid_robot|Beagle-Arduino hybrid robot]]</font><br />
|<font color="#C0C0C0">Week 45</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#XBMC_ARM_Port|XBMC Arm Port]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">3 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#GuideBeagle:_Portable_monocular_SLAM_system|Portable monocular SLAM system]]</font><br />
|<font color="#C0C0C0">Week 49</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">|[[BeagleBoard/contest#MythBeagle|MythBeagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">4 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<font color="#C0C0C0">[[BeagleBoard/contest#nullDC_.2F_Beagle|nullDC / Beagle]]</font><br />
|<font color="#C0C0C0">2010 - Week 2</font><br />
|<font color="#C0C0C0">2 votes</font><br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Touchscreen_LCD_support| Touchscreen LCD support]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#FMframe |FMframe]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleSCI |BeagleSCI]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Pictouch|Pictouch]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Fotogenic |Fotogenic]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#MyGTee|MyGTee handheld]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Beagle_Tourister_using_Hand_Gestures_and_HMD_on_Beagleboard|Beagle Tourister]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#Medical Notebook|Medical Notebook]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#miniECG|miniECG]]<br />
|<br />
|<br />
|1<br />
|1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#remoteBillBoard|Remote Bill Board]]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|[[BeagleBoard/contest#BeagleWacom|Wacom Tablet driver for Beagle Board]