CN116578319A

CN116578319A - Firmware upgrading method and device and file generating method and device

Info

Publication number: CN116578319A
Application number: CN202310487276.6A
Authority: CN
Inventors: 杨鹏
Original assignee: Hozon New Energy Automobile Co Ltd
Current assignee: Hozon New Energy Automobile Co Ltd
Priority date: 2023-05-04
Filing date: 2023-05-04
Publication date: 2023-08-11

Abstract

The application discloses a firmware upgrading method and device and a file generating method and device, and the main technical scheme comprises the following steps: determining a manifest file matching the first domain; the first domain is a domain corresponding to a domain controller in the vehicle; the manifest file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware; the corresponding relation is used for describing the corresponding relation between each sensor controller and all sensor firmware which can be burned; searching target sensor firmware in the manifest file based on the sensor controller and sensor attribute information corresponding to the sensor to be upgraded in the first domain; the target sensor firmware is used for firmware upgrading of the sensor to be upgraded; if the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware.

Description

Firmware upgrading method and device and file generating method and device

Technical Field

The present application relates to the field of vehicle engineering technologies, and in particular, to a firmware upgrading method and apparatus, and a file generating method and apparatus.

Background

Vehicles typically deploy numerous sensors to assist in the travel and operation of the vehicle through data collected by the sensors. In order to achieve the goals of reducing the repair rate of the vehicle, improving the functions of the vehicle, prolonging the life cycle of the vehicle and the like, the firmware of the sensor needs to be continuously updated.

At present, sensors used by vehicles are numerous in variety and different in function, so that firmware used by different vehicles for upgrading the sensors is different. Differences in the firmware used to upgrade the sensors result in difficulty in managing the firmware upgrades to the vehicle sensors.

Disclosure of Invention

In view of this, the present application provides a firmware upgrading method and device, and a file generating method and device, and is mainly aimed at uniformly controlling firmware upgrading of sensors in a domain by taking the domain as a unit.

In order to achieve the above purpose, the present application mainly provides the following technical solutions:

in a first aspect, the present application provides a firmware upgrade method applied to a domain controller of a vehicle, the firmware upgrade method including:

determining a manifest file matching the first domain; the first domain is a domain corresponding to the domain controller in the vehicle; the list file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware; the corresponding relation is used for describing the corresponding relation between each sensor controller and all sensor firmware which can be burned;

Searching target sensor firmware in the manifest file based on sensor controller and sensor attribute information corresponding to the sensor to be upgraded in the first domain; the target sensor firmware is used for firmware upgrading of the sensor to be upgraded;

if the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware.

According to the firmware upgrading method provided by the application, the domain is taken as a unit, the domain controller corresponding to the domain is used for upgrading the sensor firmware, after the first domain needing to be upgraded is determined, the domain controller is used for determining a list file matched with the first domain, and the target sensor firmware for upgrading the sensor firmware to be upgraded is searched in the list file based on the sensor controller corresponding to the sensor to be upgraded in the first domain and the sensor attribute information. If the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware. The manifest file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware, and the corresponding relation is used for describing the corresponding relation between each sensor controller and all the sensor firmware which can be burned. It can be seen that, for each sensor controller in the manifest file, the sensor firmware that needs to be burned in different vehicle types is in a corresponding relation with the sensor controller. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from a different sensor vendor or a different family of sensor firmware of the same sensor vendor. In this way, only one manifest file is presented for the same field in vehicles of different models or different configurations of the same model, which can be adapted to different configurations of different models or the same model. Therefore, the embodiment of the application takes the domain as a unit, and the firmware upgrading of the sensor in the domain can be uniformly managed and controlled through the domain matched manifest file.

In some embodiments of the present application, the mapping relation between the sensor controller and the sensor firmware is recorded by the address corresponding to the sensor controller, and the searching for the target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain includes: searching a target address of a sensor controller corresponding to the sensor to be upgraded in the list file; if the target address is found and the first sensor firmware exists in the sensor firmware corresponding to the target address, determining the first sensor firmware as the target sensor firmware; and the sensor attribute information corresponding to the first sensor firmware is consistent with the sensor attribute information corresponding to the sensor to be upgraded.

In some embodiments of the present application, the firmware upgrade method further includes: if the target address is not found or the first sensor firmware does not exist in the sensor firmware corresponding to the target address, a prompt of firmware upgrading abnormality is sent to the sensor to be upgraded.

In some embodiments of the present application, the manifest file is further configured to record memory address information corresponding to each sensor firmware, and then perform firmware upgrade on the to-be-upgraded sensor in the sensor controller corresponding to the to-be-upgraded sensor through the target sensor firmware, where the method includes: determining the burning position of the sensor to be upgraded in the corresponding sensor controller based on the memory address information corresponding to the target sensor firmware; burning the target sensor firmware at the burning position to finish

And upgrading the firmware of the sensor to be upgraded.

In some embodiments of the present application, before the firmware upgrade is performed on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded by using the target sensor firmware, the method further includes: detecting whether the target sensor firmware is in binary format; if yes, the step of carrying out firmware upgrading on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware is carried out; otherwise, the target sensor firmware is converted to a binary format.

In some embodiments of the present application, the manifest file is further used to record domain controller firmware corresponding to the domain controller, and the firmware upgrade method further includes: and carrying out firmware upgrade on the domain controller based on the domain controller firmware.

In some embodiments of the present application, after the firmware upgrade is performed on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded by using the target sensor firmware, the firmware upgrade method further includes: judging whether all sensors in the first domain are upgraded; if not, selecting a new sensor to be upgraded from the sensors which are not upgraded, and transferring to execute the step of searching the target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain.

In a second aspect, the present application provides a file generation method, which is applied to a server, the file generation method including:

acquiring sensor firmware provided by a sensor provider and sensor attribute information corresponding to the sensor firmware;

summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller to form at least one group; wherein the sensor firmware within the same group corresponds to the same sensor controller;

establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to the second domain; the second domain is a domain corresponding to the target domain controller in the vehicle.

The file generation method provided by the application is characterized in that after a domain needing to be subjected to inventory file production is selected and the selected domain is used as a second domain, sensor firmware provided by a sensor provider and sensor attribute information corresponding to the sensor firmware are acquired. And then summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller in the second domain to form at least one group, wherein the sensor firmware in the same group corresponds to the same sensor controller. And finally, establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to a second domain corresponding to the target domain controller. It can be seen that, for each sensor controller in the manifest file, the sensor firmware that needs to be burned in different vehicle types is in a corresponding relation with the sensor controller. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from a different sensor vendor or a different family of sensor firmware of the same sensor vendor. In this way, only one manifest file is presented for the same field in vehicles of different models or different configurations of the same model, which can be adapted to different configurations of different models or the same model. Therefore, the embodiment of the application can uniformly manage and control the firmware upgrade of the sensor in the domain by taking the domain as a unit and through the domain matched manifest file.

In some embodiments of the present application, establishing a correspondence between sensor firmware and a corresponding sensor controller within each group includes: determining the address corresponding to each packet; wherein, the address is the address of the sensor controller corresponding to the corresponding group; based on the addresses corresponding to each packet, a correspondence between the sensor firmware and the corresponding sensor controller within each packet is established.

In some embodiments of the present application, after obtaining the sensor firmware provided by the sensor vendor, the file generation method further comprises: the acquired sensor firmware is converted into a binary format.

In some embodiments of the present application, before obtaining the sensor firmware provided by the sensor vendor and the sensor attribute information corresponding to the sensor firmware, the file generating method further includes: acquiring a firmware pressure measurement report provided by a sensor provider; the firmware pressure measurement report is used for describing the performance condition of the corresponding sensor firmware; verifying the obtained firmware pressure measurement report; issuing a providing instruction to a corresponding sensor provider for a pressure measurement report passing verification; the providing instruction is used for informing the corresponding sensor provider of providing sensor firmware corresponding to the pressure measurement report and sensor attribute information corresponding to the sensor firmware.

In some embodiments of the present application, the file generating method further includes: acquiring domain controller firmware corresponding to the target domain controller; and recording the corresponding relation between the domain control firmware and the target domain controller in the list file.

In a third aspect, the present application provides a firmware upgrade apparatus applied to a domain controller of a vehicle, the firmware upgrade apparatus comprising:

a determining module for determining a manifest file matching the first domain; the first domain is a domain corresponding to the domain controller in the vehicle; the list file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware; the corresponding relation is used for describing the corresponding relation between each sensor controller and all sensor firmware which can be burned;

the searching module is used for searching the target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain; the target sensor firmware is used for firmware upgrading of the sensor to be upgraded;

And the upgrading module is used for upgrading the firmware of the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware if the target sensor firmware is searched.

In a fourth aspect, the present application provides a file generation device applied to a server, the file generation device comprising:

the acquisition module is used for acquiring sensor firmware provided by a sensor provider and sensor attribute information corresponding to the sensor firmware;

the grouping module is used for summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller to form at least one group; wherein the sensor firmware within the same group corresponds to the same sensor controller;

the generation module is used for establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and establishing a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to the second domain; the second domain is a domain corresponding to the target domain controller in the vehicle.

In a fifth aspect, the present application provides a computer readable storage medium, where the storage medium includes a stored program, where the program, when executed, controls a device in which the storage medium is located to perform the firmware upgrade method according to the first aspect, and/or performs the file generation method according to the second aspect.

In a sixth aspect, the present application provides an electronic device, including: a memory for storing a program; a processor coupled to the memory for executing the program to perform the firmware upgrade method of the first aspect and/or to perform the file generation method of the second aspect.

The foregoing description is only an overview of the present application, and is intended to be implemented in accordance with the teachings of the present application in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present application more readily apparent.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a firmware upgrade method according to one embodiment of the present application;

FIG. 2 is a flow chart of a firmware upgrade method according to another embodiment of the present application;

FIG. 3 is a flow chart illustrating a method of generating a file according to an embodiment of the present application;

FIG. 4 is a flowchart of a method for generating a file according to another embodiment of the present application;

FIG. 5 is a schematic diagram illustrating a firmware upgrade apparatus according to an embodiment of the present application;

FIG. 6 is a schematic diagram illustrating a firmware upgrade apparatus according to another embodiment of the present application;

FIG. 7 is a schematic diagram of a file generating apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a file generating apparatus according to another embodiment of the present application.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

At present, in order to achieve the goals of reducing the repair rate of the vehicle, improving the functions of the vehicle, prolonging the life cycle of the vehicle and the like, the firmware of a sensor deployed in the vehicle needs to be continuously upgraded. However, the sensors used in vehicles are numerous in variety and function, resulting in variations in the firmware used to upgrade the sensors from vehicle to vehicle. The differences in the firmware used by the sensors make it difficult to uniformly manage firmware upgrades to the vehicle sensors.

For a vehicle, the vehicle is generally divided into a plurality of domains, each domain is a set of electronic and electric architectures for controlling a certain large functional module of the vehicle, and each domain is uniformly controlled by a domain controller, i.e., domain control ECU (Electronic Control Unit ). Each domain controller governs the sensor controllers (i.e., the sensing ECUs) in its corresponding domain. The sensor controller is used for burning firmware of the corresponding sensor. The inventors found that the sensor controllers corresponding to the sensors having the same function in the same domain are identical in vehicles of different vehicle types. Therefore, the inventor has studied to uniformly manage firmware upgrades of sensors in each domain in units of domains in a vehicle, that is, for any one domain in the vehicle, firmware upgrades of sensors in the domain are uniformly managed by a domain controller in the domain, and the domain controller manages the sensor firmware upgrades to be performed according to a manifest file matched by the domain. The manifest file is a main basis for upgrading the sensor firmware, and is designed to record the correspondence between the sensor controller and the sensor firmware and record the sensor attribute information corresponding to each sensor firmware, where the correspondence is used to describe the correspondence between each sensor controller and all the sensor firmware that can be burned. For each sensor controller in the list file, the corresponding relation between the sensor firmware which needs to be burnt in different vehicle types and the sensor controller is established. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from different sensor suppliers and/or different families of sensor firmware for the same sensor supplier. Thus, the corresponding upgrade packages can be prevented from being manufactured separately for the firmware of different sensor suppliers or different series of sensors of the same supplier.

Based on the above consideration, the embodiment of the application provides a technical scheme for firmware upgrade, which specifically comprises the following steps: and determining a manifest file matched with the first domain, and searching target sensor firmware for upgrading the sensor firmware to be upgraded in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain. If the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware. The first domain is a domain corresponding to a domain controller in the vehicle, and the sensor in the first domain needs to be subjected to firmware upgrade. The list file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware, and the corresponding relation is used for describing the corresponding relation between each sensor controller and all the sensor firmware which can be burned.

