Difference between revisions of "BeagleBoard/GSoC/Ideas"

From eLinux.org
Jump to: navigation, search
(2011 -> 2012)
(Mentors)
 
(280 intermediate revisions by 39 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 2015! Below, we've collected project ideas for the GSoC-2015.
  
'''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/2014_Projects#Project:_BotSpeak_PRU_Firmware|creating an interpreter for tiny CPUs]], [[BeagleBoard/GSoC/2014_Projects#Project:_PyBBIO|adding SPI and sensor support to Python]], [[BeagleBoard/GSoC/2014_Projects#Project:_Bone101|an HTML and git based tutorial sharing environment]], [[BeagleBoard/GSoC/2014_Projects#Project:_BeaglePilot|porting autopilot software to Linux]], [[BeagleBoard/GSoC/2014_Projects#Project:_BeagleLogic|an open source 100MHz 14-channel logic analyzer]], [[BeagleBoard/GSoC/2014_Projects#Project:_Android_Remote_Display|using Android tablets as Linux displays]], [[BeagleBoard/GSoC/2013_Projects#Linux_ADC_IIO_Support|putting ADC support in Linux under the IIO framework]], [[BeagleBoard/GSoC/2013_Projects#Android-based_Boot|using Android phones as a network boot source]], [[BeagleBoard/GSoC/2013_Projects#Userspace_Arduino|Running Arduino code on Linux]], [[BeagleBoard/GSoC/2013_Projects#Robot_Operating_System|Robot Operating System support within the Yocto Project build system]], [[BeagleBoard/GSoC/2013_Projects#Minix_I2C|Minix I2C support]], [[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, element14 and others, but avoids any dependence on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 500,000 boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution, Debian and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, 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 about $50 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-gsoc the BeagleBoard GSoC IRC] or [http://groups.google.com/group/beagleboard-gsoc the BeagleBoard-GSoC 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 500 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-2014|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/gsoc2015 Melange] and request to be a mentor for BeagleBoard.org.
  
=General requirements=
+
==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.
+
==Linux kernel support for embedded devices and interfaces==
 +
Improving the state of the Linux kernel, especially with regards to embedded devices and interfaces. Includes improved ARM/OMAP/Sitara platform support, simplifying the development of add-on hardware for embedded systems and exchanging hardware connectivity information with userspace.
  
==Improve boot support==
+
===BeaglePilot 2.0: Making underwater drones===
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.  
+
In a nutshell, the idea is to create an underwater vehicle (submarine) for the APM autopilot using/porting the OpenROV code/infraestructure, an open hardware submarine. The APM code should be extended and create a new kind of vehicle (e.g.: APMSubmarine).
  
''Goals:''
+
''Goal:'' Add an underwater drone vehicle class to the APM autopilot using the OpenROV work.<br>
* U-boot updates
+
''Hardware Skills:'' PPM, PWM, PRUSS<br>
** Add support for the OMAP3 EHCI controller in U-boot
+
''Software Skills:'' C, C++, nodejs, processing <br>
*** BeagleBoard and BeagleBoard-xM both have an USB EHCI controller that is currently not supported by U-boot
+
''Possible Mentors:'' Víctor Mayoral Vilches, Alejandro Hernández Cordero, Iñigo Muguruza Goenaga<br>
*** OMAPPedia reports some patches are available for PandaBoard that could be reused for BeagleBoard
+
''Workload:'' 1 student full time. <br>
** Add support for USB MSC devices
+
''GitHub:'' https://github.com/beaglepilot2<br>
** Add support for the Ethernet controller on the BeagleBoard-xM that is connected via the EHCI controller
+
''References:'' https://github.com/OpenROV/openrov-software, https://github.com/OpenROV/openrov-software-arduino<br>
** 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==
+
 
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  
+
===BeagleRT: Real-Time Linux with the BeagleBone Black===
 +
Assessment of the real-time limitations and capabilities with the BeagleBone Black.
 +
<br>
 +
 
 +
* vanilla kernel
 +
* vanilla with PREEMPT option
 +
* PREEMPT_RT patches
 +
* Xenomai patches
 +
* PRUSS
 +
 
 +
''Goal:'' Many applications require a certain degree of real-time response. This project will analyze, test and compare the different approaches for providing Real-Time responses with the BeagleBone Black development board.<br>
 +
''Hardware Skills:'' PRU, PPM, PWM, PRUSS<br>
 +
''Software Skills:'' C, C++, Python, Assembly<br>
 +
''Possible Mentors:'' Steve Arnold<br>
 +
''Workload:'' 1 student full time. <br>
 +
''GitHub:'' https://github.com/BeagleRT/BeagleRT<br>
 +
''References:'' https://www.osadl.org/fileadmin/dam/rtlws/12/Brown.pdf<br>
 +
 
 +
===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 [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>
 +
 
 +
''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>
 +
 
 +
===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>
 +
 
 +
''Goal:'' Userspace application similar to evtest that captures debug events and instrumented IIO driver code to produce those events.<br>
 +
''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>
 +
 
 +
===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
 +
===Enhance ADC driver for BeagleBone and BeagleBone Black===
 +
Improve the onboard ADC to support more features provided by the hardware. The hardware supports
 +
things like periodic sampling and averaging along with the ability to schedule the different channels
 +
and allow them to be configured differently.
 +
 
 +
''Goal:'' The Beagleboard.org community lacks a common unified way of accessing the different features available on the ADC. Some of these hacks such as attempts at periodic sampling squaders hardware resources on the BeagleBone when in reality the ADC block can do it directly. The goal is to create
 +
a drive with a plan to upstream that will expose these additional features. It should try to coordinate with the current driver maintainer. The coordination and upstreaming parts needs to be
 +
weighed and considered due to the limited GSoC time frame.
 +
 
 +
''Existing Project:'' <br>
 +
''Hardware Skills:'' Yes<br>
 +
''Software Skills:'' C<br>
 +
''Possible mentors:'' Hunyue Yau (others welcome to volunteer)
 +
===Common bootloader for different all the BeagleBone/BeagleBoards===
 +
Create a common bootloader for all the different BeagleBone/BeagleBoards. Currently, the
 +
BBX/BBC share a common bootloader and the BBW/BBB share another one. Other boards such
 +
as the upcoming new board uses yet another.
 +
''Goal:'' Unified as many of the different bootloaders as possible. This in particular
 +
focuses on the critical SPL (initial bootloader). The challenge will be working with
 +
the limited hardware resources and differences during the initial bootloader. This initial
 +
bootloader has to fit into internal memory, configure memory, and load u-boot.
 +
''Existing Project:'' <br>
 +
''Hardware Skills:'' Yes<br>
 +
''Software Skills:'' C<br>
 +
''Possible mentors:'' Hunyue Yau (others welcome to volunteer)
 +
 
 +
==ARM processor support in open source operating systems and 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.
 +
 
 +
===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.
 
   
 
   
''Goals:''
+
''Goal:'' Utilize the Energia fork of Arduino to push support for BeagleBone and BeagleBone Black<br>
* Add EDID reading support into the BeagleBoard kernel
+
''Existing Project:'' [https://github.com/energia/Energia Energia], [http://processors.wiki.ti.com/index.php/StarterWare StarterWare]<br>
* Add automated resolution configuration
+
''Hardware Skills:'' Yes<br>
* Implement Xrandr for BeagleBoard
+
''Software Skills:'' C/C++<br>
''Existing project:'' [http://beagleboard.org/project/linux linux-omap]<br>
+
''Possible mentors:'' Jason Kridner (others can be referred if there are interested students)
''Software skills:'' C, ARMv7 assembly (desired), Linux kernel driver development, X11 knowledge<br>
+
''Possible mentors:'' <br>
+
  
==JTAG debugging==
+
==Heterogeneous co-processor support in open source operating systems and libraries==
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:
+
Enabling usage of DSPs, PRUs, FPGAs, Cortex-M3s, Arduinos, MSP430 launchpads and other attached processing platforms.
  
''ARM Cortex A8 <-> OMAP3 <-> BeagleBoard <-> Flyswatter (*)'' <-> OpenOCD <-> GDB <-> Eclipse (CDT)
+
===PRU Bridge===
 +
The aim of the project is to create a multi channel userspace Linux to PRU bridge (driver). Developers should be able to send and receive data seamlessly from the ARM or PRU. On the Linux side each channel will be represented by a file, and writing to a channel is a simple file write operation. Similarly if the client program on Linux want to read, it will read the file corresponding to the channel. On the PRU side, there will be a event loop listening to any events on any channels. If there is valid data on any channel, the corresponding callback is called.<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.
+
Currently the widely used libprussdrv supports exporting of 'interrupts' via sysfs, but no clean way of data transfer. The PRU-bridge will be a remote proc based sysfs driver. Channels here are generic, will enable export of data and interrupts to userspace. [Each channel could carry it's own semantic meaning, completely upto the developer].<br>
  
''Goal:'' Able to single step kernel code using OpenOCD, GDB, and Eclipse<br>
+
Internally the kernel driver will maintain a shared memory circular buffer for each channel, and read or write on a sysfs file will result in an "upcall-downcall" action (a method in which the kernel and PRU interact). Different channels could be specialized for different requirements (i.e. one channel could be fine tuned for block transfers, another for a stream interface).<br>
''Existing project:'' [http://beagleboard.org/project/OpenOCD+OMAP3+JTAG+support/ OpenOCD]<br>
+
''Hardware skills:'' Able to monitor logic-level digital signals<br>
+
''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
+
This project will also require the student to develop a Node.js/Python based API to communicate with the PRU.<br>
'''
+
Another interesting add on would be if the driver supported dynamic pin-muxing when prompted by the PRU. (i.e. can the PRU tell the kernel to enable h/w PWM on particular pins (instead of GPIO)?)<br>
 +
'''Having a standardized driver like this will eliminate the need for writing separate drivers as in the case of applications like [https://github.com/deepakkarki/pruspeak pruspeak].'''
  
=Multimedia and user experience projects=
 
  
==Add DSP support to VLC==
+
''Goal'': Develop a driver to enable a robust communication channels b/w Linux userspace and PRU.<br>
 +
''Existing project'': small writeup available at [https://github.com/deepakkarki/pru_serial pru_serial_doc] and high level python API [https://gist.github.com/alexanderhiam/4310934a026b79fc8c65 RPC example]<br>
 +
''Hardware skills:'' Knowledge of Linux system programming, basic understanding of Device Driver, PRU architecture.<br>
 +
''Software skills:'' Good knowledge of C, working knowledge of Python/Node.js<br>
 +
''Possible mentors:'' Deepak Karki, Alexander Hiam<br>
  
''Possible mentors:'' Vladimir Pantelic<br>
+
===PRUSS Support for the newer kernels===
  
==Add DSP support to MPlayer==
+
Until now, libprussdrv has been the first point of contact for a prospective user of the Programmable Real-Time Units present on the BeagleBone Black. However in GSoC 2014 the two projects targeting the PRUs - BeagleLogic and BotSpeak worked on the remoteproc framework of the Linux kernel for the PRUs which was found to give better results.
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)
+
  
''Goal:'' Able to play video in MPlayer using DSP codecs<br>
+
However, not everyone should need to hack the kernel and the drivers for buiding their projects and as such a proper lightweight message passing framework and firmware loading infrastructure would increase the utility of the PRUs that are on board the BeagleBone (Black).
''Existing project:'' http://www.mplayerhq.hu/<br>
+
''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==
+
Possible design goals of the new framework:
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.
+
  
''Goal:'' Able to do e.g. DSP color conversion in a gstreamer pipeline or in FFmpeg/Mplayer<br>
+
* '''Upstreaming''' The idea is to have support for the PRU in the mainline kernel and not in another "vendor" kernel. <br>Thus the entire framework has to be written keeping the Kernel coding guidelines so that the patch will be ready for submission to the LKML soon by the end of the coding period.
''Existing project:'' http://www.mplayerhq.hu/<br>
+
''Existing project:'' http://www.FFmpeg.org/<br>
+
''Existing project:'' https://gstreamer.ti.com/gf/project/gstreamer_ti/<br>
+
''Existing project:'' http://processors.wiki.ti.com/index.php/C6Accel<br>
+
''Software skills:'' C<br>
+
''Possible mentors:''  Diego Dompe<br>
+
  
==DSP accelerated USB webcam gadget==
+
* '''Simple and easy-to-use API''' Need to generate examples, documentation and keep the API as simple and straightforward as possible. There is no point in having yet another PRU framework if no one is using it.
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.  
+
  
''Goal:'' Able to stream encoded (MJPG/H264) video data to the host using the USB webcam gadget<br>
+
* '''Language-Agnostic''' Whether one swears by C, uses Python or is a JavaScript programmer, everyone can use the same basic API and objects to leverage the processing capabilities of the PRU. <br>Alexander Hiam posts a sample [https://gist.github.com/alexanderhiam/4310934a026b79fc8c65 gist] which could be used as a starting point.
''Existing project:'' https://patchwork.kernel.org/patch/48487/<br>
+
''Existing project:'' http://processors.wiki.ti.com/index.php/Codec_Engine_Overview<br>
+
''Software skills:'' C<br>
+
''Possible mentors:''  ???<br>
+
  
==Speech recognition==
+
* '''Lightweight''' The PRU is optimized for low latency memory access and I/O operations, be it toggling a GPIO, generating stepping pulses or controlling large streams of WS2812B LED strip modules or sampling GPIOs at regular intervals into RAMLarger messages increase this overhead.
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:
+
* Voice recognition integrated into Ubiquity: Integrate Mozilla Firefox, Mozilla Ubiquity, and voice recognition on the BeagleBoard with a microphoneUse 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.
+
* '''Support for interrupts to userspace''' The ability to get a callback from the PRUs to userspace or kernel space (according to need of the application). A kernel module may be able to "attach" and "detach" itself from the main pru-remoteproc driver to extend its functionality if so needed.
  
''Existing project:'' http://beagleboard.org/project/tiesr<br>
+
* '''Memory Management''' The ability to allocate shared buffers of arbitrary size shared between the PRU and the kernel if required.
''Possible mentors:'' Lorin Netsch, Sourabh Ravindran, Diego Dompe (if done with gstreamer)<br>
+
  
==Add DSP support to GNU radio==
+
The list as such is not exhaustive and prospective students / developers are encouraged to participate and edit this section with possible suggestions to make the PRUSS programming more productive and accessible to everyone.
''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>
+
''Existing project:'' [http://gnuradio.org GNURadio]<br>
+
''Software skills:'' C++<br>
+
''Mentors:'' Philip Balister<br>
+
  
==Optimize OpenCV with C6Accel==
+
''Goal'': Create a new mainline kernel-friendly infrastructure that leverages functionality of the PRU<br>
 +
''Existing project'': BeagleLogic, PRUSpeak, <br>
 +
''Hardware skills:'' Understanding of basic embedded systems.<br>
 +
''Software skills:'' Able to write software in C, understand existing patches with PRU support, PRU Assembly. create patches to the Linux kernel and perform cross-compilation<br>
 +
''Possible mentors:'' Kumar Abhishek<br>
  
''Possible mentors:'' Leo Estavez, Gagan Maur<br>
+
===PRU upstreaming===
 +
Remove HWMOD dependency requirement for PRU along with adding device tree bindings so it can be upstreamed into Linus's tree.
  
=Hardware + software projects=
+
''Goal'': Push patches to Linux mainline providing support for the AM335x PRU<br>
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.
+
''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>
  
==Create JavaScript tutorial for hardware control==
+
===PRU firmware loader===
Create a live-editable tutorial written in HTML and JavaScript to explore I/O (GPIO, I2C, SPI, USB, etc.) using the Linux kernelThe Node.JS JavaScript interpreter enables you to use your
+
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.
  
''Existing project:'' [http://blog.hangerhead.com/2011/03/nodejs-based-cloud9-javascript-ide.html Node.JS-based Cloud9 IDE running on a BeagleBoard]<br>
+
Ideal workflow:
''Existing project:'' [http://gitorious.org/beagleboard-validation/education HTML and JavaScript slideshow Education application to hold the tutorial]<br>
+
''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==
+
* Cape detected that uses the PRU
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.
+
** 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.
  
''Existing project:'' omapfbplay<br>
+
''Goal'': Push patches to Linux mainline providing support to loading firmware on PRU cores and executing<br>
''Existing project:'' libfreenect<br>
+
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br>
''Possible mentor:'' Mans, whatnick, Mark Yoder<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>
  
==Beagleboard Hardware Control Library==
+
===Program PRU using high-level scripting languages===
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.
+
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.
  
''Goal:'' provide a library to interface with GPIO, I2C and SPI on the Beagleboard <br>
+
A basic design is elaborated upon at http://github.com/jadonk/pruduino
''Hardware skills:'' basic<br>
+
''Software skills:'' C<br>
+
''Possible mentor:'' ???
+
  
==Adding Sense to Beagle==
+
''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>
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 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>
  
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.
+
===Linux on C6x===
 +
Execute Linux on the C6x core on the BeagleBoard, BeagleBoard-xM and BeagleBoard-X15.
  
''Possible mentor:'' Mark Yoder
+
''Goal'': Submit patches to the mainline Linux kernel for building a suitable kernel.
 +
''Existing project'': http://linux-c6x.org/wiki/index.php/Main_Page<br>
 +
''Hardware skills'': Able to read processor technical reference manual and comprehend it.<br>
 +
''Software skills'': Must be familiar with Linux bring-up.<br>
 +
''Possible mentors'': Jadon Kridner<br>
  
==CarPC API and implementation==
+
==Interesting Applications for PRU Processing==
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).
+
  
=Community infrastructure projects=
+
===Using BeagleBone PRUs to control CNC and 3D printer stepper motor Drivers===
==Updating BeagleBoard.org UI/backend==
+
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>
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>
+
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.
''Mentor:'' Jason Kridner<br>
+
  
=To be classified=
+
''Goal'': create code to use the AM335x PRUs to generate multiple step and direction outputs for reprap and CNC applications<br>
 +
''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>
  
==Angstrom Linux and Rowboat Android==
+
===Real-time Data Acquisition and Processing===
Some people want to play Angry Birds or run other Android apps on their BeagleBoardOf 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 systemThe input and display methods required for Android would need to be adjusted to run within an X11 window.
+
Use PRUs to process data from sensors and/or imaging devicesDeployment scenario could be solar-powered remote sensor nodes or cubesats (1-U or larger)Example applications might include:
 +
<br>
  
''Goals'':
+
* Use ultasonic transducers to make a 3-axis sonic anemometer (ie, use PRUs to calculate speed-of-sound in the x-y-z directions and derive orthogonal wind components).
* Rowboat running in a window
+
* Capture and process 4 image bands simulatneously (eg, B,G,R,NIR).
* Provide input method that works in a window
+
* Capture and process high-frequency sensor data, eg, geomagnitic field components
* 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)
+
  
 +
====Orbital Imaging Cubesat====
 +
This is essentially a prototype project for both a skeleton software framework and sensor integration (eg, via SPI, I2C, depending on data rates, etc) to process data in real-time on PRUs.  Should leverage both existing hardware projects (eg, proto-cape, other) or suitable sensor breakout board(s) and software projects (and potentially other GSoC projects) as much as possible.  The ultimate goal is a small cubesat-based orbital imaging platform, one or more "U" in size (the minimum necessary), specifically collect/process high quality magnetometer data, and hopefully detect other objects, calculate an acquisition data vetcor, etc.  This requires both high-res data acquisition/processing and generation of real-time pointing data (otherwise known as acquisition data) for use by onboard cameras or external systems.
  
==BeagleChat==
+
Several major phases are required to achieve this goal, but most likely only one phase is a viable target for a single summer's project. Careful scoping is a must.
'''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=
+
* First phase: collect/process high quality magnetometer data. Even with a short mast, data from primary sensor is still noisy; See [http://www.nasa.gov/content/goddard/cubesat-instruments-to-demonstrate-nasa-firsts/ NASA cubesat article] for example solution using secondary magnetometer measurements to collect "noise" (ie, magnetic data produced by satellite electronics, etc).  Use PRUs to process data from two magnetometers.
Some additional ideas can be found on the [[BeagleBoard/contest|BeagleBoard contest page]] and the [http://beagleboard.org/project BeagleBoard project page].
+
  
* RTEMS BSP for Beagle board: '''Medium''' [http://www.rtems.org RTEMS] is a free real-time operating systemThis 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)
+
* Second Phase: integrate GPS/comm/camera/servos with power systems, sensorsCan use PRU to capture/process camera data.
  
* 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.
+
* Third Phase: determine minimum form-factor and perform final integration. Find the sweet spot between mass, size, and power requirements. Build 2 (one to fly, one to test).
  
* Porting open-source codec to DSP (MadPlay, VLC, some of the mplayer codecs …: '''Medium'''
+
Notes: Relative speeds may be too much for accurate local image capture, however, a reasonable level of detection via onboard sensors, especially with a local acquisition data solution for an external platform, would still be useful.  If available, an external acquisition data source may be used for initial pointing prior to local detection.  This may allow imaging of known objects even with high relative speed.
  
* 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
+
''Goal'': create prototype code to use the AM335x PRUs to acquire/process high-resolution magnetometer and other sensor data and produce an acquisition data solution for a detected object<br>
 +
''Existing projects'': [https://github.com/kriswiner/MPU-6050/wiki/Affordable-9-DoF-Sensor-Fusion Sensor Data Fusion], [http://wiki.thing-printer.com/index.php?title=PyPRUSS_on_BeagleBone Python PRU binding documentation]<br>
 +
''Hardware skills:'' Able to read schematics, solder and/or use a breadboard to connect components, hook up serial console<br>
 +
''Software skills:'' Ada, C, Python, other (both reading and coding).<br>
 +
''Possible mentors:''Steve Arnold<br>
  
* beagle as DLNA/upnp renderer, server, controller, or media player.
+
==Linux userspace support of embedded devices and interfaces in high-level languages==
 +
Improving the Bonescript JavaScript library, the PyBBIO Python library, Userspace Arduino, web-based interface libraries, examples or alternatives in other languages.
  
* Wiimote + Pico Projector + 3D art tool
+
===Implementing and testing core libraries in Userspace Arduino===
 +
Implementing and testing core libraries in Userspace Arduino, especially SPI, I2C, Wire, Serial, Servo, Stepper
  
* OpenCL implementation that uses the DSP and/or NEON (could be used as framework for any dsp/neon acceleration)
+
This would primarily target the Arduino Tre.
  
* 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).
+
===Making a stable release of Processing's serial libraries for Tre===
  
=Mentors=
+
===Making a stable release of OpenFrameworks's serial libraries for Tre===
  
 +
==Improving initial experience for novice developers==
 +
Improving the methods for communicating how to build projects, improving the out-of-box experience for novices and 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.
 +
=== Demo Android app using BBBAndroid ===
 +
The [http://beagleboard.org/project/bbbandroid/ BBBAndroid project] allows you to run Android on your favorite embedded Linux board. The next step for this project would be to get more people involved by showcasing some apps that can be run on Android which make use of the awesome peripherals of the BeagleBone Black : GPIOs, i2c, spi, CAN, ADC, etc.  <br>
 +
Exact problem definition could be defined by the student<br>
 +
A good place to start is [http://icculus.org/~hendersa/android/ this website].<br>
 +
''Goal:'' Build android app(s) that can be run using BBBAndroid.<br>
 +
''Hardware Skills:'' Basic knowledge of digital circuits.<br>
 +
''Software Skills:'' Some experience with Android, C<br>
 +
''Possible Mentors:'' Andrew Henderson, Anuj Deshpande<br>
 +
 +
=== NW.js (a.k.a 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.<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>
 +
''Hardware Skills:'' N/A<br>
 +
''Software Skills:'' Able to write software in JavaScript and work with Node.js modules<br>
 +
''Possible mentors:'' Jason Kridner, Julian Duque<br>
 +
 +
===BoneScript web pages with live-running examples and documentation===
 +
{{#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.
 +
 +
'''This is a proposal, Jason Kridner needs to give the OK for this.''' <br>
 +
''Goal:'' Get the source code http://diegotc.github.io/bone101/Support/GSOC/views/index.html of last year of the GSOC program and continue
 +
making changes for this new year program. One of the main objectives will be to include the Beaglebone-UI embedded on the cards.
 +
Right now you can run programs that use the bonescript library. A new function of the platform could be that it allows users
 +
to also run programs on other languages like python or ruby. Fixed some design issues with current source code and find the best way to maintained all information on gist.github.com Taking in consideration big images can't be uploaded right now.<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>
 +
''Hardware Skills:'' Basic knowledge of digital circuits.<br>
 +
''Software Skills:'' JavaScript and some familiarity with Linux<br>
 +
''Possible mentors:'' Jason Kridner, Diego Turcios, Julian Duque<br>
 +
 +
===Android-based remote display===
 +
Extend last years project with support for keyboard, mouse and sound. The project is composed of 2 subprojects: a kernel framebuffer+usb driver and a Java application. The basic video interface is in place and tested but the project lacks user input support.
 +
 +
''Goal:'' Improve the existing project and add support for keyboard, mouse and sound<br>
 +
''Existing Project:'' [https://github.com/praveendath92/bard-droid Android application], [https://github.com/praveendath92/bard-linux Kernel framebuffer driver]<br>
 +
''Hardware Skills:'' Some knowledge of USB<br>
 +
''Software Skills:'' Java, C and Android.
 +
''Possible mentors:'' Vladimir Pantelic, Jason Kridner, Vlad Ungureanu, Praveen Kumar Pendyala (last year GSoCer), Andrew Henderson
 +
 +
Where to start? [https://github.com/praveendath92/bard-linux/blob/master/documentation/dev.md This] could be a good start.
 +
 +
===Cross platform USB boot===
 +
Boot (and flash) your BeagleBone (Black) and BealgeBoard X15 from a Windows, Mac or Linux computer without using a microSD card.
 +
 +
Extend [https://github.com/ungureanuvladvictor/bbblfs BBB Linux flasher] to support Windows, Mac and Linux hosts. The support for the BB{B/W} is in place but needs adaptation for Windows/Mac. The BeagleBoard X15 uses another way of USB booting [http://www.ti.com/lit/ug/spruhz6/spruhz6.pdf Peripheral Booting on the X15].
 +
 +
The project can be extended to automatically flash a board and then start executing tests in a CI environment. Another addition can be a cross-platform UI written using QT for easier portability.
 +
 +
''Goal:'' Download a Linux image from the web and boot a BeagleBoard 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, libusb and familiarity with Mac, Linux and Windows<br>
 +
''Possible mentors:'' Vladimir Pantelic, Jason Kridner, Vlad Ungureanu<br>
 +
 +
===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 [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.
 +
 +
''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, Andrew Henderson<br>
 +
 +
===Automated testing for BeagleBone and BeagleBone Black===
 +
Produce code samples and test harness 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.<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, Matt Porter and Jason Kridner
 +
 +
==Previous ideas==
 +
* [[BeagleBoard/GSoC/Ideas-2014]]
 +
* [[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 267: Line 407:
 
| Jason Kridner
 
| Jason Kridner
 
| jkridner
 
| jkridner
 +
| beagleboard
 
| 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
 +
|-
 +
| Vlad Ungureanu
 +
| vvu
 +
| ungureanuvladvictor
 +
| Romanian
 +
| English
 +
| GMT +2
 +
| Linux, C, Android, U-Boot, build-systems, USB
 +
| -
 +
| Cross-Platform USB Boot, Android Based Display
 
|-
 
|-
 
| Hunyue Yau
 
| Hunyue Yau
 
| ds2
 
| ds2
 +
| hygsoc
 
| English
 
| English
|
+
| -
 
| US Pacific
 
| US Pacific
| Android, C, Linux, scripting
+
| Android, C, Linux, scripting, Kernel
 
| Yes
 
| Yes
 +
| -
 
|-
 
|-
| Frans Meulenbroeks
+
| Tom Rini
| eFfeM
+
| Tartarus
| Dutch
+
| trini
| English, basic understanding of German
+
| English
| CET
+
| -
| C, User Interface, Linux, booting, performance improvement, networking technology
+
| US Eastern
| no
+
| C, u-boot, OpenEmbedded
 +
| -
 +
| U-Boot or OpenEmbedded development
 
|-
 
|-
| Kevin Hilman
+
| Pantelis Antoniou
| khilman
+
| panto
 +
| panto
 +
| Greek
 
| English
 
| English
| fluent in French
+
| GMT+2
| US Pacific
+
| Linux Kernel, S/W Architecture
 +
| -
 +
| Embedded Linux architecture fixes
 
|-
 
|-
| Luis Gustavo Lira
+
| Deepak Karki
|
+
| karki
| Spanish
+
| karki
| fluent in English and French)
+
| English
 +
| Hindi, Kannada
 +
| IST
 +
| PRU drivers, Python userspace libraries
 +
| -
 +
| PRU Bridge, PyBBIO
 
|-
 
|-
| Koen Kooi
+
| Kumar Abhishek
| _koen_
+
| Abhishek_
| Dutch
+
| Abhishek-Kakkar
| Fluent in English
+
| English
| CET
+
| Hindi
| Buildsystem integration, distribution
+
| IST
| not really
+
| PRU, Linux Kernel Programming
|  
+
| Yes
 +
| PRUSS Support for newer kernels
 
|-
 
|-
| Katie Roberts-Hoffman
+
| Alexander Hiam
| katier
+
| alexanderhiam
 +
| alexanderhiam
 
| English
 
| English
| nope
+
| -
 +
| US Eastern
 +
| Python, C, Linux Kernel
 +
| Prototyping, design, layout, debugging
 +
| PRU Bridge, PRUSS Support for the newer kernels
 +
|-
 +
| 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
 
| US Central
| Android, DSP integration (Link/CE/etc)
+
| C, Linux Kernel, Python
| nope
+
| Processor Engineer, Embedded systems Architecture
 +
| Linux kernel improvement (perf and functionality)
 
|-
 
|-
| Mans Rullgard
+
| Greg Kroah-Hartman
| mru
+
| gregkh
| English, Swedish
+
| gregh
| Some German
+
| GMT
+
| C, Assembler
+
|
+
|
+
 
|-
 
|-
| Mike Zucchi
+
| David Scheltema
| notzed
+
| dschelt
 +
| dcschelt
 
| English
 
| English
 +
| Latin ;)
 +
| US Pacific
 +
|-
 +
| Charles Steinkuehler
 
|
 
|
| Australia/South
+
| cdstienkuehler
| C, Assembly, Java, SIMD.  Applications, libraries, GUI, multi-threading.
+
| not much
+
|
+
 
|-
 
|-
| Philip Balister
+
| Steve French
| Crofton
+
| VoltVisionFrenchy
 +
| voltvisionfrenchy
 
|-
 
|-
| Robert Nelson
+
|Anuj Deshpande
| rcn-ee
+
|anujdeshpande
| English
+
|anujdeshpande
| -
+
|English
| US Central
+
|German, Hindi
| C, Shell Scripting, Deb packaging
+
|IST / GMT-530
 +
|C, Python, JS
 +
|-
 +
|Diego Turcios
 +
|DiegoTc
 +
|DiegoTc
 +
|Spanish
 +
|English
 +
|US Center
 +
|JS, Node, Javascript
 
|
 
|
 +
|Improving initial experience for novice developers
 +
|-
 +
|Praveen Kumar Pendyala
 +
|praveendath92
 +
|praveendath92
 +
|English
 +
|Hindi, Telugu
 +
|CET / GMT +2
 +
|C, Linux Kernel, Android, Java
 
|
 
|
 +
|Android Based Display
 
|-
 
|-
| Soren Steen Christensen
+
|Robert Nelson
| soren.ssc
+
|rcn-ee
| Danish
+
|
| Fluent in English and some German
+
|English
| CET
+
|
| C/C++, ASM, Device Drivers
+
|US Central
| OMAP chip, HW design, Low level development & debuging
+
|C, Linux Kernel, U-Boot, Bash, Ubuntu/Debian Root File System
| All kind of HW and low level SW stuff
+
 
|-
 
|-
| Mark Yoder
+
| Kassandra Perch
| yoder
+
| nodebotanist
 +
| nodebotanist
 +
| English
 +
| ---
 +
| Central Standard US
 +
| Javascript (Node, client-side, Johnny-Five, NW/node-webkit), little bit of C.
 +
| Wiring, soldering
 +
| getting-started app, bonescript development
 +
|-
 +
|Andrew Henderson
 +
|hendersa
 +
|hendersa
 +
|English
 
|
 
|
 +
|US Eastern
 +
|C, C++, ARM asm, Linux, Linux kernel, Android
 +
|Prototyping
 +
|Android, Linux multimedia
 
|-
 
|-
| Jeff Osier-Mixon
+
|Julian Duque
| jefro
+
|julianduque
| English (US)
+
|julianduque
|  
+
|Spanish
| US Pacific
+
|English
|  
+
|EST / GMT-5
|  
+
|JavaScript (Node.js/io.js, Frontend, Johnny-Five, NW/node-webkit), Linux
| documentation
+
|
 +
|Getting Started App, BoneScript development, Node.js/io.js update on build images
 
|-
 
|-
| Laine Walker-Avina
+
| Steve Arnold
| Ceriand
+
| nerdboy / mr_science
 +
| sarnold
 
| English
 
| English
|  
+
| -
| US Pacific
+
| US Western (PST8PDT)
| C, Assembly, Buildroot
+
| u-boot, kernel, Linux OS build/deploy, bash, Python, etc
| USB protocol & logic analyzers, Various JTAG probes
+
| basic prototyping/debugging, high-level I2C/SPI sensor interfaces
| OpenOCD, bootloaders, Linux kernel
+
| Satellites, cameras, remote sensor platforms, weather stuff
 
|-
 
|-
| Frank Walzer
+
| Víctor Mayoral
| franktango
+
| vmayoral
| German
+
| vmayoral
| English
+
| English, Spanish
 +
| -
 
| CET
 
| CET
| C++, OOP
+
| kernel, Snappy Ubuntu Core, APM, ROS
| Debug, JTAG, Interfaces
+
| drones, copters, planes, rovers
| Graphics, GUI, Build systems
+
| Erle Robotics
 
|-
 
|-
| Khasim Syed Mohammed
+
| Alejandro Hernández
| khasim
+
| ahcorde
| English
+
| ahcorde
| Hindi
+
| English, Spanish
| India
+
| -
| C, C++, Assembly, Linux device drivers, board bring up, bootloaders
+
| CET
| Schematic review, board development
+
| CV, Snappy Ubuntu Core, APM, ROS
 +
| drones, copters, planes, rovers, camera design
 +
| Erle Robotics
 
|-
 
|-
| Siji Sunny
+
| Iñigo Muguruza
| siji
+
| imuguruza
| English
+
| imuguruza
| Hindi
+
| English, Spanish, Portuguese
| India
+
| -
| C,Operating Systems(Ubuntu-Arm,Angstrom,Android,Debian),Open Source Application/GUI Development(Clutter,GTK),RF Programming,Language Computing,Text processing,Unicode,Fonts
+
| CET
| No
+
| kernel, Debian, APM, ROS
| Language Computing, Text Processing, Operating System, Text To speech ,GUI,Build Systems
+
| drones, copters, planes, rovers, PCB design
 +
| Erle Robotics
 
|-
 
|-
| Devaraj Rangasamy
+
| Victor
| Deva
+
| calculus
| Hindi, Tamil
+
| calculus
 
| English
 
| English
| India
+
| -
| Android, Linux Kernel Base Port
+
| PDT
| No
+
| Linux, C/C++, Java, ROS, Gentoo
| Language Computing, Text Processing, Operating System, Text To speech
+
| sensors (SPI/I2C), microcontrollers
 
|-
 
|-
| Joel Sherrill
+
| Marshall Culpepper
| DrJoel
+
| marshall_law
 +
| marshall_law
 
| English
 
| English
 
| -
 
| -
 
| US Central
 
| US Central
| RTEMS maintainer, real-time, cross tools
+
| Linux, C/C++, FreeRTOS, Javascript, Python
| No
+
| Prototyping
| RTEMS BSP
+
| CubeSat and HAB applications
|-
+
| Diego Dompe
+
| ddompe
+
| spanish
+
| 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 09:51, 30 March 2015


Contents

Welcome!

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

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 creating an interpreter for tiny CPUs, adding SPI and sensor support to Python, an HTML and git based tutorial sharing environment, porting autopilot software to Linux, an open source 100MHz 14-channel logic analyzer, using Android tablets as Linux displays, putting ADC support in Linux under the IIO framework, using Android phones as a network boot source, Running Arduino code on Linux, Robot Operating System support within the Yocto Project build system, Minix I2C support, 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, element14 and others, but avoids any dependence on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 500,000 boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution, Debian and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, ArchLinux, Gentoo, Buildroot and many more.

BeagleBoard was inspiration for Raspberry Pi[1] and is available for about $50 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 GSoC IRC or the BeagleBoard-GSoC 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 500 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 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

Linux kernel support for embedded devices and interfaces

Improving the state of the Linux kernel, especially with regards to embedded devices and interfaces. Includes improved ARM/OMAP/Sitara platform support, simplifying the development of add-on hardware for embedded systems and exchanging hardware connectivity information with userspace.

BeaglePilot 2.0: Making underwater drones

In a nutshell, the idea is to create an underwater vehicle (submarine) for the APM autopilot using/porting the OpenROV code/infraestructure, an open hardware submarine. The APM code should be extended and create a new kind of vehicle (e.g.: APMSubmarine).

Goal: Add an underwater drone vehicle class to the APM autopilot using the OpenROV work.
Hardware Skills: PPM, PWM, PRUSS
Software Skills: C, C++, nodejs, processing
Possible Mentors: Víctor Mayoral Vilches, Alejandro Hernández Cordero, Iñigo Muguruza Goenaga
Workload: 1 student full time.
GitHub: https://github.com/beaglepilot2
References: https://github.com/OpenROV/openrov-software, https://github.com/OpenROV/openrov-software-arduino


BeagleRT: Real-Time Linux with the BeagleBone Black

Assessment of the real-time limitations and capabilities with the BeagleBone Black.

  • vanilla kernel
  • vanilla with PREEMPT option
  • PREEMPT_RT patches
  • Xenomai patches
  • PRUSS

Goal: Many applications require a certain degree of real-time response. This project will analyze, test and compare the different approaches for providing Real-Time responses with the BeagleBone Black development board.
Hardware Skills: PRU, PPM, PWM, PRUSS
Software Skills: C, C++, Python, Assembly
Possible Mentors: Steve Arnold
Workload: 1 student full time.
GitHub: https://github.com/BeagleRT/BeagleRT
References: https://www.osadl.org/fileadmin/dam/rtlws/12/Brown.pdf

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

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

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

Enhance ADC driver for BeagleBone and BeagleBone Black

Improve the onboard ADC to support more features provided by the hardware. The hardware supports things like periodic sampling and averaging along with the ability to schedule the different channels and allow them to be configured differently.

Goal: The Beagleboard.org community lacks a common unified way of accessing the different features available on the ADC. Some of these hacks such as attempts at periodic sampling squaders hardware resources on the BeagleBone when in reality the ADC block can do it directly. The goal is to create a drive with a plan to upstream that will expose these additional features. It should try to coordinate with the current driver maintainer. The coordination and upstreaming parts needs to be weighed and considered due to the limited GSoC time frame.

Existing Project:
Hardware Skills: Yes
Software Skills: C
Possible mentors: Hunyue Yau (others welcome to volunteer)

Common bootloader for different all the BeagleBone/BeagleBoards

Create a common bootloader for all the different BeagleBone/BeagleBoards. Currently, the BBX/BBC share a common bootloader and the BBW/BBB share another one. Other boards such as the upcoming new board uses yet another. Goal: Unified as many of the different bootloaders as possible. This in particular focuses on the critical SPL (initial bootloader). The challenge will be working with the limited hardware resources and differences during the initial bootloader. This initial bootloader has to fit into internal memory, configure memory, and load u-boot. Existing Project:
Hardware Skills: Yes
Software Skills: C
Possible mentors: Hunyue Yau (others welcome to volunteer)

ARM processor support in open source operating systems and 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.

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)

Heterogeneous co-processor support in open source operating systems and libraries

Enabling usage of DSPs, PRUs, FPGAs, Cortex-M3s, Arduinos, MSP430 launchpads and other attached processing platforms.

PRU Bridge

The aim of the project is to create a multi channel userspace Linux to PRU bridge (driver). Developers should be able to send and receive data seamlessly from the ARM or PRU. On the Linux side each channel will be represented by a file, and writing to a channel is a simple file write operation. Similarly if the client program on Linux want to read, it will read the file corresponding to the channel. On the PRU side, there will be a event loop listening to any events on any channels. If there is valid data on any channel, the corresponding callback is called.

Currently the widely used libprussdrv supports exporting of 'interrupts' via sysfs, but no clean way of data transfer. The PRU-bridge will be a remote proc based sysfs driver. Channels here are generic, will enable export of data and interrupts to userspace. [Each channel could carry it's own semantic meaning, completely upto the developer].

Internally the kernel driver will maintain a shared memory circular buffer for each channel, and read or write on a sysfs file will result in an "upcall-downcall" action (a method in which the kernel and PRU interact). Different channels could be specialized for different requirements (i.e. one channel could be fine tuned for block transfers, another for a stream interface).

This project will also require the student to develop a Node.js/Python based API to communicate with the PRU.
Another interesting add on would be if the driver supported dynamic pin-muxing when prompted by the PRU. (i.e. can the PRU tell the kernel to enable h/w PWM on particular pins (instead of GPIO)?)
Having a standardized driver like this will eliminate the need for writing separate drivers as in the case of applications like pruspeak.


Goal: Develop a driver to enable a robust communication channels b/w Linux userspace and PRU.
Existing project: small writeup available at pru_serial_doc and high level python API RPC example
Hardware skills: Knowledge of Linux system programming, basic understanding of Device Driver, PRU architecture.
Software skills: Good knowledge of C, working knowledge of Python/Node.js
Possible mentors: Deepak Karki, Alexander Hiam

PRUSS Support for the newer kernels

Until now, libprussdrv has been the first point of contact for a prospective user of the Programmable Real-Time Units present on the BeagleBone Black. However in GSoC 2014 the two projects targeting the PRUs - BeagleLogic and BotSpeak worked on the remoteproc framework of the Linux kernel for the PRUs which was found to give better results.

However, not everyone should need to hack the kernel and the drivers for buiding their projects and as such a proper lightweight message passing framework and firmware loading infrastructure would increase the utility of the PRUs that are on board the BeagleBone (Black).

Possible design goals of the new framework:

  • Upstreaming The idea is to have support for the PRU in the mainline kernel and not in another "vendor" kernel.
    Thus the entire framework has to be written keeping the Kernel coding guidelines so that the patch will be ready for submission to the LKML soon by the end of the coding period.
  • Simple and easy-to-use API Need to generate examples, documentation and keep the API as simple and straightforward as possible. There is no point in having yet another PRU framework if no one is using it.
  • Language-Agnostic Whether one swears by C, uses Python or is a JavaScript programmer, everyone can use the same basic API and objects to leverage the processing capabilities of the PRU.
    Alexander Hiam posts a sample gist which could be used as a starting point.
  • Lightweight The PRU is optimized for low latency memory access and I/O operations, be it toggling a GPIO, generating stepping pulses or controlling large streams of WS2812B LED strip modules or sampling GPIOs at regular intervals into RAM. Larger messages increase this overhead.
  • Support for interrupts to userspace The ability to get a callback from the PRUs to userspace or kernel space (according to need of the application). A kernel module may be able to "attach" and "detach" itself from the main pru-remoteproc driver to extend its functionality if so needed.
  • Memory Management The ability to allocate shared buffers of arbitrary size shared between the PRU and the kernel if required.

The list as such is not exhaustive and prospective students / developers are encouraged to participate and edit this section with possible suggestions to make the PRUSS programming more productive and accessible to everyone.

Goal: Create a new mainline kernel-friendly infrastructure that leverages functionality of the PRU
Existing project: BeagleLogic, PRUSpeak,
Hardware skills: Understanding of basic embedded systems.
Software skills: Able to write software in C, understand existing patches with PRU support, PRU Assembly. create patches to the Linux kernel and perform cross-compilation
Possible mentors: Kumar Abhishek

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 languages

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

Linux on C6x

Execute Linux on the C6x core on the BeagleBoard, BeagleBoard-xM and BeagleBoard-X15.

Goal: Submit patches to the mainline Linux kernel for building a suitable kernel. Existing project: http://linux-c6x.org/wiki/index.php/Main_Page
Hardware skills: Able to read processor technical reference manual and comprehend it.
Software skills: Must be familiar with Linux bring-up.
Possible mentors: Jadon Kridner

Interesting Applications for PRU Processing

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

Real-time Data Acquisition and Processing

Use PRUs to process data from sensors and/or imaging devices. Deployment scenario could be solar-powered remote sensor nodes or cubesats (1-U or larger). Example applications might include:

  • Use ultasonic transducers to make a 3-axis sonic anemometer (ie, use PRUs to calculate speed-of-sound in the x-y-z directions and derive orthogonal wind components).
  • Capture and process 4 image bands simulatneously (eg, B,G,R,NIR).
  • Capture and process high-frequency sensor data, eg, geomagnitic field components

Orbital Imaging Cubesat

This is essentially a prototype project for both a skeleton software framework and sensor integration (eg, via SPI, I2C, depending on data rates, etc) to process data in real-time on PRUs. Should leverage both existing hardware projects (eg, proto-cape, other) or suitable sensor breakout board(s) and software projects (and potentially other GSoC projects) as much as possible. The ultimate goal is a small cubesat-based orbital imaging platform, one or more "U" in size (the minimum necessary), specifically collect/process high quality magnetometer data, and hopefully detect other objects, calculate an acquisition data vetcor, etc. This requires both high-res data acquisition/processing and generation of real-time pointing data (otherwise known as acquisition data) for use by onboard cameras or external systems.

Several major phases are required to achieve this goal, but most likely only one phase is a viable target for a single summer's project. Careful scoping is a must.

  • First phase: collect/process high quality magnetometer data. Even with a short mast, data from primary sensor is still noisy; See NASA cubesat article for example solution using secondary magnetometer measurements to collect "noise" (ie, magnetic data produced by satellite electronics, etc). Use PRUs to process data from two magnetometers.
  • Second Phase: integrate GPS/comm/camera/servos with power systems, sensors. Can use PRU to capture/process camera data.
  • Third Phase: determine minimum form-factor and perform final integration. Find the sweet spot between mass, size, and power requirements. Build 2 (one to fly, one to test).

Notes: Relative speeds may be too much for accurate local image capture, however, a reasonable level of detection via onboard sensors, especially with a local acquisition data solution for an external platform, would still be useful. If available, an external acquisition data source may be used for initial pointing prior to local detection. This may allow imaging of known objects even with high relative speed.

Goal: create prototype code to use the AM335x PRUs to acquire/process high-resolution magnetometer and other sensor data and produce an acquisition data solution for a detected object
Existing projects: Sensor Data Fusion, Python PRU binding documentation
Hardware skills: Able to read schematics, solder and/or use a breadboard to connect components, hook up serial console
Software skills: Ada, C, Python, other (both reading and coding).
Possible mentors:Steve Arnold

Linux userspace support of embedded devices and interfaces in high-level languages

Improving the Bonescript JavaScript library, the PyBBIO Python library, Userspace Arduino, web-based interface libraries, examples or alternatives in other languages.

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

Improving initial experience for novice developers

Improving the methods for communicating how to build projects, improving the out-of-box experience for novices and 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.

Demo Android app using BBBAndroid

The BBBAndroid project allows you to run Android on your favorite embedded Linux board. The next step for this project would be to get more people involved by showcasing some apps that can be run on Android which make use of the awesome peripherals of the BeagleBone Black : GPIOs, i2c, spi, CAN, ADC, etc.
Exact problem definition could be defined by the student
A good place to start is this website.
Goal: Build android app(s) that can be run using BBBAndroid.
Hardware Skills: Basic knowledge of digital circuits.
Software Skills: Some experience with Android, C
Possible Mentors: Andrew Henderson, Anuj Deshpande

NW.js (a.k.a 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, Julian Duque

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.

This is a proposal, Jason Kridner needs to give the OK for this.
Goal: Get the source code http://diegotc.github.io/bone101/Support/GSOC/views/index.html of last year of the GSOC program and continue making changes for this new year program. One of the main objectives will be to include the Beaglebone-UI embedded on the cards. Right now you can run programs that use the bonescript library. A new function of the platform could be that it allows users to also run programs on other languages like python or ruby. Fixed some design issues with current source code and find the best way to maintained all information on gist.github.com Taking in consideration big images can't be uploaded right now.
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, Diego Turcios, Julian Duque

Android-based remote display

Extend last years project with support for keyboard, mouse and sound. The project is composed of 2 subprojects: a kernel framebuffer+usb driver and a Java application. The basic video interface is in place and tested but the project lacks user input support.

Goal: Improve the existing project and add support for keyboard, mouse and sound
Existing Project: Android application, Kernel framebuffer driver
Hardware Skills: Some knowledge of USB
Software Skills: Java, C and Android. Possible mentors: Vladimir Pantelic, Jason Kridner, Vlad Ungureanu, Praveen Kumar Pendyala (last year GSoCer), Andrew Henderson

Where to start? This could be a good start.

Cross platform USB boot

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

Extend BBB Linux flasher to support Windows, Mac and Linux hosts. The support for the BB{B/W} is in place but needs adaptation for Windows/Mac. The BeagleBoard X15 uses another way of USB booting Peripheral Booting on the X15.

The project can be extended to automatically flash a board and then start executing tests in a CI environment. Another addition can be a cross-platform UI written using QT for easier portability.

Goal: Download a Linux image from the web and boot a BeagleBoard 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, libusb and familiarity with Mac, Linux and Windows
Possible mentors: Vladimir Pantelic, Jason Kridner, Vlad Ungureanu

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, Andrew Henderson

Automated testing for BeagleBone and BeagleBone Black

Produce code samples and test harness 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, Matt Porter and Jason Kridner

Previous ideas

Mentors

Name IRC nickname Melange name Native language Other languages Timezone Software help Hardware help Focus projects
Jason Kridner jkridner beagleboard 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
Vlad Ungureanu vvu ungureanuvladvictor Romanian English GMT +2 Linux, C, Android, U-Boot, build-systems, USB - Cross-Platform USB Boot, Android Based Display
Hunyue Yau ds2 hygsoc English - US Pacific Android, C, Linux, scripting, Kernel Yes -
Tom Rini Tartarus trini English - US Eastern C, u-boot, OpenEmbedded - U-Boot or OpenEmbedded development
Pantelis Antoniou panto panto Greek English GMT+2 Linux Kernel, S/W Architecture - Embedded Linux architecture fixes
Deepak Karki karki karki English Hindi, Kannada IST PRU drivers, Python userspace libraries - PRU Bridge, PyBBIO
Kumar Abhishek Abhishek_ Abhishek-Kakkar English Hindi IST PRU, Linux Kernel Programming Yes PRUSS Support for newer kernels
Alexander Hiam alexanderhiam alexanderhiam English - US Eastern Python, C, Linux Kernel Prototyping, design, layout, debugging PRU Bridge, PRUSS Support for the newer kernels
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 English Latin ;) US Pacific
Charles Steinkuehler cdstienkuehler
Steve French VoltVisionFrenchy voltvisionfrenchy
Anuj Deshpande anujdeshpande anujdeshpande English German, Hindi IST / GMT-530 C, Python, JS
Diego Turcios DiegoTc DiegoTc Spanish English US Center JS, Node, Javascript Improving initial experience for novice developers
Praveen Kumar Pendyala praveendath92 praveendath92 English Hindi, Telugu CET / GMT +2 C, Linux Kernel, Android, Java Android Based Display
Robert Nelson rcn-ee English US Central C, Linux Kernel, U-Boot, Bash, Ubuntu/Debian Root File System
Kassandra Perch nodebotanist nodebotanist English --- Central Standard US Javascript (Node, client-side, Johnny-Five, NW/node-webkit), little bit of C. Wiring, soldering getting-started app, bonescript development
Andrew Henderson hendersa hendersa English US Eastern C, C++, ARM asm, Linux, Linux kernel, Android Prototyping Android, Linux multimedia
Julian Duque julianduque julianduque Spanish English EST / GMT-5 JavaScript (Node.js/io.js, Frontend, Johnny-Five, NW/node-webkit), Linux Getting Started App, BoneScript development, Node.js/io.js update on build images
Steve Arnold nerdboy / mr_science sarnold English - US Western (PST8PDT) u-boot, kernel, Linux OS build/deploy, bash, Python, etc basic prototyping/debugging, high-level I2C/SPI sensor interfaces Satellites, cameras, remote sensor platforms, weather stuff
Víctor Mayoral vmayoral vmayoral English, Spanish - CET kernel, Snappy Ubuntu Core, APM, ROS drones, copters, planes, rovers Erle Robotics
Alejandro Hernández ahcorde ahcorde English, Spanish - CET CV, Snappy Ubuntu Core, APM, ROS drones, copters, planes, rovers, camera design Erle Robotics
Iñigo Muguruza imuguruza imuguruza English, Spanish, Portuguese - CET kernel, Debian, APM, ROS drones, copters, planes, rovers, PCB design Erle Robotics
Victor calculus calculus English - PDT Linux, C/C++, Java, ROS, Gentoo sensors (SPI/I2C), microcontrollers
Marshall Culpepper marshall_law marshall_law English - US Central Linux, C/C++, FreeRTOS, Javascript, Python Prototyping CubeSat and HAB applications
Previous mentors