Submit final Project

Makefile

@@ -0,0 +1,20 @@
+test: build
+	./anyRead/test
+	./anyWrite/test
+	./jumpTest/test
+	./regTest/test
+	#./stackmemory
+	./demo/demo
+
+build: anyRead/test.v anyRead/test.asm
+	python assembler.py anyRead/test.asm
+	python assembler.py anyWrite/test.asm
+	python assembler.py jumpTest/test.asm
+	python assembler.py regTest/test.asm
+	python assembler.py demo/demo.asm
+	iverilog -o anyRead/test anyRead/test.v
+	iverilog -o anyWrite/test anyWrite/test.v
+	iverilog -o jumpTest/test jumpTest/test.v
+	iverilog -o regTest/test regTest/test.v
+	#iverilog -o stackmemory stackmemory.t.v
+	iverilog -o demo/demo   demo/demo.v

README.md

@@ -1,87 +1,5 @@
-# CompArch Final Project
-
-The goal of the final project is for you to explore a topic of interest within Computer Architecture, driven by your personal learning goals. This could build on and extend something we discussed in class, or dive into some other area of Computer Architecture (broadly defined).
-
-You may work in teams of any size, as long as they are appropriately scaled for your proposed project. Groups with > 4 members will face heavy skepticism about meeting this requirement. 
-
-In terms of scale, this is not a months-long capstone but rather more like an extended Lab. You will have about 2 weeks to complete it, and it will comprise 15% of your final grade. Be ambitious but realistic.
-
-## Timeline
-
--	Nov 17 (in class) – project ideation and team formation fair
--	Nov 28 (in class) – draft project proposal due , consultations with teams
--	Nov 29 – revised project proposal and work plan due
--	Dec 5 – mid-point check in (self-defined in work plan, highly recommended)
--	Dec 12 – final project due
-
-## Proposal (10%)
-Your project proposal should be about 1-2 pages, and must include:
-
--	Project title
--	Team members
--	Brief description of project (1-3 paragraphs)
--	2-3 references you plan to use
--	Minimum, planned, and stretch deliverables
--	Work plan (by Tuesday)
-
-We will discuss your proposal in class on November 28 (first class after break). These meetings will be quick and to-the-point, so you must come prepared with a printed out copy of your proposal. You should have done some background research by this point and have a good idea of your planned project trajectory.
-
-Based on the feedback from this meeting, you will revise your proposal and submit the final version including a work plan the following day.
-
-## Documentation (55%)
-The documentation counts for 55% of your grade whether you succeed at your goal or not.  Did you shoot for the moon and land among the harsh vacuum of space?  You still learned something from the process, and as long as you document it well, you will get full credit.
-
-Documentation should be posted in the form of a project website (PDF or MarkDown in a repo can also be acceptable depending on the project) and must answer the following questions:
-
-### What did you do?
-Your project abstract: one catchy sentence followed by a paragraph or two.  The intended audience should include people that aren't necessarily versed in Computer Architecture, but are technically competent. 
-### Why did you do it?
-A paragraph or so about why the project you chose is worthwhile and interesting.
-### How did you do it?
-This portion can assume an audience that has taken Computer Architecture, but don't let the story you’re telling get bogged down by buzzwords.  A sure sign of a bad engineer is ORA (over reliance on acronyms). 
-
-### How can someone else build on it?
-Include everything necessary to pick up where you left off.  This should include (as appropriate):
-
--	code
--	schematics
--	scripts and build instructions
-- proper attribution for resources used and anything you did not write yourself
--	list of difficulties and ‘gotchas’ while doing this project
-- reflection on the project as a whole as well as your work plan
--	possible TODOs to extend the depth of the project
-
-This should all be posted somewhere accessible, e.g. your project webpage or repository. Please do not literally include these question prompts and then answer them (you're better than that) - instead, use them to check that you've covered all the bases as you tell the story in the way that best makes sense for your project.
-
-## Choosing and Achieving your Goal (30%)
-There is a lot of flexibility available in what your actual final project can be. As a first pass, it needs to satisfy the following criteria:
-
-1. Build upon what we have learned in class this semester or other "Computer Architecture" topics
-1. Have well-defined criteria for when it is finished and successful
-1. Be achievable within the time allotted
-
-## Possible broad directions:
-
-- Extending something you started in Computer Architecture
-- Teaching somebody something cool about Computer Architecture
-- Something useful to someone that uses Computer Architecture
-- Something that needs the skills learned in Computer Architecture
-- Something that you can present at Expo that will make people want to take Computer Architecture
-
-Append one of the following phrases to a cool project idea to make it more CompArch-y:
-
-- ... with an FPGA
-- ... in assembly
-- ... on a GPU
-- ... inside a nested series of black boxes
-- ... hardware accelerated
-
-As you put your project plans together, remember that a major portion of the project is communicating it to others.
-
-## Demo (5%)
-We’ll present your project work during the time blocked out for "final exam" period – December 12 from 12 – 3PM.  This is mainly an opportunity to show off and celebrate your great work (small percentage of overall grade), and the details are up to you.
-
-The "default" option is a poster version of your project documentation (along with a running live demo if appropriate), so that folks can walk around in a studio session and see what you did. Maybe you feel that a presentation is more appropriate for your project work. Perhaps a tutorial session with everyone participating makes the most sense. It could be that only a puppet show truly captures the essence of your project. Think about final demo format as you put together your proposal, but you don't need to make a final decision just yet.
-
-Good luck, and have fun!
-
+# TIS-100 CPU in verilog
+This is an implementation of the TIS-100 cpu from the [game of the same name](http://www.zachtronics.com/tis-100/). Information about the functions of this machine can be found in our [ISA](https://github.com/TShapinsky/FinalProject/blob/master/TIS_100_ISA.pdf)
+## Running
+To run rebuild all verilog and asm files and run all the tests as well as the demo use
+    ``make test``

anyRead/center.dat

@@ -0,0 +1,16 @@
+001100111100000000
+001100111100000000
+001100111100000000
+001100111100000000
+001100111000000000
+011100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000

anyRead/down.dat

@@ -0,0 +1,16 @@
+010010000000000100
+010010000000000101
+011100000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000
+000000000000000000

anyRead/left.dat

@@ -0,0 +1,16 @@
+010001100000000001
+011100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000

anyRead/right.dat

@@ -0,0 +1,16 @@
+010001000000000010
+011100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000
+101100000000000000