In addition, in order to provide the manifest file for firmware upgrade of the sensors in the domain controlled by the domain controller of the vehicle, the embodiment of the application also provides a technical scheme for file generation. The method comprises the following steps: sensor firmware provided by a sensor provider and sensor attribute information corresponding to the sensor firmware are acquired. And then summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller to form at least one group, wherein the sensor firmware in the same group corresponds to the same sensor controller. And finally, establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to a second domain corresponding to the target domain controller.

Based on the technical scheme of firmware upgrading, the application provides a firmware upgrading method and device. The firmware upgrading method and device provided by the embodiment of the application can be applied to the domain controller of any domain of any vehicle. The embodiment of the application does not limit the type of the vehicle and the specific type of the domain controller. Exemplary, the vehicle may be, but is not limited to, any of the following

One or two of: fuel automobiles, electric automobiles, and hybrid vehicles. Illustratively, the domain controller may be, but is not limited to, any of the following: domain controller of power domain, domain controller of chassis domain, domain controller of car domain, domain controller of cabin domain and domain controller of automatic driving domain.

Based on the technical scheme of file generation, the application provides a file generation method and device. The file generation method and the file generation device provided by the embodiment of the application can be applied to any server so that the server can generate the manifest file for upgrading the sensor firmware in the vehicle. The manifest file may be a manifest file corresponding to any one of the following fields: power domain, chassis domain, body domain, cabin domain and autopilot domain.

The firmware upgrading method and device, the file generating method and device provided by the embodiment of the application are specifically described below.

As shown in fig. 1, an embodiment of the present application provides a firmware upgrade method applied to a domain controller of a vehicle, the firmware upgrade method mainly including the following steps 101 to 103:

101. determining a manifest file matching the first domain; the first domain is a domain corresponding to a domain controller in the vehicle; the manifest file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware; the correspondence is used for describing the correspondence between each sensor controller and all the sensor firmware that can be burned.

After a vehicle needing to be upgraded of the sensor firmware is selected, a first domain is selected from domains related to the vehicle, and a sensor corresponding to a sensor controller managed by a domain controller of the first domain is a sensor of the firmware to be upgraded.

Illustratively, the vehicle 1 is divided into a power domain, a chassis domain, a body domain, a cabin domain, and an autopilot domain. And determining that the firmware upgrade needs to be carried out on the sensor related to the automatic driving domain, and determining the automatic driving domain as a first domain.

After determining the first domain, determining a manifest file matching the first domain to perform firmware upgrade on the sensor involved in the first domain by the sensor firmware recorded in the manifest file. The specific process of determining a manifest file matching the first domain may include: the query server, wherein, store at least one domain identification and correspondent manifest file of each domain identification in the server; and if the domain identifier corresponding to the first domain exists in the server, determining the manifest file corresponding to the domain identifier as the manifest file matched with the first domain.

The manifest file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware. The correspondence is used for describing the correspondence between each sensor controller and all the sensor firmware that can be burned. For a sensor controller, all the sensor firmware that can be burned in is correspondingly present in the manifest file for selection. That is, the sensor firmware for one sensor controller is based on its corresponding sensor in different vehicle models, and thus the sensor firmware for one sensor controller includes different series of sensor firmware originating from different sensor suppliers or the same sensor supplier. In this way, the firmware of different sensor suppliers or different series of sensors of the same supplier can be integrated in the same manifest file for use by different vehicle models.

102. Searching target sensor firmware in the manifest file based on the sensor controller and sensor attribute information corresponding to the sensor to be upgraded in the first domain; the target sensor firmware is used for firmware upgrading of the sensor to be upgraded.

Different vehicle models have the same domain. For each same domain, the sensor controllers corresponding to the sensors having the same function in that domain in different vehicle types have the same address in that domain. Therefore, in order to facilitate firmware upgrade of the sensors in different vehicle types, the manifest file may record the correspondence between the sensor controller and the sensor firmware through the address corresponding to the sensor controller.

For example, the sensor "front left radar" exists in the automatic driving domain of different vehicle types, and the sensor controller "ECU1" corresponding to the "front left radar" in the different vehicle types has the same address "address 1" in the automatic driving domain, and then the corresponding relationship between the sensor controller and the sensor firmware is recorded by the address corresponding to the sensor controller by the manifest file: correspondence between "address 1" and three sensor firmware that "ECU1" can burn. In addition, the address corresponding to the sensor controller may be a diagnostic address or an IP address.

After determining the manifest file, searching for target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain, wherein the target sensor firmware is used for firmware upgrade of the sensor to be upgraded. Based on the sensor controller and sensor attribute information corresponding to the sensor to be upgraded in the first domain, the specific process of searching the manifest file for the target sensor firmware may include the following steps 102A to 102B:

102A, searching a target address of a sensor controller corresponding to the sensor to be upgraded in the manifest file.

The sensor to be upgraded has a corresponding sensor controller in the first domain, and the sensor controller is used for burning firmware of the sensor to be upgraded. After determining the sensor to be upgraded, determining an address of a sensor controller corresponding to the sensor to be upgraded in the first domain as a target address, and then searching the target address in the manifest file.

102B, if the target address is found and the first sensor firmware exists in the sensor firmware corresponding to the target address, determining the first sensor firmware as the target sensor firmware; the sensor attribute information corresponding to the first sensor firmware is consistent with the sensor attribute information corresponding to the sensor to be upgraded.

If the target address is found, it is indicated that the sensor firmware corresponding to the sensor to be upgraded exists in the manifest file, so that the sensor attribute information corresponding to the sensor to be upgraded is obtained, and whether the first sensor firmware exists in the sensor firmware corresponding to the target address is judged based on the obtained sensor attribute information and the sensor attribute information of the sensor firmware corresponding to the target address. If the first sensor firmware corresponding to the target address is judged to exist, the first sensor firmware is indicated to be available for upgrading the sensor firmware to be upgraded, and therefore the first sensor firmware is determined to be the target sensor firmware.

The sensor attribute information may include a vendor code and part number (i.e., partnumber) of the sensor. Wherein the part numbers corresponding to the same vendor code have uniqueness.

Further, if the target address is not found in the manifest file, or it is determined that the first sensor firmware does not exist in the sensor firmware corresponding to the target address, a prompt of firmware upgrade abnormality is sent to the sensor to be upgraded.

If the target address is not found in the manifest file, or if the target address is found in the manifest file but it is determined that the first sensor firmware does not exist in the sensor firmware corresponding to the target address, it is indicated that the sensor firmware for upgrading the sensor firmware to be upgraded does not exist in the manifest file, so that a prompt of abnormal firmware upgrading needs to be sent to the sensor to be upgraded, so that service personnel can timely conduct abnormal elimination based on the prompt, and the firmware of the sensor to be upgraded is guaranteed to be upgraded.

The prompt of abnormal firmware upgrade can be sent to a corresponding service end of a vehicle manufacturer or after-sales vehicle, so that a manufacturer staff or after-sales vehicle staff can know the abnormality in time to remove the abnormality.

103. If the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware.

If the target sensor firmware which can be used for upgrading the sensor firmware to be upgraded is found in the manifest file, the sensor firmware to be upgraded can be upgraded, and the sensor firmware to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware. The specific process of carrying out firmware upgrading on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware comprises the following steps 103A to 103B:

103A, determining the burning position of the sensor to be upgraded in the corresponding sensor controller based on the memory address information corresponding to the target sensor firmware.

The manifest file is also used for recording memory address information corresponding to each sensor firmware, namely flash information during refreshing. The memory address information reflects the burning position allocated to the sensor controller corresponding to the sensor to be upgraded, and the burning position is the position where the sensor firmware of the sensor to be upgraded is burned. Therefore, based on the memory address information corresponding to the target sensor firmware, the burning position of the sensor to be upgraded in the corresponding sensor controller is determined.

103B, burning the firmware of the target sensor at the burning position to finish the firmware upgrading of the sensor to be upgraded.

After the burning position is determined, the existing firmware corresponding to the sensor to be upgraded is cleared at the burning position, and then the target sensor firmware is burned to the corresponding burning position, so that the firmware upgrading of the sensor to be upgraded is completed at the sensor controller corresponding to the sensor to be upgraded.

According to the firmware upgrading method provided by the embodiment of the application, the domain is taken as a unit, the domain controller corresponding to the domain is used for upgrading the sensor firmware, after the first domain needing to be upgraded is determined, the domain controller is used for determining a list file matched with the first domain, and the target sensor firmware for upgrading the sensor firmware to be upgraded is searched in the list file based on the sensor controller corresponding to the sensor to be upgraded in the first domain and the sensor attribute information. If the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware. The manifest file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware, and the corresponding relation is used for describing the corresponding relation between each sensor controller and all the sensor firmware which can be burned. It can be seen that, for each sensor controller in the manifest file, the sensor firmware that needs to be burned in different vehicle types is in a corresponding relation with the sensor controller. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from a different sensor vendor or a different family of sensor firmware of the same sensor vendor. In this way, only one manifest file is presented for the same field in vehicles of different models or different configurations of the same model, which can be adapted to different configurations of different models or the same model. Therefore, the embodiment of the application takes the domain as a unit, and the firmware upgrading of the sensor in the domain can be uniformly managed and controlled through the domain matched manifest file.

In some embodiments of the present application, after the firmware upgrade is performed on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded in step 103 through the target sensor firmware, the firmware upgrade method may further include the following steps: judging whether all sensors in the first domain are upgraded; if not, selecting a new sensor to be upgraded from the sensors not completed to be upgraded, and forwarding to execute the step 102 to search the target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain.

If it is determined that all the sensors in the first domain are upgraded, it is indicated that the firmware upgrading of the sensors in the first domain is completed, and a prompt for ending the firmware upgrading can be sent out for the first domain at this time to inform service personnel that the firmware upgrading of all the sensors in the first domain is completed.

If it is determined that there are more sensors in the first domain that have not been upgraded, a new sensor to be upgraded is selected from the sensors that have not been upgraded, and the process proceeds to step 102.

In some embodiments of the present application, before the firmware upgrade is performed on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded in step 103 through the target sensor firmware, the firmware upgrade method may further include the following steps: detecting whether the target sensor firmware is in a binary format; if yes, step 103 is executed, and firmware upgrading is carried out on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware; otherwise, the target sensor firmware is converted to a binary format.

In order to facilitate the burning of the target sensor firmware to the corresponding sensor controller, the format of the target sensor firmware needs to be detected before the firmware of the sensor to be upgraded is upgraded by using the target sensor firmware. If it is detected that the target sensor firmware is in binary format, the process proceeds directly to step 103. If it is detected that the target sensor firmware is not in the binary format, the target sensor firmware is converted into the binary format, and after the conversion is completed, the process proceeds to step 103.

In some embodiments of the present application, for a domain, in order to upgrade the firmware of the domain controller of the domain while upgrading the sensor firmware in the domain, the manifest file is further used to record the domain controller firmware corresponding to the domain controller. Therefore, the firmware upgrade method may further include the steps of: and updating the firmware of the domain controller based on the domain controller firmware.

In some embodiments of the present application, taking fig. 2 as an example below to illustrate a firmware upgrade method provided in an embodiment of the present application, the firmware upgrade method shown in fig. 2 is applied to a domain controller of a vehicle, and the firmware upgrade method includes the following steps 201 to 209:

201. and acquiring an upgrade package matched with the first domain.

The domain of the sensor firmware to be upgraded in the vehicle is selected as the first domain. The upgrade of the sensor firmware in the first domain is done by the domain controller of the first domain. Illustratively, if the domain in the vehicle in which the sensor firmware is to be upgraded is an autopilot domain, the autopilot domain is selected as the first domain.

A plurality of upgrade packages are arranged in a server of a vehicle manufacturer, and each upgrade package corresponds to one domain of the vehicle. The upgrade package is obtained by packaging the manifest file of the corresponding domain.

After determining the first domain, the domain controller of the first domain downloads the upgrade package matched with the first domain from the server based on the domain identification of the first domain.

202. And checking and decompressing the upgrade package to obtain the list file matched with the first domain.

After the upgrade package is obtained, in order to ensure security, it is necessary to check whether the upgrade package is a legal upgrade package. If the upgrade package is verified to be legal, decompressing the upgrade package to obtain a list file matched with the first domain in the upgrade package. If the upgrade package is detected to be illegal, the firmware upgrade of the first domain is stopped, and a prompt for the abnormality of the upgrade package is sent out, so that service personnel can perform corresponding abnormality processing on the upgrade package based on the prompt.

And recording the corresponding relation between the sensor controller and the sensor firmware in the list file, and recording the sensor attribute information and the memory address information corresponding to each sensor firmware. The correspondence is used for describing the correspondence between each sensor controller and all the sensor firmware that can be burned. In addition, the corresponding relation between the sensor controller and the sensor firmware is recorded by the address corresponding to the sensor controller through the manifest file.

203. A sensor to be upgraded in the first domain is determined that is currently in need of upgrading.

204. And searching target sensor firmware for upgrading the sensor firmware to be upgraded in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain. If the target sensor firmware is found, step 206 is performed. If no target sensor firmware is found, step 205 is performed.

205. If the target sensor firmware is not found, a prompt of firmware upgrading abnormality is sent to the sensor to be upgraded.

If the target sensor firmware is not found, two situations may exist: first, the target address of the sensor controller corresponding to the sensor to be upgraded is not found in the manifest file. And secondly, searching a target address of the sensor controller corresponding to the sensor to be upgraded in the list file, wherein the target address does not exist in the sensor firmware corresponding to the target address. The sensor attribute information corresponding to the target sensor firmware is consistent with the sensor attribute information corresponding to the sensor to be upgraded.

206. If the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware.

The specific process of firmware upgrade is as follows: determining the burning position of the sensor to be upgraded in the corresponding sensor controller based on the memory address information corresponding to the target sensor firmware; and burning the firmware of the target sensor at the burning position to finish the firmware upgrading of the sensor to be upgraded.

207. Judging whether all sensors in the first domain are upgraded; if not, go to step 208; if yes, go to step 209.

It should be noted that if there are sensors in the first domain that have not yet been updated, but these sensors are all sensors in the manifest file that do not have the corresponding target sensor firmware, it is also determined that all the sensors in the first domain have been updated. The sensors without corresponding target sensor firmware inform the service personnel in a prompt manner, so that the service personnel can intervene to enable the firmware upgrade of the sensors.

208. A new sensor to be upgraded is selected from the sensors that have not completed the upgrade, and step 203 is performed.

The selected new sensor to be upgraded is the sensor to be upgraded which is required to be upgraded currently,

209. and sending a prompt for ending the firmware upgrading to the first domain so as to prompt that the firmware upgrading of all the sensors in the first domain is finished.

As shown in fig. 3, an embodiment of the present application provides a file generating method, which is applied to a server, and mainly includes the following steps 301 to 303:

301. sensor firmware provided by a sensor provider and sensor attribute information corresponding to the sensor firmware are acquired.

To enable firmware upgrades to sensors in a vehicle in units of domains, sensor firmware is collected in units of domains. First, a domain to be subjected to manifest file creation is selected, and the selected domain is taken as a second domain. And summarizing the sensors related to the second fields of the multiple vehicle types, and providing sensor firmware summarizing addresses for suppliers of the sensors so that the suppliers upload the sensor firmware and sensor attribute information corresponding to the sensor firmware based on the summarizing addresses. The sensor attribute information may include a vendor code and part number (i.e., partnumber) of the sensor. Wherein, the part numbers corresponding to the same supplier code have uniqueness.

302. Summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller to form at least one group; wherein the sensor firmware within the same group corresponds to the same sensor controller.

Different vehicle models have the same domain. For each same domain, the sensor controllers corresponding to the sensors having the same function in the domain in different vehicle types are the same. Illustratively, the front left radar in the autopilot domain in the vehicle type 1 and the front left radar in the autopilot domain in the vehicle type 2 are sensors with the same function, and the sensor controllers corresponding to the front left radar are the sensor controllers 1 in the respective autopilot domains.

Based on the above consideration, the sensor firmware corresponding to the same sensor controller in the acquired sensor firmware is summarized in the same group based on the sensor controller controlled by the target domain controller.

303. Establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to the second domain; the second domain is a domain corresponding to a target domain controller in the vehicle.

The specific process of establishing the correspondence between the sensor firmware and the corresponding sensor controller within each group may include the following steps 303A to 303B:

303A, determining an address corresponding to each packet; wherein the address is the address of the sensor controller corresponding to the corresponding packet.

Different vehicle models have the same domain. For each same domain, the sensor controllers corresponding to the sensors having the same function in that domain in different vehicle types have the same address in that domain. The sensor firmware within the same packet corresponds to the same sensor controller, so that for one packet, the address corresponding to that packet is the address of the sensor controller corresponding to that packet in the corresponding second domain.

303B, based on the addresses corresponding to the packets, establishing a correspondence between the sensor firmware in each packet and the corresponding sensor controller.

After determining the addresses corresponding to the packets, for each packet, a correspondence between the address of the packet and all the sensor firmware in the packet is established, so that all the sensor firmware that the sensor controller corresponding to the packet can burn can be known based on the correspondence.

After the correspondence between the sensor firmware and the corresponding sensor controller in each group is established, in order to clarify the sensor adapted by each sensor firmware, the correspondence between each sensor firmware and the respective sensor attribute information thereof needs to be established.

After the corresponding relation between the sensor firmware and the corresponding sensor controller in each group and the corresponding relation between each sensor firmware and the respective sensor attribute information are established, the corresponding relations are recorded in a designated file to form a list file applicable to the second domain. The manifest file may be used for firmware upgrades to sensors in the second domain by a target domain controller in the second domain.

Illustratively, the server generates a manifest file corresponding to the autopilot domain. The list file comprises the corresponding relation between the sensor controller ECU1 and three sensor firmware matched with the sensor controller ECU1, and the three sensor firmware are respectively: "ECU 1_support_a.bin", "ECU 1_support_b1.bin" \ "ECU 1_support_b2.bin". The corresponding relation between the sensor controller 'ECU 2' and one sensor firmware matched with the sensor controller 'ECU 2' is recorded in the manifest file, and the sensor firmware is 'ECU 2. Bin'. And the manifest file also includes sensor attribute information corresponding to each sensor firmware.

According to the file generation method provided by the embodiment of the application, after the domain which needs to be subjected to the inventory file production is selected and the selected domain is used as the second domain, the sensor firmware provided by the sensor provider and the sensor attribute information corresponding to the sensor firmware are acquired. And then summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller in the second domain to form at least one group, wherein the sensor firmware in the same group corresponds to the same sensor controller. And finally, establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to a second domain corresponding to the target domain controller. It can be seen that, for each sensor controller in the manifest file, the sensor firmware that needs to be burned in different vehicle types is in a corresponding relation with the sensor controller. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from a different sensor vendor or a different family of sensor firmware of the same sensor vendor. In this way, only one manifest file is presented for the same field in vehicles of different models or different configurations of the same model, which can be adapted to different configurations of different models or the same model. Therefore, the embodiment of the application can uniformly manage and control the firmware upgrade of the sensor in the domain by taking the domain as a unit and through the domain matched manifest file.

In some embodiments of the present application, after the step 301 of obtaining the sensor firmware provided by the sensor vendor, the file generating method may further include the steps of: the acquired sensor firmware is converted into a binary format.

In order to reject information in the sensor firmware that is not relevant to the upgrade, after the sensor firmware is acquired, it is detected whether the sensor firmware is in binary format. If the sensor firmware is detected to be in the binary format, the sensor firmware does not need to be processed, and the sensor firmware can be directly used subsequently. If the sensor firmware is detected to be in a non-binary format (e.g., s19 or hex format), the sensor firmware is converted to a binary format.

In some embodiments of the present application, before the step 301 of obtaining the sensor firmware provided by the sensor vendor and the sensor attribute information corresponding to the sensor firmware, the file generating method may further include the following steps 304 to 306:

304. a firmware crush report provided by a sensor vendor is obtained.

The firmware crush report is used to describe the performance of the corresponding sensor firmware. To ensure that the sensor firmware recorded in the manifest file is available and free of abnormal firmware, it is therefore necessary to obtain a firmware crush report provided by the sensor vendor.

305. And verifying the obtained firmware pressure measurement report.

After the firmware pressure measurement report provided by the sensor provider is obtained, verifying that the performance of the corresponding sensor firmware meets the requirements based on the firmware pressure measurement report. And if the performance of the sensor firmware corresponding to the verification meets the requirements, determining that the firmware pressure measurement report passes the verification. If the performance of the sensor firmware corresponding to the verification is not in accordance with the requirements, determining that the firmware pressure measurement report verification is not passed.

306. And issuing a providing instruction to a corresponding sensor provider for the pressure measurement report passing the verification.

The providing instruction is used for informing the corresponding sensor provider of providing the sensor firmware corresponding to the pressure measurement report and the sensor attribute information corresponding to the sensor firmware, so that the sensor provider provides the corresponding sensor firmware and the sensor attribute information corresponding to the sensor firmware based on the providing instruction for making the manifest file.

In some embodiments of the present application, for a domain, to enable a firmware upgrade to be performed on a domain controller of the domain while the sensor firmware in the domain is being upgraded, the file generation may further include the steps of: acquiring domain controller firmware corresponding to a target domain controller; and recording the corresponding relation between the domain control firmware and the target domain controller in the list file.

The corresponding relation between the domain control firmware and the target domain controller is recorded in the manifest file, so that the target domain controller can upgrade the firmware of the sensor while the sensor controlled by the target domain controller upgrades the firmware of the sensor.

And the corresponding manifest file of one domain integrates the upgrade firmware of the domain controller of the domain and the upgrade firmware of the sensor in the domain, so that only one manifest file is presented to the outside, and the whole upgrade of the domain controller and the sensor in one domain can be realized.

In some embodiments of the present application, a file generating method provided by an embodiment of the present application is described below by taking fig. 4 as an example, where the file generating method shown in fig. 4 is applied to a server, and the file generating method includes steps 401 to 209 as follows:

401. acquiring a firmware pressure measurement report provided by a sensor provider; the firmware pressure report is used for describing the performance condition of the corresponding sensor firmware.

402. And verifying the obtained firmware pressure measurement report.

403. Issuing a providing instruction to a corresponding sensor provider for a pressure measurement report passing verification; the providing instruction is used for informing the corresponding sensor provider of providing the sensor firmware corresponding to the pressure measurement report and the sensor attribute information corresponding to the sensor firmware.

404. Sensor firmware provided by a sensor provider and sensor attribute information corresponding to the sensor firmware are acquired.

The sensor provider is provided with a summarized address so that the sensor provider can upload the sensor firmware and the sensor attribute information corresponding to the sensor firmware to the server based on the summarized address.

To further ensure that the sensor firmware is free of anomalies, execution is required for each sensor firmware acquired: testing whether the sensor firmware is abnormal; if yes, rejecting the sensor firmware, and providing feedback firmware abnormality prompts for corresponding sensor suppliers; if not, the sensor firmware is stored.

Further, to unify the format of the sensor firmware, it is necessary for the sensor firmware to be converted to a binary format for non-binary formats.

405. And summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller to form at least one group. Wherein the sensor firmware within the same group corresponds to the same sensor controller.

406. Determining the address corresponding to each packet; wherein the address is the address of the sensor controller corresponding to the corresponding packet.

407. Based on the addresses corresponding to each packet, a correspondence between the sensor firmware and the corresponding sensor controller within each packet is established.

408. And establishing a corresponding relation between each sensor firmware and the respective sensor attribute information thereof.

409. The corresponding relation between the sensor firmware and the corresponding sensor controller in each group and the corresponding relation between each sensor firmware and the respective sensor attribute information form a list file applicable to the second domain; the second domain is a domain corresponding to the target domain controller in the vehicle.

It should be noted that, the manifest file may also record memory address information corresponding to each sensor firmware, that is, flash information during writing. The memory address information reflects the burning position allocated to the sensor controller corresponding to the sensor to be upgraded, and the burning position is the position where the sensor firmware of the sensor to be upgraded is burned.

410. And preparing the list file as an upgrade package corresponding to the second domain.

411. And checking the upgrade package, and issuing the upgrade package after checking so as to be downloaded by a target domain controller in the vehicle.

The main purpose of the upgrade package is to verify that the manifest file can be properly parsed by the upgrade package and that the manifest file is available for firmware upgrade of the sensor in the second domain. And if the verification is passed, issuing an upgrade package for downloading and using by a target domain controller in the vehicle. If the verification is not passed, an exception prompt is sent out, so that service personnel can conduct exception removal processing on the upgrade package based on the exception prompt.

Further, an embodiment of the present application also provides a firmware upgrade apparatus applied to a domain controller of a vehicle, as shown in fig. 5, including:

a determining module 51, configured to determine a manifest file matching the first domain; the first domain is a domain corresponding to the domain controller in the vehicle; the list file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware; the corresponding relation is used for describing the corresponding relation between each sensor controller and all sensor firmware which can be burned;

a searching module 52, configured to search the manifest file for the target sensor firmware based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain; the target sensor firmware is used for firmware upgrading of the sensor to be upgraded;

and the upgrading module 53 is configured to upgrade the firmware of the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded by using the target sensor firmware if the target sensor firmware is found.

According to the firmware upgrading device provided by the embodiment of the application, the firmware of the sensor is upgraded by taking the domain as a unit through the domain controller corresponding to the domain, after the first domain needing to be upgraded of the sensor firmware is determined, the domain controller determines the list file matched with the first domain, and the target sensor firmware for upgrading the sensor firmware to be upgraded is searched in the list file based on the sensor controller corresponding to the sensor to be upgraded in the first domain and the sensor attribute information. If the target sensor firmware is found, the firmware of the sensor to be upgraded is upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware. The manifest file is used for recording the corresponding relation between the sensor controller and the sensor firmware and recording the sensor attribute information corresponding to each sensor firmware, and the corresponding relation is used for describing the corresponding relation between each sensor controller and all the sensor firmware which can be burned. It can be seen that, for each sensor controller in the manifest file, the sensor firmware that needs to be burned in different vehicle types is in a corresponding relation with the sensor controller. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from a different sensor vendor or a different family of sensor firmware of the same sensor vendor. In this way, only one manifest file is presented for the same field in vehicles of different models or different configurations of the same model, which can be adapted to different configurations of different models or the same model. Therefore, the embodiment of the application takes the domain as a unit, and the firmware upgrading of the sensor in the domain can be uniformly managed and controlled through the domain matched manifest file.

In some embodiments of the present application, as shown in FIG. 6, the lookup module 52 includes:

a searching unit 521, configured to search the target address of the sensor controller corresponding to the sensor to be upgraded in the manifest file; the corresponding relation between the sensor controller and the sensor firmware is recorded by the address corresponding to the sensor controller through the manifest file;

a first determining unit 522, configured to determine, if the target address is found by the finding unit 521 and there is a first sensor firmware in the sensor firmware corresponding to the target address, the first sensor firmware as the target sensor firmware; and the sensor attribute information corresponding to the first sensor firmware is consistent with the sensor attribute information corresponding to the sensor to be upgraded.

In some embodiments of the present application, as shown in FIG. 6, the lookup module 52 further includes:

and the prompting unit 523 is configured to issue a prompt for a firmware upgrade exception for the sensor to be upgraded if the target address is not found or if the first sensor firmware does not exist in the sensor firmware corresponding to the target address.

In some embodiments of the present application, as shown in FIG. 6, the upgrade module 53 includes:

The second determining unit 531 is configured to determine a recording position of the sensor to be upgraded in the corresponding sensor controller based on the memory address information corresponding to the target sensor firmware; the manifest file is also used for recording memory address information corresponding to each sensor firmware;

and the upgrading unit 532 is configured to burn the target sensor firmware at the burning position to complete the firmware upgrading of the sensor to be upgraded.

In some embodiments of the present application, as shown in fig. 6, the firmware upgrade apparatus further includes:

a conversion module 54 for detecting whether the target sensor firmware is in binary format; if yes, triggering the upgrading module 53 to switch to executing the step of upgrading the firmware of the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware; otherwise, the target sensor firmware is converted to a binary format.

In some embodiments of the present application, as shown in fig. 6, the upgrade unit 532 is further configured to upgrade the domain controller firmware based on the domain controller firmware; the manifest file is further used for recording domain controller firmware corresponding to the domain controller.

a judging module 55, configured to judge whether all the sensors in the first domain are upgraded after the upgrading module 53 performs firmware upgrading on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware; if not, selecting a new sensor to be upgraded from the sensors which are not upgraded, triggering the searching module 52 to perform the step of searching the target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain.

In the firmware upgrading device provided by the embodiment of the present application, details adopted in the operation process of each functional module may be referred to the corresponding details of the firmware upgrading method embodiment, and will not be described herein.

Further, an embodiment of the present application also provides a file generating apparatus applied to a server, as shown in fig. 7, including:

an obtaining module 61, configured to obtain sensor firmware provided by a sensor vendor and sensor attribute information corresponding to the sensor firmware;

The grouping module 62 is configured to aggregate the acquired sensor firmware based on the sensor controller controlled by the target domain controller to form at least one group; wherein the sensor firmware within the same group corresponds to the same sensor controller;

a generating module 63, configured to establish a correspondence between the sensor firmware in each group and the corresponding sensor controller, and establish a correspondence between each sensor firmware and its respective sensor attribute information, and generate a manifest file applicable to the second domain; the second domain is a domain corresponding to the target domain controller in the vehicle.

The file generating device provided by the embodiment of the application obtains the sensor firmware provided by the sensor provider and the sensor attribute information corresponding to the sensor firmware after selecting the domain needing to be subjected to the inventory file production and taking the selected domain as the second domain. And then summarizing the acquired sensor firmware based on the sensor controller controlled by the target domain controller in the second domain to form at least one group, wherein the sensor firmware in the same group corresponds to the same sensor controller. And finally, establishing a corresponding relation between the sensor firmware in each group and the corresponding sensor controller and a corresponding relation between each sensor firmware and the respective sensor attribute information thereof, and generating a list file applicable to a second domain corresponding to the target domain controller. It can be seen that, for each sensor controller in the manifest file, the sensor firmware that needs to be burned in different vehicle types is in a corresponding relation with the sensor controller. That is, for any one sensor controller in the manifest file, its corresponding sensor firmware may originate from a different sensor vendor or a different family of sensor firmware of the same sensor vendor. In this way, only one manifest file is presented for the same field in vehicles of different models or different configurations of the same model, which can be adapted to different configurations of different models or the same model. Therefore, the embodiment of the application can uniformly manage and control the firmware upgrade of the sensor in the domain by taking the domain as a unit and through the domain matched manifest file.

In some embodiments of the present application, as shown in fig. 8, the generating module 63 is specifically configured to determine an address corresponding to each packet; wherein, the address is the address of the sensor controller corresponding to the corresponding group; based on the addresses corresponding to each packet, a correspondence between the sensor firmware and the corresponding sensor controller within each packet is established.

In some embodiments of the present application, as shown in fig. 8, the acquiring module 61 is further configured to convert the acquired sensor firmware into a binary format.

In some embodiments of the present application, as shown in fig. 8, the file generating apparatus further includes:

a verification module 64 for obtaining a firmware crush report provided by the sensor vendor; the firmware pressure measurement report is used for describing the performance condition of the corresponding sensor firmware; verifying the obtained firmware pressure measurement report; issuing a providing instruction to a corresponding sensor provider for a pressure measurement report passing verification; the providing instruction is used for informing the corresponding sensor provider of providing sensor firmware corresponding to the pressure measurement report and sensor attribute information corresponding to the sensor firmware.

In some embodiments of the present application, as shown in fig. 8, the generating module 63 is further configured to obtain domain controller firmware corresponding to the target domain controller; and recording the corresponding relation between the domain control firmware and the target domain controller in the list file.

In the file generating apparatus provided in the embodiment of the present application, details adopted in the operation process of each functional module may be referred to the corresponding details of the above embodiment of the file generating method, which are not described herein again.

Further, an embodiment of the present application provides a computer readable storage medium, where the storage medium includes a stored program, and when the program runs, the device where the storage medium is controlled to execute the firmware upgrading method described above.

Further, an embodiment of the present application also provides a computer readable storage medium, where the storage medium includes a stored program, and when the program runs, the device where the storage medium is controlled to execute the file generating method described above.

Further, an embodiment of the present application also provides an electronic device, including: a memory for storing a program; and the processor is coupled to the memory and is used for running the program to execute the firmware upgrading method.

Further, an embodiment of the present application also provides an electronic device, including: a memory for storing a program; and a processor, coupled to the memory, for executing the program to perform the file generation method described above.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.

It will be appreciated that the relevant features of the methods and apparatus described above may be referenced to one another. In addition, the "first", "second", and the like in the above embodiments are for distinguishing the embodiments, and do not represent the merits and merits of the embodiments.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a construction of such a system is apparent from the description above. In addition, the present application is not directed to any particular programming language. It should be appreciated that the teachings of the present application as described herein may be implemented in a variety of programming languages and that the foregoing descriptions of specific languages are provided for disclosure of preferred embodiments of the present application.

Furthermore, the memory may include volatile memory, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), in a computer readable medium, the memory including at least one memory chip.

Those skilled in the art will appreciate that embodiments of the application may be provided as methods, systems, and articles of manufacture,

Or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data tapping device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data tapping device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data cutting apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data-cutting apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims

1. A firmware upgrade method applied to a domain controller of a vehicle, the method comprising:

2. The method of claim 1, wherein the manifest file records a correspondence between a sensor controller and sensor firmware through an address corresponding to the sensor controller, and searching for target sensor firmware in the manifest file based on sensor controller and sensor attribute information corresponding to a sensor to be upgraded in the first domain, comprising:

searching a target address of a sensor controller corresponding to the sensor to be upgraded in the list file;

if the target address is found and the first sensor firmware exists in the sensor firmware corresponding to the target address, determining the first sensor firmware as the target sensor firmware; and the sensor attribute information corresponding to the first sensor firmware is consistent with the sensor attribute information corresponding to the sensor to be upgraded.

3. The method according to claim 2, wherein the method further comprises:

if the target address is not found or the first sensor firmware does not exist in the sensor firmware corresponding to the target address, a prompt of firmware upgrading abnormality is sent to the sensor to be upgraded.

4. The method of claim 1, wherein the manifest file is further used for recording memory address information corresponding to each sensor firmware, and performing firmware upgrade on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware, including:

determining the burning position of the sensor to be upgraded in the corresponding sensor controller based on the memory address information corresponding to the target sensor firmware;

and burning the target sensor firmware at the burning position to finish the firmware upgrading of the sensor to be upgraded.

5. The method of any of claims 1-4, wherein prior to firmware upgrade of the sensor to be upgraded in a sensor controller corresponding to the sensor to be upgraded by the target sensor firmware, the method further comprises:

Detecting whether the target sensor firmware is in binary format;

if yes, the step of carrying out firmware upgrading on the sensor to be upgraded in the sensor controller corresponding to the sensor to be upgraded through the target sensor firmware is carried out;

otherwise, the target sensor firmware is converted to a binary format.

6. The method according to any one of claims 1-4, wherein the manifest file is further used to record domain controller firmware corresponding to the domain controller, and the method further comprises:

and carrying out firmware upgrade on the domain controller based on the domain controller firmware.

7. The method of any of claims 1-4, wherein after firmware upgrade of the sensor to be upgraded in a sensor controller corresponding to the sensor to be upgraded by the target sensor firmware, the method further comprises:

judging whether all sensors in the first domain are upgraded;

if not, selecting a new sensor to be upgraded from the sensors which are not upgraded, and transferring to execute the step of searching the target sensor firmware in the manifest file based on the sensor controller and the sensor attribute information corresponding to the sensor to be upgraded in the first domain.

8. A file generation method, applied to a server, the method comprising:

9. The method of claim 8, wherein establishing a correspondence between sensor firmware within each group and a corresponding sensor controller comprises:

determining the address corresponding to each packet; wherein, the address is the address of the sensor controller corresponding to the corresponding group;

based on the addresses corresponding to each packet, a correspondence between the sensor firmware and the corresponding sensor controller within each packet is established.

10. The method of claim 8, wherein after retrieving sensor firmware provided by a sensor vendor, the method further comprises:

the acquired sensor firmware is converted into a binary format.

11. The method of any of claims 8-10, wherein prior to obtaining sensor firmware provided by a sensor vendor and sensor attribute information corresponding to the sensor firmware, the method further comprises:

acquiring a firmware pressure measurement report provided by a sensor provider; the firmware pressure measurement report is used for describing the performance condition of the corresponding sensor firmware;

verifying the obtained firmware pressure measurement report;

issuing a providing instruction to a corresponding sensor provider for a pressure measurement report passing verification; the providing instruction is used for informing the corresponding sensor provider of providing sensor firmware corresponding to the pressure measurement report and sensor attribute information corresponding to the sensor firmware.

12. The method according to any one of claims 8-10, further comprising:

acquiring domain controller firmware corresponding to the target domain controller;

and recording the corresponding relation between the domain control firmware and the target domain controller in the list file.

13. A firmware upgrade apparatus for use with a domain controller of a vehicle, the apparatus comprising:

14. A file generation device for application to a server, the device comprising:

15. A computer-readable storage medium, characterized in that the storage medium comprises a stored program, wherein the program, when run, controls a device in which the storage medium is located to perform the firmware upgrade method of any one of claims 1 to 7 and/or to perform the file generation method of any one of claims 8 to 12.

16. An electronic device, the electronic device comprising:

A memory for storing a program;

a processor coupled to the memory for running the program to perform the firmware upgrade method of any one of claims 1 to 7 and/or to perform the file generation method of any one of claims 8 to 12.