This OpenECU Third Party Tool Compatibility page is an actively managed listing to communicate the latest plan of support for the elements of OpenECU.
Each release of OpenECU (e.g., OpenECU r2.9.0) includes a file in the documentation provided with the installation which details the compatibility list of tools supported for that specific release.
In summary, the following third party tools are compatible with OpenECU (r2.9.0 for non-M560 targets and r3.0.0-FS for M5xx targets):
|Third party tool||Compatible versions|
|For Simulink model based development, OpenECU requires (at a minimum) the following MathWorks tools:
In addition, if you need to add state diagrams to the model, then you will also need:
Simulink Coder generates C code which does not lend itself to efficient repeatable testing. When creating a production version of your product, you may need better control of the structure of the C code generated from the model to reduce the cost of testing the C code against any industry standards. Under these circumstances you will also need:
|MathWorks MATLAB Coder|
|MathWorks Simulink Coder (includes functionality of RTW and Stateflow Coder)|
|MathWorks Embedded Coder|
|Compiler tools for both C-API and Simulink-API
OpenECU requires (at a minimum) one of the following compiler tools
|Wind River Diab C compiler||Versions:
*Patch file can be downloaded from www.openecu.com/downloads section M560 or M580 Hardware and related OpenECU software.
|Note: All OpenECU targets use Freescale PowerPC microcontrollers.
See the Technical Specification for your target for more information.
|Reprogramming, data logging and calibration tools
To program and calibrate an OpenECU with an application, OpenECU integrates with the following calibration tools. Only one calibration tool is required. These tools have been tested for reprogramming, data logging, and calibration. Some of them have many other features which have not been tested with OpenECU.
|Vector CANape||v8.0 through v16.0|