Sending a notification causes STM32WB55 to go idle and becomes unresponsive to all further BLE requests

[mbedt]

Upon triggering a notify event calling the following function "Custom_STM_App_Update_Char()", the STM32 successfully sends data, which I receive on my iPhone using ST BLE Toolbox. However, after that, the STM32 becomes unresponsive to further BLE requests. I can see that the system hasn't crashed, as it is continusouly calling "UTIL_SEQ_Idle".

I am using a BLE application: server profile with a custom profile. I have already seen the other forum post titled "STM32WB55 Stops handling events after sending a notification" which sounds similar to this, but I am not deliberately pausing or stopping the sequencer at any point (as far as I'm aware).

Another unusual thing I've noticed, is that every other characteristic has been given a handle for the function "Custom_STM_Event_Handler(void *Event)" in "custom_stm.c", which I am able to use to call other functions to handle thos events, however, for my notify event, I can only see handles for NOTIFY_ENABLED_EVT / NOTIFY_DISABLED_EVT which aren't of much use to me.

[mbedt · Accepted solution]

I've found the issue, for those that might be interested. I had called "Custom_STM_App_Update_Char()" through a standard interrupt - the sequencer did not like this!

Having registered the task using UTIL_SEQ_RegTask() and executed it using UTIL_SEQ_SetTask(), all was right with the world. Hope this helps others.

Thanks