STM32WB55 Timer Process IDs Do Not Automatically Defer Callbacks
Keep STM32WB55 timer-server expiry in its actual RTC interrupt context unless the application explicitly implements deferred dispatch.
-
-
STM32CubeMX Referenced Libraries Can Break an Otherwise Complete Handover
A project archive can contain every visible application file and still depend on a firmware repository outside the archive.
-
STM32WB55 BLE Command Exclusion Depends on Where a Task ID Is Declared
Place every BLE command-producing task inside the STM32WB55 sequencer exclusion mask before allowing cooperative waits to run other work.
-
Removing a CubeMX Peripheral Can Remove Its User Code Container
A CubeMX user-code section can survive regeneration while its surrounding peripheral remains enabled, then disappear when that peripheral’s generated file is removed.
-
STM32WB55 HCI Notifications Can Arrive Outside the IPCC Interrupt
Audit the three calling contexts of STM32WB55 HCI notifications and preserve one-event redispatch when adapting the transport to an RTOS.
-
STM32CubeIDE Headless Builds Need an Explicit Workspace and Artifact Contract
Define the workspace, configuration and output contract for STM32CubeIDE headless builds, then reject stale binaries and preserve build failures.
-
STM32WB55 Factory Addresses Follow the Selector Before Rewriting OTP
Trace UDN, OTP and compiled-address precedence before changing factory storage on an STM32WB55 product.
-
ESP8266 Legacy OTA Migration: Audit Both Layouts and the Copy-Back Mode
Review the unreleased legacy migration gate, different 1 MB and 2 MB example maps, retained parameters and 1 MB OTA1-to-OTA0 copy-back behavior.
-
ESP8266 UART Reception Has Two Queues, and Only One Contains the Bytes
Trace ESP8266 UART payload and event paths, distinguish stash recovery from FIFO loss, and prevent notification congestion from stranding unread bytes.
-
ESP8266 Wi-Fi Scans Need a Result-Ownership State Machine
Separate driver-owned scan results from bounded application snapshots, and close the cleanup lifecycle when refreshes, cancellation or retrieval fail.
