AN215656  PSoC™ 6 MCU dual-core system design

1. Launch Eclipse IDE for ModusToolbox™ 3.0 or later and select a workspace.
2. From the Quick Panel, click New Application.
3. Once the project creator wizard opens, expand PSoC™ 6 BSPs and select CY8CPROTO-062S2-43439. Click Next.
4. In the new window, expand Getting Started, select Dual-CPU Empty PSoC6 App and Hello World. Click Create.
5. In Figure 2 , you see both applications created in the workspace.

   
   

1. For project creation, open a CLI terminal and navigate to ModusToolbox™ software installation folder such as <install_path>/ModusToolbox/tools_<version>/project-creator/.
2. Create both the applications by executing the following project-creator-cli commands.

   • project-creator-cli \
     --board-id CY8CPROTO-062S2-43439 \
     --app-id mtb-example-psoc6-hello-world \
     --user-app-name Hello_World \
     --target-dir "C:/workspace_directory"

   • project-creator-cli \
     --board-id CY8CPROTO-062S2-43439 \
     --app-id mtb-example-psoc6-dual-cpu-empty-app \
     --user-app-name Dual-CPU_Empty_PSoC6_App \
     --target-dir "C:/workspace_directory"

Alternatively, you can execute the project-creator tool in the same folder and follow the same steps described in Eclipse IDE for ModusToolbox™.

For more information, see Section 2.3 in the ModusToolbox™ user guide.

The following contents from the Hello World example need to be selectively copied to the CM4 project (proj_cm4) of the Dual CPU Empty application:

1. Makefile variables – Open the Makefile of the Hello World application and proj_cm4 application side-by-side. Compare and copy the variable values from the Hello World Makefile to the proj_cm4 Makefile. If some of the variables defined in the Hello World Makefile are not present in the proj_cm4 Makefile, they should be available in the common.mk and common_app.mk Makefiles at the root level of the dual-core empty application.

   Current values of variables such as MTB_TYPE, APPNAME, COMPONENTS, and DISABLE_COMPONENTS in the Dual CPU Empty application Makefiles should not be deleted or modified. Adding new values is still allowed for variables such as COMPONENTS and DISABLE_COMPONENTS.

   For the Hello World application case, there are no Makefile variables that need to be copied.

2. Source files – Replace all the source files from the proj_cm4 application with the Hello World application.
3. Libraries/Middleware – The libraries or middleware used in the Hello World application should also be added to the proj_cm4 application. Follow these steps to add them:
   1. In the Eclipse IDE of ModusToolbox™, from the quick planel launch Library Manager tool. Alternatively, you can launch the Library Manager from the tools folder of ModusToolbox™ installation directory, in this case the correct path to the Dual CPU Empty application needs to be selected from the Library Manager window.
   2. Once the Library Manager opens, click Add Library.
   3. Select Target Project as proj_cm4.
   4. Under Peripheral, select retarget-io library, and click OK.
   5. Click Update from the Library Manager window. Wait for the libraries to get added; see the log messages for progress.
   6. Once the libraries are updated, click Close.

The CM0+ project (proj_cm0p) of the Dual CPU Empty application enables the CM4 core and goes to Deep Sleep. To use the core for any other purpose, the cybsp_init() function needs to be called from the CM0+ core. This function will do all the system-level initialization required to run peripherals on the CM0+ core. Modify the main.c file of proj_cm0p as shown in Code Listing 1.

#include "cy_pdl.h"
#include "cycfg.h"
#include "cybsp.h"
int main(void)
{
  cy_rslt_t result;
					
  /* Initialize the device and board peripherals */
  result = cybsp_init() ;
  if (result != CY_RSLT_SUCCESS)
  {
    CY_ASSERT(0);
  }
				
  /* Enable global interrupts */
  __enable_irq();
				
  /* Enable CM4. CY_CORTEX_M4_APPL_ADDR must be updated if CM4 memory layout is changed. */
  Cy_SysEnableCM4(CY_CORTEX_M4_APPL_ADDR);
				
  for (;;)
  {
    Cy_SysPm_DeepSleep(CY_SYSPM_WAIT_FOR_INTERRUPT);
  }
}

