Method and device for converting A2L file generated by Vector into INCA compatible file

Abstract

The invention provides a method and device for converting an A2L file generated by Vector into an INCA compatible file, relates to the technical field of A2L file compatibility, and aims to solve the problem of A2L file compatibility between the Vector and an ETAS calibration tool, analyze the A2L file through AML grammar to extract key elements, convert an IFDATA segment based on an extensible mapping rule base, analyze an MAP / ELF file to update an ECU parameter physical address and verify the ECU parameter physical address. And reconstructing and generating a compatible file according to an ASAP2 standard. The system comprises an analyzer, a conversion engine, an address updating module and a file generator, automatic high-precision conversion is achieved, manual modification errors are avoided, and normal use of files in INCA is guaranteed.

Description

Technical Field

[0001] This invention relates to the technical field of A2L file compatibility, and in particular to a method and apparatus for converting A2L files generated by Vector into INCA-compatible files. Background Technology

[0002] In the field of automotive electronic control unit (ECU) development, the ASAP2 standard (ASAMMCD-2MC), as a general specification for calibration databases, defines the A2L file format for describing the ECU's communication interfaces, measurement variables, and calibration parameters. Vector's CANape and ETAS' INCA, as mainstream calibration tools in the industry, both use this standard to implement ECU calibration functions.

[0003] In current industry practice, when migrating A2L files between Vector and ETAS toolchains, engineers must manually analyze file structure differences, modify hardware-related parameters in the IF_DATA section item by item, adjust the syntax of event triggering logic, and handle compatibility issues with compiler extended keywords. While ETAS's MDA (Measurement and Diagnostics Adapter) component can achieve partial automation, manual intervention is still required to configure conversion rules, and the converted files often need secondary verification to ensure functional integrity. This situation leads to efficiency bottlenecks and the risk of human error in cross-platform calibration. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a method and apparatus for converting A2L files generated by Vector into INCA-compatible files, thereby alleviating the technical problem of A2L file compatibility between different calibration tools (Vector and INCA) through automated conversion.

[0005] In a first aspect, the present invention provides a method for converting a Vector-generated A2L file into an INCA-compatible file, comprising: Obtain the A2L file to be converted generated by Vector, the address trace file used to characterize the debugging information during the ECU program operation, and the preset configuration file used to characterize the mapping relationship between Vector and ETAS hardware interface; The ASAM standard syntax description rules are used to extract key elements from the A2L file to be converted; Based on the preset configuration file, the IF_DATA segment in the A2L file to be converted is replaced with parameters and converted with events to obtain an INCA-compatible IF_DATA segment that is adapted to the ETAS hardware interface. Based on the address tracing file, the ECU parameters in the A2L file to be converted are updated and verified using physical addresses; Based on the fixed structure template defined by the ASAP2 standard, the device parameters in the key elements, the INCA-compatible IF_DATA section, and the updated ECU parameters are reconstructed to generate an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface.

[0006] In an optional implementation, the step of extracting key elements from the A2L file to be converted using ASAM standard syntax description rules includes: The ASAM standard syntax description rules are determined based on the AML syntax definition; According to the ASAM standard syntax description rules, field information is identified from the A2L file to be converted; wherein, the field information includes keywords, block structure, and attributes; Based on the field information, key elements including device parameters, IF_DATA segments, and ECU parameters are extracted.

[0007] In an optional implementation, the step of performing parameter replacement and event conversion on the IF_DATA segment of the A2L file to be converted based on the preset configuration file to obtain an INCA-compatible IF_DATA segment adapted to the ETAS hardware interface includes: Load the preset configuration file to determine the mapping relationship between Vector and ETAS hardware interfaces; Identify the Vector hardware identifier used for positioning from the ETK block of the IF_DATA segment; Based on the mapping relationship, match the ETAS hardware identifier corresponding to the Vector hardware identifier, replace the Vector-specific interface configuration information in the IF_DATA segment with the ASAM parameter corresponding to the ETAS hardware identifier, and simultaneously adjust the interface configuration data of the IF_DATA segment. The measurement and calibration events in the IF_DATA segment of the A2L file to be converted are transformed into an event structure recognizable by the INCA scheduling model adapted to the ETAS hardware interface.

