CS274: Computer Architecture - 1 Bit ALU Design (100 Points)
Assignment Goals
The goals of this assignment are:- To synthesize an adder and classic logic gates into a 1-bit ALU
Background Reading and References
Please refer to the following readings and examples offering templates to help get you started:The Assignment
What to Do
Create a 1-bit ALU
Using the adder circuit from the prior lab, create a 1-bit ALU by creating and wiring the following additional components:
- Create and test a 3-bit and gate
- Create and test a 4-to-1 multiplexor according to the design below. You will create four input pins (
I0
,I1
,I2
, andI3
), one select input (s
: a 2-bitstd_logic_vector
), and an output pin. Create four internal signals (sig1
,sig2
,sig3
, andsig4
) to hold the intermediate values. You can port map four and gates to signals like this:A1: and3 port map(w => I0, x => "not"(s(0)), y => "not"(s(1)), z => sig1);
Using these and gates, allow
I0
to pass whens
is10
,I1
whens
is01
, and so on. If a bit ofs
is0
, invert it to produce a1
. Finally, You canor
together the four internal signals, and wire that to the output pin, to complete the multiplexor. Note that if you only need fewer than 4 inputs to your multiplexor (say, one for the adder, one for theand
gate, and one for theor
gate), you can simply wireI0
,I1
, andI2
to those pins or signals, and then create a placeholder signal that you can wire toI3
. This will leave that pin essentially disconnected, or "floating". In other words, you can port mapI3
to'0'
.
- Create a structural ALU component that wires together a 2-bit and gate, a 2-bit or gate, and a full adder, and then multiplexes them together according to a select input, as shown in this design:
Your ALU will include an input calledALUOp
, which is astd_logic_vector(1 downto 0)
. You will wire this to the select input of the mux to choose which operation your ALU will perform!
When finished with this base design, make the following modification.
Subtraction
- Create and test a 4-input or gate
- Create and test a 2-to-1 multiplexor according to this design (note that your select input will only be 1 bit now!):
- Add a
bInvert
input bit to your design, and multiplex the input signalb
withnot b
(using a 2-input mux), and use the resulting mux output as a signal to the remainingb
inputs.
Submission
In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:- Describe what you did, how you did it, what challenges you encountered, and how you solved them.
- Please answer any questions found throughout the narrative of this assignment.
- If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
- Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
- Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
- Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
- Using the grading specifications on this page, discuss briefly the grade you would give yourself and why. Discuss each item in the grading specification.
- Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).
Assignment Rubric
Description | Pre-Emerging (< 50%) | Beginning (50%) | Progressing (85%) | Proficient (100%) |
---|---|---|---|---|
Algorithm Implementation (60%) | The algorithm fails on the test inputs due to major issues, or the program fails to compile and/or run | The algorithm fails on the test inputs due to one or more minor issues | The algorithm is implemented to solve the problem correctly according to given test inputs, but would fail if executed in a general case due to a minor issue or omission in the algorithm design or implementation | A reasonable algorithm is implemented to solve the problem which correctly solves the problem according to the given test inputs, and would be reasonably expected to solve the problem in the general case |
Code Quality and Documentation (30%) | Code commenting and structure are absent, or code structure departs significantly from best practice, and/or the code departs significantly from the style guide | Code commenting and structure is limited in ways that reduce the readability of the program, and/or there are minor departures from the style guide | Code documentation is present that re-states the explicit code definitions, and/or code is written that mostly adheres to the style guide | Code is documented at non-trivial points in a manner that enhances the readability of the program, and code is written according to the style guide |
Writeup and Submission (10%) | An incomplete submission is provided | The program is submitted, but not according to the directions in one or more ways (for example, because it is lacking a readme writeup) | The program is submitted according to the directions with a minor omission or correction needed, and with at least superficial responses to the bolded questions throughout | The program is submitted according to the directions, including a readme writeup describing the solution, and thoughtful answers to the bolded questions throughout |
Please refer to the Style Guide for code quality examples and guidelines.