Main course page: ECE348 Main Page
Board test procedures - These are tests to help you make sure your board is working with both USB and serial cables.
File submissions will be made using the course AFS space. Handins will
be made to the location: /afs/ece/class/ece348/handin/ . In this directory there will be a directory for each lab/prelab (e.g. prelab_01) and subfolders for your group (or individual). The actual handins go into the early/ontime/late folders in the group/individual subfolders. You
should be able to access this space when logged in with your ECE username on
any of the ECE systems (e.g. color machines).
Make sure you are using your ECE login for submissions, NOT your Andrew login.
There will be a separate
folder for each assignment (e.g. prelab_01, lab_01, etc. and for you or your lab
group under each assignment). Late submissions will be treated in
accordance with the course late policy. If you overwrite or otherwise
update a file, the time stamp displayed will be treated as the hand-in date and
time for the entire assignment. If you want to submit a draft and
overwrite the files before the deadline that is fine.
Technical glitches can (and probably will) occur during the course of the semester. We will try to be reasonable, but it is your responsibility to submit your work on time. You should plan ahead enough so that you can turn your work in comfortably before the deadline. Report any problems with the submission as soon as you are aware of them. Most technical issues, especially those avoidable with reasonable planning, will not result in an extension of the deadline.
When grading is completed look for feedback in your subdirectory at this location: /afs/ece/class/ece348/handin/feedback/
All submitted prelab files (which are entirely YOUR OWN work) shall include
the following information in a header at the top of the first page:
All submitted lab files (which are the work of your two-person lab group)
should include the following information in a header at the top of the first
Failure to include this information will result in points deducted from your
grade. Repeated failure to include this information could result in your
submissions not being accepted at all.
All prelab filenames shall have your andrew ID appended according to the
So if your Andrew ID is pk1g, submitting lab1_prog1.c, your filename should be "lab1_prog1_pk1g.c".
All lab filenames shall have the group number appended according to the
<base filename>_g<group #>.<extension>
So if you were group 3A, submitting lab1_prog1.c, your filename should be "lab1_prog1_g3A.c".
Use descriptive, meaningful file names for the base file name! It is not the TAs job to decipher your personal file name scheme!
Good: lab1_prog1_g3A.c, prelab1_handin_yourAndrewID.pdf, lab1_handin_g3A.pdf
Bad: myCoolLab.c, lab_thisoneworks.c, DOC00001.PDF
In general, each lab or prelab is divided into parts which require only a
single .c or .asm file. These file should contain the header information
described above. Unless directed otherwise by specific directions in the
lab, submit only the relevant files and not files generated by the Codewarrior
system or files we give you that you haven't modified.
SHOW YOUR WORK when answering questions. For example, with numeric calculations show the equations you used to get the answer. Answers without a reasonable amount of supporting work shown will receive no credit.
All lab write ups shall be submitted in Adobe Acrobat (.pdf) format.
No other format will be accepted, unless stated otherwise for a specific
lab. You can access a free windows PDF printer here:
can also use the ps2pdf utility installed on any of the Andrew or ECE
Because of some confusion with using the virtual machine on lab machines, please adhere to the following steps in order to successfully connect to the module board.
FILES ARE LOCAL TO A COMPUTER AND PERSIST ACROSS USER ACCOUNTS FOR A VM. Every time before logging out, save your files elsewere and DELETE THE LOCAL COPY. Looking at other students' files that may be left on the VM is a violation of course policy.
NOTE: If you want to run your program using the project board (big board), then you do not need to use the 32 bit virtual machine - open CodeWarrior directly from the 64 bit host machine instead.
Monitor this section for updates about lab procedures, lab bugs, and general lab-related information. In general, we will post to the 348 blackboard announcements section, but check here first if you're having a problem!