SPRUIZ1B July 2023 – August 2024 TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1
FILE: ipc_ex1_basic_cpu1_cpu2_multi_c29x1.c
This example demonstrates how to configure IPC and pass information from C29x1 to C29x2 core without message queues. It is recommended to run the C29x1 core first, followed by the C29x2 core.
When using CCS for debugging the Multi-core example, after launching the debug session, connect to CPU1, load the c29x2.out followed by c29x1.out After the program is loaded, run CPU1. Once c29x1 configures and releases CPU2 out of reset, the program stops, connect to the CPU2 target now and load the symbols for c29x2.out.
In the default CPU2 linker cmd file, LPAx and LDAx RAMs are used for allocating various CPU2 sections. The CPU1 application assigns the ownership of these memory regions to CPU2 by using SysConfig. Please note that CPU2 .out file can be loaded only after CPU1 completes this configuration. The erase setting (CPU1/CPU2 On-Chip Flash -> erase setting) needs to be configured as selected banks only (Choose the corresponding BANKS allocated for CPUs) or necessary sectors only before loading CPU1/CPU2.out file (This is applicable only for FLASH configuration)
External Connections
Watch Variables