Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Difference between revisions of "BeagleBoard/GSoC/Ideas"

From eLinux.org
Jump to: navigation, search
(Mentors)
(me!)
Line 142: Line 142:
 
| Schematic Review + Design
 
| Schematic Review + Design
 
| ARM/AM335x/OMAP/PRU U-Boot and Kernel/Driver Development
 
| ARM/AM335x/OMAP/PRU U-Boot and Kernel/Driver Development
 +
|-
 +
| Koen Kooi
 +
| koen
 +
| Dutch
 +
| English
 +
| CET
 +
| Experienced on most areas of Embedded Linux, buildsystems
 
|}
 
|}

Revision as of 18:28, 25 March 2013


Welcome!

BeagleBoard.org hopes to be accepted as a mentoring organization in the Google Summer of Code for 2013!! Here we collect project ideas for the 2013 GSoC.

Background

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

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 about 150 people logged-in, 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 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 the BeagleBoard IRC or 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 300 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 ECE497 class project idea list.

Mentors wondering where to help

Please start by registering your idea below following the template given by the existing examples. Further, scroll down to the bottom and give everyone a bit of information about your expertise and availability by adding yourself to the table.

General requirements

All projects have the following basic requirements:

  1. 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 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 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.
  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 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 community.

Ideas

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.

SYSFS entries for IIO and PWM

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

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

PRU upstreaming

Remove HWMOD requirement for PRU so it be upstreamed to Linus's tree.

Goal: Push patches to Linux mainline providing support for the AM335x PRU
Existing project: http://github.com/beagleboard/kernel
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Able to write software in C, create patches to the Linux kernel and perform cross-compilation

PRU firmware loader

Allow firmware to be loaded directly on PRU cores and executed. This could be used by Cape Manager to load PRU cape specific applications .

Goal: Push patches to Linux mainline providing support to loading firmware on PRU cores and executing
Existing project: http://github.com/beagleboard/kernel
Hardware skills: Able to read schematics, understand basic digital logic and monitor logic-level digital signals
Software skills: Able to write software in C, create patches to the Linux kernel and perform cross-compilation

Secondary processor support (RPC/gcc/etc.)

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

Scripting libraries and web interfaces

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

Frameworks for open hardware projects

Consolidating support for simplified home manufacturing (CNC, 3D printers, laser cutters, pick-and-place machines, etc.), drones/bots (ROS, IMU, video streaming, etc.) or other common tasks.

Optimizations to existing userspace applications/libraries

Optimizations to applications and libraries like XBMC to make them run better on resource constrained environments or to take advantage of more specialized processing elements.

Mentors

Previous mentors

Name IRC nickname Native language Other languages Timezone Software help Hardware help Focus projects
Jason Kridner jkridner English - US Eastern JavaScript, C, u-boot wiring, timing diagrams, basic debug Bonescript development
Vladimir Pantelic av500 German English, Serbian CET Experienced on most areas of Embedded Linux, Multimedia Schematic Review + Design Embedded Linux, Linux Multimedia, Android
Matt Ranostay mranostay English 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 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