Difference between revisions of "BeagleBoard/GSoC/Ideas-2016"

From eLinux.org
Jump to: navigation, search
(Mentors)
(Mentors: Add Andrew Bradford)
(210 intermediate revisions by 35 users not shown)
Line 7: Line 7:
  
 
=Welcome!=
 
=Welcome!=
BeagleBoard.org hopes to be accepted as a mentoring organization in the [[BeagleBoard/GSoC|Google Summer of Code]] for 2013! Below, we've collected project ideas for the 2013 GSoC.
+
BeagleBoard.org hopes to be accepted as a mentoring organization in the [[BeagleBoard/GSoC|Google Summer of Code]] for 2016! Below, we've collected project ideas for the GSoC-2016.
  
 
==Background==
 
==Background==
BeagleBoard.org is a volunteer organization that seeks to advance the state of open-source software on [http://en.wikipedia.org/wiki/Open-source_hardware open-source hardware] platforms capable of running high-level languages and operating systems (primarily Linux) in embedded environments. Born from taking mobile phone processors and putting them on low-cost boards to build affordable desktop computers, BeagleBoard.org has evolved to focus on the needs of the "maker" community with greater focus on the I/O needed for controlling motors and reading sensors to build things like robots, 3d printers, flying drones, in-car computer systems and much more. Past BeagleBoard.org GSoC projects included [[BeagleBoard/GSoC/2010_Projects/C6Run|an RPC framework for heterogeneous processor communication]], [[BeagleBoard/GSoC/2010_Projects/USBSniffer|a transparent USB packet sniffer]], [[BeagleBoard/GSoC/2010_Projects/XBMC|ARM optimizations for XBMC]], [[BeagleBoard/GSoC/2010_Projects/FFTW|ARM optimizations for FFTs]], [[BeagleBoard/GSoC/2010_Projects/Pulse_Width_Modulation|make-shift pulse-width-modulation]] and [[BeagleBoard/GSoC/2010_Projects/OpenCV|RPC optimizations for OpenCV]]. BeagleBoard.org has benefited from sponsorship from Texas Instruments, CircuitCo, Digi-Key and others, but avoids any dependence on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 100,000 boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, Debian, ArchLinux, Gentoo, Buildroot and many more.
+
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.
 +
 
 +
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 Micro Center 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.
 
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.
Line 21: Line 23:
  
 
==Students looking for ideas==
 
==Students looking for ideas==
Student proposals can encompass projects inspired from the following list of ideas or can include personal project ideas. Previous Google Summer of Code projects show that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even if it is not on this list. We will be glad to help students develop ideas into projects via [http://webchat.freenode.net/?channels=beagle the BeagleBoard IRC] or [http://groups.google.com/group/beagleboard the BeagleBoard mailing list]. There are many potential project ideas and we will match students to projects based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.
+
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 300 existing projects listed at http://beagleboard.org/project. If you are interested in one of the projects listed on the BeagleBoard.org projects page, talk with the project members to see if there are any aspects of their projects that can be used 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-2012|last year's idea page]].
+
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-2015|last year's idea page]].
  
 
==Mentors wondering where to help==
 
==Mentors wondering where to help==
Please start by registering your idea below by following the template provided with the existing examples. Furthermore, scroll down to the bottom and give everyone a bit of information about your expertise and availability by adding yourself to the table.
+
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.
Line 36: Line 40:
 
# 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 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:
 
# 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 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.
 
# 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.
  
 
=Ideas=
 
=Ideas=
There are several areas needing contributions:<br>
+
==Linux kernel support for embedded devices and interfaces==
'''Kernel''': Improving the state of the Linux kernel including improved ARM/OMAP/Sitara platform support, simplifying the development of add-on hardware for embedded systems and exchanging hardware connectivity information with userspace.<br>
+
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.
'''Secondary processor support (RPC/gcc/etc.)''': Enabling usage of DSPs, PRUs, FPGAs, Cortex-M3s, Arduinos, MSP430 launchpads and other attached processing platforms.<br>
 
'''Scripting libraries and web interfaces''': Improving the Bonescript JavaScript library, web-based interface libraries, examples or alternatives in other languages.<br>
 
'''Frameworks for open-hardware projects''': Consolidating support for simplified home manufacturing (CNC, 3D printers, laser cutters, pick-and-place machines, etc.), drones/bots (ROS, IMU, video streaming, etc.) or other common tasks.<br>
 
'''Optimizations to existing userspace applications/libraries''': Optimizations to applications and libraries like XBMC to make them run better on resource constrained environments or to take advantage of more specialized processing elements.<br>
 
  
==Upstreaming Beagleboard.org Kernel Patches==
+
===Idea template===
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.
+
Description
 
<br>
 
<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>
+
''Goal:'' <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:'' <br>
''Hardware Skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals.<br>
+
''Software Skills:'' <br>
''Software Skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation and testing.<br>
+
''Possible Mentors:''<br>
''Possible mentors:'' Matt Porter, Matt Ranostay, Koen Kooi, Alan Ott<br>
+
''Upstream Repository:'' <br>
 
+
''References:'' <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:''<br>
 
''Existing Project:''<br>
 
''Hardware Skills:''<br>
 
''Software Skills:''<br>
 
''Possible mentors:''<br>
 
 
 
==node-webkit based cross-platform getting-started app==
 
''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<br>
 
 
 
==OpenEmbedded support for npm packages for node.js==
 
Using npm for packages works well for grabbing most recent versions of things, but it doesn't work well to make sure you are getting tested versions built for your platform, it doesn't integrate with the native package manager, it is a huge security hole and it generally is a mess for distributions. OpenEmbedded provides a great vehicle for creating distributions that can professionally support deploying node.js packages rather than relying on a tool that is really only geared for prototyping.
 
 
 
* Create a bitbake 'npm' class
 
* Cross-build native code using node-waf, node-gyp and nw-gyp
 
* Create dependencies using package.json
 
 
 
''Goal:''<br>
 
''Existing Project:''<br>
 
''Hardware Skills:''<br>
 
''Software Skills:''<br>
 
''Possible mentors:''<br>
 
 
 
==Bonescript web pages with live-running examples and documentation==
 
 
 
''Goal:''<br>
 
''Existing Project:''<br>
 
''Hardware Skills:''<br>
 
''Software Skills:''<br>
 
''Possible mentors:''<br>
 
 
 
==Integrate support libraries into Angstrom==
 
Many BeagleBone and embedded Linux support libraries in various programming languages exist as projects that aren't included in the distro shipped with BeagleBoard and BeagleBone. These need bitbake recipes added to meta-beagleboard such that they can be easily downloaded and incorporated into the shipping distro.
 
 
 
* Python PyBBIO
 
* Ruby beaglebone-ruby
 
* Perl bonelib
 
 
 
''Goal:''<br>
 
''Existing Project:''<br>
 
''Hardware Skills:''<br>
 
''Software Skills:''<br>
 
''Possible mentors:''<br>
 
 
 
==SYSFS entries for IIO and PWM==
 
IIO and PWM provide mechanisms for sampling touch screens, performing general purpose A/D conversions to read sensors, generating voltage levels and driving motors. The Linux kernel SYSFS mechanism provides a simplified mechanism for userspace applications to set parameters and read/write data values.
 
 
 
''Goal:'' Push patches to Linux mainline providing SYSFS entries for IIO and PWM useful for building a demo robot<br>
 
''Existing project:'' http://github.com/beagleboard/kernel<br>
 
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 
''Software skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation<br>
 
''Possible mentors:'' TBD<br>
 
 
 
==Using BeagleBone PRUs to control CNC and 3D printer stepper motor Drivers==
 
This project is to write code for the PRU (realtime processors on the AM335x used in the Beagle Bone) so that it can generate multiple step and direction outputs based on a queue of commands in real time. This needs to be done in real time so the acceleration and coordination of multiple stepper motors can be controlled and coordinated. A step/dir signal is commonly used in a lot of stepper motor drivers. While it is possible to generate stepper phase information from the PRU, it is also undesireable from a testing stand point. An example of a reason for doing this is controlling the X/Y directions of the head of a 3D printer so that it can generate precise curves. While similar code has been done, it is not done in a real time fashion so it is difficult to add coordination between motors and/or maintain a known acceleration.<p>
 
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.
 
''Goal'': create code to use the AM335x PRUs to generate multiple step and direction outputs for reprap and CNC applications<br>
 
''Existing project'': Pru Documentation, 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:'' Tom King<br>
 
 
 
==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<br>
 
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br>
 
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
 
''Software skills:'' Able to write software in C, create patches to the Linux kernel and perform cross-compilation<br>
 
''Possible mentors:'' TBD<br>
 
 
 
==PRU firmware loader==
 
Allow "firmware" which are really compile 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<br>
+
==Heterogeneous co-processor support in open source operating systems and libraries==
''Existing project'': https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/<br>
+
Enabling usage of DSPs, PRUs, FPGAs, Cortex-Ms, Arduinos, MSP430 launchpads and other attached processing platforms.
''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>
 
  
==PRU virtual machine==
+
==Interesting Applications for PRU/DSP Processing==
Based on Chris Roger's URAPI 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 command to perform delay, pinMode, attachInterrupt, analogRead, analogWrite, digitalRead and digitalWrite functions. A simple conditional goto is resolved at load-time and a minimal set of variables are available for use. Support will need to be included for simple expressions, but the pre-parser can break them down ahead of time. Introspection in JavaScript should be used to convert a minimal function definition into source to be fed to a parser and passed to the interpreter on the PRU via shared memory.
 
  
''Goal'': Implement a URAPI interpreter that off-loads hard real-time tasks from Bonescript onto the PRU and include that in the Bonescript project<br>
+
==Sample PRU code interfacing with other kernel interfaces==
''Existing projects'': http://github.com/beagleboard/am335x_pru_package, http://github.com/jadonk/bonescript, Chris' Arduino implementation<br>
+
Write sample code to demostrate how data to and from the PRU can be exposed via standard user interfaces. Possible samples include:
''Hardware skills:'' Able to read schematics, understand basic digital logic and monitor logic-level digital signals<br>
+
* Expose the PRU as a I2C/UART/SPI etc. The would act as a bitbang I2C master interface that other I2C drivers can leverage.
''Software skills:'' Able to write software in JavaScript and assembly<br>
+
* Expose data from the PRU as an IIO, input, and/or character device.
''Possible mentors:'' Jason Kridner<br>
+
The goal is to show the 2 pieces (kernel + PRU firmware) needed to use the PRU as a "normal" HW.
 +
Most likely this will have to use the remote proc interface.
  
==Android-based boot host==
+
==Linux userspace support of embedded devices and interfaces in high-level languages==
Boot your BeagleBone using your Android phone. Combined with the Android Accessory Development Kit code available for BeagleBone and an application to help code/run small applications, this gives you a complete development environment that is easy to distribute to other users.
+
Improving the Bonescript JavaScript library, the PyBBIO Python library, Userspace Arduino, web-based interface libraries, examples or alternatives in other languages.
  
''Goal:''<br>
+
==Improving initial experience for novice developers==
''Existing Project:''<br>
+
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.
''Hardware Skills:''<br>
 
''Software Skills:''<br>
 
''Possible mentors:''<br>
 
  
==Android under Angstrom==
+
=Previous ideas=
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.
+
* [[BeagleBoard/GSoC/Ideas-2015]]
 
+
* [[BeagleBoard/GSoC/Ideas-2014]]
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.
+
* [[BeagleBoard/GSoC/Ideas-2013]]
 
+
* [[BeagleBoard/GSoC/Ideas-2012]]
''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:'' TBD<br>
 
  
 
=Mentors=
 
=Mentors=
 
[[BeagleBoard/GSoC/Ideas-2012#Mentors|Previous mentors]]
 
 
 
{| border="1"
 
{| border="1"
 
! Name
 
! Name
 
! IRC nickname
 
! IRC nickname
 +
! Melange name
 
! Native language
 
! Native language
 
! Other languages
 
! Other languages
Line 212: Line 100:
 
| Jason Kridner
 
| Jason Kridner
 
| jkridner
 
| jkridner
 +
| beagleboard
 
| English
 
| English
 
| -
 
| -
Line 217: Line 106:
 
| JavaScript, C, u-boot
 
| JavaScript, C, u-boot
 
| wiring, timing diagrams, basic debug
 
| wiring, timing diagrams, basic debug
| Bonescript development
+
| BoneScript development
 
|-
 
|-
| Vladimir Pantelic
+
| Hunyue Yau
| av500
+
| ds2
| German
+
| hygsoc
| English, Serbian
 
| CET
 
| Experienced on most areas of Embedded Linux, Multimedia
 
| Schematic Review + Design
 
| Embedded Linux, Linux Multimedia, Android
 
|-
 
| Matt Ranostay
 
| mranostay
 
| English (U.S. Midwestern Dialect)
 
| None
 
| US Pacific Time
 
| Experienced on most areas of Embedded Linux or Systems
 
| Schematic Review + Design
 
| ARM/AM335x Kernel Development
 
|-
 
| Philip Balister
 
| Crofton
 
| -
 
| -
 
| -
 
| -
 
| -
 
| -
 
|-
 
| Russ Dill
 
| Russ
 
| English
 
| None
 
| US Pacific Time
 
| Experienced on most areas of Embedded Linux or Systems
 
| Schematic Review + Design
 
| ARM/AM335x Kernel Development
 
|-
 
| Matt Porter
 
| mdp
 
| English (U.S. Midwestern Dialect)
 
| None
 
| US Eastern
 
| Embedded Linux Firmware/Kernel and system level design. Designing Linux drivers to make the best use of existing infrastructure.
 
| Schematic Review + Design
 
| ARM/AM335x/OMAP/PRU U-Boot and Kernel/Driver Development
 
|-
 
| Koen Kooi
 
| koen
 
| Dutch
 
| English
 
| CET
 
| Experienced on most areas of Embedded Linux, buildsystems
 
| -
 
| -
 
|-
 
| Tom King
 
| ka6sox
 
| English
 
| None
 
| US Pacific Time
 
| Experienced on most areas of Embedded Linux or Systems
 
| Schematic Review + Design, Board Layout
 
| ARM/AM335x Kernel Development
 
|-
 
| Jayneil Dalal
 
| jayneil
 
| English
 
| Hindi, Gujarati
 
| US Central Time
 
| Basic Embedded Linux, Documentation
 
| -
 
| Application based hw/sw projects on the Beaglebone
 
|-
 
| Laine Walker-Avina
 
| Ceriand
 
 
| English
 
| English
 
| -
 
| -
 
| US Pacific
 
| US Pacific
| C, Assembly, Buildroot, Reprap
+
| Android, C, Linux, scripting, Kernel
| USB protocol & logic analyzers, Various JTAG probes, 3d printer
+
| schematics, wiring, EE details
| OpenOCD, bootloaders, Linux kernel, Reprap firmware
+
| Kernel/HW
 
|-
 
|-
| Alan Ott
+
| Anuj Deshpande
| alan_o
+
| anujdeshpande
| American English (Central Florida Dialect)
+
| anujdeshpande
| American English (Midwestern Dialect)
 
| US Eastern (EDT)
 
| Linux Kernel, Firmware
 
| Breadboard wire-jamming
 
| 802.15.4 Wireless, USB
 
|-
 
| Hunyue Yau
 
| ds2
 
 
| English
 
| English
 
| -
 
| -
| US Pacific
+
| UTC+530
| Android, C, Linux, scripting
+
| C, Python, Golang
| Yes
+
| Schematics
| -
+
| Arduino, Android
 +
|
 
|-
 
|-
| Tom Rini
+
| Andrew Bradford
| Tartarus
+
| bradfa
 +
| bradfa
 
| English
 
| English
 
| -
 
| -
 
| US Eastern
 
| US Eastern
| C, u-boot, OpenEmbedded
+
| C, Linux, U-Boot
| -
+
| KiCad, some RF
| U-Boot or OpenEmbedded development
+
| DSP/PRU/M4 communication from Linux, wifi, USB gadget
 
|-
 
|-
| Luis Gustavo Lira
+
| Name
| lglira
+
| IRC nickname
| Spanish
+
| Melange name
| English
+
| Native language
| GMT/UTC -5
+
| Other languages
| Embedded Linux, C, Android
+
| Timezone
| Design, Debug, Wiring
+
| Software help
| Projects on the BeagleBone
+
| Hardware help
|-
+
| Focus projects
| Derek Molloy
 
| molloyd
 
| -
 
| GMT (London)
 
| C++, Java, Embedded C/C++
 
| Digital Circuits, Interfacing to Sensors
 
| Beaglebone Applications, Linux Multimedia, Embedded Linux
 
 
|}
 
|}
 +
[[BeagleBoard/GSoC/Ideas-2015#Mentors|Previous mentors]]

Revision as of 08:17, 12 February 2016


Welcome!

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

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 Micro Center 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.

Idea template

Description

Goal:
Hardware Skills:
Software Skills:
Possible Mentors:
Upstream Repository:
References:

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

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

Interesting Applications for PRU/DSP Processing

Sample PRU code interfacing with other kernel interfaces

Write sample code to demostrate how data to and from the PRU can be exposed via standard user interfaces. Possible samples include:

  • Expose the PRU as a I2C/UART/SPI etc. The would act as a bitbang I2C master interface that other I2C drivers can leverage.
  • Expose data from the PRU as an IIO, input, and/or character device.

The goal is to show the 2 pieces (kernel + PRU firmware) needed to use the PRU as a "normal" HW. Most likely this will have to use the remote proc interface.

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.

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.

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
Hunyue Yau ds2 hygsoc English - US Pacific Android, C, Linux, scripting, Kernel schematics, wiring, EE details Kernel/HW
Anuj Deshpande anujdeshpande anujdeshpande English - UTC+530 C, Python, Golang Schematics Arduino, Android
Andrew Bradford bradfa bradfa English - US Eastern C, Linux, U-Boot KiCad, some RF DSP/PRU/M4 communication from Linux, wifi, USB gadget
Name IRC nickname Melange name Native language Other languages Timezone Software help Hardware help Focus projects

Previous mentors