BeagleBoard/GSoC/Ideas-2021

=Welcome!= BeagleBoard.org is applying to be a mentoring organization in the Google Summer of Code for 2018! Below, we're collecting project ideas for the GSoC-2018.

What is Google Summer of Code?
Spend your summer break writing code and learning about open source development while earning money! Accepted students work with a mentor and become a part of the open source community. Many become lifetime open source developers! The 2018 student application window is open March 27th 2018!

Google Summer of Code is open to post-secondary students, age 18 and older in most countries.

Read more on the GSoC site and the FAQ.

BeagleBoard.org 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 1,000,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 and is available for about $25 through over 30 distributors world-wide (and is even available at Micro Center 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 PocketBeagle and either a BeagleBone Black Wireless, BeagleBone Black, BeagleBone Blue, SeeedStudio BeagleBone Green, SeeedStudio BeagleBone Green Wireless or BeagleBoard-X15 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 be invited by an administrator to register on the GSoC site and request to be a mentor for BeagleBoard.org.

General requirements
All projects have the following basic requirements:
 * 1) Students must create accounts on Github, eLinux, Freenode and Google Groups prior to creating their application.
 * 2) All newly generated materials must be released under an open source license.
 * 3) Individual students shall retain copyright on their works.
 * 4) 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://bbb.io/gsocchat 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.
 * 5) 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.
 * 6) Students will demonstrate their ability to collaborate by creating an eLinux wiki page for their proposal and utilizing Freenode to collect quotes regarding the usefulness of their proposal to the BeagleBoard.org community. The wiki timestamp will help mentors recognize the provenance of ideas from prospective students. Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously.
 * 7) Source code generated during the project must be released on Github (to be cloned to github.com/beagleboard or merged with appropriate upstream project upon successful completion).
 * 8) 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 the  beagleboard-gsoc Google Group. Each status report should outline:
 * 9) what was accomplished that week,
 * 10) any issues that prevented that week's goals from being completed and
 * 11) your goals for the next week.
 * 12) 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. There is no requirement to show your faces or use English.

Idea template
Description

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

=Ideas=

