CSE 141L - Lab 1 Turnin Instructions

Lab 1 Turnin Instructions

Due: Monday, Jan 24th @ 1:50 PM (Electronic Turnin is due at 1:50pm and paper turnin at start of class)
No late submissions will be accepted.
Post lab submission questions on the webboard.

Deliverables for Lab 1

Please make sure you turn in all files and follow the naming conventions described below for full credit.

Lab 1 Report Print Out
- A complete description of your ISA & answers to all the questions in Lab 1.
- A complete listing of your filter.asl assembly program (make sure it is commented).
- List at the start of the writeup all lab partner names, their emails and the account from which you electronically turned in your files from.
- Your report must be handed in at the beginning of class.
graphics.asl
- Your assembly language program (in ASCII text form) to implement the graphics algorithm.
- File format:
  - The assembly code must be heavily commented
  - Each instruction of your program must be on a separate line.
  - Example:
```
...
ld r2, 0(r1)  ; load the current character into r2
dec r0        ; reduce the number of characters processed by 1
bnz r0, loop  ; if all characters have not been processed go back to the start of the loop
...
```
Makefile
- Your makefile for compiling your assembler and emulator.
- Here is a sample makefile. Be careful, the tabs may have been lost in the move to the web page.
assembler.(c|cc|cpp|java)
- The source code for your assembler that takes an ASCII assembly language program (your graphics.asl) as input and outputs a machine code (hexadecimal) representation.
- Command line options:
  - Your program must take your graphics.asl as input with the -i command line option.
  - Your program must output to a file specified with the -o command line option.
  - Example command lines:
```
assembler -i graphics.asl -o graphics.bin
assembler -o graphics.bin -i graphics.asl
```
- File formats:
  - See the information for graphics.asl regarding the format of your input file.
  - The machine code output will be hexadecimal encodings of your assembly code.
  - Each machine code instruction will be represented by a single two (2) digit hex number on a line by itself.
  - Example:
```
...
0C
A4
BB
...
```
- Your assembler must compile and run on ieng9.ucsd.edu (Solaris UNIX) for credit. No exceptions.
emulator.(c|cc|cpp|java)
- The source code for your emulator that takes the machine code representation of the graphics algorithm.
- Command line options:
  - Your program must take your machine code as input with the -p command line option.
  - Your program must take a file with the graphics input (specified in Lab1 description) with the -i command line option.
  - Your program must output ALL OF DATA MEMORY to a file specified with the -o command line option.
  - Your program must output the cycle count for the emulation of your program/input to a file specified with the -c command line option. This is effectively the dynamic instruction count for a single cycle machine, and it should be an integer format: e.g. 140
  - Example command lines:
```
emulator -p graphics.bin -i graphics.txt -o final.txt -c cycles.int
emulator -i graphics.txt -p graphics.bin -o final.txt -c cycles.int
emulator -o final.txt -p graphics.bin -i graphics.txt -c cycles.int
emulator -p graphics.bin -o final.txt -i graphics.txt -c cycles.int
emulator -p graphics.bin -o final.txt -c cycles.int -i graphics.txt 
emulator -c cycles.int -p graphics.bin -o final.txt -i graphics.txt
```
- File formats:
  - See web page information for assembler.{c|cc|cpp|java} regarding the format of your machine code.
  - See the web page for information on input and output file samples.
- Your emulator must compile and run on ieng9.ucsd.edu (Solaris UNIX) for credit. No exceptions.
members.txt
- A text file containing the name, student id, and email for each member in the group, each field separated by a colon.
- Example:
```
Jane Doe: A01123443 : jdoe@ucsd.edu
John Bach: A01234678 : jsbach@ucsd.edu
Agent Smith: A15123555 : asmith@ucsd.edu
```

Turnin Instructions for Lab 1

Connect to ieng9.ucsd.edu using ssh on port 22 and login with your username and password.
Use the prep command to set up your account to turnin by issuing the command
```
prep cs141w
```
at the prompt. Your shell prompt should now look similar to
```
[cs141w] ieng9.ucsd.edu% 
```
Navigate to the directory containing all the files to be turned in for lab 1. The directory must contain only these files, otherwise the bundle program will not turn in your lab. It is recommended that you make a subdirectory specifically for those files in whatever directory you are working in.
Turn in your lab by tarring all your files into one file (Makefile, any source files and anythign else we will need to run your programs). Then run the turnin command to turn in that .tar file. Like this:
```
 turnin -c cs141w filename.tar
```
- Note: Every time you turn your lab in, it overwrites the previous files turned in by your account. If the lab is turned in multiple times only the last, and presumably current, version turned in will be graded.
Only one (1) submission per group is necessary. If you are working in a group, make sure that all group member names appear on your deliverables (excluding your Makefile).
No late turnins will be accepted. Turning in early and often is highly recommended.