Difference between revisions of "BeagleBoard/GSoC/2019 Projects"

From eLinux.org
Jump to: navigation, search
m (added Vaishnav's video URL)
Line 30: Line 30:
 
* Wiki: https://github.com/vaishnav98/gbsim/wiki
 
* Wiki: https://github.com/vaishnav98/gbsim/wiki
 
* GSoC site: https://summerofcode.withgoogle.com/projects/#5996499987595264
 
* GSoC site: https://summerofcode.withgoogle.com/projects/#5996499987595264
* Intro video : TBD
+
* Intro video : https://youtu.be/QtzHhAFE0SE
  
 
==Project: [https://summerofcode.withgoogle.com/projects/#5163407328673792 PRU User Space API] ==
 
==Project: [https://summerofcode.withgoogle.com/projects/#5163407328673792 PRU User Space API] ==

Revision as of 15:04, 27 May 2019

Links

Project: ProjectPage

Description

  • Student: Your name
  • Mentors: Mentor names
  • Code: Your github page for the project
  • Upstream: Where your code will end up when submitted
  • Wiki: Full project link
  • GSoC site: Link to project on https://summerofcode.withgoogle.com
  • Intro video: YouTube video link

Project: Clickboard Support Under Greybus

Click boards are a flagship hardware product line of MikroElektronika with over 600 add-on boards ranging from wireless connectivity clicks to Human Machine Interface clicks for interfacing with peripheral sensors or transceivers. Most of the Click boards use the common protocols like SPI,I2C or UART to communicate with the Beaglebone and thus the support for them now is accomplished via device tree overlays via the bb.org-overlays repository. This requires /boot/uEnv.txt to be modified to load the drivers at boot, requiring at least one reboot to enable the support in a potentially error-prone way.

The Greybus Simulator is a tool which simulates an AP Bridge, SVC, and an arbitrary set of modules plugged into Greybus. Greybus already provides most of the interfaces used on click boards and utilizes manifest files to enumerate hardware at run-time. This project aims to enable Click Board Support via Greybus Simulator by writing suitable Manifests according to the Click board Specifications and by simply copying the manifest to a hotplug-directory a click board can be loaded, which would make the interfacing a lot easier. Detailed Proposal at https://elinux.org/BeagleBoard/GSoC/2019Proposal/clickboard-support-under-greybus

Project: PRU User Space API

This project aims to provide an API for different programming languages to load/unload firmware and communicate with the PRUs from User Space. A GUI application that runs on the terminal will also be provided for debugging the PRUs step by step.


Project: Xen on BeagleBoard-x15

The idea behind the project is to make Xen hypervisor available and easy to use on beagleboard-x15. This implementation will allow users to experiment on embedded virtualization and in related fields like automotive, critical systems prototyping and processor's resources sharing. It might also provide very interesting possibilities for heterogeneous resources' utilization. The most interesting outcome is the availability of open-source virtualization on top of the open-source hardware.