You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have to build a small prototype that implements BLE HID for a custom game-pad/joystick. After going through the module documentation I learned how to use the tools on how to configure the module. But I didn't understand how to interact with the HID profile using the BM71 Driver, until I noticed that the driver doesn't support other profiles besides the Transparent UART profile.
This Github read-me features list the following Bluetooth audio and BLE solutions but most of that seems missing at this time. The only mention of this is The BM71 also supports standard GATT predefined profiles, however the current BM71 driver does not provide access to these in ble_comm api help, which I didn't look at initially because I am not interested in the UART comms.
Is the support for the GATT predefined profiles planned, and if so is there a release date for that?
The text was updated successfully, but these errors were encountered:
I have to build a small prototype that implements BLE HID for a custom game-pad/joystick. After going through the module documentation I learned how to use the tools on how to configure the module. But I didn't understand how to interact with the HID profile using the BM71 Driver, until I noticed that the driver doesn't support other profiles besides the Transparent UART profile.
This Github read-me features list the following Bluetooth audio and BLE solutions but most of that seems missing at this time. The only mention of this is The BM71 also supports standard GATT predefined profiles, however the current BM71 driver does not provide access to these in ble_comm api help, which I didn't look at initially because I am not interested in the UART comms.
Is the support for the GATT predefined profiles planned, and if so is there a release date for that?
The text was updated successfully, but these errors were encountered: