BlackMark
3e4bfbaf48
Its comment said "opening the port does not reset a board whose DTR is unwired, so this simply listens" — true of the tiny it was written against, false of an Arduino, and this is the generic harness. Where DTR is wired to reset, that open resets the part and the activation window comes first, so a fixture emitting its banner once says it on the far side of a wait the suite cannot know the length of: the window is a compile-time constant and nothing on the wire reports it. The suite read the silence as an application that never ran, on a board where it demonstrably had. So --marker-wait, defaulting to the 2.5 s that was hardcoded, and a failure that names the window as the candidate rather than leaving the next person to suspect the loader. The other half is the fixture: PUREBOOT_HEARTBEAT makes the observation independent of when the listener arrives, which is what the rig's own builds now pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>