1 of 1 people found this helpful
ModusToolbox contains the WICED BTSDK, which supports multiple WICED Bluetooth devices. Hence, WICED and Modustoolbox works pretty much similar way except few IDE based changes.
I would suggest you to refer the "Documentations" provided in the below link to setup the Modutoolbox IDE. It has "Getting Started Documents" as well as "Configurator and Tool Documents". https://www.cypress.com/products/modustoolbox-software-environment
ModusToolbox User Guide has more explanation about the structure and usage of BTSDK libraries and BSPs. Please have a look.
When you migrate from WICED to Modustoolbox, the major change which you will be observed is in the makefile. In WICED each application will be having a "makefile.mk", where as, in Modustoolbox you will see just the "makefile". Since the structure of makefile is different in Modus, I would recommend you to create a new empty project (give appropriate custom name as well) in Modustoolbox IDE, which will obviously create an appropriate basic makefile, and then copy your WICED application code files to the project directory which you have created in Modustoolbox. If you have used any extra libraries or components in your application, please add those as well in the makefile.
If you see any compile time error, please don't hesitate to ask here. We will help you.
CYBT-413034-02, CYBT-423028-02 and CYBT-483039-02 are 20719B1 silicon based module which is supported in WICED.
CYBT-413055-02, CYBT-423054-02 and CYBT-483056-02 are 20719B2 (latest) silicon based module which is supported in Modustoolbox.
Please see below link for the change list between 20719B1 and 20719B2.