How to merge custom Nimble peripheral with protocomm/provisioning?
Posted: Sun Mar 14, 2021 5:38 am
Hi,
I implemented a Nimble peripheral, which exposes several gatt attributes to Read, Write and Notify.
Now I want to add WiFi provisioning.
I like how wifi_prov_mgr example works. Unfortunately, wifi_prov_mgr uses protocomm_nimble.c, which creates its own BLE server, which mostly duplicates my own.
I see that protocomm API provides API for custom data: wifi_prov_mgr_endpoint_create / wifi_prov_mgr_endpoint_register, but this is not enough: I need to have Notify attributes and also some custom pairing mechanism.
So, the question is what is the simplest way to merge my custom Nimble server with protocomm/provisioning?
Can I create few extra attributes in my gatt service and route them to protocomm?
Or somehow inject my custom gatt attributes to protocomm_nimble.c?
What us the simpler and cleaner way?
Thank you
I implemented a Nimble peripheral, which exposes several gatt attributes to Read, Write and Notify.
Now I want to add WiFi provisioning.
I like how wifi_prov_mgr example works. Unfortunately, wifi_prov_mgr uses protocomm_nimble.c, which creates its own BLE server, which mostly duplicates my own.
I see that protocomm API provides API for custom data: wifi_prov_mgr_endpoint_create / wifi_prov_mgr_endpoint_register, but this is not enough: I need to have Notify attributes and also some custom pairing mechanism.
So, the question is what is the simplest way to merge my custom Nimble server with protocomm/provisioning?
Can I create few extra attributes in my gatt service and route them to protocomm?
Or somehow inject my custom gatt attributes to protocomm_nimble.c?
What us the simpler and cleaner way?
Thank you