CN116302067A - Verification method and device for compressed flash file, electronic equipment and storage medium - Google Patents

Verification method and device for compressed flash file, electronic equipment and storage medium Download PDF

Info

Publication number
CN116302067A
CN116302067A CN202310287629.8A CN202310287629A CN116302067A CN 116302067 A CN116302067 A CN 116302067A CN 202310287629 A CN202310287629 A CN 202310287629A CN 116302067 A CN116302067 A CN 116302067A
Authority
CN
China
Prior art keywords
controller
refreshed
version number
file
current
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
Application number
CN202310287629.8A
Other languages
Chinese (zh)
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.)
Chery Automobile Co Ltd
Original Assignee
Chery Automobile 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 Chery Automobile Co Ltd filed Critical Chery Automobile Co Ltd
Priority to CN202310287629.8A priority Critical patent/CN116302067A/en
Publication of CN116302067A publication Critical patent/CN116302067A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
    • G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
    • G06F11/1008—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices
    • G06F11/1012—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices using codes or arrangements adapted for a specific type of error
    • G06F11/104—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices using codes or arrangements adapted for a specific type of error using arithmetic codes, i.e. codes which are preserved during operation, e.g. modulo 9 or 11 check
    • 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)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Read Only Memory (AREA)

Abstract

The application relates to a verification method, a verification device, electronic equipment and a storage medium of a compressed flash file, wherein the method comprises the following steps: judging whether a controller to be refreshed exists in the current vehicle or not; if the current vehicle has a controller to be refreshed, acquiring a driving file of the controller to be refreshed, and performing application/calibration file refreshing on the controller to be refreshed based on the driving file; detecting whether a current fault code exists in the controller to be refreshed, and judging whether the version number of the current application/calibration file of the controller to be refreshed is a target version number; and if the controller to be refreshed does not have the current fault code and the version number of the current application/calibration file is the target version number, judging that the controller to be refreshed is qualified in the refresh. Therefore, the problem that the compression brushing and verification cannot be carried out in the related technology is solved, the integrity verification of the target file can be simply, conveniently and efficiently carried out, the refreshing efficiency is greatly improved, and the production line beat is shortened.

Description

Verification method and device for compressed flash file, electronic equipment and storage medium
Technical Field
The present invention relates to the field of information writing and refreshing technologies of vehicle-mounted devices, and in particular, to a method and apparatus for verifying a compressed writing and refreshing file, an electronic device, and a storage medium.
Background
With the continuous development and advancement of the intellectualization of automobiles, the number of vehicle-mounted controllers (ElectronicControl Unit, ECU) is increased in an explosive manner, controller software is more and more complex, refreshing demands are more and more, ECU updating is performed through an OBD (On Board Diagnostics, vehicle-mounted diagnosis system) port, and the ECU runs the software program to realize the special functions; using CAN (Controller Area Network ) protocol updates take a lot of time and bus limitations, load is also getting higher and higher, which cannot meet the demand.
In order to solve the problem of the CAN bus load, the method is compatible with the original CAN communication without increasing too high cost, CANFD (CAN with Flexible Data rate) is derived from the problem, the speed of the traditional CAN is increased by more than 4 times by using the CANFD protocol, the traditional CAN supports 8 data bytes at most, and the CANFD CAN support 64 data bytes at most. The CANFD protocol is used by the EPS/HCU/EMS/TCU and other nodes, the demand quantity of the T1D PHEV project line refreshing controllers is gradually increased, the line refreshing station beats cannot support large data packets, and the traditional refreshing mode cannot be applied, so that the refreshing mode of some controllers of the T1DPHEV project is updated to be a compression refreshing technology; the T1D PHEV project must be compression refreshed by the EMS/TCU controller, etc., subject to the beat of the production line. The compression is to perform special processing on repeated data, the data after compression cannot be divided according to addresses, and the addresses after compression cannot correspond to the checksum. The compressed refresh data does not contain address information, so the compressed refresh file format can only support the BIN format. How to check the validity of the compressed refreshing file is needed to be solved.
Disclosure of Invention
The application provides a verification method, a device, electronic equipment and a storage medium for a compressed writing file, which are used for solving the problem that the compression writing and verification cannot be carried out in the related technology, and can simply, conveniently and efficiently carry out integrity verification on a target file, greatly improve the refreshing efficiency and shorten the production line beat.
An embodiment of a first aspect of the present application provides a method for verifying a compressed flash file, including the following steps: judging whether a controller to be refreshed exists in the current vehicle or not; if the current vehicle has the controller to be refreshed, acquiring a driving file of the controller to be refreshed, and performing application/calibration file refreshing on the controller to be refreshed based on the driving file; detecting whether the current fault code exists in the controller to be refreshed, and judging whether the version number of the current application/calibration file of the controller to be refreshed is a target version number; and if the current fault code does not exist in the controller to be refreshed, and the version number of the current application/calibration file is the target version number, judging that the controller to be refreshed is qualified in the refresh.
Optionally, in some embodiments, before determining whether the current vehicle has the controller to be refreshed, the method further includes: scanning a vehicle identification code VIN of the current vehicle; judging whether the current vehicle is provided with the controller to be refreshed or not based on the VIN of the current vehicle; and if the current vehicle is configured with the controller to be refreshed, judging whether the current vehicle has the controller to be refreshed.
Optionally, in some embodiments, after determining whether the current vehicle is configured with the controller to be refreshed, further includes: and if the current vehicle is not provided with the controller to be refreshed, not executing the refresh operation.
Optionally, in some embodiments, the determining whether the version number of the current application/calibration file of the controller to be flushed is the target version number includes: removing the blank in the version number of the current application/calibration file to obtain a calibrated version number after removal; and if the rejected calibration version number is consistent with the preset version number, judging that the version number of the current application/calibration file of the controller to be refreshed is the target version number.
Optionally, in some embodiments, after determining whether the version number of the current application/calibration file of the controller to be flushed is the target version number, the method further includes: and if the version number of the current application/calibration file of the controller to be refreshed is not the target version number, judging that the refresh fails.
Optionally, in some embodiments, before determining that the brushing is successful, further comprising: and printing and recording the version number of the current application/calibration file.
An embodiment of a second aspect of the present application provides a verification apparatus for compressing a write-through file, including: the judging module is used for judging whether the current vehicle has a controller to be refreshed or not; the system comprises a refreshing module, a refreshing module and a refreshing module, wherein the refreshing module is used for acquiring a driving file of the controller to be refreshed when the current vehicle has the controller to be refreshed, and carrying out application/calibration file refreshing on the controller to be refreshed based on the driving file; the detection module is used for detecting whether the current fault code exists in the controller to be refreshed or not and judging whether the version number of the current application/calibration file of the controller to be refreshed is a target version number or not; and the judging module is used for judging that the controller to be refreshed is qualified in the process of being refreshed when the current fault code does not exist in the controller to be refreshed and the version number of the current application/calibration file is the target version number.
Optionally, in some embodiments, before determining whether the current vehicle has the controller to be refreshed, the determining module is further configured to: scanning a vehicle identification code VIN of the current vehicle; judging whether the current vehicle is provided with the controller to be refreshed or not based on the VIN of the current vehicle; and if the current vehicle is configured with the controller to be refreshed, judging whether the current vehicle has the controller to be refreshed.
Optionally, in some embodiments, after determining whether the current vehicle is configured with the controller to be refreshed, the determining module is further configured to: and if the current vehicle is not provided with the controller to be refreshed, not executing the refresh operation.
Optionally, in some embodiments, the detection module further includes: removing the blank in the version number of the current application/calibration file to obtain a calibrated version number after removal; and if the rejected calibration version number is consistent with the preset version number, judging that the version number of the current application/calibration file of the controller to be refreshed is the target version number.
Optionally, in some embodiments, after determining whether the version number of the current application/calibration file of the controller to be flushed is the target version number, the determining module is further configured to: and judging that the refreshing fails when the version number of the current application/calibration file of the controller to be refreshed is not the target version number.
Optionally, in some embodiments, before determining that the brushing is successful, the determining module is further configured to: and printing and recording the version number of the current application/calibration file.
An embodiment of a third aspect of the present application provides an electronic device, including: the system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the program to realize the verification method of the compressed flash file.
An embodiment of a fourth aspect of the present application provides a computer readable storage medium having stored thereon a computer program that is executed by a processor for implementing a verification method for a compressed flash file as described in the above embodiment.
Therefore, whether the current vehicle has the controller to be refreshed or not is judged, if the current vehicle has the controller to be refreshed, a driving file of the controller to be refreshed is obtained, application/calibration file refreshing is carried out on the controller to be refreshed based on the driving file, whether the current fault code exists in the controller to be refreshed or not is detected, whether the version number of the current application/calibration file of the controller to be refreshed is a target version number or not is judged, and if the current fault code does not exist in the controller to be refreshed, and the version number of the current application/calibration file is the target version number, the controller to be refreshed is judged to be refreshed. Therefore, the problem that the compression brushing and verification cannot be carried out in the related technology is solved, the integrity verification of the target file can be simply, conveniently and efficiently carried out, the refreshing efficiency is greatly improved, and the production line beat is shortened.
Additional aspects and advantages of the application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a flowchart of a method for verifying a compressed flash file according to an embodiment of the present application;
FIG. 2 is a flow chart of a method for verifying a compressed flash file according to one embodiment of the present application;
FIG. 3 is a block diagram of a verification device for compressed flash files according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present application and are not to be construed as limiting the present application.
The following describes a verification method, a device, an electronic device and a storage medium of a compressed flash file according to an embodiment of the present application with reference to the accompanying drawings. Aiming at the problem that the related technology mentioned in the background technology cannot carry out compression brushing and verification, the application provides a verification method of compression brushing files, in the method, whether a current vehicle has a controller to be brushed or not is judged, if the current vehicle has the controller to be brushed, a driving file of the controller to be brushed is obtained, application/calibration file brushing is carried out on the controller to be brushed based on the driving file, whether the current fault code exists in the controller to be brushed or not is detected, whether the version number of the current application/calibration file of the controller to be brushed is a target version number is judged, and if the current fault code does not exist in the controller to be brushed, and the version number of the current application/calibration file is the target version number, the controller to be brushed is judged to be qualified in brushing. Therefore, the problem that the compression brushing and verification cannot be carried out in the related technology is solved, the integrity verification of the target file can be simply, conveniently and efficiently carried out, the refreshing efficiency is greatly improved, and the production line beat is shortened.
Specifically, fig. 1 is a flow chart of a verification method for a compressed and written file according to an embodiment of the present application.
As shown in fig. 1, the verification method of the compressed flash file includes the following steps:
in step S101, it is determined whether or not there is a controller to be swiped for the current vehicle.
Specifically, the embodiment of the application can judge whether the vehicle is provided with the controller to be refreshed or not by scanning the vehicle VIN through the external device.
Optionally, in some embodiments, before determining whether the current vehicle has a controller to be refreshed, the method further includes: scanning a vehicle identification code VIN of a current vehicle; judging whether the current vehicle is provided with a controller to be refreshed or not based on the VIN of the current vehicle; and if the current vehicle is provided with the controller to be refreshed, judging whether the current vehicle has the controller to be refreshed.
Specifically, before judging whether a vehicle configures a controller to be refreshed, the embodiment of the application can scan the vehicle identification code VIN of the current vehicle through external equipment, the external equipment analyzes the software configuration information of the current vehicle, scans the whole vehicle controller of the current vehicle, judges the assembly condition of the whole vehicle controller of the current vehicle, and judges whether the controller to be refreshed exists in the current vehicle if the current vehicle configures the controller to be refreshed.
Optionally, in some embodiments, after determining whether the current vehicle is configured with the controller to be refreshed, further comprising: if the current vehicle is not configured with a controller to be refreshed, no refresh operation is performed.
It can be understood that the external device analyzes the software configuration information of the current vehicle, scans the whole vehicle controller of the current vehicle, and judges the assembly condition of the whole vehicle controller of the current vehicle, if the current vehicle is not provided with the controller to be refreshed, the refreshing operation cannot be executed, that is, the refreshing operation is not executed.
In step S102, if the current vehicle has a controller to be refreshed, a driving file of the controller to be refreshed is obtained, and application/calibration file refreshing is performed on the controller to be refreshed based on the driving file.
Specifically, if a to-be-refreshed controller which needs to be refreshed exists in the current vehicle, a driving file of the to-be-refreshed controller is obtained, and application/calibration file refreshing is performed on the to-be-refreshed controller based on the driving file, wherein the driving file downloading and the application/calibration file refreshing can be implemented according to an ECU (electronic control unit) boot loader and programming to achieve a specification of ECU bootloader and programming implementation specification.
In step S103, it is detected whether the controller to be refreshed has a current failure code, and it is determined whether the version number of the current application/calibration file of the controller to be refreshed is the target version number.
It should be noted that, the compressed data is sent by the external device for compression refreshing, and the decompressed data is actually brushed into the controller, and the checksum calculated by the device is inconsistent with the checksum of the decompressed data actually brushed into the controller, which may cause a consistency check error, so that the external device does not need to judge whether the (RID: 0XFF01/0XDA 04) is consistent with the checksum of the controller.
In the response message of $77 in the refresh flow, the controller is required to reply a check sum of one byte, the check sum calculated by the controller is decompressed, and the device can only calculate the check sum before decompression, so that the external device cannot compare the check sums. For a compressed refreshed controller, the $77 response message does not need to reply to a one byte checksum, and the external test equipment does not need to judge the checksum.
Specifically, before the controller does not write the calibration data, the current fault code U3000-51 is stored (the controller is not programmed), after the calibration data is written successfully, the U3000-51 is converted into the historical fault code, and the embodiment of the present application/calibration file version number of the controller to be written can be determined as the target version number by detecting whether the current fault code U3000-51 exists in the controller to be written.
Optionally, in some embodiments, determining whether the version number of the current application/calibration file of the controller to be flushed is the target version number includes: removing the blank in the version number of the current application/calibration file to obtain a calibrated version number after removal; and if the rejected calibration version number is consistent with the preset version number, judging that the version number of the current application/calibration file of the controller to be refreshed is the target version number.
Specifically, before the controller does not write the application/calibration data, the application/calibration version number defaults to fill 0xFF, and after the application/calibration data is written successfully, the application/calibration version number is automatically updated to the actual written application/calibration version number.
It should be noted that, when judging whether the version number of the current application/calibration file of the controller to be refreshed is the target version number, the blank space in the version number of the current application/calibration file needs to be removed, and the removed calibration version number is obtained.
Specifically, the external device reads the 8/32 byte (ASCII code) version number from the controller, and if the actual length of the version number is less than 8/32 byte, the device must be filled with a space (0 x 20) at the end, and the device must reject the space contained in the version number, for example:
the nominal version number (hexadecimal) the device reads from the controller:
54 31 41 58 46 2D 46 52 4D 30 30 30 30 31 31 56 30 31 20 20 20 20 20 20 20 20 20 20 2020 20 20
mark version number after space removal (hexadecimal):
54 31 41 58 46 2D 46 52 4D 30 30 30 30 31 31 56 30 31T1AXF-FRM000011V01
the device compares only the content of the non-space part of the application/calibration version number read from the controller with the refresh file name. And if the rejected calibration version number is consistent with the preset version number, judging that the version number of the current application/calibration file of the controller to be refreshed is the target version number.
In step S104, if the controller to be refreshed does not have the current fault code and the version number of the current application/calibration file is the target version number, it is determined that the controller to be refreshed is qualified for the refresh.
Specifically, when judging that the controller to be refreshed does not have the current fault code, the external device reads the application/calibration version number stored by the controller and compares the application/calibration version number with the version number maintained by the MES/refresh file name, if the application/calibration version number is consistent with the version number maintained by the MES, the external device is legal, and the controller to be refreshed is judged to be refreshed to be qualified.
Optionally, in some embodiments, after determining whether the version number of the current application/calibration file of the controller to be flushed is the target version number, further includes: and if the version number of the current application/calibration file of the controller to be refreshed is not the target version number, judging that the refresh fails.
Specifically, the external device reads the application/calibration version number stored by the controller, compares the application/calibration version number with the version number maintained by the MES/refresh file name, and if the version number is inconsistent with the version number maintained by the MES/refresh file name, can display that the refresh fails and the calibration version is illegal, report errors and exit refresh.
Optionally, in some embodiments, before determining that the brushing is successful, further comprising: the print records the version number of the current application/calibration file.
Specifically, before the successful writing is judged, the version number and the part number of the current application/calibration file are printed and recorded after the comparison of the application/calibration version numbers is qualified.
In order to enable those skilled in the art to further understand the verification method of the compressed flash file according to the embodiments of the present application, the following details are described in connection with specific embodiments.
It should be noted that, the controllers of the T1DPHEV project with compression refresh are HCU/EMS/TCU, these controllers are CANFD protocol nodes, the external devices are CAN protocols, the protocols supported by the external devices of the controllers are different, and the corresponding processing logic strategies are required by a Central Gateway (CGW) to establish diagnosis between the CAN devices and CANFD node controllers, as follows:
(1) The central gateway supports CAN and CANFD diagnosis and refresh respectively, namely, CAN and CANFD protocol are required to be compatible, external test equipment requests to send CAN requests, and the gateway replies to the CAN, otherwise, the external test equipment requests to send CANFD, and the gateway replies to the CANFD.
(2) When diagnosing other CANFD nodes of the whole vehicle, the central gateway intermediate conversion routing strategy is: when the command sent by the external agent of the OBD port of the whole vehicle is CANFD, the central gateway directly routes the CANFD to the target network segment, and if the command sent by the external test equipment of the OBD port of the whole vehicle is CAN, the gateway needs to convert the CAN into the CANFD to route the CANFD to the target network segment, and the network signal mirror function and the routing function processing strategy are the same.
(3) For the response of the CANFD node, the central gateway cannot unpack and pack, so that the response of the controller for the CANFD node requires that the response DLC is equal to 8 bytes, and the response supports DLC 2-15 byte dynamics.
After the external test equipment and the CANFD node controller are connected in a diagnosis mode, how to ensure the integrity and reliability of the file acquired by the equipment and refresh the operation belonging to a high security level is performed, at this time, the validity of the file needs to be ensured through a set of complete verification flow, and the integrity verification of the target file can be simply and efficiently performed through the verification method of the compressed and brushed file as shown in fig. 2.
As shown in fig. 2, fig. 2 is a flowchart of a method for verifying a compressed flash file according to an embodiment of the present application.
S201, the device scans VIN.
S202, judging whether the vehicle is equipped with the controller, if so, executing step S203, otherwise, executing step jump to execute step S204.
S203, judging whether the controller needs to be refreshed.
S204, no flushing operation is performed.
S205, the device selects a drive file.
S206, driving file downloading.
S207, the device selects an application/calibration file.
S208, application/calibration file writing.
S209, judging whether the current fault code exists in the U3000-51, if yes, executing the step S211, otherwise, executing the step S210.
S210, judging whether the application/calibration version numbers are matched, if yes, executing step S212, otherwise, executing step S211,
s211, judging that the brushing fails.
S212, printing an application/calibration file version number and a part number.
S213, judging that the brushing is successful.
According to the verification method for the compressed refreshing file, whether the current vehicle has the controller to be refreshed or not is judged, if the current vehicle has the controller to be refreshed, a driving file of the controller to be refreshed is obtained, application/calibration file refreshing is conducted on the controller to be refreshed based on the driving file, whether the current fault code exists in the controller to be refreshed or not is detected, whether the version number of the current application/calibration file of the controller to be refreshed is a target version number or not is judged, if the current fault code does not exist in the controller to be refreshed, and the version number of the current application/calibration file is the target version number, the controller to be refreshed is judged to be refreshed. Therefore, the problem that the compression brushing and verification cannot be carried out in the related technology is solved, the integrity verification of the target file can be simply, conveniently and efficiently carried out, the refreshing efficiency is greatly improved, and the production line beat is shortened.
Next, a verification device for a compressed write-through file according to an embodiment of the present application will be described with reference to the accompanying drawings.
FIG. 3 is a block diagram of a verification device for compressed flash files according to an embodiment of the present application.
As shown in fig. 3, the verification apparatus 10 for compressed flash files includes: a judgment module 100, a brushing module 200, a detection module 300 and a judgment module 400.
The judging module 100 is used for judging whether the current vehicle has a controller to be refreshed or not; the brushing module 200 is configured to obtain a driving file of a controller to be brushed when the current vehicle has the controller to be brushed, and perform application/calibration file brushing on the controller to be brushed based on the driving file; the detection module 300 is configured to detect whether a current fault code exists in the controller to be refreshed, and determine whether a version number of a current application/calibration file of the controller to be refreshed is a target version number; and the judging module 400 judges that the controller to be refreshed is qualified in the process that the controller to be refreshed does not have the current fault code and the version number of the current application/calibration file is the target version number.
Optionally, in some embodiments, before determining whether the current vehicle has a controller to be refreshed, the determining module 100 is further configured to: scanning a vehicle identification code VIN of a current vehicle; judging whether the current vehicle is provided with a controller to be refreshed or not based on the VIN of the current vehicle; and if the current vehicle is provided with the controller to be refreshed, judging whether the current vehicle has the controller to be refreshed.
Optionally, in some embodiments, after determining whether the current vehicle is configured with a controller to be swiped, the determining module 100 is further configured to: if the current vehicle is not configured with a controller to be refreshed, no refresh operation is performed.
Optionally, in some embodiments, the detection module 200 further comprises: removing the blank in the version number of the current application/calibration file to obtain a calibrated version number after removal; and if the rejected calibration version number is consistent with the preset version number, judging that the version number of the current application/calibration file of the controller to be refreshed is the target version number.
Optionally, in some embodiments, after determining whether the version number of the current application/calibration file of the controller to be flushed is the target version number, the determining module 400 is further configured to: and when the version number of the current application/calibration file of the controller to be refreshed is not the target version number, judging that the refresh fails.
Optionally, in some embodiments, before determining that the swipe is successful, the determination module 400 is further configured to: the print records the version number of the current application/calibration file.
It should be noted that the foregoing explanation of the embodiment of the method for verifying a compressed flash file is also applicable to the verification device for a compressed flash file in this embodiment, and will not be repeated here.
According to the verification device for the compressed refreshing file, whether the current vehicle has the controller to be refreshed or not is judged, if the current vehicle has the controller to be refreshed, the driving file of the controller to be refreshed is obtained, application/calibration file refreshing is carried out on the controller to be refreshed based on the driving file, whether the current fault code exists in the controller to be refreshed or not is detected, whether the version number of the current application/calibration file of the controller to be refreshed is a target version number is judged, if the current fault code does not exist in the controller to be refreshed, and the version number of the current application/calibration file is the target version number, the controller to be refreshed is judged to be refreshed. Therefore, the problem that the compression brushing and verification cannot be carried out in the related technology is solved, the integrity verification of the target file can be simply, conveniently and efficiently carried out, the refreshing efficiency is greatly improved, and the production line beat is shortened.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device may include:
memory 401, processor 402, and a computer program stored on memory 401 and executable on processor 402.
The processor 402 implements the verification method of the compressed flash file provided in the above embodiment when executing the program.
Further, the electronic device further includes:
a communication interface 403 for communication between the memory 401 and the processor 402.
A memory 401 for storing a computer program executable on the processor 402.
The memory 401 may include high speed RAM (Random Access Memory ) memory, and may also include non-volatile memory, such as at least one disk memory.
If the memory 401, the processor 402, and the communication interface 403 are implemented independently, the communication interface 403, the memory 401, and the processor 402 may be connected to each other by a bus and perform communication with each other. The bus may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component, external device interconnect) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 4, but not only one bus or one type of bus.
Alternatively, in a specific implementation, if the memory 401, the processor 402, and the communication interface 403 are integrated on a chip, the memory 401, the processor 402, and the communication interface 403 may perform communication with each other through internal interfaces.
The processor 402 may be a CPU (Central Processing Unit ) or ASIC (Application Specific Integrated Circuit, application specific integrated circuit) or one or more integrated circuits configured to implement embodiments of the present application.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the method for verifying a compressed flash file as described above.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or N embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more N executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the N steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable gate arrays, field programmable gate arrays, and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
Although embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.

Claims (10)

1. The verification method of the compressed flash file is characterized by comprising the following steps of:
judging whether a controller to be refreshed exists in the current vehicle or not;
if the current vehicle has the controller to be refreshed, acquiring a driving file of the controller to be refreshed, and performing application/calibration file refreshing on the controller to be refreshed based on the driving file;
detecting whether the current fault code exists in the controller to be refreshed, and judging whether the version number of the current application/calibration file of the controller to be refreshed is a target version number; and
and if the current fault code does not exist in the controller to be refreshed, and the version number of the current application/calibration file is the target version number, judging that the controller to be refreshed is qualified in the refresh.
2. The method of claim 1, further comprising, prior to determining whether the current vehicle has the controller to be refreshed:
scanning a vehicle identification code VIN of the current vehicle;
judging whether the current vehicle is provided with the controller to be refreshed or not based on the VIN of the current vehicle;
and if the current vehicle is configured with the controller to be refreshed, judging whether the current vehicle has the controller to be refreshed.
3. The method according to claim 2, further comprising, after determining whether the current vehicle is configured with the controller to be refreshed,:
and if the current vehicle is not provided with the controller to be refreshed, not executing the refresh operation.
4. The method of claim 2, wherein the determining whether the version number of the current application/calibration file of the controller to be flushed is a target version number comprises:
removing the blank in the version number of the current application/calibration file to obtain a calibrated version number after removal;
and if the rejected calibration version number is consistent with the preset version number, judging that the version number of the current application/calibration file of the controller to be refreshed is the target version number.
5. The method of claim 1, further comprising, after determining whether a version number of a current application/calibration file of the controller to be flushed is the target version number:
and if the version number of the current application/calibration file of the controller to be refreshed is not the target version number, judging that the refresh fails.
6. The method of claim 1, further comprising, prior to determining that the swipe is successful:
and printing and recording the version number of the current application/calibration file.
7. A verification apparatus for a compressed flash file, comprising:
the judging module is used for judging whether the current vehicle has a controller to be refreshed or not;
the system comprises a refreshing module, a refreshing module and a refreshing module, wherein the refreshing module is used for acquiring a driving file of the controller to be refreshed when the current vehicle has the controller to be refreshed, and carrying out application/calibration file refreshing on the controller to be refreshed based on the driving file;
the detection module is used for detecting whether the current fault code exists in the controller to be refreshed or not and judging whether the version number of the current application/calibration file of the controller to be refreshed is a target version number or not; and
and the judging module is used for judging that the controller to be refreshed is qualified in the process of being refreshed when the current fault code does not exist in the controller to be refreshed and the version number of the current application/calibration file is the target version number.
8. The apparatus of claim 7, wherein the determination module, prior to determining whether the current vehicle has the controller to be swiped, is further configured to:
scanning a vehicle identification code VIN of the current vehicle;
judging whether the current vehicle is provided with the controller to be refreshed or not based on the VIN of the current vehicle;
and if the current vehicle is configured with the controller to be refreshed, judging whether the current vehicle has the controller to be refreshed.
9. An electronic device, comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the program to implement the method of verifying a compressed flash file as claimed in any one of claims 1 to 6.
10. A computer readable storage medium having stored thereon a computer program, the program being executable by a processor for implementing a method of verifying a compressed flash file according to any one of claims 1-6.
CN202310287629.8A 2023-03-20 2023-03-20 Verification method and device for compressed flash file, electronic equipment and storage medium Pending CN116302067A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310287629.8A CN116302067A (en) 2023-03-20 2023-03-20 Verification method and device for compressed flash file, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310287629.8A CN116302067A (en) 2023-03-20 2023-03-20 Verification method and device for compressed flash file, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116302067A true CN116302067A (en) 2023-06-23

Family

ID=86826973

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310287629.8A Pending CN116302067A (en) 2023-03-20 2023-03-20 Verification method and device for compressed flash file, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116302067A (en)

Similar Documents

Publication Publication Date Title
JP2003131885A (en) Program writing system of vehicle mounted electronic control unit
CN108566407A (en) Method, its device and the electronic equipment of communication connection are established with system for monitoring pressure in tyre
CN110809755A (en) Electronic control system
CN112732310A (en) Firmware upgrading method, system, equipment and medium based on embedded boot partition
CN111522562B (en) Dishwasher software burning method, device and equipment thereof
CN113934898A (en) Fault code classified storage method, device, equipment and storage medium
CN115657521A (en) Method, device, vehicle and storage medium for analyzing CAN message data
CN113359657B (en) ECU diagnosis configuration code verification method and system and electronic control unit thereof
US6539338B1 (en) Self-diagnostic testing of a network interface adapter
CN116302067A (en) Verification method and device for compressed flash file, electronic equipment and storage medium
CN115964063A (en) Motor controller CPLD program upgrading method and device, motor controller and vehicle
JPH09293028A (en) Semiconductor storage device
JP4543317B2 (en) Nonvolatile memory data control method
CN116094531B (en) SENT signal receiving system and chip
CN111596199A (en) Test chip, integrated circuit test method and system and detection equipment
EP2045779B1 (en) Vehicular control apparatus and program storage medium
JP2005014743A (en) Failure part detection device for vehicle
JPH10320294A (en) Control unit and its abnormality detecting method
CN116048725A (en) Remote simulation method, device, electronic equipment and storage medium
CN116723124A (en) Internet of vehicles platform testing method and device, electronic equipment and storage medium
CN114968827B (en) Vehicle bus signal information verification method and system
CN117234560A (en) Remote upgrading method and device for automobile
CN117062066A (en) TBOX-based key filling method, TBOX-based key filling device, TBOX-based key filling vehicle and TBOX-based key storage medium
CN116257437A (en) ADAS system defect verification method and device based on real vehicle data reinjection
JPH1196082A (en) Memory rewriting device for vehicle

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