Computer Science C335 , A593: Computer Structures, Spring, 2009

Necessary access:

C335 will use the laboratory space and equipment in Lindley Hall 035. Students may use the lab facilities whenever there is not a conflict with a scheduled laboratory session.

Overview

Textbooks

Required Text

• Sloss, Symes, and Wright. ARM System Developer's Guide; Designing and Optimizing System Software , San Francisco: Morgan Kaufmann/Elsevier (2004).
  

• Recommended C Reference

  • The classic is
    Kernighan and Ritchie, The C Programming Language, Upper Saddle River, NJ: Prentice Hall PTR, 2nd edition (1988).
  • However, this one is terser but will be a longer-lived reference (includes C99):
    Samuel P. Harbison, III, and Guy L. Steele, Jr. C, A Reference Manual, Fifth Edition, Upper Saddle River, NJ: Prentice Hall, Fifth Edition (2002).
• Free documentation:

  Communication

  On individual or immediate matters, contact your instructor or associate instructor via email.

  
  We very much like to talk to students after class or in posted office hours. Email can be awkward for detailed answers, so reread your email note before you send to make certain that it is clear. A very good use of email is to schedule an appointment for technical conversations.
  If you have a personal emergency, by all means send us email.
  If other office hours are necessary, we'll move some or post more.
  

  ---

  Course Content

  This course is designed very much by Professor Geoffrey Brown. C335 will explore how programs written in a high level language are evaluated by a processor to control the physical world. In particular, we will use C to write programs that control "Goofy Giggles" - a 3 wheeled robot with an embedded processor, an infrared (IR) remote control, an audio system, and various sensors. In the process we will touch topics covered in a number of subsequent CS classes including compilers, operating systems, computer architecture, and digital design. It's obvious that we will be skimming the surface of these topics; for example, we will examine what a compiler and its associated tools (assembler, linker) do in some detail, but not how they are implemented to perform their function. Our goal is that at the end of this course every student will be able to explain, in technically accurate manner, the path from program to I/0 and will be proficient in using one representative set of tools to write programs to control a defined physical world - Goofy Giggles. The progression of experiments introduces embedded system programming, programmed I/O, IR communications, PWM motor control, A/D based sensors, interrupts, and DMA.

  Lecture Topics

  The topics that we will consider from the book(s) are:
  • Computer Instructions
    • Operands and Operations
    • Instruction Representation
    • Logical Operations
    • Control Flow Operations
    • Addressing
    • Correspondence Between C and Assembly Language
  • Computer Arithmetic
    • Number Representations
    • Addition and Subtraction
    • Multiplication
  • Register Transfer Level Processor Descriptions
    • Datapath Block Diagrams
    • A Simple Register Transfer Language
    • Describing Instruction Interpretation in RTL
  • The Memory Hierarchy

  Tentative Readings/Lecture Schedule

  Attendance is required; one cannot run a lecture-lab course without your presence.
  Goofy can C.
  due Feb. 19--20

  Week	Monday	Wednesday	Lab
  1, Jan12	Intro, UNIX	Unix Shell/C	Shell/Editor Tutorial due Jan 22--23
  2, Jan19	Martin Luther King, Jr.	C / Make HW1 due Jan. 26	C/gdb due Jan. 29--30
  3, Jan26	Make/Data Repr.	Numbers HW2 due Feb. 4	Numbers due Feb. 12---Feb. 13
  4, Feb2	Numbers	LPC computer HW3 due Feb. 11	Numbers due Feb. 12--13
  5, Feb9	Review and QUIZ	ARM Instruction Set Sec. 2.0--2.3, Chap. 3 HW4 due Feb. 18
  6, Feb16 Career Fair Feb17	ARM Instruction Set Chap. 3 Career Fair Feb17	Embedded Prog, Communication to Goofy HW5 due Mar. 9	Lights and Switches due Feb. 26--27
  7, Feb23	Embedded Prog	Goofy IR reception	Motors and Sound due Mar. 5--6
  8, Mar2	More on IR C to Assembly	C assembled	IR Decoder pt. 1 due Mar. 12--13
  9, Mar9	Assembly optimization Exercise due: HW5 HW6 due Mar. 25 and a solution	Assembly optimization	IR Decoder pt. 2 due Mar. 26-27
  Mar16	recess	recess	Goofy can see.
  10, Mar23	Interrupts	Interrupts	GG Resurrection due Apr. 2--3
  11, Mar30	Interrupts	TEST and an answer key.	Drive by wire due Apr. 9--10
  12, Apr6	Logic/Adders	Logic/Adders	Interrupts buttonmain.c main-lec.c due Apr. 16--17
  13, Apr13	Processor as Interpreter	Processor as Interpreter Bring 6 copies of this sheet. HW7 due Apr. 22	Hi Jack! Attacking the OS due Apr. 30--May 1.
  14, Apr20	Processor as Interpreter	The Memory Hierarchy; read textbook Chap. 14.1--14.3.	work
  15, Apr27	Array access	Bill Hohl, ARM presentation	Final reports due
  16, May4	study	study	May 8 FINAL EXAM 10:15am--12:15pm With prior arrangements, one can start as late as ????

  ---

  Grading

  Grades are calculated as follows:
  • Labs 47%
  • Two midterms: 10% each
  • Final 20%
  • Unannounced quizzes (end of class) 3%
  • Homework 8%
  • Participation 2%

  Participation

  Participation in the class can take many forms: attendance at lectures and discussions, asking and answering questions posed in class and in lab, and prepared questions even during office hours.

  ---

  Quizzes and Exams

  There will be two 75-minute midterm tests, and a two-hour final exam. They will be weighted roughly 1:1:2 but (if, for instance, one turns out to be inordinately difficult) we reserve the right to tune these weights. Many questions are subjective (written paragraphs, code), and it is difficult to assure that one point on the midterm is the same value as another point on the final exam.
  • February 11: Midterm Test
  • April 1: Midterm Test
  • May 8: Final Examination (10:15am - 12:15pm).

  Excused Absences

  Programs are due on the announced date, immediately before your lab,because solutions may be discussed immediately thereafter; late assignments would be accepted only under the conditions similar to what could justify an Incomplete. All grades become final one week after the material is returned to you. If there is a foreseeable medical, personal, or professional reason requiring you to miss a lab or a test, notify us in advance and get written assent from the instructor. Examples: Hyperbaric treatment, funeral of family member, or an invitation to Chicago for a job interview.

Homework Policy

Homework assignments must be turned in by the beginning of lab on the due date. All homework submission will be through Vincent.

Laboratory Policy

It is required that you attend the laboratory section since we will be using this to provide specific information relating to lab.
You will be working on the laboratory experiments with a partner. Each partner is expected to write an independent report on each experiment. The report should be a concise description of problem attacked, strategies used and issues handled in solving the problem, and should include the code developed.
The report is due on the day of the laboratory section at which the next experiment is initiated. All reports must be turned in by the beginning of the lab through Vincent. There will be two assignments available there; for instance, "Lab 3 Thursday," and "Lab 3 Friday." If you are in the Thursday lab, you should use the former with a cutoff of 2:30pm Thursday and, if in the Friday lab, then the latter, similarly.

Academic Integrity

Read the Computer Science Department's Statement on Academic Integrity to be sure you understand the rules under which computer science courses operate.

Withdrawal

The last day to drop a course with an automatic W is Wednesday, March 5. After that date, a student may withdraw only with the permission of the Dean. This approval is given only for urgent reasons related to extended illness or equivalent distress.

Incomplete Grade

An Incomplete (I) final grade will be given only by prior arrangement in exceptional circumstances conforming to university and departmental policy , in which there has been some emergency late in the semester that interferes with your successful completion of the course and course work has been completed in passing fashion until the emergency.

Links

• Lab FAQ http://www.cs.indiana.edu/Facilities/hardware/h335_tools/h335_lab.html
• Vincent https://www.cs.indiana.edu/cgi-pub/c335/vincent3/student.cgi
• Course specification http://www.cs.indiana.edu/classes/c335/h335spec.html
• A reference card for the emacs editor.
• A reference card for the vi editor.
• A tutorial on make.
• A tutorial on gdb. And a quick reference card
• Ordinarily a citation to Wikipedia is suspicious, but the article on the IEEE 754 floating point standard is pretty good.
• Indiana University Computer Science Department Home Page
• The ACM Homepage
• Application to join ACM



[Site Map]

Home | Contacts | Courses | Academics | Research | People | Calendar | Resources | Facilities

Page Owner: David S. Wise   Last Modified: 2009 January 12

© D. S. Wise, Geoffrey Brown, and Trustees of Indiana University Email: info@IU CS Department