Controller flashing system and method, electronic equipment and storage medium

Abstract

The invention provides a controller flashing system and method, electronic equipment and a storage medium, and the system comprises a flashing management module which is used for storing whole vehicle version information, including a whole vehicle software version number and a software package of a controller, and is used for issuing a target software package of the controller to be flashed to a flashing module; the brushing module is used for responding to a brushing instruction of the controller to be brushed, brushing the controller to be brushed, and uploading the unique code of the part of the controller to be brushed and the brushed identification information to the brushing management module, so that the brushing management module determines a target whole vehicle software version number of the controller to be brushed; and the assembly management module is used for determining whether the loading version of the controller to be brushed is correct or not according to the target whole vehicle software version number and the actual whole vehicle software version number of the assembly vehicle of the controller to be brushed. The loading quality of the to-be-brushed controller is monitored through software version verification of the loading controller, so that the brushing accuracy of the controller is ensured, and the production quality of the whole vehicle is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle upgrade technology, and in particular to a controller flashing system, method, electronic device and storage medium. Background Art

[0002] With the rapid development of the automotive industry, especially in the era of intelligent and electrified development, the number of controllers in automotive control systems has increased dramatically. In order to improve the entertainment, comfort, and power of the vehicle, the controller software is upgraded more frequently. When one or more controllers are upgraded, the traditional flashing method is for the parts supplier to complete the development and testing, and then provide the software package to the vehicle manufacturer. Then, the vehicle manufacturer needs to further test the new software package and apply it to the vehicles on the production line.

[0003] In the related technology, the parts supplier releases the updated parts to the vehicle manufacturer, and then the vehicle manufacturer conducts trial assembly and batch installation. This involves multiple links, including the delivery, flashing and final assembly confirmation of the software package. In actual operation, this controller flashing method still has disadvantages. First, from the delivery, flashing and assembly confirmation of the software package, the controller maintenance time is slow; second, the delivery of the software package relies on manual copying to the flashing device. If the wrong version of the software package is used, there will be flashing errors. In addition, after the controller is flashed, it is released to the production line, and the assembly personnel use the flashing mark to check whether the vehicle installation version is correct. There are personnel judgment errors, especially in the process of software version upgrade, there is a situation of wrong installation of the corresponding version controller, resulting in a high risk of flashing errors and assembly errors, thereby affecting the function and quality of the whole vehicle; then, the number of corresponding versions of the flashing controller depends on personnel statistics, and it is impossible to display the number of flashed, installed and flashed inventory of each version of each flashing controller in real time, and there is a lack of effective tracking and management mechanism.

[0004] Therefore, it is necessary to propose a controller flashing solution to achieve more efficient software maintenance, more sophisticated version management, and a more reliable assembly confirmation mechanism, thereby improving the quality and efficiency of vehicle production. Summary of the invention

[0005] In view of the above-mentioned shortcomings of the prior art, the present application discloses a controller flashing system, method, electronic device and storage medium, which are used to solve the technical problem of poor accuracy of controller flashing in the prior art.

[0006] In a first aspect, the present application provides a controller flashing system, the system comprising: a flashing management module, storing at least one vehicle version information, the vehicle version information comprising the vehicle software version number and the software package of at least one controller in the vehicle, for sending the target software package of the controller to be flashed to the flashing module; the flashing module, for responding to the flashing instruction of the controller to be flashed, flashing the controller to be flashed according to the target software package, and uploading the component unique code of the controller to be flashed and the identification information after flashing to the flashing management module, so that the flashing management module determines the target vehicle software version number corresponding to the controller to be flashed, the component unique code being carried in the flashing instruction; an assembly management module, for performing a flashing version check on the controller to be flashed in the assembled vehicle according to the target vehicle software version number and the actual vehicle software version number of the assembled vehicle of the controller to be flashed, to determine whether the installed version of the controller to be flashed is correct.

[0007] In one embodiment of the present application, the flashing module includes multiple flashing devices, each flashing device is used to implement the flashing of a controller; the flashing device includes: a pre-flash verification unit, used to analyze the first identification format of the controller to be flashed before flashing, and match the first identification format with the standard identification format maintained by the flashing device, and perform a flashing device verification on the controller to be flashed; a post-flash verification unit, used to analyze the second identification format of the controller to be flashed after flashing, and match the second identification format with the standard identification format segment, and perform a flashing result verification on the controller to be flashed.

[0008] In one embodiment of the present application, the assembly management module includes: an acquisition unit, which is used to respond to a version verification instruction, retrieve the target vehicle software version number from the flashing management module according to the component unique code, and determine the actual vehicle software version number according to the vehicle identification code of the assembled vehicle, and the version verification instruction carries the component unique code and the vehicle identification code; a version verification unit, which is used to match the target vehicle software version number with the actual vehicle software version number, if the match is successful, it is determined that the installed version of the controller to be flashed is correct, if the match fails, it is determined that the installed version of the controller to be flashed is wrong.

