ASAM HMS (HEX File Management System) describes a standardized approach for the management of HEX files, which are necessary assets for today’s vehicle development. HEX Files can be everything ranging from coding files up to whole software containers for the vehicle ECUs, which are being used during the development of vehicles.
The number of ECUs in vehicles is steadily increasing and their interdependencies become more and more complex. Particularly
One significant challenge in developing and test ECUs is to properly select the right HEX file to be flashed to the vehicle's ECU. To obtain correct test results, it is necessary that the correct HEX file which functionally fits to all other ECUs in the network is selected. Metadata could help to choose the correct file. However, the HEX file itself cannot contain meta information. As a result, it is currently difficult to systematically select the correct HEX files for the development and testing of networked and dependent ECUs. Therefore, a HEX file management system is needed to allocate the proper HEX files and their metadata.
ASAM HMS defines an interface with the peripheral system that allows to obtain
Types of Metadata used to describe HEX files
Typical systems connected to the interface
By managing HEX files and their associated files (
The interfaces of ASAM HMS are standardized with the Web API from RESTful and were designed based on the opensource Microsoft REST API Guidelines. Additionally, a YAML file format is provided which can be used for Swagger flameworks and will facilitate the implementation of the system. The data models of the interfaces are described by UML class diagrams. EAP files are also delivered for the UML.
The goal of ASAMM HMS is to manage the development of ECUs and to mask HEX files with various
Hino Motors Ltd., Honda R&D Co. Ltd Automobile R&D Center, Toyota Motor Corporation, AVL LIST GMBH, DXC Technology Japan, ETAS GmbH, Vector Informatik GmbH