CN113407196A - ECU data storage method and ECU - Google Patents
ECU data storage method and ECU Download PDFInfo
- Publication number
- CN113407196A CN113407196A CN202110503015.XA CN202110503015A CN113407196A CN 113407196 A CN113407196 A CN 113407196A CN 202110503015 A CN202110503015 A CN 202110503015A CN 113407196 A CN113407196 A CN 113407196A
- Authority
- CN
- China
- Prior art keywords
- data
- ecu
- factory
- software
- module
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 24
- 238000013500 data storage Methods 0.000 title claims abstract description 13
- 238000004519 manufacturing process Methods 0.000 claims abstract description 72
- 230000015654 memory Effects 0.000 claims abstract description 68
- 238000004806 packaging method and process Methods 0.000 claims abstract description 5
- 238000003860 storage Methods 0.000 claims description 31
- 230000008859 change Effects 0.000 claims description 11
- 230000004075 alteration Effects 0.000 claims 2
- 238000011161 development Methods 0.000 abstract description 14
- 230000005540 biological transmission Effects 0.000 abstract description 6
- 230000000694 effects Effects 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 6
- 230000014759 maintenance of location Effects 0.000 description 4
- 230000001680 brushing effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000013522 software testing Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000010923 batch production Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses an ECU data storage method and an ECU, and relates to the field of data storage. The ECU data storage method comprises the steps of obtaining non-factory data which are data irrelevant to a factory production line; packaging the non-factory data into ECU software; acquiring factory data, wherein the factory data is production data determined by a factory production line; writing the ECU software brush to a first memory in an ECU; storing the plant data to a second memory in the ECU; the problem that a conventional software data storage method can not be obviously suitable for all stages in the ECU production process is solved, and the effects of improving the ECU development efficiency, reducing the transmission links of the ECU software data in the middle and ensuring the consistency of the software data are achieved.
Description
Technical Field
The application relates to the field of data storage, in particular to an ECU data storage method and an ECU.
Background
An ECU (Electronic Control Uint) is a controller for vehicle behavior Control. Before vehicle control is realized, data is required to be written to the ECU, and data updating and management are completed.
With the development of automobile intelligent process, the data volume of the vehicle-mounted ECU is more and more, the function of the ECU is more and more powerful, and in order to facilitate production management and diagnostic analysis, a large amount of software data needs to be injected and stored in the ECU production process, such as: an ECU part Number, a production date, a software version Number, a Vehicle Identification Number (VIN) code of the entire Vehicle, and the like.
However, the types of software data stored in the ECU are various, and the characteristics of different types of data are greatly different, for example, the software version number is software data that changes following the change of the ECU software, and the change frequency is high; the production date is data strongly related to a factory production line and cannot be locked in an ECU software development stage; the ECU part number does not need to be changed frequently, but is different in different stages of development of the ECU. For ECU software data which needs to be changed frequently and is transmitted to a factory production line for changing, due to the fact that a plurality of data transmission links are involved between a development department and the factory production line, data transmission efficiency is low, and consistency of the software data is difficult to guarantee.
Disclosure of Invention
In order to solve the problems in the related art, the application provides an ECU data storage method and an ECU. The technical scheme is as follows:
in a first aspect, an embodiment of the present application provides an ECU data storage method, including:
acquiring non-factory data which is data irrelevant to a factory production line;
packing the non-factory data into ECU software;
acquiring factory data, wherein the factory data is production data determined by a factory production line;
writing an ECU software brush to a first memory in the ECU;
the factory data is stored to a second memory in the ECU.
Optionally, the non-factory data includes calibration data and non-calibration data, the change frequency of the calibration data is greater than that of the non-calibration data, and the ECU software includes an application data module, an application module, a Flash driver module and a Bootloader module;
packaging non-factory data into ECU software, including:
the calibration data is imported into an application data module in ECU software;
and importing the non-calibration data into an application module in ECU software.
Optionally, the method further includes:
when the ECU is powered on, the non-factory data stored in the first memory is written into the second memory by running ECU software in the ECU.
Optionally, the factory data at least includes a production line number, a production time, and a production lot.
Optionally, the non-factory data at least includes an ECU software version number, an ECU part number, and a vehicle VIN number.
In a second aspect, an embodiment of the present application provides an ECU, in which a storage device is disposed, the storage device including a first memory and a second memory;
factory data is stored in the second memory, and the factory data is production data determined by a factory production line;
ECU software is stored in the first storage, the ECU software comprises non-factory data, and the non-factory data are data irrelevant to a factory production line.
Optionally, the non-factory data includes calibration data and non-calibration data, and the change frequency of the calibration data is greater than that of the non-calibration data;
the ECU software comprises an application data module, an application module, a Flash drive module and a Bootloader module, wherein non-calibration data is stored in the application module, and calibration data is stored in the application data module.
Optionally, when the ECU is powered on, the non-factory data stored in the first memory is written into the second memory.
Optionally, the factory data at least includes a production line number, a production time, and a production lot.
Optionally, the non-factory data at least includes an ECU software version number, an ECU part number, and a vehicle VIN number.
The technical scheme at least comprises the following advantages:
the ECU data is divided into factory data and non-factory data, the corresponding ECU data is determined according to research, development and production characteristics, storage devices in the ECU are distinguished, storages for storing the factory data and the non-factory data are separated, the first storage is used for storing the non-factory data, the second storage is used for storing the factory data, the factory data are directly responsible for a factory production line, a development department and the factory production line are separated in the aspect of data, the problem that a conventional software data storage method cannot be obviously applied to all stages in the ECU production process is solved, the ECU development efficiency is improved, intermediate transmission links of the ECU software data are reduced, the consistency of the software data is guaranteed, and the effect of the whole ECU production process is optimized.
Drawings
In order to more clearly illustrate the detailed description of the present application or the technical solutions in the prior art, the drawings needed to be used in the detailed description of the present application or the prior art description will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a schematic diagram of an ECU provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of storage of ECU data provided by an embodiment of the present application;
FIG. 3 is a flow chart of a method for storing ECU data provided by the embodiment of the present application;
wherein: 21, ECU software; 22, plant data; 31, non-factory data.
Detailed Description
The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, and do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present application. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present application, it is to be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; the connection can be mechanical connection or electrical connection; the two elements may be directly connected or indirectly connected through an intermediate medium, or may be communicated with each other inside the two elements, or may be wirelessly connected or wired connected. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art.
In addition, the technical features mentioned in the different embodiments of the present application described below may be combined with each other as long as they do not conflict with each other.
The ECU generates a large amount of data in the development and production processes, and in order to enable the external device to obtain the relevant information of the ECU, the relevant data needs to be flushed into a storage device arranged in the ECU during production.
Optionally, the external device reads data from a storage device in the ECU, and/or the external device writes data to the ECU.
In order to enable data transmission and updating to be more efficient and ensure data consistency, data needing to be stored in the ECU are classified according to the characteristics of development and production of the ECU. Specifically, data to be stored in the ECU is referred to as ECU data, and the ECU data is divided into factory data and non-factory data.
The factory data is production data determined by a factory production line, and the factory data cannot be determined in the ECU software development stage. Factory data is strongly related to factory production lines, such as: production line number, production time, batch production and the like.
The non-factory data is data irrelevant to a factory production line, and is determined and changed in the ECU software development stage, such as: ECU software version number, ECU part number, vehicle VIN code, etc.
In the ECU software development stage, the ECU also needs to perform software testing, before the ECU performs the software testing, the ECU software needs to be flushed into the ECU by a refreshing tool, and non-factory data needing to be changed is determined according to a testing result. Dividing the non-factory data into calibration data and non-calibration data according to the change frequency of the non-factory data, wherein the change frequency of the non-calibration data is less than that of the calibration data.
In the ECU software development stage, non-factory data is packaged into ECU software; when the ECU software is flushed into the ECU, non-factory data is flushed into the ECU along with the ECU software.
In order to solve the problem that the conventional data storage method cannot be applied to all stages in the ECU production process, the ECU data is divided into factory data and non-factory data, and meanwhile, the storage of the factory data and the storage of the non-factory data in the ECU are divided, the embodiment of the application provides an ECU, as shown in fig. 1, a storage device 120 is arranged in the ECU110, the storage device 120 comprises a first storage 130 and a second storage 140, and the storage device 120 can also comprise other storages.
The first memory 130 and the second memory 140 are different memories provided in the ECU.
Optionally, the number of the first memories 130 is 1 or more than 1, and the number of the first memories is determined according to the actual situation, which is not limited in the present application; the number of the second memories 140 is 1 or more than 1, and the number of the second memories is determined according to the actual situation, which is not limited in the present application.
Optionally, the first Memory and the second Memory are NVM (Non-volatile Memory) memories.
The second memory stores factory data, the first memory stores ECU software, and the ECU software comprises non-factory data.
It should be noted that, the names of the first memory and the second memory may be different for different chip manufacturers, and the names of the first memory and the second memory in the ECU are not limited in the embodiments of the present application.
Alternatively, the first memory means a memory for storing ECU software (program), and the second memory means a memory for storing data.
The factory data includes at least a production line number, a production time, and a production lot. The non-factory data at least comprises an ECU software version number, an ECU part number and a finished vehicle VIN code.
Optionally, the non-factory data includes calibration data and non-calibration data, and the change frequency of the calibration data is greater than the frequency conversion frequency of the non-calibration data.
Optionally, the ECU software 21 includes a plurality of software logic modules, which are an Application Data module (Application Data), an Application module (Application), a Flash Driver module (Flash Driver), and a Bootloader module, respectively, as shown in fig. 2.
In the ECU software, each software logic module is composed of one or more sub-modules. In one example, an Application module (Application) is composed of 2 sub-modules, namely an Application1 sub-module and an Application2 sub-module.
The Bootloader module is a program and is used for starting the functions of guiding and refreshing ECU software.
The Flash Driver is a Driver for operating Flash. The first memory and the second memory are both Flash.
It should be noted that the Flash Driver and the Bootloader module are solidified together, or the Flash Driver and the Bootloader module are separate software logic modules respectively.
Application is a program that implements Application functions.
The Application Data is a Data set used by the Application.
The calibration Data is stored in an Application Data module (Application Data), and the non-calibration Data is stored in an Application module (Application).
At the time of ECU software development, an Application Data module (Application Data) that stores calibration Data in the ECU software, and an Application module (Application) that stores non-calibration Data in the ECU software.
When the calibration data needs to be updated, the calibration data is exported from an application data module in the ECU software by using a tool, then the calibration data is changed, and after the calibration data is changed, the changed calibration data is imported into the application data module of the ECU software by using the tool. Similarly, when the non-calibration data needs to be updated, the tool is used for exporting the non-calibration data from the application module in the ECU software, then the non-calibration data is changed, and after the non-calibration data is changed, the tool is used for importing the changed non-calibration data into the application module of the ECU software.
Because the non-factory data is packaged into the ECU software, the non-factory data can be changed no matter the non-factory data is stored into the ECU, or the non-factory data needs to be changed in the ECU research, development and debugging stage or after the ECU is produced, the ECU software is written into the ECU in a flashing mode through transferring the ECU software, so that the change link of the non-factory data in the subsequent ECU is simplified, and the consistency of the data is ensured.
Optionally, in order to avoid that the external device cannot read the non-factory data stored in the first memory from the ECU due to the first memory being erased after the EUC software fails to be refreshed, after the ECU is powered on, the non-factory data stored in the first memory is written into the second memory, that is, the second memory is made to store the factory data and the non-factory data.
Referring to fig. 3, a flowchart of an ECU data storage method provided in an embodiment of the present application is shown, where the method at least includes the following steps:
The non-factory data is data unrelated to factory data, and the factory data is production data determined by a factory production line.
Non-factory data is determined and acquired in an ECU software development stage and a maintenance stage.
Alternatively, the non-factory data is determined by an ECU software development engineer.
And in the ECU software development stage and the maintenance stage, non-factory data are packaged into the ECU software.
Factory data is determined by a factory production line that produces the ECUs. For example, a technician of a plant production line determines plant data. And forming a corresponding factory data file according to the determined factory data.
In step 304, the ECU software is written to a first memory in the ECU.
The first memory is a storage device provided in the ECU.
Optionally, when the ECU software is developed and debugged, the ECU software is flushed into the first memory in the ECU.
Optionally, the ECU software is transferred to a factory production line, and the ECU software is written into the first memory in the ECU by using a refresh tool in the factory production line. Such as: when the ECU is produced in a production line, the ECU software is written into a first memory in the ECU at a software writing station of the production line in a factory.
The writing of the ECU software may be completed in a factory production line or in a scene other than a factory production line.
Since the non-factory data is included in the ECU software, the non-factory data is stored in the first memory in the ECU when the ECU software is flushed to the first memory in the ECU.
At step 305, the plant data is stored to a second memory in the ECU.
The second memory is a storage device provided in the ECU.
Optionally, the factory data is injected into the second memory in the ECU using a flash tool in a factory production line. Such as: brushing factory data into a second memory of the ECU at a factory data brushing station of a factory production line; typically, the factory data flashing station is different from the software flashing station.
Optionally, when the ECU software is developed and debugged, factory data determined by the factory production line is exported and transmitted to the ECU development department, and the ECU development department uses a writing tool to write the factory data into the second memory of the ECU.
The step of storing the plant data in the second memory of the ECU may be performed in a plant line, or may be performed in a scene other than the plant line.
It should be noted that step 305 may also be executed before step 304, which is not limited in this application.
According to the ECU data storage method provided by the embodiment of the application, ECU data are divided into factory data and non-factory data, storage devices in the ECU are distinguished, storages for storing the factory data and storages for storing the non-factory data are separated, the first storage is used for storing the non-factory data, the second storage is used for storing the factory data, the factory data are directly responsible for a factory production line, a development department and the factory production line are separated in the aspect of data, the problem that a conventional software data storage method cannot be obviously applied to all stages in the ECU production process is solved, the ECU development efficiency is improved, the transmission links of the middle ECU software data are reduced, and the consistency of the software data is guaranteed.
In an alternative embodiment based on the embodiment shown in fig. 3, the non-factory data includes calibration data and non-calibration data, the change frequency of the calibration data is greater than that of the non-calibration data, and the ECU software includes an application data module, an application module, a Flash driver module, and a Bootloader module.
Optionally, the ECU software includes a plurality of software logic modules, which are an Application Data module (Application Data), an Application module (Application), a Flash Driver module (Flash Driver), and a Bootloader module, respectively, as shown in fig. 2.
In the ECU software, each software logic module is composed of one or more sub-modules. In one example, an Application module (Application) is composed of 2 sub-modules, namely an Application1 sub-module and an Application2 sub-module.
The Bootloader module is a program and is used for starting the functions of guiding and refreshing ECU software.
The Flash Driver is a Driver for operating Flash. The first memory and the second memory are both Flash.
It should be noted that the Flash Driver and the Bootloader module are solidified together, or the Flash Driver and the Bootloader module are separate software logic modules respectively.
Application is a program that implements Application functions.
The Application Data is a Data set used by the Application.
The calibration Data is stored in an Application Data module (Application Data), and the non-calibration Data is stored in an Application module (Application).
In an alternative embodiment based on the embodiment shown in fig. 3, the step "package non-factory data into ECU software", i.e. the step 302 described above, can be implemented by the following steps:
step 3021, importing the calibration data into an application data module in the ECU software.
And step 3022, importing the non-calibration data into an application module in the ECU software.
It should be noted that step 3022 may also be performed before step 3021, which is not limited in this embodiment of the application.
When the calibration data needs to be updated, the calibration data is exported from an application data module in the ECU software by using a tool, then the calibration data is changed, and after the calibration data is changed, the changed calibration data is imported into the application data module of the ECU software by using the tool. Similarly, when the non-calibration data needs to be updated, the tool is used for exporting the non-calibration data from the application module in the ECU software, then the non-calibration data is changed, and after the non-calibration data is changed, the tool is used for importing the changed non-calibration data into the application module of the ECU software.
Optionally, the factory data at least includes a production line number, a production time, and a production lot.
Optionally, the non-factory data at least includes an ECU software version number, an ECU part number, and a vehicle VIN number.
In an alternative embodiment based on the embodiment shown in fig. 3, in order to avoid that the external device cannot read the non-factory data stored in the first memory from the ECU due to the first memory being erased after the EUC software refresh fails, the method further comprises the steps of:
and step 306, after the ECU is powered on, writing the non-factory data stored in the first memory into the second memory by operating ECU software in the ECU.
Optionally, by operating the ECU software in the ECU, the application module in the ECU software implements a function of writing the non-factory data stored in the first memory into the second memory.
After the non-factory data is written into the second memory, factory data and non-factory data are stored in the second memory.
It should be understood that the above examples are only for clarity of illustration and are not intended to limit the embodiments. Other variations and modifications will be apparent to persons skilled in the art in light of the above description. And are neither required nor exhaustive of all embodiments. And obvious variations or modifications of this invention are intended to be covered by the scope of the invention as expressed herein.
Claims (10)
1. An ECU data storage method, characterized in that the method comprises:
acquiring non-factory data which is data irrelevant to a factory production line;
packaging the non-factory data into ECU software;
acquiring factory data, wherein the factory data is production data determined by a factory production line;
writing the ECU software brush to a first memory in an ECU;
storing the plant data to a second memory in the ECU.
2. The method of claim 1, wherein the non-factory data comprises calibration data and non-calibration data, the frequency of change of the calibration data is greater than the frequency of change of the non-calibration data, the ECU software comprises an application data module, an application module, a Flash driver module, and a Bootloader module;
the packaging the non-factory data into ECU software comprises:
importing the calibration data into the application data module in the ECU software;
and importing the non-calibration data into the application module in the ECU software.
3. The method of claim 2, further comprising:
and after the ECU is powered on, writing the non-factory data stored in the first memory into the second memory by operating the ECU software in the ECU.
4. A method according to any one of claims 1 to 3, wherein said plant data includes at least production line number, production time, production lot.
5. The method of any of claims 1 to 3, wherein the non-factory data comprises at least an ECU software version number, an ECU part number, a vehicle-wide VIN code.
6. An ECU is characterized in that a storage device is arranged in the ECU, and the storage device comprises a first storage and a second storage;
factory data is stored in the second storage, and the factory data is production data determined by a factory production line;
ECU software is stored in the first storage, the ECU software comprises non-factory data, and the non-factory data are data irrelevant to a factory production line.
7. The ECU of claim 6, wherein the non-factory data comprises calibration data and non-calibration data, the frequency of alteration of the calibration data being greater than the frequency of alteration of the non-calibration data;
the ECU software comprises an application data module, an application module, a Flash drive module and a Bootloader module, wherein the non-calibration data is stored in the application module, and the calibration data is stored in the application data module.
8. The ECU of claim 7, wherein the non-factory data stored in the first memory is written to the second memory when the ECU is powered on.
9. The ECU of any one of claims 6 to 8, wherein the plant data includes at least a production line number, a production time, and a production lot.
10. The ECU of any one of claims 6 to 8, wherein the non-factory data includes at least an ECU software version number, an ECU part number, a vehicle-wide VIN code.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110503015.XA CN113407196A (en) | 2021-05-10 | 2021-05-10 | ECU data storage method and ECU |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110503015.XA CN113407196A (en) | 2021-05-10 | 2021-05-10 | ECU data storage method and ECU |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113407196A true CN113407196A (en) | 2021-09-17 |
Family
ID=77678105
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110503015.XA Pending CN113407196A (en) | 2021-05-10 | 2021-05-10 | ECU data storage method and ECU |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113407196A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706659A (en) * | 2009-11-13 | 2010-05-12 | 南京富士通南大软件技术有限公司 | Production process control system of vehicle-mounted device and realization method thereof |
| CN103377057A (en) * | 2012-04-20 | 2013-10-30 | 上海通用汽车有限公司 | System and method for refreshing software of user vehicle electronic control module |
| CN104951410A (en) * | 2014-03-27 | 2015-09-30 | 北京兆易创新科技股份有限公司 | Chip information access method and device |
| CN111177691A (en) * | 2019-11-29 | 2020-05-19 | 潍柴动力股份有限公司 | Method and device for setting ECU (electronic control Unit) whole vehicle function permission |
| CN111831479A (en) * | 2020-06-08 | 2020-10-27 | 东风汽车集团有限公司 | Vehicle-mounted computer data recovery method and system |
| CN112698857A (en) * | 2021-01-04 | 2021-04-23 | 潍柴动力股份有限公司 | Data flashing method and device |
| CN112770940A (en) * | 2018-10-15 | 2021-05-07 | 株式会社自动网络技术研究所 | Vehicle-mounted updating device, update processing program, program updating method, and vehicle-mounted updating system |
-
2021
- 2021-05-10 CN CN202110503015.XA patent/CN113407196A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706659A (en) * | 2009-11-13 | 2010-05-12 | 南京富士通南大软件技术有限公司 | Production process control system of vehicle-mounted device and realization method thereof |
| CN103377057A (en) * | 2012-04-20 | 2013-10-30 | 上海通用汽车有限公司 | System and method for refreshing software of user vehicle electronic control module |
| CN104951410A (en) * | 2014-03-27 | 2015-09-30 | 北京兆易创新科技股份有限公司 | Chip information access method and device |
| CN112770940A (en) * | 2018-10-15 | 2021-05-07 | 株式会社自动网络技术研究所 | Vehicle-mounted updating device, update processing program, program updating method, and vehicle-mounted updating system |
| CN111177691A (en) * | 2019-11-29 | 2020-05-19 | 潍柴动力股份有限公司 | Method and device for setting ECU (electronic control Unit) whole vehicle function permission |
| CN111831479A (en) * | 2020-06-08 | 2020-10-27 | 东风汽车集团有限公司 | Vehicle-mounted computer data recovery method and system |
| CN112698857A (en) * | 2021-01-04 | 2021-04-23 | 潍柴动力股份有限公司 | Data flashing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101366182B (en) | A nand flash memory controller exporting a nand interface | |
| US6550052B1 (en) | Software development framework for constructing embedded vehicle controller software | |
| CN102043680A (en) | Method and system for refreshing ECU (Electronic Control Unit) embedded software and downloading program | |
| CN111488165A (en) | Method and system for upgrading vehicle ECU through script | |
| WO2020140354A1 (en) | Full address calibration method and system supporting ultra-large calibration data volume | |
| JP2009008667A (en) | Test equipment and test method | |
| CN109002033A (en) | Automation calibration system and method based on UDS | |
| US20120038833A1 (en) | Television chip with a unique identification and method for writing the unique identification | |
| CN113407196A (en) | ECU data storage method and ECU | |
| CN202110528U (en) | ECU (electrical conversion unit) embedded type software refreshing and downloading programming system | |
| CN117524278A (en) | Dynamic random access memory compatible method, device and equipment | |
| CN112230848A (en) | NVM automatic configuration method, device and equipment | |
| JP6822928B2 (en) | Automatic method of generating test group identification information, programs, electronic controls, and vehicles | |
| CN115243047A (en) | Video compression method, device, equipment and medium | |
| JP4359327B2 (en) | Semiconductor integrated circuit device, IC card and inspection device | |
| CN101339812A (en) | Storage apparatus reading method, system and storage apparatus test apparatus | |
| CN101246741B (en) | System, device, method and packaging structure using flaw memory | |
| CN114942745A (en) | Automatic configuration method for UDS protocol stack of motor controller | |
| JP2012146360A (en) | Semiconductor integrated circuit and write processing method | |
| JP2005145247A (en) | Program writing system and method | |
| CN111580840A (en) | Method for realizing ECU (electronic control Unit) updating based on distributed memory management | |
| CN106143353B (en) | A kind of vehicle-mounted electronic control unit module method for refreshing and system | |
| CN112599172B (en) | Data writing method and device of electronic control unit and storage medium | |
| JPH05233844A (en) | Microcomputer | |
| CN116822480A (en) | Method for generating A2L file of diagnosis module of automobile controller |
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 |