= Google Summer of Code 2017 = [[TOC(GSoC/2017, depth=2)]] This page captures the students who make proposals as well as those who work on projects for RTEMS as part of GSoC 2017. {{{#!comment [[Image(GSoC2016Logo.jpg, 50%)]] }}} = Students' Proposals = Start filling in this table for yourself as soon as possible and update as needed. || '''Student''' || '''Completed Hello''' || '''IRC Handle''' || '''Proposal Title''' || '''Google Docs URL''' ||NAME || Yes or No || nick on #rtems || Project Title || Link to Google Docs for proposal (shared with mentors) ||Tanu Hari Dixit || Yes || tokencolour || RTEMS Tester Improvements || https://docs.google.com/document/d/1EWlQf3RvotGOVbZooXl5KjSQQu4mrUlexhq0AaW0WGo/edit?usp=sharing ||Sichen Zhao || Yes || sichenzhao || Beagleboard BSP projects || https://docs.google.com/document/d/10e_H84IqRHVP19meLvvFZNq7CEe4Rk2biw8L5ME28UM/edit?usp=sharing || Sagar Gupta || Yes || sgmonusg || Raspberry Pi Improvements || https://docs.google.com/document/d/12IvZZJaonk4Angjdj6Mtb0I1ykYE50mBou6vWu9LJXU/edit?usp=sharing || Abhimanyu Rawat || Yes || ABresting || Memory Protection || https://docs.google.com/document/d/1zyfBQq6bTYkSycsBrGHg-I_Y1538BzjVVNV9L3J95Z0/edit?usp=sharing || Cillian O'Donnell || Yes || cpod || Improve Coverage Analysis Tools || https://docs.google.com/document/d/1VCE5-4ccMNphLFjWM9bOULKxwdzYhEU1l8jYB1bZNX0/edit?usp=sharing || Denis Obrezkov || Yes || embden || C6x Port || https://docs.google.com/document/d/1-_kNXMd7TuNNQ-dvkfRuNWEKNTJIhBZGuxEkcLgXHDc/edit?usp=sharing || Nikolay Komashinskiy || Yes || nikokoma || TMS570 BSP improvements || https://docs.google.com/document/d/1GxAQuKK_gY5VSlgsqsVXdwHrgdQ3auw8hS_zggqz0eE/edit?usp=sharing || Vivek Kukreja || Yes || vivekk || Improvements to Tracing Framework || https://docs.google.com/document/d/1-IoZwnO1W914SJnTTeoLD6ljHJZqKBNvqZdn2gfUtkc/edit?usp=sharing || Aditya Upadhyay || Yes || adityau || Conversion to New Test Suite || https://docs.google.com/document/d/1prS88KFKAfAI2cJBzdAkyisRAoX8Ob9zVqI4ANSl7Gw/edit?usp=sharing || Aditya Upadhyay || Yes || adityau || POSIX Compliance || https://docs.google.com/document/d/1_eo87eOiHmIHokfsgFYY3F98FNmorpVTm4AI1WE-iKo/edit?usp=sharing || Faizan Khan || Yes || faizank || SD/MMC device driver for Beagelboard || https://docs.google.com/document/d/1G2eoZJBm0XeE1Lu1_o_d7yRYWjTNwAX08NWVbVxeC1k/edit?usp=sharing || Spencer Goodwin || Yes || sgoodwin || CTF Integration || https://docs.google.com/document/d/1dXL1yET8XnvRuz5eVtHZce1FETUEJS1-OI1mq33rM00/edit?usp=sharing || Mikail Yayla (SOCIS) || Yes || myay || Software-Based Fault Tolerance || https://docs.google.com/document/d/1k5tNn44xJ0k033JtJ_t0OWVWUEFhr1XBp6N8Cncys7Q/edit?usp=sharing The columns are to be filled in as follows: * The ''Student'' column is for your name. * The ''Completed Hello'' column lets us all know whether or not you completed the mandatory Hello World project. * The ''IRC Handle'' column is your handle on IRC. RTEMS folks hang out in #rtems on freenode.net. * 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 [https://docs.google.com/document/d/1F5XCodvX8AYNqWX5ssu7dfjkmFT__83uf8ABKbB_Pkg/edit?usp=sharing proposal template] should be '''copied''' and used as a baseline. This can be shared with mentors for review. Mentors can insert comments for you. '''WARNING''': The Google Docs version of the proposal is a '''WORKING''' copy. You '''MUST''' submit the official and final proposal using the [https://summerofcode.withgoogle.com Google site]. If you do not submit the final proposal via the Google site, you cannot be considered = Students' Summer of Code Tracking Table = Students whose GSoC project is accepted by RTEMS shall fill in a slot with their information in the following table, which helps to centralize [wiki:Developer/GSoC/ProjectManagement SoC Project Management]. ||'''Student Name'''|| '''IRC Handle''' || '''Project Link''' || '''Repository Link''' || '''Blog''' || '''Calendar''' ||NAME || nick on #rtems || Link to Project Wiki page || Link to project's public Github repository || Link to your development blog || Link to Calendar with Schedule ||Cillian O'Donnell || cpod || [https://devel.rtems.org/wiki/GSoC/2017/coveragetools Wiki] || [https://github.com/cillianodonnell Github] || [http://summerofrtems.blogspot.ie/ Blog] || [https://calendar.google.com/calendar/embed?src=rbb3vofvicg0c9lnlgcjv914f8%40group.calendar.google.com&ctz=Europe/Dublin Project Timeline] ||Tanu Hari Dixit || tokencolour || [https://devel.rtems.org/wiki/GSoC/2017/RTEMSTesterImprovements Wiki] || [https://github.com/tokencolour/rtems_tester_improvements Github] || [https://tokencolour.github.io/ Blog] || TBA ||Sichen Zhao || sichenzhao || [https://devel.rtems.org/wiki/GSoC/2017/BeagleboneBSPProject Wiki] || [https://github.com/hahchenchen/GSOC-2017-Bealgebone-BSP-Projects Github] || [http://sichenzhao.blogspot.com Blog] || TBA ||Nikolay Komashinskiy || nikokoma || [https://devel.rtems.org/wiki/GSoC/2017/TMS570_BSP_improvements Wiki] || [https://github.com/nikokoma/tms570_bsp_improvements Github] || [http://rtosandyou.blogspot.ru/ Blog] || TBA ||Aditya Upadhyay || adityau || [https://devel.rtems.org/wiki/GSoC/2017/POSIX_Compliance Wiki] || [https://github.com/aadit0402/PosixCompliance Github] || [https://wordpress.com/stats/day/adityaposixcompliance.wordpress.com/ Blog] || TBA ||Denis Obrezkov || embden || [https://devel.rtems.org/wiki/GSoC/2017/RTEMS_for_HiFive1 Wiki] || [https://github.com/embeddedden/rtems_hifive1 Github] || [https://embeddedden.blogspot.com/ Blog] || [https://calendar.google.com/calendar/embed?src=dpqrum4g9lchd9rsuieumit1so%40group.calendar.google.com&ctz=Europe/Moscow Project Timeline] ||Spencer Goodwin || spencergoodwin || [https://devel.rtems.org/ticket/3028#ticket Wiki] || [https://github.com/Spencer-Goodwin/RTEMS Github] || TBA || TBA The columns are to be filled in as follows: * The ''Student'' column is for your name. * The ''IRC Handle'' column is your handle on IRC. RTEMS folks hang out in #rtems on freenode.net. * The ''Project Link'' is a link to the Wiki page for your project. * The ''Repository Link'' is a link to the github repository for your project. * 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 Calender with milestones and deliverables identified. = Student Status Updates = Each student has a section below for putting in notes from the weekly IRC meetings. == Joel == * TBD == Gedare == * Jan 20: GSoC 2017 Page created. * May 24: Initial meeting held. Set meeting format and checked in with all students. * May 31 * Roll call, Sichen is absent. * Announce one withdrawal and one pending ESA SOCIS Student. * Set Expectations for Successful Evaluations * Participating in IRC and mailing lists. * Attendance at weekly meetings and providing status updates. * Posting to Github each day of work. * Student updates. == Chris == * TBD == Cillian O'Donnell == * May 24: So far I have made my way through 2014 SOCIS patches and have been working through python exercises to improve my skills. The next step revives the old SOCIS from 2015, which should produce a temporary setup with rtems-test using Couverture-Qemu and generating coverage reports. Currently the SOCIS 2015 patches are applied: Left to do is 8 files with 20 rejects, currently producing build errors in rtems-tools. * May 31: All SOCIS 2014,2015 patches are now applied and I fixed the initial build errors in covoar. Fixed some runtime errors in rtem-test and got a first run though RTEMS Tester that resulted in 446 invalid tests. All switched to dry-run due to errors in qemu.cfg. That has disappeared this morning by adding --coverage as the last flag. Problems at the moment are, some coverage code seems to run with or without the flag and Invalid path errors for SymbolSets.cfg that covoar uses.Next week I'll continue testing and fixing the runtime errors and if I get some decent test results start comparision with regular qemu for all supported bsps. == Denis Obrezkov == * May 24: initial meeting. I have read documents about HiFive1 board, Freedom E310 Architecture, E31 Coreplex core. For the next week I plan: * to read User and Priveleged mode ISA * to build the toolchain * to check the board and its peripheral * to build and run in SPICE simulator Hesham's port of RTEMS for RISC-V arcitecture. * May 31: meeting. * What was done: * I have read privileged ISA 1.10 and user ISA 2.2. * I have checked that examples for my hifive1 board work (built, ran and debugged through openOCD) * I have built a SPIKE simulator (with some issues), built RTEMS RSB but wasn't able to build RTEMS for hifive yet. * The blog post was written [http://embeddedden.blogspot.ru/2017/06/week-before-gsoc-2017-rtems-for-hifive1.html Building SPIKE] * The current issues: * some .S files aren't compiled due to unrecognized opcodes. * Plans for the next week: * to build RTEMS BSP for RISC-V and launch it in SPIKE, write a blog post about it * to figure out, what should be done in order to make RTEMS run on HiFive1 board * if I have time, I will also start trying to launch RTEMS BSP on top of the board and check that Peripheral is working. == Tanu Hari Dixit == * May 24: Initial meeting. * I have gone through all the macro files in rtems-tools.git/tester/rtems/testing and we have decided to use INI files instead of YAML because we have standard support in Python for parsing INI files. PyYAML would have been a dependency which would have been difficult to handle across different hosts. * We have finalized on the format for the INI files. Chris already pushed "configuration.py" in rtemstoolkit and this is taken out from check.py. Also the user specific configuration options--we decided we'll have a settings file that would contain user specific details. * I will come up with a ReST file as in an official documentation for the new macro files in ini format. I'll also start changing the .mc files. * May 31: * I had converted the documenation of rtems-tester to ReST and I had mistakenly added the rtems-logo too when it was not needed. * It was my first time with the Sphinx documentation of RTEMS. Though, I had worked with Sphinx before, it took me more time to come up with a suitable patch because I had to undo commits. I had less experience with that. * I have sent the new version of patches with the doc in line with the documentation of rtems-bsp-builder as Chris had suggested. This documentation also includes the new ini format. I would need to edit it as the format evolves in the course of the conversion. * Right now, I'm at converting the mc files. * Also I have still to ask Chris what to put on Github. * Chris has reviewed the changes. I need to make those changes in the doc. * Since the new release 4.12 is just on the horizon, I am supposed to remove the changes with INI bits and apply it as a second patch over the rest of the updated doc. == Sichen Zhao == * May 24:Initial meeting. * I am working on first part of my proposal goal: i2c driver * So far, i have finished the i2c code, now working on create the patch and send to devel to be review. * I get along very well with the mentors, mentors give many advices to me during the project process, they are very enthusiastic. * Next week, i will focus on modify i2c patch, at the same time, i will read the USB code in FreeBSD, prepare for second part of proposal. * May 31. * Absent the meeting for the reason of focus on my paper which deadline is today. * I modify the i2c patch and send it to RTEMS devel. * I read the USB code in FreeBSD, especially the AM335x dts file which contains the IRQ vector. * I found the reason why my USB code can't pull the USB power pin high, and fix it. But there are a new issue occuer, the code seems stuck at somewhere, i think it should stuck at the ISR. * I write the blog post about my prepare works and I2C driver. * Next week i will try to solve the USB stuck problem, at the same time, i will keep an eye on the mailing list about my i2c patch. == Aditya Upadhyay == * May 24:Initial meeting. * I am have completed the implementation of inttypes library. I have made a separate test within the samples testsuites named psxinttypes01. * I have to port inttypes.h to newlib, i am working on it. * I will commit the code of inttypes library in my local github repo. * Now i am trying to implement maths related library and will make a test for related methods.