EEZ Studio Data Inputs: Detect a New Trigger Reusing Old Values
Why can a component run on a new sequence trigger with data left over from an earlier execution?
-
-
FreeRTOS on Raspberry Pi Pico: Check Target Definitions Before Editing FreeRTOSConfig.h
Trace Pico FreeRTOS target definitions, configuration include chains and per-object compiler inputs before changing kernel options.
-
FreeRTOS on Raspberry Pi Pico: Check the SDK Wait-and-Notify Contract
Review Pico SDK FreeRTOS wait-and-notify overrides, capability flags and multi-waiter progress before changing timeouts.
-
FreeRTOS on Raspberry Pi Pico: Audit Exception Handlers on the Correct Core
Diagnose RP2040 FreeRTOS exception ownership using dynamic-registration configuration, actual vectors and core identity.
-
Zephyr OS Coredumps: Separate Missing Memory from Broken Log Transport
Diagnose Zephyr coredump gaps by separating configured memory selection from logging-backend transport dependencies.
-
Zephyr OS Composite USB: Diagnose Endpoint Capability Before Counting Interfaces
Diagnose Zephyr composite USB activation using per-configuration endpoint capability and controller resource checks.
-
Zephyr OS USB CDC ACM: Keep Waiting for a Terminal Out of Product Startup
Separate Zephyr CDC ACM DTR waiting from headless product startup and explicit diagnostic session state.
-
Zephyr OS Input Events: Assemble Coordinates Without Treating the Queue as a Frame
Assemble Zephyr multi-axis input events with explicit producer boundaries and queue-loss recovery.
-
Zephyr OS RTC Alarms: Check Supported Fields Before Promising a Calendar Schedule
Check Zephyr RTC alarm field masks and calendar representation before implementing exact-date schedules.
-
Zephyr OS Native Simulation: Keep Software Evidence Separate from Board Timing Claims
Define what Zephyr native_sim can establish about software while keeping timing and board-specific claims separate.
