BeagleBoard/GSoC 2021/Micropython for BeagleConnect Freedom
Student: new student
Mentors: Jason Kridner
GSoC: GSoC entry
This project is currently just a proposal.
Please complete the requirements listed on the ideas page and fill out this template.
IRC: Freenode IRC nickname
Github: Github account
School: School name
Primary language (We have mentors who speak multiple languages): Language
Typical work hours (We have mentors in various time zones): 8AM-5PM US Eastern
Previous GSoC participation: Tell us why you want to participate in GSoC here. Also, provide list of URLs for any previous GSoC participation with any organizations.
About your project
Project name: Micropython for BeagleConnect Freedom
BeagleConnect is a revolutionary technology which eliminates low-level software development for IoT and IIoT applications,such as building automation, factory automation, and home automation.What sets it apart is that it eliminates the need of relying on software libraries enabling it to be used for interfacing a greater number of sensors, actuators and indicators for communicating over various networks compared to other conventional solutions.This can be achieved since it is built with fully open source software with submissions to mainline Linux and Zephyr repositories to aide in support and porting.
The BeagleConnect Freedom is based on the TI CC1352 and is the first available BeagleConnect solution which runs the Zephyr RTOS and has mikroBUS ports along with BLE and Sub-GHz radios on it.The BeagleConnect has a few technologies at the core namely IPv6 (via 6LoWPAN),Zephyr support for IEEE 802.15.4 and Greybus from Project Ara.The goal of this project is to port Micropython and Circuitpython support along with GPIO, I2C, SPI, PWM and ADC drivers support in Micropython for the BeagleConnect solution.
After the porting is completed and the drivers have been inculcated,the practicality will be thoroughly tested with the help of MikroElektronika click boards of each respective protocol and documented on my blog.
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.
Is there anything else we should have asked you?