[0009] In one embodiment of the present application, the flash management module is also used to record the number of the component unique codes uploaded from the flash module as the flash quantity of the controller to be flashed; the assembly management module is also used to record the loading quantity of the controller to be flashed and send it to the flash management module, so that the flash management module calculates the difference between the flash quantity and the loading quantity, obtains the flash inventory of the controller to be flashed, and displays the flash quantity and the flash inventory of the controller to be flashed in real time.

[0010] In one embodiment of the present application, the vehicle version information also includes identification information of at least one controller in the vehicle before flashing; the flashing management module is used to respond to the software package sending instruction of the controller to be flashed, match the standard identification information of the controller to be flashed with the identification information before flashing, determine the target software package, and determine the target transmission path according to the standard identification information and the transmission path mapping table, so as to send the target software package to the target flashing device through the target transmission path, and the software package sending instruction carries the standard identification information.

[0011] In one embodiment of the present application, the flash management module is used to match the identification information after flashing with the identification information before flashing, determine the target vehicle software version number, and store the component unique code in association with the target vehicle software version number.

[0012] In one embodiment of the present application, the system also includes: a version maintenance module for managing vehicle version information of various vehicle models, each vehicle version information includes the vehicle software version number and identification information of at least one controller before flashing under the vehicle software version number, and the software package of at least one controller. If any vehicle version information is updated, the updated vehicle version information will be sent to the flash management module.

[0013] In a second aspect, the present application provides a controller flashing method, the method comprising: obtaining a target software package of the controller to be flashed; flashing the controller to be flashed according to the target software package, and reading the component unique code and identification information of the controller to be flashed after flashing; determining a target vehicle software version number corresponding to the controller to be flashed according to the component unique code and the identification information after flashing, and obtaining an actual vehicle software version number of the vehicle in which the controller to be flashed is assembled; performing a flashing version check on the controller to be flashed in the assembled vehicle according to the target vehicle software version number and the actual vehicle software version number, to determine whether the installed version of the controller to be flashed is correct.

[0014] In a third aspect, the present application provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the electronic device implements the controller flashing method described in the second aspect.

[0015] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor of a computer, the computer executes the controller flashing method described in the second aspect.

[0016] As described above, the controller flashing system, method, electronic device and storage medium provided by the embodiments of the present application have the following beneficial effects:

[0017] The system integrates a flash management module, a flash module and an assembly management module, wherein the flash management module stores at least one vehicle version information, the vehicle version information including the vehicle software version number and the software package of at least one controller in the vehicle, and sends the target software package of the controller to be flashed to the flash module through the flash management module, so that the flash module responds to the flash instruction carrying the component unique code of the controller to be flashed, flashes the controller to be flashed according to the target software package, and uploads the component unique code of the controller to be flashed and the identification information after flashing to the flash management module, so that the flash management module determines the target software package corresponding to the controller to be flashed. Mark the vehicle software version number, and finally use the assembly management module to verify the flashing version of the controller to be flashed in the assembled vehicle according to the target vehicle software version number and the actual vehicle software version number of the assembled vehicle of the controller to be flashed. In this way, in addition to personnel confirmation, the installation of the flashed controller adds version verification of the flashed version of the corresponding controller. Through the vehicle software version number corresponding to the controller to be flashed and the vehicle software version number of the assembled vehicle, it is ensured that the installed version of the controller to be flashed is correct, so as to achieve the purpose of flashing version error prevention, ensure the accuracy of controller flashing, and ensure that the vehicle is assembled with the correct version of the controller, thereby improving the quality of vehicle production.

[0018] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0020] Figure 1 is a schematic diagram of an implementation environment of a controller flashing system shown in an exemplary embodiment of the present application;

[0021] Figure 2 is a block diagram of a controller flashing system shown in an exemplary embodiment of the present application;

[0022] Figure 3 is a block diagram of another controller flashing system shown in an exemplary embodiment of the present application;

[0023] Figure 4is a flowchart of a method for issuing a software package shown in an exemplary embodiment of the present application;

[0024] Figure 5 is a flowchart of a flash version verification method shown in an exemplary embodiment of the present application;

[0025] Figure 6 is a flow chart of a method for calculating the flush inventory quantity shown in an exemplary embodiment of the present application;

[0026] Figure 7 is a flow chart of a controller flashing method shown in an exemplary embodiment of the present application;

