High-voltage component controller firmware flashing method, vehicle control unit, vehicle and medium

Abstract

The invention provides a high-voltage component controller firmware flashing method, a vehicle control unit, a vehicle and a medium, the method is applied to the vehicle control unit, and the method comprises the steps that if a firmware flashing request is received, a high-voltage component high-voltage power-on instruction is sent to a battery controller, and if a high-voltage component is in a high-voltage power supply state, the battery controller is powered on; if yes, a firmware flashing enabling signal is sent to the high-voltage component controller. In the embodiment of the invention, a vehicle control unit sends a high-voltage part high-voltage power-on instruction to a battery controller, the battery controller supplies high-voltage power to a high-voltage part, and after the precondition of firmware flashing of the high-voltage part controller is met, a firmware flashing enabling signal is sent to the high-voltage part controller, and firmware flashing of the high-voltage part controller is carried out. High-voltage power-on of the high-voltage part is achieved through the vehicle control unit and the battery controller, the process is simple, efficiency is improved, and safety risks faced by operators are avoided.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a method for flashing firmware of a high-voltage component controller, electronic equipment, vehicle, and medium. Background Technology

[0002] Controller firmware flashing refers to the process of writing new firmware programs into the controller through a specific communication interface. It can be used to fix software defects, optimize performance, or add new functions, and is an important means of maintaining and upgrading electronic equipment.

[0003] The firmware flashing of different controllers may have different prerequisites. When the firmware of the high-voltage component controller in a new energy vehicle is flashed, the corresponding high-voltage component usually needs to be in a high-voltage power-on state.

[0004] However, in related technologies, the high-voltage power-on of high-voltage components often requires manual triggering by operators, which is cumbersome, inefficient, and may even pose safety hazards to operators and equipment.

[0005] It should be noted that the information disclosed in the background section of this application is intended only to enhance the understanding of the general background of this application, and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0006] This application provides a method for flashing firmware for a high-voltage component controller, a vehicle controller, a vehicle, and a medium, which helps to solve the problems of cumbersome, inefficient, and potentially dangerous high-voltage power-on process for high-voltage components.

[0007] In a first aspect, embodiments of this application provide a method for flashing firmware for a high-voltage component controller, applied to a vehicle controller, the method comprising: If a firmware flashing request is received, a high-voltage power-on command for the high-voltage component is sent to the battery controller. The battery controller is used to supply high-voltage power to the high-voltage component according to the high-voltage power-on command. If the high-voltage component is in a high-voltage power supply state, it sends a firmware flashing enable signal to the high-voltage component controller. The high-voltage component controller is used to enter the firmware flashing mode according to the firmware flashing enable signal.

[0008] Among the possible implementations are: If the high-voltage component is in a high-voltage power supply state and the operating condition of the high-voltage component meets the preset safety alarm conditions, a high-voltage power-off command for the high-voltage component is sent to the battery controller. The battery controller is also used to power off the high-voltage component according to the high-voltage power-off command.

[0009] Among the possible implementations are: If the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, a firmware flashing termination signal is sent to the high-voltage component controller. The high-voltage component controller is also used to exit the firmware flashing mode according to the firmware flashing termination signal.

[0010] Among the possible implementations are: If the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, then a high-voltage power-off command for the high-voltage component is sent to the battery controller. The battery controller is also used to power off the high-voltage component according to the high-voltage power-off command.

[0011] In some possible implementations, after sending the firmware flashing enable signal to the high-voltage component controller, the method further includes: Obtain the firmware flashing result of the high-voltage component controller; If the firmware flashing result of the high-voltage component controller is successful, a high-voltage power-down command is sent to the battery controller. The battery controller is also used to power down the high-voltage component according to the high-voltage power-down command; and / or If the firmware flashing result of the high-voltage component controller is a flashing failure, then the firmware flashing enable signal is sent to the high-voltage component controller again.

[0012] In some possible implementations, after sending the firmware flashing enable signal to the high-voltage component controller, the method further includes: Obtain the firmware flashing result of the high-voltage component controller; If the firmware flashing result of the high-voltage component controller is successful, a high-voltage power-down command is sent to the battery controller. The battery controller is also used to power down the high-voltage component according to the high-voltage power-down command; and / or If the firmware flashing result of the high-voltage component controller is a flashing failure, then the firmware flashing enable signal is sent to the high-voltage component controller again.

