Zephyr OS Modules: Trace Missing Kconfig and CMake Integration from module.yml
Trace module recognition, Kconfig inclusion and CMake source inclusion before diagnosing runtime behavior.
-
-
Zephyr OS West Manifests: Freeze Dependencies Without Mistaking Them for Workspace State
Compare resolved manifest dependencies with actual checkout commits and local changes before claiming source reproducibility.
-
Zephyr OS Sysbuild: Keep Bootloader Configuration Out of the Application Namespace
Verify sysbuild, main-application and additional-domain settings in the correct effective configuration.
-
Zephyr OS Board Revisions: Prevent a Default Revision from Selecting the Wrong Hardware
Audit defaults, exact matching and fallback revision selection before associating an image with physical hardware.
-
Zephyr OS Devicetree Bindings: Diagnose a Property That Exists but Has No Generated API
Diagnose missing generated devicetree information through binding selection, property schema and the consumer access pattern.
-
Zephyr OS Overlay Selection: Prove Which Hardware Description Reached the Build
Diagnose an ineffective overlay using resolved inputs, cache evidence, override ordering and the generated DTS.
-
Zephyr OS Device References: Separate Missing Driver Objects from Failed Initialization
Separate missing driver objects at link time from unready devices after startup, then verify the required function.
-
TinyML Numeric Regression: Match CMSIS-NN Rounding Options Before Comparing Outputs
Separate CMSIS-NN numerical configuration from genuine regressions by selecting the correct reference, matching rounding options and reproducing the first divergent operation.
-
Zephyr OS LED Colors: Build the Array from the Controller Mapping Instead of Assuming RGB
Map semantic colors before building the LED array. Versioned implementation and integration review.
-
Zephyr zbus Listener Reentry: Prevent a Publish Path from Locking Its Own Channel
A zbus listener must not wait for a channel whose release depends on that listener returning. In the same-channel case, a nested locking read or publication can wait on the semaphore already held by its outer publication. Across channels, listener chains can form the same dependency cycle. Draw the nested call graph before changing timeout…
