BLE5-Stack 2.02.01 (SDK 5.10) to BLE5-Stack 2.02.02 (SDK 5.20)

This section will describe a way to migrate a project from BLE5-Stack 2.02.01 to a BLE5-Stack 2.02.02 project.

The best way to migrate is to open a new project from the new SDK and transfer your changes and application code over to the new example.

Porting Simple Peripheral

For this migration guide, Simple Peripheral from BLE5-Stack 2.02.01 will be ported over to BLE5-Stack 2.02.02. The recommended approach is to start with a BLE5-Stack 2.02.02 project that contains the same base functionality as the porting target project and merge in any custom functionality.

  1. Choose a BLE5-Stack 2.02.02 example project that contains your target project’s base functionality.

  2. Transfer all modified application files from BLE5-Stack 2.02.01 into the BLE5-Stack 2.02.02 example project.

    In this example, the following files from BLE5-Stack 2.02.01 were moved into Simple Peripheral BLE5-Stack 2.02.02 example:

    • simple_peripheral.c
    • simple_peripheral.h

  3. Move any profiles and services that the application is using to the BLE5-Stack 2.02.02 project.

  4. Transfer the SysConfig settings either visually through the GUI or open both the old and the new project .syscfg files and copy-paste the desired settings.

  5. If necessary, update the project to use the newer TI-RTOS drivers that are supplied with the SimpleLink CC13x2 / 26x2 SDK.

  6. Refer to the Core SDK release notes for additional information and the TI-RTOS examples included with SimpleLink CC13x2 / 26x2 SDK.

    For additional information on how BLE5-Stack 2.02.02 uses TI-RTOS see TI-RTOS (RTOS Kernel) Overview.

    For any utilized TI Drivers, review TI-RTOS Kernel (SYS/BIOS) User’s Guide and TI Drivers API Reference.

Porting Simple Central

This section of the migration guide will focus on porting Simple Central from BLE5-Stack 2.02.01 to the BLE5-Stack 2.02.02. The recommended approach is to start with a BLE5-Stack 2.02.02 project that contains the same base functionality as the porting target project and merge in any custom functionality.

  1. Choose a BLE5-Stack 2.02.02 example project that contains your target project’s base functionality.

  2. Transfer all modified application files from BLE5-Stack 2.02.01 into the BLE5-Stack 2.02.02 example project.

    In this example, the following files from BLE5-Stack 2.02.01 were moved into Simple Central BLE5-Stack 2.02.02 example:

    • simple_central.c
    • simple_central.h

  3. Modify main.c in the BLE5-Stack 2.02.02 example if additional tasks were added in the BLE5-Stack 2.02.01 project.

  4. Move any profiles and services that the application is using to the BLE5-Stack 2.02.02.

  5. Transfer the Sysconfig settings either visually through the GUI or open both the old and the new project .syscfg files and copy-paste the desired settings.

  6. If necessary, update the project to use the newer TI-RTOS drivers that are supplied with the SimpleLink CC13x2 / 26x2 SDK.

  7. Refer to the Core SDK release notes for additional information and the TI-RTOS examples included with SimpleLink CC13x2 / 26x2 SDK.

    For additional information on how BLE5-Stack 2.02.02 uses TI-RTOS see TI-RTOS (RTOS Kernel) Overview.

    For any utilized TI Drivers, review TI-RTOS Kernel (SYS/BIOS) User’s Guide and TI Drivers API Reference.

A Few Noteworthy Changes from BLE5-Stack 2.02.01 to BLE5-Stack 2.02.02

You can follow the guide above without addressing these updates, they are listed for your information only. All fine grained details might not be mentioned, please refer to the specific example you need to port and do a compare between the old and new project files. Please refer to the BLE5-Stack Release Notes for all the details.

  • The following RTLS examples were renamed, along with any references in code:

  • RTLS examples no longer enable embedded angle calculation. The AOA_MODE_RAW remains available and provide Bluetooth Core Specifications Version 5.2 compliant IQ data that can be used for the development of algorithms that will need to be specific to your product implementation.

  • The RTLS agent tools have been modified. Please refer to <SDK>/tools/ble5stack/rtls_agent/README.md for additional details.

  • The uBLE stack has been updated to support multiple connections, connection parameter updates, and channel map update procedures.

  • The rtls_passive example, which uses the Micro BLE stack, was modified to reflect these changes.

    For more information regarding the new connection monitor features, please refer to Connection Monitor (CM) Application.

  • GAP Scanner: the SCAN_PARAM_FLT_DUP parameter (see <SDK_ROOT>/source/ti/ble5stack/inc/gap_scanner.h) is now configurable via SysConfig. It is enabled by default.

  • The Bluetooth Mesh simple_mesh_node example now includes application callbacks associated with LPNs and friendship establishment/termination.