Forums - A new BLE service is not exposed in an existing profile

3 posts / 0 new
Last post
A new BLE service is not exposed in an existing profile
stodd
Join Date: 15 Mar 17
Posts: 5
Posted: Thu, 2017-03-23 08:14

A new BLE service does not show up in app_gatt_db.db_ file after a clean error free rebuild.

Adding a new service with CSR101x SDK-2.6.0.10 does not get exposed in gatt.  Infact the service_db.db file has no affect on the application, or the app_gatt_db.db_ file.

How would I add a service, custom or not, into an existing working profile and get the service exposed?   Simply adding the service_db.db file into the compiler's "GATT db files" folder, and the other supporting service files, is not sufficient to get the service exposed.

The simple example is to start off with the hr_monitor example application.  Then simply try and add a new service, say a "Blood Presure" service. Adding the files:  bp_service*.c/h,  bp_service_db.db, and  bp_service_uuid.h is not enough to completely add the service. 

What am I missing?

Thanks in advance.

  • Up0
  • Down0
stodd
Join Date: 15 Mar 17
Posts: 5
Posted: Thu, 2017-03-23 12:27

Solution found!

It turns out that you need to include the new "service_db.db" file into the "app_gatt_db.db" file.

The "app_gatt_db.db" file is nothing more than a list of included *.db files.  You must add your newly created service_db.db file into this file as an include.   Now the file "depend_Release_CSR101x_A05\app_gatt_db.db_" contains the newly added service, which can now be discovered.

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Mon, 2017-04-24 06:41

You need also to edit the last record "period" at the end of the db text ","

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.