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.
-
-
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.
-
STM32WB55 Factory Addresses Follow the Selector Before Rewriting OTP
Trace UDN, OTP and compiled-address precedence before changing factory storage on an STM32WB55 product.
-
Zephyr GATT UUID Notifications: A Search Start Does Not Limit the Match to One Service
Why can bt_gatt_notify_uuid select a characteristic in a later service when the caller passes an attribute from the intended service?
-
STM32WBA LE Audio Clocking: Keep the Codec Timer and Audio Peripheral on the Same PLL
Why can WBA LE Audio drift or miss presentation timing despite receiving valid ISO packets and completing LC3 processing?
-
STM32WBA LE Audio NVM Migration: Restore the RAM Image Before Stack Initialization
What must change when an audio application moves to the post-CubeWBA1.7.0 NVM integration contract?
-
STM32WBA BLE Libraries: Select a Compatible Feature Pair and Budget Application-Owned RAM
Can the chosen WBA55 host/link-layer variant support the required roles and still fit the product’s memory budget?
-
Zephyr OS Bluetooth Startup: Restore Settings After Enablement Before Advertising
Enforce Zephyr Bluetooth enable-then-settings ordering before advertising and identity creation.
-
EATT in BLE Products: When Parallel GATT Transactions Help and When They Do Not
EATT is useful when an independent GATT transaction is delayed behind another transaction on the same ATT bearer, and the host stacks can actually schedule the work on separate bearers. It is not an automatic throughput multiplier. Shared application locks, a serialized client wrapper or limited radio service can leave the original bottleneck unchanged. This…
-
BLE Periodic Advertising Synchronization: Acquisition Timeouts, Lost Sync and Recovery
Use separate controls for finding a periodic advertiser, detecting loss of an established synchronization and deciding that application data is stale. Cancel an expired acquisition through the stack’s documented lifecycle, wait for cancellation to finish, and only then start a replacement attempt. A parameter named synchronization timeout is not automatically an acquisition deadline. This guide…
