Difference between revisions of "BeagleBoard/GSoC/Ideas"

From eLinux.org
Jump to: navigation, search
(2011 -> 2012)
 
(194 intermediate revisions by 25 users not shown)
Line 2: Line 2:
 
[[Category: OMAP]]
 
[[Category: OMAP]]
 
[[Category: BeagleBoard]]
 
[[Category: BeagleBoard]]
 +
[[Category: GSoC]]
 +
 +
__TOC__
  
 
=Welcome!=
 
=Welcome!=
BeagleBoard.org hopes to be accepted as a mentoring organization in the [[BeagleBoard/GSoC|Google Summer of Code]] for 2012!! Here we collect project Ideas for the 2012 GSoC.
+
BeagleBoard.org hopes to be accepted as a mentoring organization in the [[BeagleBoard/GSoC|Google Summer of Code]] for 2014! Below, we've collected project ideas for the GSoC-2014.
  
'''Background'''<br>
+
==Background==
For a quick view of how the BeagleBoard relates to the open source development community, take a listen to [http://www.youtube.com/watch?v=m9xVbntl-DY Mans and Koen's interview with the Linux Outlaws]. The BeagleBoard is a popular [http://en.wikipedia.org/wiki/Open-source_hardware open-source hardware] project utilizing the first broadly available ARM Cortex-A8 processor. Over 10,000 people are experimenting with the BeagleBoard today to bring their ideas for the future of everywhere-computing to life and you can be one of them.
+
BeagleBoard.org is a volunteer organization that seeks to advance the state of open-source software on [http://en.wikipedia.org/wiki/Open-source_hardware open-source hardware] platforms capable of running high-level languages and operating systems (primarily Linux) in embedded environments. Born from taking mobile phone processors and putting them on low-cost boards to build affordable desktop computers, BeagleBoard.org has evolved to focus on the needs of the "maker" community with greater focus on the I/O needed for controlling motors and reading sensors to build things like robots, 3d printers, flying drones, in-car computer systems and much more. Past BeagleBoard.org GSoC projects included [[BeagleBoard/GSoC/2010_Projects/C6Run|an RPC framework for heterogeneous processor communication]], [[BeagleBoard/GSoC/2010_Projects/USBSniffer|a transparent USB packet sniffer]], [[BeagleBoard/GSoC/2010_Projects/XBMC|ARM optimizations for XBMC]], [[BeagleBoard/GSoC/2010_Projects/FFTW|ARM optimizations for FFTs]], [[BeagleBoard/GSoC/2010_Projects/Pulse_Width_Modulation|make-shift pulse-width-modulation]] and [[BeagleBoard/GSoC/2010_Projects/OpenCV|RPC optimizations for OpenCV]]. BeagleBoard.org has benefited from sponsorship from Texas Instruments, [[CircuitCo]], Digi-Key and others, but avoids any dependence on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 100,000 boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, Debian, ArchLinux, Gentoo, Buildroot and many more.
  
People are building autonomous flying vehicles, robots, home media centers, video walls, in-car computers and much more.  By executing or mentoring a Google Summer of Code project with BeagleBoard.org, you can work towards making these things easier to create and better to use for your peers---and you'll get some hardware too.
+
BeagleBoard was inspiration for Raspberry Pi[http://www.linuxuser.co.uk/features/raspberry-pi-interview-eban-upton-reveals-all] and is available for only $45 through over 30 distributors world-wide (and is even available at Microcenter and Radio Shack in the USA), but is more than a throw-away computer. It is an instance of true open hardware, exposing users to the broader world of electronics, demystifying computers and fostering an environment of clones that have changed the industry for good.
  
The BeagleBoard:
+
Students will be expected to demonstrate an understanding of cross-compiling before being accepted, but support for demonstration is available through the IRC channel that typically has approximately 150 online chatters logged on at any time, most with sufficient experience to explain the process.
* utilizes a complex SoC with 3 primary processing cores,
+
** one for general-purpose activities such as running Linux and applications (ARM Cortex-A8),
+
** one for running real-time signal processing algorithms (C64x+ VLIW fixed-point DSP), and
+
** one for rendering 3D graphics (Imagination SGX), and
+
* is specifically designed for low-power (typically running under 2W at full processing load), and
+
* has a very small foot-print that includes standard peripheral expansion like USB.
+
  
The result is that there are many opportunities to explore challenges in computer science in areas of:
+
'''''<span style="color:red">Every accepted student will be sent a BeagleBone Black before the first week of coding for testing their project.</span>'''''
* optimal execution of applications/algorithms on additional instruction set architectures like ARM or C6000,
+
* splitting tasks appropriately between processing cores to minimize task execution time and power consumption, and
+
* integrating computation into new form-factors.
+
  
'''Students and mentors'''<br>
+
Additional hardware will be provided depending on need and value.
Student proposals can create projects from the following ideas or propose their own project based on their own ideas.  From reading about previous Google Summer of Code projects, the key to success is being passionate about your project, so propose something that is extremely interesting to you, even if it not on the list. We will be glad to help students develop ideas into projects on [http://webchat.freenode.net/?channels=beagle the BeagleBoard IRC] or [http://groups.google.com/group/beagleboard the BeagleBoard mailing list]. There are many more ideas of what can be done and we will match projects to students interest and help scope the proposal to something that can be completed in the Summer of Code time-frame.
+
  
There are more than 200 existing projects listed at http://beagleboard.org/project. If you are interested in one of those projects, talk with the project members to see if there are any aspects of their projects with which they can help you contribute. There are also several ideas on the [[ECE597_Project_Ideas|ECE597 class project idea list]].
+
For more information, check out http://beagleboard.org and http://beagleboard.org/brief.
  
__TOC__
+
==Students looking for ideas==
 +
Student proposals can encompass projects inspired from the following list of ideas or can include personal project ideas. Previous Google Summer of Code projects show that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even if it is not on this list. We will be glad to help students develop ideas into projects via [http://webchat.freenode.net/?channels=beagle the BeagleBoard IRC] or [http://groups.google.com/group/beagleboard the BeagleBoard mailing list]. There are many potential project ideas and we will match students to projects based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.
  
=General requirements=
+
There are more than 300 existing projects listed at http://beagleboard.org/project. If you are interested in any of the projects listed on the BeagleBoard.org projects page, contact the project members to see if there are any aspects of their projects that can be enhanced to create a GSoC project. There are also several ideas on the[[ECE497_Project_Ideas|ECE497 class project idea list]]. You can also check out [[BeagleBoard/GSoC/Ideas-2013|last year's idea page]].
 +
 
 +
==Mentors wondering where to help==
 +
Please start by registering your ideas for student projects below by following the template provided with the existing ideas. Furthermore, scroll down to the bottom and give everyone a bit of information about your expertise and availability by adding yourself to the table. Jason will make final approvals for mentor assignments based on if we first get accepted as a mentoring organization and best matching mentor skill sets with student project ideas deemed valuable to the community.
 +
 
 +
You will also need to register on [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Melange] and request to be a mentor for BeagleBoard.org.
 +
 
 +
==General requirements==
 
All projects have the following basic requirements:
 
All projects have the following basic requirements:
# The project must be registered on http://beagleboard.org/project.
+
# Once accepted, the project must be registered on http://beagleboard.org/project.
 
# All newly generated materials must be released under an [http://www.opensource.org/licenses open source license].
 
# All newly generated materials must be released under an [http://www.opensource.org/licenses open source license].
 
# Individual students shall retain copyright on their works.
 
# Individual students shall retain copyright on their works.
# Source code generated during the project must be released on gitorious.org, github.com, repo.or.cz, sourceforge, code.google.com, gforge.ti.com, or omapzoom.org.
+
# Source code generated during the project must be released on github.com (to be cloned to github.com/beagleboard on successful completion).
# The registration on http://beagleboard.org/project must include an RSS feed with project announcements and updates at every milestone.  Sources for the RSS feed should be blogger.com, wordpress.com, or some other established blog hosting service with known reliability.
+
# The registration on http://beagleboard.org/project must include an RSS feed with project announcements and updates at every milestone.  Sources for the RSS feed should be blogger.com, wordpress.com, or some other established blog-hosting service with known reliability.
# To help you to break your project down into manageable chunks and also help the project's mentors to better support your efforts, weekly project status reports should be e-mailed to the project's mentors and the organization administrator (Jason Kridner). Each status report should outline:
+
# To help you to break your project down into manageable chunks and also to help the project's mentors to better support your efforts, weekly project status reports should be e-mailed to the project's mentors and the organization administrator (Jason Kridner). Each status report should outline:
 
## what was accomplished that week,  
 
## what was accomplished that week,  
## any issues that prevented that week's goals from being completed, and
+
## any issues that prevented that week's goals from being completed and
 
## your goals for the next week.
 
## your goals for the next week.
# Students will provide two recorded presentations, one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments.  Examples can be found on http://beagleboard.org/gsoc.
+
# Students will provide two recorded audio/video presentations uploaded to youtube or vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments.  Examples can be found on http://beagleboard.org/gsoc.
# Students will demonstrate their ability to cross-compile and utilize version control software by creating a "Hello World" application and uploading it as a fork to http://gitorious.org/beagleboard-validation/gsoc.  For assistance, please visit http://beagleboard.org/chat or utilize the beagleboard-gsoc Google Group.  The "Hello World" application must print your name and the date out in an ARM Linux environment.  Freely available emulators may be used to to test your application or you can ask anyone on the chat or mailing list to help you test.
+
# Students will demonstrate their ability to cross-compile and utilize version control software by creating a "Hello World" application and generating a pull request to https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner.  For assistance, please visit http://beagleboard.org/chat or utilize the beagleboard-gsoc Google Group.  The "Hello World" application must print your name and the date out in an ARM Linux environment.  Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
# All projects will produce reusable software components and will not be "what I built over my Summer vacation" projects. Including a hardware component is welcome, but the project *deliverable* will be software that may be utilized by a wide audience of the BeagleBoard community.
+
# All projects will produce reusable software components and will not be "what–I-built-over-my-summer-vacation" projects. Including a hardware component is welcome, but the project *deliverable* will be software that may be utilized by a wide audience of the BeagleBoard.org community.
  
=Fundamental infrastructure projects=
+
=Ideas=
These projects fundamentally improve support of existing open source projects for ARM-based devices in general and the BeagleBoard in specific, bringing the broad body of high-level open source applications into smaller, lower-cost, lower-power systems that can go anywhere.
+
There are several areas needing contributions:<br>
 +
'''Kernel''': Improving the state of the Linux kernel including improved ARM/OMAP/Sitara platform support, simplifying the development of add-on hardware for embedded systems and exchanging hardware connectivity information with userspace.<br>
 +
'''Secondary processor support (RPC/gcc/etc.)''': Enabling usage of DSPs, PRUs, FPGAs, Cortex-M3s, Arduinos, MSP430 launchpads and other attached processing platforms.<br>
 +
'''Scripting libraries and web interfaces''': Improving the Bonescript JavaScript library, web-based interface libraries, examples or alternatives in other languages.<br>
 +
'''Frameworks for open-hardware projects''': Consolidating support for simplified home manufacturing (CNC, 3D printers, laser cutters, pick-and-place machines, etc.), drones/bots (ROS, IMU, video streaming, etc.) or other common tasks.<br>
 +
'''Optimizations to existing userspace applications/libraries''': Optimizations to applications and libraries like XBMC to make them run better on resource constrained environments or to take advantage of more specialized processing elements.<br>
  
==Improve boot support==
+
==BeaglePilot==
There are many bootloaders available for the BeagleBoard and other ARM embedded devices, and all can be given improvements for ease-of-use for new users. Nevertheless, U-boot is the most used one and the one that most new Beagleboard users will come in contact with, so improving U-boot for new users gives the most benefit for the project.
+
Porting ArduPilot to BeagleBone Black. Some of the tasks include:
 +
<br>
  
''Goals:''
+
* PRU drivers (PWM and PPM)
* U-boot updates
+
* SPI drivers for cape sensors
** Add support for the OMAP3 EHCI controller in U-boot
+
* RC Input (PPM)
*** BeagleBoard and BeagleBoard-xM both have an USB EHCI controller that is currently not supported by U-boot
+
* Power handling
*** OMAPPedia reports some patches are available for PandaBoard that could be reused for BeagleBoard
+
* Analog sensing
** Add support for USB MSC devices
+
* Flight tests
** Add support for the Ethernet controller on the BeagleBoard-xM that is connected via the EHCI controller
+
** Verify TFTP support
+
** Debug USB OTG MUSB driver
+
** Clean up DFU patch on mailing list and get accepted mainline
+
** Replace x-loader with u-boot SPL for NAND
+
** Replace x-loader with u-boot SPL for MMC/SD
+
** Replace x-loader with u-boot SPL for USB
+
** Replace x-loader with u-boot SPL for serial
+
* Create console or Qt-based helper application to boot BeagleBoard entirely over USB, including loading kernel over DFU or TFTP and NFS-mounting the file system
+
''Possible mentors:'' Jason Kridner, Khasim Syed Mohammed, Steve Sakoman, Dirk Behme, Laine Walker-Avina<br>
+
  
==Display driver improvements==
+
''Goal:'' ArduPilot/APM is a open source autopilot system supporting multi-copters, traditional helicopters, fixed wing aircraft and rovers. The community decided to switch to the BeagleBone Black as their main target thereby the goal of this project will be to support this step, code and test everything to make the BeagleBone the next "platform for aerial devices".<br>
Many people get stuck with the BeagleBoard due to being unable to configure the resolution and timing for their monitor.  Fortunately, the BeagleBoard hardware is quite capable of reading the EDID information from the monitor, enabling the software to  
+
''Existing Project:'' [http://ardupilot.com ArduPilot Website], [https://github.com/diydrones/ardupilot Source Code], [https://github.com/BeaglePilot BeaglePilot on GitHub] <br>
+
''Hardware Skills:'' Interfacing sensors, PPM, PRUSS, some experience RC planes/multicopters<br>
''Goals:''
+
''Software Skills:'' C, C++, Python, Assembly<br>
* Add EDID reading support into the BeagleBoard kernel
+
''Possible Mentors:'' Andrew Tridgell, Kevin Hester, Lorenz Meier, Samy Kamkar <br>
* Add automated resolution configuration
+
''Workload:'' Considering the experience these first months at BeaglePilot we estimate that there's room for 3 students on this project. <br>
* Implement Xrandr for BeagleBoard
+
''eLinux project page:'' http://elinux.org/BeagleBoard/GSoC/BeaglePilot
''Existing project:'' [http://beagleboard.org/project/linux linux-omap]<br>
+
''Software skills:'' C, ARMv7 assembly (desired), Linux kernel driver development, X11 knowledge<br>
+
''Possible mentors:'' <br>
+
  
==JTAG debugging==
+
==Upstreaming Beagleboard.org Kernel Patches==
Implement, configure and document a complete open source based JTAG debugging development chain for ARM Cortex A8 in OMAP3 used on Beagle Board. This includes final port of open source JTAG software [[BeagleBoardOpenOCD|OpenOCD]] for OMAP3 on Beagle, and then configure and document all software (and hardware) components involved. This could look like:
+
The BeagleBone currently relies on a number of out-of-tree kernel patches in order to boot. These patches are maintained by Koen Kooi (CircuitCo) and come from many sources, including TI employees and various mailing lists. Getting more of these patches upstream would make it easier to boot a BeagleBone and also make use of a BeagleBone easier for users and kernel developers who need to track upstream kernel changes, or who otherwise need to be closer to the bleeding edge of Linux kernel development. The current patch set is [https://github.com/beagleboard/kernel/tree/3.8 maintained at github] and contains scripts to easily patch an upstream kernel. The scripts in this repository are used to build the BeagleBoard.org kernels which ship with the Angstrom SD card images.
 +
<br>
  
''ARM Cortex A8 <-> OMAP3 <-> BeagleBoard <-> Flyswatter (*)'' <-> OpenOCD <-> GDB <-> Eclipse (CDT)
+
''Goal:'' Push as many patches as possible to [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git Linus's mainline kernel tree] via the appropriate [http://git.kernel.org/cgit/ staging kernels] for the subsystems involved.<br>
 +
''Existing Project:'' [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git The Mainline Linux Kernel], [http://github.com/beagleboard/kernel/tree/3.8 patches needing to be pushed]<br>
 +
''Hardware Skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals.<br>
 +
''Software Skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation and testing.<br>
 +
''Possible mentors:'' Matt Porter, Matt Ranostay, Koen Kooi, Alan Ott<br>
  
(*) Note: [[BeagleBoardJTAG#TinCanTools_Flyswatter|Flyswatter]] is used as example JTAG dongle here. All OpenOCD JTAG dongles able to deal with 1.8V and configure EMUx pins correctly can be used.
+
==Generic Device Tree Creator==
 +
Device Tree usage can be a steep learning curve for many. Despite N tutorials for it. Kernel version and naming convention changes cause issues.
 +
So how about a tool to create the DT file for the Beaglebone Black.
 +
Select the required options. Need this gpio for pru. Need this adc for tsc. Need this pin.
 +
And it generated DT bindings for you.
  
''Goal:'' Able to single step kernel code using OpenOCD, GDB, and Eclipse<br>
+
Ideally it should effectively expand for other embedded development kits. If you load a Beaglebone Black Rev C file. The DT bindings for that are generated.
''Existing project:'' [http://beagleboard.org/project/OpenOCD+OMAP3+JTAG+support/ OpenOCD]<br>
+
If you load a Beaglebone White Rev A file, DT bindings for that are generated etc..
''Hardware skills:'' Able to monitor logic-level digital signals<br>
+
Similarly, kernel version changes should be easy to incorporate as well.
''Software skills:'' C, ARMv7 assembly<br>
+
''Possible mentors:'' Dirk Behme, Laine Walker-Avina <br>
+
  
'''NOTE: [http://www.tincantools.com TinCanTools] will donate [[Flyswatter]] boards for this project
+
Getting the whole thing as part of GSoC can get too much unless you are really skilled. So a basic structure should be the aim initially.  
'''
+
Suggestions for the base platform running the tool are welcome. e.g. A webapp/bonescript can be used. Python perhaps.
  
=Multimedia and user experience projects=
+
''Goal:'' Get a basic device tree creator for BBB (and possibly BBW) working with a structure to allow different board types<br>
 +
''Existing Project:'' https://github.com/jluebbe/tools is a small bit of a starting point. <br>
 +
''Hardware Skills:'' Should be able to understand the capes <br>
 +
''Software Skills:'' Cross-compile the Linux kernel and testing the DT.<br>
 +
''Possible mentors:'' Jason Kridner<br>
  
==Add DSP support to VLC==
 
  
''Possible mentors:'' Vladimir Pantelic<br>
+
==IIO debugging tools==
 +
Quick background: IIO is the new way of doing sensors but being a newer interface, it lacks tools
 +
for debugging. This project is to produce sometools to debug drivers.
 +
There are several ways this project can happen:<br>
 +
1. We can implement userland tools that read IIO data similar to the evtest tool. <br>
 +
2. We can implement a event handler for the IIO driver. This way existing tools and code can be used. There was references from another mailing list (probally LKML) talking about this.<br>
  
==Add DSP support to MPlayer==
+
''Goal:'' Userspace application similar to evtest that captures debug events and instrumented IIO driver code to produce those events.<br>
MPlayer is often used to play video on the Beagleboard and a lot of users are asking for it. Most are surprised that there is no DSP support (yet). Task to be performed would be to add DSP support to MPlayer using TI DSPLink and CodecEngine and the free DSP codecs that TI provides. CE support already exists in a branch of VLC, the task is to make that also work in MPlayer and do that in a memory efficient way (0-copy between ARM and DSP components)
+
''Existing Project:'' [http://github.com/beagleboard/kernel/tree/3.8 patched kernel with IIO driver]<br>
 +
''Hardware Skills:'' None.<br>
 +
''Software Skills:''C coding (1), (2) requires kernel coding<br>
 +
''Possible mentors:'' Hunyue Yau<br>
  
''Goal:'' Able to play video in MPlayer using DSP codecs<br>
+
==node-webkit based cross-platform getting-started app==
''Existing project:'' http://www.mplayerhq.hu/<br>
+
Newbies often have a difficult time following directions that could be replaced by an application. The steps to download and install an application is something that even newbies can typically manage. This avoid issues like having bad browsers or not having typical development tools like 'ssh'. This is a common problem across all embedded Linux platforms and node-webkit provides a good solution for making it cross-platform.
''Existing project:'' http://processors.wiki.ti.com/index.php/Codec_Engine_Overview<br>
+
''Software skills:'' C<br>
+
''Possible mentors:'' Vladimir Pantelic<br>
+
  
==DSP accelerated color conversion==
+
''Features'':
Multimedia on the Beagleboard can already make use of the DSP, yet there are still steps like color conversion that can take a lot of CPU resources (e.g. in gstreamer). Task to be performed is to move some of that processing to the DSP side where possible, preferably to run in parallel with ARM side processing. C6Accel could be used as the framework to run parts of the SW on the DSP.
+
* Provide instructions for getting up-and-running with the board based (incorporate the Getting Started Guide)
 +
* Automatically discover boards on the LAN using mDNS and predetermined IP addresses
 +
* Act as a browser to interact with the board, including performing SSH and SCP
 +
* Discover the latest SD card images from multiple distributions
 +
* Bootload the board with a USB-mass-storage-class application
 +
* Program SD cards through the board or a USB adapter
 +
* Program on-board eMMC
  
''Goal:'' Able to do e.g. DSP color conversion in a gstreamer pipeline or in FFmpeg/Mplayer<br>
+
''Goal:'' Provide a downloadable application for Linux, Windows and Mac that enables unexperienced users to get going enough to start learning about using Linux and the embedded I/O.<br>
''Existing project:'' http://www.mplayerhq.hu/<br>
+
''Existing Project:'' [http://github.com/jadonk/beaglebone-getting-started/tree/node-webkit-app Incomplete node webkit app for the BeagleBone Getting Started guide]<br>
''Existing project:'' http://www.FFmpeg.org/<br>
+
''Hardware Skills:'' N/A<br>
''Existing project:'' https://gstreamer.ti.com/gf/project/gstreamer_ti/<br>
+
''Software Skills:'' Able to write software in JavaScript and work with node.js modules<br>
''Existing project:'' http://processors.wiki.ti.com/index.php/C6Accel<br>
+
''Possible mentors:'' Jason Kridner<br>
''Software skills:'' C<br>
+
''Possible mentors:'' Diego Dompe<br>
+
  
==DSP accelerated USB webcam gadget==
+
==BoneScript web pages with live-running examples and documentation==
The Linux USB stack now has a webcam gadget, this means a Beagleboard with a connected camera can act as an USB webcam towards a host PC. Using CodecEngine and the TI DSP codecs, the webcam gadget could use the DSP to more efficiently stream already compressed video data to the host PC.  
+
{{#ev:youtube|VP0DOheLxQA||right|5 JavaScript Tricks for BeagleBone}}
 +
The BoneScript JavaScript library enables hardware control from web pages using socket.io for remote procedure calls. This provides an excellent environment for teaching how to wire-up sensors and controls and rapidly prototype user interfaces. Numerous examples exist on the web, but consolidation and testing are required to make them usable by novices. Examples include interfacing with potentiometers, light sensors, temperature sensors, motors and LED arrays then visualizing/controlling with Twitter, Facebook, jQuery, Spacebrew and dweet,io.
  
''Goal:'' Able to stream encoded (MJPG/H264) video data to the host using the USB webcam gadget<br>
+
''Goal:'' About 25 web pages with executable script that demonstrate how to connect up sensor and actuator hardware integrated into the bone101 repository and shared on http://beagleboard.org/Support/BoneScript<br>
''Existing project:'' https://patchwork.kernel.org/patch/48487/<br>
+
''Existing Projects:'' [http://makezine.com/2014/01/14/5-easy-javascript-tricks-you-can-teach-your-beaglebone/ 5 easy tricks presentation], http://beagleboard.org/Support/BoneScript, https://github.com/jadonk/bone101, [https://github.com/jadonk/beaglebone-getting-started/blob/add-bone101/Docs/demo_bmp085.html BMP085 Bonescript example], [http://elinux.org/Category:ECE497 ECE497 examples], [http://jsfiddle.net/gh/gist/jquery/1.9.1/9602198/ JSFiddle on GIST example]<br>
''Existing project:'' http://processors.wiki.ti.com/index.php/Codec_Engine_Overview<br>
+
''Hardware Skills:'' Basic knowledge of digital circuits.<br>
''Software skills:'' C<br>
+
''Software Skills:'' JavaScript and some familiarity with Linux<br>
''Possible mentors:'' ???<br>
+
''Possible mentors:'' Jason Kridner<br>
  
==Speech recognition==
+
==Integrate support libraries into Debian==
TI has released [https://gforge.ti.com/gf/project/tiesr/ source for a speech recognition library] that runs on the ARM processor of the OMAP3 on the BeagleBoard. This software has now a LGPL  v2.1 license.  Using speech recognition library, several tasks could be performed:
+
Many BeagleBone and embedded Linux support libraries in various programming languages exist as projects that aren't included in the distro shipped with BeagleBoard and BeagleBone. These need packaging scripts such that they can be easily downloaded and incorporated into the upcoming shipping Debian distro.
* Voice recognition integrated into Ubiquity: Integrate Mozilla Firefox, Mozilla Ubiquity, and voice recognition on the BeagleBoard with a microphone.  Use of a Wiimote could provide additional interactive capabilities.
+
  
Creating a gstreamer plugin for the library would improve the ability of other applications to use it.
+
* Python PyBBIO
 +
* Ruby beaglebone-ruby
 +
* Perl bonelib
  
''Existing project:'' http://beagleboard.org/project/tiesr<br>
+
''Goal:'' PyBBIO, beaglebone-ruby and bonelib included in the distro shipping with BeagleBone<br>
''Possible mentors:'' Lorin Netsch, Sourabh Ravindran, Diego Dompe (if done with gstreamer)<br>
+
''Existing Project:'' [https://github.com/alexanderhiam/PyBBIO PyBBIO], [https://github.com/ryanfaerman/beaglebone-ruby beaglebone-ruby], [http://sourceforge.net/p/bonelib/wiki/Home/ bonelib]<br>
 +
''Hardware Skills:'' Able to wire up simple hardware, like LEDs<br>
 +
''Software Skills:'' Familiarity with Python, Ruby, Perl, embedded Linux and build systems.<br>
 +
''Possible mentors:'' Jason Kridner, Robert Nelson, Rob Rittman<br>
  
==Add DSP support to GNU radio==
+
==SYSFS entries for IIO and PWM==
''Goal:'' GNU Radio is a popular Software Defined Radio package for PC based computers. GNU Radio also runs on the Beagleboard and can make use of the floating point unit on the ARM. However, the DSP on the Beagleboard has tremendous potential for increasing GNU Radio's capability on small hardware. The project difficulty is based on the level of effort desired by the student, it should be fairly easy to create a standalone GNU Radio block that talks to the DSP via dsplink, or very complex to modify the GNU Radio block scheduler to launch block on the DSP directly.<br>
+
IIO and PWM provide mechanisms for sampling touch screens, performing general purpose A/D conversions to read sensors, generating voltage levels and driving motors. The Linux kernel SYSFS mechanism provides a simplified mechanism for userspace applications to set parameters and read/write data values.
''Existing project:'' [http://gnuradio.org GNURadio]<br>
+
''Software skills:'' C++<br>
+
''Mentors:'' Philip Balister<br>
+
  
==Optimize OpenCV with C6Accel==
+
''Goal:'' Push patches to Linux mainline providing SYSFS entries for IIO and PWM useful for building a demo robot<br>
 +
''Existing project:'' http://github.com/beagleboard/kernel<br>
 +
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 +
''Software skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation<br>
 +
''Possible mentors:'' Laine Walker-Avina<br>
  
''Possible mentors:'' Leo Estavez, Gagan Maur<br>
+
==Using BeagleBone PRUs to control CNC and 3D printer stepper motor Drivers==
 +
This project is to write code for the PRU (realtime processors on the AM335x used in the Beagle Bone) so that it can generate multiple step and direction outputs based on a queue of commands in real time. This needs to be done in real time so the acceleration and coordination of multiple stepper motors can be controlled and coordinated. A step/dir signal is commonly used in a lot of stepper motor drivers. While it is possible to generate stepper phase information from the PRU, it is also undesireable from a testing stand point. An example of a reason for doing this is controlling the X/Y directions of the head of a 3D printer so that it can generate precise curves. While similar code has been done, it is not done in a real time fashion so it is difficult to add coordination between motors and/or maintain a known acceleration.<p>
  
=Hardware + software projects=
+
The result of this code should be something interfaceable to a control system like the non realtime portions of the Linux CNC project (formerly the EMC project). But as a demo, this same code should also demonstrate a node.js functionality such as a "G-code" interpreter. This node.js portion can be considered a second project due to the different skill sets required and ideally this project would be split between two GSoC students. One project would be working mostly on PRU assembly with integration into the Linux kernel. The other project would be working mostly on userspace JavaScript in node.js and C++ code for anything needing optimization or low-level kernel access. Mentors would heavily assist on defining the right interfaces between the two programming environments.
These are "Make"-style projects that advance general knowledge for creating and improving end products for consumers. These projects should need to generate code, not just documentation, and the hardware steps should be reasonably simple to reproduce.
+
  
==Create JavaScript tutorial for hardware control==
+
''Goal'': create code to use the AM335x PRUs to generate multiple step and direction outputs for reprap and CNC applications<br>
Create a live-editable tutorial written in HTML and JavaScript to explore I/O (GPIO, I2C, SPI, USB, etc.) using the Linux kernel. The Node.JS JavaScript interpreter enables you to use your
+
''Existing projects'': [http://github.com/beagleboard/am335x_pru_package Pru Documentation], [https://www.kernel.org/doc/htmldocs/uio-howto.html UIO Driver documentation]<br>
 +
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 +
''Software skills:'' Assembly and C coding. Node.js for g-code interpretation<br>
 +
''Possible mentors:''Jason Kridner, Hunyue Yau, Laine Walker-Avina<br>
  
''Existing project:'' [http://blog.hangerhead.com/2011/03/nodejs-based-cloud9-javascript-ide.html Node.JS-based Cloud9 IDE running on a BeagleBoard]<br>
+
==PRU upstreaming==
''Existing project:'' [http://gitorious.org/beagleboard-validation/education HTML and JavaScript slideshow Education application to hold the tutorial]<br>
+
Remove HWMOD dependency requirement for PRU along with adding device tree bindings so it can be upstreamed into Linus's tree.
''Existing project:'' [https://gforge.ti.com/gf/project/matrix_gui/ Matrix GUI]<br>
+
''Goals:''
+
* Bundle Cloud9 into an Angstrom recipe for easy installation
+
* Bundle the Education application into an Angstrom recipe as well
+
* Create server-side library for GPIO that probes the kernel to discover the GPIO pins
+
* Create browser-side library for exposing GPIOs and events in the browser upon GPIO interrupt events
+
* Create libraries for I2C
+
* Create libraries for SPI
+
* Create libraries for USB HID host
+
* Create libraries for USB GadgetFS and HID client
+
* Modify Matrix to provide local hosting of the Education application
+
''Possible mentor:'' Jason Kridner<br>
+
  
==BeagleWall + Kinect==
+
''Goal'': Push patches to Linux mainline providing support for the AM335x PRU<br>
Update the software utilized by the BeagleWall to create a screen-less green screen effect where foreground objects are superimposed on the video being played. A threshold on the depth channel would be turned into a alpha channel to enable overlay.
+
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br>
 +
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 +
''Software skills:'' Able to write software in C, understand existing patches with PRU support, create patches to the Linux kernel and perform cross-compilation<br>
 +
''Possible mentors:'' Start with Jason Kridner and Matt Porter, but we'll get some others involved<br>
  
''Existing project:'' omapfbplay<br>
+
==PRU firmware loader==
''Existing project:'' libfreenect<br>
+
Allow "firmware" which are really binary PRU applications to be loaded directly on PRU cores and executed using the request_firmware() functionality of the Linux Kernel. This should also be  Cape Manager to load PRU cape specific applications.
''Possible mentor:'' Mans, whatnick, Mark Yoder<br>
+
  
==Beagleboard Hardware Control Library==
+
Ideal workflow:
Create a user space library that makes using hardware connected to the Beagleboard expansion connectors easier to use. This includes functions to control GPIO pins (and trigger on GPIO Interrupts) and to send and receive data over I2C and SPI. All this should be well documented so that a new Beagleboard user can learn quickly how to control and interact with attached hardware.
+
  
''Goal:'' provide a library to interface with GPIO, I2C and SPI on the Beagleboard <br>
+
* Cape detected that uses the PRU
''Hardware skills:'' basic<br>
+
** Setup pinmux
''Software skills:'' C<br>
+
* Find the respective firmware file for PRU core (or both cores) /lib/firmware/cape_A020_pru0.bin
''Possible mentor:'' ???
+
* Load onto PRU and begin execution.
  
==Adding Sense to Beagle==
+
''Goal'': Push patches to Linux mainline providing support to loading firmware on PRU cores and executing<br>
Sensory aware applications are becoming more mainstream with the release of the Apple iPhone. This project would combine both HW and SW to add sensory awareness to beagle.  First, additional modules such as GPS, 3-axis accelerometers, Gyroscopes, Temperature Sensors, Humidity Sensors, Pressure Sensors, etc, would be added to beagle to compliment the microphone input in order to allow sensing of the real world environment.  Then SW APIs would need to be layered on top to allow easy access to the sensory data for use by applications. 
+
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br>
 +
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 +
''Software skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation<br>
 +
''Possible mentors:'' Matt Ranostay, Matt Porter<br>
  
The Freespace module is already working with the BeagleBoard as are many other sensors.  This project should seek to summarize how to connect as many sensors as possible on one place on the eLinux wiki.
+
==Program PRU using high-level scripting lanugages==
 +
Based on Chris Roger's BotSpeak work to provide a virtual machine for typical Arduino functions that can be accessed from LabView, build a virtual machine to enable PRU programming from Bonescript. The virtual machine is a simple interpreter that loops over the commands to perform such as delay, pinMode, analogRead, analogWrite, digitalRead and digitalWrite functions.
  
''Possible mentor:'' Mark Yoder
+
A basic design is elaborated upon at http://github.com/jadonk/pruduino
  
==CarPC API and implementation==
+
''Goal'': Implement a BotSpeak interpreter that off-loads hard real-time tasks from Bonescript onto the PRU and include that in the BoneScript project<br>
Creating a set of APIs and libraries allowing for rapid deployment of flexible modular CarPC environments. The project is about creating toolkit for the enthusiasts easying the creation of beagleboard-based customized carputers, covering the hardware interaction and providing an object-oriented interface to both rich input data (GPS data, maps, OBD and similar buses, voice control, cameras, internet data on traffic, variety of HID input sources, et cetera) and different output options randing from a trivial alphanumeric LCD panel to multiple displays with personal audio jacks. Ideally, this would drastically lower the entry barrier into carputer programming drawing more developpers in and abstracting them from hardware implementation, in the same time allowing the freedom of component choices which would promote DIY carputer asssembly. The code should as well be as compatible as possible with existing Linux CarPC projects(LinuxICE) and new idustry initiative GenIVI (which aims at using MeeGo).
+
''Existing projects'': [http://github.com/jadonk/pruduino PRUDUINO], http://github.com/beagleboard/am335x_pru_package, http://github.com/jadonk/bonescript, [https://sites.google.com/site/botspeak/the-language Chris' language definition]<br>
 +
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 +
''Software skills:'' Able to write software in JavaScript and assembly<br>
 +
''Possible mentors:'' Chris Rogers, Jason Kridner<br>
  
=Community infrastructure projects=
+
==Android-based remote display==
==Updating BeagleBoard.org UI/backend==
+
Use your Android phone as a remote display and control unit for you BeagleBone. Display your applications UI on the phone screen and use your phone's touchscreen to control your application on the Beaglebone.
The BeagleBoard.org website is currently written in JavaScript using Helma and makes use of several Java components through JavaScript.  One advantage of this is you can actually run an instance of the BeagleBoard.org web server on the BeagleBoard with a full clone of the website.
+
* Move existing content from from Helma to RingoJS or Node.JS
+
* Improve OpenID support
+
* Create Ubiquity scripts to simplify page editing
+
* Add tags to project entries and improve the views
+
* Import RSS feed items into pages for ranking/tagging
+
* Add microblogging support integrated with the IRC channel
+
** See http://code.google.com/p/beagleboard/issues/detail?id=46
+
** Enable users to store http://beagleboard.org/user user profiles
+
** Have the chat show Twitter and Identica update
+
* Translate BeagleBoard.org into other languages
+
** http://code.google.com/p/beagleboard/issues/detail?id=4
+
* Update the site for the BeagleBoard-xM launch occurring in June
+
  
''Software skills:'' JavaScript, XML, HTML/CSS<br>
+
Since all Android devices are required to support ADK (Accessory Development Kit) mode, a BeagleBone acting as a USB host can talk to an Android phone over USB. An Android application would provide the "remote" screen for the Beaglebone, much like an USB based external display on a PC. At the same time button presses and touchscreen events can be relayed to the Beaglebone as it if had a local keyboard connected
''Mentor:'' Jason Kridner<br>
+
  
=To be classified=
+
Many applications are possible, from a simple shell to aid developing and debugging to a remote X server that hosts GUI apps.
  
==Angstrom Linux and Rowboat Android==
+
If ADK mode can also be achieved in u-boot, it could help to setup and debug the bootloader even before the Linux kernel starts.
Some people want to play Angry Birds or run other Android apps on their BeagleBoard.  Of course, you could use the Rowboat Android project as-is, but then you'd have to give up all of their typical Linux/X11 applications available in Angstrom.  This project would use an Android-enabled kernel and a combination of both an Angstrom and Rowboat Android file system.  The input and display methods required for Android would need to be adjusted to run within an X11 window.
+
  
''Goals'':
+
Further, a part of the Android devices' filesystem could me made accessible to mount on the Beaglebone
* Rowboat running in a window
+
* Provide input method that works in a window
+
* Phase 2: Use adb to invoke apps
+
* Phase 3: Hide window when at the launcher
+
* Phase 4: Enable SGX in the Android
+
* Phase 5: Add Rowboat build into Angstrom (maybe this should go first?)
+
* Phase 6: Start using the user libs from Angstrom (probably futile)
+
  
 +
''Goal:'' Implement a remote display and keyboard for the Beaglebone running on an Android phone or tablet<br>
 +
''Existing Project:'' https://github.com/SpecLad/libusb-android, [https://code.google.com/p/rowboat/wiki/AccessoryDevKit BeagleBone implementation of Android Accessory Development Toolkit]<br>
 +
''Hardware Skills:'' Some knowledge of USB<br>
 +
''Software Skills:'' Java, C and familiarity with Android<br>
 +
''Possible mentors:'' Vladimir Pantelic, Jason Kridner and others<br>
  
==BeagleChat==
 
'''Easy'''
 
Video Chat Client on Beagle Board. Porting Ekiga (www.ekiga.org) - an open source VoIP and video conferencing application for GNOME. The client should be able to talk to ekiga software running on PC as well as another beagle board. Optimizations would involve porting audio and video codecs on Ekiga to DSP plus supporting video streaming over USB for webcam support.
 
  
=Raw ideas that need to be fleshed out=
+
==Cross platform USB boot==
Some additional ideas can be found on the [[BeagleBoard/contest|BeagleBoard contest page]] and the [http://beagleboard.org/project BeagleBoard project page].
+
Boot (and flash) your BeagleBone (Black) from a Windows, Mac or Linux computer without using a microSD card.
  
* RTEMS BSP for Beagle board: '''Medium''' [http://www.rtems.org RTEMS] is a free real-time operating system.  This project would require developing an RTEMS Board Support Package for the Beagle board. The Beagle board has come up multiple times in our community as a excellent device for students, hobbyists, and a starting point for customized boards. I am the maintainer of RTEMS and would be willing to co-mentor this with someone from the Beagle board community. --[[User:JoelSherrill|JoelSherrill]] 23:12, 18 March 2010 (UTC)
+
Extend [https://github.com/ungureanuvladvictor/BeagleDroid last year's GSoC project] to boot from an Android device to support Windows, Mac and Linux hosts.
  
* Spectrum analyzer using the DSP: '''Medium'''  Write a program that uses the DSP to take an alsa input and to all the math and a GUI on the arm that display the realtime spectrum. The DSP side needs to use xdais so other DSP programs can run at the same time.
+
''Goal:'' Download a Linux image from the web and boot a BeagleBone using it over USB<br>
 +
''Existing Project:'' https://github.com/ungureanuvladvictor/BeagleDroid, https://github.com/ungureanuvladvictor/BBBlfs<br>
 +
''Hardware Skills:'' Some knowledge of USB<br>
 +
''Software Skills:'' C and familiarity with Mac, Linux and Windows<br>
 +
''Possible mentors:'' Vladimir Pantelic, Jason Kridner<br>
  
* Porting open-source codec to DSP (MadPlay, VLC, some of the mplayer codecs …: '''Medium'''
+
==Android under Angstrom==
 +
Some people want to play Angry Birds or run other Android apps on their BeagleBoard/BeagleBone.  Of course, you could use the Rowboat Android project as-is, but then you'd have to give up all of their typical Linux/X11 applications available in Angstrom.  This project would use an Android-enabled kernel and a combination of both Angstrom and Android file systems.  The input and display methods required for Android would need to be adjusted to run in on a virtual terminal and chroot/chvt would be used to invoke the various user space windows.
  
* OpenGL DSP acceleration: '''Hard'''  Research and implement OpenGL ES using the DSP on beagleboard. The DSP side needs to use xdais so other DSP programs can run at the same time. Can take a look at Vincent OpenGL ES open source implementation and add DSP to it
+
This has essentially been done once as part of [https://www.alwaysinnovating.com/beagleboard/ Always Innovating's Super-Jumbo] demo running Ubuntu, Angstrom, ChromeOS and Android simultaneously. The fundamental challenge is getting it reproducible and integrated into the OpenEmbedded build system for Angstrom and then starting to minimize the wasted file space by sharing libraries. Eventually, even making Android applications run in a window is desired.
  
* beagle as DLNA/upnp renderer, server, controller, or media player.
+
''Goal'': Run Android applications under Angstrom and toggle back-and-forth using CTRL-ALT-Fn key presses.<br>
 +
''Existing projects'': http://arowboat.org, http://www.angstrom-distribution.org<br>
 +
''Hardware skills:'' Minimal<br>
 +
''Software skills:'' Able to write software in C and Java, experience with X11 and Android<br>
 +
''Possible mentors:'' Hunyue Yau, Vladimir Pantelic<br>
  
* Wiimote + Pico Projector + 3D art tool
+
==Library of Arduino-compatible functions for StarterWare==
 +
This would be an implementation of Arduino utilizing the BeagleBone Black and the StarterWare O/S independent library for accessing the hardware. Without having to access the hardware through an operating system, developers will be able to fine-tune the system to achieve optimal resource management of the CPU, peripherals and memory.
 +
The project would also include basic documentation and generation of code samples for various functionality of the library, such as SPI,Serial,Ethernet for starters. This would make the project thorough and ready for use by various developers in the community.
 +
 +
''Goal:'' Utilize the Energia fork of Arduino to push support for BeagleBone and BeagleBone Black<br>
 +
''Existing Project:'' [https://github.com/energia/Energia Energia], [http://processors.wiki.ti.com/index.php/StarterWare StarterWare]<br>
 +
''Hardware Skills:'' Yes<br>
 +
''Software Skills:'' C/C++<br>
 +
''Possible mentors:'' Jason Kridner (others can be referred if there are interested students)
  
* OpenCL implementation that uses the DSP and/or NEON (could be used as framework for any dsp/neon acceleration)
+
==Documentation for BeagleBone and BeagleBone Black==
 +
'''We need to avoid documentation projects for GSoC. Please turn this into a coding project. Providing code examples might be sufficient, but code needs to be the output. The documentation can be a side-effect.'''
 +
Produce HOWTOs and code samples for use of I/O on BeagleBone to be placed in the neutral elinux.org BeagleBone community pages.
  
* Video extender – take in video via usb webcam, compress it using video encoder, stream it over ethernet (could be like a security camera). Could/should be implemented using DLNA protocols (e.g. view on ps3 or tv's).
+
''Goal:'' The Beagleboard.org community has lacked a canonical source of high quality documentation on how to use peripherals found on AM335x. Peripheral use to be documented will include UARTs, I2C, SPI, PWM, ADC, USB Host/Gadget as well as advanced topics such as software development and optimization for the M3 and PRU coprocessors.<br>
 +
''Existing Project:'' [http://www.elinux.org/BeagleBone_Community elinux.org BeagleBone Community Page]<br>
 +
''Hardware Skills:'' Yes<br>
 +
''Software Skills:'' C<br>
 +
''Possible mentors:'' Hunyue Yau and Matt Porter (others welcome to volunteer)
  
=Mentors=
+
==PyBBIO library development==
 +
PyBBIO is a Python library that aims to provide Arduino-style API for hardware IO support on the Beaglebone and BeagleBone Black. It is meant to make hardware development fast and easy with Python.
  
 +
''Goal:'' Moving portions to C extensions to speed up PyBBIO, as well as adding further peripheral support and internal libraries. Possible things to add support for:
 +
 +
* On-chip peripherals (SPI, CAN, eQEP, GPMC, etc.)
 +
* Radios (XBee, Rn-42, RN-171, etc.)
 +
* Sensors (temp, rh, proximity, gyro, accel, etc.)
 +
* Displays (HD4780, KS0108, Nokia 5110, etc.)
 +
* IoT libraries (Xively, Freeboard, web UI, etc.)
 +
 +
There should also be ample example programs for any new libraries. It would also be good to have a couple larger example projects that do more than just demo API (for example a toaster oven reflow solder controller: https://github.com/alexanderhiam/toasterReflow).
 +
 +
''Existing Project:'' [https://github.com/alexanderhiam/PyBBIO PyBBIO]<br/>
 +
''Hardware Skills:'' Yes<br/>
 +
''Software Skills:'' Python, C, familiar with Python C extensions<br/>
 +
''Possible mentors:'' Alexander Hiam
 +
 +
==MMC and DMA Linux performance ==
 +
Improving performance of MMC driver by understanding issues, improving MMC, DMA drivers and eliminating bottlenecks.
 +
 +
''Goal:''
 +
Both MMC and DMA are critical to high performance of I/O intensive workloads on a Beagleboard/ARM platform, even fast system boot up depends on it.
 +
 +
A good amount of performance improvement is possible just by identifying what's going on in hot paths and how things can be done more simply, without breaking anything else. Also improvements are possible using innovative techniques such as intelligent buffer allocation and reducing overhead where possible in dependent components such as DMA. Cutting the fat in hot paths is definitely a start.
 +
 +
''Existing Project:'' [http://kernel.org Upstream Kernel]<br/>
 +
''Hardware Skills:'' Yes<br/>
 +
''Software Skills:'' C, Possible use of JTAG, ftrace, perf etc.<br/>
 +
''Possible mentors:'' Joel Fernandes
 +
 +
==Implementing and testing core libraries in Userspace Arduino==
 +
Implementing and testing core libraries in Userspace Arduino, especially SPI, I2C, Wire, Serial, Servo, Stepper
 +
 +
This would primarily target the Arduino Tre.
 +
 +
==Making a stable release of Processing's serial libraries for Tre==
 +
 +
==Making a stable release of OpenFrameworks's serial libraries for Tre==
 +
 +
==Previous ideas==
 +
* [[BeagleBoard/GSoC/Ideas-2013]]
 +
* [[BeagleBoard/GSoC/Ideas-2012]]
 +
 +
=Mentors=
 
{| border="1"
 
{| border="1"
 
! Name
 
! Name
 
! IRC nickname
 
! IRC nickname
 +
! Melange name
 
! Native language
 
! Native language
 
! Other languages
 
! Other languages
Line 266: Line 331:
 
|-
 
|-
 
| Jason Kridner
 
| Jason Kridner
 +
| jkridner
 
| jkridner
 
| jkridner
 
| English
 
| English
 
| -
 
| -
| US Central
+
| US Eastern
| web development, C, shell/perl scripting
+
| JavaScript, C, u-boot
 
| wiring, timing diagrams, basic debug
 
| wiring, timing diagrams, basic debug
| infrastructure improvements
+
| BoneScript development
 
|-
 
|-
| Leo Estevez
+
| Vladimir Pantelic
| TBD
+
| av500
| Spanish
+
| vp7
| English, French, German(basic)
+
| German
| US Central
+
| English, Serbian
| C, mobile operating systems
+
| CET
| wiring, timing diagrams, basic debug
+
| Experienced on most areas of Embedded Linux, Multimedia
| computer vision
+
| Schematic Review + Design
 +
| Embedded Linux, Linux Multimedia, Android
 +
|-
 +
| Matt Ranostay
 +
| mranostay
 +
| mranostay
 +
| English (U.S. Midwestern Dialect)
 +
| None
 +
| US Pacific Time
 +
| Experienced on most areas of Embedded Linux or Systems
 +
| Schematic Review + Design
 +
| ARM/AM335x Kernel Development
 +
|-
 +
| Matt Porter
 +
| mdp
 +
| -
 +
| English (U.S. Midwestern Dialect)
 +
| None
 +
| US Eastern
 +
| Embedded Linux Firmware/Kernel and system level design. Designing Linux drivers to make the best use of existing infrastructure.
 +
| Schematic Review + Design
 +
| ARM/AM335x/OMAP/PRU U-Boot and Kernel/Driver Development
 
|-
 
|-
 
| Hunyue Yau
 
| Hunyue Yau
 
| ds2
 
| ds2
 +
| hygsoc
 
| English
 
| English
|
+
| -
 
| US Pacific
 
| US Pacific
 
| Android, C, Linux, scripting
 
| Android, C, Linux, scripting
 
| Yes
 
| Yes
 +
| -
 
|-
 
|-
| Frans Meulenbroeks
+
| Tom Rini
| eFfeM
+
| Tartarus
| Dutch
+
| trini
| English, basic understanding of German
+
| CET
+
| C, User Interface, Linux, booting, performance improvement, networking technology
+
| no
+
|-
+
| Kevin Hilman
+
| khilman
+
 
| English
 
| English
| fluent in French
+
| -
| US Pacific
+
| US Eastern
 +
| C, u-boot, OpenEmbedded
 +
| -
 +
| U-Boot or OpenEmbedded development
 
|-
 
|-
 
| Luis Gustavo Lira
 
| Luis Gustavo Lira
|
+
| lglira
 +
| lglira
 
| Spanish
 
| Spanish
| fluent in English and French)
+
| English
 +
| GMT/UTC -5
 +
| Embedded Linux, C, Android
 +
| Design, Debug, Wiring
 +
| Projects on the BeagleBone
 
|-
 
|-
| Koen Kooi
+
| Frans Meulenbroeks
| _koen_
+
| eFfeM
 +
| effem
 
| Dutch
 
| Dutch
| Fluent in English
+
| English
 
| CET
 
| CET
| Buildsystem integration, distribution
+
| Linux (including drivers), U-Boot, C, Documentation; Coding Style, QA
| not really
+
| device interfacing (for drivers), review FPGA code
|  
+
| -
 
|-
 
|-
| Katie Roberts-Hoffman
+
| Pantelis Antoniou
| katier
+
| panto
 +
| panto
 +
| Greek
 
| English
 
| English
| nope
+
| GMT+2
| US Central
+
| Linux Kernel, S/W Architecture
| Android, DSP integration (Link/CE/etc)
+
| -
| nope
+
| Embedded Linux architecture fixes
 
|-
 
|-
| Mans Rullgard
+
| Andrew Tridgell
| mru
+
| tridge
| English, Swedish
+
| andrewtridgell
| Some German
+
| GMT
+
| C, Assembler
+
|
+
|
+
|-
+
| Mike Zucchi
+
| notzed
+
 
| English
 
| English
|
 
| Australia/South
 
| C, Assembly, Java, SIMD.  Applications, libraries, GUI, multi-threading.
 
| not much
 
 
|  
 
|  
 +
| GMT+11
 +
| Linux Kernel, C, C++, python
 +
| -
 +
| BeaglePilot
 
|-
 
|-
| Philip Balister
+
| Kevin Hester
| Crofton
+
| kevinh /kevinh_
|-
+
| geeksville
| Robert Nelson
+
| rcn-ee
+
 
| English
 
| English
 +
|
 +
| GMT-8
 +
| Linux embedded, C, C++
 
| -
 
| -
| US Central
+
| BeaglePilot
| C, Shell Scripting, Deb packaging
+
|
+
|
+
 
|-
 
|-
| Soren Steen Christensen
+
| Lorenz Meier
| soren.ssc
+
| LorenzMeier
| Danish
+
| lomeier
| Fluent in English and some German
+
| CET
+
| C/C++, ASM, Device Drivers
+
| OMAP chip, HW design, Low level development & debuging
+
| All kind of HW and low level SW stuff
+
|-
+
| Mark Yoder
+
| yoder
+
|
+
|-
+
| Jeff Osier-Mixon
+
| jefro
+
| English (US)
+
|
+
| US Pacific
+
|
+
|
+
| documentation
+
|-
+
| Laine Walker-Avina
+
| Ceriand
+
 
| English
 
| English
 
|  
 
|  
| US Pacific
+
| GMT+1
| C, Assembly, Buildroot
+
| mobile localization, 3D reconstruction on smartphones and micro air vehicles
| USB protocol & logic analyzers, Various JTAG probes
+
| -
| OpenOCD, bootloaders, Linux kernel
+
| BeaglePilot
 
|-
 
|-
| Frank Walzer
+
| Alexander Hiam
| franktango
+
| alexanderhiam
| German
+
| alexanderhiam
 
| English
 
| English
| CET
+
| -
| C++, OOP
+
| US Eastern
| Debug, JTAG, Interfaces
+
| Python, C, Linux Kernel
| Graphics, GUI, Build systems
+
| Prototyping, design, layout, debugging
 +
| PyBBIO
 
|-
 
|-
| Khasim Syed Mohammed
+
| Samy Kamkar
| khasim
+
| samy/samy_
 +
| -
 
| English
 
| English
| Hindi
+
| -
| India
+
| US Eastern
| C, C++, Assembly, Linux device drivers, board bring up, bootloaders
+
| Python, C, Linux Kernel
| Schematic review, board development
+
| Privacy and security researcher, computer hacker, whistleblower and entrepreneur
 +
| BeaglePilot
 
|-
 
|-
| Siji Sunny
+
| Joel Fernandes
| siji
+
| joel_
 +
| joelagnel
 
| English
 
| English
| Hindi
+
| -
| India
+
| US Central
| C,Operating Systems(Ubuntu-Arm,Angstrom,Android,Debian),Open Source Application/GUI Development(Clutter,GTK),RF Programming,Language Computing,Text processing,Unicode,Fonts
+
| C, Linux Kernel, Python
| No
+
| Processor Engineer, Embedded systems Architecture
| Language Computing, Text Processing, Operating System, Text To speech ,GUI,Build Systems
+
| Linux kernel improvement (perf and functionality)
 
|-
 
|-
| Devaraj Rangasamy
+
| Greg Kroah-Hartman
| Deva
+
| gregkh
| Hindi, Tamil
+
| gregh
| English
+
| India
+
| Android, Linux Kernel Base Port
+
| No
+
| Language Computing, Text Processing, Operating System, Text To speech
+
 
|-
 
|-
| Joel Sherrill
+
| David Scheltema
| DrJoel
+
| dschelt
| English
+
| dcschelt
| -
+
|-
| US Central
+
| Charles Steinkuehler
| RTEMS maintainer, real-time, cross tools
+
|
| No
+
| cdstienkuehler
| RTEMS BSP
+
 
|-
 
|-
| Diego Dompe
+
| Steve French
| ddompe
+
| VoltVisionFrenchy
| spanish
+
| voltvisionfrenchy
| english
+
| GMT -6.00
+
| Expert on most areas of embedded development, Gstreamer, GUI, DSP development
+
| No
+
| GStreamer
+
 
|}
 
|}
 +
[[BeagleBoard/GSoC/Ideas-2012#Mentors|Previous mentors]]

Latest revision as of 10:10, 22 April 2014


Welcome!

BeagleBoard.org hopes to be accepted as a mentoring organization in the Google Summer of Code for 2014! Below, we've collected project ideas for the GSoC-2014.

Background

BeagleBoard.org is a volunteer organization that seeks to advance the state of open-source software on open-source hardware platforms capable of running high-level languages and operating systems (primarily Linux) in embedded environments. Born from taking mobile phone processors and putting them on low-cost boards to build affordable desktop computers, BeagleBoard.org has evolved to focus on the needs of the "maker" community with greater focus on the I/O needed for controlling motors and reading sensors to build things like robots, 3d printers, flying drones, in-car computer systems and much more. Past BeagleBoard.org GSoC projects included an RPC framework for heterogeneous processor communication, a transparent USB packet sniffer, ARM optimizations for XBMC, ARM optimizations for FFTs, make-shift pulse-width-modulation and RPC optimizations for OpenCV. BeagleBoard.org has benefited from sponsorship from Texas Instruments, CircuitCo, Digi-Key and others, but avoids any dependence on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 100,000 boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, Debian, ArchLinux, Gentoo, Buildroot and many more.

BeagleBoard was inspiration for Raspberry Pi[1] and is available for only $45 through over 30 distributors world-wide (and is even available at Microcenter and Radio Shack in the USA), but is more than a throw-away computer. It is an instance of true open hardware, exposing users to the broader world of electronics, demystifying computers and fostering an environment of clones that have changed the industry for good.

Students will be expected to demonstrate an understanding of cross-compiling before being accepted, but support for demonstration is available through the IRC channel that typically has approximately 150 online chatters logged on at any time, most with sufficient experience to explain the process.

Every accepted student will be sent a BeagleBone Black before the first week of coding for testing their project.

Additional hardware will be provided depending on need and value.

For more information, check out http://beagleboard.org and http://beagleboard.org/brief.

Students looking for ideas

Student proposals can encompass projects inspired from the following list of ideas or can include personal project ideas. Previous Google Summer of Code projects show that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even if it is not on this list. We will be glad to help students develop ideas into projects via the BeagleBoard IRC or the BeagleBoard mailing list. There are many potential project ideas and we will match students to projects based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.

There are more than 300 existing projects listed at http://beagleboard.org/project. If you are interested in any of the projects listed on the BeagleBoard.org projects page, contact the project members to see if there are any aspects of their projects that can be enhanced to create a GSoC project. There are also several ideas on theECE497 class project idea list. You can also check out last year's idea page.

Mentors wondering where to help

Please start by registering your ideas for student projects below by following the template provided with the existing ideas. Furthermore, scroll down to the bottom and give everyone a bit of information about your expertise and availability by adding yourself to the table. Jason will make final approvals for mentor assignments based on if we first get accepted as a mentoring organization and best matching mentor skill sets with student project ideas deemed valuable to the community.

You will also need to register on Melange and request to be a mentor for BeagleBoard.org.

General requirements

All projects have the following basic requirements:

  1. Once accepted, the project must be registered on http://beagleboard.org/project.
  2. All newly generated materials must be released under an open source license.
  3. Individual students shall retain copyright on their works.
  4. Source code generated during the project must be released on github.com (to be cloned to github.com/beagleboard on successful completion).
  5. The registration on http://beagleboard.org/project must include an RSS feed with project announcements and updates at every milestone. Sources for the RSS feed should be blogger.com, wordpress.com, or some other established blog-hosting service with known reliability.
  6. To help you to break your project down into manageable chunks and also to help the project's mentors to better support your efforts, weekly project status reports should be e-mailed to the project's mentors and the organization administrator (Jason Kridner). Each status report should outline:
    1. what was accomplished that week,
    2. any issues that prevented that week's goals from being completed and
    3. your goals for the next week.
  7. Students will provide two recorded audio/video presentations uploaded to youtube or vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments. Examples can be found on http://beagleboard.org/gsoc.
  8. Students will demonstrate their ability to cross-compile and utilize version control software by creating a "Hello World" application and generating a pull request to https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner. For assistance, please visit http://beagleboard.org/chat or utilize the beagleboard-gsoc Google Group. The "Hello World" application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
  9. All projects will produce reusable software components and will not be "what–I-built-over-my-summer-vacation" projects. Including a hardware component is welcome, but the project *deliverable* will be software that may be utilized by a wide audience of the BeagleBoard.org community.

Ideas

There are several areas needing contributions:
Kernel: Improving the state of the Linux kernel including improved ARM/OMAP/Sitara platform support, simplifying the development of add-on hardware for embedded systems and exchanging hardware connectivity information with userspace.
Secondary processor support (RPC/gcc/etc.): Enabling usage of DSPs, PRUs, FPGAs, Cortex-M3s, Arduinos, MSP430 launchpads and other attached processing platforms.
Scripting libraries and web interfaces: Improving the Bonescript JavaScript library, web-based interface libraries, examples or alternatives in other languages.
Frameworks for open-hardware projects: Consolidating support for simplified home manufacturing (CNC, 3D printers, laser cutters, pick-and-place machines, etc.), drones/bots (ROS, IMU, video streaming, etc.) or other common tasks.
Optimizations to existing userspace applications/libraries: Optimizations to applications and libraries like XBMC to make them run better on resource constrained environments or to take advantage of more specialized processing elements.

BeaglePilot

Porting ArduPilot to BeagleBone Black. Some of the tasks include:

  • PRU drivers (PWM and PPM)
  • SPI drivers for cape sensors
  • RC Input (PPM)
  • Power handling
  • Analog sensing
  • Flight tests

Goal: ArduPilot/APM is a open source autopilot system supporting multi-copters, traditional helicopters, fixed wing aircraft and rovers. The community decided to switch to the BeagleBone Black as their main target thereby the goal of this project will be to support this step, code and test everything to make the BeagleBone the next "platform for aerial devices".
Existing Project: ArduPilot Website, Source Code, BeaglePilot on GitHub
Hardware Skills: Interfacing sensors, PPM, PRUSS, some experience RC planes/multicopters
Software Skills: C, C++, Python, Assembly
Possible Mentors: Andrew Tridgell, Kevin Hester, Lorenz Meier, Samy Kamkar
Workload: Considering the experience these first months at BeaglePilot we estimate that there's room for 3 students on this project.
eLinux project page: http://elinux.org/BeagleBoard/GSoC/BeaglePilot

Upstreaming Beagleboard.org Kernel Patches

The BeagleBone currently relies on a number of out-of-tree kernel patches in order to boot. These patches are maintained by Koen Kooi (CircuitCo) and come from many sources, including TI employees and various mailing lists. Getting more of these patches upstream would make it easier to boot a BeagleBone and also make use of a BeagleBone easier for users and kernel developers who need to track upstream kernel changes, or who otherwise need to be closer to the bleeding edge of Linux kernel development. The current patch set is maintained at github and contains scripts to easily patch an upstream kernel. The scripts in this repository are used to build the BeagleBoard.org kernels which ship with the Angstrom SD card images.

Goal: Push as many patches as possible to Linus's mainline kernel tree via the appropriate staging kernels for the subsystems involved.
Existing Project: The Mainline Linux Kernel, patches needing to be pushed
Hardware Skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals.
Software Skills: Able to write software in C, create patches to the Linux kernel and perform cross-compilation and testing.
Possible mentors: Matt Porter, Matt Ranostay, Koen Kooi, Alan Ott

Generic Device Tree Creator

Device Tree usage can be a steep learning curve for many. Despite N tutorials for it. Kernel version and naming convention changes cause issues. So how about a tool to create the DT file for the Beaglebone Black. Select the required options. Need this gpio for pru. Need this adc for tsc. Need this pin. And it generated DT bindings for you.

Ideally it should effectively expand for other embedded development kits. If you load a Beaglebone Black Rev C file. The DT bindings for that are generated. If you load a Beaglebone White Rev A file, DT bindings for that are generated etc.. Similarly, kernel version changes should be easy to incorporate as well.

Getting the whole thing as part of GSoC can get too much unless you are really skilled. So a basic structure should be the aim initially. Suggestions for the base platform running the tool are welcome. e.g. A webapp/bonescript can be used. Python perhaps.

Goal: Get a basic device tree creator for BBB (and possibly BBW) working with a structure to allow different board types
Existing Project: https://github.com/jluebbe/tools is a small bit of a starting point.
Hardware Skills: Should be able to understand the capes
Software Skills: Cross-compile the Linux kernel and testing the DT.
Possible mentors: Jason Kridner


IIO debugging tools

Quick background: IIO is the new way of doing sensors but being a newer interface, it lacks tools for debugging. This project is to produce sometools to debug drivers. There are several ways this project can happen:
1. We can implement userland tools that read IIO data similar to the evtest tool.
2. We can implement a event handler for the IIO driver. This way existing tools and code can be used. There was references from another mailing list (probally LKML) talking about this.

Goal: Userspace application similar to evtest that captures debug events and instrumented IIO driver code to produce those events.
Existing Project: patched kernel with IIO driver
Hardware Skills: None.
Software Skills:C coding (1), (2) requires kernel coding
Possible mentors: Hunyue Yau

node-webkit based cross-platform getting-started app

Newbies often have a difficult time following directions that could be replaced by an application. The steps to download and install an application is something that even newbies can typically manage. This avoid issues like having bad browsers or not having typical development tools like 'ssh'. This is a common problem across all embedded Linux platforms and node-webkit provides a good solution for making it cross-platform.

Features:

  • Provide instructions for getting up-and-running with the board based (incorporate the Getting Started Guide)
  • Automatically discover boards on the LAN using mDNS and predetermined IP addresses
  • Act as a browser to interact with the board, including performing SSH and SCP
  • Discover the latest SD card images from multiple distributions
  • Bootload the board with a USB-mass-storage-class application
  • Program SD cards through the board or a USB adapter
  • Program on-board eMMC

Goal: Provide a downloadable application for Linux, Windows and Mac that enables unexperienced users to get going enough to start learning about using Linux and the embedded I/O.
Existing Project: Incomplete node webkit app for the BeagleBone Getting Started guide
Hardware Skills: N/A
Software Skills: Able to write software in JavaScript and work with node.js modules
Possible mentors: Jason Kridner

BoneScript web pages with live-running examples and documentation

5 JavaScript Tricks for BeagleBone

The BoneScript JavaScript library enables hardware control from web pages using socket.io for remote procedure calls. This provides an excellent environment for teaching how to wire-up sensors and controls and rapidly prototype user interfaces. Numerous examples exist on the web, but consolidation and testing are required to make them usable by novices. Examples include interfacing with potentiometers, light sensors, temperature sensors, motors and LED arrays then visualizing/controlling with Twitter, Facebook, jQuery, Spacebrew and dweet,io.

Goal: About 25 web pages with executable script that demonstrate how to connect up sensor and actuator hardware integrated into the bone101 repository and shared on http://beagleboard.org/Support/BoneScript
Existing Projects: 5 easy tricks presentation, http://beagleboard.org/Support/BoneScript, https://github.com/jadonk/bone101, BMP085 Bonescript example, ECE497 examples, JSFiddle on GIST example
Hardware Skills: Basic knowledge of digital circuits.
Software Skills: JavaScript and some familiarity with Linux
Possible mentors: Jason Kridner

Integrate support libraries into Debian

Many BeagleBone and embedded Linux support libraries in various programming languages exist as projects that aren't included in the distro shipped with BeagleBoard and BeagleBone. These need packaging scripts such that they can be easily downloaded and incorporated into the upcoming shipping Debian distro.

  • Python PyBBIO
  • Ruby beaglebone-ruby
  • Perl bonelib

Goal: PyBBIO, beaglebone-ruby and bonelib included in the distro shipping with BeagleBone
Existing Project: PyBBIO, beaglebone-ruby, bonelib
Hardware Skills: Able to wire up simple hardware, like LEDs
Software Skills: Familiarity with Python, Ruby, Perl, embedded Linux and build systems.
Possible mentors: Jason Kridner, Robert Nelson, Rob Rittman

SYSFS entries for IIO and PWM

IIO and PWM provide mechanisms for sampling touch screens, performing general purpose A/D conversions to read sensors, generating voltage levels and driving motors. The Linux kernel SYSFS mechanism provides a simplified mechanism for userspace applications to set parameters and read/write data values.

Goal: Push patches to Linux mainline providing SYSFS entries for IIO and PWM useful for building a demo robot
Existing project: http://github.com/beagleboard/kernel
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Able to write software in C, create patches to the Linux kernel and perform cross-compilation
Possible mentors: Laine Walker-Avina

Using BeagleBone PRUs to control CNC and 3D printer stepper motor Drivers

This project is to write code for the PRU (realtime processors on the AM335x used in the Beagle Bone) so that it can generate multiple step and direction outputs based on a queue of commands in real time. This needs to be done in real time so the acceleration and coordination of multiple stepper motors can be controlled and coordinated. A step/dir signal is commonly used in a lot of stepper motor drivers. While it is possible to generate stepper phase information from the PRU, it is also undesireable from a testing stand point. An example of a reason for doing this is controlling the X/Y directions of the head of a 3D printer so that it can generate precise curves. While similar code has been done, it is not done in a real time fashion so it is difficult to add coordination between motors and/or maintain a known acceleration.

The result of this code should be something interfaceable to a control system like the non realtime portions of the Linux CNC project (formerly the EMC project). But as a demo, this same code should also demonstrate a node.js functionality such as a "G-code" interpreter. This node.js portion can be considered a second project due to the different skill sets required and ideally this project would be split between two GSoC students. One project would be working mostly on PRU assembly with integration into the Linux kernel. The other project would be working mostly on userspace JavaScript in node.js and C++ code for anything needing optimization or low-level kernel access. Mentors would heavily assist on defining the right interfaces between the two programming environments. Goal: create code to use the AM335x PRUs to generate multiple step and direction outputs for reprap and CNC applications
Existing projects: Pru Documentation, UIO Driver documentation
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Assembly and C coding. Node.js for g-code interpretation
Possible mentors:Jason Kridner, Hunyue Yau, Laine Walker-Avina

PRU upstreaming

Remove HWMOD dependency requirement for PRU along with adding device tree bindings so it can be upstreamed into Linus's tree.

Goal: Push patches to Linux mainline providing support for the AM335x PRU
Existing project: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Able to write software in C, understand existing patches with PRU support, create patches to the Linux kernel and perform cross-compilation
Possible mentors: Start with Jason Kridner and Matt Porter, but we'll get some others involved

PRU firmware loader

Allow "firmware" which are really binary PRU applications to be loaded directly on PRU cores and executed using the request_firmware() functionality of the Linux Kernel. This should also be Cape Manager to load PRU cape specific applications.

Ideal workflow:

  • Cape detected that uses the PRU
    • Setup pinmux
  • Find the respective firmware file for PRU core (or both cores) /lib/firmware/cape_A020_pru0.bin
  • Load onto PRU and begin execution.

Goal: Push patches to Linux mainline providing support to loading firmware on PRU cores and executing
Existing project: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Able to write software in C, create patches to the Linux kernel and perform cross-compilation
Possible mentors: Matt Ranostay, Matt Porter

Program PRU using high-level scripting lanugages

Based on Chris Roger's BotSpeak work to provide a virtual machine for typical Arduino functions that can be accessed from LabView, build a virtual machine to enable PRU programming from Bonescript. The virtual machine is a simple interpreter that loops over the commands to perform such as delay, pinMode, analogRead, analogWrite, digitalRead and digitalWrite functions.

A basic design is elaborated upon at http://github.com/jadonk/pruduino

Goal: Implement a BotSpeak interpreter that off-loads hard real-time tasks from Bonescript onto the PRU and include that in the BoneScript project
Existing projects: PRUDUINO, http://github.com/beagleboard/am335x_pru_package, http://github.com/jadonk/bonescript, Chris' language definition
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Able to write software in JavaScript and assembly
Possible mentors: Chris Rogers, Jason Kridner

Android-based remote display

Use your Android phone as a remote display and control unit for you BeagleBone. Display your applications UI on the phone screen and use your phone's touchscreen to control your application on the Beaglebone.

Since all Android devices are required to support ADK (Accessory Development Kit) mode, a BeagleBone acting as a USB host can talk to an Android phone over USB. An Android application would provide the "remote" screen for the Beaglebone, much like an USB based external display on a PC. At the same time button presses and touchscreen events can be relayed to the Beaglebone as it if had a local keyboard connected

Many applications are possible, from a simple shell to aid developing and debugging to a remote X server that hosts GUI apps.

If ADK mode can also be achieved in u-boot, it could help to setup and debug the bootloader even before the Linux kernel starts.

Further, a part of the Android devices' filesystem could me made accessible to mount on the Beaglebone

Goal: Implement a remote display and keyboard for the Beaglebone running on an Android phone or tablet
Existing Project: https://github.com/SpecLad/libusb-android, BeagleBone implementation of Android Accessory Development Toolkit
Hardware Skills: Some knowledge of USB
Software Skills: Java, C and familiarity with Android
Possible mentors: Vladimir Pantelic, Jason Kridner and others


Cross platform USB boot

Boot (and flash) your BeagleBone (Black) from a Windows, Mac or Linux computer without using a microSD card.

Extend last year's GSoC project to boot from an Android device to support Windows, Mac and Linux hosts.

Goal: Download a Linux image from the web and boot a BeagleBone using it over USB
Existing Project: https://github.com/ungureanuvladvictor/BeagleDroid, https://github.com/ungureanuvladvictor/BBBlfs
Hardware Skills: Some knowledge of USB
Software Skills: C and familiarity with Mac, Linux and Windows
Possible mentors: Vladimir Pantelic, Jason Kridner

Android under Angstrom

Some people want to play Angry Birds or run other Android apps on their BeagleBoard/BeagleBone. Of course, you could use the Rowboat Android project as-is, but then you'd have to give up all of their typical Linux/X11 applications available in Angstrom. This project would use an Android-enabled kernel and a combination of both Angstrom and Android file systems. The input and display methods required for Android would need to be adjusted to run in on a virtual terminal and chroot/chvt would be used to invoke the various user space windows.

This has essentially been done once as part of Always Innovating's Super-Jumbo demo running Ubuntu, Angstrom, ChromeOS and Android simultaneously. The fundamental challenge is getting it reproducible and integrated into the OpenEmbedded build system for Angstrom and then starting to minimize the wasted file space by sharing libraries. Eventually, even making Android applications run in a window is desired.

Goal: Run Android applications under Angstrom and toggle back-and-forth using CTRL-ALT-Fn key presses.
Existing projects: http://arowboat.org, http://www.angstrom-distribution.org
Hardware skills: Minimal
Software skills: Able to write software in C and Java, experience with X11 and Android
Possible mentors: Hunyue Yau, Vladimir Pantelic

Library of Arduino-compatible functions for StarterWare

This would be an implementation of Arduino utilizing the BeagleBone Black and the StarterWare O/S independent library for accessing the hardware. Without having to access the hardware through an operating system, developers will be able to fine-tune the system to achieve optimal resource management of the CPU, peripherals and memory. The project would also include basic documentation and generation of code samples for various functionality of the library, such as SPI,Serial,Ethernet for starters. This would make the project thorough and ready for use by various developers in the community.

Goal: Utilize the Energia fork of Arduino to push support for BeagleBone and BeagleBone Black
Existing Project: Energia, StarterWare
Hardware Skills: Yes
Software Skills: C/C++
Possible mentors: Jason Kridner (others can be referred if there are interested students)

Documentation for BeagleBone and BeagleBone Black

We need to avoid documentation projects for GSoC. Please turn this into a coding project. Providing code examples might be sufficient, but code needs to be the output. The documentation can be a side-effect. Produce HOWTOs and code samples for use of I/O on BeagleBone to be placed in the neutral elinux.org BeagleBone community pages.

Goal: The Beagleboard.org community has lacked a canonical source of high quality documentation on how to use peripherals found on AM335x. Peripheral use to be documented will include UARTs, I2C, SPI, PWM, ADC, USB Host/Gadget as well as advanced topics such as software development and optimization for the M3 and PRU coprocessors.
Existing Project: elinux.org BeagleBone Community Page
Hardware Skills: Yes
Software Skills: C
Possible mentors: Hunyue Yau and Matt Porter (others welcome to volunteer)

PyBBIO library development

PyBBIO is a Python library that aims to provide Arduino-style API for hardware IO support on the Beaglebone and BeagleBone Black. It is meant to make hardware development fast and easy with Python.

Goal: Moving portions to C extensions to speed up PyBBIO, as well as adding further peripheral support and internal libraries. Possible things to add support for:

  • On-chip peripherals (SPI, CAN, eQEP, GPMC, etc.)
  • Radios (XBee, Rn-42, RN-171, etc.)
  • Sensors (temp, rh, proximity, gyro, accel, etc.)
  • Displays (HD4780, KS0108, Nokia 5110, etc.)
  • IoT libraries (Xively, Freeboard, web UI, etc.)

There should also be ample example programs for any new libraries. It would also be good to have a couple larger example projects that do more than just demo API (for example a toaster oven reflow solder controller: https://github.com/alexanderhiam/toasterReflow).

Existing Project: PyBBIO
Hardware Skills: Yes
Software Skills: Python, C, familiar with Python C extensions
Possible mentors: Alexander Hiam

MMC and DMA Linux performance

Improving performance of MMC driver by understanding issues, improving MMC, DMA drivers and eliminating bottlenecks.

Goal: Both MMC and DMA are critical to high performance of I/O intensive workloads on a Beagleboard/ARM platform, even fast system boot up depends on it.

A good amount of performance improvement is possible just by identifying what's going on in hot paths and how things can be done more simply, without breaking anything else. Also improvements are possible using innovative techniques such as intelligent buffer allocation and reducing overhead where possible in dependent components such as DMA. Cutting the fat in hot paths is definitely a start.

Existing Project: Upstream Kernel
Hardware Skills: Yes
Software Skills: C, Possible use of JTAG, ftrace, perf etc.
Possible mentors: Joel Fernandes

Implementing and testing core libraries in Userspace Arduino

Implementing and testing core libraries in Userspace Arduino, especially SPI, I2C, Wire, Serial, Servo, Stepper

This would primarily target the Arduino Tre.

Making a stable release of Processing's serial libraries for Tre

Making a stable release of OpenFrameworks's serial libraries for Tre

Previous ideas

Mentors

Name IRC nickname Melange name Native language Other languages Timezone Software help Hardware help Focus projects
Jason Kridner jkridner jkridner English - US Eastern JavaScript, C, u-boot wiring, timing diagrams, basic debug BoneScript development
Vladimir Pantelic av500 vp7 German English, Serbian CET Experienced on most areas of Embedded Linux, Multimedia Schematic Review + Design Embedded Linux, Linux Multimedia, Android
Matt Ranostay mranostay mranostay English (U.S. Midwestern Dialect) None US Pacific Time Experienced on most areas of Embedded Linux or Systems Schematic Review + Design ARM/AM335x Kernel Development
Matt Porter mdp - English (U.S. Midwestern Dialect) None US Eastern Embedded Linux Firmware/Kernel and system level design. Designing Linux drivers to make the best use of existing infrastructure. Schematic Review + Design ARM/AM335x/OMAP/PRU U-Boot and Kernel/Driver Development
Hunyue Yau ds2 hygsoc English - US Pacific Android, C, Linux, scripting Yes -
Tom Rini Tartarus trini English - US Eastern C, u-boot, OpenEmbedded - U-Boot or OpenEmbedded development
Luis Gustavo Lira lglira lglira Spanish English GMT/UTC -5 Embedded Linux, C, Android Design, Debug, Wiring Projects on the BeagleBone
Frans Meulenbroeks eFfeM effem Dutch English CET Linux (including drivers), U-Boot, C, Documentation; Coding Style, QA device interfacing (for drivers), review FPGA code -
Pantelis Antoniou panto panto Greek English GMT+2 Linux Kernel, S/W Architecture - Embedded Linux architecture fixes
Andrew Tridgell tridge andrewtridgell English GMT+11 Linux Kernel, C, C++, python - BeaglePilot
Kevin Hester kevinh /kevinh_ geeksville English GMT-8 Linux embedded, C, C++ - BeaglePilot
Lorenz Meier LorenzMeier lomeier English GMT+1 mobile localization, 3D reconstruction on smartphones and micro air vehicles - BeaglePilot
Alexander Hiam alexanderhiam alexanderhiam English - US Eastern Python, C, Linux Kernel Prototyping, design, layout, debugging PyBBIO
Samy Kamkar samy/samy_ - English - US Eastern Python, C, Linux Kernel Privacy and security researcher, computer hacker, whistleblower and entrepreneur BeaglePilot
Joel Fernandes joel_ joelagnel English - US Central C, Linux Kernel, Python Processor Engineer, Embedded systems Architecture Linux kernel improvement (perf and functionality)
Greg Kroah-Hartman gregkh gregh
David Scheltema dschelt dcschelt
Charles Steinkuehler cdstienkuehler
Steve French VoltVisionFrenchy voltvisionfrenchy
Previous mentors