1 of 1 people found this helpful
Yes, ModusToolbox consists of a new Board Support Package (BSP) flow which makes it easier to interact with Cypress Kits. In ModusToolbox, we have configurators which help you configure the parameters for the blocks you want to interact with and generate code. This way you don't need to write everything from scratch.
Here are some guides which will help you learn more about this:
Coming to Mbed, Cypress Kit BSPs are part of the MbedOS Library. For instance, you will find all targets defined at this path: "mbed-os\targets\TARGET_Cypress\TARGET_PSOC6".
Based on the Mbed Supported Kit you have, you will find the configuration files (design.modus, design.cycapsense etc..) and Generated Source folder available inside the TARGET directory here: "TARGET_PSOC6\TARGET_CY8CPROTO_062_4343W\COMPONENT_BSP_DESIGN_MODUS" . You can make use of the Configurators which are packaged with ModusToolbox available in the tools directory in the path: "<modus install dir>\tools_2.0\".
For example, you will use the Device Configurator to open the design.modus file and make necessary changes. Similary, you will use the CapSense Configurator to open the design.cycapsense file and make changes.
Once you have done the changes, save it. When you build your application in mbed, you will find the files being generated in the GeneratedSource folder which you can make use of in your mbed application.
We have a getting started guide for mbed which should be helpful here.
When it comes to creating a Custom BSP, refer Question no 24 here. Once the custom BSP is created, you can place it in the TARGET_PSOC6 directory using the prefix TARGET_<yourBSPName>. For targeting this during compilation, use:
mbed compile -t GCC_ARM -m yourBSPName
Regarding Creator and Mbed, the answer is no. There is no BSP flow in Creator, it is a device specific and schematic based design flow.
The problem I'm having is that the latest version of Modus Toolbox doesn't support the SAR using pins through ABUSMUX?
Yes, you're right. This is being fixed in the next release of ModusToolbox. Stay tuned for that