knaxuslearn · build · ship

Roadmaps / STM32 / Who this is for

Read first

Who this is for

Hours by path (core path only; the work version is extra).

You areStart atSkipYour assignmentsYour milestone scopeAim for
Fresher (under a year of work; C basics, Git, a shell)Week 0, then Week 1Nothing. Do all the weeks, and plan 20 (see the time model)Practice projects 1 and 2 in each phase, checkpoints 1 to 4Core scope: floating-point PI loop, CRC-32 image check, trial boot with rollback2 Sound on every dimension
Senior (5 to 8 years, owns services or firmware)Week 1 (skim Weeks 1 and 2)Week 3 if you already configure clock trees (still run the Week 4 latency table)All practice projects, checkpoints 1 to 4Adds a signed image, a fault-injection suite run from CI, ADRs 6 and 73 Proven on every dimension
Staff (10+ years, sets direction)The fast lane (12 hours, below), then Phase 4Weeks 1 to 4 in full and Phases 2 and 3 (use their Check yourself questions and checkpoint rows as a gap test)Checkpoint 4, Checkpoint W and the decision memoAdds an update-strategy memo with numbers, field diagnostics, a platform memo3 on all, 4 on two
Principal (15+ years, sets strategy)The milestone section, the fast lane, Phase 4, then Interview topicsThe weekly tables of Phases 1 to 3The work version (Checkpoint W below) on a real product, plus a review checklist others reuseAdds a product-line decision memo with a measured outcome3 on all; 4 only through the work version
PathPartsHoursWeeks at your pace
FresherWeek 0 (optional, 10), Weeks 1 to 16128 (160 with the extra checkpoint weeks)20 at 8 hours; 32 at 5; 40 at 4 (on the 160-hour plan)
SeniorSkim Weeks 1 and 2 (4), Weeks 4 to 16 (104), Senior-only items (24)13222 at 6 hours; 27 at 5
StaffFast lane (12), Phase 4 (32)44, plus 30 for Checkpoint W (74)74 hours: 19 at 4 hours; 25 at 3
PrincipalFast lane (12), Phase 4 (32), Checkpoint W or W-P (30)7425 at 3 hours

The fast lane (12 hours) is for Staff and Principal readers: build only the Checkpoint 1 harness from the Cube TIM and ADC examples and add a printed reset reason. It gives Checkpoint 4 the running loop and the missed-sample counter it needs. If you already own a firmware product with a measured loop, run Checkpoint 4 on it and skip the fast lane. A Principal may instead review one other person's Checkpoint 4 hand-in against the four levels in How the plan works (about 8 hours) and run W-P alone.

Fresher 20-week schedule. Checkpoint weeks (4, 8, 12 and 16) each hold a whole checkpoint, so they take two plan weeks: build, then capture. Anyone who needs more than 8 hours for a checkpoint may do the same.

PhasePlan weeksRoadmap weeks done
11 to 51, 2, 3, 4, 4
26 to 105, 6, 7, 8, 8
311 to 159, 10, 11, 12, 12
416 to 2013, 14, 15, 16, 16

Do Practice projects 1 and 2 of each phase in its first weeks, before the checkpoint week.

Prerequisites for a fresher. If one is missing, do Week 0 first.

  • You can read and write C: pointers, structs, bit masks and shifts, volatile.
  • You can use a Linux, macOS or Windows shell, and Git (commit, branch, diff).
  • You can script in Python to read a log file and print simple statistics.
  • You know what a voltage, a resistor, a capacitor and a pull-down resistor are.
  • You have seen a binary number and a hexadecimal address in a datasheet.

This roadmap covers one platform, the STM32G4 family (Arm Cortex-M4F), through one board. For boards in general, including Linux boards, take Embedded Systems Engineer first. For the Arm architecture across profiles, take the ARM roadmap when it is published.