NOTICE: You MUST participate in at least one in-person oral
discussion about quizzes or homework by December 29, 2026. After each
discussion, you must follow up by email and obtain the instructor’s
acknowledgment. Otherwise, you will receive no credit for any
quizzes.
You MUST participate in at least one in-person oral discussion about
quizzes or homework by December 29, 2026. After each discussion, you
must follow up by email and obtain the instructor’s acknowledgment.
Otherwise, you will receive no credit for any quizzes. The email must be
written in American English and sent to both the instructor and the
course teaching assistants. The instructor may ask you to improve your
understanding or work on specific topics, and you must follow those
instructions.
Homework
1 is out. Turn minirubik into hand-written RV32I with a working LED
Matrix visualization by Oct 8, then talk an AI agent through it in a
recorded LiveTrial session by Oct 18; skip either and the assignment
does not count.
If you voluntarily participate in the class discussions for Quiz1, please email
the instructor afterward, including your responses to the instructor’s
questions and any follow-up contributions. You will receive an
additional 10 points for Quiz 1.
In today’s class, we will discuss the progress of Homework 1
with the students. Ensure your code meets the requirements, is updated
in the designated forked GitHub repository, and has been successfully
pushed. When the instructor talks with you, you should paste the
hyperlink to your forked GitHub repository for Homework 1
here. \(\to\)2026-10-06
Quiz 3 is scheduled for Oct 21. Be sure to carefully review past
quizzes, understand their level of difficulty, and practice
thoroughly.
Homework1:
Because development of the CodeTrial project originally intended for
this assignment has not progressed as expected, the CodeTrial/LiveTrial
interactive component of this assignment has been canceled. Instead,
students must submit an explanatory video of at least 15 minutes. The
earlier two-phase schedule is also canceled: everything, including the
video, is due Oct 18, 2026, 23:59 (GMT+8).
Quiz 3 is scheduled for October 21 and will cover RISC-V assembly
programming, software optimization, instruction encoding, sequential and
combinational logic, and a review of Homework 1.
The follow-ups for Quizzes 1 and 2, including lecture discussions
and further improvements, have been updated in the syllabus. Please
review them carefully.
Homework 2 will be assigned next week, focusing on bare-metal
programming, an essential skill for embedded system engineers. Search bare-metal
via Google Career.
Yes, you can implement a few logic-like elements without
electricity.
Logic gates are primarily implemented using diodes or transistors
acting as electronic switches, but can also be constructed using vacuum
tubes, electromagnetic relays (relay logic), fluidic logic, pneumatic
logic, optics, molecules, or even mechanical elements. Now, most logic
gates are made from MOSFETs (metal–oxide–semiconductor field-effect
transistors).
sequential logic is a type of logic circuit whose output depends on
the present value of its input signals and on the sequence of past
inputs, the input history.
Quiz3:
RISC-V programming and instruction encoding + Digital systems / solution
Week 8 (Oct 27): Review + Datapath and Control
Announcement:
The textual description of Problem D in Quiz3 is correct,
but the accompanying image is incorrect. As compensation, all
participants of Quiz 3 will receive a 15-point increase.
If you voluntarily participate in the class discussions for Quiz3, please email
the instructor afterward, including your responses to the instructor’s
questions and any follow-up contributions. You will receive an
additional 10 points for Quiz 3.
“What I cannot create, I do not understand.” - On Richard Feynman’s
blackboard at the time of his death in 1988 / Build Your Own X
an interactive tutorial created by dramforever that introduces the
fundamentals of RISC-V assembly programming through hands-on
experimentation. Inspired by Easy 6502, it uses a browser-based
simulator to let learners observe every step of program execution — from
instruction decoding to register and memory state changes — without
requiring any software installation or toolchain setup.
The tutorial focuses on the minimalist yet complete RV32I + Zicsr
instruction set, guiding readers from their first simple instruction
sequence (addi, ebreak) to more complex topics such as arithmetic and
logic operations, branches, jumps, memory access, stack management,
function calls, control and status registers (CSRs), privilege levels,
exceptions, and even the construction of a bare-bones operating
system.
Constructing Hardware in a Scala Embedded Language (Chisel) is an
open-source hardware description language (HDL) used to describe digital
electronics and circuits at the register-transfer level that facilitates
advanced circuit generation and design reuse for both ASIC and FPGA
digital logic designs.
In today’s class, we will discuss the progress of Homework 2 and
Homework 3
with the students. Whether you are voluntarily or non-voluntarily
participating in the Q&A, you should follow the assignment
guidelines, prepare your HackMD notes, and set them to public.
When the instructor talks with you, you should paste the link to your
HackMD notes for Homework 2
here. \(\to\)2025-11-18
In today’s class, we will discuss the progress of Homework 2 and
Homework 3
with the students. Whether you are voluntarily or non-voluntarily
participating in the Q&A, you should follow the assignment
guidelines, prepare your HackMD notes, and set them to public.
When the instructor talks with you, you should paste the link to your
HackMD notes for Homework 2
here. \(\to\)2025-11-18
This semester, we will conduct 7 quizzes. Out of these, the best 4
will be selected for grading purposes.
The instructor will submit the grades on the school’s designated
deadline (Jan 23, 2026) for grade registration. This means that
students will have ample time to dedicate to the final project assigned
in this course.
Term
projects: Contact the instructor as early as possible. You must
provide the materials and demonstrate to the instructor before Jan 20,
2026. Deliverables
A development log and accompanying report
Complete source code sufficient for full reproduction
In today’s class, we will discuss the progress of Homework 3 and
Term project
with the students. Whether you are voluntarily or non-voluntarily
participating in the Q&A, you should follow the assignment
guidelines, prepare your HackMD notes, and set them to public.
When the instructor talks with you, you should update HackMD note here.
\(\to\)2025-12-02
Lockstep
systems are fault-tolerant computers that simultaneously perform
identical operations in parallel. Borrowed from military marching
terminology, these systems use redundancy to detect and correct errors.
With two systems (dual modular redundancy), errors can be identified,
and with three systems (triple modular redundancy), errors can be
automatically corrected through majority voting.
In today’s class, we will discuss the progress of Term project
with the students. Whether you are voluntarily or non-voluntarily
participating in the Q&A, you should follow the assignment
guidelines, prepare your HackMD notes, and set them to public.
When the instructor talks with you, you should update HackMD note here.
\(\to\)2025-12-02
Term
Projects: You must provide the materials and demonstrate to the
lecturer before Jan 19, 2027
The instructor sent an email on December 15 with the subject line
“Re: CompArch: Term Project Assigned — Read Carefully and Start Logging
Early”, outlining important guidelines and requirements for the term
project. Students are required to read the email carefully and respond
thoughtfully in accordance with the instructions provided.
Compiler First: The founders emphasized that an architecture is
useless without a working C compiler. Early efforts focused heavily on
porting GCC, LLVM, and Linux to ensure the hardware was actually
usable.
Community Power: By embracing open source, they allowed global
developers to fix bugs and optimize performance, moving much faster than
a single proprietary team could.
