|
Instructor TA TA |
Cyrus Bazeghi (cyrus@soe.ucsc.edu) TBA TBA |
Introduction to Computer Systems 2nd Edition, Patt and Patel, McGraw Hill, 2004. ISBN: 0-07-246750-9. Available at BayTree and at SlugBooks. REQUIRED
Computer Organization and Design: The Hardware/Software Interface, 2nd edition, Patterson and Hennessy, Morgan Kaufmann, 1997. ISBN: 1-55860-491-X or 1-55860-428-6. The CMPE110 text. Optional.
CMPE012c Lab Manual online!
HC11 Manual To be distributed midquarter. Free, courtesy of Motorola.
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.
You are expected to attend lectures. You are adults though and if you do not feel like coming that is up to you. There may be pop quizzes, this is not to punish students who are not present. If you do come to lectures please refrain from the following: talking to other students while the professor is talking, teasing other students (unless the professor is also teasing them), eating or drinking loudly or bringing food that smells like it should be buried not eaten, sleeping (if you do fall sleep you are agreeing that it is okay for the professor to have fun at your expense), asking questions that make the professor look like a moron (especially if they relate to spelling). Seriously though, feel free to ask questions that are appropriate, even if they make the professor seem dim.
The course work for this class will consist of weekly homework assignments, possible pop quizzes, two tests, and one final examination during finals week. Please check the current syllabus for grading criteria. It is STRONGLY recommended that you do all the homework assignements, both because they are graded and because it takes practice to learn some of the material. Also, homework material is of course on the examinations
Please ask question during lectures and make use of office hours. Good students are the ones that ask for help when they need it. Do not fall behind on the material as most of it builds upon the earlier stuff. This class teaches a lot of basics that you will need for future classes. The material is not difficult, if you find it so please come and get help right away.
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, including other sections. If you go to another section the students enrolled in that section will get helped first. Labs meet in BE109.
You must be enrolled in CMPE 12L to remain in this class (unless you have passed this class in the past)! Due to organizational difficulties, changing lab sections is not permitted. Labs will be submitted electronically and graded by the TA's. You are free to attend other lab sections but you are required to go to the one you signed up for.
It is expected that you have read the lab assignment and started the process of coming up with a solution before going to lab section. You will NOT finish the lab assignments if you do not spend time outside of lab sections programming. Coding can happen any place and anytime, all you need is paper and a pencil.
There is may be a fee for cmpe012L! The lab fees are posted at http://www.cse.ucsc.edu/bels/
Be sure to check out the cmpe012c Lab Manual as it has lots of helpfull material in it!!
We will be working with two assembly languages in this course: LC-3 (via a simulator) and HC11 (via a different set of tools and a really neat lab kit.) The LC-3 architecture is a very eligant RISC architecture. Many modern processors use RISC like features that the MIPS processor pioneered. The HC11 is from Motorola and is a microcontroller used in embedded applications. A microcontroller is basically a microprocessor with IO, memory, and other features "built" into it.
We will have semi-weekly lab assignments. We will experiment with "Paired Programming" (also called "Extreme Programming") this quarter. If students desire they can work with ONE partner. The critieria for this will be covered in more detail in class and rules will be posted in the Labwork section of the website eventually.
No collaboration is allowed on programming assignments unless explicitly permitted (unless you work in a pair and then only with your partner) 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 and lab. 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 IF NOT IN A PAIR AND THEN ONLY WITH YOUR PARTNER!!!!
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 lab and further damage to your academic career as appropriate.
See the current syllabus for evaluation criteria.
This page maintained by cyrus@cse.ucsc.edu.