Firmware upgrading method of control system, control system and computer storage medium

By adopting a layered control module and status marking distinction mechanism in the elevator control system, batch firmware upgrades of multiple control modules are achieved, solving the problems of cumbersome upgrade process and high hardware requirements in the existing technology, and improving the upgrade efficiency and flexibility.

CN119271248APending Publication Date: 2025-01-07苏州安驰控制系统有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310810297.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-07-04
Publication Date
2025-01-07

AI Technical Summary

Technical Problem

The firmware upgrade process of the existing elevator control system requires technical service personnel to manually remove the shell, which is cumbersome and inefficient. The interfaces of different control modules are different, which increases technical difficulty and hardware requirements.

Method used

The control module is adopted with a layered setting to achieve firmware upgrade through bus connection, and the status marks are used to distinguish between the self-upgrade and the next layer of upgrade status, share the data transmission link, reduce the interface connection and burning steps in turn, and improve the upgrade efficiency.

Benefits of technology

It realizes automatic batch upgrade of multiple control modules, reduces the requirements for hardware and data processing capabilities, and improves upgrade efficiency and flexibility.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119271248A_ABST
    Figure CN119271248A_ABST
Patent Text Reader

Abstract

The invention provides a firmware upgrading method of a control system, the control system and a computer storage medium. The control system comprises at least two layers of control modules which are arranged in a layered mode, at least one of the control modules on the upper layer is connected with the control module on the lower layer through a bus, the firmware upgrading method is used for the control module, and the firmware upgrading method comprises the steps that a boot loader is executed, and a state mark is obtained; responding to the state mark as the first mark, and working in a firmware upgrading state; and responding to the state mark as the second mark, and working in a next-layer upgrading working state. By means of the mode, batch firmware upgrading can be achieved for the control system with the multiple control modules, upgrading efficiency can be improved, and the requirements for hardware and data processing capacity of equipment are lowered.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data control technology, and in particular to a firmware upgrade method for a control system, a control system, and a computer storage medium. Background Art

[0002] In modern society, elevators have become indispensable transportation equipment and are widely used in various scenarios. The elevator control system can adjust the various operating parameters of the elevator to monitor the overall operation of the elevator. In addition to the main board, i.e. the elevator controller and the host computer, the elevator control system usually also includes multiple other control modules such as the drive controller, door machine controller, car top controller, and car controller. These control modules are often distributed in different places. During the maintenance of the elevator, it is often necessary to upgrade different control modules.

[0003] At present, the upgrade plan for the elevator control system usually requires technical service personnel to carry mobile burning equipment to dismantle the outer shell of the elevator control room, and burn and upgrade each control module in turn through data transmission equipment. Since the interfaces of multiple control modules are different, this upgrade method requires a high level of technical skills from the technical service personnel, and the operation is cumbersome and the upgrade efficiency is low. Summary of the invention

[0004] The present application provides a control system firmware upgrade method, a control system and a computer storage medium to implement batch firmware upgrades for a control system containing multiple control modules, and can improve upgrade efficiency and reduce hardware requirements and data processing capability requirements for equipment.

[0005] To solve the above technical problems, a technical solution adopted in the present application is: to provide a firmware upgrade method for a control system, the control system includes at least two layers of control modules arranged in layers, at least one of the control modules in the upper layer is connected to the control modules in the lower layer through a bus, the firmware upgrade method is used for the control module, and the firmware upgrade method includes: executing a boot loader to obtain a status mark; in response to the status mark being a first mark, working in a firmware upgrade state; in response to the status mark being a second mark, working in a next-layer upgrade working state.

[0006] Among them, working in the next-layer upgrade working state includes: obtaining upgrade data, parsing the upgrade data, obtaining the upgrade package and target address information; and transmitting the upgrade data to the next-layer control module based on the target address information.

[0007] Among them, working in the next-layer upgrade working state also includes: updating the state mark to a third mark; and entering the application loader in response to the completion of the upgrade of the next-layer control module.

[0008] Among them, working in the firmware upgrade state includes: obtaining upgrade data, and performing firmware upgrade based on the upgrade data; after the firmware upgrade is completed, updating the state mark to the fourth mark, and entering the application loader.

[0009] The firmware upgrade method further includes: in response to the status mark being the third mark or the fourth mark, entering the application loader.

[0010] The firmware upgrade method further includes: after entering the application loader, in response to the status mark being the third mark, determining that the current startup is a normal device restart.

