EE 460N Lab Assignments

Useful Links

• Getting Started with gcc
• How to port code from Windows to Unix
• Note about Security of your files
• Visual Studio: Compiling your code with C99
• 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.

Instructions for Testing and Submitting Code

• Lab Assignment Submission Instructions
• Late Lab Submission Instructions Use this link to fix older labs

Labs

Lab Assignment 0 (posted - 01/23/19)

Due January 27, 11.59pm.

Lab Assignment 1 (posted - 01/29/19)

Due February 10, 11.59pm.

Note the grader and the tester will not be available until Friday, February 1st.

• Useful code page (posted - 01/29/19)
• Submission instructions (posted - 01/29/19)

Lab Assignment 2 (last updated - 02/09/19)

Due February 18, 11.59pm.

Note the grader and the tester will not be available until Wednesday, February 13th.

• Submission instructions (posted - 02/09/19)
• LC3b Assembler for Linux (posted - 02/11/19)

Lab Assignment 3 (last updated - 02/24/19)

Due March 10th, 11.59pm.

Note the grader and the tester will not be available until Wednesday, February 27th.

• Submission instructions (posted - 02/24/19)
• An example of simulator run
• The control store template in Excel and PDF formats.

Lab Assignment 4 (last updated - 03/16/19)

Due April 7th, 11.59pm.

• Submission instructions (posted - 03/16/19)
• You can use the following pdf files to show the changes you made to the datapath, state diagram and microsequencer. Please note that you can submit hand drawn diagrams.
  • datapath pdf file
  • state machine pdf file
  • microsequencer 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 grader 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.
• The control store template in Excel and PDF formats.

Lab Assignment 5 (last updated - 04/14/19)

Due April 28th, 11.59pm.

• Submission instructions (posted - 04/14/19)
• You can use the following pdf files to show the changes you made to the datapath, state diagram and microsequencer. Please note that you can submit hand drawn diagrams.
  • datapath pdf file
  • state machine pdf file
  • microsequencer file pdf file
• Important note: Make sure your Lab 4 implementation is correct before starting Lab 5. Passing all the tests does not mean that your Lab 4 is correct! An incorrect program may just happen to behave correctly on our test cases. It is your responsibility to ensure that your Lab 4 is correct. See this for more details.
• The control store template in Excel and PDF formats.

Lab Assignment 6 (last updated - 04/30/19)

Due May 10th, 5pm.

• NOTE: The official due date for the lab is Friday May 10th. However, we will accept late submissions without penalty until Wednesday May 15th, 11:59pm.
• Submission instructions
• 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
  • example2.asm, example2.hex, example2.dump, example2.state, example2.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.