This week was a weird one. Hot off the heels of our demo, I was pretty motivated to work on some more of my implementation, and since the software stuff is mostly done, that meant building out some SystemVerilog (finally). However, there was a more pressing matter–I flew home for the rest of the semester this past Thursday, so we needed to ensure that all our hardware worked before we were all separated. This meant I needed to build a…
This week, I worked pretty heavily on getting everything ready to demo. This means that the software display interface is finally done! Now, all I have to do is write it to hardware, which (I hope) is not going to be too hard. I don’t know what else to put here, since you guys saw the majority of my work 🙂 This week, I’m focusing on testing all the hardware components with an Arduino. I want to make sure I…
This week, I worked on trying to get all the necessary components ready for the demo on Monday. This meant writing a lot of software before we wrote any hardware, since we plan for the demo to be completely based in our software co-simulation environment. The encoders, I can say proudly, are finally done–after talking about the parameters that they hold and control with Joe, I have finally settled on a system that will allow us to have the correct…
It’s a spooky day today! Anyway, I finally finished work on the encoders and began to do some stuff with the SPI interface to the display. I know I was told to include images–most of the stuff I’m doing is just source code, though, so I don’t know what exactly that entails? Regardless, I’m trying to design this interface in such a way that it can be reused for driving the DAC that we’re using, which should also use SPI….
This week, I worked more on the encoder software simulator. This module has to tie in pretty closely with both the settings and display modules, so I’m trying to find a setup that is extensible enough to work in a variety of circumstances, yet well-tuned enough to work with these modules without much fuss. My current plan is as follows: We split the encoders into two modules. The first module takes in the raw data of the encoder, synchronizes it,…
This week, I worked on a few PRs from Joe, but mostly, I worked on figuring out what our hardware looks like. My first RTL Design is the encoders, so it’s important to make sure I know their exact functionality before doing any spin-off parts, like the display or the settings. I worked a bit on the software and hardware models for the encoders, but mostly, I just made a quick hardware schematic (which involves a few more resistors than…
After Joe wrote the testbench last week, I refactored it pretty heavily into something that was a little easier to use. Our final UVM-esque environment is something that I’m very proud of–we have cycle-accurate checking now, and we even automatically look up python modules based on the path of their containing file, which is a bit of Python3 that I wasn’t sure was super possible. Next week, IÂ really have to get to work on the encoder stuff, though–I imagine I’ll…
This week, I worked pretty heavily on the logistics and environment for the project. While Joe worked on testing environment, I did some work with my own setup, dealing with the style guide for the project as well as etiquette for pull requests. I finished reviewing Joe’s code, and now that the test environment is mostly finalized, I’m not as wary of jumping into writing my testbenches. I think I didn’t really get as much done as I wanted to,…