[0013] In some possible implementations, if the firmware flashing result of the high-voltage component controller fails, the firmware flashing enable signal is sent to the high-voltage component controller again, including: If the firmware flashing result of the high-voltage component controller is a flashing failure, and the number of flashing retries is greater than or equal to a preset retry threshold, then a high-voltage power-down command for the high-voltage component is sent to the battery controller; and / or If the firmware flashing result of the high-voltage component controller is a flashing failure, and the number of flashing retries is less than the preset retry threshold, then the firmware flashing enable signal is sent to the high-voltage component controller again.

[0014] Secondly, embodiments of this application also provide a vehicle controller, which is configured to perform the method described in any one of the first aspects; Thirdly, embodiments of this application also provide a vehicle, the vehicle comprising: The vehicle controller, the high-voltage component controller, and the battery controller are configured to perform the method described in any one of the first aspects.

[0015] Fourthly, embodiments of this application also provide a computer-readable storage medium, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the method described in any one of the first aspects.

[0016] In this embodiment, the vehicle controller sends a high-voltage power-on command to the battery controller, and the battery controller supplies high-voltage power to the high-voltage component. When the preconditions for firmware flashing of the high-voltage component controller are met, a firmware flashing enable signal is sent to the high-voltage component controller to perform firmware flashing of the high-voltage component controller. High-voltage power-on of the high-voltage component is achieved through the vehicle controller and the battery controller. The process is simple, the efficiency is improved, and the safety risks faced by the operator are avoided. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a structural diagram illustrating an application scenario provided in an embodiment of this application. Figure 2 A flowchart illustrating a firmware flashing method for a high-voltage component controller provided in this application embodiment; Figure 3 A flowchart illustrating another method for flashing firmware for a high-voltage component controller provided in this application embodiment; Figure 4 A flowchart illustrating another method for flashing firmware for a high-voltage component controller provided in this application embodiment; Figure 5 A flowchart illustrating another method for flashing firmware for a high-voltage component controller provided in this application embodiment; Figure 6 This is a structural schematic diagram of a vehicle provided in an embodiment of this application. Detailed Implementation To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0019] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0020] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0021] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0022] Controller firmware flashing refers to the process of writing new firmware programs into the controller through a specific communication interface. It can be used to fix software defects, optimize performance, or add new functions, and is an important means of maintaining and upgrading electronic equipment.

[0023] Specifically, the controller to be flashed can communicate with external devices, and the firmware flashing is performed based on the communication with the external devices and the controller's internal boot program. Firmware flashing can be performed via a wired connection or via Over-the-Air (OTA) technology. That is, firmware updates can be remotely pushed to terminal devices such as controllers via a server and communication network, and the controller can then execute the flashing process after receiving the update.

[0024] The firmware flashing of different controllers may have different prerequisites. When the firmware of the high-voltage component controller in a new energy vehicle is flashed, the corresponding high-voltage component usually needs to be in a high-voltage power-on state.

[0025] It is understandable that new energy vehicles typically include multiple high-voltage components. These high-voltage components may include drive motors, electric compressors, etc. Each high-voltage component is usually managed and controlled by a corresponding high-voltage component controller. For example, the drive motor controller controls the vehicle's drive motor, and the compressor controller controls the vehicle's electric compressor.

[0026] Furthermore, there may be specific requirements when flashing the firmware of high-voltage component controllers in new energy vehicles. For example, relevant technical standards (such as ISO 14229-1) specify the preconditions for flashing the firmware of high-voltage component controllers, including simultaneously ensuring both low-voltage power supply to the controller and high-voltage power supply to the high-voltage components. The low-voltage power supply maintains the basic operation of the controller, while the high-voltage power supply ensures that its associated high-voltage components are in an active state.

[0027] See Figure 1 This is a structural diagram illustrating an application scenario provided in an embodiment of this application, such as... Figure 1 As shown, the vehicle 100 includes a vehicle controller 101, a high-voltage component controller 102, and a high-voltage component 103. The vehicle controller 101 is electrically connected to the high-voltage component controller 102, and the high-voltage component controller 102 is electrically connected to the high-voltage component 103.

[0028] Understandably, the vehicle controller 101 is usually the core control unit of the vehicle 100. It can be used to generate and send control commands to other controllers based on the driver's operation instructions, vehicle status information and / or feedback signals from various components, so as to achieve the orderly operation of the vehicle.

[0029] A communication connection is typically established between the vehicle controller 101 and the high-voltage component controller 102. This communication connection can include a connection via an in-vehicle network such as a Controller Area Network (CAN) bus, or a direct hardwired connection. Through this communication connection, the vehicle controller 101 can send commands to the high-voltage component controller 102. The high-voltage component controller 102 can then execute corresponding operations based on the received commands, or control its corresponding high-voltage component 103 to perform corresponding operations.

[0030] As mentioned earlier, firmware flashing of the high-voltage component controller 102 typically requires certain preconditions to be met. These include the high-voltage component controller 102 itself receiving a stable low-voltage power supply, and the high-voltage component 103 it controls being in a high-voltage powered state. Specifically, the high-voltage component controller 102 can be supplied with a low-voltage power supply through the battery in the vehicle 100, while the high-voltage component 103 can be supplied with a high-voltage power supply through the power battery in the vehicle 100.

[0031] Once the aforementioned preconditions for firmware flashing are met, firmware flashing of the high-voltage component controller 102 can be performed. In one possible implementation, the vehicle 100 can establish a connection with a remote server via a communication network. The vehicle controller 101 can act as a relay for forwarding firmware flashing commands and data. Specifically, the vehicle controller 101 can receive a firmware data packet for updating the high-voltage component controller 102 from the server. Subsequently, the vehicle controller 101 can send the firmware data packet to the target high-voltage component controller 102 via the aforementioned communication connection, whereby the high-voltage component controller 102 performs firmware flashing using a preset flashing bootloader and the received firmware data packet.

[0032] However, in related technologies, the high-voltage power-on of high-voltage components often requires manual triggering by operators, which is cumbersome, inefficient, and may even pose safety hazards to operators and equipment.

[0033] In view of this, this application provides a method for flashing firmware for a high-voltage component controller. This method, applied to a vehicle controller, helps to solve the problems of cumbersome, inefficient, and potentially dangerous high-voltage power-on processes for high-voltage components. The embodiments of this application are described in detail below with reference to the accompanying drawings.

[0034] See Figure 2 This is a flowchart illustrating a firmware flashing method for a high-voltage component controller provided in an embodiment of this application, which can be applied to, for example... Figure 1 The application scenarios shown are as follows: Figure 2 As shown, the method specifically includes the following steps.

[0035] S201: If a firmware flashing request is received, a high-voltage power-on command for the high-voltage components is sent to the battery controller.

[0036] The battery controller is used to supply high-voltage power to the high-voltage components according to the high-voltage power-on command.

[0037] In this embodiment, the firmware flashing request is typically a signal sent by an external device to initiate the firmware flashing process. It usually includes the identification information of the controller to be flashed and the firmware version. The external device may include a cloud server and a diagnostic device. Specifically, when the firmware flashing request originates from a cloud server, the Vehicle Control Unit (VCU) can receive the request through a vehicle networking communication module such as a Telematics Box (TBOX). When the firmware flashing request originates from a local diagnostic device, the VCU can receive the request through an on-board diagnostic interface.

[0038] Those skilled in the art will understand that a battery controller typically refers to a control unit within a Battery Management System (BMS) that manages and controls the vehicle's battery. The battery controller can control the vehicle's power battery. In the embodiments of this application, the battery controller is communicatively connected to the vehicle controller. Specifically, this communication connection can be achieved via hard wiring or the vehicle's CAN bus. This allows the vehicle controller to send control commands to the battery controller, and the battery controller to send battery status information and / or command feedback to the vehicle controller. It is understandable that a high-voltage component power-on command can be a command issued by the vehicle controller to the battery controller to provide high-voltage power to a specific high-voltage component. Specifically, the high-voltage component power-on command is usually a specific flag bit or status signal predefined in the application layer protocol.

[0039] In this embodiment, if the vehicle controller receives a firmware flashing request, it sends a high-voltage power-on command to the battery controller. The battery controller then supplies high-voltage power to the high-voltage component according to the command. Specifically, after receiving the high-voltage power-on command, the battery controller controls the operation of switching elements such as contactors or relays to establish a high-voltage power supply circuit for the target high-voltage component through the power battery, thus supplying high-voltage power to the high-voltage component.

