Embedded Systems
Lab Curriculum.

BUG FOUND: ECE graduates who know circuits in theory, but cannot debug firmware on hardware.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. C for embedded: pointers, registers, and bit operations applied to hardware.
2. Microcontroller basics: GPIO, timers, interrupts, and UART.
3. Reading datasheets and schematics to find pin / voltage / timing facts.
4. Sensor basics: ADC, digital sensors, and noisy readings.
5. Debugging tools: serial logs, LEDs, multimeter concepts, and debugger basics.
6. Writing a small firmware task and testing it with a test log.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: C toolchain, simulator / dev board concepts, serial logs, datasheets.

• BUG #1: Sensor reads garbage values — decide code vs wiring vs sensor fault, fix the real cause, prove stable readings.
• BUG #2: Firmware hangs intermittently — find the interrupt / timing / stack cause, fix it, show a long stable run.
• BUG #3: Hardware-software mismatch: code expects one pin, board uses another — find it in schematic vs code, correct it, document the change.
• BUG #4: Timing bug: a task runs too late / too often — measure timing, fix the timer / interrupt priority, verify.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Navigate firmware + hardware docs for an unfamiliar board: map pins, peripherals, and code modules.
• Trace a fault to code vs circuit with evidence, not guessing; test both hypotheses.
• Refactor a messy firmware module (split init, loop, and handlers) without changing behaviour.
• Review a peer's firmware change for timing, interrupt safety, and hardware limits.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — working device logic demonstrated end-to-end, with a test log and a fault report.

$ ship → PROOF — exact output: working device logic (code + demo), test log, and a fault report.

$ run --lab embedded-systems → ✓ SHIPPED, job-ready