[0027] Figure 8 It is a structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0028] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0029] It should be noted that the illustrations provided in the following embodiments are only used to illustrate the basic concept of the present application in a schematic manner, and therefore the illustrations only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the form, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0030] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0031] First of all, it should be noted that when one or more controllers are undergoing software upgrades, the traditional flashing method is for the parts supplier to complete the development and testing and then provide the software package to the vehicle manufacturer. Then, the vehicle manufacturer needs to further test the new software package and apply it to the vehicles on the production line. This method involves multiple links, including the delivery, flashing, and final assembly confirmation of the software package. However, the inventor of this application has found that this controller flashing method still has disadvantages in actual operation. First, the controller maintenance time is slow from the delivery and flashing of the software package to the assembly confirmation. Secondly, the delivery of the software package relies on manual copying to the flashing device. If the wrong version of the software package is used, there will be flashing errors. In addition, after the controller is flashed and released to the production line, the assembly personnel will use the flashing mark to check whether the vehicle installation version is correct. There are personnel judgment errors, especially in the process of software version upgrade, there is a situation of wrong installation of the corresponding version controller, resulting in a high risk of flashing errors and assembly errors, thus affecting the function and quality of the whole vehicle. Then, the number of corresponding versions of the flashing controller depends on personnel statistics, and it is impossible to display the flashed number, installed number and flashed inventory of each version of each flashing controller in real time, and there is a lack of effective tracking and management mechanism. Therefore, the quality and efficiency of vehicle production are affected.

[0032] Therefore, see Figure 1 , Figure 1 FIG. 1 is a schematic diagram of an implementation environment of a controller flashing system shown in an exemplary embodiment of the present application. Figure 1 As shown, the implementation environment may include a controller flashing system 110 and a computer device 120. The controller flashing system 110 may be set in the computer device 120 for flashing the controller. The computer device 120 may be at least one of a desktop graphics processing unit (GPU) computer, a GPU computing cluster, a neural network computer, etc. The controller flashing system 110 integrates a flashing management module, a flashing module and an assembly management module to perform a flashing version check on the controller to be flashed in the assembled vehicle. In this way, in addition to personnel confirmation, the flashing controller is loaded on the vehicle, and the version check of the flashed version of the corresponding controller is added. By comparing the vehicle software version number corresponding to the controller to be flashed with the vehicle software version number of the assembled vehicle, the installed version of the controller to be flashed is ensured to be correct, so as to achieve the purpose of flashing version error prevention, ensure the accuracy of controller flashing, and ensure that the vehicle is assembled with the correct version of the controller, thereby improving the quality of vehicle production.

[0033] See also Figure 2 , Figure 2 is a block diagram of a controller flashing system shown in an exemplary embodiment of the present application. The system can be applied to Figure 1The implementation environment shown is a schematic diagram. It should be understood that the system may also be applicable to other exemplary implementation environments, and this embodiment does not limit the implementation environment to which the system is applicable.

[0034] like Figure 2 As shown, in an exemplary embodiment, the controller flashing system 200 includes at least a flashing management module 210, a flashing module 220 and an assembly management module 230, which are described in detail as follows:

[0035] The flash management module 210 stores at least one vehicle version information, which includes the vehicle software version number and the software package of at least one controller in the vehicle, and is used to send the target software package of the controller to be flashed to the flash module 220.

[0036] In this embodiment, the flash management module 210 uniformly manages the flashing of each controller in various vehicle models. Therefore, the flash management module 210 stores at least one vehicle version information corresponding to the flashing of the controller in at least one vehicle model. In addition, the vehicle software version number is the code of the unified set of software and hardware versions of all controllers of a vehicle model. If the information of one or more controllers in the set changes, the vehicle software version number changes.

[0037] In one embodiment, see Figure 3 , Figure 3 FIG. 1 is a block diagram of another controller flashing system shown in an exemplary embodiment of the present application. Figure 3 As shown, the controller flashing system 200 also includes: a version maintenance module 240, which is used to manage vehicle version information of various vehicle models. Each vehicle version information includes the vehicle software version number and identification information of at least one controller before flashing under the vehicle software version number, and the software package of at least one controller. If any vehicle version information is updated, the updated vehicle version information will be sent to the flashing management module 210.

[0038] The identification information of each controller before flashing includes at least the controller device number, the controller software version number, the controller hardware version number and the controller vendor code before flashing the controller.

[0039] It should be noted that the vehicle version information includes the vehicle software version number, the identification information before the controller is flashed, and the software package of the controller. Among them, the identification information and software package of the controller are still developed and tested by the parts supplier and then provided to the vehicle manufacturer. The vehicle manufacturer tests it through the corresponding controller product engineer. After the test is passed, the version maintenance module 240 is used to maintain and take effect on the controller feature information such as the controller device number, the controller software version number, the controller hardware version number, the controller supplier code and the controller software package. The feature information of each controller is maintained and taken effect by the corresponding controller product engineer. When one or more controller information corresponding to the vehicle software version number changes, its vehicle software version number changes, that is, the vehicle version changes. Each vehicle software version number is maintained and taken effect by the software version engineer. After the vehicle software version number is updated and released, a new vehicle version information is formed, which is sent to the flash management module 210 by the version maintenance module 240. The flash management module 210 stores it in the database and then flashes the controller.