[0040] For example, after receiving a high-voltage power-on command for the high-voltage component, the battery controller closes the pre-charge relay and the main positive relay to establish a high-voltage pre-charge circuit including the power battery and the target high-voltage component, thus performing high-voltage pre-charge for the high-voltage component. Once pre-charge is complete, the pre-charge relay is disconnected and the main negative relay is closed to establish a complete high-voltage power supply circuit, providing high-voltage power to the high-voltage component.

[0041] Of course, the vehicle controller can also obtain or directly obtain the status parameters or power-on feedback of the high-voltage component's high-voltage power-on process through the battery controller to safely control the high-voltage power-on process of the high-voltage component. For example, during the high-voltage pre-charging process of the high-voltage component, the resistance temperature of the pre-charging resistor in the pre-charging circuit can be obtained; when the main negative relay and / or the main positive relay are closed, the voltage in the high-voltage power supply circuit can be obtained. If the status parameters or power-on feedback of the high-voltage component's high-voltage power-on process meet the preset abnormal conditions, corresponding safety measures will be taken.

[0042] In some possible implementations, if a firmware flashing request is received, the operating status of the high-voltage component is obtained; if the operating status of the high-voltage component does not meet the preset firmware flashing conditions, a high-voltage power-on command for the high-voltage component is sent to the battery controller.

[0043] Understandably, the operating status of high-voltage components can include information such as whether the high-voltage component is in a high-voltage energized state, whether there are fault codes, and the current operating temperature. Specifically, the vehicle controller can directly obtain the operating status of the high-voltage components or obtain it through a communication connection with the high-voltage component controller.

[0044] Understandably, after receiving a firmware flashing request, the vehicle controller can first obtain the current operating status of the target high-voltage component and compare it with the preset firmware flashing conditions. If the operating status of the high-voltage component does not meet the preset firmware flashing conditions, a high-voltage power-on command is sent to the battery controller. Further, if the operating status of the high-voltage component meets the preset firmware flashing conditions, the vehicle controller can execute subsequent procedures.

[0045] Specifically, the preset firmware flashing conditions may include the high-voltage components being in a high-voltage powered-on state. In addition, other conditions may be included, such as whether there are fault alarms and whether the component temperature is within the allowable range.

[0046] For example, if the high-voltage component is not currently in a high-voltage power-on state, it is determined that the operating condition of the high-voltage component does not meet the preset firmware flashing conditions, and the vehicle controller sends a high-voltage power-on command to the battery controller to establish a high-voltage power supply for the high-voltage component.

[0047] S202: If the high-voltage component is in a high-voltage power supply state, send a firmware flashing enable signal to the high-voltage component controller.

[0048] The high-voltage component controller is used to enter the firmware flashing mode according to the firmware flashing enable signal.

[0049] In this embodiment, the firmware flashing enable signal is typically an instruction or notification sent by the vehicle controller to the target high-voltage component controller. It authorizes or instructs the target high-voltage component controller to prepare for the firmware flashing process, i.e., to enter firmware flashing mode. Specifically, the firmware flashing enable signal can be represented by a specific communication message, such as a data frame with a specific identifier in the Controller Area Network (CAN) bus, or a service request sent via a diagnostic protocol.

[0050] Furthermore, firmware flashing mode is typically a specific operating state for high-voltage component controllers. When a high-voltage component controller receives a firmware flashing enable signal, it can switch from its normal operating mode to this mode. After entering firmware flashing mode, the high-voltage component controller can execute an internally preset boot program, receive transmitted firmware data, and perform specific firmware flashing operations based on the received data.

[0051] It should be noted that, in the embodiments of this application, high-voltage components generally refer to high-voltage electrical components in the vehicle's high-voltage system other than the power battery. Correspondingly, the high-voltage component controller and the battery controller are usually two different entities. Of course, those skilled in the art can also use the high-voltage component controller flashing method provided in the embodiments of this application for firmware flashing of the battery controller according to actual needs.

