CN116560688A - Software updating method for domain controller - Google Patents
Software updating method for domain controller Download PDFInfo
- Publication number
- CN116560688A CN116560688A CN202310496026.9A CN202310496026A CN116560688A CN 116560688 A CN116560688 A CN 116560688A CN 202310496026 A CN202310496026 A CN 202310496026A CN 116560688 A CN116560688 A CN 116560688A
- Authority
- CN
- China
- Prior art keywords
- software
- domain controller
- configuration file
- updating method
- stage
- 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 36
- 238000011161 development Methods 0.000 claims abstract description 43
- 230000004044 response Effects 0.000 claims abstract description 13
- 238000012360 testing method Methods 0.000 claims description 37
- 238000004891 communication Methods 0.000 claims description 14
- 238000004519 manufacturing process Methods 0.000 claims description 11
- 230000001680 brushing effect Effects 0.000 claims 1
- 230000007246 mechanism Effects 0.000 abstract description 13
- 238000005516 engineering process Methods 0.000 description 4
- 230000015654 memory Effects 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000004927 fusion Effects 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 1
- 238000004377 microelectronic Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000016776 visual perception Effects 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/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
Abstract
The application relates to a software updating method for a domain controller, wherein the software of the domain controller comprises micro control unit side software and system level chip side software, and the software updating method comprises the following steps: in response to the requirement of independently upgrading the software of the micro control unit side, the programmer is utilized to realize the upgrading of the software of the micro control unit side through software programming; and in response to the need to upgrade the system-on-chip side software and the micro control unit side software as a whole or in response to the need to upgrade the system-on-chip side software alone, determining a development stage in which the domain controller is located, and selecting a manner of reading a configuration file for the domain controller based on the development stage in which the domain controller is located, so that the domain controller can perform a flush with the read configuration file to realize the upgrade of the corresponding software. The software updating method can provide software upgrading and debugging mechanisms for domain controllers in different development stages.
Description
Technical Field
The present application relates to the field of vehicles, and in particular to a software update method for a domain controller.
Background
With the addition of new technologies such as intelligence and networking and the like to the development of the whole vehicle, the electronic architecture of the whole vehicle gradually changes from decentralization to centralization, and various module controllers such as an engine controller, a gearbox controller, a battery controller, a whole vehicle controller, an entertainment system controller, a central controller and the like on the vehicle are integrated along with the development of the whole vehicle, the intelligent and networking and other new technologies are gradually designed into different domain controllers such as a power domain controller, a cabin domain controller, an ADAS (advanced driver assistance system) domain controller and the like according to different regions on the whole vehicle, the hardware and software complexity of the controllers are increased along with the development of the intelligent and networking technologies, the main chip of the intelligent and networking technology is upgraded from a previous Micro Control Unit (MCU) to a system-level chip (SoC), and the fusion of the MCU and the SoC has higher requirements on the software upgrading and debugging of the controllers, and particularly, the requirements on the wire harness interfaces and hardware of the embedded domain controllers are different in different stages of the development period of the whole vehicle.
Disclosure of Invention
Embodiments of the present application provide a software update method for domain controllers for providing software upgrade and debug mechanisms for domain controllers at different development stages.
According to an aspect of the present application, there is provided a software update method for a domain controller, the software of the domain controller including Micro Control Unit (MCU) side software and system on chip (SoC) side software, the software update method including: in response to the requirement of independently upgrading the software of the micro control unit side, the programmer is utilized to realize the upgrading of the software of the micro control unit side through software programming; and in response to the need to upgrade the system-on-chip side software and the micro control unit side software as a whole or in response to the need to upgrade the system-on-chip side software alone, determining a development stage in which the domain controller is located, and selecting a manner of reading a configuration file for the domain controller based on the development stage in which the domain controller is located, so that the domain controller can perform a flush with the read configuration file to realize the upgrade of the corresponding software.
In some embodiments of the present application, optionally, the development stage includes: bench test stage, real vehicle test stage and mass production stage.
In some embodiments of the present application, optionally, the manner of reading the configuration file includes: reading a configuration file in a flash memory (SD or TF) card, reading a configuration file in a storage device via a Universal Serial Bus (USB) interface, and reading a remotely downloaded configuration file via a gateway.
In some embodiments of the present application, optionally, the selecting, based on a development stage in which the domain controller is located, a manner of reading a configuration file for the domain controller includes: and when the domain controller is in the bench test stage, reading the configuration file in the flash memory card.
In some embodiments of the present application, optionally, the selecting, based on a development stage in which the domain controller is located, a manner of reading a configuration file for the domain controller includes: and when the domain controller is in a real vehicle testing stage, reading a configuration file in the storage device through a universal serial bus interface.
In some embodiments of the present application, optionally, the selecting, based on a development stage in which the domain controller is located, a manner of reading a configuration file for the domain controller includes: and when the domain controller is in the mass production stage, reading the remotely downloaded configuration file through a gateway.
In some embodiments of the present application, optionally, the software updating method further includes: in response to a need to debug the micro control unit side software, the debugging of the micro control unit side software is accomplished via Controller Area Network (CAN) communications.
In some embodiments of the present application, optionally, the software updating method further includes: and responding to the requirement of debugging the system-level chip side software, determining the development stage of the domain controller, and selecting a software debugging mode for the domain controller based on the development stage of the domain controller so as to realize the debugging of the system-level chip side software.
In some embodiments of the present application, optionally, the selecting a manner of software debug for the domain controller based on a development stage in which the domain controller is located includes: debugging the system on chip side software via Universal Asynchronous Receiver Transmitter (UART) communication when the domain controller is in a bench test phase; and debugging the system-on-chip side software through a human-machine interface (HMI) when the domain controller is in a real-vehicle testing phase.
According to another aspect of the present application, there is provided a computer readable storage medium having instructions stored therein, which when executed by a processor, cause the processor to perform any one of the software updating methods as described above.
The serial-parallel software updating mechanism can be suitable for different stages of full life cycle development of the domain controller, and different mechanisms are selected according to different stages, so that great convenience is brought to software updating.
Drawings
The foregoing and other objects and advantages of the application will be apparent from the following detailed description taken in conjunction with the accompanying drawings in which like or similar elements are designated by the same reference numerals.
FIG. 1 illustrates a domain controller update system according to one embodiment of the present application;
FIG. 2 illustrates software upgrade steps for a domain controller according to one embodiment of the present application;
FIG. 3 illustrates software debugging steps for a domain controller according to one embodiment of the present application.
Detailed Description
For the purposes of brevity and explanation, the principles of the present application are described herein primarily with reference to exemplary embodiments thereof. However, those skilled in the art will readily recognize that the same principles are equally applicable to all types of software update methods for domain controllers, and that these same or similar principles may be implemented therein, any such variations without departing from the true spirit and scope of the present application.
The domain controller updating system 100 of one embodiment of the present application will be described below in conjunction with fig. 1.
Fig. 1 illustrates a domain controller update system 100 according to one embodiment of the present application. As shown in fig. 1, the domain controller update system 100 includes a domain controller 110, wherein the domain controller 110 may be an embedded domain controller. In some embodiments, the domain controller 110 may be applied in a vehicle, for example, may be extended to advanced driving assistance and unmanned fields. The hardware architecture of the domain controller 110 may include an MCU domain 111 and an SoC domain 112. The software architecture of the domain controller 110 may include MCU side software corresponding to the MCU domain 111 and SoC side software corresponding to the SoC domain 112. Fig. 1 shows an example of a hardware architecture of a domain controller 110 including one MCU domain 111 and one SoC domain 112, and in other embodiments, the domain controller 110 may include other hardware architectures in combination.
In some embodiments, the present application may configure flash card interface 120, universal Serial Bus (USB) interface 122, joint test workgroup (JTAG) interface 124, and gateway 128 for domain controller 110 for implementing the software upgrade functions of domain controller 110.
As shown in fig. 1, a flash card interface 120 may be used to connect a flash card 121, so that the domain controller 110 may read a configuration file stored in the flash card 121 through the flash card interface 120 for performing a software upgrade. In some embodiments, the flash memory card may be a SD (Secure Digital) card or TF (Trans Flash) card. The USB interface 122 may be used to connect the storage device 123 so that the domain controller 110 may read the configuration file stored in the storage device 123 through the USB interface 122 for performing a software upgrade. In some embodiments, the storage device may be a USB flash disk. JTAG interface 124 may be used to connect to programmer 125 such that domain controller 110 may load programming software 126 through programmer 125 to implement software programming through programming software 126. The gateway 128 may be communicatively coupled to the domain controller 110 through the port physical layer 127 so that the domain controller 110 may read the configuration file of the remote download 129 via the gateway 128. In some embodiments, gateway 128 may be an ethernet gateway.
In some embodiments, the present application may configure a Controller Area Network (CAN) transceiver 130, a Low Voltage Differential Signaling (LVDS) interface 133, and a Universal Asynchronous Receiver Transmitter (UART) interface 135 for the domain controller 110 for implementing software debug functions of the domain controller 110.
As shown in fig. 1, the CAN transceiver 130 may be used to connect with the CAN debugger 131, so that the domain controller 110 may load the CAN debug software 132 through the CAN debugger 131 to implement software debugging through the CAN debug software 132. The LVDS interface 133 may be used to connect a human-machine interface (HMI) display 134 so that the domain controller 110 may debug software through the HMI display 134. UART interface 135 may be used to interface with serial port debug tool 136 so that domain controller 110 may debug software through serial port debug tool 136.
In some embodiments, the present application may configure one or more memories for domain controller 110 for storing logs (logs) during debugging software for domain controller 110. Fig. 1 shows an example of a domain controller 110 configured with three memories, flash 137, eMMC (Embedded Multi Media Card), 138 and LPDDR4 (Low Power Double Data Rate) 139, respectively.
In some embodiments, the domain controller update system 100 shown in fig. 1 may adapt the software upgrade and debug mechanisms of the domain controller 110 (e.g., embedded domain controller) over a full lifecycle. In some embodiments, the full life development cycle of domain controller 110 may include: bench test stage, real vehicle test stage and mass production stage.
Next, a software update method for the domain controller 110 according to an embodiment of the present application will be described with reference to fig. 2 and 3. In some embodiments, the software update method for the domain controller 110 may include a software upgrade step 200. In other embodiments, the software update method for the domain controller 110 may further include a software debug step 300.
Fig. 2 illustrates a software upgrade step 200 for the domain controller 110 according to one embodiment of the present application. The software upgrading step 200 of the embodiment of the present application may perform a corresponding software upgrading step in response to a need to individually upgrade the MCU side software, a need to individually upgrade the SoC side software, and a need to integrally upgrade the SoC side software and the MCU side software. In some embodiments, the user may choose to update the SOC-side software or the MCU-side software according to his own needs. As shown in fig. 2, the software upgrade step 200 may include steps S210 to S270.
In step S210, in the case where the domain controller 110 currently has a need for software upgrade, it is determined whether the domain controller 110 needs to individually upgrade the MCU-side software. In some embodiments, if so, step S260 may be further performed; if not, indicating that the domain controller 110 currently has a need to individually upgrade the SoC-side software or a need to upgrade the SoC-side software and the MCU-side software as a whole, step S220 may be further performed.
In step S260, an Integrated Development Environment (IDE) opens a software burn. In some embodiments, the programmer 125 may be connected to the JTAG interface 124, and the software package is loaded by the upper computer programming software to implement MCU side software programming. For example, the MCU programming package may be loaded in the upper computer IDE software, the programmer 125 is connected to the domain controller 110 in hardware, and programming is started in the IDE software, waiting for the programming to be completed. For ease of description, the manner in which software is upgraded by programming the software via JTAG interface 124 is referred to herein as "JTAG upgrade". After step S260, step S270 may be further performed.
In step S220, the development stage of the domain controller 110 is determined. In the embodiment of the present application, with respect to the current requirement that the domain controller 110 separately upgrades the SoC side software or the requirement that the SoC side software and the MCU side software are integrally upgraded, the development stage in which the domain controller 110 is located may be further determined, so that the corresponding software upgrade step may be performed based on the development stage in which the domain controller 110 is located. In some embodiments, the development stage in which domain controller 110 is in response to the need for software upgrades includes: bench test stage, real vehicle test stage and mass production stage. Step S230 may be further performed for the domain controller 110 in the bench test phase. Step S240 may be further performed for the domain controller 110 in the real vehicle test phase. Step S250 may be further performed for the domain controller 110 to be in the mass production stage.
In step S230, the configuration file in the flash card 121 is read and the swiping is started based on the read configuration file to enable an associated software upgrade by the swiping. For the flash memory card 121 to be an example of an SD/TF card, software to be upgraded (e.g., software for SoC side and MCU side) may be packaged into the SD/TF card, and then the SD/TF card is inserted into the flash memory card interface 120 of the domain controller 110, so that the domain controller 110 may automatically upgrade the associated software by reading the software version and the swipe address in the configuration file from the SD/TF card. For convenience of description, the manner in which software is upgraded via the SD/TF card reading of the configuration file is referred to herein as "SD/TF upgrade". After step S230, step S270 may be further performed.
In step S240, the configuration file in the storage device 123 is read via the USB interface 122 and the overwriting starts based on the read configuration file to realize the associated software upgrade by the overwriting. For the example that the storage device 123 is a USB disk, software to be upgraded on the SoC side and the MCU side may be packaged into the USB disk, and then the USB disk may be inserted into the USB interface 122 of the domain controller 110, so that the domain controller 110 may automatically upgrade the associated software by reading the software version and the address of the flash from the USB disk. For convenience of description, the manner in which the configuration file is read via USB interface 122 to upgrade the software is referred to herein as "USB upgrade". After step S240, step S270 may be further performed.
In step S250, the remotely downloaded configuration file is read via gateway 128 and a swipe is started based on the read configuration file to enable an associated software upgrade by the swipe. For an example where gateway 128 is an ethernet gateway, step S250 may include: the software package is downloaded remotely from the server side to the local environment via gateway 128 and then upgraded via ethernet communications. For ease of description, the manner in which the software is upgraded by reading the configuration file via gateway 128 is referred to herein as "Over The Air (OTA) upgrade. After step S250, step S270 may be further performed.
In step S270, after the software upgrade is completed, the domain controller 110 may be restarted. For example, the domain controller 110 may be restarted by a boot board. In some embodiments, the software debug step 300 may be further performed after the domain controller 110 is restarted. That is, after the domain controller 110 can enter the debug phase after the software upgrade is completed.
The inventor of the application finds that the software update based on CAN/CANFD has certain requirements on the size of an upgrade package, and the upgrade speed is low, so that the software update method is suitable for carrying out software update on an MCU controller and cannot meet the software update requirement of an SOC controller; the updating and upgrading speed of the software based on the Ethernet is higher, but the software is not updated based on the SD card communication protocol, and the different domain partition software (comprising SOC side software and MCU side software) of the domain controller cannot be selectively and independently upgraded; in addition, the remote software update based on the OTA can realize the function upgrade after mass production, however, the software implementation complexity is higher, and a certain security risk exists.
Based on the limitations of the above software updating method, the inventor of the present application recognizes that the method of performing software updating on the MCU controller is often not applicable to the SoC domain controller, because the size of the software package programmed in the MCU controller is in Kbytes level, and some of the software package reaches Mbytes level, but the size of the operating system and the software system package running in the SoC domain controller is in GBytes level, and the software updating cannot be performed by using the programmer; the software running on the SoC in the embedded domain controller is complex, and comprises an embedded system, kernel software, each kernel firmware, an application layer software algorithm and the like, so that the programming speed of the software in the SoC chip is slow; the software programming mode of the embedded domain controller is single, the embedded domain controller cannot adapt to different periods of whole vehicle project development, particularly, all controllers are arranged and assembled according to the whole vehicle structure in the later test and acceptance stage of the project, and the software programming is inconvenient; particularly, after the automobile is marketed, some controllers cannot support remote online upgrade based on OTA, and cannot bring extremely good performance experience to clients; in addition, in different stages such as bench test and real vehicle test, the mode of debugging the software running on the SoC chip and the MCU chip in the embedded domain controller is single, inconvenience is brought to the test, different project development stages cannot be adapted, for example, the debugging of visual perception algorithm in the SOC cannot be related only by diagnosis and debugging based on CAN.
The application provides a serial-parallel software update mechanism. The software updating method provided by the application can be suitable for different stages of full life cycle development of the embedded domain controller, and different software updating mechanisms are selected according to different stages based on the characteristics of software updating. In some embodiments, the serial-parallel software upgrading mechanism based on communication protocols such as SD card and USB, JTAG, OTA achieves the purpose of correspondingly selecting proper software updating and debugging mechanisms according to different stages of whole vehicle project development, and the software updating modes are combined in parallel and in series along with time nodes to meet the software development requirements of a controller, and software of different chip modules can be selectively upgraded independently. For example, in the bench test stage, for the domain controller 110, an SD card upgrade may be selected; in the real vehicle test stage, a USB flash disk upgrading stage can be selected; in the mass production stage, OTA upgrading can be selected, so that great convenience is brought to software upgrading.
Fig. 3 illustrates a software debugging step 300 for the domain controller 110 according to one embodiment of the present application. The software debugging step 300 of the embodiment of the present application may be performed in response to a requirement for debugging the MCU side software and a requirement for debugging the SoC side software. As shown in fig. 3, the software debugging step 300 may include steps S310 to S360.
In step S310, in the case where there is a need for software debugging of the domain controller 110 at present, it is determined whether the domain controller 110 is to debug the MCU-side software. In some embodiments, if so, step S350 may be further performed; if not, indicating that the domain controller 110 currently has a need to debug SoC-side software, step S320 may be further performed.
In step S350, the MCU-side software is debugged via the communication of the CAN transceiver 130. In some embodiments, on one hand, the variable running in the software may be packaged by the CAN communication and the packaged data may be sent to the CAN bus, on the other hand, the CAN debugger 131 may be connected to the domain controller 110, to implement CAN communication between the PC and the domain controller 110, and then, the CAN message receiving and the variable parsing may be performed in the upper computer CAN debug software, so as to implement the debugging of the MCU side software. For convenience of description, the manner in which software is debugged via communication of the CAN transceiver 130 is referred to herein as "CAN debugging". After step S350, step S360 may be further performed.
In step S320, it is determined whether the domain controller 110 is in the stage of bench test. In the embodiment of the present application, in response to the requirement of debugging the SoC-side software, the development stage in which the domain controller 110 is located may be further determined, so that the corresponding software debugging step can be performed based on the development stage in which the domain controller 110 is located. In some embodiments, the development stage in which domain controller 110 is located may include: a bench test stage and a real vehicle test stage. If it is determined that the stage is currently in the bench test stage based on step S320, step S330 may be further performed. If it is determined that the stage is not currently in the bench test stage based on step S320, it means that the stage is currently in the real vehicle test stage, and step S340 may be further performed.
In step S330, the SoC side software is debugged via the communication of the UART interface 135. In some embodiments, serial port debugging tool 136 may be connected to UART interface 135 to enable UART communication between a computer (PC) and domain controller 110, and then software is debugged in host serial port software. For convenience of description, the manner in which software is debugged via communication of UART interface 135 is referred to herein as "serial port debugging". After step S330, step S360 may be further performed.
In step S340, the SoC-side software is debugged through the human-machine interface (HMI) display 134. In some embodiments, the debugging of domain controller 110 may be accomplished by selecting a debug mode on the HMI interface to send different debug instructions to domain controller 110 via messaging between the HMI interface and the controller. For example, the debug mode may be initiated through an HMI interface where the results of software execution during the debug may be displayed in real-time on the HMI interface. For convenience of description, the manner in which software is debugged via HMI display 134 is referred to herein as "HMI debugging". After step S340, step S360 may be further performed.
In step S360, log (log) information is saved or recorded. In some embodiments, the next stage of software upgrade step 200 and/or software debug step 300 may be further performed based on saved or recorded log (log) information in order to further optimize the software. Fig. 3 shows an example in which step S360 of saving or recording log is performed after the step of corresponding debugging software, however in other examples, step S360 of saving or recording log may be performed at the same time as the step of corresponding debugging software is performed. For example, during serial port debugging, log information may be printed; log information CAN be saved during CAN commissioning; and log information can be printed in real-time onto the HMI during HMI commissioning. In some embodiments, log information may be saved to an SD/TF card or U disk. In some embodiments, after waiting for the log recording to end, the software update and software debug may be optimized based on the log information, and then further performed.
The software updating (including software updating and software debugging) mechanism provided by the application can be adapted to the hardware architecture of different domain controllers 110 and different SoC chip architectures, such as a single MCU controller scheme, a single SoC controller scheme, and a fusion scheme of the SoC controller and the MCU controller, and the corresponding software updating and debugging mechanism is selected according to different domain controller schemes, so that the coverage and the adaptability are good. In addition, the software updating mechanism provided by the application can independently and selectively update SoC side software or MCU side software according to different debugging purposes of users, the whole software package is not required to be updated every time, and the software upgrading time is greatly saved. In addition, the software debugging mechanism provided by the application CAN adapt to corresponding software update, for example, updated MCU software CAN be debugged in a CAN mode, and updated SOC software CAN be debugged in an HMI (human machine interface) and serial port mode. In addition, in different development stages of the domain controller 110, different hardware modules, such as Integrated Circuit (IC) chips and microelectronic components used in other upgrading modes can be selected, so that hardware cost is saved, configurability is strong, and flexibility and simplicity are realized.
According to another aspect of the present application, there is provided a computer readable storage medium having stored therein instructions which, when executed by a processor, cause the processor to perform any of the software update methods for a domain controller as described above. Computer-readable media, as referred to in this application, include any type of computer storage media which can be accessed by a general purpose or special purpose computer. For example, the computer-readable medium may include RAM, ROM, EPROM, E 2 PROM, registers, hard disk, a removable disk, a CD-ROM or other optical disk, a magnetic disk memory or other magnetic storage device, or any other temporary or non-temporary medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Disk, as used herein, typically replicates data magnetically, while disk replicates data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
The present application realizes multiple software upgrading serial-parallel schemes in the domain controller 110 to cope with software updating tasks of different development stages without increasing hardware cost, and can automatically select an upgrading mode and upgrade software, wherein the serial software upgrading mode is implemented in a bench test stage, a real vehicle test stage and a mass production stage, the whole software package can be upgraded, and the parallel software upgrading mode is selected in a continuous development period of the bench stage and the real vehicle stage, so that different software modules can be upgraded.
In some embodiments, the application can implement the software upgrade to the domain controller 110 in parallel by adopting SD/TF upgrade and JTAG upgrade in the project initial stage bench test stage, namely, the whole SOC and MCU side software can be refreshed by adopting SD/TF upgrade, and the MCU software can be upgraded independently by JTAG upgrade, so that the method is simple and quick. In addition, in the stage of bench test, the SOC software CAN be debugged through serial port debugging, log is printed and stored in the SD/TF card in real time, the MCU software is debugged through CAN debugging, and the variable value running in the software is monitored in real time and log is stored. In the mid-project real vehicle test (or real vehicle verification) stage, the application can realize the software upgrade of the domain controller 110 by adopting the parallel of USB upgrade and JTAG upgrade, namely, the whole SOC and MCU side software can be refreshed by adopting the USB upgrade, and the MCU software can be upgraded independently by adopting the JTAG upgrade. In addition, in the actual vehicle testing stage, software CAN be debugged through an actual vehicle HMI interface, log is displayed on a central control screen in real time, MCU software is debugged in a CAN mode, and variable values running in the software are monitored in real time and log is saved. In the later mass production stage of the project, the method can remotely upgrade the software on line in an OTA mode.
The foregoing is merely a specific embodiment of the present application, and the scope of the present application is not limited thereto. Other possible variations or substitutions will occur to those skilled in the art from the teachings disclosed herein and are intended to be within the scope of the present application. In the case of no conflict, the embodiments of the present application and the features of the embodiments may also be combined with each other. The claims of the protection scope of the present application control.
Claims (10)
1. A software updating method for a domain controller, wherein the software of the domain controller includes a micro control unit side software and a system on chip side software, the software updating method comprising:
in response to the requirement of independently upgrading the software of the micro control unit side, the programmer is utilized to realize the upgrading of the software of the micro control unit side through software programming; and
and determining a development stage of the domain controller in response to the requirement of integrally upgrading the system-level chip-side software and the micro control unit-side software or to the requirement of independently upgrading the system-level chip-side software, and selecting a mode of reading the configuration file for the domain controller based on the development stage of the domain controller so that the domain controller can utilize the read configuration file to perform brushing to realize upgrading of corresponding software.
2. The software updating method according to claim 1, wherein the development stage comprises: bench test stage, real vehicle test stage and mass production stage.
3. The software updating method according to claim 2, wherein the manner of reading the configuration file includes: reading a configuration file in the flash memory card, reading a configuration file in the storage device via the universal serial bus interface, and reading a remotely downloaded configuration file via the gateway.
4. A software updating method according to claim 3, wherein the selecting a manner of reading a configuration file for the domain controller based on a development stage in which the domain controller is located comprises:
and when the domain controller is in the bench test stage, reading the configuration file in the flash memory card.
5. The software updating method according to claim 4, wherein the selecting a manner of reading a configuration file for the domain controller based on a development stage in which the domain controller is located comprises:
and when the domain controller is in a real vehicle testing stage, reading a configuration file in the storage device through a universal serial bus interface.
6. The software updating method according to claim 5, wherein the selecting a manner of reading a configuration file for the domain controller based on a development stage in which the domain controller is located comprises:
and when the domain controller is in the mass production stage, reading the remotely downloaded configuration file through a gateway.
7. The software updating method according to claim 1, characterized in that the software updating method further comprises:
and responding to the requirement of debugging the micro control unit side software, and realizing the debugging of the micro control unit side software through the communication of a controller local area network.
8. The software updating method according to claim 7, characterized in that the software updating method further comprises:
and responding to the requirement of debugging the system-level chip side software, determining the development stage of the domain controller, and selecting a software debugging mode for the domain controller based on the development stage of the domain controller so as to realize the debugging of the system-level chip side software.
9. The software updating method according to claim 8, wherein the selecting a software debug mode for the domain controller based on a development stage in which the domain controller is located comprises:
debugging the system-on-chip side software via universal asynchronous receiver transmitter communication when the domain controller is in a bench test phase; and
and when the domain controller is in a real vehicle testing stage, debugging the system-level chip-side software through a human-computer interface.
10. A computer readable storage medium having instructions stored therein, which when executed by a processor, cause the processor to perform the software update method of any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310496026.9A CN116560688A (en) | 2023-05-05 | 2023-05-05 | Software updating method for domain controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310496026.9A CN116560688A (en) | 2023-05-05 | 2023-05-05 | Software updating method for domain controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116560688A true CN116560688A (en) | 2023-08-08 |
Family
ID=87489238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310496026.9A Pending CN116560688A (en) | 2023-05-05 | 2023-05-05 | Software updating method for domain controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116560688A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215603A (en) * | 2023-11-08 | 2023-12-12 | 宁德时代新能源科技股份有限公司 | Software flashing method and device of domain controller, computer equipment and storage medium |
-
2023
- 2023-05-05 CN CN202310496026.9A patent/CN116560688A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215603A (en) * | 2023-11-08 | 2023-12-12 | 宁德时代新能源科技股份有限公司 | Software flashing method and device of domain controller, computer equipment and storage medium |
| CN117215603B (en) * | 2023-11-08 | 2024-04-02 | 宁德时代新能源科技股份有限公司 | Software flashing method and device of domain controller, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3352080B1 (en) | Gateway device, firmware update method, and control program | |
| US7099750B2 (en) | Data access method and data access apparatus for accessing data at on-vehicle information device | |
| CN109783340B (en) | SoC test code programming method, IP test method and device | |
| CN109933348A (en) | The update method and device of Bootloader in a kind of electronic control unit | |
| CN107479913A (en) | A kind of FPGA configurations low-resources that start take update method and implement system more | |
| CN106547574A (en) | The outside download system and method for a kind of DSP programs and FPGA programs | |
| CN111158718A (en) | Local communication server, OTA (over the air) upgrading method thereof and cloud server | |
| CN115658160B (en) | Multi-operating system upgrading method, device and system based on multi-core heterogeneous SOC | |
| CN109086058A (en) | Onboard program upgrade-system | |
| CN110851163B (en) | Software updating method compatible with multi-equipment platform based on CAN communication | |
| CN105718281A (en) | Touch screen firmware upgrading method and device | |
| CN116560688A (en) | Software updating method for domain controller | |
| US20060156302A1 (en) | Control program download device | |
| CN116737244A (en) | Method and device for starting multiple hardware domains of chip | |
| CN113377384A (en) | Program burning method and device, vehicle-mounted terminal and medium | |
| CN102495746A (en) | Onboard embedded computer data loading method | |
| CN101667133B (en) | Method for updating firmware and chip updating firmware by using same | |
| CN110941444A (en) | Upgrade configuration logic circuit, method and system and programmable logic device | |
| US11449329B2 (en) | Vehicle control device and program update system | |
| CN108694052B (en) | Firmware upgrading method, firmware upgrading device and firmware upgrading system | |
| CN112925569A (en) | Firmware data processing method, device, equipment and storage medium | |
| CN116700765A (en) | Firmware upgrading method and device of servo driver and servo driver | |
| CN107908418B (en) | Method for upgrading logic program of fiber channel node card and fiber channel bus equipment | |
| CN111045740A (en) | MCU software parameter calibration method and system based on USBCAN | |
| CN112395224A (en) | Data processing method and system, concatenation device and electronic equipment |
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 |