Skip to main content
YGail.2
Associate III
February 15, 2023
Solved

STM32WB getDescriptor UUID 2902 returns null

  • February 15, 2023
  • 2 replies
  • 1277 views

I successfully implemented a service with different characteristics. However on the android side when I call getDescriptor()

descriptor =characteristic.getDescriptor(UUID.fromString(CLIENT_CHARACTERISTIC_CONFIG));
CLIENT_CHARACTERISTIC_CONFIG = "00002902-0000-1000-8000-00805f9b34fb";

It always returns null. I need this to set the notify command to be true. In the ST BLE Toolbox, this works perfectly. So in principle, this should be able to be called. It seems that I missed a setting in CubeMX.

This topic has been closed for replies.
Best answer by YGail.2

I found probably why UUID 2902 is not callable. aci_gatt_add_char_desc() which in my opinion add the descriptor (UUID 2902) is never called. Hence I opened a new threat to this routine (https://community.st.com/s/question/0D53W000028ScADSA0/how-to-use-acigattaddchardesc-for-stm32wb-ble), as I could not find any documentation in the manual.

2 replies

Javier1
Principal
February 15, 2023

What languaje is this? is that code from your ST BLE mcu?

hit me up in https://www.linkedin.com/in/javiermuñoz/
YGail.2
YGail.2Author
Associate III
February 15, 2023

This is java on the android side. I could not call the given UUID from MCU. Hence I suppose that I missed something in CubeMx​

YGail.2
YGail.2AuthorBest answer
Associate III
February 16, 2023

I found probably why UUID 2902 is not callable. aci_gatt_add_char_desc() which in my opinion add the descriptor (UUID 2902) is never called. Hence I opened a new threat to this routine (https://community.st.com/s/question/0D53W000028ScADSA0/how-to-use-acigattaddchardesc-for-stm32wb-ble), as I could not find any documentation in the manual.