|
Instructor Lab TA Class TA |
Cyrus Bazeghi (cyrus@cse.ucsc.edu) Joseph Sung (chengyus@soe.ucsc.edu) Dan Yuan (dyuan@soe.ucsc.edu) |
A Programmer's View of Computer Architecture, Goodman and Miller, Saunders College Publishing, 1993. Available at BayTree and at SlugBooks. On reserve at the science library.
HC11 Manual To be distributed midquarter. Free, courtesy of Motorola.
CMPE012c Lab Manual -- get your copy at the Baytree Bookstore or online!
Computer Organization and Design: The Hardware/Software Interface, 2ed, Patterson and Hennessy, Morgan Kaufmann, 1997. The CMPE110 text. Optional, on reserve at the science library.
Our web site: http://www.cse.ucsc.edu/classes/cmpe012c
Check the newsgroup and web page regularly. You are responsible for all announcements on the web page, in the newsgroup, and in class.
The newsgroup ucsc.class.cmpe12c is available for our use. Use netscape, pine, or rn
(or xrn) to read the newsgroup. Instructions.
In addition to going to lectures, you are expected to attend one lab section twice weekly. You may go to the lab at any time, but questions from students who are signed up will always get first priority. Labs meet in BE109.
There are weekly 12L lab sections. You must be enrolled in CMPE 12L to remain in this class (unless you have passed this class in the past)! The lab assignments may be due on either of your two lab days (to be announced each week). Due to organizational difficulties, changing lab sections is not permitted. Labs will be submitted electronically and graded by the TA. You are free to attend other lab sections but you are required to go to the one you signed up for. People assigned to a lab section have priority during that time.
There is a $10 lab fee for cmpe012L! The lab fees are posted at http://www.cse.ucsc.edu/bels/
Be sure to pick up a cmpe012c Lab Manual!!
We will be working with two assembly languages in this course: MIPS (with the SPIM simulator) and HC11 (via a different set of tools and a really neat lab kit.)
We will have semi-weekly lab assignments. No collaboration is allowed on programming assignments unless explicitly permitted in the assignment writeup. When permitted, collaboration must be acknowledged and may only be with students currently enrolled in CE12C. Failure to give credit when collaboration is allowed is a form of academic dishonesty and can be grounds for failure of the course. Collaboration is the discussion of the assignment and how to solve it, it is not discussion of how to code it. DO NOT EVER AT ANY POINT SHARE ACTUAL CODE!!!!
Academic honesty is a requirement for the course. As mentioned, all assignments must be your own independent work. Similarly, cheating on the midterm or the final will result in failure in the course and further damage to your academic career as appropriate.
See the current syllabus for evaluation criteria.
This page maintained by cyrus@cse.ucsc.edu.