The application can be built and programmed using one of the following methods:

• Using Eclipse IDE for ModusToolbox™
  1. Select the Dual-CPU_Empty_PSoC6_App application from the project explorer.
  2. From the quick panel, select Dual-CPU_Empty_PSoC6_App Program MultiCore (KitProg3). This will build and program both projects – proj_cm0p and proj_cm4, one after the other.
  3. Alternatively, you can program individual projects (proj_cm0p or proj_cm4), but this is only possible through CLI interface as explained below.
• Using Command-line Interface (CLI)
  1. Open a modus-shell and navigate it to the root directory of the Dual-CPU_Empty_PSoC6_App application.
  2. Run command - make program. This will build and program both projects – proj_cm0p and proj_cm4, one after the other.
  3. Alternatively, you can program individual projects (proj_cm0p or proj_cm4). Navigate the modus-shell to the required project directory. Run command - make program_proj.

The build artifacts for each project is generated in its own project directory under a folder named build. Note that the build folder in the application level has a copy of the project hex files. It also has a combined hex file containing the data of individual project hex files.

If the projects fail to build due to a flash overflow error, follow the steps from the Customizing linker scripts section to allocate the required memory for each project.

ModusToolbox™ software has a mechanism to load and run applications on the following IDEs:

• IAR Embedded Workbench
• Keil µVision
• Visual Studio Code

For more details on how to export and set up debugging with these tools, see the “Exporting to IDEs” chapter in the ModusToolbox™ user guide.

If you are using PSoC™ Creator, you can export your project to Keil µVision or IAR Embedded Workbench for dual-core debugging. Following are the steps to do so:

1. 1.
2. 1.
3. 1.
4. 1.
5. 1.

1. Configure the PSoC™ Creator Project

   Update the Target IDEs settings in the project Build Settings, as Figure 11 shows

   For µVision, select CMSIS Pack: > Generate. Enter appropriate identifying text for the CMSIS pack in the Vendor, Pack, and Version fields

   Recommended: select Toolchain: > ARM MDK Generic

   For IAR, you only need to select IAR EW-ARM: > Generate. (An advanced option, Generate without copying PDL files, is also available.) IAR has its own compiler (not supported by PSoC™ Creator), so the Toolchain selection is irrelevant

   
   

   Then build your PSoC™ Creator project in the usual manner. A folder Export is created in your <project>. cydsn folder, which contains relevant files for exporting to the selected IDE or IDEs

   For µVision, after the PSoC™ Creator project is built, find the corresponding .pack file in the folder Export \ Pack. Double-click the file to install it as a µVision pack, as Figure 12 shows.

   Note: Do not use the µVision Pack Installer Wizard File Import function to install this pack.

   
   

   if you update the PSoC™ Creator project, consider changing the µVision pack version number (see Figure 11) and installing the new pack

   For more information, see AN219434 - Importing PSoC™ Creator Code into an IDE for a PSoC™ 6 Project

