2025-06-08 5:24 AM
Hello,
I've been unable to get the ACI_GATT_SRV_READ_VSEVT_CODE case to trigger on the STM32WB05. Since this chip doesn't seem to support line for line debugging with an STLink to the Serial Wire interface due to Sequencer, I haven't been able to find a solution. The ACI_GATT_SRV_WRITE_VSEVT_CODE triggers fine and I've enabled GATT_NOTIFY_READ_REQ_AND_WAIT_FOR_APPL_RESP in CUBEMX. Does anyone know what the issue could be?
Kind Regards
Solved! Go to Solution.
2025-06-11 9:01 AM
If your characteristic has a buffer that is handled by the stack, the ACI_GATT_SRV_READ_VSEVT_CODE will not be generated.
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-06-09 3:27 AM
Hello @JSGraaf
This event is not generated if the read is requested on a characteristic or a descriptor that has an associated buffer handled by the stack (see ble_gatt_chr_def_t and ble_gatt_descr_def_t). So, ensure that the read is requested on a characteristic or a descriptor that does not have an associated buffer handled by the stack.
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-06-11 8:45 AM
Thank you for the response @STTwo-32!The characteristic has a buffer that is handled by the stack. Is there a way to still get a read event to fire or do I have to switch to non-buffered?
Kind Regards
2025-06-11 9:01 AM
If your characteristic has a buffer that is handled by the stack, the ACI_GATT_SRV_READ_VSEVT_CODE will not be generated.
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-06-11 12:42 PM
Thank you!