CN112230848A - NVM automatic configuration method, device and equipment - Google Patents

NVM automatic configuration method, device and equipment Download PDF

Info

Publication number
CN112230848A
CN112230848A CN202011078939.1A CN202011078939A CN112230848A CN 112230848 A CN112230848 A CN 112230848A CN 202011078939 A CN202011078939 A CN 202011078939A CN 112230848 A CN112230848 A CN 112230848A
Authority
CN
China
Prior art keywords
data block
file
configuration
generating
nvm
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202011078939.1A
Other languages
Chinese (zh)
Other versions
CN112230848B (en
Inventor
陶喆
朱心放
奚莉
田佰辉
范鹏
杜立新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nasn Automotive Electronics Co Ltd
Original Assignee
Nasn Automotive Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nasn Automotive Electronics Co Ltd filed Critical Nasn Automotive Electronics Co Ltd
Priority to CN202011078939.1A priority Critical patent/CN112230848B/en
Publication of CN112230848A publication Critical patent/CN112230848A/en
Application granted granted Critical
Publication of CN112230848B publication Critical patent/CN112230848B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/064—Management of blocks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0673—Single storage device
    • G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The invention discloses a method, a device and equipment for automatically configuring an NVM. The method comprises the following steps: analyzing the NV data block requirement file to obtain NV data block requirement information; generating a plurality of configuration files with different formats according to the NV data block requirement information; and generating an NV data block configuration table according to the configuration files with different formats. By using the method, the automatic configuration of the NVM module can be realized, and the problems of large workload, low efficiency and the like in the manual configuration method are effectively solved.

Description

NVM automatic configuration method, device and equipment
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an NVM automatic configuration method, device and equipment.
Background
In an electronic control unit of an electronic controller of an automobile chassis, a nonvolatile RAM Manager (NVM) is mainly used for managing nonvolatile data in a charged Erasable Programmable read only memory (EEPROM) and a Flash analog EEPROM. The NVM can directly abstract and isolate the specific data storage medium from the data user to achieve the purpose of decoupling NV data from the specific data storage medium, data writing mode, and data reading mode. The NV data is initialized, read, written, validity checked, check code calculation, data redundancy and other functions are realized through the NVM.
The NVM function is realized by two parts, including an NVM basic function module and an NVM configuration module. In the prior art, NVM configuration requires manual configuration of each NV data block in a configuration tool according to NVM usage requirements of software, and there is a requirement for professional skills on a development engineer performing the configuration work, which requires detailed knowledge of the NVM protocol stack. In addition, in the development process of the electronic controller, as the NV data block is changed for many times, the NVM configuration work needs to be repeatedly executed, the workload is large, and the maintenance is difficult.
Therefore, how to implement NVM auto-configuration is a current technical problem to be solved.
Disclosure of Invention
The embodiment of the invention provides an NVM automatic configuration method, device and equipment, which can realize NVM module automatic configuration and effectively reduce the problems of large workload, low efficiency and the like in a manual configuration method.
In a first aspect, an embodiment of the present invention provides an NVM auto-configuration method, including:
analyzing the NV data block requirement file to obtain NV data block requirement information;
generating a plurality of configuration files with different formats according to the NV data block requirement information;
and generating an NV data block configuration table according to the configuration files with different formats.
In a second aspect, an embodiment of the present invention further provides an NVM auto-configuration apparatus, including:
the NV data block requirement information acquisition module is used for acquiring an NV data block requirement file according to the NV data block requirement information, analyzing the NV data block requirement file and determining attribute information of the NV data block;
the configuration file generation module is used for generating files with different formats by a configuration tool according to the NV data block requirement information;
and the configuration table generating module is used for generating a corresponding NV data block information table according to the NV database configuration report, the NVM module configuration code and the configuration file which are contained in the different files.
In a third aspect, an embodiment of the present invention further provides a computer device, including:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the NVM auto-configuration method of any embodiment of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the NVM auto-configuration method according to any embodiment of the present invention.
The embodiment of the invention provides an NVM automatic configuration method, a device and equipment, firstly, NV data block requirement information is obtained by analyzing an NV data block requirement file; then generating a plurality of configuration files with different formats according to the NV data block requirement information; and finally, generating an NV data block configuration table according to the configuration files with different formats. By utilizing the technical scheme, the automatic configuration of the NVM module can be realized, and the problems of large workload, low efficiency and the like in a manual configuration method are effectively solved.
Drawings
FIG. 1 is a flowchart illustrating an NVM auto-configuration method according to an embodiment of the present invention;
FIG. 2 is a schematic flowchart of an NVM auto-configuration method according to a second embodiment of the present invention;
FIG. 3 is a flowchart illustrating an exemplary method for automatically configuring an NVM according to a second embodiment of the present invention;
FIG. 4 is a schematic structural diagram of an NVM auto-configuration device according to a third embodiment of the present invention;
fig. 5 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like. In addition, the embodiments and features of the embodiments in the present invention may be combined with each other without conflict.
The term "include" and variations thereof as used herein are intended to be open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment".
Example one
Fig. 1 is a flowchart of an NVM auto-configuration method according to an embodiment of the present invention, where the method is applicable to configure an NVM module in a non-volatile RAM manager, and the method can be executed by an NVM auto-configuration apparatus, where the apparatus can be implemented by software and/or hardware and is generally integrated on a computer device.
It should be noted that, after the NVM module is configured by the computer device through the NVM auto-configuration method provided by the embodiment of the present invention, the computer device may perform compiling on the computer device to generate a hex file, and download the hex file to the electronic controller in the vehicle, where the hex file may implement the NVM function in the operation of the electronic controller through refreshing.
As shown in fig. 1, a method for NVM auto-configuration according to an embodiment of the present invention includes the following steps:
and S110, analyzing the NV data block requirement file to obtain the NV data block requirement information.
In this embodiment, the NVM is a non-volatile RAM manager, which is a memory capable of storing saved data even when the power of the computer is turned off.
A requirement user of the software NV data block can fill the most basic data requirement in the NV configuration module to form an NV data block requirement file, and NV data block requirement information can be obtained by analyzing the NV data block requirement file. The number of NV data blocks may be plural, and is not particularly limited herein.
The NV data block requirement file may be a csv format file, and the NV data block requirement file may be a file including NV data block requirement information.
The NV data block requirement information may be the most basic data requirement that a requirement user of the software NV data block fills in the NV configuration module, and the NV data block requirement information may be requirement information for each NV data block. The NV data block requirement information may include: the size, name and ID of the NV data block, the write conditions and write characteristics of the NV data block, the erase conditions and the call conditions.
It should be noted that the size of the NV data block may be determined by the amount of data contained in the NV data block, and the size of the NV data block may be strictly consistent with the size actually used by the user; the writing condition of the NV data block can be understood as the time when the NV data block is written, and is description information of the NV data block; the write characteristics of the NV data blocks may include: whether the NV data block is uniformly read when the power is on, whether the NV data block is uniformly read from the FLASH space by a demand user according to the demand, whether the NV data block is uniformly written into the FLASH space by the demand user when the power is off, whether the FLASH space is written into by the demand user according to the demand, and whether the FLASH space is required to be immediately written into in the engineering compiling process; the erasing condition can be understood as whether the existing NV data block stored in the FLASH space can be erased by an external control command; the calling regulation can be understood as that whether a callback function needs to be called to inform a user that the writing into the FLASH space is successful or not after the NV data block is successfully written into the FLASH space. The FLASH space is a storage space of the NV data block, and variables in the NV data block can be stored in the FLASH space after power failure, so that the variables in the NV data block before power failure can be directly called for use when the FLASH space is powered on.
For example, the NV data block requirement file may be read in a list, where the list may include requirement information of each NV data block, each NV data block may occupy a line of memory in the list, and the line of memory may include each requirement information of the NV data block, and parsing the NV data block requirement file may be understood as extracting the requirement information of each NV data block in the list, parsing the requirement information into corresponding attributes, and creating a dictionary in the automatic configuration tool according to the attribute information.
And S120, generating a plurality of configuration files with different formats according to the NV data block requirement information.
The NV configuration module can analyze the NV data block requirement file to obtain a plurality of NV data block requirement information and generate a plurality of configuration files with different formats.
In this embodiment, the configuration files of different formats may include the FEE module configuration file, the control macro file, the FEE protocol file, the NVM protocol file, and the link script file.
The FEE module can be understood as a module in which the NVM module corresponds to the FLASH space, the FEE module configuration file can be a file formed after the NV data block requirement file of the NVM module corresponds to the FEE module, and the FEE module configuration file can be a file in a format of. xdm; the control macro file can be understood as a MemMap memory Layout control macro file corresponding to the NV data block, and the control macro file is a file in a format of h; the FEE protocol file may include a configuration C code and a header file of the FEE software protocol stack, which is a file of the format of.h or.c; the NVM protocol file may include the configuration C code and header files of the NVM protocol stack, which are files in the h or C format; the link script file may be a variable link script file in the NVM module, and the link script file may be understood as a memory Layout link script file of NV data blocks in the RAM, which is a file in a.lsl.
The FEE module configuration file can be a configuration file of a FLASH analog EEPROM, that is, a FEE driver, and the FEE module configuration file can be used to define NV data blocks and check codes, where each NV data block corresponds to a FLASH analog EEPROM.
It should be noted that the FLASH simulation EEPROM can be understood as replacing the real EEPROM by the FLASH simulation, and can also be understood as DATA FLASH hardware simulation EEPROM abstraction layer. Illustratively, for a real EEPROM, the NV data block is stored at a fixed address, reading and writing can be real-time, and the FLASH analog EEPROM means that the real EEPROM is powered down and then powered down to store the data in a FLASH manner, but is limited in life and characteristics and cannot be read and written at any time. The EEPROM is a charged erasable programmable read-only memory and is a memory chip with no data loss after power failure, and the EEPROM can erase existing information and reprogram on a computer or special equipment.
The control macro file can be used for automatically positioning the memory address of a variable in the NV data block subsequently, the NV configuration module generates a MemMap Layout control macro corresponding to the Autosar mark for each NV data block, the MemMap Layout control macro is equivalent to one mark, and the address of the variable in the NV data block can be determined according to the MemMap Layout control macro.
The configuration C code and the header file of the NVM protocol stack included in the NVM protocol file may be used to define an operation ID macro definition, an NV data block size, a read-write mode, a verification mode, an erase mode, and an abnormal condition handling mode of each MV data block according to the code and the header file.
The link script file can be used for controlling the linker to generate a memory space for storing NV data blocks in the RAM when engineering compilation is performed. It should be noted that the link file in the format of. lsl may be generated into an executable file by a compiler, and the RAM memory space refers to a RAM memory space in which software runs the NV data block, and it may also be understood that, when the software needs to run the NV data block, the NV data block stored in the FLASH space may be pulled to the RAM memory space to run, and after the running is completed, the NV data block is stored in the FLASH space, so that a variable in the NV data block may be stored after power failure.
In addition, the link script file may also specify certain characteristics associated with the compiler to the target NV data block to be used, setting the address space location and the run address of the target NV data block.
And S130, generating an NV data block configuration table according to the configuration files in different formats.
In this embodiment, the NV data block configuration table may include all the configuration files generated in the above steps, and the NV data block configuration table may be used to summarize contents included in the FEE module configuration file, the control macro file, the FEE protocol file, the NVM protocol file, and the link script file.
For example, the NV data block configuration table may include NV data blocks, check codes, and read-write operation modes of the NV data blocks in the FEE module configuration file; the NV data block configuration table may include Memmap Start macro and Memap Stop macro for memory location in the control macro file; the NV data block configuration table may include the size, ID, and name of NV data blocks in the NVM protocol file; the NV data block configuration table may also include an address space and a running address of the target NV data block in the link script file.
The NV data block configuration table may be used to record the entire automatic configuration process, collect all configuration information to generate a configuration table, and store and record all configuration information in the NV data block configuration table.
The embodiment of the invention provides an NVM automatic configuration method, which comprises the steps of firstly analyzing an NV data block requirement file to obtain NV data block requirement information; then generating a plurality of configuration files with different formats according to the NV data block requirement information; and finally generating an NV data block configuration table according to the configuration files with different formats. By utilizing the method, the automatic configuration of the NVM module is realized, and the problems of large workload, low efficiency and the like in the manual configuration method are effectively solved.
Further, analyzing the NV data block requirement file to obtain NV data block requirement information, including: reading the NV data block requirement file in a text format, analyzing each line of data in the NV data block requirement file, and obtaining requirement information corresponding to each NV data block; wherein, a line of data corresponds to an NV data block; instantiating the requirement information corresponding to each NV data block respectively; merging the requirement information corresponding to all the instantiated NV data blocks into a list; wherein, the demand information includes: the size, name and ID of the NV data block, the write conditions and write characteristics of the NV data block, the erase conditions and the call conditions.
In this embodiment, the NV configuration module may read the NV data block requirement file, and instantiate the requirement information in the NV data block requirement file as an NV data block object, so as to subsequently generate configuration files in various formats.
The NV data block requirement file can be a file in a csv format, the file can be displayed as an excel table after being read, each row in the excel table corresponds to one NV data block, each row in the table can include all requirement information of the corresponding NV data block, and the NV data blocks in each row are analyzed according to the sequence of each row in the table.
It can be understood that after the NV data blocks in each row in the table are analyzed, the requirement information corresponding to each NV data block is instantiated as a word in a dictionary in Python software, that is, a global variable.
And after recombining the requirement information corresponding to all instantiated NV data blocks in an excel table, extracting the table into a configuration tool.
Further, if the configuration file is a FEE module configuration file, generating the configuration file according to NV data block requirement information may include: generating demand information of an FEE data block corresponding to each NV data block based on the demand information of the NV data block; calling a set template file according to the requirement information of the FEE data block to generate an FEE module configuration file; the configuration file of the FEE module is a xdm format file.
The NVM configuration module may generate the requirement information of the FEE data blocks corresponding to the NV data blocks, respectively, based on the requirement information of the NV data blocks, and may be understood as corresponding the requirement information of each NV data block in the NVM module to the FEE module in the FLASH space to generate the requirement information of the corresponding FEE data block.
The set template file may be a template file pre-stored in the non-volatile RAM manager, and the requirement information of the FEE data block is stored according to the format of the template file and the corresponding position, so as to obtain a FEE module configuration file in the format of xdm.
It should be noted that the FEE module configuration file is a file conforming to an AUTomotive Open System ARchitecture (AUTomotive Open System ARchitecture, AUTOSAR) specification, where the AUTomotive Open System specification is an Open and standardized AUTomotive embedded System software ARchitecture, and the software and hardware coupling degree of the AUTomotive embedded System is greatly reduced due to the high abstraction of the AUTomotive embedded System hierarchical ARchitecture.
Further, generating the requirement information of the FEE data block corresponding to each NV data block based on the requirement information of the NV data block includes: distributing ID information of an FEE data block corresponding to each NV data block according to the NV data block requirement information; adding a set prefix or suffix to the NV data block name to obtain a corresponding FEE data block name; and determining the size of the corresponding FEE data block according to the size of the NV data block and the size of the additional data.
For example, by traversing the instantiated NV data blocks, the total number of NV data blocks may be calculated, and each NV data block may be assigned the ID information of the corresponding FEE data block, where the ID information of the FEE data block is different from the ID information of the NV data block.
For example, the obtained FEE data block name may be obtained by uniformly adding a prefix or a suffix to the NV data block name in all generated codes in the Python base module to obtain the corresponding FEE data block name.
The size of the NV data block may be determined by the number of variables included in the NV data block, and when the number of variables included in one NV data block is large, it indicates that the NV data block is large. Optionally, the additional data may include one byte of Cyclic Redundancy Check (CRC) data and one byte of header information for characterizing the status of the NV data block. The size of the corresponding FEE data block can be obtained by adding the size of the additional data to the NV data block size.
Further, if the configuration file is a control macro file, the configuration file is generated according to the NV data block requirement information, and the configuration file includes: traversing the NV data block, and generating a corresponding control macro file according to the name of the NV data block; the control macro file is used for optimizing variables in the NV data block and positioning memory addresses of the variables in the NV data block during engineering compilation.
The control macro file may be macro definitions corresponding to the NV data blocks, each macro definition corresponds to an instruction for controlling the compiler, and addresses of variables in the NV data blocks may be determined according to the macro definitions.
For example, optimizing the variable in the NV data block and locating the memory address of the variable in the NV data block may be to map an internal variable into a protected memory by means of MemMap, so as to achieve optimal protection, where both optimal protection and memory location are basic requirements of the AUTOSAR specification.
Further, if the configuration file is an FEE protocol file, generating the configuration file according to the NV data block requirement information may specifically include: acquiring a computer user and the current time as annotation information; generating an FEE module configuration code and a header file according to the requirement information of the FEE data block, and adding the annotation information to the FEE module configuration code and the header file; the FEE module configuration code and the header file form a FEE protocol file.
The automatic configuration tool can be a file in a py format, and a script file in a bat format can be operated only by clicking. By reading the current running script file, the name and the current time of the computer user running the current script file can be obtained, and the read information can be used as annotation information.
And traversing the NV data block, and converting the requirement information of the NV data block into the requirement information of the corresponding FEE data block. Specifically, the requirement information of each row of NV data blocks in the NV data block requirement file is extracted, analyzed into corresponding attribute information, stored in the FEE module to obtain the requirement information of the corresponding FEE data block, and the FEE module configuration code and the header file are generated according to the requirement information of the FEE data block.
The annotation information may include information of a computer user, version information and time information of the configuration code, and the like, so as to facilitate subsequent tracing. And generating an FEE protocol file which can be used for carrying out engineering compilation subsequently to generate an operation file.
Further, if the configuration file is an FEE protocol file, generating the configuration file according to the NV data block requirement information, which may specifically include: acquiring a computer user and the current time as annotation information; traversing the NV data blocks, and generating an operation handle of each NV data block; analyzing the finally compiled address information based on the operation handle and the requirement information to generate an NVM module configuration code and a header file; adding the annotation information to the NVM module configuration code and header file; the NVM module configuration code and the header file constitute an NVM protocol file.
The operation handle of the NV data block can be simply understood as an operation pointer, and the operation handle corresponding to each NV data block is generated by analyzing the requirement information of the NV data block; meanwhile, according to the read-write attribute of the NV data block, the size of the address generated by the final compiling of the NV data block is analyzed, and a configuration C code and a header file of the NVM module are generated.
The generated NVM protocol file can be used for subsequent engineering compilation to generate an operation file.
Further, if the configuration file is a link script file, the generating a configuration file according to the NV data block requirement information specifically includes: and traversing the NV data blocks, and generating a link script file of the NV data blocks in a memory according to the size of each NV data block and the check codes of the NV data blocks.
Illustratively, after traversing the NV data blocks, the size of each NV data block and check codes of each NV data block can be combined, then a memory Layout link file of addresses of the NV data blocks in the RAM and the ROM is generated according to a compiler link file syntax, and the generated link script file can be used for controlling the final storage position of variable data in the NV data blocks.
Specifically, each NV data block check code may be a CRC calculated when each NV data block is stored, where the CRC is a channel coding technique that generates a short fixed-bit check code according to data such as a network data packet or a computer file, and is mainly used to detect or check errors that may occur after data transmission or storage. The check code has a fixed size and may be a hexadecimal value.
It should be noted that the NV data block is stored at a random address, but when the NV data block is damaged, it needs to be determined whether the NV data block is damaged through a checking mechanism. The NV data block calculates the CRC of the NV data block before being stored in a FLASH space, then the NV data block and the calculated CRC are stored in the FLASH space together, the CRC is calculated again when the NV data block is used after next power-on, then the CRC is compared with the CRC calculated in the previous storage, if the CRC calculated twice is the same, the NV data block can be determined to be not damaged and can be continuously used, and if the CRC calculated twice is different, the NV data block can be determined to be damaged, and then the NV data block is discarded.
The generate chain pin file may further include: and combining the size of the NV data block and the size of the check code, controlling each variable initial value stored in the NV data block to be stored in a memory Layout link file in a FLASH space through a compiler link file grammar, and controlling a link script file to store the specific position of the variable initial value of the NV data block in the FLASH space when engineering compilation is carried out.
The initial values of the variables of the NV data blocks need to be stored in the ROM space, and therefore space application and address location need to be performed through the link script file. The link script file in lsl format can be used to describe to the compiler the properties of the ROM space to which the initial values of the variables of the NV data blocks are applied, and the specific storage address can be determined by the compiler.
Optionally, when the NV data block is not read from the EEPROM or the FLASH analog EEPROM, a default value of the variable stored in the NV data block in the FLASH is first used as the variable value. When the NV data in the EEPROM or the FLASH simulation EEPROM is not verified, the NV data block is damaged, and the NV data block is automatically switched to the default value of the variable in the NV data block stored in the FLASH, so that the running safety of software is not influenced by the wrong NV data block.
Example two
Fig. 2 is a schematic flowchart of an NVM auto-configuration method according to a second embodiment of the present invention, as shown in fig. 2: firstly, acquiring NVM _ Cfg.csv, then acquiring an NVM configuration file generation tool, namely an automatic configuration tool, and finally generating files with different formats.
Wherein NVM _ Cfg.csv: analyzing the NV data block requirement file;
wherein, Fee.xdm: generating a corresponding FEE module configuration file according to NV data block requirement information;
wherein, memmap.h: generating a Memmap memory Layout control macro corresponding to the NV data block;
wherein, nvm.lsl: and generating a memory Layout link script file of the NV data block in the RAM by combining the size of the NV data block and the grammar of a compiler link file.
Wherein, NvM _ rom.lsl: and controlling the variable initial value of each NV data block stored in the NV data block to be stored in the memory Layout link script file in the F LASH by combining the size of the NV data block and the size of each NV data block check code with the grammar of a compiler link file.
Wherein, Fee _ PBCfg.c, Fee _ Cfg.h: FLASH simulates EEPROM. The method is used for defining the data block and the check code of each NV data block in the FLASH analog EEPROM and the read-write operation mode.
Wherein, NvM _ Cfg _ auto.h, NvM _ Cfg _ auto.c: and the configuration C code and the header file of the NVM protocol stack are used for defining the operation ID macro definition, the size of the NV data block, the reading and writing mode, the checking mode, the erasing mode and the abnormal condition processing mode of each NV data block.
Wherein, NVM _ memmapraco.csv: and the NV data block configuration report is used for summarizing and explaining the available sizes and names of all NV data blocks in the current project, the Memmap Start macro and the Memmap Stop macro for memory location.
Fig. 3 is a schematic flowchart illustrating an exemplary flow of an NVM auto-configuration method according to a second embodiment of the present invention, as shown in fig. 3, the NVM auto-configuration method according to the present embodiment includes the following steps: first, analysis was conducted
The method comprises the following steps: firstly, acquiring demand information of NV data blocks by using an NVM-Cfg.csv file, namely an NV data block demand file, then generating an FEE module configuration file according to the NV data block demand, then distributing a MemMap Layout control macro according to the NV data block name, then generating a configuration C code and a header file of an FEE software protocol stack, generating a configuration C code and a header file of an NVM protocol stack, generating a link script file of the NV data blocks, and finally generating an NV data block information table.
The specific process of the steps is described as follows:
reading the NVM-Cfg.csv file, and instantiating the requirement information in the NVM-Cfg.csv file into NV data block objects for subsequently generating configuration files with various different formats. The method comprises the following specific steps:
1) reading the NVM _ Cfg.csv file in a text format;
2) analyzing NV data blocks in the NVM-Cfg-csv file according to rows, wherein each row of memory contains independent NV data block information;
3) after analyzing the demand information of the NV data blocks, instantiating each NV data block as an independent object in Python, namely a global variable;
4) merging the requirement information of all instantiated NV data blocks in a list of NVM _ Cfg.
And step two, generating an FEE module configuration file which meets AUTOSAR specifications according to the requirement information of the NV data block. The method comprises the following specific steps:
1) traversing the NV data block examples, calculating the total number of the NV data blocks, and distributing the ID information of the FEE data block corresponding to each NV data block;
2) calculating the name of the corresponding FEE data block according to the NV data block name;
3) calculating the size of a corresponding FEE data block according to the size of the NV data block and by combining additional data which is additionally added by an NVM protocol stack;
4) and generating a configuration file of the format of xdm of the FEE module according to the set template file in the configuration tool.
And step three, generating a corresponding AUTOSAR mark MemMap Layout control macro for each NV data block, and using the control macro to automatically position the memory address of the variable in the NV data block subsequently. The method comprises the following specific steps:
1) traversing the NV data block, generating corresponding macro definitions according to the name of the NV data block, wherein each macro definition corresponds to an instruction for controlling a compiler and is used for carrying out optimization protection and memory location on variables defined in the NV data block when compiling a code.
And fourthly, generating a configuration C code and a header file of the FEE software protocol stack. The method comprises the following specific steps:
1) reading a computer user of a current running script and the current time, namely acquiring the computer user and the current time;
2) traversing the NV data block, converting the NV data block into the requirement information of the corresponding FEE data block according to the requirement information of the NV data block, and generating a corresponding FEE module configuration C code and a header file;
3) and adding annotation information into the generated header file, wherein the annotation information indicates the time of generating the file and the use of a generator for subsequent tracing.
And step five, generating a configuration C code and a header file of the NVM protocol stack. The method comprises the following specific steps:
1) reading a computer user of a current running script and the current time, namely acquiring the computer user and the current time;
2) and traversing the NV data blocks and generating an operation handle of each NV data block. Meanwhile, according to information such as read-write attributes of the NV data block, analyzing the size of an address generated by the final compiling of the NV data block, and generating a C code and a header file for the NVM module configuration;
3) and adding annotation information into the generated file, wherein the annotation information indicates the time of generating the file and the use of a generator for subsequent tracing.
And step six, generating an NVM variable link script file, namely generating a link script file of the NV data block in the memory, and controlling the final storage position of the variable in the NV data block. The method comprises the following specific steps:
1) and traversing the NV data blocks, and generating a link script file for controlling the addresses of variables in the NV data blocks in the RAM and the ROM according to the requirement information of each NV data block.
And seventhly, generating an NV data block information table.
According to the method for automatically configuring the NVM, all codes and configuration files of NVM software and the memory Layout link script file of RAM and FLASH can be automatically generated only by filling the most basic NV data block requirement information by a requirement user, and reasonable RAM space and FLASH space are automatically allocated to each NV data block. By using the method, the NVM software can be automatically configured, and when the NV data block is changed, the configuration can be automatically completed, so that the workload of manual configuration is reduced, and the problem that the NVM is not suitable for maintenance during manual configuration is effectively solved.
EXAMPLE III
Fig. 4 is a schematic structural diagram of an NVM auto-configuration apparatus according to a third embodiment of the present invention, which is applicable to configure an NVM module in a non-volatile RAM manager, where the apparatus can be implemented by software and/or hardware and is generally integrated on a computer device.
As shown in fig. 4, the apparatus includes:
the NV data block requirement information obtaining module 410 is configured to obtain an NV data block requirement file according to NV data block requirement information, analyze the NV data block requirement file, and determine attribute information of the NV data block;
a configuration file generating module 420, configured to generate files with different formats by a configuration tool according to the NV data block requirement information;
and the configuration table generating module 430 is configured to generate a corresponding NV data block information table according to the NV database configuration report, the NVM module configuration code, and the configuration file included in the different files.
In this embodiment, the apparatus is first configured to obtain an NV data block requirement file according to NV data block requirement information through an NV data block requirement information obtaining module, analyze the NV data block requirement file, and determine attribute information of the NV data block; secondly, a configuration file generating module is used for generating files with different formats by a configuration tool according to the NV data block requirement information; and finally, generating a corresponding NV data block information table according to the NV database configuration report, the NVM module configuration code and the configuration file which are included in the different files by a configuration table generating module.
The embodiment provides an NVM automatic configuration device, which can implement NVM module automatic configuration and effectively solve the problems of large workload, low efficiency and the like in the manual configuration method.
Further, the NV data block requirement information obtaining module 410 is specifically configured to read the NV data block requirement file in a text format, analyze each line of data in the NV data block requirement file, and obtain requirement information corresponding to each NV data block; wherein, a line of data corresponds to an NV data block; instantiating the requirement information corresponding to each NV data block respectively; merging the requirement information corresponding to all the instantiated NV data blocks into a list;
wherein, the demand information includes: the size, name and ID of the NV data block, the write conditions and write characteristics of the NV data block, the erase conditions and the call conditions.
Further, if the configuration file is a FEE module configuration file, the configuration file generating module 420 is specifically configured to: generating demand information of an FEE data block corresponding to each NV data block based on the demand information of the NV data block; calling a set template file according to the requirement information of the FEE data block to generate an FEE module configuration file; the configuration file of the FEE module is a xdm format file.
Further, an FEE data block requirement information generating module, configured to allocate, according to each NV data block requirement information, ID information of a FEE data block corresponding to each NV data block; adding a set prefix or suffix to the NV data block name to obtain a corresponding FEE data block name; and determining the size of the corresponding FEE data block according to the size of the NV data block and the size of the additional data.
Further, if the configuration file is a control macro file, the configuration file generating module 420 is specifically configured to: traversing the NV data block, and generating a corresponding control macro file according to the name of the NV data block; the control macro file is used for optimizing variables in the NV data block and positioning memory addresses of the variables in the NV data block during engineering compilation.
Further, if the configuration file is a FEE protocol file, the configuration file generating module 420 is specifically configured to: acquiring a computer user and the current time as annotation information; generating an FEE module configuration code and a header file according to the requirement information of the FEE data block, and adding the annotation information to the FEE module configuration code and the header file; the FEE module configuration code and the header file form a FEE protocol file.
Further, if the configuration file is an NVM protocol file, the configuration file generating module 420 is specifically configured to: acquiring a computer user and the current time as annotation information; traversing the NV data blocks, and generating an operation handle of each NV data block; analyzing the finally compiled address information based on the operation handle and the requirement information to generate an NVM module configuration code and a header file; adding the annotation information to the NVM module configuration code and header file; the NVM module configuration code and the header file constitute an NVM protocol file.
The NVM automatic configuration device can execute the NVM automatic configuration method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Example four
Fig. 5 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention. As shown in fig. 5, a computer device provided in the fourth embodiment of the present invention includes: one or more processors 51 and storage 52; the processor 51 in the electronic controller device may be one or more, and fig. 5 illustrates one processor 51 as an example; storage 52 is used to store one or more programs; the one or more programs are executed by the one or more processors 51, such that the one or more processors 51 implement the NVM auto-configuration method according to any of the embodiments of the present invention.
The computer device may further include: an input device 53 and an output device 54.
The processor 51, the storage means 52, the input means 53 and the output means 54 in the computer apparatus may be connected by a bus or other means, which is exemplified in fig. 5.
The storage device 52 in the computer apparatus is used as a computer-readable storage medium, and can be used to store one or more programs, which may be software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the NVM auto-configuration method according to one or two embodiments of the present invention (for example, the modules in the NVM auto-configuration device shown in fig. 4 include an NV data block requirement information obtaining module 410, a configuration file generating module 420, and a configuration table generating module 430). The processor 51 executes various functional applications and data processing of the computer device by running software programs, instructions and modules stored in the storage device 52, that is, implements the NVM auto-configuration method in the above-described method embodiment.
The storage device 52 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the computer device, and the like. Further, the storage 52 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the storage 52 may further include memory located remotely from the processor 51, which may be connected to the device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 53 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function controls of the computer apparatus. The output device 54 may include a display device such as a display screen.
And, when one or more programs included in the above-mentioned computer apparatus are executed by the one or more processors 51, the programs perform the following operations:
analyzing the NV data block requirement file to obtain NV data block requirement information;
generating a plurality of configuration files with different formats according to the NV data block requirement information;
and generating an NV data block configuration table according to the configuration files with different formats.
EXAMPLE five
An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program is used, when executed by a processor, to execute an NVM auto-configuration method, where the method includes:
analyzing the NV data block requirement file to obtain NV data block requirement information;
generating a plurality of configuration files with different formats according to the NV data block requirement information;
and generating an NV data block configuration table according to the configuration files with different formats.
Optionally, the program, when executed by the processor, may be further configured to perform the NVM auto-configuration method provided by any of the embodiments of the present invention.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), a flash Memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. A computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take a variety of forms, including, but not limited to: an electromagnetic signal, an optical signal, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. An NVM auto-configuration method, comprising:
analyzing the NV data block requirement file to obtain NV data block requirement information;
generating a plurality of configuration files with different formats according to the NV data block requirement information;
and generating an NV data block configuration table according to the configuration files with different formats.
2. The method of claim 1, wherein parsing the NV data block requirement file to obtain NV data block requirement information comprises:
reading the NV data block requirement file in a text format, analyzing each line of data in the NV data block requirement file, and obtaining requirement information corresponding to each NV data block; wherein, a line of data corresponds to an NV data block;
instantiating the requirement information corresponding to each NV data block respectively;
merging the requirement information corresponding to all the instantiated NV data blocks into a list;
wherein, the demand information includes: the size, name and ID of the NV data block, the write conditions and write characteristics of the NV data block, the erase conditions and the call conditions.
3. The method of claim 2, wherein if the configuration file is a FEE module configuration file, generating the configuration file according to the NV data block requirement information comprises:
generating demand information of an FEE data block corresponding to each NV data block based on the demand information of the NV data block;
calling a set template file according to the requirement information of the FEE data block to generate an FEE module configuration file;
the configuration file of the FEE module is a xdm format file.
4. The method of claim 3, wherein generating the requirement information of the FEE data block corresponding to each NV data block based on the requirement information of the NV data block comprises:
distributing ID information of an FEE data block corresponding to each NV data block according to the NV data block requirement information;
adding a set prefix or suffix to the NV data block name to obtain a corresponding FEE data block name;
and determining the size of the corresponding FEE data block according to the size of the NV data block and the size of the additional data.
5. The method of claim 2, wherein if the configuration file is a control macro file, the generating the configuration file according to the NV data block requirement information comprises:
traversing the NV data block, and generating a corresponding control macro file according to the name of the NV data block; the control macro file is used for optimizing variables in the NV data block and positioning memory addresses of the variables in the NV data block during engineering compilation.
6. The method of claim 3, wherein if the configuration file is an FEE protocol file, generating the configuration file according to the NV data block requirement information comprises:
acquiring a computer user and the current time as annotation information;
generating an FEE module configuration code and a header file according to the requirement information of the FEE data block, and adding the annotation information to the FEE module configuration code and the header file; the FEE module configuration code and the header file form a FEE protocol file.
7. The method of claim 5, wherein if the configuration file is an NVM protocol file, generating the configuration file according to the NV data block requirement information comprises:
acquiring a computer user and the current time as annotation information;
traversing the NV data blocks, and generating an operation handle of each NV data block;
analyzing the finally compiled address information based on the operation handle and the requirement information to generate an NVM module configuration code and a header file;
adding the annotation information to the NVM module configuration code and header file; the NVM module configuration code and the header file constitute an NVM protocol file.
8. The method of claim 2, wherein if the configuration file is a link script file, the generating the configuration file according to the NV data block requirement information comprises:
and traversing the NV data blocks, and generating a link script file of the NV data blocks in a memory according to the size of each NV data block and the check codes of the NV data blocks.
9. An NVM auto-configuration apparatus, comprising:
the NV data block requirement information acquisition module is used for acquiring an NV data block requirement file according to the NV data block requirement information, analyzing the NV data block requirement file and determining attribute information of the NV data block;
the configuration file generation module is used for generating files with different formats by a configuration tool according to the NV data block requirement information;
and the configuration table generating module is used for generating a corresponding NV data block information table according to the NV database configuration report, the NVM module configuration code and the configuration file which are contained in the different files.
10. A computer device, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the NVM auto-configuration method of any of claims 1-8.
CN202011078939.1A 2020-10-10 2020-10-10 NVM automatic configuration method, device and equipment Active CN112230848B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011078939.1A CN112230848B (en) 2020-10-10 2020-10-10 NVM automatic configuration method, device and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011078939.1A CN112230848B (en) 2020-10-10 2020-10-10 NVM automatic configuration method, device and equipment

Publications (2)

Publication Number Publication Date
CN112230848A true CN112230848A (en) 2021-01-15
CN112230848B CN112230848B (en) 2023-12-22

Family

ID=74113258

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011078939.1A Active CN112230848B (en) 2020-10-10 2020-10-10 NVM automatic configuration method, device and equipment

Country Status (1)

Country Link
CN (1) CN112230848B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114936045A (en) * 2021-02-04 2022-08-23 广汽埃安新能源汽车有限公司 Automatic configuration method and system for IO (input/output) driving module of MCAL (micro channel logic) and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100218199A1 (en) * 2009-02-26 2010-08-26 David Lutterkort Method for programmatic editing of configuration files
US20140358549A1 (en) * 2013-06-03 2014-12-04 Avaya Inc. System and method for conversational configuration of applications
US20180335822A1 (en) * 2017-05-19 2018-11-22 Dell Products, L.P. Configurable voltage regulator controllers
CN109361711A (en) * 2018-12-14 2019-02-19 泰康保险集团股份有限公司 Firewall configuration method, apparatus, electronic equipment and computer-readable medium
CN109660376A (en) * 2017-10-12 2019-04-19 中兴通讯股份有限公司 A kind of mapping method of virtual network, equipment and storage medium
CN111522583A (en) * 2020-04-08 2020-08-11 芯海科技（深圳）股份有限公司 Method and device for generating configuration file, computer equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100218199A1 (en) * 2009-02-26 2010-08-26 David Lutterkort Method for programmatic editing of configuration files
US20140358549A1 (en) * 2013-06-03 2014-12-04 Avaya Inc. System and method for conversational configuration of applications
US20180335822A1 (en) * 2017-05-19 2018-11-22 Dell Products, L.P. Configurable voltage regulator controllers
CN109660376A (en) * 2017-10-12 2019-04-19 中兴通讯股份有限公司 A kind of mapping method of virtual network, equipment and storage medium
CN109361711A (en) * 2018-12-14 2019-02-19 泰康保险集团股份有限公司 Firewall configuration method, apparatus, electronic equipment and computer-readable medium
CN111522583A (en) * 2020-04-08 2020-08-11 芯海科技（深圳）股份有限公司 Method and device for generating configuration file, computer equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114936045A (en) * 2021-02-04 2022-08-23 广汽埃安新能源汽车有限公司 Automatic configuration method and system for IO (input/output) driving module of MCAL (micro channel logic) and storage medium
CN114936045B (en) * 2021-02-04 2023-08-04 广汽埃安新能源汽车有限公司 Automatic configuration method and system for IO driving module of MCAL and storage medium

