ECE 550D: Fundamentals of Computer Systems and Engineering — Fall 2021

Class meeting times and location: TuTh 10:15–11:30AM and 1:45–3:00PM (2 sections) — Hudson Hall 125 and Wilkinson 130

Recitation meeting time and location: F 12:00–1:15PM — FITZPATRICK SCHICIANO B 1466

based on a diagram by Dr. Tyler Bletsch

• Wenxin Xu (wx65) — Head TA for projects
• Shiyi Jiang (sj255) — Head TA for homework
• Hanzhou Shen (hs312) — Head TA for recitations
• Ke Chen (kc426) — Head TA for cheating detection
• Libo Zhang (lz200)
• Qishen Wang (qw98)

• MW: 4:45–6:45
• TuTh: 9–11
• F: 10:30–11:30 & 3:00–4:00

Course Description

Learning Outcomes

• design combinational and sequential circuits at the transistor (CMOS) and gate/logic levels;
• implement, simulate, and test logic circuits;
• use Verilog hardware description language;
• write programs using Assembly language;
• describe and analyze how computer memory operates;
• describe the basic operations of IO devices, interrupts, and exceptions; and
• design, implement, and test a processor.

Textbook and Other Course Material

Grading Policy

• Recitations (10%): Recitations are sessions for hands-on practice using Quartus and Modelsim. Grades are based on completion (must demonstrate working module to TA).
• Homeworks (20%): About 5 homeworks (check the schedule below).
• Exam 1 (15%).
• Exam 2 (15%).
• Project (40%): Checkpoints that build up to implementing a processor.
• NO FINAL EXAM!
• Late policy: Late submissions are not allowed unless you have a valid excuse. In that case, email me about it as soon as possible and wait for a decision (might involve a penalty, depending on the excuse). Refer to this list of common but unacceptable excuses borrowed from Dr. Bletsch's webpage.
• Regrading policy: Regrade requests must be submitted no later than one week after the assignment grade is released.

Important Notes

***Extremely important advice:

• Start as early as you can! Leave ample time for testing!
• Review class lectures after every class (or before the next one).
• Manage your time well and work on multiple assignments in parallel. Split bigger task into smaller (realistic) ones. Make sure you use a calendar and a to-do list.
• Use Git to keep track of previous versions of your work and use a cloud storage service to back up your work (GitLab, GitHub, etc.).
• Ask questions! We are here to help! We want you to succeed!

We can only grade what we receive. Always check what you are submitting and make sure you submit the right files.

Contacting the instructor and the TAs:

• For questions that can be answered by any TA or the instructor: use Ed Discussion
• To contact a specific TA or the instructor: use email (do not text, facebook, ...)

Misconduct

• Academic misconduct will not be tolerated and will be taken very seriously.
• You are expected to complete the assignments individually unless otherwise stated.
• Students are encouraged to share ideas, learn from each other, and learn from online sources, but cheating is not tolerated.
• Any borrowed design/code/etc. — if allowed to be borrowed — should be properly cited.
• Students suspected violating the Duke Community Standard will be reported.
• In addition to the measures taken by the administration, the affected assignment(s) will receive zero credit, or possibly -100% in extreme cases.
• If you are considering this course of action, please see me instead, and we can work something out! I want every student in my course to be successful.
• Note that programming submissions will be compared to one another and to previous semesters using Stanford's Measure of Software Similarity (MOSS) to detect signs of plagiarism.

Communications Support at Pratt

Tentative Schedule