Embedded Systems — question 2 of 10
Write a real answer. It is graded against the question's rubric, and the mastery movement is computed by the same engine the product uses. Scoring here is deterministic rather than model-written, so this page costs nothing to run and nothing is saved. In a track built from your own posting, the same rubric is graded by the model, which is what produces feedback about your reasoning rather than about coverage.
You write firmware that polls a peripheral status register in a tight loop, something like `while (STATUS_REG & BUSY_BIT);`, waiting for a hardware operation to finish. It works fine in a debug build, but the same code compiled with optimizations turned on for release hangs forever on that line. What is actually happening here, and what's the structural fix so this class of bug never comes back?