[0052] Specifically, if firmware flashing of the battery controller requires meeting the prerequisite of high-voltage power-on of the corresponding high-voltage component, such as the power battery, the method provided in this application embodiment includes: if a firmware flashing request is received, sending a high-voltage power-on command to the high-voltage component to the battery controller; if the high-voltage component is in a high-voltage power supply state, sending a firmware flashing enable signal to the battery controller. The battery controller is used to supply high-voltage power to the high-voltage component according to the high-voltage power-on command; the battery controller is also used to enter firmware flashing mode according to the firmware flashing enable signal.

[0053] In practical applications, high-voltage components may also experience abnormal conditions such as safety alarms during high-voltage power supply, which may pose safety hazards.

[0054] In some possible implementations, if the high-voltage component is under high-voltage power supply and the operating condition of the high-voltage component meets the preset safety alarm conditions, a high-voltage power-off command for the high-voltage component is sent to the battery controller.

[0055] The battery controller is also used to cut off the high voltage of the high voltage component according to the high voltage power-off command of the high voltage component.

[0056] In this embodiment, the preset safety alarm conditions can be a set of predefined rules for determining whether the high-voltage power supply status of the high-voltage component should be canceled. The preset safety alarm conditions are usually set according to the key parameters of the high-voltage component.

[0057] Understandably, when high-voltage components are under high-voltage power supply, the vehicle controller can obtain the operating status of the high-voltage components. When the vehicle controller determines that the operating status of the high-voltage components meets the preset safety alarm conditions, the vehicle controller can send a high-voltage power-off command to the battery controller.

[0058] Corresponding to the aforementioned high-voltage component power-on command, the high-voltage component power-off command can be a control signal used to instruct the battery controller to cut off the high-voltage power supply to the high-voltage component. Similarly, the high-voltage component power-off command is usually a specific flag bit or status signal predefined in the application layer protocol.

[0059] Furthermore, the battery controller is also used to de-energize the high-voltage component according to the high-voltage component de-energizing command. It can be understood that after receiving the command, the battery controller can control the corresponding relay or contactor to disconnect, thereby cutting off the high-voltage power supply circuit between the power battery and the target high-voltage component, thus achieving high-voltage de-energizing. For example, after receiving the command, the battery controller can sequentially disconnect the main positive relay and the main negative relay corresponding to the high-voltage component, thereby cutting off the high-voltage power supply circuit between the power battery and the target high-voltage component, thus achieving high-voltage de-energizing.

[0060] Of course, those skilled in the art can also set preset safety alarm conditions based on the key parameters of the vehicle's high-voltage system. For example, preset safety alarm conditions may include monitoring whether the insulation resistance of the high-voltage system is less than a preset insulation resistance threshold; when the value is lower than the preset threshold, such as 100Ω / V, a leakage risk can be determined. They may also include whether the high-voltage interlock circuit is open, or whether the high-voltage interlock circuit opening time is greater than a preset circuit-breaking time threshold; when the circuit is detected to be open for more than a preset duration, such as 200 milliseconds, the integrity of the high-voltage circuit can be determined to be compromised. Furthermore, they may include whether the fluctuation range of the DC bus voltage is greater than the bus fluctuation threshold; when the fluctuation range exceeds the normal range, such as ±10%, an unstable factor in the power supply can be determined.

[0061] Furthermore, depending on the specific content of the preset safety alarm conditions, the vehicle controller can take different response actions. For example, in the case of excessively low insulation resistance, the response action could be to record a diagnostic fault code (DTC) and execute a high-voltage power-off; in the case of a high-voltage interlock being disconnected, the response action could be to immediately interrupt subsequent processes; in the case of excessive voltage fluctuations, the response action could be to suspend data transmission and re-perform system status checks. In addition, the vehicle controller can also report corresponding alarm information to diagnostic equipment or a cloud server when a safety mechanism is triggered. Through this dynamic monitoring and response mechanism, potential risks can be detected and addressed in a timely manner during high-voltage power supply, improving the safety of the entire process.

[0062] In practical applications, when the high-voltage component controller is in firmware flashing mode, abnormal situations such as safety alarms may occur, which may lead to firmware flashing failure or even safety hazards.

[0063] See Figure 3 This is a flowchart illustrating another method for flashing firmware for a high-voltage component controller provided in this application embodiment. Figure 3 As shown, in Figure 2 Based on the method shown, the method further includes the following steps.

