XDK API  3.6.0
Documentation
Macros
BleConfig.h File Reference
#include "BLECustomConfig.h"
+ Include dependency graph for BleConfig.h:
+ This graph shows which files directly or indirectly include this file:

Macros

#define BLE_DIRECT_CONNECTION_SUPPORT   0
 
#define BLE_ENABLE_HCI_LOCK   0
 
#define BLE_FUNC_PTR   static
 
#define BLE_NUM_MAX_CONNECTION   1
 
#define BLE_SM_DOUBLE_ROLE_BONDING   0
 
#define BLE_SM_DYNAMIC_ENCRYPTION_KEY_SIZE   0
 
#define BLE_SM_OUTOFBAND_PAIRING   0
 
#define BLE_STACK_SKIP_MUTEX_FUNCTIONS   0
 
#define BLE_USE_INTERNAL_MEMORY_FUNCTIONS   1
 
#define BLE_USE_MICROSECONDS_TIMER   0
 
#define BLECONTROLLER_DEFAULT   0
 
#define BLECONTROLLER_EM   1
 
#define BLEL2CAP_MTU   23
 
#define BLEPROCESSOR_BIGENDIAN   2
 
#define BLEPROCESSOR_LITTLEENDIAN   1
 
#define BLEPROCESSOR_TYPE   BLEPROCESSOR_UNKNOWNTYPE
 
#define BLEPROCESSOR_UNKNOWNTYPE   0
 
#define BLESCTK_USE_DEPRECATED_API   1
 
#define BLESPECIFICATION_4_0   (0x06u)
 
#define BLESPECIFICATION_4_1   (0x07u)
 
#define BLESTCK_VERSION   0x01010100
 
#define BLETRANSPORT_CUSTOM   1
 
#define BLETRANSPORT_UART   0
 
#define BLETRANSPORT_USED   BLETRANSPORT_UART
 
#define L2CAP_DEBUG_TRACES   0
 
#define NUM_COMMAND_PACKETS   2
 
#define NUM_EVENT_PACKETS   4
 
#define NUM_RX_DATA_PACKETS   4
 
#define NUM_TX_DATA_PACKETS   4
 
#define SM_IO_DISPLAY_ONLY   0
 
#define SM_IO_DISPLAY_YESNO   1
 
#define SM_IO_KEYBOARD_DYSPLAY   4
 
#define SM_IO_KEYBOARD_ONLY   2
 
#define SM_IO_NOINPUTNOOUTPUT   3
 

Macro Definition Documentation

#define BLE_DIRECT_CONNECTION_SUPPORT   0

BLE_DIRECT_CONNECTION_SUPPORT Defines if the direct connections (either duty cycle) are supported in the HOST stack.

This configuration is ignored when BLE_CONNECTION_SUPPORT is disabled. It allows an advertiser to use directed advertising type.

Enabling direct connections increase final ROM and RAM memory footprint.

The default value is 0 (DISABLED)

#define BLE_ENABLE_HCI_LOCK   0

BLEL2CAP_CONNECTION_ORIENTED_CHANNELS Define if the LE L2CAP CONNECTION ORIENTED CHANNELS are supported by the stack. This is a Bluetooth 4.1 feature allowing profiles to be exchange data directly over L2CAP protocol. This configuration is ignored when BLE_CONNECTION_SUPPORT is disabled.

The default value is to enable this feature if the Bluetooth specification compliance configuration ( BLESPECIFICATION_COMPLIANCE ) is configured for Bluetooth specification 4.1 and disable the feature if the Bluetooth specification compliance configuration ( BLESPECIFICATION_COMPLIANCE ) is configured for Bluetooth specification 4.0 BLE_ENABLE_VENDOR_SPECIFIC Define if the HCI vendor specific command handling is enabled (BLE_ENABLE_VENDOR_SPECIFIC set to 1) or disabled (BLE_ENABLE_VENDOR_SPECIFIC set to 0).

Supporting this allows the application to use the BLEHCI_SendVendorSpecificCommand interface.

As well the application can receive the vendor specific Event (event code 0xff) through the BLEEVENT_VENDOR_SPECIFC_EVENT_RECEIVED in the application callback. If the BLE_ENABLE_VENDOR_SPECIFIC is disabled, the stack silently discard any vendor specific event.

Enabling vendor specific command support increase final ROM memory footprint.

