Skip to main content
Hueli.1
Associate III
Nov 17, 2026 3:33 PM UTC
Question

STM32WB55: Command-event ordering and blocked waits in hci_send_req()

Hello,

We use an STM32WB55VGY with STM32CubeWB v1.17.2 middleware and are investigating blocking in the command-response path.

In hci_send_req(), each call to hci_cmd_resp_wait() is followed by draining HciCmdEventQueue. The function remains busy until a Command Status or Command Complete event reports Num_HCI_Command_Packets > 0.

Could you clarify:

  1. Can CPU2 generate multiple Command Status/Command Complete events during one hci_send_req() call—for example, a response with zero command credits followed by an opcode-zero credit update?
  2. Can an opcode-zero credit notification arrive before the matching command response? If so, what prevents hci_send_req() from returning before receiving that response?
  3. Are there known issues or recommended updates concerning blocked HCI/SHCI response waits in this middleware version?

Thank you.