Embedded IDE Link TS 1.3.1
for Altium TASKING

Product Description

• Introduction and Key Features
• Working with Embedded IDE Link™ TS
• Using Embedded IDE Link™ TS with MATLAB®
• Using Embedded IDE Link™ TS with Simulink®
• Using Embedded IDE Link™ TS with Real-Time Workshop®

Using Embedded IDE Link™ TS with Simulink®

Embedded IDE Link TS lets you perform component-based testing using Simulink as a test harness. During code generation with Real-Time Workshop Embedded Coder, Embedded IDE Link TS 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 model. When executed as part of the PIL cosimulation loop, a plant 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 the object code. You can then automatically compare functional differences between the model and the generated code.

During a PIL test, you can use the TASKING debugger to set breakpoints, step through the code, and watch variables. After the test, Embedded IDE Link TS returns execution profiling and code coverage reports to MATLAB for your review.

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