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

From eLinux.org
Jump to: navigation, search
(Mentors: Add Andrew Bradford)
(519 intermediate revisions by 64 users not shown)
Line 1: Line 1:
 
[[Category: Linux]]
 
[[Category: Linux]]
 
[[Category: OMAP]]
 
[[Category: OMAP]]
== Summer code of ideas for 2009 ==
+
[[Category: BeagleBoard]]
This page collects ideas for [[BeagleBoard]] specific [[BeagleBoard/GSoC|Google Summer of Code 2009]].  Some additional ideas can be found on the [[BeagleBoard/contest| BeagleBoard contest page]] and the [http://beagleboard.org/project BeagleBoard project page].
+
[[Category: GSoC]]
  
Student proposals should expand on these projects, or students are free to propose their own project.  From reading about previous Summer of Code, the key to success are people passionate about their project, so propose something that is extremely interesting to you, even if it not on the list. We will be glad to talk about your ideas on irc or the mailing list.
+
__TOC__
  
== Ideas ==
+
=Welcome!=
 +
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.
  
=== NEON Support for FFTW ===
+
==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/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.
  
[http://www.fftw.org| FFTW] is a library for calculating the [http://mathworld.wolfram.com/FastFourierTransform.html| Fast Fourier Transform]. The current implementation of FFTW contains SIMD optimizations for several instructions sets. It should be possible to add optimizations for the NEON SIMD co-processor in the Beagle Board. FFTW is widely used in the open source sommunity and this project would make FFTW far more useful on processors with NEON instructions. The mentor is particularly interested in improving GNU Radio on the OMAP3 and improving FFTW performance would be very useful.
+
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.
  
=== Codec Engine (C64x+) implementation of Ogg Theora ===
+
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.
  
There was a Neuros GSoC project to port Ogg Theora to the C64x+ last year, but it was never finished. See the [http://wiki.neurostechnology.com/index.php/Summer_of_Code_2008/Ogg_Theora_Codec Neuros project page] to understand the status.
+
'''''<span style="color:red">Every accepted student will be sent a BeagleBone Black before the first week of coding for testing their project.</span>'''''
  
=== Voice recognition integrated into Ubiquity ===
+
Additional hardware will be provided depending on need and value.
  
Integrate Mozilla Firefox, Mozilla Ubiquity, and voice recognition on the BeagleBoard with a microphone. Use of a Wiimote could provide additional interactive capabilities.
+
For more information, check out http://beagleboard.org and http://beagleboard.org/brief.
  
=== Audio-based translator ===
+
==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.
  
Utilizing voice recognition on the BeagleBoard with a microphone, submit text to Google Translator, then perform text-to-speech.
+
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]].
  
=== Spectrum analyzer using the DSP ===
+
==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.
  
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.
+
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.
  
=== USB sniffer ===
+
==General requirements==
 +
All projects have the following basic requirements:
 +
# 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].
 +
# Individual students shall retain copyright on their works.
 +
# 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.
 +
# 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,
 +
## any issues that prevented that week's goals from being completed and
 +
## your goals for the next week.
 +
# 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.
 +
# 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.
  
Come up with a USB sniffer solution. Idea is that the device to be sniffed is connected to the USB host port of the beagle and the beagle itself to the original host. The beagle will pass-trhu all usb data while logging that data. This could be a great help diagnosing USB problems or reengineering USB communication to a device (by logging the behaviour of a device when connected to a PC (software solutions for that exist too (usbsnoop), but a hardware solution could also support replay etc.
+
=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.
  
=== USB device audio support ===
+
===Idea template===
 +
Description
 +
<br>
  
The Linux USB gadget infrastructure doesn't have audio device class support (but Linux does have [http://www.linux-usb.org/USB-guide/x319.html USB host audio] support.  There is some work on a [http://docs.blackfin.uclinux.org/doku.php?id=gadget_midi gadget MIDI audio driver].  Some work has been done over at [http://blackfin.uclinux.org/gf/project/uclinux-dist/tracker/?action=TrackerItemEdit&tracker_item_id=4212 Blackfin], but is reported as not working very well.  Getting USB isochronous endpoint, gadget audio driver connected to audio on BeagleBoard would be beneficial to all OMAP3 isochronous USB needs, better isochronous gadget support in Linux (there are no standard gadgets test for isochronous endpoints), and a prove out a real gadget driver that requires isochronous endpoints.  Anyone wanting to learn about communication protocols, a well designed layered communication implementation, and a chance to work at the driver level will enjoy this project.
+
''Goal:'' <br>
 +
''Hardware Skills:'' <br>
 +
''Software Skills:'' <br>
 +
''Possible Mentors:''<br>
 +
''Upstream Repository:'' <br>
 +
''References:'' <br>
  
=== Touchscreen and LCD open hardware design ===
+
==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.
  
BeagleBoard rev C has a new connector for attaching an LCD.  The Touchscreen and LCD open hardware design project would consist of a schematic, PCB layout, and bill of materials that can be purchased easily over the Internet.  On online PCB fab could make the PCBs cheaply.  Only a soldering iron should be needed to populate the PCB.  Once built, the user could connect the PCB to their BeagleBoard had have an LCD with touchscreen support.  This project is targeted toward those interested in hardware and shouldn't require any complex software if a well supported touch screen controller chip is selected.
+
==Interesting Applications for PRU/DSP Processing==
  
=== OpenCV DSP accelleration ===
+
==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.
  
Research and implement hardware acceleration for OpenCV using the DSP on beagleboard. The DSP side needs to use xdais so other DSP programs can run at the same time.
+
==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.
  
=== Power Aware Computing APIs ===
+
==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.
  
Power consumption is a major problem in mobile devices.  While there are many HW level power management features in processors such as the OMAP35x, SW lacks the ability to manipulate and control those features.  Research those power features and implement kernel APIs to allow applications to manage their power more efficiently.
+
=Previous ideas=
 +
* [[BeagleBoard/GSoC/Ideas-2015]]
 +
* [[BeagleBoard/GSoC/Ideas-2014]]
 +
* [[BeagleBoard/GSoC/Ideas-2013]]
 +
* [[BeagleBoard/GSoC/Ideas-2012]]
  
=== OpenGL DSP accelleration ===
+
=Mentors=
 
+
{| border="1"
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.
+
! Name
 
+
! IRC nickname
=== Adding Sense to Beagle ===
+
! Melange name
 
+
! Native language
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. 
+
! Other languages
 
+
! Timezone
 
+
! Software help
=== ideas not worked out ===
+
! Hardware help
 
+
! Focus projects
* Move Firefox to Cairo on OpenVG and minimize memory footprint
+
|-
* Implement OpenVG with the C64x and DMAs
+
| Jason Kridner
* more codecs on the dsp (e.g. mp3 encoder/decoder, mpeg2 decoder, codecs for IP telephony (with video), ...)
+
| jkridner
* port LXDE (see www.lxde.org)
+
| beagleboard
* beagle as upnp renderer
+
| English
* beagle variant of "from 0 to 60 in 5 seconds" make a beagle that starts in < 5 seconds
+
| -
* good text to speech support
+
| US Eastern
* Clean MythTV, Boxee, XBMC, or Miro builds
+
| JavaScript, C, u-boot
* facial recognition with depth analysis using pico projector and webcam
+
| wiring, timing diagrams, basic debug
* high-speed 3d scanning with pico projector and webcam
+
| BoneScript development
* implementing a single pixel camera with beagleboard, pico projector and webcam; accelerate processing using DSP
+
|-
* USB class converters (MTP to mass-storage, audio to midi, ...) or invasive sniffer
+
| 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
 +
|}
 +
[[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