BeagleBoard/GSoC/2021 Proposal/simpPRU Improvements
===== About =====
Student: Archisman Dey
This project is currently just a proposal.
IRC: archismandey (@archismandey:matrix.org)
GitHub: GitHub Account
School: Indian Institute of Technology Guwahati
Primary language: English, Bengali, Hindi
Typical work hours: 10:30 AM - 8:30 PM US Indian Standard Time
Previous GSoC participation: This is the first time I am participating in GSoC.
About your project
Project name: Improvements to simpPRU
This project aims to improve simpPRU, the simple python-like language developed during GSoC 2020 to make programming the PRU easier, by doing the following things:
- Add suport for BeagleBone Blue: Currently, simpPRU supports the following boards: PocketBeagle, BeagleBone Black, BeagleBone Black Wireless and BeagleBone AI. This project will add support for the BeagleBone Blue (solving issue#4). Adding support for other boards in the BeagleBone family like the SeedStudio boards can also be done depending on availability.
- Add unit tests: Currently, simpPRU lacks any testing apart from making sure the examples work. This project will add unit tests for every feature present in simpPRU.
- Update the grammar so that control statements (break/continue) can only be called inside loops: Currently, they can be called inside any compound statement such as conditionals, which will throw an error while compiling the generated C code.
- Update the grammar so that return statements can be called anywhere in the function: Currently they can be called only at the end of a function, which is less flexible.
- Add a more flexible for loop: Currently the for loop in simpPRU can only handle loops of the form for : var in range_1:range_2, where range_2 > range_1. This project will add support for more flexible for loops of the form for : var in range_1:range_2:increment, where range_1 and range_2 can be any integers.
- Better error handling in the parser: simpPRU has some error handling in the bison parser, but it is not comprehensive. This project will add more comprehensive error handling.
- Bonus: Add support for calling C code from simpPRU: This can be done if time is left after the other tasks are completed. Approaches will have to discussed with mentors.
Adding support for BeagleBone Blue This will be done by adding the pin mappings for the BeagleBone Blue in include/pin_config.h, and setting the device model in src/pin_config.c.
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.
What will you do if you get stuck on your project and your mentor isn’t around?
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.
Please complete the requirements listed on the ideas page. Provide link to pull request.