SDAA440 June   2026 AM13E23019

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Processor-in-the-Loop (PIL)
  6. 3 Prerequisites
  7. 4 Benchmarking the Current Control Algorithm on AM13x
    1. 4.1 Reference C28x Example Simulation Model
    2. 4.2 Simulation Model Configured for F28379D
    3. 4.3 Simulation Results
  8. 5 Isolating the Algorithm: Converting the Subsystem to a Model Reference
    1. 5.1 Conversion Procedure
    2. 5.2 Converted Model Reference Block Configured for Processor in the Loop
  9. 6 Configuring the Model Reference for AM13x PIL
    1. 6.1 Target Hardware Selection
    2. 6.2 SysConfig Configuration
  10. 7 SIL/PIL Manager
    1. 7.1 Launching the SIL/PIL Manager and Running PIL
      1. 7.1.1 Simulation Time Consideration
      2. 7.1.2 PIL Results: Showing Numerical Verification
      3. 7.1.3 PIL Results: Execution Profiling
  11. 8 Optimization and Re-Profiling
    1. 8.1 PIL Results: With Single Datatype and Sine/Cosine TMU
    2. 8.2 Codegen Report Showing TMU Functions
    3. 8.3 Enable Code View from Compare Runs Option
    4. 8.4 PIL Results: Execution Profiling with Single Datatype and Sine/Cosine TMU
  12. 9 Summary
  13. 10References

1 Introduction

Embedded control algorithms developed in Simulink are frequently first validated in simulation or prototyped on an initial target platform before a production hardware decision is finalized. In motor control, power conversion, and signal processing applications, it is common for an algorithm such as Field-Oriented Control (FOC) to have an established simulation history verified numerically in Simulink, and potentially already deployed and profiled on a prior embedded target such as the TI C28x real-time microcontroller or the TI AM261x or from a non-TI platform entirely, represented as a self-contained Simulink subsystem with no target-specific dependencies.