Transitioning from the v1.x to the v2.x Bluetooth Mesh SDK#

NOTE: This section replaces AN1298: Transitioning from the v1.x to the v2.x Bluetooth Mesh SDK. Further updates to this application note will be provided here.

Bluetooth Mesh Software Development Kit (SDK) v2.x contains a number of changes compared to Bluetooth Mesh SDK v1.x. Many of these changes are due to an underlying framework redesign that results in an improved developer experience within the new Simplicity Studio 5. Projects are now built on a component architecture. Simplicity Studio 5 includes project configuration tools that provide an enhanced level of software component discoverability, configurability, and dependency management. These include a Component Editor, a redesigned GATT configurator, a DCD configurator, and the stack configurator.

In Bluetooth Mesh SDK v2.x, sample applications have a new software architecture, and the Bluetooth Mesh API is redesigned. Additionally, the stack can now be configured in separate header files, and platform components can be added to the project with the Project Configurator instead of copying and including files manually. While these changes are a result of overall improvements in the SDK and in Simplicity Studio 5, it also means that migrating projects from Bluetooth Mesh SDK v1.x to v2.x is not trivial and has to be done manually. This document explains the steps needed to move your Bluetooth Mesh v1.x project into the v2.x environment.

This document is the Bluetooth Mesh extension of AN1255: Transitioning from the v2.x to the v3.x Bluetooth® SDK which contains the general Bluetooth software architecture level information.

Key Points#

Reviews difference in:

  • Software architecture for Bluetooth Mesh application

  • API

  • Stack configuration

  • New components

Bluetooth Mesh Software Development KitBluetooth Mesh Software Development Kit