2. Create µVision projects

   For µVision, you must create two projects: one for each PSoC™ 6 MCU CPU: CM0+ and CM4. Do the following:

   Recommended: create a new folder (For example. µVisionBuild) within your PSoC™ Creator <project>. cydsn folder to store all µVision project files separately from the PSoC™ Creator files (this is different from the IAR instructions). Within that folder, create another new folder for CM4 object files (For example, ObjectsM4), as Figure 13 shows:

   
   

   Open µVision 5.25 or later and create a new project (Project > New µVision Project...) in the µVisionBuild folder

   Recommended: name the project based on the original PSoC™ Creator project name and the target CPU. For example, for the CE216795 dual-core blinky project, create a µVision project BlinkyM0p for the CM0+ CPU, as Figure 14 shows:

   
   

   After you click Save, a Select Device for Target ‘Target 1’... dialog box is displayed. The two PSoC™ 6 MCU CPUs that were defined in the previously installed pack (Figure 12) are displayed. Select the CM0+ CPU, as Figure 15 shows. Click OK.

   
   

   Next, a Manage Run-Time Environment dialog box is displayed. Click Select Packs and uncheck Use latest versions of all installed Software Packs. Select the pack from the PSoC™ Creator project, as Figure 16 shows:

   
   

   Click OK; the Manage Run-Time Environment dialog changes as Figure 17 shows. Select the Device Startup and PDL Drivers and click OK. The project is created, with a Target 1, a Source Group 1, and Device startup and PDL files, as Figure 18 shows

   
   

   
   

   Right-click Source Group 1, and select Add Existing Files to Group ‘Source Group 1’.... Navigate to your PSoC™ Creator project folder and select main_cm0p.c, cy_ipc_config.c, and all other non-system .c and assembler files needed for your project, as Figure 19 shows. You do not have to add any .h files, startup, or system .c, or assembler files. Click Add; the files are added to the source group in the µVision project. Click Close.

   
   

   Now that the project is created, you must set its options. Right-click Target 1, and select Options for Target ‘Target 1’.... Confirm in the Target tab that the device, CPU, IROM1, and IRAM1 are correct for your PSoC™ 6 MCU device, as Figure 20 shows. Updating other fields such as Xtal (MHz) and Operating system is optional

   
   

   In the User tab, verify that the correct post-build batch file from the pack is being called. Hover the cursor over the User Command field and confirm that postbuildCortexm0p.bat is called, as Figure 21 shows. Add other pre- and post-build batch files, and select other options, as needed

   
   

   Confirm in the C/C++ tab that the C99 mode option is checked, as Figure 22 shows. (PDL is developed based on C99.) Add the PSoC™ Creator <project>.cydsn folder to the Include Paths; this provides a link to the .h files in the PSoC™ Creator project. Update other options and fields as needed

   
   

   Confirm in the Linker tab that the R/O Base and R/W Base fields are correct for your PSoC™ 6 MCU device, as Figure 23 shows. Select the appropriate Scatter File from your PSoC™ Creator project folder

   
   

   Connect the CY8CKIT-062-BLE USB port to your computer. Press the kit button SW3 to put KitProg2 into CMSIS-DAP mode; see the kit guide for details. This allows debugging without using any external probes

   In the Debug tab, select Use CMSIS-DAP Debugger, as Figure 24 shows. Click Settings, select KitProg2 CMSIS-DAP, and confirm that all other settings are at the defaults shown. Click OK and go back to the Options dialog

   
   

   In the Utilities tab, confirm that Use Debug Driver is checked, and then uncheck Update Target before Debugging. Click Settings, and uncheck all Download Function boxes, as Figure 25 shows. Click Do not Erase. Click OK and go back to the Options dialog.A warning “Nothing to do ... “ is displayed; click OK. The application will be loaded by the CM4 project. Click OK to save and close the options settings

   
   

   Repeat the previous steps and create a second project for CM4.

   Recommended: name the project based on the original PSoC™ Creator project name and the target CPU. For example, for the CE216795 dual-core blinky project, create µVision project BlinkyM4p; see Figure 14. Configure the project in the same manner as the CM0+ project, with the following differences:

   • The CM4 project must be in the same folder as the CM0+ project; in this case, µVisionBuild. See Figure 14
   • Select the CM4 CPU from the previously installed pack; see Figure 15
   • Navigate to your PSoC™ Creator project folder and select main_cm4.c, cy_ipc_config.c, and all other non-system .c and assembler files needed for your project, as Figure 19 shows. You do not have to add any .h files, startup, system .c, or assembler files
   • In the Options dialog, Output tab, click Select Folder for Objects..., and select the ObjectsM4 folder that you created; see Figure 13
   • In the Options dialog, C/C++ tab, add --fpu=fpv4-sp to Misc Controls; see Figure 22
   • In the Options dialog, Linker tab, select the “cm4_dual” scatter file, as Figure 26 shows. The CM4 project will contain code for both CPUs. Add --fpu=fpv4-sp to Misc Controls

   
   

   • In the Options dialog, Debug tab, Target Driver Setup, select VECTRESET for the Reset option; see Figure 24.
   • In the Options dialog, Utilities tab, confirm that Update Target before Debugging is checked, as Figure 27 shows. Set the RAM for Algorithm values as indicated. Checking Reset and Run is optional but convenient

   
   

   Finally, create a µVision workspace (Project > New Multi-Project Workspace...), named for example Blinky, in the uVisionBuild folder. Add the two created projects to that workspace. The created workspace and projects, and the corresponding files, should be similar to Figure 28.

   
   

   Build the projects in sequence; build the CM0+ project first. Note that µVision has a batch build feature to automate the process. After building is successfully completed, right-click the BlinkyM4 project and set it as the active project. Then test your build options by (1) erasing flash (Flash > Erase), and (2) downloading the project (Flash > Download) and confirming correct operation. If you did not select Reset and Run (see Figure 27), you must press the kit reset button (RST / SW1) to start operation

   Note: If you change any code in the CM0+ project, you must rebuild both projects. Note that µVision has a batch build feature to automate the process.