[0040] It should also be noted that in the version maintenance module 240, the vehicle version information of various vehicle models and various software versions is maintained.

[0041] In this embodiment, the controller software package is no longer transmitted by manual download or USB flash drive copying, but is transmitted through the controller flashing system. The software of the corresponding controller is maintained by the version maintenance module 240, and after it takes effect, it is directly sent to the flashing management module 210. In this way, the controller software package is obtained legally. The flashing management module 210 can download the controller software package in a timely and efficient manner, while avoiding the problem of software package transmission errors during the transmission process between personnel, thereby ensuring the accuracy of the controller software package transmission process.

[0042] The flashing module 220 is used to respond to the flashing instruction of the controller to be flashed, flash the controller to be flashed according to the target software package, and upload the component unique code of the controller to be flashed and the identification information after flashing to the flashing management module 210, so that the flashing management module 210 determines the target vehicle software version number corresponding to the controller to be flashed, and the flashing instruction carries the component unique code.

[0043] It should be noted that when the flash management module 210 sends the target upgrade package of the controller to be flashed to the flash module 220, the flash module 220 issues a flashing prompt, and then the controller to be flashed can be flashed.

[0044] In addition, the flashing module 220 includes multiple flashing devices, each of which is used to implement the flashing of a controller, that is, the flashing device and the controller type are in a one-to-one correspondence. Therefore, the flashing management module 210 sends the target upgrade package of the controller to be flashed to the corresponding flashing device in the flashing module 220, and after the flashing device issues a flashing prompt, the controller to be flashed can be flashed.

[0045] In this embodiment, if it is necessary to flash the controller to be flashed, the controller to be flashed must be flashed after the corresponding flashing device scans the component unique code of the controller to be flashed. After the flashing device scans the component unique code of the controller to be flashed, it generates and executes the flashing instruction of the controller to be flashed. The flashing instruction carries the component unique code, and the controller to be flashed is flashed according to the target software package. After the flashing is completed, the flashing device uploads the component unique code of the controller to be flashed and the identification information after the flashing to the flashing management module 210, so that the flashing management module 210 locks the target vehicle software version number corresponding to the controller to be flashed. Among them, the identification information after the flashing includes at least the control device number, controller software version number, controller hardware version number and controller vendor code of the controller to be flashed after the flashing.

[0046] For example, if controller A needs to be flashed, the corresponding controller A flashing device needs to scan the unique code of the components of controller A before flashing controller A. After the controller flashing device A scans the unique code of the components of controller A, it generates and executes the flashing instruction of controller A, which carries the unique code of the components of controller A, and flashes controller A according to the target software package. After the flashing is completed, the controller flashing device A uploads the unique code of the components of controller A and the identification information after the flashing to the flashing management module 210, so that the flashing management module 210 locks the target vehicle software version number corresponding to controller A.

[0047] In one embodiment, the vehicle version information also includes identification information of at least one controller before flashing; the flashing management module 210 is used to respond to the software package sending instruction of the controller to be flashed, match the standard identification information of the controller to be flashed with the identification information before flashing, determine the target software package, and determine the target transmission path according to the standard identification information and the transmission path mapping table, so as to send the target software package to the target flashing device through the target transmission path, and the software package sending instruction carries the standard identification information.

[0048] It should be noted that the flash management module 210 stores the vehicle version information of different models, and the vehicle version information of the same model includes the software package of at least one controller in the vehicle. Therefore, when the controller to be flashed needs to be flashed, the target software package corresponding to the controller to be flashed needs to be locked.

[0049] In this embodiment, the standard identification information corresponding to the controller to be flashed is matched with the identification information of each controller before flashing in the vehicle version information maintained in the flashing management module 210, and the target software package corresponding to the controller to be flashed is locked and sent from the flashing management module 210 to the flashing module 220. In this way, it can be ensured that the software package flashed to the controller to be flashed is correct, thereby improving the accuracy of controller flashing.

[0050] As a possible embodiment, in the flashing device, the target software package is automatically decompressed, the driver APP and the application APP are obtained after decompression, and then the controller to be flashed is flashed.

[0051] See also Figure 4 , Figure 4 FIG. 1 is a flowchart of a method for delivering a software package according to an exemplary embodiment of the present application. Figure 4 As shown, the version maintenance module 240 first issues the updated vehicle version information to the flash management module 210, that is, the vehicle version information includes: vehicle software version number, control device number, controller software version number, controller hardware version number, controller supplier code and controller software package. In the flash management module 210, after receiving the vehicle version information issued by the version maintenance module 240, it is stored, and the vehicle software version number, control device number, controller software version number, controller hardware version number and controller supplier code of each controller are maintained to be effective to the flash device, and each controller software package is transmitted to the designated path of the corresponding flash device to complete the software package issuance. The controller software package is obtained in the form of online maintenance, and through efficient software maintenance and fine version management, the influence of the traditional flash device manually transmitting the wrong software package is eliminated, and the upstream software package information is quickly and stably transmitted.

[0052] In one embodiment, the flashing device includes: a pre-flash verification unit, which is used to analyze a first identification format of a controller to be flashed before flashing, and match the first identification format with a standard identification format maintained by the flashing device, and perform a flashing device verification on the controller to be flashed; a post-flash verification unit, which is used to analyze a second identification format of the controller to be flashed after flashing, and match the second identification format with a standard identification format segment, and perform a flashing result verification on the controller to be flashed.

[0053] In this embodiment, the flashing device performs a flashing device verification before flashing, that is, matches the first identification format of the controller to be flashed before flashing with the standard identification format maintained by the flashing device. If the match is successful, the controller to be flashed is flashed; if the match fails, an error is reported and subsequent flashing is not performed to ensure that the controller type flashed by the flashing device is consistent with the controller type of the controller to be flashed, so that the controller to be flashed is accurately flashed; the flashing device performs a flashing result verification after flashing, that is, matches the second identification format of the controller to be flashed after flashing with the standard identification format segment. If the match is successful, the flashing is successful; if the match fails, an error is reported to ensure that the flashing operation of the controller to be flashed is successful.

[0054] In this way, by combining the flashing device verification before flashing and the flashing result verification after flashing, the flashing quality monitoring of the controller to be flashed is achieved, thereby improving the reliability of the flashing of the controller to be flashed.

[0055] In addition, the flashing device establishes communication with the controller to be flashed according to the unique code of the components of the controller to be flashed, and by scanning the unique code of the components of the controller to be flashed, the flashing device can read the identification information of the controller to be flashed itself. In the pre-flash verification unit, the control device number, controller hardware version number and controller vendor code of the controller to be flashed before flashing are read, and the format of these identifications is analyzed to obtain the first identification format; in the post-flash verification unit, the control device number, controller hardware version number, controller vendor code and controller software version number of the controller to be flashed after flashing are read, and the format of these identifications is analyzed to obtain the second identification format. It should be noted that the identification information of the controller to be flashed follows a certain format before and after flashing, and the flashing is successful.

[0056] For example, after the controller A flashing device scans the unique code of the components of controller A, it reads the part number of controller A, the hardware version number of controller A, and the supplier code of controller A, and then analyzes the identification format and matches it with the identification format maintained by the flashing device of controller A. If the match fails, an error is reported and no subsequent flashing is performed. After the match succeeds, subsequent flashing is automatically performed. After the flashing of controller A is completed, the part number, hardware version number, supplier code, and software version number of the flashed controller A are read and compared with the information maintained by the flashing device of controller A to match the identification format. If the match fails, an error is reported. If the match succeeds, the identification information of the controller to be flashed and its unique code of components are uploaded to the flashing management module 210.

[0057] In one embodiment, the flash management module 210 is used to match the identification information after flashing with the identification information before flashing, determine the target vehicle software version number, and store the component unique code in association with the target vehicle software version number.

[0058] It should be noted that multiple vehicle software version numbers are stored in the flashing management module 210. Therefore, in this embodiment, the identification information of the controller to be flashed after flashing uploaded by the flashing module 220 is matched with the identification information before flashing, the target vehicle software version corresponding to the controller to be flashed is locked, and the unique code of the component of the controller to be flashed is associated with the corresponding target vehicle software version number. This is beneficial to the subsequent vehicle installation version inspection of the controller to be flashed.

[0059] The assembly management module 230 is used to perform a flashing version check on the controller to be flashed in the assembled vehicle according to the target vehicle software version number and the actual vehicle software version number of the assembled vehicle of the controller to be flashed, and determine whether the installed version of the controller to be flashed is correct.

[0060] In this embodiment, the assembly management module 230 performs a flashing version check on the controller to be flashed in the assembled vehicle by comparing the target vehicle software version number with the actual vehicle software version number to ensure the accuracy of the installed version of the controller to be flashed, thereby ensuring the vehicle production quality.

[0061] Specifically, the assembly management module 230 includes: an acquisition unit, which is used to respond to a version verification instruction, retrieve the target vehicle software version number from the flashing management module 210 according to the component unique code, and determine the actual vehicle software version number according to the vehicle identification code of the assembled vehicle, and the version verification instruction carries the component unique code and the vehicle identification code; a version verification unit, which is used to match the target vehicle software version number with the actual vehicle software version number. If the match is successful, it is determined that the installed version of the controller to be flashed is correct. If the match fails, it is determined that the installed version of the controller to be flashed is incorrect.

[0062] In this embodiment, the version verification instruction carries the component unique code of the controller to be flashed, and the acquisition unit can retrieve the corresponding target vehicle software version number from the flash management module 210 according to the component unique code, that is, the target vehicle software version number corresponding to the controller to be flashed. In addition, when the controller to be flashed is installed on the vehicle, the actual vehicle software version number of the corresponding assembled vehicle is maintained and generated by the assembly management module 230, and the actual vehicle software version number can be obtained according to the vehicle identification code of the assembled vehicle. The version verification instruction carries the vehicle identification code of the vehicle on which the controller to be flashed is installed, thereby obtaining the actual vehicle software version number corresponding to the controller to be flashed.

[0063] In this embodiment, in addition to personnel confirmation when loading the flashed controller, verification of the flashed version of the corresponding controller is added to ensure that the installed version of the controller to be flashed is correct, thereby achieving the purpose of flashing version error prevention, ensuring the accuracy of controller flashing, and ensuring that the vehicle is assembled with the correct version of the controller, thereby improving the quality of vehicle production.

[0064] For example, after controller A is installed on a vehicle, the assembly management module 230 maintains and generates the actual vehicle software version number of the assembled vehicle. The assembly management module 230 scans the component unique code and vehicle identification code of controller A, and generates a version verification instruction carrying the component unique code and vehicle identification code. In response to the version verification instruction, the acquisition unit of the assembly management module 230 obtains the corresponding target vehicle software version number from the flash management module 210 according to the component unique code, and obtains the actual vehicle software version number maintained in the assembly management module 230 according to the vehicle identification code. The version verification unit determines whether the target vehicle software version number of controller A matches the actual vehicle software version number of the assembled vehicle. If they do not match, an error is reported. If they match, the software version of controller A assembled on the vehicle is correct.

[0065] In a possible embodiment, the assembly management module 230 may be a MOM (Manufacturing Operation Management) system, and a subsystem under the MOM system performs verification of the flashed version of the controller to be flashed in the assembled vehicle.

[0066] See also Figure 5 , Figure 5 FIG. 1 is a flowchart of a flash version verification method shown in an exemplary embodiment of the present application. Figure 5 As shown, first, in the assembly management module 230, the VIN (Vehicle Identification Number) of the assembled vehicle and the component unique code of the controller to be flashed are obtained by scanning, and then, the corresponding target vehicle software version number is obtained from the flashing management module 210 through the component unique code, and the actual vehicle software version number corresponding to the controller to be flashed is obtained from the maintained vehicle software version number according to the vehicle identification code. The correctness of the flashing version is determined by the matching result of the target vehicle software version number and the actual vehicle software version number. If correct, subsequent assembly is carried out. If wrong, the flashed controller in the assembled vehicle is replaced.

[0067] In a possible embodiment, the assembly management module 230 further includes: a version number generating unit, which is used to generate an actual vehicle software version number according to the production time of the vehicle identification code in the assembled vehicle, or to generate an actual vehicle software version number according to a preset vehicle identification code.

[0068] In this embodiment, the actual vehicle software version number can be maintained according to the VIN production time. For example, the maintenance rule is to generate AA from 2023:10:10:15:00:00 to 2024:10:10:15:00:00. If the vehicle is generated during this period, the actual vehicle version number is: "AA"; it is also possible to use a preset method to bind the specified VIN to other vehicle software version numbers. In this way, errors caused by untimely time maintenance can be avoided.

[0069] In one embodiment, the flash management module 210 is also used to record the number of unique component codes uploaded from the flash module 220 as the flash quantity of the controllers to be flashed; the assembly management module 230 is also used to record the loading quantity of the controllers to be flashed and send it to the flash management module 210, so that the flash management module 210 calculates the difference between the flash quantity and the loading quantity, obtains the flash inventory of the controllers to be flashed, and displays the flash quantity and the flash inventory of the controllers to be flashed in real time.

[0070] In this embodiment, the flash management module 210 will record the number of unique component codes uploaded from the flash module 220 as the flash quantity of the controllers to be flashed, and the assembly management module 230 will record the loaded quantity of the controllers to be flashed and send it to the flash management module 210. The flash management module 210 can obtain the flash inventory of the controllers to be flashed by calculating the difference between the flash quantity and the loaded quantity, and display the flash quantity and the flash inventory of the controllers to be flashed. In this way, the controller flash inventory is displayed by comparing and associating the flashed and loaded controllers, which is conducive to the reasonable arrangement of the flashing work.

[0071] It should be understood that the flash management module 210 records the flash quantity of various controllers and various software versions. After the final assembly, the controller performs a scan of the unique code of the controller parts and the VIN of the assembly vehicle. By collecting the flash quantity of each controller + each software version, and the number of each controller + each software version installed collected by the assembly management module 230, a correlation calculation is performed to display the flash inventory of each controller + each software version in real time. According to the flash inventory, it is convenient to arrange the flash work of various controllers and various software versions in real time, such as the start and stop of controller flashing, the allocation of personnel for each flashing equipment, etc. In the traditional case of manual confirmation of the flashing controller inventory, the system displays the flashing inventory status of each controller in real time, which improves the efficiency and real-time performance of the controller flashing.

[0072] For example, after final assembly, controller A will scan the unique code of the parts and the VIN of the assembled vehicle. The flashing management module 210 records the unique code of the parts uploaded by the flashing device of controller A and counts the quantity. The assembly management module 230 records the unique code of the parts that controller A has installed on the vehicle and counts the quantity and transmits it to the flashing management module 210. The flashing management module 210 calculates the number of unique codes of parts that have been flashed by controller A (i.e., the flashing quantity) - the number of unique codes of parts that have been installed on the vehicle (i.e., the installed quantity) = the number of unique codes of parts that have been flashed but not installed on the vehicle (i.e., the flashing inventory). Finally, the flashing management module 210 displays the flashing quantity and flashing inventory of controller A.

[0073] See also Figure 6 , Figure 6 FIG. 1 is a flowchart of a method for calculating the flush inventory quantity shown in an exemplary embodiment of the present application. Figure 6 As shown, various controller flashing devices will upload the unique code of the controller components and the identification information after flashing to the flashing management module 210. Therefore, the flashing management module 210 can record the number of unique codes of the controller components and determine the flashing quantity of the controllers. The assembly management module 230 transmits the loading quantity of the controllers to the flashing management module 219. The flashing management module 210 associates the flashing quantity and loading quantity of each controller based on the unique code of the components of each controller, calculates the flashing inventory of each controller, and displays the flashing quantity and flashing inventory of each controller.

[0074] It should also be noted that the controller flashing system can simultaneously flash multiple controllers on the production line, that is, flash various controllers in different vehicle models. The system is an external flashing system that independently performs flashing control outside the vehicle, that is, after flashing the controller on the production line, the controller is then assembled on the vehicle. During actual flashing, the system can be connected to the vehicle computer through an interface to act on the vehicle.

[0075] The controller flashing system mentioned above integrates a flashing management module, a flashing module and an assembly management module, wherein the flashing management module stores at least one vehicle version information, the vehicle version information includes the vehicle software version number and the software package of at least one controller in the vehicle, the target software package of the controller to be flashed is sent to the flashing module through the flashing management module, so that the flashing module responds to the flashing instruction carrying the component unique code of the controller to be flashed, flashes the controller to be flashed according to the target software package, and uploads the component unique code of the controller to be flashed and the identification information after flashing to the flashing management module, so that the flashing management module determines the controller to be flashed. The target vehicle software version number corresponding to the controller is determined, and finally the assembly management module is used to perform a flashing version verification on the controller to be flashed in the assembled vehicle according to the target vehicle software version number and the actual vehicle software version number of the assembled vehicle of the controller to be flashed. In this way, in addition to personnel confirmation, the installation of the flashed controller adds a version verification of the flashed version of the corresponding controller. The vehicle software version number corresponding to the controller to be flashed and the vehicle software version number of the assembled vehicle are used to ensure that the installed version of the controller to be flashed is correct, thereby achieving the purpose of flashing version error prevention, ensuring the accuracy of controller flashing, and ensuring that the vehicle is assembled with the correct version of the controller, thereby improving the quality of vehicle production.

[0076] See also Figure 7 , Figure 7 is a flowchart of a controller flashing method shown in an exemplary embodiment of the present application. The method can be applied to Figure 1 The implementation environment shown is a schematic diagram. It should be understood that the method may also be applicable to other exemplary implementation environments, and this embodiment does not limit the implementation environment to which the method is applicable.

[0077] like Figure 7 As shown, in an exemplary embodiment, the controller flashing method at least includes steps S710 to S740, which are described in detail as follows:

[0078] Step S710, obtaining the target software package of the controller to be flashed;

[0079] Step S720, flashing the controller to be flashed according to the target software package, and reading the component unique code of the controller to be flashed and the identification information after flashing;

[0080] Step S730, determining the target vehicle software version number corresponding to the controller to be flashed according to the component unique code and the identification information after flashing, and obtaining the actual vehicle software version number of the vehicle on which the controller to be flashed is installed;

[0081] Step S740, based on the target vehicle software version number and the actual vehicle software version number, the controller to be flashed in the assembled vehicle is verified for flashing version to determine whether the installed version of the controller to be flashed is correct.

[0082] This controller flashing method adds a version check of the flashed version of the corresponding controller. By comparing the vehicle software version number corresponding to the controller to be flashed with the vehicle software version number of the assembled vehicle, it ensures that the installed version of the controller to be flashed is correct, thereby achieving the purpose of flashing version error prevention, ensuring the accuracy of controller flashing, and ensuring that the vehicle is assembled with the correct version of the controller, thereby improving the quality of vehicle production.

[0083] It should be noted that the controller flashing method provided in the above embodiment and the controller flashing system provided in the above embodiment belong to the same concept, wherein the contents of each step have been described in detail in the system embodiment and will not be repeated here.

