The Wind River (Diab) compiler 5.9.0.0 can be installed by running the file
setup.exe from the supplied media — several
options will be presented during the compiler install and the following
responses should be used:
Follow the guidance given in Section 1.5.9, “Wind River (Diab) C Compiler v5.5.1.0”.
If using a single version of the Wind River (Diab) compiler,
either setup the OPENECU_DIAB_5_9 environment variable as described
in the next point, or adjust Window's system path to include the absolute path to the
compiler's bin directory.
If using multiple versions of the Wind River (Diab) compiler (for
instance, when you are using two or more versions of OpenECU which require different
versions of the Wind River (Diab) compiler), the environment variable
OPENECU_DIAB_5_9 must be set to the absolute path to the
compiler's bin directory. This macro must terminate in a
“\” and must use the DOS 8.3 short naming convention.
E.g., D:\Progra~1\diab\5_9_0_0\win32\bin\
After setting the environment variable, MATLAB may need to be restarted to pick up the new setting. If in doubt, issue the:
oe_check_compiler
command at MATLAB's prompt to check that the environment variable is correctly setup and the compiler is available.
Closed: Can't use Simulink look up blocks
There has been a known issue which restricts the compiler to use Simulink lookup block. When using Simulink lookup blocks, the Diab compiler would stop compilation with this error message:
'[model-name].c', line [line-num]: warning (dcc:1792):
trying to assign 'ptr to volatile' to 'ptr'This has now been fixed, see F-CR 13325 in the release notes.
Open: Error message 0169
The Diab 5.9.0.0 compiler generates object files that cause the Diab ddump command to generate the following error message during an application build.
Error 0169 at offset NNNNNNNN: Unexpected EOF.
The error appears to be benign and can be ignored. Currently, there is no known workaround.