Embedded Target for Motorola MPC555

Applications for the Embedded Target
for Motorola MPC555

The Embedded Target for Motorola MPC555 provides targets that support three application scenarios.

• Processor-in-the-loop cosimulation (PIL) target
• Real-time execution and rapid prototyping (RT) target
• Algorithm export (AE) target

In the sections that follow, we summarize typical applications and the tasks you will need to perform for each; we also provide links to the relevant documentation.

Processor-in-the-Loop

The processor-in-the-loop (PIL) target lets you run a cosimulation of a closed-loop Simulink model for the purpose of code validation and analysis. When running a PI cosimulation, you use a closed-loop model with two major components: a plant model and a controller. The plant model may contain any Simulink blocks including a combination of continuous-time and discrete-time blocks. The controller must not include any continuous-time blocks, since this component is used for code generation in the Embedded-C format of the Real-Time Workshop Embedded Coder.

To get started with the PIL target, see Tutorial 1: Building and Running a PIL Cosimulation. The tutorial covers the following topics:

• Target preferences setup
• Creating the controller subsystem
• Connecting the plant model to the controller
• Selecting the PIL target
• Generating the ERT S-function and the corresponding library block
• Inserting the S-function back into the closed-loop model
• Automatic downloading of generated code with
• SingleStep debugger and a Background Debug Mode (BDM) port connector
• CodeWarrior and a BDM connector
• Running a PIL cosimulation

You may also be interested in generating code analysis information from your PIL target build. See Code Analysis Reporting for details.

Real-Time Execution and Rapid Prototyping

The Embedded Target for Motorola MPC555 real-time target enables you to use your controller block diagram in real time to perform embedded control. With this target, you can add I/O blocks for the MPC555 to your controller subsystem, generate and build code, download to the target, and run the generated C code.

When you first begin using the RT target, see Tutorial: Creating a New Application, which demonstrates the following topics through the use of a simple model with a device driver:

• Toolchain setup using target preferences
• Creating the controller subsystem
• Connecting the plant model to the controller
• Adding the MPC555 Resource Configuration block to your subsystem
• Adding I/O device drivers from the Embedded Target for Motorola MPC555 library
• Selecting the RT target
• Generating code for real-time
• Downloading code with
• SingleStep debugger and a BDM connector
• CAN
• Running the generated in real-time code

You may also be interested in generating code analysis information from your RT target build. See Code Analysis Reporting for details.

Algorithm Export

The Embedded Target for Motorola MPC555 algorithm export (AE) target enables you generate code for your controller subsystem and build the code as a stand-alone executable for use on the MPC555. The difference between the AE and the PIL target is that the AE target eliminates all extraneous code (such as serial communications code) used for cosimulation, and also eliminates any real-time interrupts. The AE target therefore generates code only for the basic controller subsystem (e.g. algorithm code). You can then modify or customize this code for your own special purposes.

In contrast, the RT target provides turnkey code including interrupt service routines, driver code, and underlying initialization code for the MPC555. Depending upon your particular application, you may find it more valuable to begin with the AE target baseline, and extend this environment for your own use.

The AE target is documented in Algorithm Export Target.

Like the PIL and RT targets, the AE target supports generation of code analysis information. See Code Analysis Reporting for details.

Feature Summary

Hardware and Software Requirements