EE 460N Lab Assignments

Spring 2013

Getting Started with gcc
How to port code from Windows to Unix
Note about Security of your files
Remotely access Unix machines with VNC
Visual Studio: Compiling your code with ANSI C
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
A reference card with commonly used commands for emacs
A reference card with commonly used commands for vim
GDB, a command-line debugger for linux. To use GDB, be sure to include the "-g" flag when you compile with gcc.
Lab Assignment Submission Instructions (posted - 02/03/13)
Lab Assignment Testing Instructions (posted - 03/18/13)

Due May 3rd, 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 28th, 11.59pm.

Please submit all required files from grader1 using the same submit-ee360n script as in previous labs. Be sure to include the appropriate header comment as in previous labs. You must turn in a hard copy of your readme by 5 p.m. on Monday, April 29. If are unable to attend class on the 29th to submit the readme, it is your responsibility to contact a TA and arrange a time to submit the documentation in advance. 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.
Please make you sure your Lab 4 is correct before starting Lab 5. The testing system for Lab 4 is up. See Lab 3 details for usage information.

Due April 7th, 11.59pm.

Submission instructions (last updated - 03/29/13)
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 grader1 to test your Lab 3 program. Submit the lc3bsim3.c and ucode3 files first with submit-ee360n -late, then run submit-ee360n -lategrade. Run submit-ee360n to see all available options. 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. See this for more details.
Clarifications (posted - 03/19/13)
The control store template in Excel and PDF formats.

Due February 24th, 11.59pm.

Due February 10th, 11.59pm.

Due February 3th, 11.59pm.