ModustoolBox (MTB) 2.2 brings with it a new unified workflow for applications. In ModustoolBox 2.0 or ModustoolBox 2.1, BTSDK apps had a different workflow than PSoC6 SDK apps, but with ModustoolBox 2.2, apps using PSoC6/BTSDK/AnyCloud SDK follow the same workflow.
In addition to the unified flow, there are some improvements available in MTB 2.2 such as added flexibility in how libraries are managed.
It’s necessary to make some changes in MTB 2.0/2.1 BTSDK applications to start using the unified flow in MTB 2.2. This blog will give you migration steps for BTSDK apps from MTB 2.0/2.1 to MTB 2.2
Before we move on to the steps for migration, there are some points to note:
What has changed in BTSDK app structure in MTB 2.2?
Steps to migrate an MTB 2.0/2.1 BTSDK application to the MTB 2.2 workflow
With wiced_btsdk 2.8, if you add more than one BSP to a project, the build will result in an error. Refer to the Bluetooth SDK 2.8 Release Notes.
To work with a different BSP, use library manager and remove (deselect) the older BSP, select the new BSP and update. Note that in a single project you can have only the BSP/BSPs of the same chip, but in a workspace if you have two or more projects, each one can use a different BSP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.