The process of building the model creates a number of files which
can be downloaded or programmed into an OpenECU to run in real-time. The
build process is started by selecting the model, and either pressing
CTRL-B or selecting the menu option
Tools -> Real-Time Workshop -> Build Model.
This instructs RTW to generate C code from the model and to invoke
OpenECU's template makefile to compile the C code.
The result of a successful build produces a number of files in the same directory as the step1 model:
step1_tool_generic.a2l
— the generic ASAP2 file for the build model (includes details
about the stp signals amongst other things);
step1_tool_inca.a2l — the ETAS INCA specific ASAP2 file for the build model;
step1_tool_vision.a2l — the ATI Vision specific ASAP2 file for the build model;
step1_tool_canape.a2l — the Vector CANape specific ASAP2 file for the build model;
step1_tool_vision.vst — the ATI Vision Strategy file for the build model (combined ASAP2 and S-record files — only generated if a compatible version of ATI Vision is installed);
step1.a2l.err — any errors that resulted from creating the ASAP2 file (if there are any errors, a short extract is displayed at the end of the build);
step1_image_small.s37 — the image bytes to program into the OpenECU in Motorola S-record format (small representing the minimum amount of code and data bytes to program the OpenECU device) — suitable for the ATI Vision calibration tool;
step1_image_small.hex — the image bytes to program into the OpenECU in Intel HEX format — suitable for the Vector CANape and ETAS INCA calibration tool;
step1.elf — the compiler's version of some of the above files — suitable for the PiSnoop development tool;
step1.snx — lists of variables PiSnoop will show or hide automatically — suitable for the PiSnoop development tool;
If the build fails for any reason, go back through the stages of the example and identify any corrections, or look at the installed and completed step1 model to identify any differences.