- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried to use bleprofile_sendReadByTypeReq to search the handle of Client Characteristic Configuration Descriptor, but cannot find it when the device works with an Android phone. (The same code works with an iPhone.) I use other app to look into the attribute list in the Android phone and the app can see the descriptor. What are the possible reasons that bleprofile_sendReadByTypeReq cannot find the descriptor (the codes is below)? The callback function shows the length of the return is zero.
UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION = 0x2902
bleprofile_sendReadByTypeReq(startHandle, endHandle, UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION);
The startHandle and endHandle are both correct.
I have no problem to use bleprofile_sendReadByTypeReq to find all the characteristic:
bleprofile_sendReadByTypeReq(startHandle, endHandle, UUID_ATTRIBUTE_CHARACTERISTIC);
Solved! Go to Solution.
- Labels:
-
ReadWrite Characteristics
-
SDK 2.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which exactly is central and peripheral ? Is the smartphone the client server and the Cypress chip the peripheral ? If this is the case which CLIENT_CHARACTERISTIC_CONFIGURATION are you trying to discover ?
After the above questions are made clear, which app did you use to test it out ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Smart phone is the peripheral and has attribute. Cypress chip is the master. We wrote the android app (peripheral) by ourselves and used the 3rd party app (BLE scanner) to simulation the connection. The 3rd party app can see the Descriptor.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem solved. The problem is on the Android side.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content