[0011] The firmware upgrade method further includes: after entering the application loader, in response to the status mark being the fourth mark, determining that the firmware upgrade is successful; and updating the status mark to the third mark.

[0012] The firmware upgrade method further includes: during the execution of the application loader, in response to the upgrade instruction, updating the status mark to the first mark, executing the boot loader and performing the firmware upgrade.

[0013] To solve the above technical problems, another technical solution adopted in the present application is: to provide a control system, which includes: at least two layers of control modules arranged in layers, at least one of the control modules in the upper layer is connected to the control module in the lower layer through a bus; wherein the control module adopts the above firmware upgrade method to implement firmware upgrade.

[0014] The control system further comprises: a host computer connected to at least one of the upper layer control modules via a bus to issue status marks and upgrade data.

[0015] The control system further includes: a mobile terminal, which is wirelessly connected to at least one of the upper-layer control modules to issue status marks and upgrade data.

[0016] To solve the above technical problem, another technical solution adopted by the present application is to provide a computer storage medium having program instructions stored thereon, which are executed by a processor to implement the above firmware upgrade method.

[0017] The beneficial effects of the present application are as follows: the control system provided by the present application comprises at least two layers of control modules arranged in layers, at least one of the control modules in the upper layer is connected to the control modules in the lower layer through a bus, and the control module works in its own firmware upgrade state in response to the first mark and in the working state of the next layer upgrade in response to the second mark by obtaining the status mark, so that batch automatic upgrade of multiple control modules can be realized, thereby enabling batch firmware upgrade of the control system containing multiple control modules connected by the bus; and the present application can distinguish between the current control module self-upgrade and the next layer control module upgrade through the status mark, so that the upgrade data required for the current control module self-upgrade and the next layer control module upgrade can share the same data transmission link, thereby reducing the operation steps of sequentially connecting to different interfaces of multiple control modules and then sequentially burning and upgrading, thereby improving the upgrade efficiency of multiple firmware upgrades of multiple layers of different control modules, and reducing the hardware requirements for the device; and the present application can selectively distribute the upgrade data packets required for upgrading a specific control module according to the status mark, and selectively start the firmware upgrade program for the control module that needs to be upgraded, thereby reducing the requirements for the data processing capabilities of the burning device and the device to be burned. Therefore, the present application can implement batch firmware upgrades for a control system containing multiple control modules, and can improve upgrade efficiency and reduce hardware requirements and data processing capability requirements for the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0019] Figure 1 It is a flowchart of an embodiment of a firmware upgrade method of a control system of the present application;

[0020] Figure 2 yes Figure 1 A specific flow chart of step S12 in the embodiment;

[0021] Figure 3 yes Figure 1 A specific flow chart of step S13 in the embodiment;

[0022] Figure 4 It is a flowchart of another embodiment of the firmware upgrade method of the control system of the present application;

[0023] Figure 5 It is a flowchart of another embodiment of the firmware upgrade method of the control system of the present application;

[0024] Figure 6 It is a flowchart of another embodiment of the firmware upgrade method of the control system of the present application;

[0025] Figure 7 This is a structural example diagram of an embodiment of the control system of the present application;

[0026] Figure 8 It is a structural diagram of an embodiment of the computer storage medium of the present application. DETAILED DESCRIPTION

[0027] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0028] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back, etc.), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0029] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0030] This application first proposes a firmware upgrade method for a control system, such as Figure 1 As shown, Figure 1 The flowchart of the firmware upgrade method of the control system of the present application is a flowchart of an embodiment of the firmware upgrade method of the control system of the present application. The control system of the present embodiment includes at least two layers of control modules arranged in layers, at least one of the control modules of the upper layer is connected to the control module of the lower layer through a bus, and the firmware upgrade method is used for the control module. The firmware upgrade method of the present embodiment specifically includes the following steps:

[0031] Step S11: Execute the boot loader and obtain the status mark.

[0032] In a specific application scenario, after the control system is started, the control module in the control system of this embodiment starts to execute a bootloader program to obtain a status mark of the control module itself.

[0033] Among them, the status mark is used to mark the working state of the control module. For example, the status mark can specifically include a first mark, a second mark, a third mark, and a fourth mark. Among them, the first mark is used to indicate that the control module currently needs to perform a firmware upgrade, the second mark is used to indicate that the control module needs to enter the next level of upgrade working state, the third mark is used to indicate that the control module has completed a normal restart of its own device instead of a firmware upgrade, and the fourth mark is used to indicate that the control module has successfully upgraded its own firmware. For example, the first mark can be state 1, the second mark can be state 3, the third mark can be state 0, and the fourth mark can be state 2.

