Embedded IDE Link™ MU (for Green Hills® MULTI®) 1.0.1

Product Description

• Introduction and Key Features
• Working with Embedded IDE Link MU
• Typical Application
• Using Embedded IDE Link MU with MATLAB®
• Using Embedded IDE Link MU with Simulink®
• Using Embedded IDE Link MU with Real-Time Workshop®

Using Embedded IDE Link MU with Simulink®

Embedded IDE Link™ MU lets you perform component-based testing using Simulink® as a test harness. During the Real-Time Workshop® Embedded Coder code generation process, the link creates a PIL block from one of several Simulink components, including a model, a subsystem in a model, or a subsystem in a library. You then place the generated PIL block inside a Simulink model that serves as the test harness, and run open- or closed-loop tests.

Open-loop tests can use the Signal Builder block to provide the input test stimulus or any other Simulink signal generation device. Closed-loop tests can use the same devices as open-loop tests, but will often include a plant or environment model. When it is executed as part of the PIL cosimulation loop, a system model provides test engineers with high-fidelity test scenarios to exercise portions of the software's dynamic behavior that open-loop, stimulus-response testing cannot achieve.

PIL tests do not run in real time. After each sample period, the test halts to ensure that all data has been exchanged between the Simulink test harness and object code. You can then check functional differences between the model and generated code.

During a PIL test, you can use the MULTI® debugger to set breakpoints, step through the code, and watch variables.

An example of object code verification using processor-in-the-loop (PIL) testing. PIL testing lets you use a Simulink® test harness to compare object code execution with model simulation results. Click on image to see enlarged view.

Next