Difference between revisions of "User:Tlazar"

From REU@MU
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
−
== About Me ==
+
<h2>About Me</h2>
 +
<p>Tom Lazar</p>
 +
<ul>
 +
<li>Incoming Sophmore at Marquette University | Computer Science Major</li>
 +
<li>Working On [[Upgrading Embedded Xinu for the Multi-Core Raspberry Pi 3]]</li>
 +
<li>Interests
 +
<ul>
 +
<li>OSS</li>
 +
<li>CS</li>
 +
<li>Hackathons</li>
 +
<li>Photography</li>
 +
<li>Games, both video and board</li>
 +
</ul>
 +
</li>
 +
<li>Involvement
 +
<ul>
 +
<li>Marquette Student ACM, President</li>
 +
<li>Marquette Girls Who Code, Mentor</li>
 +
<li>FRC BEAST Robotics, Mentor</li>
 +
</ul>
 +
</li>
 +
</ul>
 +
<h2>Weekly Logs</h2>
 +
<h3>Week 1</h3>
 +
<table style="border-collapse: collapse; font-family:tahoma" border="1" cellpadding="2px" width="100%">
  
−
:- Incoming Sophmore at Marquette University | Computer Science Major
+
<tr>
−
:- Working on [[Upgrading Embedded Xinu for the Multi-Core Raspberry Pi 3]]
+
<th style="font-family:verdana; border: 2px solid #000000;">DAY</th>
−
:- Github/OSS Enthusiast
+
<th style="font-family:verdana; border: 2px solid #000000;">DESCRIPTION</th>
 +
</tr>
  
−
Github: [http://github.com/tomlazar tomlazar]
 
  
−
Website: http://tomlazar.github.io
+
<tr>
 +
<td>Wednesday</td>
 +
<td>started working on the original pis, understanding how xinu worked and what would need to be done to get it working on the new pi 3 boards</td>
 +
</tr>
 +
<tr>
 +
<td>Thursday</td>
 +
<td>Started working with a pi3 bare metal kernel to see the differences. found out there are a lot, the pi3's use a new architecture the aarch64, meaning we had to convert all of the assembly files from 32 to 64 bits.</td>
 +
</tr>
 +
<tr>
 +
<td>Friday</td>
 +
<td>Got all the compilers installed and began converting the code.</td>
 +
</tr>
  
−
== Weekly Log and Milestones ==
+
</table>
 +
<h3>Week 2</h3>
 +
<table style="border-collapse: collapse; font-family:tahoma" border="1" cellpadding="2px" width="100%">
  
−
=== Week 1, 5/30 - 6/2 ===
+
<tr>
 +
<th style="font-family:verdana; border: 2px solid #000000;">DAY</th>
 +
<th style="font-family:verdana; border: 2px solid #000000;">DESCRIPTION</th>
 +
</tr>
  
−
:- Began work on Xinu for Raspberry Pi 3
 
−
:- Tested Pi 3 Boards,
 
−
:- Read though Xinu Build process
 
  
 +
<tr>
 +
<td>Monday</td>
 +
<td>Got the lite version of xinu working with the LED code, and began work on getting the serial driver to work.</td>
 +
</tr>
 +
<tr>
 +
<td>Tuesday</td>
 +
<td>Attended RCR training.</td>
 +
</tr>
 +
<tr>
 +
<td>Wednesday</td>
 +
<td>Got the mini-UART driver working and begun trying to get the more complicated pl011 serial driver to work. Also began to set up the xinu codebase to work with our project.</td>
 +
</tr>
 +
<tr>
 +
<td>Thursday</td>
 +
<td>Worked on debugging the serial driver using the Oscilloscope, and did some more work setting up the xinu codebase to work with the new RPI3. The xinu-project source code is split up into platform and components, each platform has its own loader and system code, but the components subsystems remain similar for most of the various platforms</td>
 +
</tr>
  
−
=== Week 2, 6/5 - 6/10 ===
+
</table>
 +
<h3>Week 3</h3>
 +
<table style="border-collapse: collapse; font-family:tahoma" border="1" cellpadding="2px" width="100%">
 +
 
 +
<tr>
 +
<th style="font-family:verdana; border: 2px solid #000000;">DAY</th>
 +
<th style="font-family:verdana; border: 2px solid #000000;">DESCRIPTION</th>
 +
</tr>
 +
 
 +
 
 +
<tr>
 +
<td>Monday</td>
 +
<td>Got the Full PL011 UART Working, the problem was in the frequency we were using to control the baud rate.</td>
 +
</tr>
 +
<tr>
 +
<td>Tuesday</td>
 +
<td>Went through the git repo and deleted some branch, edited the README and added all stable code to a dev branch.</td>
 +
</tr>
 +
<tr>
 +
<td>Wednesday</td>
 +
<td>Helped Priya and Patrik work on getting processes working, we ran into problems with the stack that we were not able to solve. Also experimented with running XSH on the PI3's, since it required the asynchronous serial driver it wouldn't work, so I added a quick workaround that would use the synchronous.</td>
 +
</tr>
 +
<tr>
 +
<td>Thursday</td>
 +
<td>Started researching process management in other operating systems, including Linux's completely Fair scheduler.</td>
 +
</tr>
 +
<tr>
 +
<td>Friday</td>
 +
<td>Worked on identifying which core we are currently using and looking at different ways to disable and use them. Also helped fix several errors and problems that arose from improper check-ins and broken code.</td>
 +
</tr>
 +
 
 +
</table>

Latest revision as of 21:29, 26 June 2017

About Me

Tom Lazar

  • Incoming Sophmore at Marquette University | Computer Science Major
  • Working On Upgrading Embedded Xinu for the Multi-Core Raspberry Pi 3
  • Interests
    • OSS
    • CS
    • Hackathons
    • Photography
    • Games, both video and board
  • Involvement
    • Marquette Student ACM, President
    • Marquette Girls Who Code, Mentor
    • FRC BEAST Robotics, Mentor

Weekly Logs

Week 1

DAY DESCRIPTION
Wednesday started working on the original pis, understanding how xinu worked and what would need to be done to get it working on the new pi 3 boards
Thursday Started working with a pi3 bare metal kernel to see the differences. found out there are a lot, the pi3's use a new architecture the aarch64, meaning we had to convert all of the assembly files from 32 to 64 bits.
Friday Got all the compilers installed and began converting the code.

Week 2

DAY DESCRIPTION
Monday Got the lite version of xinu working with the LED code, and began work on getting the serial driver to work.
Tuesday Attended RCR training.
Wednesday Got the mini-UART driver working and begun trying to get the more complicated pl011 serial driver to work. Also began to set up the xinu codebase to work with our project.
Thursday Worked on debugging the serial driver using the Oscilloscope, and did some more work setting up the xinu codebase to work with the new RPI3. The xinu-project source code is split up into platform and components, each platform has its own loader and system code, but the components subsystems remain similar for most of the various platforms

Week 3

DAY DESCRIPTION
Monday Got the Full PL011 UART Working, the problem was in the frequency we were using to control the baud rate.
Tuesday Went through the git repo and deleted some branch, edited the README and added all stable code to a dev branch.
Wednesday Helped Priya and Patrik work on getting processes working, we ran into problems with the stack that we were not able to solve. Also experimented with running XSH on the PI3's, since it required the asynchronous serial driver it wouldn't work, so I added a quick workaround that would use the synchronous.
Thursday Started researching process management in other operating systems, including Linux's completely Fair scheduler.
Friday Worked on identifying which core we are currently using and looking at different ways to disable and use them. Also helped fix several errors and problems that arose from improper check-ins and broken code.
Retrieved from "https://reu.cs.mu.edu/index.php?title=User:Tlazar&oldid=2541"