CN117075922A - Heterogeneous cross-domain controller upgrading method, device, equipment and medium - Google Patents
Heterogeneous cross-domain controller upgrading method, device, equipment and medium Download PDFInfo
- Publication number
- CN117075922A CN117075922A CN202310928123.0A CN202310928123A CN117075922A CN 117075922 A CN117075922 A CN 117075922A CN 202310928123 A CN202310928123 A CN 202310928123A CN 117075922 A CN117075922 A CN 117075922A
- Authority
- CN
- China
- Prior art keywords
- firmware
- upgraded
- version information
- domain controller
- image file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000003860 storage Methods 0.000 claims abstract description 45
- 230000001680 brushing effect Effects 0.000 claims abstract description 14
- 238000005192 partition Methods 0.000 claims description 52
- 238000012795 verification Methods 0.000 claims description 14
- 238000012545 processing Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 12
- 238000005096 rolling process Methods 0.000 claims description 11
- 238000001514 detection method Methods 0.000 claims description 7
- 238000005457 optimization Methods 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 4
- 238000004519 manufacturing process Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000012827 research and development Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 239000000306 component Substances 0.000 description 7
- 238000013461 design Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 230000006978 adaptation Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 239000004973 liquid crystal related substance Substances 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000010923 batch production Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a heterogeneous cross-domain controller upgrading method, a heterogeneous cross-domain controller upgrading device, heterogeneous cross-domain controller upgrading equipment and a medium, wherein the heterogeneous cross-domain controller upgrading method comprises the following steps: acquiring firmware to be upgraded of the heterogeneous cross-domain controller and making an image file, wherein version information is carried in the image file; reading version information of firmware which does not need to be upgraded in the heterogeneous cross-domain controller; verifying version information corresponding to the image file according to version information of firmware which does not need to be updated; if the version information corresponding to the image file is compatible with the version information of the firmware which does not need to be updated, checking is passed, the version information corresponding to the image file and the image file are written into an address space corresponding to the storage device in a refreshing mode, so that updating is completed, and before updating, the version information of the firmware which does not need to be updated in the image file and the heterogeneous cross-domain controller is checked, so that on one hand, software error brushing is avoided, and the accuracy and the efficiency of firmware updating are improved; on the other hand, the research and development cost and the maintenance cost of the software are also reduced.
Description
Technical Field
The application belongs to the technical field of vehicle software, and particularly relates to a heterogeneous cross-domain controller upgrading method, device, equipment and medium.
Background
With the evolution of the whole vehicle EE (Electronic Engineering, electronic and electric) architecture and the development of ICT (Information Communications Technology, information communication technology) technology, SOC (System on Chip) computing power can bear more services, and the current whole vehicle electronic and electric architecture tends to be changed from a distributed architecture to a domain-centralized architecture. Therefore, the whole-vehicle cross-domain controller generally adopts a heterogeneous configuration design of an SOC chip integrated MPU (Micro processor Unit, a microprocessor, namely an A core) +MCU (Micro controller Uni, a microcontroller, namely an R core or an M core).
However, in the related art, when the heterogeneous cross-domain controller is adopted to develop the whole vehicle cross-domain controller (Vehicle Computing Platform), not only the software to be refreshed needs to be split into a plurality of image files, but also complex software strategies need to be designed for adaptation, for example, firmware version compatibility checking and software development and maintenance are required, so that development cost and maintenance cost are high, and firmware upgrading efficiency is low and upgrading success rate cannot be ensured.
Disclosure of Invention
In view of the above drawbacks of the prior art, the present application aims to provide a heterogeneous cross-domain controller upgrading method, device, equipment and medium, which are used for solving the problems of high upgrading cost and low upgrading efficiency in upgrading a heterogeneous cross-domain controller in the prior art.
To achieve the above and other related objects, a first aspect of the present application provides a heterogeneous cross-domain controller upgrade method, including:
acquiring firmware to be upgraded in a heterogeneous cross-domain controller and making an image file, wherein version information is carried in the image file; reading version information of firmware which does not need to be updated in a partition to be updated; verifying version information corresponding to the image file according to the version information of the firmware which does not need to be updated; if the version information corresponding to the image file is compatible with the version information of the firmware which does not need to be upgraded, checking is passed, the version information corresponding to the image file is stored in an address space corresponding to a storage device configuration file, and the image file is written in the address space corresponding to the storage device in a refreshing mode to finish upgrading.
A second aspect of the present application provides a heterogeneous cross-domain controller upgrade apparatus, including: the file making module is used for obtaining firmware to be upgraded in the heterogeneous cross-domain controller and making an image file, wherein version information is carried in the image file; the heterogeneous cross-domain controller at least comprises a partition to be upgraded; the version verification module is used for verifying version information corresponding to the image file according to the version information of the firmware which does not need to be upgraded; and the firmware upgrading module is used for checking if the version information corresponding to the image file is compatible with the version information of the firmware which does not need to be upgraded, storing the version information corresponding to the image file into an address space corresponding to the storage equipment configuration file, and writing the image file into the address space corresponding to the storage equipment in a refreshing way so as to finish upgrading.
A third aspect of the present application provides a heterogeneous cross-domain controller upgrade apparatus, comprising: one or more processing devices; a memory for storing one or more programs; when the one or more programs are executed by the one or more processing devices, the one or more processing devices are caused to implement the heterogeneous cross-domain controller upgrade method described above.
A fourth aspect of the present application provides a computer-readable storage medium having stored thereon a computer program for causing the computer to execute the heterogeneous cross-domain controller upgrade method described above.
As described above, the heterogeneous cross-domain controller upgrading method, device, equipment and medium according to the technical scheme of the application have the following beneficial effects:
before firmware upgrading, the version information corresponding to the image file is checked through the version information of the firmware which does not need to be upgraded; if the version information corresponding to the image file is compatible with the version information of the firmware to be upgraded, checking to pass, and refreshing the image file to an address space corresponding to the storage device to finish upgrading; compared with the existing mode, on one hand, complex software strategy adaptation for image file design and compatibility check for firmware version are avoided, meanwhile, software error brushing is avoided, and accuracy and efficiency of firmware upgrading are improved; on the other hand, the research and development cost and the maintenance cost of the software are also reduced.
Drawings
FIG. 1 is a diagram showing an implementation environment of a heterogeneous cross-domain controller upgrade method provided by the present application;
FIG. 2 is a flow chart of a method for upgrading a heterogeneous cross-domain controller provided by the application;
FIG. 3 is a flowchart illustrating an implementation of S230 in a heterogeneous cross-domain controller upgrade method according to the present application;
FIG. 4 shows a complete flowchart of a heterogeneous cross-domain controller upgrade method provided by the present application;
FIG. 5 is a block diagram showing the structure of a heterogeneous cross-domain controller upgrading device according to the present application;
fig. 6 is a schematic structural diagram of an electronic device suitable for implementing an embodiment of the present application.
Detailed Description
Other advantages and effects of the present application will become apparent to those skilled in the art from the following disclosure, which describes the embodiments of the present application with reference to specific examples. The application may be practiced or carried out in other embodiments that depart from the specific details, and the details of the present description may be modified or varied from the spirit and scope of the present application. It should be noted that the following embodiments and features in the embodiments may be combined with each other without conflict.
It should be noted that the illustrations provided in the following embodiments merely illustrate the basic concept of the present application by way of illustration, and only the components related to the present application are shown in the drawings and are not drawn according to the number, shape and size of the components in actual implementation, and the form, number and proportion of the components in actual implementation may be arbitrarily changed, and the layout of the components may be more complicated.
The embodiment of the application provides a heterogeneous cross-domain controller upgrading method which can be applied to a terminal, a server or software running in the terminal or the server. In some embodiments, the terminal may be an electronic device such as a smart phone, tablet computer, vehicle terminal, notebook computer, or desktop computer; the server can be configured as an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, basic cloud computing services such as big data and artificial intelligent platforms and the like; the software may be an application program or the like generated by the firmware program upgrade, but is not limited to the above form.
For example, referring to fig. 1, taking the heterogeneous cross-domain controller upgrade method as an example, the vehicle terminal may obtain firmware to be upgraded (i.e., a software program to be upgraded) of a first controller and a second controller in the heterogeneous cross-domain controller, and make an image file according to the firmware to be upgraded of the first controller and the second controller, where the image file carries version information; reading version information of firmware which does not need to be updated in the first controller and the second controller; verifying version information corresponding to the image file according to version information of firmware which does not need to be updated; if the version information corresponding to the image file is compatible with the version information without updating firmware, checking is passed, the version information corresponding to the image file is stored in an address space corresponding to the storage device configuration file, and the image file is written in the address space corresponding to the storage device in a refreshing mode to finish updating.
The present invention will be described in detail with reference to specific examples. Referring to fig. 2, fig. 2 is a flowchart of a heterogeneous cross-domain controller upgrading method according to an embodiment of the present invention, including the following steps:
step S210, obtaining firmware to be upgraded in the heterogeneous cross-domain controller, and manufacturing an image file according to the firmware to be upgraded, wherein version information is carried in the image file;
The heterogeneous cross-domain controller generally adopts a design of integrating an MPU (A core) +MCU (R core or M core) heterogeneous configuration by using an SOC chip, wherein a SoC (System on Chip) chip is an integrated circuit technology, and refers to integrating all functional components of a computer system, including a central processing unit, a memory, an I/O (input/output) interface, a display controller and the like, on one chip. MPU Mi cro P rocessor Unit) a Central Processing Unit (CPU) in a microcomputer is called a Microprocessor (MPU), and is a core component constituting the microcomputer, and may be referred to as a heart of the microcomputer. It plays a role in controlling the operation of the whole microcomputer, generating control signals to control the corresponding components, and executing the corresponding operations. MCU is Micro Controller Unit for short, chinese called microcontroller, commonly called singlechip, which is to reduce the frequency and specification of CPU (central processing unit), integrate interfaces such as memory, counter, USB (universal serial bus), A/D (analog/digital) conversion, and even LCD (liquid crystal display) drive circuit on a chip to form a chip-level computer, and provide various combination control for application occasions of various colors.
Specifically, if the heterogeneous cross-domain controller is composed of a first controller which is an MPU (a core) microprocessor and a second controller which is an MCU (R core or M core) microcontroller, a first image file containing a microprocessor software basic package, a second image file containing a microcontroller software package, and a third image file containing a microprocessor software package are respectively manufactured, wherein the software basic package is applicable to all vehicle models on the same platform, is a general program file, and the second image file and the third image file are different along with the different vehicle models, namely, the corresponding software variable packages of each vehicle model are different, and the corresponding software variable packages of the microcontroller software packages are also different.
The quantity of mirror image files manufactured by the heterogeneous cross-domain controller is determined according to the types of the first controller and the second controller, for example, the whole vehicle cross-domain controller (Vehicle Computing Platform) adopts a single SOC (A core+R core) to adapt to a client platform type vehicle, wherein the A core software consists of two mirror image files of a basic software package and a variable software package, the basic software package is applicable to all vehicle types of the same platform, the variable software packages are different due to different vehicle type configurations, and the R core software is uniformly packaged into one mirror image file to form three mirror image files.
In the embodiment, as the cross-domain controller software package is designed into three image files according to the update frequency, the problem that complex software strategy adaptation is required to be designed for checking the compatibility of the firmware version and developing and maintaining the software when the cross-domain controller software package is further finely disassembled into more image files is avoided, so that the development cost and the software maintenance cost are greatly reduced; meanwhile, when the software of the three mirror image files is updated, dependency checking can be carried out, so that software error brushing among different vehicle types can be avoided, the usability of vehicle functions is ensured, and the after-sale cost is reduced.
It should be further noted that, the heterogeneous cross-domain controller may further include an ARM core and a DSP core to form an heterogeneous design, and the present application is not limited to two cores, and may further include multi-core heterogeneous designs such as an ARM core, a DSP core, an FPGA core, and the like, which are not described herein in detail.
It should be appreciated that creating an image file includes the following: acquiring requirement information for generating an image file, wherein the requirement information comprises identification information of the file to be imaged and configuration information corresponding to the file to be imaged; acquiring an installation file of the mirror image file to be generated according to the identification information; installing the installation file on a pre-created virtual host to generate a file to be mirrored; selecting a customized file matched with the configuration information from a pre-stored customized file set, wherein the customized file contains data required for modifying the file content; and updating the file to be mirrored based on the customized file matched with the configuration information, and generating the mirrored file.
In the embodiment, the automatic generation of the image file is realized, so that batch production of the image file is facilitated. Meanwhile, the artificial participation process is reduced, and the consistency of the same mirror image file is guaranteed.
In some embodiments, a firmware upgrade task package for heterogeneous cross-domain controllers in each target vehicle is received based on an OTA over-the-air technology, wherein the firmware upgrade task package is made into an image file, and the image file includes a vehicle model to which the firmware to be upgraded belongs, a model of the firmware to be upgraded (special software firmware) (for example, an a core, an R core, an M core), an upgrade package (image) associated with each firmware to be upgraded, and version information carried.
Making an image file according to firmware to be upgraded of the first controller and the second controller, wherein version information is carried in the image file;
the OTA (Over-the-Air) refers to a technology for remotely managing firmware, data and applications on a part terminal of a target vehicle through a mobile communication network (4G/5G or Wifi). Briefly, the OTA technique is implemented in three steps: firstly, uploading the update software to an OTA center of a cloud, then, wirelessly transmitting the update software to a target vehicle by the OTA center, and finally, automatically updating the software by a heterogeneous cross-domain controller in the target vehicle.
It should be noted that, in the image file of the heterogeneous cross-domain controller in the present application, each firmware to be upgraded generates one image file, and there is no case that multiple firmware generates one image file.
Step S220, reading version information of firmware which does not need to be upgraded in the partition to be upgraded;
specifically, the heterogeneous cross-domain controller reads software version information of all firmware in the first controller and the second controller and feeds the software version information back to the cloud, and the cloud compares the received firmware to be upgraded with all firmware version information fed back by the vehicle end to determine whether the firmware upgrade needs to be pushed to the vehicle end (namely, the target vehicle).
For example, the cloud end determines which firmware to be upgraded and which firmware to be not upgraded, and sends version information corresponding to the firmware to be upgraded to the target vehicle, so as to determine the version information of the partition to be upgraded (backup operation partition) without the firmware to be upgraded.
Step S230, verifying version information corresponding to the image file according to the version information without updating firmware;
in some embodiments, referring to fig. 3, verifying version information corresponding to an image file according to version information of firmware to be upgraded, further includes:
step S310, determining the type of the controller to which the firmware to be upgraded belongs in the heterogeneous cross-domain controller and version information of the firmware which is not required to be upgraded;
the firmware is a basic software package, a variable software package and an MCU software package.
Step S320, determining at least one image file associated with the firmware to be upgraded according to the type of the controller to which the firmware to be upgraded does not need to be upgraded, and reading at least one version information associated with the current firmware to be upgraded in the at least one image file;
specifically, for example, the a-core software upgrade package is divided into a base software package and a variable software package, and is composed of two image files.
Step S330, comparing the version information associated with the current firmware to be upgraded in the image file with the version information associated with the firmware not to be upgraded in the heterogeneous cross-domain controller, and checking the compatibility between the image file and the firmware not to be upgraded.
In the first case, if only one version information related to only one firmware to be upgraded exists in the image file, comparing the current only one version information with the version information related to the firmware which does not need to be upgraded in the heterogeneous cross-domain controller, and checking the compatibility between the image file and the firmware which does not need to be upgraded;
specifically, the image file refers to a file generated by adding firmware to be upgraded (software to be updated) and software version information, and each firmware to be upgraded corresponds to one image file.
In the second case, if at least two version information related to the firmware to be upgraded currently in the image file, comparing the at least two version information with version information related to the firmware which does not need to be upgraded in the heterogeneous cross-domain controller, and checking compatibility between the image file and the firmware which does not need to be upgraded and compatibility between the image files.
Each firmware to be upgraded corresponds to one image file, two or more version information are associated with one image mailing file corresponding to the current firmware to be upgraded, and verification can be completed only by respectively comparing the current two or more version information with the version information associated with the firmware to be upgraded.
Specifically, compatibility between image files can be achieved through the cloud. If the version information related to the image file and the version information of the firmware which does not need to be upgraded belong to the same class of a preset compatibility table, wherein the preset compatibility table is used for representing the compatibility among various software package versions; compatibility is determined to be satisfied between the image file and the firmware that does not need to be upgraded. Comparing version information to determine compatibility may also include, for example, V1.0.1 as version information associated with firmware to be upgraded in an image file, where v1.0 belongs to major version information and 1 belongs to minor version information, and when comparing version information to determine compatibility, only major version information of two version information needs to be compared, and if major version information is the same, two versions are determined to be compatible. Therefore, whether the subclass version information is the same or not is not required to be considered, the preset compatibility table is not required to be used, the problem that the preset compatibility table is difficult to maintain and manage along with frequent updating is avoided, and the compatibility can be easily determined through simple comparison.
By the mode, at least compatibility between the image file and the current firmware which does not need to be updated is determined, the situations of error brushing, error brushing and the like are effectively avoided, and the success rate of firmware updating and brushing is improved.
Step S240, if the version information corresponding to the firmware to be upgraded of the image file is compatible with the version information of the firmware not to be upgraded, checking to pass, storing the version information corresponding to the firmware to be upgraded into the address space corresponding to the storage device configuration file, and writing the image file into the address space corresponding to the storage device to finish the upgrading.
Specifically, if the version information corresponding to the firmware to be upgraded in the image file is incompatible with the version information of the firmware not to be upgraded, verification is not passed, and firmware upgrading is not performed, wherein the version information corresponding to the firmware to be upgraded is stored in the head of the image file, and after the image file is completely received, the version information is obtained through analysis.
It should be noted that, if the same firmware to be upgraded corresponds to one image file, not only version information corresponding to the image file and version information of firmware to be upgraded need to be checked, so that compatibility between a version in the image file corresponding to the firmware to be upgraded and a version of firmware to be upgraded need to be determined, but also version information between two or more image files needs to be checked, so that compatibility between the firmware to be upgraded needs to be determined. It should be understood that the version information corresponding to the image file is saved to the address space corresponding to the configuration file of the storage device, and the corresponding image file needs to be written to the address space corresponding to the storage device, so that the firmware upgrade can be completed.
Optionally, in some embodiments, before verifying version information corresponding to the image file according to version information of firmware to be upgraded, the method further includes:
determining the vehicle type of the heterogeneous cross-domain controller according to the read vehicle type configuration information table; and determining the vehicle type of the heterogeneous cross-domain controller according to the target vehicle where the heterogeneous cross-domain controller is acquired.
If the version information carried in the mirror image file accords with the vehicle model to which the current heterogeneous cross-domain controller belongs, triggering and checking the version information; if the version information carried in the mirror image file is inconsistent with the vehicle model to which the current heterogeneous cross-domain controller belongs, the version information is not triggered to be checked.
In the embodiment, the heterogeneous cross-domain controller is developed according to a platform, but different configuration vehicle types exist on the platform, configuration information of the vehicle type is written into the heterogeneous cross-domain controller through a diagnostic instrument when the whole vehicle is off line, and the heterogeneous cross-domain controller firstly reads the vehicle type configuration information to identify a specific vehicle type when software is written (OTA or external diagnostic instrument is connected with the controller for writing); the heterogeneous cross-domain controller checks whether the software to be brushed belongs to the vehicle model based on the identified vehicle model; if the software to be refreshed belongs to the vehicle model, further checking whether the version information of the software to be input is compatible with the version information of other software in the current heterogeneous cross-domain controller, otherwise, if the software to be refreshed does not belong to the vehicle model, not triggering the verification of the version information of the software.
Through the mode, the problem of firmware upgrading failure caused by error brushing can be avoided, and through checking the compatibility between the vehicle type and the version information in advance, on one hand, the success accuracy of firmware upgrading can be improved, and on the other hand, the firmware upgrading flow is simplified.
In some embodiments, before the upgrade is completed, further comprising:
performing reliability detection on a corresponding upgrading environment of a target vehicle to which the heterogeneous cross-domain controller belongs, wherein the upgrading environment comprises the working state of the target vehicle, a processor, a memory and the electric quantity of a magnetic disk and a battery; if each configuration parameter in the upgrading environment is detected to meet the preset requirement, triggering upgrading; if the fact that a certain configuration parameter in the upgrading environment does not meet the preset requirement is detected, the configuration parameter is displayed for reminding, meanwhile, the upgrading success rate of the heterogeneous cross-domain controller is estimated, and an optimization suggestion for adjusting the corresponding configuration parameter is generated.
In the embodiment, through reliability detection on the upgrading environment where the target vehicle is located, after the upgrading environment meets the reliability detection requirement, the subsequent upgrading can be triggered, so that the success rate of firmware upgrading is ensured from the hardware environment, and the firmware upgrading failure caused by hardware is avoided; meanwhile, when the detection of the upgrading environment does not meet the requirement, prompt is carried out through timely feedback, and meanwhile, optimization suggestions for adjusting corresponding configuration parameters are given, so that the target vehicle currently meets the upgrading environment to carry out reliability detection.
In some embodiments, after the upgrade is completed, further comprising:
loading the updated firmware, and determining whether the heterogeneous cross-domain controller is successfully updated according to version information of the updated firmware; if the heterogeneous cross-domain controller is not successfully upgraded, rolling back the firmware which is currently failed to be upgraded of the heterogeneous cross-domain controller to a version before upgrading in an OTA scene, or/and, using a diagnostic instrument to brush the upgrading scene, and responding to the operation of the diagnostic instrument; and if the heterogeneous cross-domain controller is successfully upgraded, displaying that the upgrading is successful.
Specifically, the OTA is an online upgrade mode, and the diagnostic apparatus is an offline upgrade mode.
Through upgrade verification, whether the firmware is successfully upgraded or not can be detected, and the firmware upgrade management is facilitated.
In some embodiments, if the heterogeneous cross-domain controller upgrade is unsuccessful, rolling back the version before the upgrade of the firmware that fails to be upgraded according to the current OTA scenario, further including:
and carrying out firmware version rollback on the firmware which is failed to be upgraded currently through a preset rollback strategy, and after the firmware version rollback is completed, brushing the firmware of the heterogeneous cross-domain controller to a version before the upgrade, wherein the rollback strategy comprises the steps of acquiring a firmware rollback package and the current battery electric quantity of a target vehicle, and if the current battery electric quantity is greater than or equal to a preset minimum electric quantity threshold value, carrying out firmware version rollback through installing the firmware rollback package.
The method comprises the steps that firmware version upgrading is conducted on a cross-domain controller, and if the firmware which is failed to upgrade currently is upgraded, whether a target vehicle meets rollback conditions is determined through rollback strategies; for example, if the current battery power is greater than or equal to the preset minimum power threshold, the firmware version rollback is performed according to the firmware rollback policy. If the heterogeneous cross-domain controller has a partition, the firmware version can be rolled back through switching the partition, and compared with the process of rolling back the firmware version through installing a rolling back package, the rolling back time is reduced, so that the electric quantity consumption is reduced, on the other hand, when the cross-domain controller cannot be operated through switching the partition, under the condition that the current battery electric quantity of the vehicle terminal meets the minimum electric quantity threshold value, the rolling back package is installed to roll back the firmware version, so that the situation that the electric quantity consumption of the vehicle storage battery is excessive due to the rolling back of the firmware version, and the vehicle cannot be started is avoided.
Optionally, in some embodiments, the validity of the image file is determined according to the verification performed by loading the image file by the heterogeneous cross-domain controller; the downloaded image file is subjected to the following verification, for example, the Hash verification and the upgrade package signature are used for verifying the integrity and the legality of the upgrade package, and if the verification is satisfied, the image file is determined to satisfy the validity.
In some embodiments, before the upgrade is completed, further comprising: the storage device backs up the firmware and the firmware version information into the nonvolatile memory, and simultaneously backs up the version before the firmware to be upgraded is upgraded to form a firmware rollback package.
By setting the rollback mechanism, the firmware to be upgraded is not successfully upgraded, and the firmware which is failed to upgrade can be rolled back to the firmware version before being upgraded, so that normal use of vehicle functions is not influenced.
In some embodiments, storing version information corresponding to firmware to be upgraded in an address space corresponding to a storage device configuration file, and writing an image file in the address space corresponding to the storage device to complete the upgrade, including:
if the number of the firmware to be upgraded is multiple, generating an upgrading order according to the type of the controller to which each firmware to be upgraded belongs and the priority of each firmware to be upgraded;
the heterogeneous cross-domain controller comprises a main operation partition and a backup operation partition, wherein the main operation partition and the backup operation partition both comprise a first controller and a second controller to operate firmware to be upgraded;
the to-be-upgraded partition is a backup operation partition, the firmware to be upgraded in the backup operation partition is upgraded according to the upgrading order, and the heterogeneous cross-domain controller is switched to the backup operation partition for operation after the backup operation partition is upgraded.
Specifically, after the backup operation partition is upgraded, after the power-off, the heterogeneous cross-domain controller is switched to the backup operation partition, the upgraded backup operation partition is used as a new main operation partition, and in order not to influence the operation service of the heterogeneous cross-domain controller, the original main operation partition which is not upgraded is used as the new backup operation partition, so that the new round of upgrading operation is completed.
In this embodiment, the upgrade order of each firmware to be upgraded is determined by the upgrade order, so that the firmware upgrade failure can be ensured, the original firmware version can be rolled back normally,
in other embodiments, referring to fig. 4, a complete flowchart of a heterogeneous cross-domain controller upgrade method provided by the present application is described in detail below:
1) When an image file of the core software basic package A, the core software package R and the core software variable package A is produced, version information is packed in the head of the image file;
2) Reading version information (such as V1.0.1 _delta) of an image from the head of an A/R core software image file to be upgraded when FOTA (over-the-air software upgrade of a mobile terminal) or a diagnostic instrument refreshes and upgrades the A/R core software;
3) Reading version information (V1.0.1) of other un-upgraded firmware in the flash zone cross-domain controller from Bootcfg (fault recovery control instruction) of an EMMC (embedded memory) of the peripheral storage device;
4) Reading version information of the two image files, and allowing upgrading if and only if the basic version number (namely, the A-core software basic package) is consistent with the previous basic version information (namely, the A-core software variable package) of the variable version number (namely, the A-core software variable package) as shown in a schematic V1.0.1; if the images are not compatible, the upgrade is not allowed;
5) If the verification result is that the updating is allowed, writing version information of the mirror image to be refreshed into a Bootcfg address space corresponding to the EMMC;
6) And writing the mirror image file to be refreshed into an address space corresponding to the EMMC to finish the refreshing and upgrading at the present time.
In this embodiment, since the frequency of changing and updating after the mass production of the basic software package of the a-core is small, when designing, the strong dependency relationship parts such as the IPC protocol of the a-core and the R-core image are put into the basic package image of the a-core as much as possible, and any change of the interaction format of the IPC-related protocol or application in the basic package image of the a-core or the image of the R-core affects the running compatibility of the two images, so that the compatibility identification requirement between different images is considered when naming the version numbers of the files of the R-core and the image of the a-core in the earlier stage of project development. It is necessary to check the dependency of the software to be refreshed when any firmware of the VCP is updated by a refresh.
Before firmware is upgraded, the version information corresponding to the image file is checked through the version information without upgrading the firmware; if the version information corresponding to the image file is compatible with the version information without updating firmware, checking the version information to pass, and refreshing the image file to an address space corresponding to the storage device to finish updating; compared with the existing mode, on one hand, complex software strategy adaptation for image file design, firmware version compatibility checking and software development and maintenance are avoided, meanwhile, software error brushing is avoided, and the accuracy and efficiency of firmware upgrading are improved; on the other hand, the research and development cost and the maintenance cost of the software are also reduced.
Referring to fig. 5, a block diagram of a heterogeneous cross-domain controller upgrade apparatus 500 provided by the present application includes:
the file making module 501 is configured to obtain firmware to be upgraded in the heterogeneous cross-domain controller and make an image file, where version information is carried in the image file; the method comprises the steps of carrying out a first treatment on the surface of the
The version information determining module 502 is configured to read version information of firmware to be upgraded in the partition to be upgraded, where the heterogeneous cross-domain controller at least includes the partition to be upgraded
A version verification module 503, configured to verify version information corresponding to the image file according to version information of the firmware that does not need to be upgraded;
and the firmware upgrade module 504 is configured to, if the version information corresponding to the image file is compatible with the version information of the firmware that does not need to be upgraded, check and pass, save the version information corresponding to the image file to an address space corresponding to the storage device configuration file, and write the image file to the address space corresponding to the storage device in a refreshing manner, so as to complete the upgrade.
In some embodiments, if the heterogeneous cross-domain controller is composed of a first controller that is a microprocessor and a second controller that is a microcontroller, a first image file that includes a microprocessor software foundation package, a second image file that includes a microcontroller software foundation package, and a third image file that includes a microprocessor software variable package are respectively manufactured, where the software foundation package is applicable to all vehicle models of the same platform, and the software variable package and the microcontroller software package corresponding to each vehicle model are different.
In some embodiments, before verifying version information corresponding to the image file according to version information of firmware that does not need to be upgraded, the method further includes: determining the type of the vehicle according to the read type configuration information table; if the version information of the head part of the mirror image file is consistent with the vehicle model of the current heterogeneous cross-domain controller, triggering verification of the version information; if the version information carried in the mirror image file is inconsistent with the vehicle model to which the current heterogeneous cross-domain controller belongs, the version information is not triggered to be checked.
In some embodiments, the version verification module 503 further comprises: determining the type and version information of the controller to which the firmware does not need to be upgraded in the partition to be upgraded; determining at least one image file associated with the current firmware to be upgraded according to the type of the controller to which the firmware to be upgraded does not need to be upgraded, and reading at least one version information associated with the current firmware to be upgraded in the at least one image file; if the version information related to the current firmware to be upgraded in the image file is compared with the version information related to the firmware which does not need to be upgraded in the heterogeneous cross-domain controller, the compatibility between the image files is checked, or/and the compatibility between the image files and the firmware which does not need to be upgraded is checked.
If only one version information related to the current firmware to be upgraded in the image file is related to the version information related to the firmware to be upgraded in the heterogeneous cross-domain controller, comparing the current only one version information with the version information related to the firmware to be upgraded in the heterogeneous cross-domain controller, and checking the compatibility between the image file and the firmware to be upgraded;
and if at least two pieces of version information related to the firmware to be upgraded currently in the image file are compared with the version information related to the firmware which does not need to be upgraded in the heterogeneous cross-domain controller, checking the compatibility between the image file and the firmware which does not need to be upgraded and checking the compatibility between the image file.
In some embodiments, before firmware upgrade module 504 completes the upgrade, it further comprises: performing reliability detection on a corresponding upgrading environment of a target vehicle to which the heterogeneous cross-domain controller belongs, wherein the upgrading environment comprises the working state of the target vehicle, a processor, a memory and the electric quantity of a magnetic disk and a battery; if each configuration parameter in the upgrading environment is detected to meet the preset requirement, triggering upgrading; if the fact that a certain configuration parameter in the upgrading environment does not meet the preset requirement is detected, the configuration parameter is displayed, meanwhile, the upgrading success rate of the heterogeneous cross-domain controller is estimated, and an optimization suggestion for adjusting the corresponding configuration parameter is generated.
In some embodiments, after firmware upgrade module 504 completes the upgrade, it further includes: loading the updated firmware, and determining whether the heterogeneous cross-domain controller is successfully updated according to version information of the updated firmware; if the heterogeneous cross-domain controller is not successfully upgraded, rolling back firmware which is failed to be upgraded currently to a version before upgrading according to the current OTA scene, or/and, brushing the upgrading scene by using a diagnostic instrument, and responding to the operation of the diagnostic instrument through the cross-domain controller; and if the heterogeneous cross-domain controller is successfully upgraded, displaying that the upgrading is successful.
In some embodiments, if the heterogeneous cross-domain controller upgrade is unsuccessful, rolling back the version before the upgrade according to the firmware that the heterogeneous cross-domain controller current upgrade fails, further comprising: and carrying out firmware version rollback on the firmware which is failed to be upgraded currently through a preset rollback strategy, and after the firmware version rollback is completed, brushing the firmware of the heterogeneous cross-domain controller to a version before the upgrade, wherein the rollback strategy comprises the steps of acquiring a firmware rollback package and the current battery electric quantity of a target vehicle, and if the current battery electric quantity is greater than or equal to a preset minimum electric quantity threshold value, carrying out firmware version rollback through installing the firmware rollback package.
In some embodiments, firmware upgrade module 504, before the upgrade is completed, further comprises: and backing up the image file and version information stored by the storage device to the flash memory, and backing up the version before the firmware to be upgraded is upgraded to form a firmware rollback package.
In some embodiments, storing version information corresponding to the image file in an address space corresponding to a configuration file of the storage device, and writing the image file in the address space corresponding to the storage device to complete the upgrade, including:
If the number of the firmware to be upgraded is multiple, generating an upgrading order according to the type of the controller to which each firmware to be upgraded belongs and the priority of each firmware to be upgraded; the heterogeneous cross-domain controller comprises a main operation partition and a backup operation partition, wherein the main operation partition and the backup operation partition both comprise a first controller and a second controller to operate firmware to be upgraded;
the to-be-upgraded partition is a backup operation partition, the firmware to be upgraded in the backup operation partition is upgraded according to the upgrading order, and the heterogeneous cross-domain controller is switched to the backup operation partition for operation after the backup operation partition is upgraded.
It should be further noted that, the heterogeneous cross-domain controller upgrading method and the heterogeneous cross-domain controller upgrading device are in a one-to-one correspondence relationship, where technical details and technical effects related to the heterogeneous cross-domain controller upgrading device are the same as those of the identification method, and are not described in detail herein, please refer to the heterogeneous cross-domain controller upgrading method.
Before firmware is upgraded, the version information corresponding to the image file is checked through the version information without upgrading the firmware; if the version information corresponding to the image file is compatible with the version information without updating firmware, checking the version information to pass, and refreshing the image file to an address space corresponding to the storage device to finish updating; compared with the existing mode, on one hand, complex software strategy adaptation for image file design, firmware version compatibility checking and software development and maintenance are avoided, meanwhile, software error brushing is avoided, and the accuracy and efficiency of firmware upgrading are improved; on the other hand, the research and development cost and the maintenance cost of the software are also reduced.
Referring now to fig. 6, fig. 6 is a schematic diagram of an electronic device suitable for implementing an embodiment of the present application. It should be noted that, the electronic device 600 shown in fig. 6 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 6, the electronic apparatus 600 includes a central processing unit (Central Processing Unit, CPU) 601, which can perform various appropriate actions and processes, such as performing the methods in the above-described embodiments, according to a program stored in a Read-Only Memory (ROM) 602 or a program loaded from a storage section 608 into a random access Memory (Random Access Memory, RAM) 603. In the RAM603, various programs and data required for system operation are also stored. The CPU 601, ROM 602, and RAM603 are connected to each other through a bus 604. An Input/Output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and a speaker, etc.; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. When being executed by a Central Processing Unit (CPU) 601, performs the various functions defined in the apparatus of the present application.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with a computer-readable computer program embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing.
A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied 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 foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based devices which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to perform a heterogeneous cross-domain controller upgrade method as before. The computer-readable storage medium may be included in the electronic device described in the above embodiment or may exist alone without being incorporated in the electronic device.
The above embodiments are merely illustrative of the principles of the present application and its effectiveness, and are not intended to limit the application. Modifications and variations may be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the application. Accordingly, it is intended that all equivalent modifications and variations of the application be covered by the claims, which are within the ordinary skill of the art, be within the spirit and scope of the present disclosure.
Claims (14)
1. The heterogeneous cross-domain controller upgrading method is characterized by comprising the following steps of:
acquiring firmware to be upgraded of a heterogeneous cross-domain controller and manufacturing an image file, wherein version information is carried in the image file;
reading version information of firmware which does not need to be upgraded in a partition to be upgraded, wherein the heterogeneous cross-domain controller at least comprises the partition to be upgraded;
verifying version information corresponding to the image file according to version information of firmware which does not need to be upgraded in the partition to be upgraded;
if the version information corresponding to the image file is compatible with the version information of the partition to be upgraded without upgrading firmware, checking to pass, storing the version information corresponding to the image file into an address space corresponding to a storage device configuration file, and writing the image file into the address space corresponding to the storage device in a refreshing mode to finish upgrading.
2. The heterogeneous cross-domain controller upgrading method according to claim 1, wherein the number of the image files produced by the heterogeneous cross-domain controller is determined according to the type of each firmware to be upgraded.
3. The heterogeneous cross-domain controller upgrade method according to claim 1 or 2, wherein if the heterogeneous cross-domain controller is composed of a Microprocessor (MPU) as the first controller and a Microcontroller (MCU) as the second controller, a first image file including the basic package of the microprocessor software, a second image file including the software package of the microcontroller, and a third image file including the variable package of the microprocessor software are manufactured respectively, wherein the basic package of the software is applicable to all models of the same platform, and the variable package of the software and the variable package of the microcontroller corresponding to each model of the vehicle are different.
4. The heterogeneous cross-domain controller upgrading method according to claim 3, wherein before verifying version information corresponding to the image file according to version information of firmware to be upgraded in the partition to be upgraded, the method further comprises:
determining the vehicle type of the heterogeneous cross-domain controller according to the version information of the firmware which does not need to be updated in the first controller and the second controller;
if the version information carried in the mirror image file accords with the current vehicle model of the heterogeneous cross-domain controller, triggering and checking the version information; if the version information carried in the mirror image file is inconsistent with the vehicle type to which the heterogeneous cross-domain controller belongs, the version information is not triggered to be checked.
5. The heterogeneous cross-domain controller upgrading method according to claim 1, wherein verifying version information corresponding to the image file according to version information of firmware to be upgraded in the partition to be upgraded comprises:
determining the type and version information of the controller to which the firmware does not need to be upgraded in the partition to be upgraded;
determining at least one image file associated with the firmware to be upgraded currently according to the type of the controller to which the firmware to be upgraded does not need to be upgraded, and reading at least one version information associated with the firmware to be upgraded currently in the at least one image file;
And if the version information related to the current firmware to be upgraded in the image file is compared with the version information related to the firmware which does not need to be upgraded in the heterogeneous cross-domain controller, checking the compatibility between the image files, or/and checking the compatibility between the image file and the firmware which does not need to be upgraded.
6. The heterogeneous cross-domain controller upgrade method according to claim 5, wherein if only one version information associated with the firmware to be upgraded is present in the image file, comparing the present only one version information with version information associated with firmware not to be upgraded in the heterogeneous cross-domain controller, and checking compatibility between the image file and the firmware not to be upgraded;
and if at least two pieces of version information related to the firmware to be upgraded in the image file are currently related to the firmware to be upgraded, comparing the at least two pieces of version information with the version information related to the firmware to be upgraded in the heterogeneous cross-domain controller, and checking the compatibility between the image file and the firmware to be upgraded and the compatibility between the image files.
7. The heterogeneous cross-domain controller upgrade method according to claim 1, further comprising, before the upgrade is completed:
Performing reliability detection on a corresponding upgrading environment of a target vehicle to which the heterogeneous cross-domain controller belongs, wherein the upgrading environment comprises a working state of the target vehicle, a processor, a memory and electric quantity of a magnetic disk and a battery; triggering upgrading if detecting that each configuration parameter in the upgrading environment meets the preset requirement; if the fact that a certain configuration parameter in the upgrading environment does not meet the preset requirement is detected, the configuration parameter is displayed, meanwhile, the upgrading success rate of the heterogeneous cross-domain controller is estimated, and an optimization suggestion for adjusting the corresponding configuration parameter is generated.
8. The heterogeneous cross-domain controller upgrade method according to claim 1, further comprising, after the upgrade is completed:
loading the updated firmware, and determining whether the heterogeneous cross-domain controller is successfully updated according to version information of the updated firmware; if the heterogeneous cross-domain controller is not successfully upgraded, rolling back the firmware which is currently failed to be upgraded of the heterogeneous cross-domain controller to a version before upgrading in an OTA scene, or/and, using a diagnostic instrument to brush the upgrading scene, and responding to the operation of the diagnostic instrument; and if the heterogeneous cross-domain controller is successfully upgraded, displaying that the upgrading is successful.
9. The method for upgrading a heterogeneous cross-domain controller according to claim 8, wherein if the heterogeneous cross-domain controller is not successfully upgraded, rolling back a version of the heterogeneous cross-domain controller before upgrading a firmware that is failed to be upgraded according to a current OTA scenario, further comprising:
and carrying out firmware version rollback on the firmware which is failed to be upgraded currently through a preset rollback strategy, and after the firmware version rollback is completed, brushing the firmware of the heterogeneous cross-domain controller to a version before the upgrade, wherein the rollback strategy comprises the steps of acquiring a firmware rollback package and the current battery electric quantity of a target vehicle, and if the current battery electric quantity is greater than or equal to a preset minimum electric quantity threshold value, carrying out firmware version rollback through installing the firmware rollback package.
10. The heterogeneous cross-domain controller upgrade method according to claim 1, further comprising, before the upgrade is completed: and backing up the image file and version information stored by the storage device to a flash memory, and backing up the version of the firmware to be upgraded before upgrading to form a firmware rollback package.
11. The heterogeneous cross-domain controller upgrade method according to claim 1, wherein saving version information corresponding to the image file to an address space corresponding to a storage device configuration file, and brushing the image file to the address space corresponding to the storage device, so as to complete the upgrade, comprises:
If the number of the firmware to be upgraded is multiple, generating an upgrading order according to the type of the controller to which each firmware to be upgraded belongs and the priority of each firmware to be upgraded;
the heterogeneous cross-domain controller comprises a main operation partition and a backup operation partition, wherein the main operation partition and the backup operation partition both comprise a first controller and a second controller to operate firmware to be upgraded;
and the partition to be upgraded is a backup operation partition, firmware to be upgraded in the backup operation partition is upgraded according to the upgrading order, and after the backup operation partition is upgraded, the heterogeneous cross-domain controller is switched to the backup operation partition for operation.
12. A heterogeneous cross-domain controller upgrade apparatus, comprising:
the file making module is used for obtaining firmware to be upgraded in the heterogeneous cross-domain controller and making an image file, wherein version information is carried in the image file;
the heterogeneous cross-domain controller at least comprises a partition to be upgraded;
the version verification module is used for verifying version information corresponding to the image file according to the version information of the firmware which does not need to be upgraded;
And the firmware upgrading module is used for checking if the version information corresponding to the image file is compatible with the version information of the firmware which does not need to be upgraded, storing the version information corresponding to the image file into an address space corresponding to the storage equipment configuration file, and writing the image file into the address space corresponding to the storage equipment in a refreshing way so as to finish upgrading.
13. A heterogeneous cross-domain controller upgrade apparatus, comprising:
one or more processing devices;
a memory for storing one or more programs; when the one or more programs are executed by the one or more processing devices, the one or more processing devices are caused to implement the heterogeneous cross-domain controller upgrade method of any of claims 1-11.
14. A computer-readable storage medium having stored thereon a computer program for causing a computer to perform the heterogeneous cross-domain controller upgrade method of any of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310928123.0A CN117075922A (en) | 2023-07-26 | 2023-07-26 | Heterogeneous cross-domain controller upgrading method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310928123.0A CN117075922A (en) | 2023-07-26 | 2023-07-26 | Heterogeneous cross-domain controller upgrading method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117075922A true CN117075922A (en) | 2023-11-17 |
Family
ID=88708866
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310928123.0A Pending CN117075922A (en) | 2023-07-26 | 2023-07-26 | Heterogeneous cross-domain controller upgrading method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117075922A (en) |
-
2023
- 2023-07-26 CN CN202310928123.0A patent/CN117075922A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106293507B (en) | Electronic device with external memory and method of operating the same | |
| US10447814B2 (en) | Joint servicing of software packages | |
| CN103577201B (en) | The update method and system of Embedded Double system | |
| CN104185836A (en) | Method and system for verifying proper operation of computing device after system change | |
| CN113220332B (en) | BIOS firmware refreshing test method and device, electronic equipment and storage medium | |
| WO2022213641A1 (en) | Method and apparatus for process succession, electronic device and storage medium | |
| CN109828774B (en) | Server system and starting method thereof | |
| CN111506331A (en) | Server BMC refreshing method, system, terminal and storage medium | |
| CN117215656A (en) | Linux system-based self-adaptive vehicle chip method and device, electronic equipment and vehicle | |
| CN117075922A (en) | Heterogeneous cross-domain controller upgrading method, device, equipment and medium | |
| CN116610336A (en) | Firmware upgrading method, system, device and readable storage medium | |
| CN110134456A (en) | For managing the method, apparatus, equipment and storage medium of operating system | |
| CN113254158B (en) | Deployment method and device of deep learning system | |
| CN115033261A (en) | Program updating method, device, equipment and storage medium | |
| CN115357355A (en) | Method, device and equipment for software cross-system migration and readable storage medium | |
| CN114296764A (en) | System upgrading method and device, storage medium and electronic equipment | |
| CN114090054A (en) | Intelligent equipment upgrading method and device, storage medium and electronic equipment | |
| CN114995847A (en) | Hot update method, device, equipment and computer readable storage medium | |
| CN112817622A (en) | BIOS refreshing method and device, electronic equipment and storage medium | |
| CN114047715A (en) | Control method of peripheral device during software update of ECU application layer and storage medium | |
| CN113268266B (en) | Multi-version coexistence management method, system and medium for applet rendering framework | |
| CN114153388B (en) | Hard disk system, hard disk configuration information refreshing method, device and medium | |
| CN113890825B (en) | Interactive upgrade test method and device of equipment, storage medium and electronic equipment | |
| CN117827547B (en) | Method and system for recovering touch abnormality of vehicle-mounted display screen, electronic equipment and medium | |
| CN111949278B (en) | Method, system, terminal and storage medium for automatically installing MCS system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |