EE 360N Lab Assignments

Spring 2009

Getting Started with gcc
How to port code from Windows to sunfire
Note about Security of your files
Secure Shell (SSH) client for windows
WinSCP A Secure Copy client for windows - Useful if you want to copy files to/from your unix account.
"The C Programming Language" by Kernighan and Ritchie. This is an excellent book on the C language.
C/C++ Reference has some useful information about the functions available in the standard C library.
A quick tutorial on the Unix environment (updated - 02/04/09)
A reference card with commonly used commands for emacs
A reference card with commonly used commands for vim
DDD A graphical front-end for GDB, a command-line debugger for linux. To use GDB or DDD, be sure to include the "-g" flag when you compile with gcc.

Due May 8th, 05.00pm.

Submission instructions
Clarifications
Control store sheet (Excel spreadsheet)
Sample simulator runs to help you in debugging your simulator (Each of the hex files were simulated cycle by cycle using the "run 1" command and an "idump" was performed after each cycle. *.dump files show the cycle by cycle output of idump. *.state files summarize the contents of the pipeline latches. *.timeline shows a timeline of the execution of the program in the pipeline):
- example0.asm, example0.hex, example0.dump, example0.state, example0.timeline
- example1.asm, example1.hex, example1.dump, example1.state, example1.timeline
Note that these test cases are not meant to be exhaustive. You should write your own test cases to make sure that your simulator is working for every instruction and program.

Due April 19th, 11.59pm.

(Posted: 04/10/2009) Lab 5 submission is now open. Please submit all required files from a sunfire machine using the same submit-ee360n script as in previous labs. You may turn in a hard copy of your readme by 5 p.m. on Monday, April 20. Please note that your C code must simulate the hardware described in the readme and your microcode must represent your submitted state diagram. Significant discrepancies will be penalized harshly.
(Posted: 04/10/2009) Please make you sure your Lab 4 is correct before starting Lab 5. The testing system for Lab 4 is up. Use -lab4 as the first parameter to the submit-ee360n script. Examples:

Submit some new files for Lab 4 testing

submit-ee360n -lab4 lc3bsim4.c ucode4

Check which files have you submitted for Lab 4 testing

submit-ee360n -lab4 -ls

Test your Lab 4 files

submit-ee360n -lab4 -test

Remember, passing all the tests does not mean that your Lab 4 is correct!

Due April 5th, 11.59pm.

Submission instructions
You can use the following xfig files or pdf files to show the changes you made to the datapath, state diagram and microsequencer. You can modify the xfig files using the xfig drawing program installed on LRC UNIX/Linux machines. Please note that you can submit hand drawn diagrams (You may use the pdf files), if you are not comfortable using xfig.
- datapath xfig file , pdf file
- state machine xfig file , pdf file
- microsequencer xfig file , pdf file
Important note: Make sure your Lab 3 implementation is correct before starting Lab 4. You may use the submit-ee360n command on sunfire to test your Lab 3 program. Submit the lc3bsim3.c and ucode3 files first, then run submit-ee360n -test. Passing all the tests does not mean that your Lab 3 is correct! An incorrect program may just happen to behave correctly on our test cases. It is your responsibility to ensure that your Lab 3 is correct. The testing system will be available until April 1st.
Clarifications
The control store template in Excel and PDF formats.

Due Sunday, March 1st, 11.59pm.

Due February 15th, 11.59pm.

Due February 8th, 11.59pm.

Regrade instructions (last updated - 02/20/09)
Submission instructions (last updated - 02/02/09)
Useful code
Clarifications (last updated - 02/06/09)
LC3b Assembler for Linux (uploaded - 02/03/09) On a linux system, the usage is : ./assembler.linux < asm source file > < output file >