Compliance with Bluetooth Qualification - adopted services

[Mohammad Afaneh]

In the source files of standard/adopted services, there's a comment stating:

/* Attention!
 * To maintain compliance with Nordic Semiconductor ASA's Bluetooth profile
 * qualification listings, this section of source code must not be modified.
 */

If one wants to use one of these services and initialize it as a secondary service instead of a primary service, does that interfere with the qualification?

What's the best way to re-use one of these services as a secondary service? I assume modifying the original files for these services would not be a good idea(?)

[Mohammad Afaneh]

Hi Hung,

Thanks for the answer. The use case I'm running into is as follows: I have an nRF52 acting as a "gateway" running in Central Mode to connect and read data from other Peripherals, and then as a Peripheral to expose this data to the nRF Cloud via a PC (or another internet-connected device such as a Raspberry Pi 3).

The end nodes in the system each has a battery and exposes a Battery service, so my thinking is that instead of having multiple instances of the Battery service on the peripheral side for my "gateway" (one for each end node), I'd create one secondary Battery service and include it in multiple services.

Does this make sense? any suggestions?

Thanks!