2025-01-24 07:44 AM
I am using the stm32wb5x_BLE_Stack_full_extended_fw.bin (1.18) on my STM32WB55. I would expect to get the HCI_COMMAND_COMPLETE_EVENT after calling hci_reset(), but I never get the event. I get the other HCI events such as HCI_DISCONNECTION_COMPLETE_EVENT, HCI_LE_META_EVT_CODE, HCI_VENDOR_SPECIFIC_DEBUG_EVT_CODE. Should I HCI_COMMAND_COMPLETE_EVENT after calling hci_reset()?
2025-01-24 09:07 AM
Hello @Dean_Sweeney
Could you please try to test this behavior using the P2P server and the stm32wb5x_BLE_Stack_full_extended_fw.bin file from thelast version of the STM32CubeWB (V1.21.1) on a Nucleo-WB55RG.
Best Regards.
STTwo-32
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-01-24 12:08 PM
Hi STTwo-32,
Thank you for the quick response. I tested the behavior using the P2P server and the stm32wb5x_BLE_Stack_full_extended_fw.bin file from the last version of the STM32CubeWB (V1.21.1) on a Nucleo-WB55RG.
Same result as before, I placed a breakpoint inside HCI_COMMAND_COMPLETE_EVT_CODE and it never gets called:
SVCCTL_UserEvtFlowStatus_t SVCCTL_App_Notification(void *p_Pckt)
{
...
switch (p_event_pckt->evt)
{
case HCI_COMMAND_COMPLETE_EVT_CODE:
{
hci_command_complete_evt_t *p_command_complete_event =
(hci_command_complete_evt_t*)p_event_pckt->data;
break;
}
...
}
}