ADV flags role ?

RE: ADV flags role ?

endnode — Thu, 09 Mar 2017 15:35:41 GMT

These are just header constants copying BT SIG specification, they are not saying anything about actual support of particular feature. I don't see any reason why to remove them...

RE: ADV flags role ?

Petter Myhre — Thu, 09 Mar 2017 15:08:12 GMT

Maybe they should be removed, but Bluetooth Classic is not supported.

RE: ADV flags role ?

ToTo — Thu, 09 Mar 2017 14:56:04 GMT

Why then we have that flag defined in the SDK examples ?

    /**@defgroup BLE_GAP_ADV_FLAGS GAP Advertisement Flags
 * @{ */
#define BLE_GAP_ADV_FLAG_LE_LIMITED_DISC_MODE         (0x01)   /**< LE Limited Discoverable Mode. */
#define BLE_GAP_ADV_FLAG_LE_GENERAL_DISC_MODE         (0x02)   /**< LE General Discoverable Mode. */
#define BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED         (0x04)   /**< BR/EDR not supported. */
#define BLE_GAP_ADV_FLAG_LE_BR_EDR_CONTROLLER         (0x08)   /**< Simultaneous LE and BR/EDR, Controller. */
#define BLE_GAP_ADV_FLAG_LE_BR_EDR_HOST               (0x10)   /**< Simultaneous LE and BR/EDR, Host. */
#define BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE   (BLE_GAP_ADV_FLAG_LE_LIMITED_DISC_MODE | BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED)   /**< LE Limited Discoverable Mode, BR/EDR not supported. */
#define BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE   (BLE_GAP_ADV_FLAG_LE_GENERAL_DISC_MODE | BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED)   /**< LE General Discoverable Mode, BR/EDR not supported. */
/**@} */

RE: ADV flags role ?

Petter Myhre — Thu, 09 Mar 2017 14:52:32 GMT

Our devices and SoftDevices doesn't support Bluetooth Classic, only Bluetooth low energy.

I'm not sure if the SoftDevice even allows you to do this, but you will definately not be able to connect to any Bluetooth Classic device.