Google Summer of Code 2022

This page is for the contributors who make proposals as well as those who work on projects for RTEMS as part of GSoC 2022.

Contributors' Proposals

Start filling in this table for yourself as soon as possible and update as needed.

Contributor Name	Completed Hello	Discord Handle	Proposal Title	Google Docs URL	Final Submitted
Mohd Noor Aman	Yes	katana-flinger	RTEMS port for Raspberry pi 4 AArch64	​RTEMS port for RPi 4B AArch64 Proposal	Yes
Prashanth S	Yes	Prashanth S	BeagleBoard? BSP Projects	​CAN and ADC Peripheral Support for BBB	Yes
Mahmoud Abumandour	Yes	NRG-500	RTEMS Release Notes Generator	​Release Notes Generator	Yes
Kamlesh Bharodiya	Yes	curious	R5 BSP on Qemu	​Proposal	Yes
Duc Doan	Yes	duk3	STM32F4 BSP Project	​STM32F4 BSP Project Proposal	Yes

The columns are to be filled in as follows:

• The Contributor column is for your name.
• The Completed Hello column lets us all know whether or not you completed the mandatory Hello World project. Email your proof to Gedare, Joel, and Chris Johns.
• The nick on Discord column is your handle on Discord. RTEMS folks hang out there with best-effort service.
• The Proposal Title should be self-explanatory.
• The Google Docs URL is your proposal in Google Docs that can be reviewed and commented on by mentors. The ​proposal template should be copied and used as a baseline. This can be shared with mentors for review. Mentors can insert comments for you. You can use this as your Draft Proposal in the ​GSoC site.
• The Final Submitted should be set to Yes when you have submitted your Final PDF proposal on the official ​GSoC site. If you do not submit the final proposal via the Google site, you cannot be considered!

Contributors' Summer of Code Tracking Table

Contributors whose GSoC project is accepted by RTEMS shall fill in a slot with their information in the following table, which helps to centralize SoC Project Management.

Contributor Name	Handle	Project Link	Repository Link on Github	Blog	Calendar
NAME	nick on Discord	​Project Wiki	​Project's Github repo	​Blog	​Project Schedule
Duc Doan	duk3	​Project Wiki	​Project's Github repo	​Blog	​Project Schedule
Mohd Noor Aman	katana-flinger	​Project Wiki	​Project's Github repo	​Blog	​Project Schedule
Mahmoud Abumandour	NRG-500	​Project Wiki	​Project's Github repo	​Blog	​Project Schedule

The columns are to be filled in as follows:

• The Contributor Name column is for your name.
• The Handle column is your nickname on Discord.
• The Project Link is a link to the Wiki page for your project.
• The Repository Link on Github is a link to the Github repository for your project. It should be a specific repository, not just your github account!
• The Blog is a link to your blog with entries about your project. It should be updated regularly during the summer.
• The Calendar is a link to your Google Calendar with milestones and deliverables identified.

Contributor Status Updates

Each contributor has a section below for putting in notes from the weekly Discord meetings.

Gedare

• Jan 5: Tracking status page created.
• Feb 7: Org Application submitted.
• May 25: Held Initial Meeting.
  • Set format of meeting.
  • Discuss expectations.
  • Student Updates

Joel

• Feb 7: Joined application as Org Admin.

Duc

• June 1: Second Meeting
  • Last week: introduction, blog, tracking table, setting up environment.
  • Obstacle: VM and WSL problems
  • This week's plan: test hardware, check STM32H7 tree for idea about BSP, mailing list re: STM32F4

Mohd Noor Aman

• June 1: Community bonding second meeting
  • Last week's work: Introduction to community, discussions, blog writing, bought FT232H adapter, tested serial communication using PL011 (Raspbian bullseye arm64 and alpine 3.15.4 aarch64)
  • Blocker: Very less documentation about FT232H and raspberry pi 4 JTAG
  • Next week's plan: Mid-term exams, testing JTAG + serial with OpenOCD and GDB, and blog about it.

Mahmoud Abumandour

• June 1: Bonding period second meeting
  • Last week's work: Fixing glaring issues with the current ReleaseNotesGenerator? repository, learning about reStructuredText, generating overall summary before detailed descriptions of individual tickets, and investigating performance issues with fetching and processing tickets sequentially.
  • Blocker: Profiling shows that most time is spent in fetching the tickets from trac, which means an internet speed limitation and not bottlenecked by data processing.
  • Next week's plan: Going through final exams and taking care of my graduation thesis, I don't expect to be able to put much effort. I will start a blog for the project and include manually-written pre-existing top-level notes to the new generator, like in the rtems-release workflow.