Prerequisites Basic computer literacy and a willingness to document experiments.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Voltage/current and safe measurement Digital logic and GPIO Datasheets and pinouts Serial communication concepts C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools Breadboard Multimeter Microcontroller board
Hands-on exercise Build a safe LED/input circuit and document pin mapping and expected signals. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A documented circuit and hardware bill of materials. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Measurements match the circuit design and safe voltage limits. Evidence must be reproducible and tied to C Programming.
Next: C/C++ fundamentals & memory constraints
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Types, pointers and memory layout Interrupt-safe code and volatile Fixed buffers and bounds Build flags and linker output C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools GCC/Clang GDB Static analysis
Hands-on exercise Write a small driver-style module and test boundary conditions on host and device. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A portable firmware module with host-side tests. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Memory use and input bounds are understood and documented. Evidence must be reproducible and tied to C Programming.
Next: Microcontroller peripherals & buses
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn GPIO interrupts and debouncing Timers, PWM and ADC UART, I2C and SPI Peripheral registers and HAL trade-offs C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools MCU SDK Logic analyser Serial monitor
Hands-on exercise Read a sensor over a bus and validate the signal using a logic analyser or simulator. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A sensor acquisition module with documented timing. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Readings are stable and timing constraints are measured. Evidence must be reproducible and tied to C Programming.
Next: RTOS, scheduling & concurrency
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Tasks, priorities and scheduling Queues, mutexes and semaphores Interrupt-to-task handoff Deadlock and stack analysis C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools FreeRTOS or vendor RTOS RTOS trace tools Debugger
Hands-on exercise Separate acquisition and communication tasks and test queue saturation. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A multi-task firmware prototype with timing notes. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Tasks meet timing targets and shared resources are safely protected. Evidence must be reproducible and tied to C Programming.
Next: Drivers, boot & embedded Linux
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Boot chain and bootloader Device tree and kernel modules Character devices and sysfs Cross-compilation and root filesystem C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools Embedded Linux SDK Buildroot/Yocto concepts Serial console
Hands-on exercise Build a minimal target image or driver exercise in an isolated development setup. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A reproducible embedded image/build configuration. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria The build is reproducible and device dependencies are documented. Evidence must be reproducible and tied to C Programming.
Next: Connectivity, security & reliability
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Secure boot and firmware update Device identity and key provisioning TLS/MQTT and offline buffering Watchdogs and fault recovery C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools MQTT broker TLS test certs Firmware update mechanism
Hands-on exercise Simulate a disconnected device and verify buffered events and authenticated reconnect. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A secure device-to-service data flow with threat notes. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Credentials are unique per device and reconnect behaviour is bounded. Evidence must be reproducible and tied to C Programming.
Next: Hardware-in-loop testing & production
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Unit and hardware-in-loop tests Power and thermal measurement Manufacturing test fixtures Logging and field diagnostics C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools Logic analyser Power meter CI build tooling
Hands-on exercise Run a repeatable sensor/peripheral test and record tolerance limits. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A test fixture concept and manufacturing verification checklist. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Known hardware tolerances and failure modes are covered. Evidence must be reproducible and tied to C Programming.
Next: Capstone: connected embedded device
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn System block diagram and interfaces Firmware architecture and test strategy Security/update and failure recovery Build, BOM and field support C Programming specialization: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Tools MCU or SBC Sensor/actuator Git and test rig
Hands-on exercise Demonstrate normal, disconnected and recovery scenarios with recorded evidence. Context for this route: Track-specific focus: C Programming. Use the tools and standards named in this path; avoid treating this route as a generic overview of Embedded Systems & IoT.
Suggested project A working device prototype with source, schematics, BOM and test report. The outcome must directly demonstrate C Programming, not merely list tools.
Learning resources Completion criteria Another engineer can reproduce the build and understand device safety boundaries. Evidence must be reproducible and tied to C Programming.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete