STM32WB55 BLE suite

One engineering reference for the nine companion descriptors that observe the STM32WB5MM-DK peer-to-peer BLE demo.

Download the complete suite · Domain catalog

Scope and compatibility

These files target the STM32WB55-based STM32WB5MM-DK demo with its single-link BLE observation ABI 1, matching Debug ELF and current Trace Domains v1 host. They do not acquire private CPU2 state or sniff radio traffic. Generic connection/GATT/journal concepts can be adapted to another producer, but require the same verified observation contract. IPCC fields are STM32WB-specific and the P2P profile uses ST application symbols. No broader target compatibility is claimed.

Each file remains separate to bound its input count. Install the files you need; no runtime file has been merged. The P2P Send action additionally requires command mailbox ABI 1 and a live BKPT Debug host with typed-actions-v1. Desktop and history views are read-only.

Files and sections

Reading the suite

Read availability and Present flags first. The observer retains four services, eight characteristics, 16 payload bytes per characteristic and 16 significant journal records. Polls may span several firmware generations; retained data can outlive a connection. A local stack success or application acknowledgement does not prove phone receipt. Registry overflow and truncation describe observation limits. The bundled ST P2P app registers one service and two characteristics, so GATT pages for slots 2–7 normally show unused entries.

All values are separately sampled firmware observations; the requested poll rates below are not guaranteed achieved rates. Unavailable or stale inputs are not zero. DWARF paths require the exact ELF. Unknown value codes remain numeric. Counters can reset with the application, and raw journal timestamps/sequences can wrap. Inspect retained records after halting only when a consistent multi-field snapshot is needed; a halt also interrupts BLE application handling.

A value is a raw code, count, handle or register word unless its explanation gives a scale; a table has a unit column only where the descriptor declares units. A wrapping counter accounts for rollover at its integer width; a reset can look like a wrap, and several wraps between two samples cannot be recovered. Only BLE overview declares automatic findings; the absence of a finding does not establish healthy operation.

BLE overview

com.bkpt.ble.overview · version 0.1.0 · API 1. Download · GitHub

Connection cards establish whether a live link exists. Command/error rows retain outcomes, while service tables describe only intercepted successful registrations, not CPU2's complete database.

61 inputs, 0 derived channels; requested polling 2 Hz per input.

BLE overview · Cards and tables

BLE overview · Connection

Single-link peripheral observation ABI 1. Connection intervals use 1.25 ms units; supervision timeout uses 10 ms units. Values persist until superseded; disconnected timing/PHY values describe the previous link.

BLE overview · Command outcomes and observation health

Firmware-retained application observation. Polls may span updates; halt for a consistent snapshot. Not private CPU2 state or proof of radio delivery.

BLE overview · Service slots 0–3

Present=0 means unused. These are successful application add-service calls, not an enumeration of CPU2's entire database; GAP/GATT built-ins are not intercepted. UUID words 3,2,1,0 form the 128-bit UUID in hexadecimal; type 1 uses word 0's low 16 bits. All 4 slots have these fields; N is the slot number, 0 to 3.

BLE overview · Sampled inputs

Every input is read from firmware at the member path its channel name spells out: ble.* from ble_observer (u32). For example, ble.services.N.uuid.0 reads ble_observer.services[N].uuid[0].

wrapping counters: ble.commands, ble.command_errors, ble.events, ble.malformed_events, ble.registry_overflows, ble.value_truncations.

BLE overview · Findings

BLE overview · A command returned non-success

warning · command-errors. ble.command_errors increases between valid samples.

The retained command error count increased. Inspect the retained opcode/status and journal; an accepted GATT update is not remote delivery.

Evidence: ble.command_errors.

BLE overview · Observation registry capacity exceeded

warning · registry-full. ble.registry_overflows increases between valid samples.

The firmware omitted an object because its fixed registry is full. Increase adapter capacity and generate matching bounded descriptor pages.

Evidence: ble.registry_overflows.

BLE overview · Command response still pending

warning · command-pending. ble.command_pending ≥ 1 for 2000 ms of observations.

A command has remained pending across at least two seconds of running samples. Inspect shared transport flags and application execution. Halting pauses observations.

Evidence: ble.command_pending.

BLE GATT slots 0–7

4 files that differ only in the slots they cover, each version 0.1.0 · API 1.

Each GATT file covers two physical characteristic slots. Read Present and Value source before interpreting payload words. Slots 0–1 serve the supplied P2P application; later slots require additional registrations.

Each file: 48 inputs, 10 derived channels; requested polling 1 Hz per input.

BLE GATT slots 0–7 · Cards and tables

BLE GATT slots 0–7 · Characteristic slots 0–7

Present=0 means unused. Handles, UUIDs and properties come from successful registration. Value origin=0 means no observed value. Payload is the retained 16-byte prefix in four little-endian words. Values and counters are application observations; update success does not prove client receipt. CCCD is for the single current connection. All 8 slots have these fields; N is the slot number, 0 to 7.

BLE GATT slots 0–7 · Sampled inputs

Every input is read from firmware at the member path its channel name spells out: ble.* from ble_observer (u32). For example, ble.characteristics.N.uuid.0 reads ble_observer.characteristics[N].uuid[0].

