Difference between revisions of "BeagleBoard/GSoC/2022 Proposal/bb-config improvements & GPIO Benchmarking"

From eLinux.org
Jump to: navigation, search
(Created page with "Category: BeagleBoard Category: GSoC Category: GSoCProposal2021 =Proposal Template = About ''Student'': [http://elinux.org/U...")
 
Line 1: Line 1:
 
[[Category: BeagleBoard]]
 
[[Category: BeagleBoard]]
 
[[Category: GSoC]]
 
[[Category: GSoC]]
[[Category: GSoCProposal2021]]
+
[[Category: GSoCProposal2022]]
  
 
=[[BeagleBoard/GSoC/ProposalTemplate|Proposal Template]] =
 
=[[BeagleBoard/GSoC/ProposalTemplate|Proposal Template]] =

Revision as of 08:16, 26 March 2022


Proposal Template

About Student: Seak Jian De
Mentors: Jason Kridner
Code:
Wiki:
GSoC:

Status

This project is currently just a proposal.

Proposal

Please complete the requirements listed on the ideas page and fill out this template.

About you

IRC: Jian De
Github: https://github.com/Fred-JD
School: Universiti Teknologi Malaysia
Country: Malaysia
Primary language: English, Mandarin Malay
Typical work hours: 4PM - 11PM UTC +8
Previous GSoC participation: First year apply gsoc.

About your project

Project name: bb-config improvements & GPIO Benchmarking

Description

Bb-Config Improvement
Beagle-config is a terminal UI to make the configuration of beaglebone devices easier and more visually.

  • Update to the latest FTXUI Version
  • Adding a graph section for ADC/DAC using FTXUI graph
  • Support for network-manager using dbus API. Talking directly to dbus saves a step and may expose a richer interface than the command line.
  • Filesystem over NFS(Network File System)
  • Enable/disable "stuff" that takes up the boot up time issue#45
  • Scan Overlays and give a selection box issue#46
  • Add support for setting custom pinmux issue#42

GPIO Benchmarking
Benchmark GPIOs using the below four approaches

  • Memory-mapped GPIO with C
  • C++ with file system access
  • LKM
  • PRUs


Timeline

Provide a development timeline with a milestone each of the 11 weeks and any pre-work. (A realistic timeline is critical to our selection process.)

Mar 29 Applications open, Students register with GSoC, work on proposal with mentors
Apr 13 Proposal complete, Submitted to https://summerofcode.withgoogle.com
May 17 Proposal accepted or rejected
Jun 07 Pre-work complete, Coding officially begins!
Jun 17 Milestone #1, Introductory YouTube video
June 24 Milestone #2
June 30 Milestone #3
July 12 18:00 UTC Milestone #4, Mentors and students can begin submitting Phase 1 evaluations
July 16 18:00 UTC Phase 1 Evaluation deadline
July 23 Milestone #5
July 30 Milestone #6
Aug 06 Milestone #7
August 10 Milestone #8, Completion YouTube video
August 16 - 26 18:00 UTC Final week: Students submit their final work product and their final mentor evaluation
August 23 - 30 18:00 UTC Mentors submit final student evaluations

Experience and approach

In 5-15 sentences, convince us you will be able to successfully complete your project in the timeline you have described.

Contingency

What will you do if you get stuck on your project and your mentor isn’t around?

Benefit

If successfully completed, what will its impact be on the BeagleBoard.org community? Include quotes from BeagleBoard.org community members who can be found on http://beagleboard.org/discuss and http://bbb.io/gsocchat.

Misc

Please complete the requirements listed on the ideas page. Provide link to pull request.

Suggestions

Is there anything else we should have asked you?