BeagleBoard/GSoC/2020 Projects/Cape Compatibility
Contents
Proposal for Cape compatibility layer for BeagleBone Black and BeagleBone AI
Student: Deepak Khatri
Mentors: Jason Kridner
Code: https://github.com/deepaklorkhatri007/linux/tree/4.14
Wiki: http://elinux.org/BeagleBoard/GSoC/2020Proposal/DeepakKhatri
GSoC: [N/A]
Status
This project is currently just a proposal.
Proposal
Completed all the requirements listed on the ideas page. the code for the cross-compilation task can be found here submitted through the pull request #130.
About you
IRC: lorforlinux
Github: Deepak Khatri
School: Netaji Subhas Univerity of Technology (NSUT) formely NSIT
Country: India
Primary language(s): Hindi,English
Typical work hours: 9AM - 7PM IST
Previous GSoC participation: I participated in GSoC2019 but i was not selected for the project. The project was to make a jekyll website for AIMA organization, Discussion on the project can be found here and the prototype i made can be found here. From the GSoC2019 i learned the importance of communication.
About your project
Project name: Cape compatibility layer for BeagleBone Black and BeagleBone AI
Description
The idea of this project is to make the same userspace examples work, to use the same references to drivers for peripherals assigned to the same pins between Black and AI. For making the boards pin to pin compatible as in pin names, we are required to create new device tree sources include files. The file "am335x-bone-common-univ.dtsi" defines the pin names for P8 and P9 header of Black and we are required to implement a similar file for am5729 like "am5729-beagleboneai-common-univ.dtsi". To use serial ports and userspace I2cdev/spidev, aliases provided by the device trees would match. For GPIOs, examples would work using pin names under libgpiod.
Timeline
| Mar 30 | Proposal complete, Submitted to https://summerofcode.withgoogle.com |
| Apr 27 | Proposal accepted or rejected |
| May 18 | Pre-work complete, Coding officially begins! |
| May 25 | Milestone #1, Introductory YouTube video |
| June 1 | Milestone #2, |
| June 8 | Milestone #3 |
| June 15 18:00 UTC | Milestone #4, Mentors and students can begin submitting Phase 1 evaluations |
| June 19 18:00 UTC | Phase 1 Evaluation deadline |
| June 22 | Milestone #5 |
| June 29 | Milestone #6 |
| July 6 | Milestone #7 |
| July 13 18:00 UTC | Milestone #8, Mentors and students can begin submitting Phase 2 evaluations |
| July 17 18:00 UTC | Phase 2 Evaluation deadline |
| July 20 | Milestone #9 |
| July 27 | Milestone #10 |
| August 3 | Milestone #11, Completion YouTube video |
| August 10 - 17 18:00 UTC | Final week: Students submit their final work product and their final mentor evaluation |
| August 17 - 24 18:00 UTC | Mentors submit final student evaluations |
Experience and approach
I have done an internship on Embedded Electronics using BeagleBoneBlack. I completed this project called Mausam National during my internship.
Mausam National Front image
Mausam National Back image
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.
Suggestions
Is there anything else we should have asked you?
