Application variable data calibration method and related device
By uniformly writing variable information description files and generating calibration instructions, the problem that each application software on the SoC chip needs to be equipped with a specific A2L file is solved, and efficient management and simplified maintenance of variable data are achieved.
Patent Information
- Application Number
- CN202510488223.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-17
- Publication Date
- 2025-08-08
AI Technical Summary
On SoC chips, the prior art requires each application software to be equipped with a specific A2L file, resulting in high complexity in the management and maintenance of variable information description files.
By writing the variable description information of each target application in advance to the variable information description file, a calibration instruction is generated and parsed to determine the target position in shared memory, and perform calibration measurements. Only update the file can manage the variable data of all target applications.
It simplifies the management and maintenance complexity of variable information description files, improves the calibration efficiency and measurement capabilities of multiple target applications, and reduces system complexity and communication burden.
Smart Images

Figure CN120447969A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to an application variable data calibration method and related devices. Background Art
[0002] XCP (Universal Measurement and Calibration Protocol) is a standard protocol for calibrating and measuring parameters in vehicle electronic control units (ECUs). It is widely used in the development and testing of vehicle ECUs. Current ECU chips have evolved from traditional microcontroller units (MCUs) to more powerful system-on-chips (SoCs). Designed for MCUs, the Universal Measurement and Calibration Protocol (XCP) calibrates variable addresses at fixed memory addresses. However, application software on SoCs uses dynamically changeable virtual addresses. To calibrate application software on SoCs, variable addresses are represented by the application's base address plus an offset. The memory addresses of the variables in the original A2L file are replaced with the application's offset address. This design requires each application to have a dedicated A2L file to isolate and manage data.
[0003] Although the current XCP calibration implementation method for application software in SoC (System on Chip) has been adjusted for the dynamically variable addresses of SoC chips, it may still have the following defects: each application software requires a specific A2L file, which makes the management and maintenance of A2L files complicated. Summary of the Invention
[0004] In view of the above problems, this application provides an application variable data calibration method and related devices to reduce the management complexity of variables corresponding to multiple application software. The specific solution is as follows:
[0005] A method for calibrating application variable data, comprising:
[0006] Obtaining a calibration instruction sent by a calibration tool, where the calibration instruction is an instruction generated based on variable description information of a target application stored in a variable information description file;
[0007] Parsing the calibration instruction, and determining a target location of the shared memory corresponding to the target application to be calibrated based on the parsing result;
[0008] The target position is calibrated and measured based on the calibration instruction, and an instruction execution result is generated.
[0009] Optionally, in the above-mentioned application variable data calibration method, before determining the shared memory corresponding to the target application to be calibrated based on the analysis result, the method further includes:
[0010] Determining the identity information of the target application based on the parsing result of the calibration instruction;
[0011] Determining whether there is a shared memory corresponding to the target application based on the identity information;
[0012] When there is a shared memory corresponding to the target application, the shared memory is calibrated and measured based on the variable description information of the target application stored in the variable information description file, and subsequent steps are performed.
[0013] Optionally, in the above-mentioned application variable data calibration method, determining the shared memory corresponding to the target application to be calibrated based on the analysis result includes:
[0014] Obtaining an address and a size contained in the calibration instruction based on the parsing result, wherein the address refers to an address offset of the variable data to be accessed or operated in the shared memory, and the size refers to a data length of the variable data to be accessed or operated;
[0015] The shared memory corresponding to the target application that needs to be calibrated is determined based on the address and size.
[0016] Optionally, in the above-mentioned application variable data calibration method, after calibrating and measuring the shared memory based on the variable description information of the target application stored in the variable information description file, the method further includes:
[0017] Monitor the target application's connection requests;
[0018] establishing shared memory communication of the target application based on the connection request;
[0019] The variable data in the shared memory corresponding to the target application and the variable data inside the target application are synchronously updated.
[0020] Optionally, in the above-mentioned application variable data calibration method, synchronously updating the variable data in the shared memory corresponding to the target application and the variable data inside the target application includes:
[0021] Determining whether the value of the variable data within the target application has changed, and if so, updating the variable data in the shared memory corresponding to the target application based on the variable data within the target application;
[0022] It is determined whether the value of the variable data in the shared memory corresponding to the target application changes, and when it changes, the variable data inside the target application is updated based on the variable data in the shared memory corresponding to the target application.
[0023] Optionally, in the above-mentioned application variable data calibration method, determining whether the value of the variable data in the shared memory corresponding to the target application has changed, and when the value has changed, updating the variable data within the target application based on the variable data in the shared memory corresponding to the target application includes:
[0024] Determine whether the value of the variable data in the shared memory corresponding to each target application has changed;
[0025] When there is changed variable data, determining whether the target application corresponding to the variable data has established shared memory communication with the shared memory;
[0026] When shared memory communication is not established, generating and storing prompt information corresponding to the target application;
[0027] When it is detected that the shared memory communication of the target application is established, determining whether there is prompt information corresponding to the target application;
[0028] When the prompt information exists, the variable data inside the target application is updated based on the variable data in the shared memory corresponding to the target application, and the prompt information corresponding to the target application is deleted.
[0029] An ECU calibration device, comprising:
[0030] A data acquisition unit, configured to obtain a calibration instruction sent by a calibration tool, wherein the calibration instruction is an instruction generated based on variable description information of a target application stored in a variable information description file;
[0031] A parsing unit, configured to parse the calibration instruction and determine a target location of the shared memory corresponding to the target application to be calibrated based on the parsing result;
[0032] A calibration unit is used to calibrate and measure the target position based on the calibration instruction and generate an instruction execution result.
[0033] An electronic device comprising at least one processing device and a storage device connected to the processing device, wherein:
[0034] The storage device is used to store computer programs;
[0035] The processing device is used to execute the computer program so that the electronic device can implement the application variable data calibration method as described in any one of the above.
[0036] A computer storage medium carries one or more computer programs, which, when executed by an electronic device, can enable the electronic device to implement the application variable data calibration method as described in any one of the above.
[0037] By means of the above-mentioned technical solution, the above-mentioned solution provided by the present application pre-writes the variable description information of each target application into a variable information description file. When the target application needs to be calibrated, a calibration instruction is generated based on the description information of each variable of the target application stored in the variable information description file. When the gateway applying this method obtains the calibration instruction, it parses the calibration instruction, determines the target position of each variable in the shared memory based on the parsing result, and then calibrates and measures the target position based on the parsing result. Therefore, only one variable information description file needs to be configured to complete the maintenance of the variable data of all target applications. When multiple target applications need to be updated, only the variable information description file needs to be updated, which simplifies the complexity of the management and maintenance of the variable information description file. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] The above and other features, advantages, and aspects of the various embodiments disclosed in this application will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.
[0039] Figure 1 A flow chart of the variable data calibration method disclosed in the embodiment of the present application;
[0040] Figure 2 A schematic diagram of a calibration scenario of the variable data calibration method disclosed in an embodiment of the present application;
[0041] Figure 3 A schematic diagram of the structure of the shared memory in the variable data calibration method disclosed in the embodiment of the present application;
[0042] Figure 4 A flow chart of a variable data calibration method disclosed in another embodiment of the present application;
[0043] Figure 5 A schematic structural diagram of a variable data calibration device disclosed in an embodiment of the present application;
[0044] Figure 6 This is a structural diagram of an electronic device for implementing a variable data calibration method disclosed in an embodiment of the present application. DETAILED DESCRIPTION
[0045] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.
[0046] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0047] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.
[0048] This application can be applied in the field of data processing. Taking the automotive scenario as an example, the following will introduce multiple application scenarios that have been implemented in products.
[0049] First, the application scenario of this application is introduced.
[0050] This application can be applied to, but is not limited to, applications with data processing capabilities or cloud services provided by cloud-side servers. The following describes each of these:
[0051] In order to solve the above problems raised in the background technology, the embodiment of the present application provides an application variable data calibration method. The application variable data calibration method of the embodiment of the present application is described in detail below with reference to the accompanying drawings.
[0052] Reference Figure 1 , Figure 1 The process diagram of a method for calibrating variable data provided in an embodiment of the present application is as follows: Figure 1 As shown, a data processing method provided in an embodiment of the present application may include steps S401 to S403, and these steps are described in detail below.
[0053] Step S101: Acquire a calibration instruction sent by a calibration tool.
[0054] In the technical solution disclosed in the embodiment of the present application, the application variable data calibration method can be configured in a gateway, which can be an XCP gateway. The gateway is integrated into the target object of the required service. The target object has multiple target applications for variable monitoring. The target object can be an ECU, MCU, VCU or other device. The calibration measurement of the variable data corresponding to each target application in the target object is realized through the gateway.
[0055] For details, see Figure 2 The XCP gateway configuration tool can be used to configure the variable description information of each target application and store the variable description information in a variable information description file. In this embodiment, the variable information description file can be an A2L file. The A2L file is a structured ASCII text file based on the ASAP2 standard, which is used to describe the calibration and measurement data of the electronic device (such as the automotive electronic control unit (ECU)) to which this method is applied. Then, the variable information description file is imported into the calibration tool. At the same time, the XCP gateway configuration tool is also needed to generate the application software engineering (such as Figure 2 This project includes the settings of the communication layer and protocol layer parameters of the XCP gateway, as well as the application software ID (for example Figure 2 In the example, application 1 ID=1, application 2 ID=2, application n ID=n), variable type and size, etc. Among them, the XCP gateway configuration tool specifies the layout of variables in the application in shared memory and generates skeleton code. The application developed based on this skeleton code will have the function of communicating with the XCP gateway and perform calibration measurements according to the agreed memory layout to communicate and exchange data with the ECU (engine control unit). The project file needs to include header files and source files for declaring and defining variables, as well as IPC communication related interfaces. Users can develop based on existing projects and deploy the compiled binary code files to the target object ( Figure 2 The target object shown is ECU), and the deployment of each target application in the target object is completed.
[0056] When the user needs to calibrate the shared memory corresponding to each target application, the user can use the calibration tool to generate calibration instructions based on the variable address information corresponding to these target applications in the A2L file, and then use the calibration tool to send the calibration instructions to the gateway that implements this method. If the number of calibration instructions generated at the same time is greater than 1, each of the calibration instructions can be sent to the gateway simultaneously or in sequence. Specifically, when the calibration tool starts calibration, it first needs to parse the variable information description file to obtain detailed information on all relevant variables in the target application, such as variable name, data type, address offset (address) in the shared memory, byte size, and possible scaling factor or offset (used to convert raw data into physical value). Then, based on the address offset (address) of each variable in the shared memory corresponding to the target application and the byte size of the variable in this information, the target position of each variable in the shared memory can be determined.
[0057] S102: Parse the calibration instruction, and determine a target location in the shared memory corresponding to the target application to be calibrated based on the parsing result.
[0058] When the gateway receives a calibration command from the calibration tool, it parses the calibration results, which may include the application ID of the calibration variable, as well as its address in shared memory, byte size, variable name, data type, and possible scaling factor or offset. The application ID here identifies the corresponding shared memory, and the address is the offset relative to the starting position of this shared memory. Based on the parsed application ID of the calibration variable, the address of the calibration variable in shared memory (the shared memory of the application corresponding to the calibration variable), and the byte size, the location of the desired calibration variable in shared memory can be determined and recorded as the target location.
[0059] S103: Calibrate and measure the target position based on the calibration instruction, and generate an instruction execution result.
[0060] After parsing the calibration instruction to determine the target location, the gateway ensures that a mapping relationship has been established with the shared memory maintained by the target application (this mapping relationship allows the XCP gateway to directly access specific addresses in shared memory). The corresponding variables at each target location in shared memory are calibrated based on the variable description information (variable name, data type, scaling factor or offset, etc.) obtained from parsing the calibration instruction. This typically involves locating the variable and writing the variable. Locating the variable: locating the specific location in shared memory where the variable is stored based on the address offset information in the variable information description file. Writing the data: writing the variable value in the variable information description file to the shared memory based on the data type and data size information in the variable information description file.
[0061] It can be seen from the above scheme that the present invention configures a shared memory for each target application, and uniformly writes the variable description information of each target application into a variable information description file. When the target application needs to be calibrated, a calibration instruction is generated based on the description information of each variable of the target application stored in the variable information description file. When the gateway applying this method obtains the calibration instruction, it parses the calibration instruction, determines the target position of each variable in the shared memory based on the parsing result, and then calibrates and measures the target position based on the parsing result. Therefore, only one variable information description file needs to be configured to complete the maintenance of the variable data of all target applications. When multiple target applications need to be updated, only the variable information description file needs to be updated, which simplifies the complexity of the management and maintenance of the variable information description file.
[0062] At the same time, when using the calibration tool to calibrate the shared memory of each target application, since the variable description information corresponding to each target application is stored in the same variable information description file, there is no need to frequently switch between different variable information description files, thereby improving the ability to measure and calibrate multiple target applications simultaneously in a single session, the measurement and calibration efficiency is extremely high, and the complexity and communication burden of the system are reduced.
[0063] In this embodiment, the type of gateway can be selected according to user needs. For example, the gateway in the embodiment of the present application can be an XCP gateway. When the gateway is an XCP gateway, in order to isolate variables between multiple target applications, the present invention extends the addressing method in the XCP protocol. The XCP calibration protocol stipulates that the variable address is represented by a 40-bit address, a 32-bit XCP address and an 8-bit extended address. In this addressing method, each target application is configured with a globally unique identity information (ID). The XCP gateway will create a shared memory corresponding to the identity information, such as Figure 3 By using the target application ID as the extended address and the offset address in the shared memory as the XCP address (the address is the address resolved in step S402 ), effective isolation and management of variables between different target applications can be achieved.
[0064] In the technical solution disclosed in this embodiment, the user can choose whether a target application uses the shared memory according to their own needs. Therefore, when there are multiple applications in the target object, there may be a target application that does not use the shared memory. Therefore, after obtaining the calibration instruction sent by the calibration tool, before determining the shared memory corresponding to the target application to be calibrated based on the parsing result, it is necessary to determine the identity information of the target application based on the parsing result of the calibration instruction. The identity information may refer to the ID corresponding to the target application. Then, based on the identity information, it is determined whether there is a shared memory corresponding to the target application. When there is a shared memory corresponding to the target application, the shared memory is calibrated and measured based on the variable description information of the target application stored in the variable information description file, and subsequent steps are performed. When there is no shared memory corresponding to the target application, the calibration instruction is not responded to or a negative response is returned.
[0065] In this embodiment, an additional IPC connection needs to be established between the target application and the gateway. After the variable data of the target application in the shared memory is calibrated, the gateway will notify the target application to read the variables in the shared memory and synchronously update the variables in its stack to synchronize the variables in the shared memory. The specific steps are as follows: Figure 4 As shown:
[0066] Step S401: monitoring the connection request of the target application.
[0067] In this step, the target application automatically initiates a connection request to the gateway that applies this method after startup. When the gateway monitors the connection request, it continues to execute subsequent steps.
[0068] Step S402: establishing shared memory communication of the target application based on the connection request.
[0069] When the gateway using this method monitors the connection request of the target application, it establishes shared memory communication with the target application. The shared memory is a mapping of the calibration variables of the target application.
[0070] Step S403: synchronously updating the variable data in the shared memory corresponding to the target application and the variable data inside the target application.
[0071] In this step, after the shared memory communication of the target application is established, the variable data in the shared memory can be assigned values through the variables of the target application. Specifically, during the user's use of the target software, the variable data inside the target software is monitored. When it is detected that the variables inside the target software have changed, the values of the changed variables are sent to the gateway, so that the gateway updates the variables in the shared memory according to the values, thereby keeping the variables in the shared memory synchronized with the variables in the target application. Specifically, the process may include: determining whether the value of the variable data within the target application has changed, and when it has changed, updating the variable data in the shared memory corresponding to the target application based on the variable data within the target application; of course, in this step, after the shared memory communication of the target application is established, the variable data in the target application may also be assigned values through the variables in the shared memory. Specifically, during the user's use of the target software, the variable data in the shared memory is monitored, and when a change is detected in the variable data in the shared memory (the change is not caused by the synchronization of the variable data in the shared memory and the variable data in the target software), the value of the changed variable is sent to the target application, so that the target application updates the variable data therein according to the value, thereby keeping the variables in the shared memory synchronized with the variables in the target application.
[0072] In distributed or embedded systems, shared memory serves as an efficient inter-process communication mechanism. Its creation and deallocation are typically handled by a gateway, while target applications only have access permissions. Because shared memory is a critical resource, mutual exclusion is required for shared memory access. To ensure mutual exclusion and prevent data races and inconsistencies, synchronization mechanisms such as semaphores and mutexes are used.
[0073] In a technical solution disclosed in another embodiment of the present application, when it is necessary to correct the variable parameters of the target application, the variable parameters of the target application in the shared memory can be directly corrected without starting the target application. When the target application is started, the variable value in the shared memory is assigned to the shared memory. Therefore, in the above solution, it is judged whether the value of the variable data in the shared memory corresponding to the target application has changed. When it has changed, the variable data inside the target application is updated based on the variable data in the shared memory corresponding to the target application. It can include: judging whether the value of the variable data in the shared memory corresponding to each target application has changed. When there is variable data that has changed, judging whether the target application corresponding to the variable data has established shared memory communication with the shared memory. When shared memory communication has not been established, generating and storing prompt information corresponding to the target application. When it is detected that shared memory communication with the target application has been established, responding to the prompt information, assigning the variable data in the shared memory to the target application. In addition, when it is detected that a target application establishes shared memory communication, it can be determined whether there is corresponding prompt information. If there is the prompt information, the variable data in the shared memory is assigned to the target application in response to the prompt information.
[0074] Based on the above solutions, this application has the following advantages:
[0075] Expand the variable addressing mode of the XCP protocol, and represent the variable address by combining the target application ID and the offset address in the shared memory, thereby achieving effective isolation and management of variables between different target applications;
[0076] By utilizing the shared memory mechanism, calibration measurements of multiple target applications can be achieved, ensuring efficient access and synchronization of calibration data;
[0077] By using the XCP gateway to centrally manage the calibration measurements of multiple target applications, all target applications within the ECU are abstracted as a unified slave node, achieving centralized and standardized calibration management.
[0078] The variables of the target application are configured with the help of the XCP gateway configuration tool, and the variable descriptions of multiple application software are integrated into one A2L file through the extended XCP address scheme, thereby simplifying the management and use of calibration data.
[0079] The above describes an application variable data calibration method provided by an embodiment of the present application. The following describes an apparatus for executing the above application variable data calibration method.
[0080] See also Figure 5 , Figure 5This is a schematic diagram of the structure of an application variable data calibration device provided in an embodiment of the present application. Figure 5 As shown, the application variable data calibration device includes:
[0081] The data acquisition unit 10 is used to obtain the calibration instruction sent by the calibration tool, wherein the calibration instruction is an instruction generated based on the variable description information of the target application stored in the variable information description file;
[0082] A parsing unit 20 is configured to parse the calibration instruction and determine a target location of the shared memory corresponding to the target application to be calibrated based on the parsing result;
[0083] The calibration unit 30 is configured to calibrate and measure the target position based on the calibration instruction and generate an instruction execution result.
[0084] An electronic device is also provided in an embodiment of the present application. Figure 6 , which shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present application. The electronic devices in the embodiments of the present application may include, but are not limited to, fixed terminals such as vehicle-mounted terminals (such as ECUs), mobile phones, laptop computers, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. The target applications are various applications installed in the electronic devices. The methods for implementing the above-mentioned application variable data calibration method can be integrated into the memory 602 of the electronic device. These programs can be called by its processing device 601. The processing device 601 and the memory 602 can be connected via a bus 604. Figure 6 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.
[0085] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any one of the application variable data calibration methods provided in the embodiment of the present application.
[0086] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When one or more computer programs are executed by an electronic device, the electronic device can implement any application variable data calibration method provided in an embodiment of the present application.
[0087] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.
[0088] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.
[0089] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.
[0090] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, training device or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center that includes one or more available media integrations. The available medium can be a magnetic medium, (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state drive (SSD)).
Claims
1. A method for calibrating application variable data, characterized in that: include: Obtaining a calibration instruction sent by a calibration tool, where the calibration instruction is an instruction generated based on variable description information of a target application stored in a variable information description file; Parsing the calibration instruction, and determining a target location of the shared memory corresponding to the target application to be calibrated based on the parsing result; The target position is calibrated and measured based on the calibration instruction, and an instruction execution result is generated.
2. The method for calibrating application variable data according to claim 1, wherein: Before determining the shared memory corresponding to the target application to be calibrated based on the analysis results, the following steps are also included: Determining the identity information of the target application based on the parsing result of the calibration instruction; Determining whether there is a shared memory corresponding to the target application based on the identity information; When there is a shared memory corresponding to the target application, the shared memory is calibrated and measured based on the variable description information of the target application stored in the variable information description file, and subsequent steps are performed.
3. The method for calibrating application variable data according to any one of claims 1 to 2, characterized in that: Based on the analysis results, the shared memory corresponding to the target application to be calibrated is determined, including: Obtaining an address and a size contained in the calibration instruction based on the parsing result, wherein the address refers to an address offset of the variable data to be accessed or operated in the shared memory, and the size refers to a data length of the variable data to be accessed or operated; The shared memory corresponding to the target application that needs to be calibrated is determined based on the address and size.
4. The method for calibrating application variable data according to claim 1, wherein: After calibrating and measuring the shared memory based on the variable description information of the target application stored in the variable information description file, the method further includes: Monitor the target application's connection requests; establishing shared memory communication of the target application based on the connection request; The variable data in the shared memory corresponding to the target application and the variable data inside the target application are synchronously updated.
5. The method for calibrating application variable data according to claim 4, characterized in that: Synchronously updating variable data in a shared memory corresponding to the target application and variable data within the target application, including: Determining whether the value of the variable data within the target application has changed, and if so, updating the variable data in the shared memory corresponding to the target application based on the variable data within the target application; It is determined whether the value of the variable data in the shared memory corresponding to the target application changes, and when it changes, the variable data inside the target application is updated based on the variable data in the shared memory corresponding to the target application.
6. The method for calibrating application variable data according to claim 5, characterized in that: Determining whether a value of variable data in the shared memory corresponding to the target application changes, and when a change occurs, updating variable data within the target application based on the variable data in the shared memory corresponding to the target application, including: Determine whether the value of the variable data in the shared memory corresponding to each target application has changed; When there is changed variable data, determining whether the target application corresponding to the variable data has established shared memory communication with the shared memory; When shared memory communication is not established, generating and storing prompt information corresponding to the target application; When it is detected that the shared memory communication of the target application is established, determining whether there is prompt information corresponding to the target application; When the prompt information exists, the variable data inside the target application is updated based on the variable data in the shared memory corresponding to the target application, and the prompt information corresponding to the target application is deleted.
7. An ECU calibration device, characterized in that: include: A data acquisition unit, configured to obtain a calibration instruction sent by a calibration tool, wherein the calibration instruction is an instruction generated based on variable description information of a target application stored in a variable information description file; A parsing unit, configured to parse the calibration instruction and determine a target location of the shared memory corresponding to the target application to be calibrated based on the parsing result; A calibration unit is used to calibrate and measure the target position based on the calibration instruction and generate an instruction execution result.
8. An electronic device, characterized in that: comprising at least one processing device and a storage device connected to the processing device, wherein: The storage device is used to store computer programs; The processing device is used to execute the computer program so that the electronic device can implement the application variable data calibration method according to any one of claims 1 to 6.
9. The electronic device according to claim 8, wherein The electronic device is an ECU.
10. A computer storage medium, characterized in that The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device can implement the application variable data calibration method as described in any one of claims 1 to 6.