[0008] In an optional implementation, the step of updating and verifying the physical address of the ECU parameters in the A2L file to be converted based on the address tracing file includes: Load the address traceability file and extract the physical address information corresponding to the simple and complex parameters in the ECU parameters using the parser built into the address traceability file; Based on the parameter type of the ECU parameters, the corresponding physical address information is selected to replace the virtual address extracted from the ECU parameters; Verify the boundary validity and data type matching of the updated address of the ECU parameters.

[0009] In an optional implementation, the step of loading the address traceability file and extracting the physical address information corresponding to the simple and complex parameters in the ECU parameters using the parser built into the address traceability file includes: The physical addresses of simple parameters in the ECU parameters during ECU program runtime are extracted from the MAP file of the address tracing file by the script; The physical base address and structure offset information of global variables are extracted from the ELF file of the address tracing file using the debug_info section, and the physical address of complex parameters in the ECU parameters is calculated.

[0010] In an optional implementation, the step of reconstructing and generating an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface, based on a fixed structure template defined by the ASAP2 standard, the device parameters in the key elements, the INCA-compatible IF_DATA section, and the updated ECU parameters, includes: Based on the fixed structure template defined by the ASAP2 standard, the device parameters in the key elements are used to fill the file header, project information and module declaration. The hardware interface configuration for ETAS hardware compatibility is completed based on the converted IF_DATA segment. Then, according to the physical address provided by the updated ECU parameters, the INCA compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface is reconstructed in the fixed order of the ASAP2 standard.

[0011] In an optional implementation, the A2L file to be converted includes at least device parameters, the Vector's preset IF_DATA segment, and ECU parameters; the address tracing file includes at least a compiled MAP file or ELF file; and the preset configuration file includes at least a mapping rule library for the correspondence between Vector and ETAS hardware interfaces.

[0012] Secondly, the present invention provides an apparatus for converting Vector-generated A2L files into INCA-compatible files, comprising: The module acquires the A2L file to be converted generated by Vector, the address trace file used to characterize the debugging information during the ECU program's operation, and the preset configuration file used to characterize the mapping relationship between Vector and ETAS hardware interfaces. The extraction module uses ASAM standard syntax to describe rules and extracts key elements from the A2L file to be converted. The conversion module, based on the preset configuration file, performs parameter replacement and event conversion on the IF_DATA segment in the A2L file to be converted, to obtain an INCA-compatible IF_DATA segment that is adapted to the ETAS hardware interface; The update module updates and verifies the physical address of the ECU parameters in the A2L file to be converted, based on the address tracing file. The reconstruction module, based on a fixed structure template defined by the ASAP2 standard, uses the device parameters in the key elements, the INCA-compatible IF_DATA segment, and the updated ECU parameters to reconstruct and generate an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface.

[0013] Thirdly, the present invention provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the computer program to implement the steps of the method described in any of the foregoing embodiments.

[0014] Fourthly, the present invention provides a machine-readable storage medium storing machine-executable instructions, which, when invoked and executed by a processor, cause the processor to perform the steps of the method described in any of the foregoing embodiments.

[0015] This invention provides a method and apparatus for converting Vector-generated A2L files into INCA-compatible files. First, it obtains the A2L file to be converted generated by Vector, an address traceability file (MAP / ELF file) representing ECU program debugging information, and a preset configuration file representing the mapping relationship between Vector and the ETAS hardware interface. Then, using ASAM standard syntax description rules, it accurately extracts key elements such as device parameters, interface data information, and ECU parameters from the A2L file to be converted. Subsequently, based on the preset configuration file, it performs hardware interface parameter replacement and Vector-specific measurement / calibration event conversion on the IF_DATA segment of the A2L file to obtain an INCA-compatible IF_DATA segment adapted to the ETAS hardware interface. Simultaneously, based on the address traceability file, it extracts variable physical addresses and calculates base addresses and element offsets for complex parameters such as structures, completing the update of ECU parameter physical addresses and verifying address boundary legality and data type matching. Finally, based on the ASAP2 standard fixed structure template, it integrates the device parameters, the INCA-compatible IF_DATA segment, and the updated ECU parameters to reconstruct and generate an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface. This solution uses standardized parsing, automated mapping conversion, precise address updates, and structured reconstruction as its core technical approaches. It effectively overcomes the compatibility barrier between Vector-generated A2L files and the INCA tool adapted to ETAS, completely solving the problems of low efficiency and error-proneness in traditional manual or semi-automatic conversion. It achieves automation and high precision in IF_DATA segment adaptation and ECU parameter address updates, ensuring that the converted A2L file can normally connect to the ECU and access all variables in the INCA environment. This provides an efficient and reliable compatibility solution for automotive ECU calibration development.

