WO2018188222A1

WO2018188222A1 - A2l file merging method and device

Info

Publication number: WO2018188222A1
Application number: PCT/CN2017/093167
Authority: WO
Inventors: 钟韦; 张坤明
Original assignee: 宁德时代新能源科技股份有限公司
Priority date: 2017-04-14
Filing date: 2017-07-17
Publication date: 2018-10-18
Also published as: CN108733674B; CN108733674A

Abstract

Provided are an A2L file merging method and device. The method comprises: parsing each A2L file to obtain an A2L object (S101); updating address information of the A2L object according to an identifier of the A2L object (S102); and merging the A2L object whose the address information is updated to obtain a target A2L file (S103). Therefore, the problem of merging A2L files in the prior art can be solved, and the cost is saved.

Description

A2L file merging method and device

The present application claims priority to Chinese Patent Application No. PCT Application No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. in.

Technical field

The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for merging A2L files.

Background technique

At present, in the development of automotive software, the software of the automotive electronic control unit needs to calibrate and measure the data, and the calibration and measurement data is generally stored in the AASAM MCD-2MC format, and the file name ends with .a2l, referred to as the A2L file. . However, in the car software development process, multiple A2L files are usually generated, and only one A2L file can be input when data calibration. Therefore, it is very important to merge A2L files.

In the prior art, Vector's A2L file merge tool is generally used, but there is no disclosed A2L file merge method.

Application content

In view of this, the present application provides an A2L file merging method and apparatus for solving the problem of merging A2L files in the prior art.

In one aspect, the application provides a method for merging A2L files, including:

Parse each A2L file to get an A2L object;

Updating address information of the A2L object according to the identifier of the A2L object;

The A2L objects after updating the address information are merged to obtain a target A2L file.

The foregoing aspect and any possible implementation manner further provide an implementation manner of parsing each A2L file to obtain an A2L object, including:

Read the data in each A2L file line by line;

Identify the attribute type of the A2L object corresponding to each row of data;

The data of each row is parsed by an analysis method corresponding to the attribute type of the A2L object to obtain an A2L object.

The foregoing aspect, and any possible implementation manner, further provide an implementation manner, before the address information of the A2L object is updated, the method further includes:

Extracting identifier and address information of the A2L object in the address information file;

An address information list is generated based on the identifier and address information of the A2L object in the address information file.

The aspect as described above and any possible implementation manner further provide an implementation manner of updating address information of the A2L object, including:

Detecting, in the address information list, whether there is a target identifier that is the same as an identifier of at least one of the A2L objects;

The address information of the A2L object in which the target identifier exists in the address information list is replaced with the address information corresponding to the target identifier.

The aspect as described above and any possible implementation manner further provide an implementation manner of merging A2L objects after updating the address information, including:

Performing identifier conflict processing on the A2L object after the update address information;

The A2L object processed by the identifier conflict is output to an A2L file according to the generation format of the A2L file, and the target A2L file is obtained.

In another aspect, the application provides an A2L file merging device, including:

An analysis unit for parsing each A2L file to obtain an A2L object;

An update unit, configured to update address information of the A2L object according to the identifier of the A2L object;

The merging unit is configured to merge the A2L objects after updating the address information to obtain a target A2L file.

The above-mentioned aspect and any possible implementation manner further provide an implementation manner, where the parsing unit is specifically configured to:

Read the data in each A2L file line by line;

The above-mentioned aspect and any possible implementation manner further provide an implementation manner, the device further includes:

An extracting unit, configured to extract identifiers and address information of the A2L object in the address information file;

And a generating unit, configured to generate an address information list according to the identifier and the address information of the A2L object in the address information file.

The above-mentioned aspect and any possible implementation manner further provide an implementation manner, where the update unit is specifically configured to:

The foregoing aspect, and any possible implementation manner, further provide an implementation manner, where the merging unit is specifically configured to:

One of the above technical solutions has the following beneficial effects:

In the present application, an A2L object is obtained by parsing and splitting each A2L file, and then the address information of these A2L files is updated, and then these A2L objects are combined to obtain a target A2L file; In the present application, a plurality of A2L files are merged into one target A2L file by parsing and splitting the generated first, and the target A2L file contains most of the A2L objects in the A2L files, and is generated and output at this time. The target A2L file can meet the requirement of calibrating the data in the A2L file in the process of developing the automobile software, and solves the problem of merging the A2L file in the prior art, thereby saving the cost.

DRAWINGS

In order to more clearly illustrate the technical solutions of the present application, the drawings to be used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application, which are common to the art. For the technicians, don’t pay Other drawings can also be obtained from these drawings on the premise of creative labor.

1 is a schematic flow chart of a method for merging an A2L file provided by the present application;

2 is a schematic flow chart of parsing an A2L file in the present application;

3 is a schematic flowchart of updating address information of an A2L object in the present application;

4 is a schematic flowchart of performing identifier conflict processing on an A2L object in the present application;

FIG. 5 is a functional block diagram of an A2L file merging apparatus provided by the present application.

detailed description

In order to better understand the technical solutions of the present application, the present application will be described in detail below with reference to the accompanying drawings.

It should be understood that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

The terminology used in the present application is for the purpose of describing particular embodiments, and is not intended to be limiting. The singular forms "a", "the" and "the"

It should be understood that the term "and/or" as used herein is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, while A and B, there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining" or "in response to detecting." Similarly, depending on the context, the phrase "if determined" or "if detected (conditions or events stated)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event) "Time" or "in response to a test (condition or event stated)".

In view of the problem of A2L file merging existing in the prior art, the present application provides the following solution: by parsing each A2L object in each A2L file, and then merging these A2L objects according to the format, generating and outputting A target A2L file.

Under the guidance of this idea, the embodiment of the solution provides the following feasible implementations.

Embodiment 1

This application presents a method for merging A2L files.

Specifically, please refer to FIG. 1 , which is a schematic flowchart of a method for merging A2L files provided by the present application. As shown in FIG. 1 , the method includes the following steps:

S101. Parse each A2L file to obtain an A2L object.

S102. Update the address information of the A2L object according to the identifier of the A2L object.

S103: Combine the A2L objects after updating the address information to obtain a target A2L file.

Specifically, the document structure in the A2L file may include: a document header, an A2L object, and a document end. The document header contains the version information of the ASAM used by the A2L file, the item name corresponding to the A2L file, and the like, and the end of the document corresponds to the header of the document, and the end of the document needs to be marked at the end of the document.

Specifically, the A2L objects are classified according to the data type, and can be roughly classified into: calibrating A2L objects and measuring A2L objects. The data corresponding to the A2L object is calibrated, and the data corresponding to the A2L object is measured.

Specifically, the attribute types of the A2L object may include, but are not limited to, A2ML, IF_DATA, MOD_COMMON, MOD_PAR, MEASUREMENT, CHARACTERISTIC, COMPU_METHOD, RECORD_LAYOUT, GROUP, AXIS_PTS. For convenience of description, the A2L object of the A2ML attribute type is simply referred to as the A2ML object, and the A2L objects of the remaining attribute types are similarly processed.

Among them, A2ML is a format for describing data of a special interface (an interface is a way of communicating with an external device). IF_DATA is data used to describe a particular interface. MOD_COMMON is used to describe the storage length and storage of data variables in A2L files. MOD_PAR is used to describe which data is stored for which devices. MEASUREMENT is used to describe the attributes of the object being measured. CHARACTERISTIC is used to describe the properties of the calibration object. COMPU_METHOD is used to describe the calculation method of converting one value to another. RECORD_LAYOUT is used to describe the layout object of the variable's data structure in memory. GROUP is used to classify calibration and measurement objects. AXIS_PTS is used to describe the parameters of points in the coordinate space.

In the present application, it is considered that the above A2L objects have no clear order in the A2L file, and the number of A2L objects of each attribute type is also uncertain except for the A2L objects of the three attribute types A2ML, MOD_COMMON, and MOD_PAR. Based on this, when S101 is executed, the A2L file can be parsed in a sequential parsing mode.

In a specific implementation process, parsing each A2L file, the process of obtaining the A2L object may include: reading the data in each A2L file line by line, and then identifying the attribute type of the A2L object corresponding to each row of data, after that, The data of each row is parsed by an analysis method corresponding to the attribute type of the A2L object to obtain an A2L object.

Specifically, please refer to FIG. 2 , which is a schematic flowchart of parsing an A2L file in the present application. As shown in FIG. 2 , the data in the A2L file is read row by row, and when a row of data is read, the row is sequentially determined. Whether the data is an A2ML object, a MOD_COMMON object, a MEASURE object, a CHARACTERISTIC object, an IF_DATA object, a COMPU_METHOD object, an AXIX_PTS object, a RECORD_LAYOUT object, a GROUP object, a FUNCTION object, a MODULE object, when the judgment process at any step is YES, it is determined The attribute type of the data row, and thus, the A2L object can be obtained by parsing the data according to the parsing method corresponding to the attribute type. And after each parsing process is finished, it is judged whether or not the end of the A2L file is reached. When the judgment is no, the judgment of the next row of data is continued; when the judgment is YES, the process ends.

Thus, by reading in line by line and judging line by line, until the end of the A2L file is read, all A2L objects of the A2L file can be parsed.

In a specific implementation process, it is considered that the A2L object in the A2L file generally has an identifier, and the identifier is equivalent to the identity of each object. Therefore, the attribute type of each row of data can be determined according to the identifier. Specifically, when it is determined that one row of data has an identifier corresponding to any one of the attribute types, the attribute type of the row of data may be determined.

In a specific implementation, the identifier can be the name of an A2L object.

However, the objects of the three attribute types A2ML, MOD_COMMON, and MOD_PAR have one and only one type in one A2L file, and these three attribute types are not Have an identifier.

The content specifically included in the A2L object obtained by the analysis is not particularly limited. For example, the data obtained by parsing the A2L object of the attribute types COMPU_METHOD, RECORD_LAYOUT, and GROUP includes the identifier attribute. The data parsed by the MEASUREMENT object includes the identifier Name, the data type Datatype, the conversion method Conversion, the precision Accuracy, the numerical maximum value LowerLimit, the numerical minimum value UpperLimit, and the ECU memory address information. The data parsed by the CHARACTERISTIC object includes the name Name, the annotation LongIdentifier, the type Type, and the address information Address.

In the present application, it is considered that the address information of the partial A2L object may be acquired in S101, but whether the address information is correct or not cannot be determined. Therefore, before the merging, S102 needs to be executed, so that the merged target A2L file is obtained. The address information of each A2L object is correct.

In the present application, the address information of the A2L object is updated based on the identifier of the A2L object. Based on this, there are various implementations when S102 is executed. In order to explain the solution more specifically, the present application gives the following implementations.

Before executing S102, the identifier and address information of the A2L object in the address information file (map file) are extracted in advance, and the address information list PLIST is generated based on the identifier and address information of the A2L object in the extracted map file.

Specifically, the address information of the calibration A2L object and the address information of the measured A2L object in the A2L file are stored in the map file, and the map file may also contain multiple address information types.

When extracting the address information in the map file, it can also be implemented by the line-by-line reading judgment. Specifically, the address information in the A2L file generally starts with ".rodata", ".bss", ".vletext", ".data", ".calib", ".app_const", ".app_data", and each line There are only 3 data segments (composed of consecutive characters). Based on this, the data in the map file can be read line by line. If there is any row of data, it is ".rodata", ".bss", ".vletext", ".data", ".calib", ".app_const". ", ".app_data" begins, and the data segment of the line (composed of consecutive characters) has only three, then the address information of the A2L object contained in the data can be extracted. Extract the identifier of the A2L object The method is as described above, and will not be described again here. Then, after the identifier and the address information of the A2L object are extracted, the identifier of the A2L object and the address information are simultaneously stored in the address information list PLIST.

It should be noted that the A2L object in the map file may be the same as the A2L object obtained in S101, and may be different. For example, the A2L object acquired in S101 is identical to the A2L object in the map file. Alternatively, for example, the A2L object acquired in S101 may be included in the A2L object in the map file.

In the present application, by detecting whether there is a target identifier identical to the identifier of the at least one A2L object in the address information list PLIST, and then replacing the address information of the A2L object in which the target identifier exists in the address information list PLIST with the target identifier The address information corresponding to the address is not updated for the address information of other A2L objects that do not have the target identifier.

Based on this, when S102 is executed, when the address information is updated for any one of the A2L objects, it is only necessary to detect whether or not the same target identifier as the identifier of the A2L object exists in the generated address information list PLIST. Therefore, when the target identifier exists in the address information list PLIST, the address information of the A2L object is replaced with the address information corresponding to the target identifier to update the acquired address information of the A2L object.

There are also a variety of implementations that can be implemented in the implementation of this step. For example, it is possible to compare the address information corresponding to the target identifier with the address information of the A2L object, and if the two do not match, replace the address information of the A2L object with the address information corresponding to the target identifier. Alternatively, for example, the address information of the A2L object may be directly replaced with the address information corresponding to the target identifier by determining the presence of the target identifier in the address information list without determining the comparison process.

On the other hand, if the target identifier of an A2L object does not exist in the address information list, the address information of the A2L object is not updated.

In the above manner, the address information may be updated one by one for the plurality of A2L objects acquired in S101, or may be batch processed. This application does not specifically limit this. It should be noted that when the address information is updated in batches of multiple A2L objects acquired in S101, the A2L object acquired in S101 may be There are many, based on this, when updating the address information of these A2L objects in batches, each A2L object corresponds to a different target identifier. When there is a target identifier corresponding to any A2L object, only the A2L object needs to be The address information can be updated.

The above is to update the address information according to the manner in which the acquired A2L object queries the target identifier in the address information list PLIST; or, conversely, the acquired address information of the A2L object based on the address information list. Update.

In a specific implementation process, the A2L object obtained in S101 can be stored into different linked lists according to the data type according to the data type of the A2L object. Specifically, two linked lists can be established, and one linked list is a CLIST linked list. For storing all the calibrated A2L objects, the other linked list is the MLIST linked list, which is used to store all measured A2L objects. Thereafter, the address information is updated separately for each linked list.

Specifically, please refer to FIG. 3 , which is a schematic flowchart of updating address information of an A2L object in the present application. As shown in Figure 3, this step includes:

S301, creating a hash table HC and HM.

Among them, the HC is used to store the calibration A2L object, and the HM is used to store the measured A2L object.

S302, the calibration A2L object in the CLIST is stored in the HC, and the measurement A2L object in the MLIST is stored in the HM.

S303. The iterator selects the first element of the PLIST.

S304. Query whether there is an A2L object having the same identifier as the element in the HC; if yes, execute S305; if not, execute S306.

S305. Update the address information of the A2L object in the HC that is the same as the identifier of the element.

S306. Query whether there is an A2L object with the same identifier of the element in the HM; if yes, execute S307; if not, execute S308.

S307. Update the address information of the A2L object in the HM that is the same as the identifier of the element.

S308, determining whether the current element is empty; if yes, the loop ends, executing S310; if not, the loop is not finished, and executing S309.

S309, the iterator selects the next element in the PLIST.

S310, clear the data in the CLIST and the MLIST, and store the data of the HC in the CLIST, and store the data of the MC in the MLIST.

The above is a specific implementation manner of updating the address information of A2L in S102, and is not intended to limit the present application. Moreover, in the process of actually implementing S102, there may be other implementation manners.

For example, by extracting the address information in the map file as described above, it is also possible to extract the address information corresponding to the identifier of the A2L object obtained in S101 directly in the map file without comparison. The update of the address information of the A2L object is implemented, and details are not described herein.

In the present application, in consideration of obtaining a plurality of A2L objects in a plurality of A2L files, there may be a case where a large number of names are duplicated in these A2L objects, that is, a case where the identifiers are repeated. Moreover, the repetition of such identifiers exists not only between A2L objects of the same type, but also between identifiers of different types of A2L objects, including attribute types and data types.

Based on this, in the process of executing S103, the method may include two steps: performing an identifier conflict processing on the A2L object after updating the address information, and then outputting the A2L object processed by the identifier conflict to the generated format of the A2L file to In an A2L file, you can get the target A2L file.

Hereinafter, the identifier conflict processing for the case where the identifiers existing between the A2L objects of the same attribute type are repeated will be specifically described as an example.

Please refer to FIG. 4 , which is a schematic flowchart of identifier conflict processing for an A2L object in the present application. As shown in Figure 4, this step includes:

S401. Create an output linked list and an identifier storage hash table H for each attribute type A2L object, and the output linked list is used to store the A2L object.

S402. Query whether each of the A2L objects parsed in each A2L file is in existence.

S403. Store the A2L object existing in H into an output linked list of the attribute type, and store the identifier of the A2L object into H.

It should be noted that, in S402, if an A2L object does not exist in H, it is not necessary to add the A2L object to the output link table of the A2L object of the attribute type.

Based on the above steps, an output linked list of A2L objects of each attribute type can be obtained, and there is no case where the identifiers are duplicated in the output linked list. Based on these output linked lists, identifier conflicts between different attribute types can be further processed, and will not be described here.

The format of the target A2L file may be preset according to actual needs, which is not specifically limited in this application.

In a specific implementation process, the target A2L file can be obtained by outputting to the A2L file according to the document header, A2ML, AXIS_PTS, IF_DATA, MOD_COMMON, MOD_PAR, MEASUREMENT, CHARACTERISTIC, COMPU_METHOD, RECORD_LAYOUT, GROUP, and the end of the document.

The technical solution of the present application has the following beneficial effects:

Embodiment 2

Based on the A2L file merging method provided in the first embodiment, the present application further provides an apparatus embodiment for implementing the steps and methods in the foregoing method embodiments.

Please refer to FIG. 5 , which is a functional block diagram of an A2L file merging apparatus provided by the present application. As shown in Figure 5, the device includes:

The parsing unit 51 is configured to parse each A2L file to obtain an A2L object;

The updating unit 52 is configured to update address information of the A2L object according to the identifier of the A2L object;

The merging unit 53 is configured to merge the A2L objects after updating the address information to obtain a target A2L file.

Specifically, in this application, the parsing unit 51 is specifically configured to:

Read the data in each A2L file line by line;

The analysis method corresponding to the attribute type of the A2L object is used to parse each line of data to obtain an A2L object.

In a specific implementation process, the device further includes:

The extracting unit 54 is configured to extract identifiers and address information of the A2L object in the address information file;

The generating unit 55 is configured to generate an address information list according to the identifier and the address information of the A2L object in the address information file.

At this time, the updating unit 52 is specifically configured to:

Detecting whether there is a target identifier in the address information list that is identical to the identifier of the at least one of the A2L objects;

In the present application, the merging unit 53 is specifically configured to:

The A2L object after the address information is updated is subjected to identifier conflict processing;

Since the units in this embodiment can perform the method shown in FIG. 1, and the parts not described in detail in this embodiment, reference may be made to the related description of FIG.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined. Or it can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods of the various embodiments of the present application. Part of the steps. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

The above is only the preferred embodiment of the present application, and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc., which are made within the spirit and principles of the present application, should be included in the present application. Within the scope of protection.

Claims

An A2L file merging method, the method comprising:

Parse each A2L file to get an A2L object;

Updating address information of the A2L object according to the identifier of the A2L object;

The A2L objects after updating the address information are merged to obtain a target A2L file.
The method according to claim 1, wherein each A2L file is parsed to obtain an A2L object, including:

Read the data in each A2L file line by line;

Identify the attribute type of the A2L object corresponding to each row of data;

The data of each row is parsed by an analysis method corresponding to the attribute type of the A2L object to obtain an A2L object.
The method according to claim 1, wherein before updating the address information of the A2L object, the method further includes:

Extracting identifier and address information of the A2L object in the address information file;

An address information list is generated based on the identifier and address information of the A2L object in the address information file.
The method according to claim 3, wherein the updating the address information of the A2L object comprises:

Detecting, in the address information list, whether there is a target identifier that is the same as an identifier of at least one of the A2L objects;

The address information of the A2L object in which the target identifier exists in the address information list is replaced with the address information corresponding to the target identifier.
The method according to claim 1, wherein the A2L objects after updating the address information are merged, including:

Performing identifier conflict processing on the A2L object after the update address information;

The A2L object processed by the identifier conflict is output to an A2L file according to the generation format of the A2L file, and the target A2L file is obtained.
An A2L file merging device, characterized in that the device comprises:

An analysis unit for parsing each A2L file to obtain an A2L object;

An update unit, configured to update address information of the A2L object according to the identifier of the A2L object;

The merging unit is configured to merge the A2L objects after updating the address information to obtain a target A2L file.
The device according to claim 6, wherein the parsing unit is specifically configured to:

Read the data in each A2L file line by line;

Identify the attribute type of the A2L object corresponding to each row of data;

The data of each row is parsed by an analysis method corresponding to the attribute type of the A2L object to obtain an A2L object.
The device according to claim 6, wherein the device further comprises:

An extracting unit, configured to extract identifiers and address information of the A2L object in the address information file;

And a generating unit, configured to generate an address information list according to the identifier and the address information of the A2L object in the address information file.
The device according to claim 8, wherein the updating unit is specifically configured to:

Detecting, in the address information list, whether there is a target identifier that is the same as an identifier of at least one of the A2L objects;

The address information of the A2L object in which the target identifier exists in the address information list is replaced with the address information corresponding to the target identifier.
The device according to claim 6, wherein the merging unit is specifically configured to:

Performing identifier conflict processing on the A2L object after the update address information;

The A2L object processed by the identifier conflict is output to an A2L file according to the generation format of the A2L file, and the target A2L file is obtained.