[0064] S301: If the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, a firmware flashing termination signal is sent to the high-voltage component controller. The high-voltage component controller is also used to exit the firmware flashing mode according to the firmware flashing termination signal.

[0065] In this embodiment, the firmware flashing termination signal can be an instruction sent by the vehicle controller to the high-voltage component controller in firmware flashing mode, used to actively terminate the ongoing firmware flashing process and instruct the target controller to exit this special mode. Specifically, the firmware flashing termination signal can be represented by a specific communication message, such as a data frame with a specific identifier in the CAN bus, or a service request sent through a diagnostic protocol. After receiving the firmware flashing termination signal, the high-voltage component controller can exit the firmware flashing mode.

[0066] Similarly, when the high-voltage component controller is in firmware flashing mode, the vehicle controller can continuously or periodically acquire the operating status of the high-voltage components. When the operating status of the high-voltage component is determined to meet the preset safety alarm conditions, the vehicle controller sends a firmware flashing termination signal to the high-voltage component controller. Upon receiving this signal, the high-voltage component controller exits the firmware flashing mode.

[0067] In this embodiment, the preset safety alarm conditions may further include abnormal situations specific to the firmware flashing process. For example, conditions may include data verification failure during flashing, or communication interruption between the vehicle controller and the high-voltage component controller. The vehicle controller triggers a termination signal based on these conditions, preventing further flashing under unsafe or unstable conditions, thereby protecting the integrity of the high-voltage component controller firmware.

[0068] Furthermore, while sending the firmware flashing termination signal, the vehicle controller can also record the corresponding diagnostic fault code, such as "firmware flashing was aborted due to a safety alarm", and can report this status to the diagnostic equipment or cloud server for subsequent analysis.

[0069] In some possible implementations, if the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, a high-voltage power-off command for the high-voltage component is sent to the battery controller. The battery controller is also used to power off the high-voltage component according to the high-voltage power-off command.

[0070] It is understandable that when the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, the vehicle controller can send a high-voltage component power-off command to the battery controller after sending the firmware flashing termination signal.

[0071] Similar to the aforementioned, the high-voltage component power-off command can be a control signal used to instruct the battery controller to cut off the high-voltage power supply to the high-voltage component. The battery controller is also used to power off the high-voltage component according to the high-voltage component power-off command. It can be understood that after receiving the command, the battery controller can control the corresponding relay or contactor to disconnect, thereby cutting off the high-voltage power supply circuit between the power battery and the target high-voltage component, thus achieving high-voltage power-off.

[0072] In practical applications, after sending a firmware flashing enable signal to the high-voltage component controller, the high-voltage component may unnecessarily maintain a high-voltage state, which may result in wasted power, component wear and tear, or even safety hazards.

[0073] See Figure 4 This is a flowchart illustrating another method for flashing firmware for a high-voltage component controller provided in this application embodiment. Figure 4 As shown, in Figure 2 Based on the method shown, after step S202, the method further includes the following steps.

[0074] S401: Obtain the firmware flashing result of the high-voltage component controller.

[0075] In this embodiment of the application, after receiving the firmware flashing enable signal from the vehicle controller, the high-voltage component controller enters the firmware flashing mode. Further, the high-voltage component controller can determine the firmware flashing result of the high-voltage component controller according to the final state of the firmware flashing, and send the firmware flashing result of the high-voltage component controller to the vehicle controller. The vehicle controller can receive the firmware flashing result of the high-voltage component controller.

[0076] Specifically, the vehicle controller can obtain the firmware flashing results of the high-voltage component controller through various methods. For example, after sending a firmware flashing enable signal, the vehicle controller can periodically send status query requests to the high-voltage component controller to proactively obtain the flashing progress and final result. Alternatively, after completing the firmware flashing operation (whether successful or failed), the high-voltage component controller can proactively send a status report or notification message containing the firmware flashing result to the vehicle controller. Upon receiving the status report or notification message, the vehicle controller obtains the firmware flashing result of the high-voltage component controller.

[0077] Understandably, firmware flashing results for high-voltage component controllers typically include successful and failed flashing. Specifically, a successful flash indicates that the new firmware data has been completely written into the high-voltage component controller's memory and has passed integrity verification; the controller is now ready to run based on the new firmware. A failed flash, on the other hand, indicates that the flashing process failed to complete for some reason, including but not limited to data transmission interruption, write verification errors, or the controller not responding as expected.

[0078] S402: If the firmware flashing result of the high-voltage component controller is successful, a high-voltage power-off command for the high-voltage component is sent to the battery controller.

[0079] The battery controller is also used to cut off the high voltage of the high voltage component according to the high voltage power-off command of the high voltage component. Understandably, when the vehicle controller receives the firmware flashing result from the high-voltage component controller, if the firmware flashing result of the high-voltage component controller is successful, it is not necessary to continue to maintain the high-voltage power supply state of the high-voltage component. The vehicle controller can send a high-voltage power-off command to the battery controller.

[0080] Similar to the aforementioned, the high-voltage component power-off command can be a control signal used to instruct the battery controller to cut off the high-voltage power supply to the high-voltage component. The battery controller is also used to power off the high-voltage component according to the high-voltage component power-off command. It can be understood that after receiving the command, the battery controller can control the corresponding relay or contactor to disconnect, thereby cutting off the high-voltage power supply circuit between the power battery and the target high-voltage component, thus achieving high-voltage power-off.

[0081] S403: If the firmware flashing result of the high-voltage component controller is a flashing failure, then send the firmware flashing enable signal to the high-voltage component controller again.

[0082] Understandably, after the vehicle controller receives the firmware flashing result from the high-voltage component controller, if the firmware flashing result from the high-voltage component controller is a flashing failure, the vehicle controller can send a firmware flashing enable signal to the high-voltage component controller again.

[0083] Similar to the aforementioned process, the high-voltage component controller receives the firmware flashing enable signal from the vehicle controller again. Based on this signal, it prepares for the firmware flashing process again, entering firmware flashing mode. In this way, the high-voltage component controller can again execute its internally preset bootloader, receive the transmitted firmware data, and perform the specific firmware flashing operation based on the received data.

[0084] See Figure 5 This is a flowchart illustrating another method for flashing firmware for a high-voltage component controller provided in this application embodiment. Figure 5 As shown, in Figure 4 Based on the method shown, step S403 specifically includes the following steps.

[0085] S4031: If the firmware flashing result of the high-voltage component controller is a flashing failure, and the number of flashing retries is greater than or equal to the preset retry number threshold, then send a high-voltage component power-off command to the battery controller.

[0086] In this embodiment, the vehicle controller can record the cumulative number of retries due to flashing failure during a single firmware flashing process of the high-voltage component controller, i.e., the flashing retry count. Furthermore, the preset retry count threshold is typically a configurable parameter used to prevent infinite retry loops.

[0087] Understandably, if the vehicle controller determines that the number of retry attempts is greater than or equal to the preset retry threshold, the vehicle controller can conclude that the retry cannot be successfully completed. At this time, in order to avoid unnecessary power consumption, the vehicle controller sends a high-voltage power-off command to the battery controller, so that the high-voltage components return to a safe power-off state.

[0088] S4032: If the firmware flashing result of the high-voltage component controller is a flashing failure, and the number of flashing retries is less than the preset retry threshold, then send the firmware flashing enable signal to the high-voltage component controller again.

[0089] Understandably, when the vehicle controller receives the firmware flashing result from the high-voltage component controller, if the firmware flashing result from the high-voltage component controller is a flashing failure and the number of flashing retries is less than the preset retry threshold, the vehicle controller can send the firmware flashing enable signal to the high-voltage component controller again.

[0090] Similar to the aforementioned process, the high-voltage component controller receives the firmware flashing enable signal from the vehicle controller again. Based on this signal, it prepares for the firmware flashing process again, entering firmware flashing mode. In this way, the high-voltage component controller can again execute its internally preset bootloader, receive the transmitted firmware data, and perform the specific firmware flashing operation based on the received data.

[0091] Corresponding to the above embodiments, this application also provides a vehicle controller, which is configured to perform the method described in any one of the method embodiments.

[0092] For details regarding the embodiments of this application, please refer to the description of the above method embodiments. For the sake of brevity, these details will not be repeated here.

[0093] Corresponding to the above embodiments, this application also provides a vehicle.

