SoC Blockset™ enables simulation of multiprocessor executions as they behave on a multiprocessor SoC. In multiprocessor simulations, each processor reference model executes simultaneously, where each processor execution is managed by an independent Task Manager block representing either the OS or bare-metal scheduler for that processor. Processors can interact with each other using interprocessor communication channels, through the IPC Channel block, enabling for synchronization of tasks and algorithms between the task manager of each processor.
A multiprocessor SoC model contains at least two Task Manager blocks, each connected to a Model reference block representing the process to be run on a separate processor. This figure shows a minimal independent two-processor system.
In simulation, each Task Manager and Model block automatically acts as an independent processor. The tasks assigned to different Task Manager blocks run independently of the other processor while tasks within a single Task Manager block still behave dependently. For more information of task execution within a single processor, see What is Task Execution? and Multicore Execution and Core Visualization.
All tasks within the top-level model must use a unique identifier name.
Processors can communicate to each other asynchronously using a interprocess data channel. An interprocess data channel consists of the Interprocess Data Write, Interprocess Data Channel, and Interprocess Data Read blocks. For more information on processor to processor communication channels, see Interprocess Data Communication in Operating Systems and Interprocess Data Communication via Dedicated Hardware Peripheral.
In code generation, the top-level Simulink® model and each reference Model blocks must have their Hardware board parameter set to
a supported multiprocessor hardware board, such as
F2837xD. In the top-level model, you must set the Processing
Unit parameter to
none to indicate that the model does
not build. In each reference Model block, you must set the
Processing Unit parameter to a specific processor, such as
This example shows a minimal multiprocessor model representing an TI Delfino F2837xD hardware board that contains a pair of C28x architectures processors in the same microcontroller die.
Each reference model, driven by the Task Manager, contains a free running counter and gain. The first model,
soc_minimal_multiCPU_ref1, runs a timer task with a period of 0.01 and median task duration of 0.008. The second model,
soc_minimalCPU_ref2, runs a timer driven task with a period of 0.02 and median task duration of 0.018. To run the simulation, on the Simulation tab, click Run.
Inspecting the execution timing of the two tasks,
Task21, shows that each task executes independently of the other, simulating the expected behavior of the multiprocessor TI Delfino F2837xD device.