SWRU581 March   2021 CC2564C , CC2564MODA , CC2564MODN , WL1831

 

  1.   Trademarks
  2. 1 Introduction
  3. 2 Bluetopia
  4. 3 Bluetopia Platform Manager (BluetopiaPM)
  5. 4 Hardware Requirements
  6. 5 Software Requirements
  7. 6 Stack Supported Features
  8. 7 TI BluetopiaPM Stack Linux Architecture
  9. 8 Installing Bluetopia Platform Manager
  10. 9 BluetopiaPM Architecture
    1. 9.1 Installation Directory Structure
    2. 9.2 BluetopiaPM Structure
  11. 10The BluetopiaPM Server – Pairing Mode
  12. 11Platform Integration
    1. 11.1 Build BluetopiaPM
      1. 11.1.1 Modification of the PM Build Environment
  13. 12Adding BluetopiaPM to the SD Card
    1. 12.1 Sample Applications
    2. 12.2 Gstreamer Plugin
    3. 12.3 VNET Plugin
      1. 12.3.1 Voice Over BLE Python Script
    4. 12.4 Init-scripts
    5. 12.5 Bluetooth Hardware Configuration Script
  14. 13Terminal Connection
  15. 14Running a Sample Application
  16. 15BluetopiaPM Samples
  17.   A C256X EVM Modifications for COM8 Connector
  18.   B Bluetopia Build Log for Reference
  19.   C Sample Run
  20.   D Using the CC256x Service Pack With Linux (TI-BT-4-2-STACK-LINUX-ADDON)

10 The BluetopiaPM Server – Pairing Mode

SS1BTPM is compiled to support secure simple pairing as the default configuration. If legacy pairing is needed instead, for example so that the user is forced to enter a fixed pin code, then it is possible to configure and recompile SS1BTPM to only support legacy pairing. To do this open <INSTALLATION_DIR>/BluetopiaPM/ss1btpm/server/BTPMSRVR.c in a text editor. Near the bottom of the file modify the assignment:

DefaultInitializationData.DefaultPairabilityModeSSP = TRUE;

and change TRUE to FALSE.

DefaultInitializationData.DefaultPairabilityModeSSP = FALSE;

After making this change next rebuild SS1BTPM.

SS1BTPM is now compiled to support only legacy pairing. You will notice that the next time a device pairs with the target that the demo application will prompt the user for a pin code response. When this occurs respond with the PINCodeResponse command, for example PINCodeResponse 0000. The pin code used, 0000 in this example, must be the same on both devices.

Note: Keep in mind that Legacy Pairing is generally not as secure as Secure Simple Pairing. If security is a concern for your application then legacy pairing is not recommended. For more details on the security of Bluetooth pairing modes refer to the core specification that can be found on the Bluetooth SIG's website. Also note that, in the default configuration where secure simple pairing is enabled, legacy pairing is still supported. If a remote device attempts to connect to the target and the remote device only supports legacy pairing, the target will fall back to legacy pairing.