When the application is built, the automatically generated application code and the platform software are combined, and the result is the application software configured for the target ECU hardware.
The application name, description and copyright, as well as the time and date when the application was built, is available through ASAP2 entries. This information is useful when confirming what the ECU is actually executing.
Table 5.12. Automatic ASAP2 entries for application build information
| ASAP2 name | Description | Units |
|---|---|---|
| mpl_app_ver_major | The application software major version number. | - |
| mpl_app_ver_minor | The application software minor version number. | - |
| mpl_app_ver_sub | The application software sub-minor version number. | - |
| mpl_app_build_sec | The seconds when the application software was built. | seconds |
| mpl_app_build_min | The minute when the application software was built. | minutes |
| mpl_app_build_hour | The hour (in 24 hour format) when the application software was built. | hours |
| mpl_app_build_day | The numerical day when the application software was built. | days |
| mpl_app_build_month | The numerical month when the application software was built. | months |
| mpl_app_build_year | The numerical year when the application software was built. | years |
| mpls_app_build_time | The date and time when the application was built as a text string. | - |
| mpls_app_copyright | The copyright notice for the application. | - |
| mpls_app_description | The application description. | - |
| mpls_app_name | The name of the built application. | - |
| mpls_app_version | The application version number as a text string. | - |
The time displayed at the end of a build in Simulink matches ASAP2 entries above. This can be useful when determining whether the correct version of the application was programmed into the ECU.