[0034] In a specific application scenario, the control system of this embodiment is the control system of an elevator. The control modules of each floor in this embodiment can each include a single or multiple (multiple including two or more) control modules, and the control modules in this embodiment can belong to sub-modules with different control functions in the control system of the elevator, such as a drive control module, a door machine control module, an external call control module, etc.

[0035] Step S12: In response to the state mark being the first mark, operating in the firmware upgrade state.

[0036] In a specific application scenario, when the control module obtains that the status mark of the module itself is the first mark, it enters its own firmware upgrade state.

[0037] The first mark may be state 1. In response to state 1, the current control module operates in a firmware upgrade state.

[0038] Optionally, this embodiment can be implemented by Figure 2 The method shown implements step S12, Figure 2 The method shown specifically includes step S21 and step S22.

[0039] Step S21: in response to the state flag being the first flag, acquiring upgrade data, and performing firmware upgrade based on the upgrade data.

[0040] For example, the first mark may be state 1. If the state mark of the control module is state 1, the control module obtains upgrade data and performs firmware upgrade based on the upgrade data.

[0041] Step S22: After the firmware upgrade is completed, the status mark is updated to the fourth mark and the application loading program is entered.

[0042] For example, if the firmware upgrade of the control module itself is completed, the fourth mark may be state 2, the state mark of the control module itself is updated to state 2, and the application loader, ie, the APP program, is entered.

[0043] The beneficial effect of the above method is that the firmware is upgraded according to the acquired upgrade data, and the status mark is modified to the fourth mark after the upgrade is completed, which can be distinguished from the control module status before the firmware upgrade, and is helpful to monitor and manage the working status of the specific control module; after the upgrade is completed, the application loader is automatically entered, which saves operating steps and facilitates operation.

[0044] Optionally, step S12 may also be implemented in other ways, such as directly entering the application loader after the firmware upgrade is completed.

[0045] Step S13: In response to the state mark being the second mark, working in the next level upgrade working state.

[0046] For example, the second mark may be state 3. If the state mark of the control module is state 3, the current control module works in the next-level upgraded working state.

[0047] Optionally, this embodiment can be implemented by Figure 3 The method shown implements step S13, Figure 3 The method shown specifically includes step S31 and step S32.

[0048] Step S31: in response to the status mark being the second mark, obtaining upgrade data, parsing the upgrade data, and obtaining an upgrade package and target address information.

[0049] Specifically, in an application scenario, the control module first obtains the upgrade data, and parses the upgrade data to obtain the upgrade package and the target address information of the upgrade package, wherein the target address information may be a device address or other data identifying the address information. The target address information is the address information of one or more control modules to be upgraded located in the lower layer of the current control module, and these control modules to be upgraded establish a data connection with the current control module through a bus between one or more layers.

[0050] For example, the second mark may be state 3. If the state mark of the control module is state 3, the current control module obtains the upgrade data, parses the upgrade data, and obtains the upgrade package and the target address information.

[0051] Step S32: passing the upgrade data to the next layer control module based on the target address information.

[0052] Specifically, in an application scenario, the control module obtains the target address information of the lower-level control module to be upgraded based on the upgrade data, and can pass the upgrade data to the next-level control module according to the target address information. Based on the firmware upgrade method of this embodiment, the upgrade data can be passed layer by layer to the control module to be upgraded through the current control module. For example, in Figure 7 In the application scenario shown, when there is a lower-level control module 52 connected to the current control module 52 via a bus, the current control module 52 can obtain upgrade data based on the second status mark, and parse the upgrade data to obtain the target address information of the lower-level control module 52 to be upgraded. Based on this target address information, the current control module 52 can pass the acquired upgrade data to the next-level control module. Furthermore, since the firmware upgrade method of this embodiment can be run in each control module 52, the upgrade data can be passed layer by layer to the target address information, that is, to the control module to be upgraded.

[0053] Through steps S31 and S32, the control module can automatically identify the target address information of the control module that needs to be upgraded when working in the next-level upgrade working state, and can pass the upgrade data to the next-level control module through the bus; further, when the control module to be upgraded is not in the next level of the current control module, but in the next level of the next-level control module, based on the firmware upgrade method of this embodiment, the next-level control module can further pass the upgrade data downward to pass the upgrade data to the control module to be upgraded.

[0054] In one application scenario, only one control module in each layer of control modules serves as a control module with a gateway function to communicate with the upper and lower layer control modules, and the upper layer control module can directly pass the upgrade data to this only control module; in another application scenario, if a certain layer of control modules has multiple control modules with a gateway function, the upgrade data includes not only the target address information, but also the intermediate address information of the middle layer control module, so that the upper layer control module can send the upgrade data to the middle layer control module based on the intermediate address information.

[0055] Optionally, Figure 3 The method shown may further include step S33 and step S34, the specific contents of which are:

[0056] Step S33: Update the status flag to the third flag.

[0057] Specifically, in one application scenario, the control module can update its own status mark to the third mark while working in the next-level upgrade working state. This can distinguish its own upgrade state from the next-level upgrade state, and can also distinguish its own upgrade state from its own restart state, so as to more accurately identify the current state of the current control module.

[0058] For example, the third mark may be state 0, and the control module may update its own state mark to state 0 while working in the next-level upgrade working state, to indicate that the current control module has completed a normal restart.

[0059] Optionally, the control module may execute step S33 after completing step S32, that is, completing the transmission of the upgrade data; the control module may also execute step S33 after the upgrade of the next layer of control modules is completed, and there is no specific limitation.

[0060] Optionally, after completing the upgrade, the lower-layer control module may transmit the upgrade success information to the upper-layer control module.

[0061] Step S34: In response to the completion of the upgrade of the next-layer control module, enter the application loading program.

[0062] Specifically, in an application scenario, after the next-layer control module is upgraded, it can enter its own application loading program.

[0063] Optionally, the current control module may determine that the upgrade of the next-layer control module is completed by receiving a message that the next-layer control module is successfully upgraded.

[0064] Optionally, the current control module may continue to pass upward the received information that the next-layer control module has been successfully upgraded.

[0065] Optionally, since each control module adopts the firmware upgrade method of this embodiment, the information of successful upgrade of the next-layer control module can be transmitted layer by layer to reach the technician's burning device, such as a host computer or a mobile terminal.

[0066] Through steps S33 and S34, when the current control module is working in the next-level upgrade state, the status mark can be changed to distinguish its own upgrade from the next-level upgrade, and the application loader of the current control module can continue to enter without being restricted by the progress of the next-level upgrade. Therefore, this setting method can enable other control modules that do not need to be upgraded to enter the application loader normally to run corresponding business instructions when some modules of the control system are in the upgrade state, thereby improving the flexibility and operational convenience of the control system.

[0067] The beneficial effect of the firmware upgrade method of this embodiment is that by obtaining the status mark, responding to the first mark to work in the state of the own firmware upgrade, responding to the second mark to work in the state of the next level upgrade, it is possible to realize batch automatic upgrade of multiple control modules, so that the control system of multiple control modules connected by the bus can realize batch firmware upgrade; and this embodiment can distinguish between the current control module itself upgrade and the next level control module upgrade through the status mark, so that the upgrade data required for the current control module itself upgrade and the next level control module upgrade can share the same data transmission link, so that the operation steps of sequentially connecting with different interfaces of multiple control modules and then sequentially burning and upgrading can be reduced, so that the upgrade efficiency of multiple firmware upgrades of multiple layers of different control modules can be improved, and the hardware requirements for the device can be reduced; and this embodiment can selectively distribute the upgrade data packets required for upgrading the specific control module according to the status mark, and selectively start the firmware upgrade program for the control module that needs to be upgraded, reducing the requirements for the data processing capabilities of the burning device and the device to be burned. Therefore, this embodiment can realize batch firmware upgrades for the control system of multiple control modules, and can improve the upgrade efficiency, and reduce the hardware requirements and data processing capabilities of the device.

[0068] This application further proposes another method for upgrading the firmware of a control system, such as Figure 4 As shown, Figure 4 It is a flowchart of another embodiment of the firmware upgrade method of the control system of the present application. The control system of the present embodiment includes at least two layers of control modules arranged in layers, at least one of the control modules in the upper layer is connected to the control module in the lower layer via a bus, and the firmware upgrade method is used for the control module. The firmware upgrade method of the present embodiment specifically includes the following steps:

[0069] Step S41: Execute the boot loader and obtain the status mark.

[0070] The specific implementation manner can refer to the above embodiments.

[0071] Step S42: In response to the state mark being the first mark, operating in the firmware upgrade state.

[0072] The specific implementation manner can refer to the above embodiments.

[0073] Step S43: In response to the state mark being the second mark, working in the next level upgrade working state.

[0074] The specific implementation manner can refer to the above embodiments.

[0075] Step S44: In response to the status mark being the third mark or the fourth mark, entering the application loading program.

[0076] In one application scenario, when the status mark of the control module itself is the third mark or the fourth mark, it is considered that the current control module and the lower-level control modules associated with the current control module do not need to perform firmware upgrades, and the current control module can directly enter the application loader; further, optionally, in this state the current control module may not need to obtain upgrade data.

[0077] For example, the third mark may be state 0 and the fourth mark may be state 2. In response to the state mark being state 0 or state 2, the control module enters the application loader.

[0078] The setting of step S44 helps the control module to distinguish whether it and the lower control module need to be upgraded, helps upgrade data to be selectively issued and received, can reduce the transmission of useless data, and reduce the requirements on the data processing capabilities of the burning device and the device to be burned.

[0079] This application further proposes another method for upgrading the firmware of a control system, such as Figure 5 As shown, Figure 5 1 is a flow chart of another embodiment of the firmware upgrade method of the control system of the present application. The firmware upgrade method of this embodiment specifically includes the following steps:

[0080] Step S51: Execute the boot loader and obtain the status mark.

[0081] The specific implementation manner can refer to the above embodiments.

[0082] Step S52: in response to the state flag being the first flag, acquiring upgrade data, and performing firmware upgrade based on the upgrade data.

[0083] The specific implementation of step S52 may refer to the above step S21.

[0084] Step S53: After the firmware upgrade is completed, the status mark is updated to the fourth mark and the application loading program is entered.

[0085] The specific implementation of step S53 may refer to the above step S22.

[0086] Step S54: in response to the status mark being the second mark, obtaining upgrade data, parsing the upgrade data, and obtaining the upgrade package and target address information.

[0087] The specific implementation of step S54 may refer to the above step S31.

[0088] Step S55: passing the upgrade data to the next layer control module based on the target address information.

[0089] The specific implementation of step S55 may refer to the above step S32.

[0090] Step S56: Update the status flag to the third flag.

[0091] The specific implementation of step S56 may refer to the above step S33.

[0092] Step S57: In response to the completion of the upgrade of the next-layer control module, enter the application loading program.

[0093] The specific implementation of step S57 may refer to the above step S34.

[0094] Step S58: After entering the application loader, in response to the status mark being the third mark, it is determined that this startup is a normal device restart.

[0095] In one application scenario, after the control module enters the application loader, it is necessary to judge the status mark. If the status mark is the third mark, it is determined that this startup is a normal restart of the current control module and does not involve the firmware upgrade of the current control module itself.

[0096] For example, the third mark may be state 0. After entering the application loader, the control module responds to state 0 and determines that the current startup is a normal device restart.

[0097] Optionally, after determining that the current startup is a normal restart of the current control module, the current control module may send a message of a normal restart success to the host computer or other connected devices.

[0098] The setting of step S58 helps to distinguish the firmware upgrade of the current control module itself from the normal restart of the current control module itself, especially in the application scenario where the lower-level control module of the current control module needs to be upgraded, but the current control module does not need to be upgraded. It is more helpful to accurately identify based on the status marking method that the current control module has not undergone a firmware upgrade but has only undergone a normal restart, thereby improving the judgment accuracy of the firmware upgrade method when monitoring the upgrade status of each control module.

[0099] Optionally, this embodiment may further include step S59 and step S510, the specific contents of which are:

[0100] Step S59: After entering the application loader, in response to the status mark being the fourth mark, it is determined that the firmware upgrade is successful.

[0101] Specifically, in one application scenario, after entering the application loader, it is necessary to judge the status mark. When the status mark is the fourth mark, it is determined that the firmware upgrade of the current control module is successful. This setting method can use the status mark to identify the situation of entering the application loader after the firmware upgrade is successful, so as to more accurately identify whether the current control module has undergone a firmware upgrade.

[0102] Furthermore, optionally, after determining that the firmware upgrade is successful, the current control module may send a message reminder of the successful upgrade of the current control module to the host computer or other connected devices, so that the technicians can learn the upgrade status of each control module.

[0103] For example, the fourth mark may be state 2. After entering the application loader, the control module determines that the firmware upgrade is successful in response to state 2.

[0104] Step S510: Update the status flag to a third flag.

[0105] For example, the third flag may be state 0, and the state flag is changed to state 0.

[0106] Specifically, in one application scenario, after the firmware upgrade is determined to be successful based on step S59, the status mark is updated to the third mark. Because the current control module has been upgraded, changing to the third mark can improve the accuracy of the current state judgment of the current control module and provide convenience for subsequent control.

[0107] In summary, the settings of step S59 and step S510 can identify the situation of entering the application loader after the firmware upgrade is successful through the status mark, so as to more accurately identify whether the current control module has undergone a firmware upgrade; and changing to the third mark helps to improve the accuracy of the current state judgment of the current control module, providing convenience for subsequent control.

[0108] Similar improvements can be made to the other embodiments above.

[0109] This application further proposes another method for upgrading the firmware of a control system, such as Figure 6 As shown, Figure 6 This is a flow chart of another embodiment of the firmware upgrade method of the control system of the present application. The firmware upgrade method specifically includes the following steps:

[0110] Step S61: Execute the boot loader and obtain the status mark.

[0111] The specific implementation manner can refer to the above embodiments.

[0112] Step S62: In response to the state mark being the first mark, operating in the firmware upgrade state.

[0113] The specific implementation manner can refer to the above embodiments.

[0114] Step S63: In response to the state mark being the second mark, working in the next level upgrade working state.

[0115] The specific implementation manner can refer to the above embodiments.

[0116] According to the analysis, the control module will enter the application loader when it is working in the firmware upgrade state and the next level upgrade state.

[0117] Step S64: During the execution of the application loader, in response to the upgrade instruction, the state mark is updated to the first mark, and the boot loader and the firmware upgrade are executed.

[0118] Specifically, in an application scenario, when the current control module is in the process of executing the application loader, if it receives an operation instruction to upgrade itself, it updates its own status mark to the first mark, executes its own boot loader, and starts executing related programs for firmware upgrade.

[0119] The setting of step S64 can still accept the operation instruction of firmware upgrade sent by the technician or the corresponding program when the current control module is in the application loader, and execute the boot loader based on the operation instruction to execute the related program of firmware upgrade. Therefore, the startup conditions of the firmware upgrade program can be increased to adapt to different application scenarios and improve the convenience of the firmware upgrade method.

[0120] Similar improvements can be made to the other embodiments above.

[0121] The present application further provides a control system, such as Figure 7 As shown, Figure 7 1 is a structural example diagram of an embodiment of the control system of the present application. The control system comprises: at least two layers of control modules 52 arranged in layers, at least one of the upper layer of control modules 52 is connected to the lower layer of control modules 52 via a bus 53; wherein the control modules 52 implement firmware upgrade using the above firmware upgrade method.

[0122] It should be noted that, in this embodiment, the number of control modules 52 at each layer is not limited.

[0123] The control system of this embodiment connects multiple layers of control modules together through a multi-bus. When data transmission or batch upgrade of different control modules is required, it is only necessary to establish a data connection with the control module of the first layer to realize data transmission and control of the entire control system. Since the data interfaces of different control modules are different, this design method can not only reduce the technical difficulty and operation complexity when technicians need to control and maintain multiple different control modules, but also reduce the hardware requirements for the host computer or other operating terminals, thereby realizing batch upgrades of the firmware of the control system and improving the upgrade efficiency.

[0124] Optionally, in this embodiment, the upper layer control module 52 may have multiple control modules 52 connected to the lower layer control module 52. In an elevator control system application scenario, the first layer control module 52 may be the main control board of the elevator control system, the second layer may be the main control module of each submodule of the elevator control system, such as the drive control module, the door machine control module, the outbound call control module, etc., the third layer control module 52 may be the control module 52 under each submodule, and so on. In other embodiments, the function of each layer control module is not limited.

[0125] Optionally, for each control module 52 connected to a next-layer control module 52 , there is no limit on the number of next-layer control modules 52 that can be connected.

[0126] Optionally, each control module 52 connected to a control module 52 of a next layer may be a control module 52 with a gateway function, which can be used to implement a data communication link between layers.

[0127] Optionally, the number of control modules 52 of the entire control system is less than 255.

[0128] Optionally, the data connection between the control modules 52 at each layer can be achieved through RS485 or CAN field bus.

[0129] In this embodiment, the specific number of layers included in the control system is not limited.

[0130] Optionally, the control system further comprises: a host computer 50 connected to at least one of the upper layer control modules 52 via a bus 53 to issue status marks and upgrade data.

[0131] The technician can connect to the top-level control module 52 through the host computer 50, thereby sending status marks and upgrade data to the entire control system. In an application scenario of an elevator control system, the host computer 50 can establish a data connection with the first-level control module 52, that is, the main control board of the elevator control system, so as to send status marks and upgrade data to the entire control system. This method can improve the convenience of transmitting data to different control modules 52, and can also improve the upgrade efficiency of batch upgrades of the control modules 52 of the entire control system.

[0132] In other embodiments, the status mark of each control module may also be obtained in other ways.

[0133] Optionally, the technician may use burning software in the host computer 50 .

[0134] Optionally, the burning software stores the version information of the hardware and software of the current device, and determines whether the control module 52 to be upgraded meets the requirements through the version information. If it does not meet the requirements, the upgrade is rejected and the error information is reported through the host computer 50.

[0135] Optionally, the host computer 50 can establish a data connection with the first-layer control module 52 through a universal synchronous asynchronous receiver and transmitter (USART), an upgraded version of CAN (Flexible Data-Rate CAN, FDCAN), RS232, RS485, CAN, Bluetooth, wired LAN or wireless LAN, etc. The burning software on the host computer 50 can obtain the address and device information of the control module 52 on all buses, and upgrade each control module 52 of the entire elevator control system through different buses 53.

[0136] The present application further provides a control system, which includes: at least two layers of control modules arranged in layers, at least one of the upper layer of control modules is connected to the lower layer of control modules 52 via a bus; wherein the control module adopts the above-mentioned firmware upgrade method to implement firmware upgrade.

[0137] The control system also includes: a mobile terminal, which is wirelessly connected to at least one of the upper-layer control modules to issue status marks and upgrade data.

[0138] Technicians can connect to the top-level control module through a mobile terminal, thereby sending status marks and upgrade data to the entire control system. In an elevator control system application scenario, a mobile terminal can establish a data connection with the first-level control module, that is, the main control board of the elevator control system, to send status marks and upgrade data to the entire control system. This method can improve the convenience of transmitting data to different control modules and improve the upgrade efficiency of batch upgrades of control modules of the entire control system.

[0139] Optionally, the technician can use the burning software in the mobile terminal.

[0140] Optionally, the burning software stores the version information of the hardware and software of the current device, and determines whether the control module to be upgraded meets the requirements based on the version information. If it does not meet the requirements, the upgrade is rejected and an error message is reported through the mobile terminal.

[0141] Optionally, the mobile terminal can establish a data connection with the first-layer control module through a universal synchronous asynchronous receiver and transmitter (USART), an upgraded version of CAN (Flexible Data-Rate CAN, FDCAN), RS232, RS485, CAN, Bluetooth, wired LAN or wireless LAN, etc. The burning software on the mobile terminal can obtain the address and device information of the control modules on all buses, and upgrade each control module of the entire elevator control system through different buses 53.

[0142] Compared with the prior art, the mobile terminal of this embodiment only needs to send the status mark and upgrade data to the control module with gateway function in the first layer, and does not need to send them to each control module that needs firmware upgrade.

[0143] The present application further proposes a computer storage medium. Figure 8 As shown, Figure 8 The computer storage medium 60 stores program instructions 61, which are executed by a processor to implement the above firmware upgrade method.

[0144] Among them, the program instructions 61 can form a program file and be stored in the above-mentioned storage medium in the form of a software product, so that an electronic device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) executes all or part of the steps of the various implementation methods of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes, or terminal devices such as computers, servers, mobile phones, tablets, etc.

[0145] The computer storage medium 60 of this embodiment can be, but is not limited to, a USB flash drive, an SD card, a PD optical drive, a mobile hard disk, a large-capacity floppy drive, a flash memory, a multimedia memory card, a server, etc.

[0146] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer storage medium. A processor of an electronic device reads the computer instructions from the computer storage medium, and the processor executes the computer instructions, so that the electronic device performs the steps in the above-mentioned method embodiments.

[0147] In addition, if the above functions are implemented in the form of software functions and sold or used as independent products, they can be stored in a storage medium readable by a mobile terminal, that is, the present application also provides a storage device storing program data, the program data can be executed to implement the method of the above embodiment, and the storage device can be, for example, a USB flash drive, an optical disk, a server, etc. In other words, the present application can be embodied in the form of a software product, which includes a number of instructions for enabling a smart terminal to execute all or part of the steps of the method described in each embodiment.

[0148] In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, mechanisms, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, mechanisms, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0149] Different from the prior art, the firmware upgrade method of the control system provided by the present application can realize batch upgrade of multiple layers of different control modules by obtaining a status mark, working in its own firmware upgrade state in response to a first mark, and working in the working state of the next layer upgrade in response to a second mark, thereby realizing batch firmware upgrade of control systems with multiple layers of different control modules containing multiple buses; and the present application can distinguish between the upgrade of the current control module itself and the upgrade of the next layer of control modules through the status mark, so that the upgrade data required for the upgrade of the current control module itself and the upgrade of the next layer of control modules share the same data transmission link, thereby reducing the operation steps of sequentially connecting to different interfaces of multiple control modules and then sequentially burning and upgrading, thereby improving the upgrade efficiency of multiple firmware upgrades of multiple layers of different control modules, and reducing the hardware requirements for the device; and the present application can selectively distribute the upgrade data packets required for upgrading a specific control module according to the status mark, and selectively start the firmware upgrade program for the control module that needs to be upgraded, thereby reducing the requirements for the data processing capabilities of the burning device and the device to be burned. Therefore, the present application can implement batch firmware upgrades for control systems with multiple layers of different control modules containing multiple buses, and can improve upgrade efficiency and reduce hardware requirements and data processing capability requirements for the device.

[0150] The above are only implementation methods of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for upgrading the firmware of a control system, characterized in that: The control system includes at least two layers of control modules arranged in layers, at least one of the upper layer of control modules is connected to the lower layer of control modules via a bus, and the firmware upgrade method is used for the control modules, and the firmware upgrade method includes: Execute the boot loader and get the status flag; In response to the state mark being the first mark, operating in a firmware upgrade state; In response to the state mark being the second mark, working in the next level upgrade working state.

2. The firmware upgrade method according to claim 1, characterized in that: The work is in the next level upgrade working state, including: Obtaining upgrade data, and parsing the upgrade data to obtain upgrade packages and target address information; The upgrade data is transmitted to the control module of the next layer based on the target address information.

3. The firmware upgrade method according to claim 2, characterized in that: The work is in the next level upgrade work state, and also includes: Updating the status flag to a third flag; In response to the completion of the upgrade of the control module of the next layer, the application loading program is entered.

4. The firmware upgrade method according to claim 1, characterized in that: The working in the firmware upgrade state includes: Acquire upgrade data, and perform firmware upgrade based on the upgrade data; After the firmware upgrade is completed, the status mark is updated to the fourth mark and the application loader is entered.

5. The firmware upgrade method according to claim 1, characterized in that: The firmware upgrade method further includes: In response to the state flag being the third flag or the fourth flag, entering an application loader program.

6. The firmware upgrade method according to any one of claims 3 to 5, characterized in that: The firmware upgrade method further includes: After entering the application loader, in response to the state mark being the third mark, it is determined that this startup is a normal device restart.

7. The firmware upgrade method according to any one of claims 3 to 5, characterized in that: The firmware upgrade method further includes: After entering the application loader, in response to the state mark being the fourth mark, determining that the firmware upgrade is successful; The state flag is updated to a third flag.

8. The firmware upgrade method according to claim 1, characterized in that: The firmware upgrade method further includes: During the execution of the application loader, in response to an upgrade instruction, the state mark is updated to a first mark, and the boot loader is executed and the firmware upgrade is performed.

9. A control system, characterized in that: The control system comprises: at least two layers of control modules arranged in layers, at least one of the control modules in the upper layer is connected to the control modules in the lower layer via a bus; wherein the control modules implement firmware upgrade using the firmware upgrade method according to any one of claims 1 to 8.

10. The control system according to claim 9, characterized in that: The control system further comprises: The upper computer is connected to at least one of the upper layer control modules via a bus to issue the status mark and upgrade data.

11. The control system according to claim 9, characterized in that: The control system further comprises: The mobile terminal is wirelessly connected to at least one of the upper layer control modules to send the status mark and upgrade data.

12. A computer storage medium, characterized in that: The computer storage medium stores program instructions, and the program instructions are executed by a processor to implement the firmware upgrade method according to any one of claims 1 to 8.