[0094] See Figure 6 This is a structural schematic diagram of a vehicle provided in an embodiment of this application, such as... Figure 6As shown, vehicle 600 includes a high-voltage component controller 601, a vehicle controller 602, and a battery controller 603. These components communicate via one or more buses. Those skilled in the art will understand that the vehicle shown in the figures does not constitute a limitation on the embodiments of this application; it can be a bus topology or a star topology, and may include more or fewer components than shown, or combine certain components, or have different component arrangements. The vehicle controller is configured to perform the method described in any one of the method embodiments.

[0095] For details regarding the embodiments of this application, please refer to the description of the above method embodiments. For the sake of brevity, these details will not be repeated here.

[0096] Corresponding to the above embodiments, this application also provides a computer-readable storage medium, wherein the computer-readable storage medium may store a program, and when the program runs, it can control the device where the computer-readable storage medium is located to execute some or all of the steps in the above method embodiments. In specific implementation, the computer-readable storage medium may be a magnetic disk, an optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0097] For details regarding the embodiments of this application, please refer to the description of the above method embodiments. For the sake of brevity, these details will not be repeated here.

[0098] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0099] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0100] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the above-described apparatus, controller, and computer storage medium can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0101] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0102] The above description is merely a specific embodiment of this application. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. The protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for flashing firmware on a high-voltage component controller, characterized in that, Applied to a vehicle controller, the method includes: If a firmware flashing request is received, a high-voltage power-on command for the high-voltage component is sent to the battery controller. The battery controller is used to supply high-voltage power to the high-voltage component according to the high-voltage power-on command. If the high-voltage component is in a high-voltage power supply state, it sends a firmware flashing enable signal to the high-voltage component controller. The high-voltage component controller is used to enter the firmware flashing mode according to the firmware flashing enable signal.

2. The method according to claim 1, characterized in that, Also includes: If the high-voltage component is in a high-voltage power supply state and the operating condition of the high-voltage component meets the preset safety alarm conditions, a high-voltage power-off command for the high-voltage component is sent to the battery controller. The battery controller is also used to power off the high-voltage component according to the high-voltage power-off command.

3. The method according to claim 1, characterized in that, Also includes: If the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, a firmware flashing termination signal is sent to the high-voltage component controller. The high-voltage component controller is also used to exit the firmware flashing mode according to the firmware flashing termination signal.

4. The method according to claim 3, characterized in that, Also includes: If the high-voltage component controller is in firmware flashing mode and the operating status of the high-voltage component meets the preset safety alarm conditions, then a high-voltage power-off command for the high-voltage component is sent to the battery controller. The battery controller is also used to power off the high-voltage component according to the high-voltage power-off command.

5. The method according to claim 1, characterized in that, After sending a firmware flashing enable signal to the high-voltage component controller, the process also includes: Obtain the firmware flashing result of the high-voltage component controller; If the firmware flashing result of the high-voltage component controller is successful, a high-voltage power-down command is sent to the battery controller. The battery controller is also used to power down the high-voltage component according to the high-voltage power-down command; and / or If the firmware flashing result of the high-voltage component controller is a flashing failure, then the firmware flashing enable signal is sent to the high-voltage component controller again.

6. The method according to claim 5, characterized in that, If the firmware flashing result of the high-voltage component controller fails, then sending the firmware flashing enable signal to the high-voltage component controller again includes: If the firmware flashing result of the high-voltage component controller is a flashing failure, and the number of flashing retries is greater than or equal to a preset retry threshold, then a high-voltage power-down command for the high-voltage component is sent to the battery controller; and / or If the firmware flashing result of the high-voltage component controller is a flashing failure, and the number of flashing retries is less than the preset retry threshold, then the firmware flashing enable signal is sent to the high-voltage component controller again.

7. The method according to claim 1, characterized in that, If a firmware flashing request is received, a high-voltage power-on command for the high-voltage components is sent to the battery controller, including: If a firmware flashing request is received, the operating status of the high-voltage components is obtained. If the operating condition of the high-voltage component does not meet the preset firmware flashing conditions, a high-voltage power-on command for the high-voltage component is sent to the battery controller.

8. A vehicle controller, characterized in that, The vehicle controller is configured to perform the method of any one of claims 1 to 7.

9. A vehicle, characterized in that, include: The vehicle controller, the high-voltage component controller, and the battery controller are configured to perform the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1-7.

Images