[0016] Other features and advantages of this disclosure will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the techniques described above.

[0017] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0018] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating a method for converting a Vector-generated A2L file into an INCA-compatible file, provided in an embodiment of the present invention; Figure 2 This is a functional block diagram of an apparatus for converting Vector-generated A2L files into INCA-compatible files, provided in an embodiment of the present invention. Figure 3 This is a schematic diagram of the hardware architecture of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] The A2L file, serving as a crucial data interface between the calibration system and the ECU, contains standard sections such as HEADER, MODULE, MEASUREMENT, and CHARACTERISTIC. At the implementation level, different vendors' tools extend the ASAP2 standard differently: Vector tools embed Vector hardware-specific communication interface configurations, including XCP-on-CAN or XCP-on-Ethernet protocol stack parameters, into the IF_DATA section; while the ETAS toolchain requires matching the interface description of its hardware device to establish a valid connection. Regarding measurement events and calibration scheduling mechanisms, both tools employ triggering strategies based on their own runtime environments, resulting in toolchain dependencies in the event definition syntax. Furthermore, in terms of compiler support, the Vector toolchain may include extended keywords specific to the Tasking or Diab compilers, while the ETAS tool supports custom syntax for its compiler suite.

[0022] Based on this, embodiments of the present invention provide a method and apparatus for converting Vector-generated A2L files into INCA-compatible files, wherein Vector-generated A2L files are compatible with INCA environments that adapt to ETAS hardware interfaces.

[0023] To facilitate understanding of this embodiment, a method for converting a Vector-generated A2L file into an INCA-compatible file, as disclosed in this embodiment of the invention, will first be described in detail. This method is applied to system software deployed in control devices such as host computers.

[0024] Figure 1This is a flowchart illustrating a method for converting a Vector-generated A2L file into an INCA-compatible file, as provided in an embodiment of the present invention.

[0025] like Figure 1 As shown, the method includes the following steps: S102, obtain the A2L file to be converted generated by Vector, the address trace file used to characterize the debugging information during the ECU program operation, and the preset configuration file used to characterize the mapping relationship between Vector and ETAS hardware interface.

[0026] Here, three types of core files input by the user in the development environment are obtained to provide basic data for the subsequent conversion process. Among them, the A2L file to be converted includes at least device parameters, the Vector's preset IF_DATA segment and ECU parameters; the address traceability file includes at least the compiled MAP file or ELF file; and the preset configuration file includes at least a mapping rule library of the correspondence between Vector and ETAS hardware interface.

[0027] S104 uses the ASAM standard syntax to describe rules and extracts key elements from the A2L file to be converted.

[0028] In some embodiments, key elements are extracted from the A2L file to be converted, i.e., the one recognizable by the Vector calibration tool, according to standards that both Vector and ETAS calibration tools must meet; this step S102 includes: Step 1.1: Determine the ASAM standard syntax description rules based on the AML syntax definition; Here, AML syntax is used to define file modules, clearly defining the ASAM standard syntax description rules and providing syntactic support for line-by-line parsing. In other words, the standard that both Vector and ETAS calibration tools must meet is visualized based on the ASAM standard syntax description rules.

[0029] Step 1.2: Identify field information from the A2L file to be converted according to the ASAM standard syntax description rules; The field information includes keywords, block structure, and attributes. For example, the A2L file content generated by Vector can be read word by word based on the text stream using an A2L file reader to identify keywords, block structure, and attributes in the file. Step 1.3: Extract key elements based on field information, including device parameters, IF_DATA segments, and ECU parameters.

[0030] Here, the embodiments of the present invention need to specifically extract three types of key elements: device parameters include basic ECU information and communication interface configuration; the IF_DATA segment includes the key extraction of Vector-specific ETK and CAN interface descriptions (such as hardware identifier VX1160); ECU parameters include calibration quantity, observation quantity, characteristic curve, MAP graph, and record layout (including the virtual address of each parameter, such as the virtual address 0x80001000 of the calibration quantity FuelMap).

[0031] S106, based on the preset configuration file, performs parameter replacement and event conversion on the IF_DATA segment in the A2L file to be converted, and obtains an INCA-compatible IF_DATA segment that is compatible with the ETAS hardware interface. Here, in the scenario of converting A2L files between Vector and the ETAS calibration tool based on the mapping relationship, the conversion of parameters and events in the IF_DATA segment plays a crucial role. This step S106 can be achieved through the following steps, including: Step 2.1: Load the preset configuration file and determine the mapping relationship between Vector and ETAS hardware interfaces; Here, a preset configuration file is loaded to obtain a preset mapping rule base, thereby clarifying the correspondence between Vector and the ETAS hardware interface; Step 2.2: Identify the Vector hardware identifier used for positioning from the ETK block of the IF_DATA segment; Locate the IF_DATAETK block in the VectorA2L file extracted in the aforementioned embodiment and identify the Vector hardware identifier (such as VX1160) within it; the IF_DATA segment is an interface data segment.

[0032] Step 2.3: Based on the mapping relationship, match the ETAS hardware identifier corresponding to the Vector hardware identifier, replace the Vector-specific interface configuration information in the IF_DATA segment with the ASAM parameter corresponding to the ETAS hardware identifier, and adjust the interface configuration data of the IF_DATA segment synchronously. The system queries the mapping relationship rule base, matches the corresponding ETAS hardware identifier (such as ES430) based on the Vector hardware identifier, and replaces the corresponding parameters in the ETAS hardware identifier with ASAM parameters, and synchronously adjusts the interface configuration data (such as address mapping and cache size). It should be noted that core configuration items are generally adjusted in the following ways: Address mapping adjustment: If the interface address range corresponding to the Vector hardware (such as the data receive / send buffer address) differs from that of the ETAS hardware, the Vector address range in the IF_DATA segment needs to be replaced with the address range supported by the ETAS hardware according to the address mapping table preset in the rule base, so as to ensure that the hardware buffer can be accessed accurately during data transmission. Cache size adjustment: Different hardware interfaces have different cache capacities (e.g., Vector hardware cache is 512 bytes, ETAS hardware is 1024 bytes). The cache size parameter in the IF_DATA segment needs to be adjusted according to the ETAS hardware cache specification in the rule base to avoid data loss or transmission failure due to cache mismatch. Other interface parameter adjustments: Based on the rule base configuration, synchronously correct communication baud rate, frame format adaptation parameters, hardware interrupt triggering conditions, etc., to ensure that the interface configuration fully meets the operating requirements of ETAS hardware.

[0033] Step 2.4: Convert the measurement events and calibration events in the IF_DATA segment of the A2L file to be converted into an event structure that can be recognized by the INCA scheduling model adapted to the ETAS hardware interface.

[0034] The Vector's measurement event MEASUREMENT_EVENT and calibration event CALIBRATION_EVENT are converted into an event structure that the INCA scheduling model can recognize.

[0035] It is understood that the INCA scheduling model can adapt to, identify, and apply A2L files generated by the ETAS calibration tool. Through the method provided in this embodiment of the invention, the INCA scheduling model can also process A2L files generated by the Vector calibration tool.

[0036] S108, based on the address traceability file, update and verify the physical address of the ECU parameters in the A2L file to be converted; Based on the aforementioned embodiments, in the scenario of converting A2L files between Vector and the ETAS calibration tool, it is also necessary to update and verify the physical address of the ECU parameters in the A2L file to be converted; for example, this step S108 specifically includes: Step 3.1: Load the address traceability file and extract the physical address information corresponding to the simple and complex parameters in the ECU parameters using the built-in parser of the address traceability file; Simple parameters refer to single variables or basic data type parameters with independent structures and no nested levels. No additional offset calculation is required; the physical address can be directly extracted from the address tracing file as the final physical address. Commonly used simple parameters include: scalar / observable quantities of basic data types and independent parameters without any association. Complex parameters refer to parameters that have nested levels or combined structures; the main complex parameters used in common scenarios include: structure type parameters, array type parameters, and nested structure parameters.

[0037] In practical applications, the address tracing file based on the original A2L file can be compiled into a MAP file or ELF file, which can then be used to extract physical address information of different parameter types, including: A. Extract the physical addresses of simple parameters from the ECU program's runtime parameters in the MAP file of the address tracing file using script parsing; The script parses the MAP file to obtain the actual runtime address of the variables. This allows for the extraction of the physical address of simple parameters, such as scalarized / observable values ​​of basic data types: like single integer (int) or floating-point (float) parameters (e.g., the scalarized FuelMap in the documentation, although named a Map, is essentially a single, independently stored parameter, not a nested structure type); and unrelated independent parameters: these parameters do not belong to any complex data structures such as structures or arrays, and their storage addresses are continuous and unique, allowing their physical addresses to be directly located through the address tracing file.

