Vehicle system firmware upgrading method and apparatus, electronic device and storage medium

Abstract

The present application discloses a vehicle system firmware upgrading method, a vehicle system firmware upgrading system, a vehicle system firmware upgrading apparatus, an electronic device and a storage medium. The method comprises: a system master is connected to a communication slave; the communication slave acquires firmware identity information of the system master; the communication slave is connected to an external communication link; the communication slave filters communication information on the external communication link on the basis of the firmware identity information of the system master, and determines whether a file name used for updating firmware of the system master exists; and if the file name used for updating the firmware of the system master is filtered, the master-slave modes of the system master and the communication slave are converted. According to the described solution, a subsystem communicating with the outside is provided to acquire a firmware updating file of a subsystem connected to the subsystem, thereby allowing for online firmware updates for the subsystems without independently disassembling the firmware and then updating the firmware one by one.

Description

Vehicle system firmware upgrade method, device, electronic device and storage medium Technical Field

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

[0002] Smart electric vehicles are developing rapidly, involving multiple hardware subsystems in a single vehicle. However, not all hardware subsystems have external communication channels. If you want to upgrade the firmware, you need to disassemble them separately. For example, the screen, as a carrier of human-computer interaction, carries more functions. The reliability and stability of the screen itself not only affect the display effect, but also the safe driving of the car. Therefore, when there is a problem with the screen firmware, it is necessary to update the screen firmware in a timely manner to ensure normal functions and safe driving of the car; but it is necessary to use a specific hardware upgrade tool (provided by the screen manufacturer) to upgrade the firmware; the screen will affect normal display during the upgrade process; the screen can only be upgraded offline with the help of an external storage device (such as a USB flash drive, etc.); during the screen upgrade, because it cannot display normally, it can only be upgraded when the vehicle is not in motion.

[0003] Therefore, a solution for vehicle system firmware upgrade is needed, which enables each independent vehicle subsystem to automatically complete the firmware update without having to be disassembled separately.

[0004] Summary of the Invention

[0005] The object of the present invention is to provide a vehicle system firmware upgrade method, a vehicle system firmware upgrade system, a vehicle system firmware upgrade device, an electronic device and a storage medium, so as to solve at least one of the above-mentioned technical problems.

[0006] The present invention provides the following solutions:

[0007] According to one aspect of the present invention, a vehicle system firmware upgrade method is provided, the vehicle system firmware upgrade method comprising:

[0008] The system host connects to the communication slave;

[0009] The communication slave obtains the firmware identity information of the system host;

[0010] The communication slave is connected to an external communication link;

[0011] The communication slave filters the communication information on the external communication link according to the firmware identity information of the system host, and determines whether there is a file name for updating the firmware of the system host;

[0012] If a file name for updating the system host firmware is found through filtering, the system host and the communication slave switch to a master-slave mode.

[0013] Furthermore, it also includes:

[0014] Obtain a download link based on the file name for the system host firmware update filtered by the communication slave;

[0015] According to obtaining the download link, the communication slave obtains the firmware update file for the system master.

[0016] Furthermore, it also includes:

[0017] Obtaining a firmware update file for the system host according to the communication slave, sending a request to update the system host firmware, and waiting for feedback from the system host;

[0018] If, within a first preset time threshold, the communication slave obtains feedback from the system master that the system master firmware is allowed to be updated, then according to the feedback sent by the system master, the system master switches to a slave working mode, and according to the feedback received by the communication slave, the communication slave switches to a master working mode;

[0019] The feedback includes instruction information for switching between the master and slave machines.

[0020] Furthermore, it also includes:

[0021] According to the switching of the communication slave to the master working mode, the communication slave queries the current firmware running area of ​​the system master;

[0022] According to the current firmware running area of ​​the system host, the communication slave sends a request to receive a firmware update file and waits for feedback;

[0023] The system host self-detects whether the firmware storage space can receive the firmware update file upon receiving the request to receive the firmware update file;

[0024] If the detection result is no, the system host sends a feedback message of refusing to receive the firmware update file.

[0025] Furthermore, the self-detection of whether the firmware storage space can receive the firmware update file further includes:

[0026] If the detection result is yes, the system host sends feedback information allowing reception of the firmware update file;

[0027] According to the feedback information of sending the permission to receive the firmware update file, the system host verifies the received firmware update file package, including the sub-packages split from the firmware update file package;

[0028] According to the failure of verification of the firmware update file package and any sub-package of the firmware update file package, the system host re-receives the firmware update file package and records the number of times the firmware update file package is re-received;

