BeagleBoard/GSoC/2020Proposal/VedantParanjape

Proposal for Port am335x_pru_package to remoteproc

Student: Vedant Paranjape
Mentors: Kumar Abhishek, Zubeen Tolani
Code: https://github.com/beagleboard/am335x_pru_package
Wiki: https://elinux.org/BeagleBoard/GSoC/2020Proposal/VedantParanjape
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 #138.

About you

IRC: vedant16
Github: https://github.com/vedantparanjape/
School: Veermata Jijabai Technological Institute (VJTI)
Country: India
Primary language : English, Hindi, Marathi
Typical work hours : 10AM - 7PM Indian Standard Time
Previous GSoC participation: I find embedded pretty interesting, given I have experience with ESP32, I think I will be able to excel in this project. This is the first time i am participating in GSoC

About your project

Project name: Port am335x_pru_package to remoteproc

Description

In 10-20 sentences, what are you making, for whom, why and with what technologies (programming languages, etc.)? (We are looking for open source SOFTWARE submissions.)

Timeline

Apr 27	Proposal accepted or rejected	Community Bonding Period and discussion on the project and resources available.
May 18	Pre-work complete	Coding officially begins!
May 25	Milestone #1	Introductory YouTube video Setting up PocketBeagle i.e flashing up to date Linux image and Testing user-led blink code :D Running existing example codes from this repository Creating header file for the new userland driver which uses remoteproc
June 1	Milestone #2
June 8	Milestone #3
June 15 18:00 UTC	Milestone #4 (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 (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 decent experience in C++, C and Python. I have done several projects involving embedded systems like ESP32, I well-versed with freeRTOS. I recently did a project on ESP32, in which I used ESP to control and plot PID loop running on the embedded device, plotting the values on a python GUI. Other than that I have developed firmware for a 3 DOF arm based on a ESP32 custom board. I did a internship with a embedded deviced startup, where I built:

1. Built TCP network stack for embedded IoT Devices
2. Implemented Synchronous TCP server using Boost.Asio(C++) and Boost.Thread(C++)
3. Implemented a tool to calculate round trip time(RTT) of tcp packets

I actively contribute to open source and do a lot of mini projects throughout the year, you can find my several more interesting projects at my github page

Contingency

I believe that if I get stuck on my project and my mentor isn’t around, I will use the resources that are available to me. Some of those information portals are listed below.

1. https://git.ti.com/pru-software-support-package
2. https://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs PRU Guide
3. https://markayoder.github.io/PRUCookbook/ Mark Yoder's cookbook is a excellent guide
4. Derek Molly's beagle bone guide provides all the information needed for getting up and running with my beagle.
5. The technical reference manuals provided by TI on am3358 and am5729 are the best source
6. Processor SDK Linux Software Guide is a good reference material

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?