Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I have also been trying to create a ble app using the BCM4343W and have found it very frustrating without any doc. I started with the "hello_sensor" app with the intent of figuring out the format. I can see that the creation of a GATT database defines the services and the structure of this database is pretty straighforward. I call wiced_bt_gatt_db_init and it returns a 0 indicating success in setting the database but the services available always are the same services no matter what I put in the database structure.
I ran the app several times under the debugger to understand its flow and verify my thoughts on its operation. When I stared modifying, all I have done is comment out these lines in hello_sensor_gatt_database :
in hello_sensor_gatt_server_read_request_handler. This should have removed the battery state service but it does not. If I trace through, I can see the database no longer has it just before the call to wiced_bt_gatt_db_init. If I select that service and try to access it characteristics, it fails so its like it is partially removed but I cannot seem to remove it from being broadcast as an available service. I have tried other values within the gatt database as well with similar results. The services are always the same services.
What is going on here? It seems as if the gatt database is being stored someplace in NV storage.