Group Actions
Engagement
  • Author Author: Jan Cumps
  • Date Created: Date Created
  • Views 3953 views
  • Likes 7 likes
  • Comments 5 comments
Related
Recommended

PSoC 6 and ModusToolbox: Create a Project with its own Board- and Module configurations

Jan Cumps

By default, projects in a workspace in the Cypress ModusToolbox IDE (mtb) share board and device configuration files.

There are several good reasons to do this, but it's not always what you need.

If you want to build designs with a different configuration, there are a few options.

The two easy ones are: multiple workspaces and - what I test here - a project with fully contained configurations.

image

 

The procedure is explained in the ModusToolbox User Guide, 5.4 Modifying the BSP Configuration for a Single Application.

If you have the IDE installed, the user guide is also available from the Help menu.

 

Summary of the goal: create a project in an active workspace that is isolated.

Board or device changes made to the project do not impact other projects.

Changes made to other projects do not impact this project.

 

Step 1: create a project for your board

 

In the IDE, create a new project. File -> New -> ModusToolbox Application

image

 

I'm using a PSoC 6 WiFi and Bluetooth prototype kit (I got this from !).

image

I use the "empty" project for this board as the base. I name it Standalone_e14_blog.

Then click Create.

image

 

The result is a new project in the IDE.

image

It uses the shared configuration in the mtb_shared folder. If I reconfigure a device or the board file in my project now, my other project SCB_UART_Trans... would get the modification too.

Now let's start to isolate our configurations.

 

Step 2: set up local configuration structure

 

Create a directory named COMPONENT_CUSTOM_DESIGN_MODUS in the root of the new project.

Right click on Project -> New -> Folder

image

Enter COMPONENT_CUSTOM_DESIGN_MODUS and click Finish.

image

In that folder, create a subfolder with the structure . In my case TARGET_CY8CPROTO-062-4343W.

image

If you don't know what the name for your board should be, check the mtb_shared project. It will have a folder with the correct name for your board.

Then, I copy the necessary files into the new folder.

Copy everything from the mtb_shared / TARGET_XXXXXXXX_ / latest-vXXXX / COMPONENT_BSP_DESIGN_MODUS, except the GeneratedSource subfolder.

 

image

I paste the files in the custom folder structure of my freshly generated project:

image

Step 3: adapt the makefile

 

You need to add two lines to the makefile. It will tell the builder to look for our local configurations.

These two lines need to be added.

 

COMPONENTS += CUSTOM_DESIGN_MODUS
DISABLE_COMPONENTS += BSP_DESIGN_MODUS

 

image

 

Save the file.

 

Last step: Refresh the Quick Panel

 

In the Quick Panel, click the Refresh Quick Panel hyperlink.

image

 

This is it. All tools will now use your local project configuration.

image

 

I have attached the project to this blog post as a zip file. You can import it in your IDE if you don't want to do all the steps.

 

PSoC 6 series
Create a Project with its own Board- and Module configurations
Low Power Management - prepare the board for current measurements
Power consumption without WiFi or Bluetooth
Create a FreeRTOS 10.3 Project
UART receiver with FreeRTOS
FreeRTOS message queue
UART receiver with FreeRTOS - Deep Sleep support
Attachments:
Standalone_e14_blog.zip
Parents

  • A little trick I use often in Eclipse to get fast access to documentation.

     

    I create a lightweight Eclipse project to collect common documentation. In this case: Controller and evelopment kit docs.

    In that project I create a virtual folder, named Documentation. It's not a real file location, but it acts a s one in Eclipse.

    Then I drag and drop any PDF that I want to have accessible while developing on that folder. This creates a link to the documents.

    All of this takes very little disk space. There are no files copied or duplicated.

     

    When opening the first one, I do that by right-clicking on it, open with other -> internal web browser,

    and click use it for all pdf files.

    The files then open as an Eclipse window just like source files.

     

    image

     

    Often, the PDF files have odd names that do not tell what the content is.

    You can rename them in Eclipse. It does not change the actual file name of the document, only how it shows in Eclipse.

     

    For documents that are project specific, like datasheets of ICs used in a particular project, I create a similar virtual folder in the project itself, and drop the datasheets in it...

Comment

  • A little trick I use often in Eclipse to get fast access to documentation.

     

    I create a lightweight Eclipse project to collect common documentation. In this case: Controller and evelopment kit docs.

    In that project I create a virtual folder, named Documentation. It's not a real file location, but it acts a s one in Eclipse.

    Then I drag and drop any PDF that I want to have accessible while developing on that folder. This creates a link to the documents.

    All of this takes very little disk space. There are no files copied or duplicated.

     

    When opening the first one, I do that by right-clicking on it, open with other -> internal web browser,

    and click use it for all pdf files.

    The files then open as an Eclipse window just like source files.

     

    image

     

    Often, the PDF files have odd names that do not tell what the content is.

    You can rename them in Eclipse. It does not change the actual file name of the document, only how it shows in Eclipse.

     

    For documents that are project specific, like datasheets of ICs used in a particular project, I create a similar virtual folder in the project itself, and drop the datasheets in it...

Children
No Data