Offline SmartSpeaker with BeagleBone
Goal: The big picture goal is a entire offline smart speaker system using a BeagleBone (or another member of the Beagle family. Within the timeframe of GSoC, the goal is to have a piece (open to definition in the application) of the smart speaker system implemented. Most current implementations of a smart speaker system perform most of the processing in the cloud. This has a lot of potential ramifications including but not limited to privacy and other abuses of the dataset. The purpose of this is to provide a possible offline implementation. Piece to focus on for this project are: Trigger word detection and Voice recognition. Ideally, this should run on the Cortex-A8 based Beagles (BeagleBone, BeagleBoard Classic, BeagleBoard Xm) for maximum flexibility. The BeagleBones can initially use a USB sound card.   Hardware Skills:  Minimal. Ability to connect a microphone and speaker '' Software Skills'': C/C++ programming mainly. Ability to work with different build systems (Cmake/autoconf/etc). ; Linux device drivers Possible Mentors: Hunyue Yau Upstream Repository: References:

Update PRU Python loader
Goal: Provide an update to PyPRUSS to support remote-proc loading and the latest BeagleBone images. Hardware Skills: Minimal '' Software Skills'': Linux, C and Python programming Possible Mentors: Jason Kridner, Kumar Abhishek Upstream Repository: https://github.com/beagleboard/linux, https://github.com/beagleboard/pypruss References: https://bitbucket.org/intelligentagent/pypruss, https://beagleboard.org/latest-images

Connected PocketBeagle
Goal: Have reference application notes, code, example, and “How-To” document for each type of wireless communications for PocketBeagle. Wireless protocols should include at a minimum: 802.11 (WiFi), BLE, Cellular (GSM or LTE), NFC, ZigBee and GPS. Each should have easy to use references for users building projects to use as a cut/paste library. Hardware Skills: Prototyping skills with MikroElektronika Click Boards '' Software Skills'': C and Python programming;  Linux device drivers Possible Mentors: Upstream Repository: https://github.com/beagleboard/linux References: https://www.mikroe.com/click/wireless-connectivity, https://github.com/beagleboard/bb.org-overlays, https://github.com/beagleboard/linux

Getting Started Materials for PocketBeagle
Goal: Update the BeagleBone getting started materials for PocketBeagle. This includes having Bone101 updated to work with PocketBeagle and updates BeagleBone Blue Control Libraries to work with PocketBeagle. Hardware Skills: Basic prototyping skills Software Skills: C, Assembly, and JavaScript programming. Linux Possible Mentors: Jason Kridner '' Upstream Repository'': https://github.com/beagleboard/bone101 '' References'': https://beagleboard.org/support/bone101 and http://strawsondesign.com/#!manual-source-code

Modern “Speak & Spell” using PocketBeagle
Goal: To celebrate the 40th anniversary of the “Speak & Spell” from Texas instruments, create an updated “Speak & Spell” using a PocketBeagle. This should be a general Linux application that can be reproduced and should not be a one-off build. Hardware Skills: Prototyping / Re-braining electronics Software Skills: C and Python programming; Linux '' Possible Mentors'': '' Upstream Repository'': '' References'': https://en.wikipedia.org/wiki/Speak_%26_Spell_(toy)

BeagleBone Audio Platform
Goal: BeagleBone and/or BeagleBoard-X15 as Audio Platform (e.g. effects box for musicians) Hardware Skills: New audio and hardware UI capes Software Skills: Audio and UI applications Possible Mentors: Robert Manzke, Henrik Langer, tbd Upstream Repository: Beagle Kernel or Use Case repo References: Audio Project from 2016 BeagleBoard/GSoC/2016_Projects, CTAG face2|4, http://bela.io/, Beagle Audio Cape

BeagleBone synchronous data collection
Goal: Synchronous data collection via the PRU. This complements BeagleLogic which asynchronously acquires data. Hardware Skills: Understanding of a synchronous signal Software Skills: C and assembly programming Possible Mentors: Hunyue Yau, Kumar Abhishek Upstream Repository: References: BeagleLogic from prior years.

BeagleBone GPU offload
Goal: Sample programs to utilize the GPU for computations. The GPU on most of the BeagleBone/Board are limited to OpenGL ES 2; Goal is to provide sample programs to show using GLES2 for computations. Hardware Skills: N/A Software Skills: OpenGLES Possible Mentors: Hunyue Yau Upstream Repository: possibly thebookofshaders References: http://thebookofshaders.com/

BeagleBone/Beagle board PRU DMA
Goal: Create a sample program to demostrate using EDMA on the PRU to transfer data to and from the main (DDR) memory with a Linux host. Most existing code utilizes(wastes) the 2nd PRU on the PRUSS for data xfer. Using DMA can allow the PRU to be used for other purposes. Hardware Skills: Datasheet/specification reading Software Skills: Assembly language programming/Linux kernel programming Possible Mentors: Hunyue Yau Upstream Repository: N/A References: N/A

BeagleBone Remote Seismometer Node
Goal: Working prototype remote strong motion sensor, web-based control and display. Determine "best" sensor library interface, integrate accelerometer output with QCN client software. Hardware Skills: Datasheet/specification reading, patch cables/breadboard Software Skills:Python, C++, C programming, basic understanding of serial buses, sensors and data, physical principles Possible Mentors: Stephanie Lockwood-Childs, Steve Arnold Upstream Repository: QCN Client References: quake catcher network, generic project desc. , BeagleBone Green , PRU-ICSS

BeagleBone Sonic Anemometer / Basic Weather Station
Goal: Working prototype sonic anemometer using BeagleBone, high speed DAC (eg, PRUDAQ), and ultrasonic sensors. Analyze methods for accuracy/sensitivity (eg, time-of-flight vs. phase difference) and implement "best" method. Use PRUs for independent real-time control of ultrasonics. Example architecture and software on github (see repos and references below) Hardware Skills: Datasheet/specification reading, patch cables/breadboard/soldering (at least two), serial/debug Software Skills: C/assembly and python programming, basic understanding of serial buses, sensors and data, physical principles Possible Mentors: Stephanie Lockwood-Childs, Steve Arnold Upstream Repository: beagle-sonic from prior years, also UChSonicAnemometer from Univ of Chile. References: PRU-ICSS, sonic anemometer basics

BeagleBone Cubesat Software/Platform Integration
Goal: Integrate BeagleSat "satellite" platform with existing MAVLink/autopilot framework, including previous GSoC BeagleSat magnetometer application. Determine best autopilot platform for BeagleBone (mainly begalepilot vs. apm2) based on science experiment needs; using BeagleSat project magnetic field measurements as example, requirements include SPI burst data reads from 2 independent magnetometers (ie, use BBIO MPU9250 SPI driver for data acquisition). Integrate navigation model with autopilot firmware and selected Beaglebone hardware and data acquisition example. Hardware Skills: Datasheet/specification reading, soldering/prototyping, serial/debug Software Skills: high-level language skills (Python, C, etc), some knowledge of micro-controller compilers and targets, kernel config/programming and serial bus interfaces (some) Possible Mentors: Stephanie Lockwood-Childs, Steve Arnold Upstream Repository: BeagleSat, MAVLink , BeaglePilot References: BeagleBone Blue board features, Building (ardupilot) for BeagleBone Black on Linux , MAVLink Commands

BeagleBone-based Serial Terminal Server
Goal: Often in embedded development it is valuable to have a serial terminal server which can retain a serial port connection along with buffered past I/O separate from a typical host PC, either for longer term logging of serial port data or to enable remote management of a device via serial port. Commercial units which have this capability are very expensive. The BeagleBones have 4 highly capable UARTs exposed besides UART0 through the cape connectors and a simple cape hardware could easily enable a BeagleBone to physically have all the interfaces needed to be a serial terminal server. The cape hardware does not need to be created for this project to go forward, so long as other devices which connected to the BeagleBone terminal server used 3.3 V UARTs themselves.

This project would begin with a survey of existing software which could be adapted to provide a terminal server experience (for example something as simple as using GNU screen with some adaptations over an SSH connection to the BeagleBone) and then proceed to create software changes needed to enable such operation in an easy to use and deploy way. This resulting (or found) software would likely end up being generic for Linux based serial terminal servers. The end result of this project should likely be an easy to deploy SD card image to enable someone to setup a low cost serial terminal server based on a BeagleBone in only a few minutes.

A reach goal would be to enable the cape hardware and also to potentially provide DC relays which could switch 5-12 V at 2-3 A such that development boards could be powered on and off through the same software interface as is used for the serial communications. Since hardware is not the focus of GSoC, actual development of such hardware should not be the focus of the project itself. Hardware Skills: Datasheet/specification reading Software Skills: C programming/Linux kernel programming Possible Mentors: Michael Welling Upstream Repository: N/A References: N/A

PRUs to offload processing of raw data from on-board Peripherals
Goal: The goal is to be able to access on-board peripherals like the McSPI, McASP etc from the PRUs and to be able to use fetch data directly from these peripherals. This will allow to offload processing of the Raw data onto the PRUs. The project will basically involve developing C libraries for the PRUs to connect to these peripherals, developing DT overlays for the peripherals to be used and developing Drivers to reserver the device on behalf of the PRUs. Hardware Skills: Datasheet/Specification reading Software Skills: C programming/Linux Kernel Programming, Assembly language Possible Mentors: Zubeen Tolani, tbd Upstream Repository: N/A 'References:'' pru-software-suppor-package

Integrate node-beagle-boot to Chrome plug-in
Modify node-beagle-boot's use of node-usb calls to allow them to be replaced by Chrome USB calls and create a Chrome plug-in around it. Goal: Boot PocketBeagle via a Chrome plug-in, download the latest image from beagleboard.org/latest-images and use the bootloaded PocketBeagle code to write that latest image to a microSD card. Hardware Skills: some familiarity with USB architecture, knowledge of what bootloaders do and basic embedded systems concepts Software Skills: JavaScript, Linux and browsers Possible Mentors: Jason Kridner Upstream Repository: TBD (https://github.com/beagleboard/node-beagle-boot) References: https://github.com/ravikp7/node-beagle-boot, https://github.com/ungureanuvladvictor/BBBlfs, https://developer.chrome.com/apps/app_usb

Integrate node-beagle-boot into Etcher.io
node-beagle-boot works stand-alone, but now we must complete the integration into the Etcher.io API. Goal: Etcher.io should boot a PocketBeagle into mass storage class mode and write the latest image from beagleboard.org/latest-images to a microSD. Hardware Skills: understanding bootloaders, knowledge of USB Software Skills: C, JavaScript (node.js) Possible Mentors: Jason Kridner Upstream Repository: TBD (https://github.com/beagleboard/node-beagle-boot) References: https://github.com/ravikp7/node-beagle-boot, Etcher.io API

Port BeagleBone USB-based bootloader server from C to JavaScript (node.js)
The BBBlfs project is capable of booting a BeagleBone into USB mass storage class mode. This will eventually be integrated into a variant of http://etcher.io to make an all-in-one BealgeBone flasher/updater. Goal: Booting BeagleBone into USB mass storage class mode should be as easy as 'npm install beaglebone-boot; cd node_modules/beaglebone-boot; npm start' and connecting the board with the BOOT button pressed via USB. Hardware Skills: understanding bootloaders, knowledge of USB Software Skills: C, JavaScript (node.js) Possible Mentors: Jason Kridner Upstream Repository: TBD (https://github.com/beagleboard/node-beaglebone-boot) References: https://github.com/ungureanuvladvictor/BBBlfs, https://boundarydevices.com/u-boot-usb-mass-storage-gadget/, https://github.com/tessel/node-usb

Re-purpose PiTop Power Interface for BeagleBone
Port power monitor and backlight software to Beaglebone SPI interface (using prototype power cable) and integrate with standard desktop power interface (upower/pm-utils dbus abstraction). Replace existing UI with desktop integration (ie, LXQT and XFCE power managers).

Goal: Battery status, power/backlight control on BeagleTop running standard Debian desktop. Hardware Skills: Datasheet/specification reading, wiring. Software Skills: C and Python, some knowledge of XDG desktop specification Possible Mentors: Michael Welling, Stephen Arnold, Stephanie Lockwood-Childs Upstream Repository: pi-top-install References: freedesktop.org specs hub assembly

Fix bugs in BoneScript
Run through the issues list at http://github.com/jadonk/bonescript/issues and fix them!

Goal: Close all issues. Hardware Skills: Wiring LEDs and simple sensors Software Skills: JavaScript and Linux Possible Mentors: Jason Kridner Upstream Repository: https://github.com/beagleboard/bonescript References: http://beagleboard.org/bonescript

Port am335x_pru_package to remoteproc
The am335x_pru_package is a community supported set of tools and examples on using the PRU. It includes an assembler and a C library for managing the PRU over UIO. The BeagleBoard community mostly desires to migrate PRU development to remoteproc to give the Linux kernel greater knowledge of the cores.

Goal: Move all examples to remoteproc, including adding elf support to pasm, adding an option to build using clpru and updating the C library to use the remoteproc interface for basic PRU control and using mmap for a limited set of communications functions. Hardware Skills: N/A Software Skills: C, assembly, Linux kernel Possible Mentors: Jason Kridner, Kumar Abhishek Upstream Repository: https://github.com/beagleboard/am335x_pru_package References: v5 examples TI Training Labs

Add BeagleBone Pinmux/Overlay Manger to Mainline U-Boot
Add a pinmux/overlay manager to U-Boot, similar to the old kernel pin manager used in 3.8.x/4.1.x kernels. This manager should read the 4 eeprom, auto load those capes, then also allow enable/disable/override functionality. Currently we run a nasty u-boot script to load each overlay with a very basic pin manager. (see references). Currently both the Pi and Chip boards in u-boot have a basic overlay manager already integrated.

Goal: Add a pinmux/overlay manager to U-Boot, for the BeagleBone family. Hardware Skills: N/A Software Skills: C, assembly, U-Boot Possible Mentors: Robert Nelson Upstream Repository: http://git.denx.de/?p=u-boot.git;a=summary References: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2018.01/0002-U-Boot-BeagleBone-Cape-Manager.patch

Create a PRU based soft-peripheral example
The PRU is a hard realtime co-processor with dedicated realtime pins. Previous GSoC have created an assortment of examples and foundation pieces. However, most of them have custom interfaces. This project is to tie things together to implement at least one example of using the PRU with a standard interface. For example, this can be a SPI master interface that can be bound with another peripheral via DT.

Goal: Create at least one non trivial example that includes both the PRU firmware and the kernel driver interface. Utilization of remoteproc (other means of loading the firmware will be considered provided it is appropriately justified) to load the firmware and control the PRU. A device driver should expose the functionality using standard kernel APIs. The example should NOT be a trivial one (i.e. GPIO controller, simple input events, plain on-off LEDs) unless proper justification is provided. Simple non trivial possible examples include SPI master, I2C master (potential HW issues), or UART. This project includes creating the relevant PRU firmware. Hardware Skills: Some understanding of I/O is needed esp if the I2C master is choosen. Software Skills: C, assembly, Linux kernel Possible Mentors: Hunyue Yau Upstream Repository: N/A References:

Reference Design For A GPIO-based Parallel Bi-Directional Bus
While the BeagleBone family has a large number of pins available on their P8/P9 headers, projects requiring a large amount of GPIO I/O may still be infeasible due to pinmux conflicts with other interfaces (SPI, UARTs, etc.). The newer PocketBeagle platform is even more restricted in the number of available GPIOs for interfacing. In addition, bi-directional bus communication using GPIOs is infeasible, as each GPIO is configured for either input or output. This project will combine your hardware and software skills to address these limitations by creating a shift register-based hardware design that will allow serial streams of data going in/out of the PocketBeagle or BeagleBone family GPIOs to be mapped into a bi-directional communications bus. Some practical uses of this are for GPIO-based game controller inputs (using *lots of buttons*), communication address/data buses for interfacing with older microcontrollers and microprocessors, and providing large numbers of logical bi-directional GPIOs.

Goal: Create a hardware design will incorporate shift registers (and potentially logic level converter solutions as appropriate) to allow BB.org hardware to communicate with hardware via a parallel, bi-directional bus. Create a software design that incorporates both a kernel driver to communicate with the parallel bus and a user space application/library using ioctl calls to communicate with this kernel driver. The kernel device tree fragment associated with the kernel driver shall configure it by specifying the number of parallel lines to use, the input/output/both direction of each bus signal, and the GPIOs allocated to the serial input/output/clock/latch signals. In addition, the device tree and kernel driver may also support specifying particular parallel bus lines as GPIO inputs that are mapped as GPIO keys. Hardware Skills: Basic digital logic (i.e. comfortable prototyping IC-based circuits on a breadboard, understanding of buses and signals, able to read/write/understand schematics), use of logic analyzer/multimeter/oscilloscope as needed for troubleshooting, ability to read component data sheets. Software Skills: C, kernel driver development, kernel device tree, interfacing with kernel drivers using ioctl calls from user space. Possible Mentors: Andrew Henderson Upstream Repository: TBD References: http://www.ti.com/lit/ds/sdfs071b/sdfs071b.pdf, https://www.arduino.cc/en/Tutorial/ShiftOut

=Mentors= Previous mentors