PSOC™ 6 and XMC7000/TRAVEO™ II multi-core applications

1. Select the CM4/CM7 core project and go to Project > Options:
   
   
   
   

    

2. On the dialog, select the Debugger category in the Setup tab, and then select the appropriate Driver (I-jet, CMSIS-DAP, J-Link):
   
   
   
   

    

3. Enable hex file generation.
   
   
   
   
   • In the Runtime Checking > Output Converter category, select the Generate additional output check box.
   • Ensure Output format is set to Intel Extended hex.
   • Click OK.

    

4. Repeat these steps for all CM4/CM7 projects.

1. Select the CM0+ project and open the Options dialog.

    

2. On the dialog, select the Debugger category in the Setup tab, and then select the applicable Driver (I-jet, CMSIS-DAP, J-Link):
   
   
   
   

    

3. Switch to the Images tab to specify the extra image to be downloaded prior to debugging in order to download images of all projects in one process.
   • Select the Download extra image check box.
   • Provide a Path to the CM4/CM7's HEX image.
   • Enter 0 for Offset.
   
   
   
   
   

   If you provide an OUT file instead of a HEX file, the IAR IDE will fail to halt at the beginning of main() due to the main function present in both the CM0+ and CM4/CM7 OUT files.

   Note:

   For triple-core MCUs you should download two extra images.
4. Switch to the Build Actions category.
   
   
   
   
   • Click the New button to open the Build Action dialog.
   • Paste the following command to build the CM7_0 (or CM4) project in the Command line field as single line (edit the file name for your project)

     iarbuild.exe "..\proj_cm7_0\[project-name].ewp" -make Debug

   • Select Build Order “Run before linking”.
   • Click OK to close the Build Action dialog.
   • Click the New button again.
   • Paste the following command to build the CM7_1 project (if applicable) in the Command line field as single line (edit the file name for your project)

     iarbuild.exe "..\proj_cm7_1\[project-name].ewp" -make Debug

   • Select Build Order “Run before linking”.
   • Click OK to close the Build Action dialog.

      

   The final list should look similar to this:
   

   

   
   

    

5. Enable hex file generation. In the Runtime Checking > Output Converter category:
   • Select the Generate additional output check box.
   • Ensure Output format is set to Intel Extended hex.
   
   
   
   
   

    

6. Click OK, and then select File > Save All to save all the changes.

    

7. Build the project.

1. Create a session configuration file.

   This is an xml file containing a projects list that should be launched in a multi-core debug session. The following shows an example for a triple-core device. For a dual-core device, remove the third partner node.

   <?xml version="1.0" encoding="utf-8"?>
   
   <sessionSetup>
       <partner>
           <name>cm0</name>
           <workspace>C:\Users\mtw-multi-core\Multicore_App\multi-core_workspace.eww</workspace>
           <project>cm0</project>
           <config>Debug</config>
           <numberOfCores>1</numberOfCores>
           <attachToRunningTarget>false</attachToRunningTarget>
       </partner>
       <partner>
           <name>cm7_0</name>
           <workspace>C:\Users\mtw-multi-core\Multicore_App\multi-core_workspace.eww</workspace>
           <project>cm7_0</project>
           <config>Debug</config>
           <numberOfCores>1</numberOfCores>
           <attachToRunningTarget>true</attachToRunningTarget>
       </partner>
       <partner>
           <name>cm7_1</name>
           <workspace>C:\Users\mtw-multi-core\Multicore_App\multi-core_workspace.eww</workspace>
           <project>cm7_1</project>
           <config>Debug</config>
           <numberOfCores>1</numberOfCores>
           <attachToRunningTarget>true</attachToRunningTarget>
       </partner>
   </sessionSetup>

    

2. Configure multi-core debugging for the CM0+ project.
   1. Go to Project > Options -> Debugger.
   2. Switch to the Multicore tab.
   3. Select the Advanced radio button and specify a path to the session configuration file in the Session configuration field.
   4. Click OK.
   
   
   
   
   

    

3. Save the workspace.

Select the CM0 project and click the Download and debug button.

IAR builds all projects, programs all the separate images, and launches a multi-core debug session. IAR opens a separate IDE instance for each project specified in the session file. For dual-core MCUs, it should look like to this:

The left side of the screen shows the IAR IDE instance attached to the CM0+ core. The right side shows the CM4 (or CM7) core not started yet. Once the Cy_SysEnableCM4() function is executed on the CM0+ core, the CM4/CM7 will start executing its application.

You can step through the code by switching back and forth between the two IAR IDE instances.

The IAR IDE does not have native support for the J-Link driver, which imposes some limitations:

IAR does not provide native multi-core debugging support when using a J-Link probe. This means that in order to launch multi-core debugging, you must open a few IAR IDE instances manually (one instance per core). Also, multi-core debugging with a J-Link probe lacks some features available with CMSIS-DAP and I-jet probes. Therefore, depending on the target probe, you need to configure projects slightly differently.

• IAR will not automatically open separate IDE instances for each core, so you need to do it manually.
• Some enhanced features are not available; see the Multi-core toolbar and CTI usage section for more details.

To launch multi-core debugging with J-Link:

1. Open your multi-core IAR workspace in separate IDE instances (the number of IDE instances should be equal to the number of cores on your MCU).

    

2. Select the CM0+ project in the first IDE instance and click Download and Debug. The debugger will download all images, reset the target, and halt at the beginning of the CM0+ project's main().

    

3. Switch to the other IDE instances and select: Project > Attach to Running Target.