Weekly Schedule (Tentative)
| Week | High School (HS) Students | CSUF Undergraduate Students |
|---|---|---|
| 1 | • What a chip is and what it does • Everyday examples of chips • Inputs, outputs, and simple rules • Reflection: “Where do I see chips?” | • Semiconductor overview • Digital vs. analog chips • Overview of the semiconductor ecosystem |
| 2 | • “If–then” logic in real systems • Block diagrams of systems • Conceptual chip design flow | • CMOS basics • Design → synthesis → layout → fabrication • Intro to simulation workflows |
| 3 | • Step-by-step execution of simple programs • Instruction flow diagrams • Concept of registers and operations • Each instruction corresponds to a hardware action | • Datapath overview (ALU, registers, PC) • Instruction formats • System-level processor design |
| 4 | • Logic flow using diagrams • Understanding operations (add, subtract, logic) • Operations represent what hardware is built to do | • Verilog syntax and modules • ALU implementation • Simulation and waveform analysis |
| 5 | • State machines on paper • Instruction sequencing • How systems change over time • State machines show how hardware follows a program | • FSM implementation in Verilog • Control logic design • Testbenches and debugging |
| 6 | • Program tracing (step-by-step execution) • Connecting system components • Tracing a program = simulating hardware cycle-by-cycle | • Integrate datapath + control • Execute simple programs |
| 7 | • Manual test cases • Identifying errors in logic • Debugging means finding where hardware behavior goes wrong | • Debugging processor behavior • Verification strategies |
| 8 | • Big-picture review of chips • Industry applications and careers • Programs run because hardware is designed to execute them • Presentation preparation | • Synthesis (area, timing) • Design tradeoffs • Presentation preparation • Send designs for fabrication |
| 9 | • Joint presentations (system explanation) • Reflection and discussion • Explain how a program is executed by hardware | • Joint presentations (technical depth) • Design results and lessons learned |