This lab is very simple as we haven’t gotten into
any of the real subject matter yet.
However, we can get some preliminaries out of the way such as signing
out your lab kits and making sure you can log in to the lab computers and start
up the software you’ll be using this quarter.
It may take a little bit of a time, but it will save a lot next week.
The
design kits contain everything you need to construct most of the circuits
assigned to you over the course of the quarter. You are responsible for your
lab kit and we expect that you will return the kit in good working order with
all pieces intact. This especially applies to the chips, which have very
delicate pins (that should inserted and removed from the solder-less bread-board
– the white rectangle will all the holes – with extra care).
Please
make sure all of the above are provided for you in your kit. We will provide
additional materials later on in the quarter if they are necessary to complete
a lab.
We are aware that accidents can happen and the pins on chips may already been
weakened from years of use. Typically if you break a pin the chip will be
replaced and the damage will be forgiven; however in cases of gross negligence
you will have to pay for a replacement. Take care not to short out your board by
connecting Ground to Power. This results in a very large current that can
quickly destroy the components of the board including the board itself. Finally
be careful not to snap off wires inside the I/O connectors or the holes in the
solder-less breadboard. Wires are best extracted with the needle-nosed pliers.
The picture above is a diagram of the prototyping board with most of the major
components highlighted. For the first few labs you will be using the various
input/output devices located directly on the board such as the switches and
LEDs. Further details will be provided in each lab. Take note of the large FPGA
(Field Programmable Gate Array) that is highlighted on the board. Later on in
the quarter you will be programming this and directly interfacing with all the
devices on the board.
The image is a zoomed in picture of the prototyping board. As you can see, each
little hole has a corresponding pin mapping (more on this in later labs) and a
pre-programmed functionality. Remember the program that the TA’s put in the non-volatile
memory mentioned above? Well in addition to having the HEX display scroll CSE
370, the program also maps those holes to the indicated switches, keys, or
LEDs. So for example, if I hooked up the hole labeled "A13 SW9" to
the hole labeled "D21 LEDR9" with a wire, I would be controlling the
red led labeled LEDR9 on the DE1 board with the switch labeled SW9.
The solder-less breadboard attached to your prototyping
board is where you will be building all of your circuits. Notice the red and
black wires going to each of the rows at the top and bottom of the board. The red
wire denotes VDD (+5 Volts) and the black wire denotes Ground (0
Volts) – we will always use this convention with all our circuits. Never directly connect these two rows
together in any way. You should have both a VDD and Ground at the top of your
board and a set at the bottom. Even though there are spaces between the rows
all of the holes are directly connected to each other. This means you have
rails of VDD and Ground both at the top and bottom of your board.
In addition to the rails of VDD and Ground provided for you on the board there
are two 43 column holes separated by an indented divider. All 5 holes in one
column are connected, however, the column of 5 holes above the divider is not
connected to the column of 5 holes below the divider. All of these connections
are internal to the board so you cannot see them. So remember, if you connect
VDD into one of the five holes in a column, all five holes now have VDD (+5v) running
across them.
|
Normally,
a TA needs to "Check You Off" for each of the tasks of the lab
assignment. This won’t be necessary with
this first lab, but do make sure to let the TAs know if you have any trouble
with the steps above.
Comments
to: cse370-webmaster@cs.washington.edu