[0029] Determining whether the number of times the system host re-receives the firmware update file package exceeds a preset update number threshold;

[0030] If the number of updates exceeds a preset threshold, the system host stops receiving the firmware update file package and sends a feedback message of refusing to receive the firmware update file;

[0031] The communication slave stops sending the request for receiving the firmware update file according to the feedback information of refusing to receive the firmware update file.

[0032] Furthermore, the determining whether the number of times the system host re-receives the firmware update file package exceeds a preset update number threshold further includes:

[0033] If the preset update number threshold is not exceeded and the system host has completed receiving the firmware update file package, the system host sends feedback information indicating that the firmware update file has been received;

[0034] The communication slave receives feedback information indicating that the firmware update file has been completed, and stops sending requests for receiving the firmware update file;

[0035] The communication slave switches to a slave working mode according to the request to stop sending and receiving the firmware update file;

[0036] The system host switches to the host working mode according to the feedback information of completing sending and receiving the firmware update file or sending the feedback information of refusing to receive the firmware update file.

[0037] According to two aspects of the present invention, there is provided a vehicle system firmware upgrade system, the vehicle system firmware upgrade system comprising: a screen display system and a CSC host system;

[0038] The screen display system is used for the system host;

[0039] The CSC host system is used to communicate with the slave;

[0040] The CSC host system is connected to the cloud or storage to obtain the firmware update file of the screen display system;

[0041] The CSC host system is connected to the screen display system, and sends a request to update the screen display system firmware according to the firmware update file of the screen display system;

[0042] The screen display system obtains a firmware update file of the screen display system according to the CSC host system, and feeds back feedback information allowing the screen display system to receive the firmware update file;

[0043] According to the feedback information allowing the screen display system to receive the firmware update file, the screen display system switches to the slave mode;

[0044] According to the CSC host system receiving feedback information that allows the screen display system to receive the firmware update file, the CSC host system switches to the host mode;

[0045] The screen display system receives the firmware update file, and displays a graphic or symbol corresponding to the progress or status of receiving the firmware update file on the screen display terminal according to the progress or status of receiving the firmware update file.

[0046] According to three aspects of the present invention, a vehicle system firmware upgrade device is provided, the vehicle system firmware upgrade device comprising:

[0047] System host module, used to connect to communication slaves;

[0048] Communication slave module, used to obtain the firmware identity information of the system host;

[0049] an external communication link module, configured to connect to the communication slave;

[0050] A file filtering module, configured for the communication slave to filter the communication information on the external communication link according to the firmware identity information of the system host, and to determine whether there is a file name for updating the firmware of the system host;

[0051] The mode conversion module is used to convert the master-slave mode of the system host and the communication slave if a file name for updating the system host firmware is filtered out.

[0052] According to four aspects of the present invention, there is provided an electronic device, characterized in that it includes: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0053] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the vehicle system firmware upgrade method.

[0054] According to five aspects of the present invention, a computer-readable storage medium is provided, characterized in that it includes: a computer program that can be executed by an electronic device is stored therein, and when the computer program runs on the electronic device, the electronic device executes the steps of the vehicle system firmware upgrade method.

[0055] Through the above solution, the following beneficial technical effects are achieved:

[0056] This application uses a subsystem that can communicate with the outside to obtain the firmware update file of the subsystem connected to the subsystem, so that each subsystem can update its firmware online without having to disassemble it separately and update the firmware one by one.

[0057] This application converts the master-slave working mode of the subsystem so that the subsystem that communicates with the outside world can use the slave as the master to update the firmware for the slave. After the update is completed, it returns to the original master-slave working mode, so that the subsystems in the master working mode and the slave working mode can complete the firmware update with the assistance of the subsystem that communicates with the outside world.

[0058] This application partially upgrades the firmware of a subsystem and maintains the working status of other subsystems, so that the vehicle can complete the firmware update online without suspending the entire vehicle system, reducing the impact on vehicle operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] FIG1 is a flowchart of a vehicle system firmware upgrade method provided by one or more embodiments of the present invention.

[0060] FIG2 is a structural diagram of a vehicle system firmware upgrade system provided by one or more embodiments of the present invention.

[0061] FIG3 is a structural diagram of a vehicle system firmware upgrading device provided by one or more embodiments of the present invention.

[0062] FIG4 is a schematic diagram of a system for upgrading a screen display system according to a specific embodiment of the present invention.

[0063] FIG5 is a timing diagram of a screen display system upgrade according to a specific embodiment of the present invention.

[0064] FIG6 is a schematic diagram of a flow chart of screen display system upgrade according to a specific embodiment of the present invention.

[0065] FIG7 is a block diagram of an electronic device structure of a vehicle system firmware upgrade method provided by one or more embodiments of the present invention. DETAILED DESCRIPTION

[0066] The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0067] FIG1 is a flowchart of a vehicle system firmware upgrade method provided by one or more embodiments of the present invention.

[0068] The vehicle system firmware upgrade method shown in FIG1 includes:

[0069] Step S1, the system host connects to the communication slave;

[0070] Step S2, the communication slave obtains the firmware identity information of the system master;

[0071] Step S3, the communication slave connects to the external communication link;

[0072] Step S4, the communication slave filters the communication information on the external communication link according to the firmware identity information of the system master, and determines whether there is a file name for updating the system master firmware;

[0073] Step S5, wherein if a file name for updating the system host firmware is filtered out, the system host and the communication slave switch the master-slave mode.

[0074] Specifically, the system host is connected to the communication slave, the system host works in the host mode, and the communication slave works in the slave mode, and the system host and the communication slave are in a master-slave relationship. The communication slave is connected to the external communication link and communicates with external remote devices, such as cloud servers. The communication slave filters the communication information on the external communication link according to the firmware identity information of the system host. For example, it obtains the firmware update file name corresponding to the system host firmware from the cloud server; according to the file name, it can be downloaded from the cloud server to the local computer for updating the firmware for the system host. Since the system host does not have a communication link with the cloud server, the communication slave can replace the cloud server or the USB flash drive to update the firmware for the system host. During the firmware update process, the communication slave is in control and will also involve the restart of the system host. Therefore, the system host is switched from host mode to slave mode, and the communication slave is switched to host mode. After the firmware update is completed, the previous master-slave mode is restored.

[0075] In this embodiment, it also includes:

[0076] Filter the file name used for system host firmware update based on the communication slave and obtain the download link;

[0077] According to the download link, the communication slave obtains the firmware update file for the system master.

[0078] Specifically, the communication slave obtains the download link according to the file name of the system host firmware update, first downloads it from the cloud server to the local storage space, and then copies the firmware update file from the storage space controlled by the communication slave to the storage space of the system host.

[0079] In this embodiment, it also includes:

[0080] Obtain the firmware update file for the system host from the communication slave, send a request to update the system host firmware, and wait for feedback;

[0081] If, within a first preset time threshold, the communication slave obtains feedback that allows the system master firmware to be updated, then according to the system master sending the feedback, the system master switches to a slave working mode, and according to the communication slave receiving the feedback, the communication slave switches to a master working mode;

[0082] The feedback includes instruction information for switching between the master and slave machines.

[0083] Specifically, the communication slave initiates an update of the system master's firmware. After obtaining the firmware update file for the system master, it sends a request to the system master to update the system master's firmware and waits for feedback. The feedback contains information about the master-slave switch. At this point, the system master and the communication slave each actively switch their operating modes: the communication slave switches to master mode, and the system master switches to slave mode.

[0084] The system host needs to self-detect the storage area where the firmware is stored. For example, the storage area where the system host stores the firmware is divided into A / B areas. A / B areas can each store a copy of the firmware. When the screen is displayed normally, the firmware of one partition in the A / B area is used, and the corresponding other partition can be erased and written. When the screen restarts, the timestamps of the two partitions will be detected. The firmware of the partition with the closer time will be executed. If the system host self-detection is completed within the first preset time threshold and meets the conditions for updating the firmware, a request is sent to the communication slave for the system host and the communication slave to switch to the master-slave mode. The communication slave responds to the request for the master-slave mode. At this time, the communication slave and the system host can each switch to the master-slave mode, or the system host can switch to the slave mode first, and the communication slave can switch to the master working mode based on the feedback of the system host switching to the slave mode.

[0085] In this embodiment, it also includes:

[0086] According to the communication slave switching to the master working mode, the communication slave queries the system master's current firmware running area;

[0087] According to the current firmware operation area of ​​the system host, the communication slave sends and receives a request for the firmware update file and waits for feedback;

[0088] The system host self-detects whether the firmware storage space can receive the firmware update file upon receiving the request to receive the firmware update file;

[0089] If the detection result is no, the system host sends a feedback message of refusing to receive the firmware update file.

