Resynchronize emulated device framing after a corrupt header
One damaged length prevents decoding all later frames. Recover at a documented sync marker without trusting random payload bytes.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Parser recovery · Protocols
Estimated field mix
- Embedded and edge50%
- Networking50%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional environmental-display devices send synthetic noncritical readings to a local gateway. Implement a byte-stream emulator; no physical device, radio, credentials or safety-critical control is involved.
Setup prerequisites
- Specify a small frame format with length sequence payload and checksum.
- Generate local byte streams with fragmentation corruption and reconnects.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Valid later frame can recover
- Recovery scans within a cap
- Rejected bytes never dispatch as readings
Implementation constraints
- Define marker escaping or ambiguity handling explicitly.
Verification to include
- Corrupt header before valid frame
- Embed marker-like bytes in payload
Deliverables
- Resynchronization algorithm and ambiguity cases
Rollout and recovery
Close the link when a safe boundary cannot be found.
Value of the work
For the engineer: Practice incremental parsing, fixed resource limits and protocol recovery.
For the team: Inspect whether a device adapter survives malformed input without corrupting accepted readings.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.