wrapping counters: ble.characteristics.N.writes, ble.characteristics.N.updates, ble.characteristics.N.update_ok.

Derived from ble.characteristics.N.properties: ble.characteristics.N.property.1 is bit 1, ble.characteristics.N.property.2 is bit 2, ble.characteristics.N.property.3 is bit 3, ble.characteristics.N.property.4 is bit 4, ble.characteristics.N.property.5 is bit 5.

BLE ST peer-to-peer profile

com.bkpt.ble.profile.st-p2p · version 0.2.0 · API 1. Download · GitHub

The P2P service UUID is 0000fe40-cc7a-482a-984a-7f2ed5b3e58f, LED FE41 and button FE42 in their full ST UUIDs. Values contain device selection (1 here) then state. Little-endian word 257 means bytes 01 01, word 1 means 01 00. The LED characteristic does not notify, so a client may need a fresh read. Missing profile symbols affect this profile without making generic GATT observations valid or invalid.

8 inputs, 0 derived channels; requested polling 2 Hz per input.

BLE ST peer-to-peer profile · Cards and tables

BLE ST peer-to-peer profile · LED and button

Optional profile decoder for ST's P2P application context. Missing P2P symbols make this profile unavailable while the generic GATT domains still work. LED is applied application state; button is local state even when notifications are disabled.

BLE ST peer-to-peer profile · Application commands

Send calls the application's LED handler and updates the readable P2P LED characteristic. An acknowledgement is a local application result; it does not prove phone receipt.

BLE ST peer-to-peer profile · Sampled inputs

Every input is read from firmware at the member path its channel name spells out: p2p.* from P2P_Server_App_Context (u8), ble.* from ble_observer (u32), command.* from domain_command (u32). For example, p2p.LedControl.Led1 reads P2P_Server_App_Context.LedControl.Led1.

wrapping counters: ble.button_presses, ble.notifications_skipped.

BLE ST peer-to-peer profile · Actions

The Blue LED draft offers Off (0) or On (1), encoded as one u8. Only explicit Send publishes operation 1 to domain_command; selecting a draft does not write. Firmware validates the mailbox and operation, updates the actual GATT value and applies the LED state, then publishes its result. The host waits up to 3000 ms for matching completion. Rejection/unknown completion is not success, and the host does not automatically retry. Acknowledgement proves local handling, not physical LED verification or phone receipt.

BLE ST peer-to-peer profile · Blue LED

set_led; completion: application.

{
  "input": {
    "ty": "u8",
    "choices": [
      {
        "value": "0",
        "label": "Off"
      },
      {
        "value": "1",
        "label": "On"
      }
    ]
  },
  "target": {
    "kind": "mailbox",
    "symbol": "domain_command",
    "operation": 1,
    "timeout_ms": 3000
  }
}

BLE STM32WB shared transport

com.bkpt.ble.stm32wb-transport · version 0.1.0 · API 1. Download · GitHub

Three application-copied IPCC registers help correlate a pending command with inter-core transport flags. They measure neither queue depth nor RF activity; the descriptor provides raw words without per-bit decoding.

3 inputs, 0 derived channels; requested polling 2 Hz per input.

BLE STM32WB shared transport · Cards and tables

BLE STM32WB shared transport · IPCC status samples

Application-copied read-only IPCC status and mask registers. Transient flags between samples may be missed; these are not queue lengths. CPU2 private radio/GATT state is inaccessible.

BLE STM32WB shared transport · Sampled inputs

Every input is read from firmware at the member path its channel name spells out: ble.* from ble_observer (u32). For example, ble.ipcc_c1_status reads ble_observer.ipcc_c1_status.

BLE activity slots 0–15

2 files that differ only in the slots they cover, each version 0.1.0 · API 1.

Each journal file exposes eight physical slots of the shared 16-record journal. The journal is a retained window, not a complete event log. Order by sequence; unused/in-progress sequence zero is not an event.

Each file: 48 inputs, 0 derived channels; requested polling 1 Hz per input.

BLE activity slots 0–15 · Cards and tables

BLE activity slots 0–15 · Journal slots 0–15

Physical ring slots, not sorted rows. Sort mentally by sequence; sequence 0 is unused/in-progress. Last 16 significant observations are retained. Radio-activity callbacks only increment the event counter. Halt for a consistent journal; polling does not capture every entry. All 16 slots have these fields; N is the slot number, 0 to 15.

BLE activity slots 0–15 · Sampled inputs

Every input is read from firmware at the member path its channel name spells out: ble.* from ble_observer (u32). For example, ble.journal.N.sequence reads ble_observer.journal[N].sequence.

Value lookups

Shared by the linked fields throughout the suite. Unlisted codes remain numeric and must not be treated as success.

Last command status values

Source verification and contributions

Verified against observation ABI 1 in ble_observer.h, API wrappers/event decoding/poll copies in ble_observer.c, version/advertising producers in app_entry.c and app_ble.c, the pinned ST BLE status/opcode headers, and descriptor-driven card/enum rendering. Action semantics were checked in domain_command.c and P2PS_APP_Command.

Contribute a correction or an adapted domain. The nine individual downloads are exact copies of the canonical definitions; the ZIP contains those same files.