Embedded Systems
RTOS Bring-up for Field Devices
Hands-on lab sequence for scheduling, drivers, and power states on a Cortex-M class board.
Format: Bootcamp · Level: Intermediate · Duration: 5 weeks
Tuition (informational): 980,000 KRW
Lead mentor
Former lead firmware engineer on consumer gateways; prefers small diffs and loud test names.
Overview
You move from a bare board to a predictable firmware loop: interrupt priorities, DMA hand-offs, and logging that stays readable under load. Labs use real sensors and a gateway so you can observe traffic the way production teams do. Mentors focus on reviewable commits and naming conventions that survive hand-off to cloud teams.
What is included
- Board bring-up checklist you can reuse on new silicon
- Thread timing exercises with logic analyzer captures
- OTA staging pattern without blocking factory recovery
- Structured logging that maps cleanly to cloud log streams
- Power-state table workshop with measured draw targets
- Pairing sessions on readable HAL boundaries
- Capstone: ship a two-week soak test plan
Outcomes
- Ship a firmware image with documented rollback
- Explain interrupt latency trade-offs to peers
- Produce a power profile baseline for your board
Participant notes
-
The RTOS Bring-up labs finally connected JTAG traces to the story our cloud team tells about latency. Week two felt dense, yet the soak-test capstone made the pacing worth it.
Minseo K. · Firmware engineer · 5/5 · survey