Also Published As

Publication number Publication date
CN112230848B (en) 2023-12-22

Similar Documents

Publication Publication Date Title
CN109039824B (en) Automatic test system and method for wireless remote communication protocol of vehicle-mounted terminal
US20180246713A1 (en) Method for programming vehicle electronic control modules
CN110888414B (en) Test method for upgrading vehicle controller
US20100095159A1 (en) Apparatus and method for automatic testing of software or digital devices
KR20210149045A (en) artificial intelligence chip verification
CN108319575B (en) Page component checking method, device, server and storage medium
CN109933521A (en) Automated testing method, device, computer equipment and storage medium based on BDD
US20130103379A1 (en) Apparatus and method for verifying interoperability between application software and autosar service
CN111400167A (en) Redfish service compliance verification method, device, equipment and medium
CN110515643A (en) A kind of host computer tool for writing with a brush dipped in Chinese ink BIN file
CN110209389A (en) A kind of data generating tool development system based on XML
CN113591422B (en) System for generating test case flow information in chip verification and application
CN112230848B (en) NVM automatic configuration method, device and equipment
CN116225501A (en) ECU upgrading method and device and readable storage medium
CN116681013B (en) Simulation verification method, platform, device, equipment and medium of network chip
CN110955605A (en) Method for verifying single step dynamic execution by CPU
CN100359485C (en) Testing device and method for flush-bonding system
US11958511B2 (en) Train signal system and linkage method therefor
CN115437675A (en) Method, device, equipment and medium for online upgrading application program
CN104678292A (en) Test method and device for CPLD (Complex Programmable Logic Device)
Ji et al. Implementation and research of bootloader for automobile ECU remote incremental update
CN109947407B (en) Data acquisition method and device
CN111190615A (en) Method for remotely modifying equipment parameters and upgrading equipment parameters
CN111857664B (en) Application development method, device, equipment and storage medium
CN117272694B (en) Method, system and medium for establishing equipment simulation model based on parameter componentization

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant