ECE 30 - Introduction to Computer Engineering

Spring 2012





Practical Information

Course load

4 units

Prerequisites

with grades of C- or better

Lectures

Tuesday & Thursday 5:00-6:20pm, CENTR 214 (20 lectures in total)

Lab sections

Monday, Tuesday, Wednesday, Thursday 7:00-9:50pm (EBU2, 333A), led by TA and/or professor.

Discussion sections

Monday 9:00-9:50am (CENTR 214), led by the professor.

Quizzes will be held during the Monday discussion sections.

Final Exam

7:00-10:00pm, Thursday, June 14th, 2012

Instructor

Gert Lanckriet

Email: gert@ece.ucsd.edu
Office: 5604 Jacobs Hall
Office hours: Monday 10:15-11:30am / Thursday 6:30-7:00pm

Due to the large size of the class, Gert will forward every ECE30 email he receives to the head TA, at ecethirty@gmail.com, except for email marked with [FOR THE PROFESSOR ONLY] in the subject line (which he may still forward to the head TA, depending on the question).

Head TA

Janani Kalyanam

Email: ecethirty@gmail.com
Office: Janani will meet students in EBU2, room 333A
Office hours: Wednesday 11:00am-12:00pm, Friday 11:30am-12:30pm (week 1 - 4); shared office hours with Akinyinka (week 5 - 10)

If you have any questions related to ECE30: ALWAYS email the head TA, at the above email address. The head TA will route your question appropiately, to the professor or any of the other TAs.

Head Project TA

Akinyinka Omigbodun

Office: Akinyinka will meet students in EBU2, room 333A
Office hours: see project assignment

TAs / Tutors

Ansum Dholakia

Office: Ansum will meet students in EBU2, room 333A
Office hours: Tuesday 2:00-3:30pm, Friday 10:00-11:30am



Bryan Binotti

Office: Bryan will meet students in EBU2, room 333A
Office hours: Monday 12:30-2:00pm, Thursday 9:00-10:30am



Tsung-Yi Lin

Office: Tsung-Yi will meet students in EBU2, room 333A
Office hours: Tuesday 10:00-11:30am, Wednesday 3:30-5:00pm

Jianjian Gao

Office: Jianjian will meet students in EBU2, room 333A
Office hours: Wednesday 12:00-1:00pm, Thursday 1:00-2:00pm

Grading

Quizzes: 40%
Programming Project: 15%
Final Exam: 45%

Back

Class Schedule and Suggested Reading

Full schedule of lectures, discussion sections and lab sections, and suggested reading can be found here.

Back

Updates & Announcements

Back

Course Materials

Topics


Textbook

The textbook for this course is ``Computer Organization and Design, Patterson and Hennessy'' (3rd, 4th or 5th edition).

Podcast

Podcasts for the lectures of this course are available at http://podcast.ucsd.edu/

Lecture Notes / Slides


SPIM Simulator

You can download a PC version or a Unix version from here. Ubuntu users can type "sudo apt-get install spim". In addition, UC Berkeley maintains a Web page for a MAC OSX version.

You can find a nice tutorial for the SPIM simulator here.

Note to Windows 7 users: If SPIM complains about a missing "exceptions.s", you can fix it by going to Simulator->Settings, and changing the path from "C:\Program Files\PCSpim\exceptions.s" to "C:\Program Files (x86)\PCSpim\exceptions.s".


Study Problems

Study problems with solutions will be posted weekly. It is strongly recommended that these problems be worked out and thoroughly understood (quiz problems will be based on material covered in class, lab problems and study problems).

Week 1 - Performance Measures: study problems.

Week 2 - Assembly: Basics: study problems.

Week 3 - Assembly: Procedures: study problems.

Week 4 - Assembly: Procedures: study problems.

Week 5 - Arithmetic for Computers: Logic, Negative Numbers, Adders: study problems.

Week 6 - Arithmetic for Computers: Negative Numbers, Real Numbers, Adders, Multiplication: study problems.

Week 7 - CPU Design: study problems.

Back


Labs

Lab week 2 (mandatory): assignment 1 (solutions), assignment 2 (solutions), sample.s.

Lab week 3 (mandatory): assignment (solutions).

Lab week 4: assignment (solutions).

Lab week 5 & 7 (mandatory): programming project (more information under Programming Project).

Lab week 6: assignment (solutions).

Back


Quizzes & Final Exam

Some example problems will be posted to give you an idea of possible quiz problems.

Week 1 - Performance Measures: example problems (solutions).

Week 2 - Assembly: Basics: example problems (solutions).

Week 3 - Assembly: Procedures: example problems (solutions).

Week 4 - Assembly: Procedures: example problems (solutions).

Week 5 - Arithmetic for Computers: Logic, Negative Numbers, Adders: example problems (solutions).

Week 6 - Arithmetic for Computers: Negative Numbers, Real Numbers, Adders, Multiplication: example problems (solutions).

Week 7 - CPU Design: example problems

Quizzes are based on material covered in class, lab problems and study problems. They will be held during Monday discussion sections as indicated on the schedule. Every Sunday before a quiz, there will be a special "quiz office hour", 2:00-3:30pm in EBU2, room 333A.

Final: June 14th, 7:00-10:00pm. No calculator, no cheat sheet.

There will be a review session the day before the final (Wednesday June 13th), 7:00-9:00pm, in EBU2, room 333A, with instructor and TAs present.

Back


Programming Project

The project: Selecting Order Statistics - assignment, project submission.s, examples, description of median5.

Due: Thursday, June 7, 2012

The programming project must be done in groups of two. You may select your own partner, from the same lab section as yours.

The programming project is in MIPS R2000 assembly language. You will need to download a simulator called SPIM on your own computer, which can be used to verify the correctness of your assembly language program. You can use either the PC (Windows) version, the MAC OSX version, or the Unix/Linux version.

You must turn in a commented source code electronically by the due date.

Please follow the instructions in the assignment carefully.

If the TA can't easily run your program, you will lose points.

The program is due by 5PM on Thursday, June 7, 2012. Any program received after that will lose points for being late.

Turn in the program by emailing it to Akinyinka at ecethirty@gmail.com with subject line ECE30 PROGRAM. In the email body include the email addresses and full names of both partners. Be sure to attach the program!

Copying code will not be tolerated. It will be penalized with an "F" grade for the class, for both group members of both the team that provided the code as well as the team that copied the code.

Back