3. Debug µVision projects

   Start debugging with the CM4 project – downloading the CM4 project installs code for both CPUs. Set the CM4 project as the active project, download it if needed, and click Debug > Start/Stop Debug Session to start debugging. The µVision window appears similar to Figure 29.

   
   

   If you are running the CE216795 dual-core blinky project, set a breakpoint at line 63, Cy_Syslib_Delay(). Then repeatedly click Debug > Run, and the red LED toggles on each stop at the breakpoint

   Now open a second instance of µVision and load the same workspace. Both instances share the kit connection and the PSoC™ 6 MCU debug access port (DAP). Make the CM0+ project active, and start a debug session. Set a breakpoint at line 63, Cy_Syslib_Delay(). Then repeatedly click Debug > Run, and the blue LED toggles on each stop at the breakpoint

   Note: Executing the Cy_SysEnableCM4() function call at line 55 causes CM4 to start running again. Go to the CM4 window, click Debug > Stop, then Debug > Run. CM4 runs to the breakpoint again.

   It helps to place the instance windows side by side on your desktop. The windows appear similar to Figure 30. Click in the appropriate window to perform a debug operation on the desired CPU. Note that breakpoints can be set separately for each CPU. You can read and update the same memory addresses from either window

   
   

4. Create IAR-EW projects

   For IAR Embedded Workbench (IAR-EW), you must create two projects: one for each PSoC™ 6 MCU CPU: CM0+ and CM4. Do the following:

   Note: The IAR-EW project files should be created in your PSoC™ Creator <project>.cydsn folder. Do not create a separate folder within your PSoC™ Creator <project>.cydsn folder (this is different from the µVision instructions). Recommended: add a tag such as “IAR_” to each project and workspace file name, to distinguish the IAR-EW files from the PSoC™ Creator files in the same folder.

   Open IAR Embedded Workbench for ARM® 8.22 or later and create a new project (Project > Create New Project...). In the Create New Project dialog (Figure 31), confirm that the Tool chain is Arm®, select the Empty project template, then click OK.

   
   

   Recommended: in the Save As dialog (Figure 32), name the project based on the original PSoC™ Creator project name and the target CPU. For example, for the CE216795 dual-core blinky project, create a µVision project IAR_BlinkyM0p for the CM0+ CPU

   
   

   Select Tools > Options and make sure that Enable project connections is checked. Click OK. Then select Project > Add Project Connection.... In the next dialog, select Connect using IAR Project Connection, and click OK. Then select the ...CortexM0p.ipcf file, as Figure 33 shows. Click OK, and several folders and files are added to the project in the Workspace window

   
   

   Now that the project is created, you must set its options. Right-click the project, and select Options.... Confirm in the Options dialog, Build Actions section that postbuildCortexM0p.bat is called, as Figure 34 shows

   
   

   In the Debugger section, Setup tab, select the CMSIS DAP driver. In the Download tab, check Suppress download. In the CMSIS DAP section, Setup tab, set Reset to Disabled (no reset). The application will be loaded by the CM4 project. In the Interface tab, select SWD. Click OK.

   Repeat the previous steps and create a second project for CM4. Recommended: name the project based on the original PSoC™ Creator project name and the target CPU. For example, for the CE216795 dual-core blinky project, create IAR-EW project IAR_BlinkyM4; see Figure 32. Configure the project similar to the CM0+ project, with the following differences:

   • The CM4 project must be in the same folder as the CM0+ project; in this case, your PSoC™ Creator <project>.cydsn folder. See Figure 32
   • Select the ...CortexM4.ipcf file; see Figure 33
   • In the Options dialog, General Options section, Output tab, change the output directories for object and list files, as Figure 35 shows. Do not change the executables/libraries output folder

   
   

   • In the Build Actions section, confirm that postbuildCortexM4.bat is called, see Figure 34
   • In the Debugger section, Setup tab, select the CMSIS DAP driver. In the CMSIS DAP section, Setup tab, confirm that Reset is set to System (default). In the Interface tab, select SWD. Click OK

   Save Workspace As dialog, create an IAR-EW workspace, named for example IAR_Blinky, in your PSoC™ Creator <project>.cydsn folder. The created workspace and projects, and the corresponding files, should be similar to Figure 36. The files and folders generated by IAR-EW are highlighted

   
   

   Connect the CY8CKIT-062-BLE USB port to your computer. Press kit button SW3 to put KitProg2 into CMSIS-DAP mode; see the kit guide for details. This allows debugging without using any external debug probes

   Build the projects in sequence; build the CM0+ project first. Note that IAR-EW has a batch build feature to automate the process. After building is successfully completed, right-click the BlinkyM4 project and set it as the active project. Then confirm that your build options are correct, by (1) erasing flash (Project > Download > Erase memory), and (2) downloading the project (Project > Download > Download active application) and confirming correct operation. After downloading, press the kit reset button (RST / SW1) to start operation

   Note: When erasing flash, you typically only need to erase PSoC™ 6 MCU application flash (0x1000 0000 – 0x100F FFFF), as Figure 37 shows.

   
   

   Note: If you change any code in the CM0+ project, you must rebuild both projects. Note that IAR-EW has a batch build feature to automate the process.
5. Debug IAR-EW projects

   Reopen the options for the CM4 project, and go to the Debugger section, Multicore folder. PSoC™ 6 MCU has different cores, for example, CM0+ and CM4, which is referred to as "asymmetric multicore". Therefore, fill in the fields in the Asymmetric multicore section as Figure 38 shows. Checking Enable multicore master mode makes the CM4 CPU the master for download and debugging purposes. Do not change the Port.

   
   

   Select File > Save All to save the project options changes. Then start debugging by selecting either Project > Download and Debug or Project > Debug without Downloading. A second (slave) instance of IAR Embedded Workbench is automatically opened for the CM0+ project. Both instances share the kit connection and the PSoC™ 6 MCU debug access port (DAP).

   In the slave instance, set a breakpoint at line 63, Cy_Syslib_Delay(). Then repeatedly click Debug > Go, and the blue LED toggles on each stop at the breakpoint

   Click anywhere in the CM4 instance window and repeat the process. The red LED toggles on each stop at the breakpoint

   It helps to place the instance windows side by side on your desktop. The windows appear like Figure 39. Click in the appropriate window to perform a debug operation on the desired CPU. Note that breakpoints can be set separately for each CPU. You can read and update the same memory addresses from either window

   
   

   You can stop debugging in either window; debugging is ended for both CPUs. Press the kit reset button (RST/SW1) to restart kit operation