This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/WL1835MOD: Where are the Bluetopia flags documented?

Part Number: WL1835MOD

Tool/software: Linux

Within the Bluetopia Platform Manager documentation (Bluetopia® Platform Manager Core API Reference Manual) a lot of flags are mentioned.

E.g.

DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR

DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_KEEP_CONNECTION

Header files do enumerate these flags only. Where is the documention for these flags?

  • Hi Thomas,

    The two flags mentioned above can be found in the DEVMMSG.h. The latest release of the TI dual mode Bluetooth stack for Linux (v4.2.1.1.1.0) contains a recent addition of doxygen based code documentation in html format. For ease of use, I would recommend using the doxygen instead. You can start by opening the TIBluetopiaAPIs.html file in the Documentation folder of your SDK install directory and search for APIs, definitions and structs etc. easily from there.

    Best regards,
    Vihang
  • Hi Vihang,

    sorry, but there is no documentation about these flags at all. Did you perform the steps you recommended? Did you see any further description?

    Who is responsible and can provide us the missing documentation about the product?

    Regards,

    Thomas

    PS: Copied from file:///home/tthielemann/project/Transfer/AM335xBluetopiaLinuxProduction-4.2.1.1.1.0/Documentation/doxygen/html/_d_e_v_m_m_s_g_8h.html#a7bd996669cc9f536870a92f690b6ea4c

    ◆ DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR

    #define DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR   0x00000001
  • Thomas,

    While I agree that there is no detailed documentation on these flags, please note that these are just bitmasks that can be used in the APIs.

    For example, the DEVM_PAIR_WITH_REMOTE_DEVICES_FLAGS* bitmasks will be used in the DEVM_Pair_WithRemoteDevice API (from DEVMAPI.h) like the following.

    /* Pair with remote LE device and force pair. */
    Result = DEVM_PairWithRemoteDevice(BD_ADDR_of_Remote_LE_Device, (DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR | DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_LOW_ENERGY));

    Best regards,

    Vihang

  • Hi Vihang,

    the usage of these bits is known. But what is the difference between use or don't use DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR

    DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_KEEP_CONNECTION while pairing?

    Regards,
    Thomas

  • Hi Thomas,

    Thomas Thielemann said:
    the usage of these bits is known. But what is the difference between use or don't use DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR

    DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_KEEP_CONNECTION while pairing?

    I understand.

    • DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_FORCE_PAIR flag will cause the local DEVM to start a new pairing procedure (and discard older pairing keys if needed) with the remote device even if the remote device is already paired. This can be used as a security mechanism to update the pairing info (and the associated encryption keys) of an already existing connection in case the keys are compromised.
    • DEVM_PAIR_WITH_REMOTE_DEVICE_FLAGS_KEEP_CONNECTION flag is mainly related to the Low Energy pairing. This flag will cause local DEVM to keep the LE connection active after pairing is done. Without this flag, the low energy device will be disconnected after pairing if it was not already connected before the pairing procedure started.

    Best regards,

    Vihang