TinyML Arduino Serial Tests: Separate Data Transfer Completion from Inference Success
Debug archived Arduino test-over-serial by distinguishing decoded byte acknowledgments, typed callback progress and the host’s final inference matcher/assertion.
-
-
TinyML Arduino Audio Capture: Detect When Inference Falls Behind the Sample History
Expose stale audio that modulo indexing hides in the archived Arduino speech provider, then propagate retention failures through the feature consumer.
-
FreeRTOS on Raspberry Pi Pico: Assign TinyUSB Servicing Before Relying on USB Stdio
Trace Pico FreeRTOS USB stdio initialization and TinyUSB servicing ownership before interpreting missing logs as scheduler failure.
-
FreeRTOS on Raspberry Pi Pico: Give Core One a Single Startup Owner
Audit RP2040 FreeRTOS core-one reset, launch, FIFO and spinlock ownership before merging multicore examples.
-
Zephyr OS RTIO Buffers: Release the Completion Slot and Payload Separately
Trace RTIO completion-slot and pool-backed payload ownership independently to prevent exhaustion and premature reuse.
-
Zephyr OS Counter Alarms: Handle a Deadline That Passes While You Arm It
Design Zephyr counter absolute-alarm late-setting policy with guard periods, wraparound and coordinated callback handling.
-
SquareLine Studio Component Transfer: Check Referenced Assets After Copying a Component to Another Project
How can copying a reusable component into a new project expose missing images, fonts or target references before integration?
-
SquareLine Studio Don’t Export: Test the Generated Dependency Boundary, Not Just the Canvas
How can a design-only widget be excluded without leaving event targets, aliases or unnecessary asset exports in the product?
-
EEZ Studio Image Export: Trace C Descriptors and Binary Files as Different Deployment Contracts
How can an EEZ Studio image failure be localized to C-source linkage, binary asset deployment or the emitted pixel representation?
-
EEZ Studio Native Variables: Audit Renames and Type Changes at the Adapter Boundary
How can EEZ Studio variable renames and type edits be detected before an obsolete getter silently remains in the firmware?
