Embedded Target for Motorola MPC555 |
 |
Feature Summary
Simulation and Cosimulation
- Automatic S-function generation lets you validate your generated code in software-in-the-loop (SIL) simulation.
- Processor-in-the-loop (PIL) cosimulation lets you integrate generated code, running on the target processor, into your simulation.
- SIL and PIL code components are generated by the Real-Time Workshop Embedded Coder. These simulation components are in the same compact and efficient format as the production code generated for final deployment.
Production Code Generation
- The Real-Time Workshop Embedded Coder generates production code for use on the target MPC555 microcontroller.
- The Real-Time Workshop Embedded Coder generates project or makefiles for popular cross-development systems:
- Wind River Systems Diab cross-compiler
- Metrowerks® CodeWarrior®
- Debugger support:
- Wind River Systems SingleStep debugger
- Metrowerks CodeWarrior debugger
Code and Performance Analysis
Web-viewable code generation report includes
- Analysis of RAM/ROM usage and other variables
- Analysis of code generation options used, with optimization suggestions
- Hyperlinks to all generated code files
- Hyperlinks from generated code to source model in Simulink
Applications Development and Rapid Prototyping
- Generation of real-time, stand-alone code for MPC555
- Scheduler and time functions for single- rate or multirate real-time operation
- CAN-based loader for download of generated code to RAM or flash memory
- CAN-based host-target communications for non-real-time retrieval of data on host computer
Device Driver Support
- The Embedded Target for Motorola MPC555 Library provides device driver blocks that let your applications access on-chip resources. The I/O blocks support the following features of the MPC555:
- Pulse width modulation (PWM) generation via the Modular Input/Output Subsystem (MIOS) PWM unit.
- Analog input via the Queued Analog-to-Digital Converter (QADC64)
- Digital input and output via the MIOS
- Digital input via the QADC64
- Frequency and pulse width measurement via the MIOS Double Action Submodule (MDASM)
- Transmit or receive Controller Area Network (CAN) messages via the MPC555 TouCAN modules
- Utility blocks such as a watchdog timer
- Device driver blocks support a pass-through option. The pass-through option lets you leave your device driver blocks in your model during simulation. You can then provide a Simulink signal to use in place of the actual device driver signal.
CAN Support
- Transmit or receive CAN messages via the MPC555 TouCAN modules.
- CAN Drivers (Vector) library provides blocks for configuring and connecting to Vector-Informatik CAN hardware and drivers.
- The CAN Message Blocks library includes blocks for transmitting, receiving, decoding, and formatting CAN messages. It also supports message specification via the Vector-Informatik CANdb standard.
Code Validation and Performance Analysis
Code Validation. Since signal data is available to Simulink during each sample interval in a PIL simulation, you can observe signal data on Scope blocks or other Simulink signal viewing blocks. You can also store signal data to MAT-files via To File blocks. To validate the results obtained by the generated code running on the target processor, you can compare these files to results obtained using a normal Simulink plant/controller simulation.
Determining Code Size. In control design it is critical to ensure that the size of the generated code does not exceed physical limitations of RAM and ROM. The Embedded Target for Motorola MPC555 automatically produces a code generation report that displays the RAM usage and ROM size of the generated code.
This capability is useful when selecting which code generation optimizations will be used. After determining the size of the required RAM and ROM, you can consider which code generation optimizations to use, and consider modifications to the modeling style.
| Introduction to the Embedded Target for Motorola MPC555 | | Applications for the Embedded Target for Motorola MPC555 |  |