[0084] See also Figure 8 , Figure 8 It is a structural schematic diagram of an electronic device provided by an embodiment of the present application. Figure 8 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 8 The computer system 800 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0085] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 802 or the program loaded from the storage part 808 to the random access memory (RAM) 803, such as executing the method in the above embodiment. In RAM 803, various programs and data required for system operation are also stored. CPU 801, ROM 802 and RAM 803 are connected to each other through bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0086] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed so that a computer program read therefrom is installed into the storage section 808 as needed.

[0087] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 809, and / or installed from a removable medium 811. When the computer program is executed by a central processing unit (CPU) 801, various functions defined in the system of the present application are executed.

[0088] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer executes the controller flashing method as described above. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.

[0089] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0090] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0091] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0092] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A controller flashing system, characterized in that: The system comprises: A flash management module stores at least one vehicle version information, wherein the vehicle version information includes the vehicle software version number and the software package of at least one controller in the vehicle, and is used to send the target software package of the controller to be flashed to the flash module; The flashing module is used to respond to the flashing instruction of the controller to be flashed, flash the controller to be flashed according to the target software package, and upload the component unique code of the controller to be flashed and the identification information after flashing to the flashing management module, so that the flashing management module determines the target vehicle software version number corresponding to the controller to be flashed, and the flashing instruction carries the component unique code; The assembly management module is used to perform a flashing version check on the controller to be flashed in the assembled vehicle according to the target vehicle software version number and the actual vehicle software version number of the assembled vehicle of the controller to be flashed, so as to determine whether the installed version of the controller to be flashed is correct.

2. The controller flashing system according to claim 1, characterized in that: The flashing module includes a plurality of flashing devices, each of which is used to implement the flashing of a controller; The flash writing device comprises: A pre-flashing verification unit, used for analyzing a first identification format of the controller to be flashed before flashing, matching the first identification format with a standard identification format maintained by the flashing device, and performing a flashing device verification on the controller to be flashed; The post-flashing verification unit is used to analyze the second identification format of the controller to be flashed after being flashed, match the second identification format with the standard identification format segment, and verify the flashing result of the controller to be flashed.

3. The controller flashing system according to claim 2, characterized in that: The assembly management module includes: an acquisition unit, configured to, in response to a version verification instruction, retrieve the target vehicle software version number from the flash management module according to the component unique code, and determine the actual vehicle software version number according to the vehicle identification code of the assembled vehicle, wherein the version verification instruction carries the component unique code and the vehicle identification code; The version verification unit is used to match the target vehicle software version number with the actual vehicle software version number. If the match is successful, it is determined that the installed version of the controller to be flashed is correct. If the match fails, it is determined that the installed version of the controller to be flashed is wrong.

4. The controller flashing system according to claim 1, characterized in that: The flash management module is further used to record the number of the component unique codes uploaded from the flash module as the flash quantity of the controller to be flashed; The assembly management module is also used to record the loading quantity of the controller to be flashed and send it to the flash management module, so that the flash management module calculates the difference between the flash quantity and the loading quantity, obtains the flash inventory of the controller to be flashed, and displays the flash quantity and the flash inventory of the controller to be flashed in real time.

5. The controller flashing system according to claim 2, characterized in that: The vehicle version information also includes identification information of at least one controller in the vehicle before flashing; The flash management module is used to respond to the software package sending instruction of the controller to be flashed, match the standard identification information of the controller to be flashed with the identification information before flashing, determine the target software package, and determine the target transmission path according to the standard identification information and the transmission path mapping table, so as to send the target software package to the target flashing device through the target transmission path, and the software package sending instruction carries the standard identification information.

6. The controller flashing system according to claim 5, characterized in that: The flash management module is used to match the identification information after flashing with the identification information before flashing, determine the target vehicle software version number, and associate the component unique code with the target vehicle software version number for storage.

7. The controller flashing system according to any one of claims 1 to 6, characterized in that: The system further comprises: The version maintenance module is used to manage the vehicle version information of various vehicle models. Each vehicle version information includes the vehicle software version number and the identification information of at least one controller before flashing under the vehicle software version number, and the software package of at least one controller. If any vehicle version information is updated, the updated vehicle version information will be sent to the flash management module.

8. A controller flashing method, characterized in that: The method comprises: Get the target software package of the controller to be flashed; Flashing the controller to be flashed according to the target software package, and reading the unique code of the components of the controller to be flashed and the identification information after flashing; Determine the target vehicle software version number corresponding to the controller to be flashed according to the component unique code and the identification information after flashing, and obtain the actual vehicle software version number of the vehicle on which the controller to be flashed is installed; According to the target vehicle software version number and the actual vehicle software version number, a flashing version check is performed on the controller to be flashed in the assembled vehicle to determine whether the installed version of the controller to be flashed is correct.

9. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the controller flashing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is enabled to execute the controller flashing method described in any one of claims 1 to 7.

Images