[0090] Specifically, the communication slave queries the system host whether the current firmware running area is normal. For example, if the current firmware is running in area A, and area B is not normally accessible, then the firmware update will be difficult to implement. According to the communication slave switching to the host working mode, the communication slave can query the system host for the current firmware running area. If the current firmware running area is detected to be normal, then another area can be used as a storage space for receiving firmware update files. The communication slave sends a request to receive the firmware update file, activating the system host to self-detect whether the firmware storage space can receive the firmware update file. If the detection result is no, the system host sends feedback information refusing to receive the firmware update file, and the communication slave can give up the firmware update.

[0091] In this embodiment, self-detecting whether the firmware storage space can receive the firmware update file further includes:

[0092] If the detection result is yes, the system host sends a feedback message allowing the reception of the firmware update file;

[0093] According to the feedback information of sending permission to receive the firmware update file, the system host verifies the received firmware update file package, including the sub-packages split from the firmware update file package;

[0094] If verification of the firmware update file package and any sub-package of the firmware update file package fails, the system host receives the firmware update file package again and records the number of times the firmware update file package is received again;

[0095] Determine whether the number of times the system host re-receives the firmware update file package exceeds a preset update number threshold;

[0096] If the number of updates exceeds the preset threshold, the system host stops receiving the firmware update file package and sends a feedback message of refusing to receive the firmware update file;

[0097] The communication slave stops sending requests for receiving the firmware update file according to the feedback information of receiving the rejection of the firmware update file.

[0098] Specifically, if the self-detection firmware storage space can receive the firmware update file, the firmware update file will be transferred from the communication slave to the system host. The firmware update file cannot be transferred directly in one step, and needs to be split into multiple small data packets and finally spliced ​​into a complete firmware update file. The system host verifies each small data packet. If any small data packet fails to be transferred, the entire firmware update file fails to be transferred. The previous data packet needs to be discarded and the firmware update file needs to be transferred again. If the firmware update file package is not received successfully multiple times, there may be a communication failure. You can first abandon the transfer of the firmware update file to maintain the current stable working state. The communication slave also stops sending requests to receive the firmware update file based on the feedback information of the rejection of the firmware update file.

[0099] In this embodiment, determining whether the number of times the system host re-receives the firmware update file package exceeds a preset update number threshold further includes:

[0100] If the preset update number threshold is not exceeded and the system host has completed receiving the firmware update file package, the system host sends a feedback message indicating that the firmware update file has been received;

[0101] The communication slave receives feedback information indicating that the firmware update file has been completed, and stops sending requests for receiving the firmware update file;

[0102] The communication slave switches to slave working mode according to the request to stop sending and receiving firmware update files;

[0103] The system host switches to the host working mode according to the feedback information of sending and receiving the firmware update file completion or sending the feedback information of refusing to receive the firmware update file.

[0104] Specifically, regardless of whether the firmware update file is successfully or unsuccessfully transmitted, the system must return to normal operation. If the communication slave receives a request to stop sending and receiving firmware update files, it indicates that the system master has rejected the firmware update and the communication slave switches to slave mode. Feedback indicating that the firmware update file is complete or that the firmware update file has been rejected indicates that the firmware update has concluded and the system must switch to master mode, returning to normal operation.

[0105] FIG2 is a structural diagram of a vehicle system firmware upgrade system provided by one or more embodiments of the present invention.

[0106] The vehicle system firmware upgrade system shown in FIG2 includes: a screen display system and a CSC host system;

[0107] Screen display system, used for system host;

[0108] CSC host system, used for communicating slaves;

[0109] The CSC host system connects to the cloud or storage to obtain the firmware update file of the display system;

[0110] The CSC host system connects to the screen display system and sends a request to update the screen display system firmware according to the firmware update file obtained from the screen display system;

[0111] The screen display system obtains the firmware update file of the screen display system according to the CSC host system, and the feedback allows the screen display system to receive feedback information of the firmware update file;

[0112] According to the feedback information allowing the screen display system to receive the firmware update file, the screen display system is converted into the slave mode;

[0113] According to the feedback information received by the CSC host system allowing the screen display system to receive the firmware update file, the CSC host system switches to the host mode;

[0114] The screen display system receives the firmware update file and displays a graphic or symbol corresponding to the progress or status of the firmware update file on the screen display terminal according to the progress or status of the firmware update file.

[0115] Specifically, the CSC host system itself has an interface for external communications, while the on-screen display system, as a host, lacks such an interface. To upgrade the on-screen display system, the CSC host system is required to retrieve the firmware update file. Since the on-screen display system can still operate under the old firmware while receiving the firmware update file, it can display graphics or symbols such as a progress bar based on the feedback from receiving the firmware update file. Once the progress is fully displayed, the on-screen display system can be restarted to use the new firmware file.

[0116] FIG3 is a structural diagram of a vehicle system firmware upgrading device provided by one or more embodiments of the present invention.

[0117] The vehicle system firmware upgrade device shown in FIG3 includes: a system host module, a communication slave module, an external communication link module, a file filtering module, and a mode conversion module;

[0118] System host module, used to connect to communication slaves;

[0119] Communication slave module, used to obtain the firmware identity information of the system host;

[0120] External communication link module, used for connecting with communication slaves;

[0121] A file filtering module is used for the communication slave to filter the communication information on the external communication link according to the firmware identity information of the system host and determine whether there is a file name for updating the system host firmware;

[0122] The mode conversion module is used to convert the master-slave mode of the system host and the communication slave if a file name for updating the system host firmware is filtered out.

[0123] It is worth noting that although this system only discloses the personnel system host module, communication slave module, external communication link module, file filtering module, and mode conversion module, relatively speaking, what the present invention wants to express is that, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the existing technology to form an infinite number of embodiments or technical solutions. In other words, this system is open rather than closed. Just because this embodiment only discloses individual basic functional modules, it cannot be considered that the scope of protection of the claims of the present invention is limited to the above-mentioned basic functional modules.

[0124] Through the above solution, the following beneficial technical effects are achieved:

[0125] This application uses a subsystem that can communicate with the outside to obtain the firmware update file of the subsystem connected to the subsystem, so that each subsystem can update its firmware online without having to disassemble it separately and update the firmware one by one.

[0126] This application converts the master-slave working mode of the subsystem so that the subsystem that communicates with the outside world can use the slave as the master to update the firmware for the slave. After the update is completed, it returns to the original master-slave working mode, so that the subsystems in the master working mode and the slave working mode can complete the firmware update with the assistance of the subsystem that communicates with the outside world.

[0127] This application partially upgrades the firmware of a subsystem and maintains the working status of other subsystems, so that the vehicle can complete the firmware update online without suspending the entire vehicle system, reducing the impact on vehicle operation.

[0128] FIG4 is a schematic diagram of a system for upgrading a screen display system according to a specific embodiment of the present invention.

[0129] FIG5 is a timing diagram of a screen display system upgrade according to a specific embodiment of the present invention.

[0130] FIG6 is a schematic diagram of a flow chart of screen display system upgrade according to a specific embodiment of the present invention.

[0131] In a specific embodiment, as shown in Figure 4, when the screen needs to be upgraded, the screen firmware can be obtained from the cloud or offline using a USB flash drive. After the vehicle's CSC host obtains the screen firmware, it will perform security and integrity checks on the firmware. After ensuring that there are no problems with the firmware, the screen firmware will be stored in a shared directory; when the user wants to upgrade the screen, he can click the Start Upgrade button on the screen. At this time, the OTA Service (online service) transmits the upgrade control command to the screen node. After receiving the upgrade command, the screen node will traverse the corresponding shared directory to find the firmware .bin file that meets the naming rules; when the corresponding firmware is found, it will be read into the system. At this time, the screen node notifies the screen device to update the firmware; starting from reading the firmware in the shared directory, the screen node will regularly feedback the upgrade status to the OTA Service, and the CSC host will display the upgrade progress or upgrade error status on the screen. At this time, the screen is still using the old firmware, and the display function is not affected.

[0132] In another specific embodiment, as shown in FIG5 , the host (screen) requests an upgrade. The screen determines whether to perform a firmware upgrade based on its own status. If the current status is suitable for an upgrade, the screen notifies the CSC host to send the firmware information. If it is not suitable for an upgrade or another error occurs, the CSC host is notified of the abnormal status. The CSC host sends the firmware information to the screen based on the received screen information. The screen confirms the number of sub-packets based on the firmware information (firmware size, checksum, sub-packet size, etc.), and then notifies the CSC host to send the sub-packets with the corresponding sequence numbers. The screen sends the corresponding sub-packets based on the received information, and this cycle repeats until the screen receives all sub-packets. During the interactive firmware sub-packetization process, the screen checks and verifies the integrity and security of each sub-packet. If any error occurs in any intermediate packet, after five repetitions, the screen stops the upgrade, reports the error to the CSC host, and resets. After the last packet is transmitted, the screen performs another verification. If the verification passes, the CSC host is notified of the successful upgrade, and the screen-side upgrade is complete. After receiving the upgrade success message, the CSC host can choose to reset the screen and switch the A / B side, completing the entire process.

[0133] The CSC host queries the current screen version number and confirms whether the current screen firmware is running in area A or area B, and then the other area is available.

[0134] The CSC host sends the upgrade request instruction (including information about upgrading area A or area B) to the screen. After receiving the upgrade request, the screen checks the read / write status of its own partition. If the free partition is not writable, the upgrade request from the CSC host is rejected. If it is writable, the CSC host is notified to send firmware information, and the two devices interact frame by frame according to the protocol.

[0135] During the firmware package exchange process, the screen will check and verify the integrity and security of each sub-package. If any package in the middle has an error, after repeating 5 times, the screen will stop the upgrade process and notify the CSC vehicle computer;

[0136] After the last packet is received, the screen performs an integrity check on the upgrade package. If the check passes, the CSC host is notified that the screen upgrade is complete, and the screen waits for reset to switch between the A / B side.

[0137] During the entire screen upgrade process, since the partition being written is a free partition, it will not affect the normal display of the screen. After the upgrade is successful, the screen will be reset and restarted again before selecting the newer one in the A / B side for use, so the display function of the screen will not be affected throughout the process.

[0138] The .bin file is the firmware used to upgrade the display. Its file type extension is "bin," and it serves as a firmware update file. The display node is the module in the CSC host that communicates with the display and is a self-contained code module within the CSC host. The display's status determines whether the partition to be upgraded is writable. If the partition storing the firmware is protected or non-writable, the display cannot be upgraded. The display detects this status and reports it to the CSC host via feedback. Because the storage area where the screen stores firmware is divided into A / B area, A / B area can store one copy of firmware respectively. When the screen displays normally, it uses the firmware of one partition in A / B area, and the corresponding other partition can be erased and written. When the screen restarts, it will detect the timestamps of the two partitions. The firmware of the partition with the more recent time will be executed, and the partition with the older firmware will be in an erasable state. The partition where the current firmware of the screen is executed can be obtained from the version number. The screen version number will be read when the CSC host is powered on. When the CSC sends an upgrade request, it specifies whether the current area to be upgraded is A or B in the request instruction, so as not to affect the current screen display. The entire upgrade process is started by the on-board CSC host. At this time, the screen node in the on-board CSC acts as a slave, and the screen receives the upgrade start request as the host. Screen self-detection After that, the self-test information and master-slave switching are fed back to the screen node of the CSC. At this time, the screen node in the on-board CSC is converted from a communication slave to a host, and the system host is converted to a slave. After the upgrade process is started, the screen node of the on-board CSC sends the corresponding firmware package or stops the upgrade according to the feedback from the screen; when the screen firmware needs to be updated, the on-board CSC host will prompt the user on the screen that new firmware is currently available. At this time, the user can choose to update the firmware. After the on-board CSC host receives the user's choice to update the firmware, it obtains the new firmware from the cloud (or USB flash drive). After obtaining the new firmware, it will prompt the user on the screen "Firmware acquisition successful, do you want to upgrade the screen immediately?", and then the user can choose whether to upgrade the screen; when the user does not want to upgrade the screen at this time, he can select "No"; and then choose a suitable time to upgrade the screen (the subsequent screen will prompt the user that there is firmware for upgrading the screen according to a certain period).

[0139] In another specific embodiment, as shown in FIG6 , the CSC vehicle computer periodically checks the cloud or queries whether there is updateable screen firmware in the U disk inserted into the vehicle computer. The screen firmware file name has a certain naming rule, and the detection is performed according to this rule; when available screen firmware is detected, the corresponding icon will flash on the screen to prompt the user that screen firmware is currently available for upgrade; the user clicks the flashing icon, and a corresponding dialog box pops up to prompt the user whether to obtain the firmware. If the user chooses yes, the CSC vehicle computer obtains the firmware immediately. If the user chooses no, the icon goes out and a prompt box pops up to inform the user that the icon will flash again in 6 hours to prompt the user with this message; if the user chooses to obtain the firmware immediately, the icon stops flashing and becomes constantly on. If the firmware acquisition fails due to network or U disk transmission reasons, the user will be prompted with the reason for the failure and asked whether to obtain the firmware again; if the user chooses yes, it will be obtained again. If the user chooses no, the icon goes out A prompt box will pop up to inform the user that the icon will flash again in 6 hours to prompt the user with this message; after the user obtains the firmware, it will be verified. If the verification fails, the user will be prompted and asked whether to obtain the firmware again, and then the same process as 4 will be executed; if the verification passes, the available firmware icon will go out, and the screen upgrade icon will start flashing. At this time, a prompt box will pop up to ask the user whether to upgrade immediately; if the user chooses to upgrade immediately, the CSC car computer will start to interact with the screen for upgrading (see Figure 5 for the interaction process); if the user chooses no, the screen upgrade icon will go out, and a prompt box will pop up to inform the user that the icon will flash again in 6 hours to prompt the user with this message; during the upgrade process, the screen will display the firmware upgrade progress in real time; if the upgrade is successful, a dialog box will pop up to ask the user whether to reset the screen immediately and use the new firmware. If you choose yes, the screen will reset, the A / B side will switch, and the upgrade will end; if you choose no, you will exit the upgrade process and wait for the next screen restart to use the new firmware. If an error occurs during the upgrade process, an upgrade error code will be displayed and the user will be asked whether to upgrade again. If you select Yes, the upgrade process will be repeated. If you select No, the upgrade icon on the screen will be turned off and a prompt box will pop up to inform the user that the icon will flash again in 6 hours to remind the user of this message.

[0140] FIG7 is a block diagram of an electronic device structure of a vehicle system firmware upgrade method provided by one or more embodiments of the present invention.

[0141] As shown in FIG7 , the present application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0142] A computer program is stored in the memory. When the computer program is executed by the processor, the processor executes the steps of a vehicle system firmware upgrade method.

[0143] The present application also provides a computer-readable storage medium storing a computer program executable by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of a vehicle system firmware upgrade method.

[0144] The present application also provides a vehicle, comprising:

[0145] An electronic device for implementing the steps of a vehicle system firmware upgrade method;

[0146] a processor that runs a program and, when the program is running, executes the steps of the vehicle system firmware upgrade method based on data output by the electronic device;

[0147] The storage medium is used to store a program, and when the program is running, it executes the steps of the vehicle system firmware upgrade method for data output from the electronic device.

[0148] The communication bus mentioned in the electronic device mentioned above may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0149] The electronic device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory. The operating system can be any one or more computer operating systems that control electronic devices through processes, such as the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the Windows operating system. In the embodiments of the present invention, the electronic device can be a handheld device such as a smartphone or a tablet computer, or an electronic device such as a desktop computer or a portable computer, which is not particularly limited in the embodiments of the present invention.

[0150] The execution subject of the electronic device control in the embodiment of the present invention can be an electronic device, or a functional module in the electronic device that can call a program and execute the program. The electronic device can obtain the firmware corresponding to the storage medium. The firmware corresponding to the storage medium is provided by the supplier. The firmware corresponding to different storage media can be the same or different, and is not limited here. After the electronic device obtains the firmware corresponding to the storage medium, it can write the firmware corresponding to the storage medium into the storage medium, specifically, burn the firmware corresponding to the storage medium into the storage medium. The process of burning the firmware into the storage medium can be implemented using existing technology and will not be described in detail in the embodiment of the present invention.

[0151] The electronic device can also obtain a reset command corresponding to the storage medium. The reset command corresponding to the storage medium is provided by the supplier. The reset commands corresponding to different storage media can be the same or different, and are not limited here.

[0152] In this case, the storage medium of the electronic device is a storage medium in which the corresponding firmware is written. The electronic device can respond to the reset command corresponding to the storage medium in which the corresponding firmware is written, thereby resetting the storage medium in which the corresponding firmware is written according to the reset command corresponding to the storage medium. The process of resetting the storage medium according to the reset command can be implemented in the existing technology and will not be described in detail in the embodiments of the present invention.

[0153] For the convenience of description, the above devices are described as various units and modules according to their functions. Of course, when implementing this application, the functions of each unit and module can be implemented in the same or multiple software and / or hardware.

[0154] Those skilled in the art will understand that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by those skilled in the art in the art to which the present invention pertains. It should also be understood that terms such as those defined in common dictionaries should be understood to have meanings consistent with those in the context of the prior art and, unless specifically defined, will not be interpreted in an idealized or overly formal sense.

[0155] For simplicity of description, the method embodiments are described as a series of actions. However, those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because certain steps can be performed in other orders or simultaneously according to the embodiments of the present invention. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0156] As can be seen from the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented using software plus a necessary general-purpose hardware platform. Based on this understanding, the technical solution of the present application, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for causing a computer device (such as a personal computer, server, or network device) to execute the methods described in various embodiments of the present application, or portions thereof.

[0157] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A vehicle system firmware upgrade method, characterized in that: The vehicle system firmware upgrade method comprises: The system host connects to the communication slave; The communication slave obtains the firmware identity information of the system host; The communication slave is connected to an external communication link; The communication slave filters the communication information on the external communication link according to the firmware identity information of the system host, and determines whether there is a file name for updating the firmware of the system host; If a file name for updating the system host firmware is filtered out, the system host and the communication slave switch the master-slave mode.

2. The vehicle system firmware upgrade method according to claim 1, characterized in that: Also includes: Obtain a download link according to the file name for updating the system host firmware filtered by the communication slave; According to obtaining the download link, the communication slave obtains the firmware update file for the system master.

3. The vehicle system firmware upgrade method according to claim 2, characterized in that: Also includes: Acquire a firmware update file for the system host according to the communication slave, send a request to update the system host firmware, and wait for feedback from the system host; If, within a first preset time threshold, the communication slave obtains feedback from the system host that the system host firmware is allowed to be updated, then according to the system host sending the feedback, the system host switches to a slave working mode, and according to the communication slave receiving the feedback, the communication slave switches to a master working mode; The feedback includes instruction information for switching between the master and slave machines.

4. The vehicle system firmware upgrade method according to claim 3, characterized in that: Also includes: According to the communication slave being converted into the host working mode, the communication slave queries the current firmware running area of ​​the system host; According to the current firmware running area of ​​the system host, the communication slave sends a request to receive a firmware update file and waits for feedback; The system host self-detects whether the firmware storage space can receive the firmware update file according to the request for receiving the firmware update file; If the detection result is no, the system host sends feedback information of refusing to receive the firmware update file.

5. The vehicle system firmware upgrade method according to claim 4, characterized in that: The self-detection of whether the firmware storage space can receive the firmware update file also includes: If the detection result is yes, the system host sends feedback information allowing the firmware update file to be received; According to the feedback information of sending the permission to receive the firmware update file, the system host verifies the received firmware update file package, including the sub-packages of the firmware update file package; According to the failure of verification of the firmware update file package and any sub-package of the firmware update file package, the system host receives the firmware update file package again, and records the number of times the firmware update file package is received again; Determine whether the number of times the system host re-receives the firmware update file package exceeds a preset update number threshold; If the number of updates exceeds a preset threshold, the system host stops receiving the firmware update file package and sends a feedback message of refusing to receive the firmware update file; The communication slave stops sending the request for receiving the firmware update file according to the feedback information of refusing to receive the firmware update file.

6. The vehicle system firmware upgrade method according to claim 5, characterized in that: The determining whether the number of times the system host re-receives the firmware update file package exceeds a preset update number threshold further includes: If the preset update number threshold is not exceeded and the system host has completed receiving the firmware update file package, the system host sends feedback information indicating that the firmware update file has been received; The communication slave receives feedback information indicating that the firmware update file has been completed, and stops sending requests for receiving the firmware update file; The communication slave is converted into a slave working mode according to the request to stop sending and receiving the firmware update file; The system host switches to the host working mode according to the feedback information of completing the sending and receiving of the firmware update file or sending the feedback information of refusing to receive the firmware update file.

7. A vehicle system firmware upgrade system, characterized in that: The vehicle system firmware upgrade system includes: a screen display system and a CSC host system; The screen display system is used for the system host; The CSC host system is used for communicating with slaves; The CSC host system is connected to the cloud or storage to obtain the firmware update file of the screen display system; The CSC host system is connected to the screen display system, and sends a request to update the screen display system firmware according to the firmware update file of the screen display system; The screen display system obtains a firmware update file of the screen display system according to the CSC host system, and feeds back feedback information allowing the screen display system to receive the firmware update file; According to the feedback information allowing the screen display system to receive the firmware update file, the screen display system is converted into a slave mode; According to the CSC host system receiving feedback information that allows the screen display system to receive the firmware update file, the CSC host system switches to the host mode; The screen display system receives the firmware update file, and displays a graphic or symbol corresponding to the progress or status of receiving the firmware update file on the screen display terminal according to the progress or status of receiving the firmware update file.

8. A vehicle system firmware upgrade device, characterized in that: The vehicle system firmware upgrade device comprises: System host module, used to connect to the communication slave; The communication slave module is used to obtain the firmware identity information of the system host; An external communication link module, used for connecting with the communication slave; A file filtering module, used for the communication slave to filter the communication information on the external communication link according to the firmware identity information of the system host, and determine whether there is a file name for updating the firmware of the system host; The mode conversion module is used to convert the master-slave mode of the system host and the communication slave if a file name for updating the system host firmware is filtered out.

9. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; A computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the vehicle system firmware upgrade method according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: include: It stores a computer program that can be executed by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the vehicle system firmware upgrade method described in any one of claims 1 to 6.

Images