[0038] B. Use the debug_info section to extract the physical base address and structure offset information of global variables from the ELF file of the address tracing file, and calculate the physical address of complex parameters in the ECU parameters.

[0039] Here, the debug_info section of the ELF file can be used to extract the physical address and structure offset information of global variables.

[0040] The physical address of complex parameters cannot be directly extracted. It is necessary to use the base address of the structure / array as a reference and add the offsets of the internal elements to obtain the final address. For example, for structure-type parameters: composite structures composed of multiple member variables (such as engine control parameter structures containing multiple members such as injection pulse width and ignition advance angle), the base address of the entire structure must be extracted first, then the offset of each member variable relative to the base address is extracted, and finally the physical address of each member is calculated. For array-type parameters: arrays containing multiple elements (such as multi-condition calibration arrays), the array itself has a unified base address, and the final physical address of each array element = array base address + offset corresponding to the element index. For nested structure parameters: structures containing substructures, arrays, and other multi-level structures (such as a body control parameter structure containing an air conditioning control substructure), the base address of the outer structure, the offset of the substructure, and the offsets of the internal members must be added to calculate the final physical address.

[0041] Step 3.2: Select the corresponding physical address information based on the parameter type of the ECU parameters and replace the virtual address extracted from the ECU parameters; It can be understood here that, based on the physical address information obtained from the parameter type in the aforementioned embodiments, the virtual address extracted from the ECU parameters is replaced.

[0042] Step 3.3: Verify the boundary validity and data type matching of the updated ECU parameter address.

[0043] To ensure the reliability of subsequent conversion applications, it is also necessary to check the legality of the updated address boundaries (such as whether it is within the ECUFlash address space) and the data type matching to prevent address out-of-bounds or type errors.

[0044] S110, based on a fixed structure template defined by the ASAP2 standard, uses key elements such as device parameters, INCA-compatible IF_DATA sections, and updated ECU parameters to reconstruct and generate an INCA-compatible A2L file that conforms to the ASAP2 standard and is compatible with the ETAS hardware interface.

[0045] Based on the IF_DATA segment determined in the preceding steps and the updated physical address in the ECU parameters, step S110 reconstructs the A2L file generated by the Vector calibration tool, enabling the INCA scheduling model adapted to the ETAS calibration tool to be compatible with this reconstructed A2L file generated by the Vector calibration tool, including: Based on the fixed structure template defined by the ASAP2 standard, the file header, project information and module declaration are filled with the device parameters in the key elements. The hardware interface configuration for ETAS hardware compatibility is completed based on the converted IF_DATA segment. Then, according to the physical address provided by the updated ECU parameters, the INCA compatible A2L file that conforms to the ASAP2 standard and adapts to the ETAS hardware interface is reconstructed in the fixed order of the ASAP2 standard to generate the physical address provided by the updated ECU parameters.

[0046] In the INCA environment, the file generated by the reconstruction is preloaded and verified to confirm that INCA can connect to the ECU and access variables normally based on the file generated by the reconstruction.

[0047] In a preferred embodiment of practical application, the incompatible Vector and ETAS are converted into a format that can be recognized by the ETAS tool based on the mapping relationship between Vector and ETAS. At the same time, the converted A2L file can also be recognized by the Vector tool, providing an efficient and reliable compatibility solution for automotive ECU calibration development. In other words, to solve the compatibility problem of Vector-generated A2L files in INCA, this invention can realize automatic mapping and replacement of IF_DATA segments, dynamic tracking and updating of variable addresses, and automatic verification of converted files.

[0048] In some embodiments, such as Figure 2 As shown, this embodiment of the invention also provides a device 200 for converting Vector-generated A2L files to INCA-compatible files, comprising: The module 201 acquires the A2L file to be converted generated by Vector, the address trace file used to characterize the debugging information during the ECU program's operation, and the preset configuration file used to characterize the mapping relationship between Vector and ETAS hardware interfaces. Extraction module 202 uses ASAM standard syntax description rules to extract key elements from the A2L file to be converted; The conversion module 203, based on the preset configuration file, performs parameter replacement and event conversion on the IF_DATA segment in the A2L file to be converted, to obtain an INCA-compatible IF_DATA segment that is adapted to the ETAS hardware interface; The update module 204 updates and verifies the physical address of the ECU parameters in the A2L file to be converted according to the address tracing file. Reconstruction module 205, based on a fixed structure template defined by the ASAP2 standard, reconstructs and generates an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface, using the device parameters in the key elements, the INCA-compatible IF_DATA segment, and the updated ECU parameters.

[0049] This invention extracts device parameters, IF_DATA segments, and ECU parameters from the A2L file generated by Vector using an AML syntax definition file module and line-by-line parsing technology. Relying on a pre-defined and user-customizable Vector-ETAS hardware interface mapping rule library, it dynamically replaces hardware identifiers in the IF_DATA segment, updates ASAM parameters, and adjusts interface configuration data. It also converts Vector-specific measurement and calibration events into a structure recognizable by the INCA scheduling model. By integrating a MAP / ELF parser, it extracts the physical addresses of variables from the debug_info section of the MAP or ELF file, calculates base addresses and element offsets for complex types such as structures, replaces virtual addresses in the A2L file, and verifies address boundary validity and data type matching. Finally, based on the ASAP2 standard definer, it performs template-based reconstruction, integrates the processing results of each stage to generate a standard-compliant INCA-compatible A2L file, and supports pre-loading verification in the INCA environment. This solution achieves the technical effects of automatic mapping and replacement of IF_DATA segments, dynamic tracking and updating of variable addresses, and automatic verification of converted files. It effectively solves the problems of cumbersome and error-prone traditional manual modification or semi-automatic conversion processes, and provides an automated, high-precision, and configurable compatibility conversion solution, ensuring that the A2L file generated by Vector can be correctly connected to the ECU and access all variables in the INCA tool.

[0050] Figure 3 This is a schematic diagram of the hardware architecture of the electronic device 300 provided in an embodiment of the present invention. See also... Figure 3 As shown, the electronic device 300 includes a machine-readable storage medium 301 and a processor 302, and may also include a non-volatile storage medium 303, a communication interface 304, and a bus 305; wherein the machine-readable storage medium 301, the processor 302, the non-volatile storage medium 303, and the communication interface 304 communicate with each other through the bus 305. The processor 302 can execute the method described in the above embodiments for converting Vector-generated A2L files into INCA-compatible files by reading and executing machine-executable instructions in the machine-readable storage medium 301 for converting A2L files into INCA-compatible files.

[0051] The machine-readable storage medium mentioned in this article can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, etc. For example, machine-readable storage media can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0052] Non-volatile media can be non-volatile memory, flash memory, storage drives (such as hard disk drives), any type of storage disk (such as optical discs, DVDs, etc.), or similar non-volatile storage media, or combinations thereof.

[0053] It is understood that the specific operation methods of each functional module in this embodiment can be referred to the detailed description of the corresponding steps in the above method embodiment, and will not be repeated here.

[0054] The computer-readable storage medium provided in the embodiments of the present invention stores a computer program. When the computer program code is executed, it can implement the method of converting A2L files generated by Vector into INCA-compatible files as described in any of the above embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0055] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0056] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms installation, connection, and linking should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0057] In the description of this invention, it should be noted that the terms center, up, down, left, right, vertical, horizontal, inner, and outer, indicating orientation or positional relationships, are based on the orientation or positional relationships shown in the accompanying drawings and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms first, second, and third are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0058] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit them. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the scope of the technology disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention.

Claims

1. A method for converting A2L files generated by Vector into INCA-compatible files, characterized in that, include: Obtain the A2L file to be converted generated by Vector, the address trace file used to characterize the debugging information during the ECU program operation, and the preset configuration file used to characterize the mapping relationship between Vector and ETAS hardware interface; The ASAM standard syntax description rules are used to extract key elements from the A2L file to be converted; Based on the preset configuration file, the IF_DATA segment in the A2L file to be converted is replaced with parameters and converted with events to obtain an INCA-compatible IF_DATA segment that is adapted to the ETAS hardware interface. Based on the address tracing file, the ECU parameters in the A2L file to be converted are updated and verified using physical addresses; Based on the fixed structure template defined by the ASAP2 standard, the device parameters in the key elements, the INCA-compatible IF_DATA section, and the updated ECU parameters are reconstructed to generate an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface.