The default value is DISABLED (0) BLE_ENABLE_HCI_LOCK HCI packets can be locked (BLE_ENABLE_HCI_LOCK set to 1) or not (BLE_ENABLE_HCI_LOCK set to 0).

The default value is DISABLED (0)

#define BLE_FUNC_PTR   static

UNUSED_PARAMETER A way to deal with some function not used parameter to avoid compiler warning, it is most of the time defined as (P=P) or ((void)(P)) (which can also trigs some warning CONST_DECL The keyword to define where to place the "constant" variables declaration the default behaviour is to place them using "const" keyword. BLE_FUNC_PTR The stack registers and uses internally function pointer to be called by other internal layer, for example internal timers, Core stack callback or Attribute Protocol callback may be registered internally by the stack and Profiles. These functions (passed as pointer) are defined local in a layer and may be called by another layer. So by default they are prototyped as "static" but some compiler does not accept to call function pointer that are prototyped as "static".

#define BLE_NUM_MAX_CONNECTION   1

BLE_ROLE_ADVERTISER defines if the ADVERTISER role is enabled (1) or disabled (0) this role increases ROM and RAM size of the BLE application By default this option is enabled (1) BLE_ROLE_SCANNER defines if the SCANNER role is enabled (1) or disabled (0) this role increases ROM and RAM size of the BLE application By default this option is DISABLED (0) BLE_ADVERTSING_TX_POWER_SUPPORT BLE_ADVERTSING_TX_POWER_SUPPORT define if the Advertising TX power level should be retrieved by the stack. It enables some GAP API to fill Advertisement data. And stack APIs that retrieve the advertisement TX Power. Defining the BLE_ADVERTSING_TX_POWER_SUPPORT to 1 (one) increase consequently the final ROM size. By default, this option is enabled (1) BLE_ADVERTISING_DIRECTED_LOW_DUTY_CYCLE_SUPPORT BLE_ADVERTISING_DIRECTED_LOW_DUTY_CYCLE_SUPPORT define if the local device is able to set the advertising packet type to ADV_DIRECT_IND, Low duty Cycle. This feature is a Bluetooth 4.1 Specification feature. IT is not allowed to enable this feature when the local device is claiming Bluetooth 4.0 compliance.

It enables as well some GAP API to use direct Advertising with Low duty Cycle support.

Defining the BLE_ADVERTISING_DIRECTED_LOW_DUTY_CYCLE_SUPPORT to 1 (one) increase consequently the final ROM size. This configuration is ignored when BLE_CONNECTION_SUPPORT is disabled. This configuration is ignored when BLE_ROLE_ADVERTISER is disabled. This configuration is ignored when BLE_DIRECT_CONNECTION_SUPPORT is disabled.

The default value is to enable this feature if the Bluetooth specification compliance configuration ( BLESPECIFICATION_COMPLIANCE ) is configured for Bluetooth specification 4.1 and disable the feature if the Bluetooth specification compliance configuration ( BLESPECIFICATION_COMPLIANCE ) is configured for Bluetooth specification 4.0 BLE_CONNECTION_SUPPORT allows the local BLE device to support the Link layer connection handling. It enables the Interface to create an outgoing link layer connection, And mechanism to handle incoming connection. Moreover, it enables the L2CAP layer needed to handle data over the link layer connection.

Note that in order to create an outgoing connection you should be in the scanning mode so the BLE_ROLE_SCANNER should also be enabled.

Be careful, defining the BLE_CONNECTION_SUPPORT to 1 (one) increase consequently the final ROM size.

Disabling this value lets you act as:

  • A BROADCASTER. A broadcaster device is a BLE device that operates only as an advertiser and uses only non-connectable advertising events to broadcast data. A BLE device that is a broadcaster only may be implemented without a receiver. To be a broadcaster BLE_ROLE_ADVERTISER shall be set to 1.
  • An OBSERVER. An observer device is a BLE device that operates only as a scanner using passive scanning to acquire data from broadcaster devices. A BLE device that is an observer only may be implemented without a transmitter. To be an observer BLE_ROLE_SCANNER shall be set to 1.

Enabling this value lets you act as:

  • A PERIPHERAL : A peripheral device is a BLE device that is capable of operating as a slave in a link layer connection. Consequently, such a device shall be able to operate as an advertiser using connectable advertising events to invite establishment of a link layer connection. To be a peripheral BLE_ROLE_ADVERTISER shall be set to 1.
  • A CENTRAL : A central device is a BLE device that is capable of operating as a master in a link layer connection. Consequently, such a device shall be able to operate as a scanner and initiator to establish a link layer connection. To be a central BLE_ROLE_SCANNER shall be set to 1.

See below for a review of all roles according configuration definition:

                     BLE_CONNECTION_SUPPORT    BLE_CONNECTION_SUPPORT
                  |           = 0           |           =1            |

----------------——+-------------------——+-------------------——+ BLE_ROLE_ADVERTISER=0 | NOT POSSIBLE | NOT POSSIBLE | BLE_ROLE_SCANNER=0 | | | ----------------——+-------------------——+-------------------——+ BLE_ROLE_ADVERTISER=1 | BROADCASTER ONLY | BROADCASTER AND | BLE_ROLE_SCANNER=0 | | PERIPHERAL | ----------------——+-------------------——+-------------------——+ BLE_ROLE_ADVERTISER=0 | OBSERVER ONLY | OBSERVER AND | BLE_ROLE_SCANNER=1 | | CENTRAL | ----------------——+-------------------——+-------------------——+ BLE_ROLE_ADVERTISER=1 | OBSERVER OR | ALL FOUR ROLES | BLE_ROLE_SCANNER=1 | BROADCASTER | | ----------------——+-------------------——+-------------------——+

the default value for BLE_CONNECTION_SUPPORT is ENABLED (1) BLE_NUM_MAX_CONNECTION Defines the maximum simultaneous link layer connections that can exist at a given time. Increasing this value impacts the final RAM and ROM size. It cannot be equal to zero if BLE_CONNECTION_SUPPORT is ENABLED

the default value is 1

#define BLE_SM_DOUBLE_ROLE_BONDING   0

SM_IO_CAPABILITIES Define the STATIC local System Input/Output capabilities used in Security manager for the Pairing process. When BLE_SM_DYNAMIC_IO_CAPABILITIES is DISABLED then SM_IO_CAPABILITIES is the local device IO capability for all the device lifeTime. When BLE_SM_DYNAMIC_IO_CAPABILITIES is ENABLED then SM_IO_CAPABILITIES is the default local device IO capability before any change thanks to BLESMP_SetIOCapability() .

The default configuration is NO INPUT / NO OUTPUT BLE_SM_DOUBLE_ROLE_BONDING This option defines if the local device request or distribute also the master encryption keys in order to be also bonded when the role (peripheral - central) change between to bonded devices.

If enabled, (set to 1) : If the local device is CENTRAL (MASTER), during bonding procedure it will also try to distribute this LTK, DIV and RAND in order to not repeat the BONDING if the local device is PERIPHERAL (SLAVE) in future connections with the same device. Also, if the device is PERIPHERAL (SLAVE), during bonding procedure, it will try to request the LTK, DIV and RAND from CENTRAL (MASTER).

Enabling this option increase the ROM and over the AIR traffic during Pairing procedure. If a device have mainly a static ROLE (either CENTRAL or PERIPHERAL), this option should be left DISABLED in order to save POWER. The default configuration is DISABLED ( set to 0)

#define BLE_SM_DYNAMIC_ENCRYPTION_KEY_SIZE   0

BLE_SM_DYNAMIC_IO_CAPABILITIES Define if the device is able to change its security IO capability during its lifetime. If ENABLED (set to 1) then the device IO capability is set by the application during runtime thanks to BLESMP_SetIOCapability(). If DISABLED ( set to 0) then the IO capability is STATIC and set during compilation thanks to SM_IO_CAPABILITIES definition.

The default configuration is DISBALED (0) BLE_SM_DYNAMIC_ENCRYPTION_KEY_SIZE Define if the device is able to change the encryption Key Size during its lifetime. If ENABLED (set to 1) then the device supported maximum encryption key size is set by the application during runtime between 7 bytes and 16 bytes thanks to the BLESMP_SetMaximumEncrytionKeySize() API. Note that the default value at start-up is 16 bytes If DISABLED ( set to 0) then the local device maximum encryption key size is 16 bytes. Note: using a Key size of 16 bytes instead or 7 bytes does not add over the air traffic or Baseband additional calculation, and it is better in term of security. It is why a value of 16 bytes is just fine and an application should not change this value and let this option to disabled. However some stack qualification test cases requires modifying this setting

The default configuration is DISBALED (0)

#define BLE_SM_OUTOFBAND_PAIRING   0

BLE_SM_OUTOFBAND_PAIRING This option defines if the local device enable out of band mechanism in order to exchange pairing information. If ENABLED (set to 1), then the SMP API BLESMP_SetOobData and BLESMP_ClearOobData are enabled in order to manage Out of band data used in the pairing procedure.

The default configuration is DISABLED ( set to 0)

#define BLE_STACK_SKIP_MUTEX_FUNCTIONS   0

BLE_STACK_SKIP_MUTEX_FUNCTIONS allows the stack code to not calling mutex function defined in "bleSystem.h". In case on monotasking systems, these functions may be useless and skipping them save code memory footprint.

Default value is 0 (means that the implementer must defined them, even empty).

#define BLE_USE_INTERNAL_MEMORY_FUNCTIONS   1

BLE_PROTECT_ISR_FUNCTION_CALL allows the stack code to protect the stack functions that are called both from the transport layer within Interrupt service routine (ISR) and from the Application Layer Interface (API). If transport layer (for example) BLETRANSPORT_UartDataReceived is handled upon ISR This option should be overridden to 1 to avoid reentrancy problem. Default value is 0. BLE_USE_RESTRICTED_LOCAL_MEMORY allows the stack code to implement mechanism for restricted stack memory size environment. if this option is overridden to 1, the stack code will use some local variables used in the stack as global. Default value is 0. BLETYPES_ALREADY_DEFINED allows the stack code to define in "bletypes.h" the standard U8, U16 and U32 types. If the system already define these types or if these type should be different that is defined in bletypes.h, set BLETYPES_ALREADY_DEFINED to one and if needed redefine them in "BLECustomConfig.h" Default value is 0 (means that the stack use its own defined type). BLE_USE_INTERNAL_MEMORY_FUNCTIONS allows the stack code to use its internal memory functions definition for SYSTEM_Mem*** (see declaration in "bleSystem.h") if the system already define these functions , set BLE_USE_INTERNAL_MEMORY_FUNCTIONS to 0 in "BLECustomConfig.h" and implement these functions in the application code, it may save ROM memory. Default value is 1 (means that the stack use its own defined functions).

#define BLE_USE_MICROSECONDS_TIMER   0

BLE_USE_MICROSECONDS_TIMER allows the stack code to use the stack timer in microseconds instead of milliseconds. It may be useful in case of only high precision timers are available or if the User application need microsecond timers through BLEMGMT_AddUserTimerEvent(..). If enabled SYSTEM_CreateTimer() takes microseconds instead of milliseconds in parameter. Default value is 0 (means that the stack does not use microseconds timers but milliseconds timers ).

#define BLECONTROLLER_DEFAULT   0
#define BLECONTROLLER_EM   1
#define BLEL2CAP_MTU   23

BLEL2CAP_MTU Define if the maximum transmission unit for the PDU in a BLEL2CAP packet. Increasing this value impacts the final RAM size.

the default value is 23

#define BLEPROCESSOR_BIGENDIAN   2
#define BLEPROCESSOR_LITTLEENDIAN   1
#define BLEPROCESSOR_TYPE   BLEPROCESSOR_UNKNOWNTYPE

BLEPROCESSOR_TYPE allows the user to choose which kind of host is used

This enables internal specific code and optimisation for a given microprocessor type Override this definition in the CustomConfig file to change the value. The different possible values are BLEPROCESSOR_BIGENDIAN, BLEPROCESSOR_LITTLEENDIAN or BLEPROCESSOR_UNKNOWNTYPE Default value is BLEPROCESSOR_UNKNOWNTYPE.

#define BLEPROCESSOR_UNKNOWNTYPE   0

BLECONTROLLER_USED allows the user to choose the Bluetooth Low energy controller used by the BLE stack.

This enables specific code and optimisation for given controller Override this definition in the CustomConfig file to change the value. The different possible values are BLECONTROLLER_EM or BLECONTROLLER_DEFAULT. Default value is BLECONTROLLER_DEFAULT. BLECONTROLLER_NEED_SPECIFIC_INIT give access to interface used by the HCI layer to call specific radio initialisation

The BLERADIO_Init() function is called during the HCI LAYER initialisation.

  • The BLERADIO_HciEventHandler() routes the HCI events during radio initialisation.
  • The BLEHCI_RadioInitialized() shall be called after specific radio initialisation code

Note that the RADIO initialisation shall send the HCC_RESET command (0x0C03), because the stack initialisation will not send it if BLECONTROLLER_NEED_SPECIFIC_INIT is enabled (1).

#define BLESCTK_USE_DEPRECATED_API   1

BLE_SM_SLAVE_RESOLVE_MASTER_RANDOM_ADDRESS This option defines enable the ability for the local device, acting a SLAVE, to resolve remote random address. It may be useful for devices that need to set-up bonding with the device using RANDOM RESOLVABLE address type. When enabling this feature the security layer needs to access to additional persistent memory storage features. This option is ignored if SLAVE role is not available : i.e. if (BLE_CONNECTION_SUPPORT == 0) or (BLE_ROLE_ADVERTISER == 0)

See also
SYSTEM_UpdateDeviceAddressAtIndexInPersistentMemory
SYSTEM_GetDeviceAddressAtIndexInPersistentMemory
SYSTEM_GetNumberOfDevicesInPersistentMemory

The default configuration is DISABLED ( set to 0) BLE_RANDOM_ADDRESSING_SUPPORT Define if the random addressing support is enabled (BLE_RANDOM_ADDRESSING_SUPPORT set to 1) or disabled (BLE_RANDOM_ADDRESSING_SUPPORT set to 0).

Supporting this allow to use the random Addressing API and allow the Application to generate a random address to use in advertisement, scanning and connection.

If you do not use random addressing, the application always uses the local device public hardware address.

Enabling random addressing support increase final ROM and RAM memory footprint.

The default value is DISABLED (0) BLE_PARMS_CHECK allows the user to check at runtime if the parameter of the interfaces are well formatted and / or are in the allowed values range. When the BLE_PARMS_CHECK is defined to zero, the stack does not check the parameters values and assume that they are always corrects. Be careful defining the BLE_PARMS_CHECK to 1 (one) increase consequently the final ROM size.

the default value is DISABLED (0) BLEERROR_HANDLER allows the stack to control the errors by calling the BLEERROR_CatchException to prevent crashing

When the BLEERROR_HANDLER is ENABLED (0), the Stack includes code that check pointer or data integrity. for example bad transport character received or null pointer resulting from bad configuration. So the application will be notified when the stack has reach an error Be careful defining the BLEERROR_HANDLER to 1 (one) increase consequently the final ROM size. the default value is DISABLED (0) BLESCTK_USE_DEPRECATED_API allows the application to control if it uses deprecated API. It enables (set to 1) or disables (set to 0) the API / Types / or definitions that are deprecated and that will be removed in next ALPW-BLESDK versions. Then by disabling this configuration (set to 0) an application can check if it is compliant with next release.

The default value is ENABLED (1), means deprecated API are still available in the code

#define BLESPECIFICATION_4_0   (0x06u)
#define BLESPECIFICATION_4_1   (0x07u)
#define BLESTCK_VERSION   0x01010100
#define BLETRANSPORT_CUSTOM   1

Transport used is CUSTOM

#define BLETRANSPORT_UART   0

BLESPECIFICATION_COMPLIANCE defines for which Bluetooth specification version the SDK is configured. Claiming Bluetooth 4.1 Bluetooth specification compliance will define the Default configuration for the following BT 4.1 features to enable (thus some of these features could be enabled/disabled):

  • L2CAP connection oriented Channels (can be disabled with BLEL2CAP_CONNECTION_ORIENTED_CHANNELS configuration )
  • 32-bit UUID attribute in ATT and GATT (can be disabled with ATT_SERVER_SUPPORT_32_BIT_UUID ATT configuration )
  • Low duty Cycle Directed Advertising (can be disabled with BLE_ADVERTISING_DIRECTED_LOW_DUTY_CYCLE_SUPPORT configuration )
  • LE Link Layer Topology (Allowing a device to be MASTER/SLAVE simultaneously and SLAVE/SLAVE simultaneously) Claiming Bluetooth 4.1 Host Compliance on a Bluetooth 4.0 controller will lead on an Initialisation failure.Transport used is UART
#define BLETRANSPORT_USED   BLETRANSPORT_UART

BLETRANSPORT_USED allows the user to choose the transport used by the BLE stack.

This enables the specific transport API for UART or custom. The default configuration is UART. Override this definition in the CustomConfig file to change the value. The different possible values are BLETRANSPORT_UART or BLETRANSPORT_CUSTOM. Default value is BLETRANSPORT_UART.

#define L2CAP_DEBUG_TRACES   0

BLE_PRINT_DEBUG_TRACES enabled the SYSTEM_Log() function in order to allow several stack layer to Print DEBUG TRACES Default behaviour is to not export traces. The stack layer Debug trace must be activated separately (see ATT_DEBUG_TRACES or SMP_DEBUG_TRACES). But disabling BLE_PRINT_DEBUG_TRACES disables all the stack layer debug* traces SMP_DEBUG_TRACES defines if the Security Manager Layer exports some debug traces during Runtime. The debug print are exported through the SYSTEM_Log() function Default behavior is to not export traces. Note that this option is ignored and override when BLE_PRINT_DEBUG_TRACES is disabled (set to 0) L2CAP_DEBUG_TRACES defines if the L2CAP Layer exports some debug traces during Runtime. The debug print are exported through the SYSTEM_Log() function Default behavior is to not export traces. Note that this option is ignored and override when BLE_PRINT_DEBUG_TRACES is disabled (set to 0)

#define NUM_COMMAND_PACKETS   2

NUM_COMMAND_PACKETS Defines the number of buffers used by the stack for HCI command transmission

#define NUM_EVENT_PACKETS   4

NUM_EVENT_PACKETS Defines the number of buffers used by the stack for HCI events reception

#define NUM_RX_DATA_PACKETS   4

NUM_RX_DATA_PACKETS Defines the number of buffers used by the stack for ACL reception

#define NUM_TX_DATA_PACKETS   4

NUM_TX_DATA_PACKETS Defines the number of buffers used by the stack for ACL transmission, minimum is 3: 1 for ATT, 1 for SMP, 1 for APP and one to be be available when the stack send packet during the L2CAP callback

#define SM_IO_DISPLAY_ONLY   0

BLE_WHITE_LIST_SUPPORT Define if the white list management support is enabled (BLE_WHITE_LIST_SUPPORT set to 1) or disabled (BLE_WHITE_LIST_SUPPORT set to 0).

Supporting this allows the application to use the White List API by adding a remote device to a white list, clearing the white list and get the white list free slot.

If the application does not uses this features, it can not defined accurate filter policy rules using the white list.

Enabling white List support increase final ROM memory footprint.

The default value is DISABLED (0) BLE_USE_HOST_CHANNEL_CLASSIFICATION Define if the HCI channels classification is enabled (BLE_USE_HOST_CHANNEL_CLASSIFICATION set to 1) or disabled (BLE_USE_HOST_CHANNEL_CLASSIFICATION set to 0).

Enabling channel classification increase final ROM memory footprint.

The default value is DISABLED (0) BLE_ENABLE_TEST_COMMANDS Define if the HCI test command support is enabled (BLE_ENABLE_TEST_COMMANDS set to 1) or disabled (BLE_ENABLE_TEST_COMMANDS set to 0).

Supporting this allows the application to use the test API by starting the receiver test, the transmitter test or stopping the tests.

Enabling HCI test command support increase final ROM memory footprint.

The default value is DISABLED (0) BLE_SECURITY Define if the Security Manager support is enabled (BLE_SECURITY set to 1) or disabled (BLE_SECURITY set to 0).

Supporting this allows to use the Security Manager API and allows the Application to use authentication and encryption for active connection.

If you do not use security, the application will reject the remote pairing request. Note that the security is active only on connection; it is automatically disabled if BLE_CONNECTION_SUPPORT is DISABLED

Enabling security support increase consequently final ROM and RAM memory footprint.

The default value is ENABLED (1)

#define SM_IO_DISPLAY_YESNO   1
#define SM_IO_KEYBOARD_DYSPLAY   4
#define SM_IO_KEYBOARD_ONLY   2
#define SM_IO_NOINPUTNOOUTPUT   3

All rights reserved. The use is subject to the XDK SDK EULA by Bosch Connected Devices and Solutions GmbH.
This documentation file has been automatically generated on Thu Mar 14 2019 19:12:41 by doxygen 1.8.8