Original question:
F29H859TU-Q1: How to build a multi-core project with multi-core sysconfig
Part Number: F29H859TU-Q1
Hi team,
I ask this for my customer.
It metioned that system.xml link all the core project to one multi-core project.
Now customer want to link their own project to the multi-core project, what they need to modify in the system.xml file? And any other in project configuration needed to be modified in addition to xml file? Do we have more detailed description for this?
BRs
Shuqing
Hi Shuqing .
To link examples into a multicore project, the user first needs to edit the system.xml file in the master project folder. Additionally, the user is required to modify the pre-build and post-build steps of the projects to be merged, which may also involve changes to the makefile. It is recommended that customers create their multicore project by importing an empty multicore project and building on it, rather than attempting to merge existing projects from scratch, as this approach is more complex and prone to errors.
Currently, there is no proper documentation available on how to merge projects into a multicore project from scratch. I will raise this documentation-related issue with the relevant concerned team.
Regards ,
Lakshya Verma
Hi Shuqing,
Let me explain the complete flow.
When you import empty_project_multi into your workspace, it also imports the following projects automatically:
• empty_project_multi_c29x1
• empty_project_multi_c29x2
• empty_project_multi_c29x3
The empty_project_multi project contains a system.xml file.
This file specifies:
• Which projects are part of the multi-core system, and
• The order in which these projects are built.
As shown in the attached image, the compilation order is CPU3 project → CPU2 project → CPU1 project (this order is important).
In this setup:
• CPU1 (project: empty_project_multi_c29x1) acts as the master core
• CPU2 and CPU3 (projects: empty_project_multi_c29x2 and empty_project_multi_c29x3) act as secondary cores
CPU1 is responsible for starting and initializing CPU2 and CPU3.This behavior can be seen in the empty_project_multi_c29x1.c file.
If you check Build → Steps for each project:
• CPU2 and CPU3 projects have only post-build steps
• CPU1 project has both pre-build and post-build steps
The overall build flow is as follows:
1. CPU3 is built first . After compilation, its post-build step generates cpu3App.bin.
2. CPU2 is built next . After compilation, its post-build step generates cpu2App.bin.
3. CPU1 build starts , before compilation, CPU1 pre-build steps use cpu2App.bin and cpu3App.bin to determine how much memory space needs to be reserved for CPU2 and CPU3 programs (refer to cpuAppSec2.c, cpuAppSec3.c, and the CPU1 pre-build commands). CPU1 is then compiled and linked.
After compilation, CPU1 post-build steps copy the CPU2 and CPU3 binaries into CPU1’s output file.
As a result, the final CPU1.out contains: CPU1 program + CPU2 program + CPU3 program
When CPU1.out is loaded and executed:
CPU1 starts first , CPU1 initializes CPU2 and CPU3 then CPU2 and CPU3 are released from reset .All cores synchronize using IPC
To merge individual single-core examples from scratch, the following are required:
• Editing system.xml
• Correctly configuring pre-build and post-build steps
• Having one master project that initializes its own CPU, then initializes the other CPUs and loads their programs
This master project must follow the same structure as empty_project_multi_c29x1.
Creating this setup entirely from scratch is complex and error-prone.
That is why I recommend starting with empty_project_multi and building your application on top of it.
Regards ,
Lakshya Verma