2. The method according to claim 1, characterized in that, The steps for extracting key elements from the A2L file to be converted, using ASAM standard syntax description rules, include: The ASAM standard syntax description rules are determined based on the AML syntax definition; According to the ASAM standard syntax description rules, field information is identified from the A2L file to be converted; wherein, the field information includes keywords, block structure, and attributes; Based on the field information, key elements including device parameters, IF_DATA segments, and ECU parameters are extracted.

3. The method according to claim 1, characterized in that, Based on the preset configuration file, the steps of replacing parameters and converting events in the IF_DATA segment of the A2L file to be converted to obtain an INCA-compatible IF_DATA segment adapted to the ETAS hardware interface include: Load the preset configuration file to determine the mapping relationship between Vector and ETAS hardware interfaces; Identify the Vector hardware identifier used for positioning from the ETK block of the IF_DATA segment; Based on the mapping relationship, match the ETAS hardware identifier corresponding to the Vector hardware identifier, replace the Vector-specific interface configuration information in the IF_DATA segment with the ASAM parameter corresponding to the ETAS hardware identifier, and simultaneously adjust the interface configuration data of the IF_DATA segment. The measurement and calibration events in the IF_DATA segment of the A2L file to be converted are transformed into an event structure recognizable by the INCA scheduling model adapted to the ETAS hardware interface.

4. The method according to claim 1, characterized in that, The steps of updating and verifying the physical address of the ECU parameters in the A2L file to be converted based on the address tracing file include: Load the address traceability file and extract the physical address information corresponding to the simple and complex parameters in the ECU parameters using the parser built into the address traceability file; Based on the parameter type of the ECU parameters, the corresponding physical address information is selected to replace the virtual address extracted from the ECU parameters; Verify the boundary validity and data type matching of the updated address of the ECU parameters.

5. The method according to claim 4, characterized in that, The steps of loading the address traceability file and extracting the physical address information corresponding to the simple and complex parameters in the ECU parameters using the parser built into the address traceability file include: The physical addresses of simple parameters in the ECU parameters during ECU program runtime are extracted from the MAP file of the address tracing file by the script; The physical base address and structure offset information of global variables are extracted from the ELF file of the address tracing file using the debug_info section, and the physical address of complex parameters in the ECU parameters is calculated.

6. The method according to claim 1, characterized in that, Based on the fixed structure template defined by the ASAP2 standard, the steps of reconstructing and generating an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface, including the device parameters in the key elements, the INCA-compatible IF_DATA section, and the updated ECU parameters, include: Based on the fixed structure template defined by the ASAP2 standard, the device parameters in the key elements are used to fill the file header, project information and module declaration. The hardware interface configuration for ETAS hardware compatibility is completed based on the converted IF_DATA segment. Then, according to the physical address provided by the updated ECU parameters, the INCA compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface is reconstructed in the fixed order of the ASAP2 standard.

7. The method according to claim 1, characterized in that, The A2L file to be converted includes at least device parameters, the Vector's preset IF_DATA segment, and ECU parameters; the address tracing file includes at least a compiled MAP file or ELF file; and the preset configuration file includes at least a mapping rule library for the correspondence between Vector and ETAS hardware interfaces.

8. An apparatus for converting Vector-generated A2L files into INCA-compatible files, characterized in that, include: The module acquires the A2L file to be converted generated by Vector, the address trace file used to characterize the debugging information during the ECU program's operation, and the preset configuration file used to characterize the mapping relationship between Vector and ETAS hardware interfaces. The extraction module uses ASAM standard syntax to describe rules and extracts key elements from the A2L file to be converted. The conversion module, based on the preset configuration file, performs parameter replacement and event conversion on the IF_DATA segment in the A2L file to be converted, to obtain an INCA-compatible IF_DATA segment that is adapted to the ETAS hardware interface; The update module updates and verifies the physical address of the ECU parameters in the A2L file to be converted, based on the address tracing file. The reconstruction module, based on a fixed structure template defined by the ASAP2 standard, uses the device parameters in the key elements, the INCA-compatible IF_DATA segment, and the updated ECU parameters to reconstruct and generate an INCA-compatible A2L file that conforms to the ASAP2 standard and is adapted to the ETAS hardware interface.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 7.

10. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores machine-executable instructions that, when invoked and executed by a processor, cause the processor to perform the steps of the method according to any one of claims 1 to 7.

Images