Real-Time & Constraint Analysis

Real-Time & Constraint Analysis

Embedded products fail when the software is "correct" but too late, too hungry, or too large for the chip. This subject is about making timing, memory, and power constraints explicit before you design: hard vs. soft deadlines, worst-case latency, sampling rates, and what happens if a deadline is missed. You turn those constraints into requirements and checks, not afterthoughts.

Starting Points

• Real-time systems
• Liu, J. W. S. Real-Time Systems. Prentice Hall.
• FreeRTOS. Preemptive vs cooperative scheduling.

Key Points

• You classify timing needs in a studio scenario as hard, firm, or soft real-time and explain the consequence of a missed deadline.
• You derive measurable constraints (cycle time, latency, jitter, sampling rate, stack/RAM budget, energy budget) from stakeholder needs.
• You identify which functions must run on a schedule vs. which can be best-effort.
• You validate your analysis with a simple measurement or calculation (scope, logic analyzer, or cycle budget) rather than assuming the MCU is "fast enough".
• You document constraints so they can be traced into firmware design and tests.