Touch device, touch MCU upgrading method and computer readable storage medium

Abstract

The invention provides touch equipment, an upgrading method of a touch MCU (Microprogrammed Control Unit) and a computer readable storage medium, and belongs to the technical field of display. The touch control device comprises the touch control MCU and a main control module which are electrically connected with each other. The upgrading method of the touch MCU comprises the steps that a main control module determines a target upgrading file according to configuration parameters of the touch MCU; the configuration parameters of the touch MCU meet the pairing parameters of the target upgrading file; and the main control module writes the target upgrading file into the touch MCU, so that the touch MCU is upgraded according to the target upgrading file. According to the upgrading method of the touch MCU, the convenience and safety of upgrading of the touch MCU can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of display technology, and in particular to a touch device, a touch MCU upgrade method, and a computer-readable storage medium. Background Art

[0002] Many touch-screen all-in-one computers run the Android system. These devices have the advantages of fast touch response, multi-touch support, and high touch accuracy. Touch-screen all-in-one computers have high requirements for touch performance, so the touch MCU (microcontroller) needs to be debugged for function and performance during the development of touch-screen all-in-one computers.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The purpose of the present disclosure is to overcome the above-mentioned deficiencies of the prior art, provide a touch device and a touch MCU upgrade method, and a computer-readable storage medium, so as to improve the convenience and safety of the touch MCU upgrade.

[0005] According to one aspect of the present disclosure, a method for upgrading a touch control MCU of a touch control device is provided, wherein the touch control device further comprises a main control module electrically connected to the touch control MCU;

[0006] The upgrading method comprises:

[0007] The main control module determines the target upgrade file according to the configuration parameters of the touch control MCU; the configuration parameters of the touch control MCU meet the pairing parameters of the target upgrade file;

[0008] The main control module writes the target upgrade file into the touch control MCU, so that the touch control MCU is upgraded according to the target upgrade file.

[0009] According to an embodiment of the present disclosure, the main control module is configured to be able to read one or more upgrade files;

[0010] The upgrading method further comprises:

[0011] The main control module reads the MD5SUM value of at least one upgrade file and calculates the MD5SUM value of the upgrade file; if the MD5SUM value of the read upgrade file is different from the calculated MD5SUM value of the upgrade file, the upgrade file cannot be selected as the target upgrade file.

[0012] According to an embodiment of the present disclosure, the main control module is configured to be able to read one or more upgrade files; the configuration parameters of the touch MCU include at least one of a software version number, a touch MCU model, a device brand, and a device size; the pairing parameters of the upgrade file include at least one of a software version number, a touch MCU model, a device brand, and a device size;

[0013] The main control module determines the target upgrade file according to the configuration parameters of the touch control MCU, including:

[0014] When the software version number in the pairing parameter is not higher than the software version number in the configuration parameter, the upgrade file is not selected as the target upgrade file;

[0015] and / or, when the touch control MCU model in the pairing parameter is inconsistent with the touch control MCU model in the configuration parameter, the upgrade file is not selected as the target upgrade file;

[0016] and / or, when the device brand in the pairing parameter is inconsistent with the device brand in the configuration parameter, the upgrade file is not selected as the target upgrade file;

[0017] And / or, when the device size in the pairing parameter is inconsistent with the device size in the configuration parameter, the upgrade file is not selected as the target upgrade file.

[0018] According to an implementation of the present disclosure, the touch control MCU has a parameter partition, and the parameter partition stores configuration parameters of the touch control MCU;

[0019] The main control module determines the target upgrade file according to the configuration parameters of the touch control MCU, including:

[0020] The main control module reads the configuration parameters of the touch control MCU from the parameter partition of the touch control MCU.

[0021] According to an embodiment of the present disclosure, the touch control MCU has a boot partition and an application partition;

[0022] The main control module writes the upgrade file into the touch control MCU so that the touch control MCU is upgraded according to the target upgrade file, which includes:

[0023] The main control module writes the target upgrade file into the application partition of the touch control MCU;

[0024] After the boot partition of the touch control MCU updates the startup parameters, the main control module controls the touch control MCU to restart.

[0025] According to an embodiment of the present disclosure, the main control module controls the touch control MCU to restart, including:

[0026] The main control module loads a restart instruction to the touch control MCU, and the restart instruction causes the touch control MCU to restart; or, the main control module stops loading the chip power supply voltage to the touch control MCU and then reloads the chip power supply voltage to the touch control MCU.

[0027] According to an embodiment of the present disclosure, the touch control device has a boost circuit, and the boost circuit is electrically connected to a chip power pin of the touch control MCU and a universal pin of the main control module;

[0028] After the main control module stops loading the chip power supply voltage to the touch control MCU, reloading the chip power supply voltage to the touch control MCU includes:

[0029] The main control module causes the common pin of the boost circuit to be loaded with a low level, and after maintaining the low level for 1 to 5 seconds, the chip power supply voltage is reloaded to the boost circuit.

[0030] According to an embodiment of the present disclosure, the upgrading method further includes:

[0031] The main control module determines the touch control MCU from the UID list through the VID and PID.

[0032] According to an embodiment of the present disclosure, the upgrading method further includes:

[0033] The main control module monitors the log of the touch control MCU and outputs it.

[0034] According to a second aspect of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored; the main control module of the touch control device can execute the computer program in the computer-readable storage medium to implement the above-mentioned upgrading method.

[0035] According to a third aspect of the present disclosure, a touch control device is provided, comprising a main control module and a touch control MCU electrically connected to each other; the main control module has an executable computer program, and the main control module implements the above-mentioned upgrade method when executing the computer program.

[0036] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0038] Figure 1 It is a schematic structural diagram of a touch device in one embodiment of the present disclosure.

[0039] Figure 2 The figure is a flowchart of a method for upgrading a touch MCU in one embodiment of the present disclosure.

[0040] Figure 3 The following is a schematic diagram of the contents of a property file of an upgrade file in one implementation manner of the present disclosure.

[0041] Figure 4 The figure is a schematic diagram of partitioning of a touch control MCU in one embodiment of the present disclosure.

[0042] Figure 5 The figure is a schematic diagram of the connection between the touch control MCU and the SOC in one embodiment of the present disclosure.

[0043] Figure 6 The figure is a schematic diagram of the upgrade process of the touch MCU in an example of the present disclosure. DETAILED DESCRIPTION

[0044] Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in a variety of forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that the present disclosure will be comprehensive and complete and fully convey the concepts of the example embodiments to those skilled in the art. The same reference numerals in the figures represent the same or similar structures, and thus their detailed description will be omitted. In addition, the drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale.

[0045] Although relative terms such as "upper" and "lower" are used in this specification to describe the relative relationship of one component of the illustration to another component, these terms are used in this specification only for convenience, such as according to the orientation of the examples described in the drawings. It is understood that if the device of the illustration is turned upside down, the component described as "upper" will become the component "lower". When a structure is "on" other structures, it may mean that the structure is formed integrally on the other structure, or that the structure is "directly" disposed on the other structure, or that the structure is "indirectly" disposed on the other structure through another structure.

[0046] The terms "a", "an", "the", "said" and "at least one" are used to indicate the presence of one or more elements / components / etc.; the terms "including" and "having" are used to express an open-ended inclusive meaning and mean that additional elements / components / etc. may exist in addition to the listed elements / components / etc.; the terms "first", "second" and "third" etc. are used merely as labels and are not intended to limit the quantity of their objects.

[0047] If the touch MCU (touch microcontroller) software malfunctions and performance failures occur during the use of an Android all-in-one machine, problems such as mismatches between the drawn lines and the actual drawn lines, breakpoints in the drawn lines, and high writing delays will occur during use. To solve these problems, the touch MCU program and the Android system need to be jointly debugged, which may require multiple erasing of the touch MCU. The touch MCU is an external chip and is usually not integrated with the SOC (system-on-chip) on a motherboard. The existing touch MCU upgrade method generally uses the Windows PC (personal computer with Windows operating system) end program provided by the supplier to upgrade the touch MCU software.

[0048] Considering the actual usage scenario, this method requires disassembling the Android all-in-one machine and connecting it with a dedicated USB (Universal Serial Bus) extension cable to upgrade the touch MCU normally. The advantage is that the upgrade method provided by the touch MCU supplier is universal and highly reliable. The disadvantage is that the Android all-in-one machine needs to be disassembled, and there is a risk of damage to the Android all-in-one machine during the disassembly process. The upgrade process requires the use of a Windows PC and a dedicated USB extension cable, and the port of the USB extension cable is paired with the USB pin of the touch MCU. When pairing, the D+ (first data signal) pin, D- (second data signal) pin, VCC (chip power supply voltage) pin, and GND (ground) pin of the touch MCU's USB need to be paired and connected with the D+ line, D- line, VCC line, and GND line of the USB bus respectively; at this time, power supply and data transmission are through a dedicated USB extension cable connected to the Windows PC, and a digital multimeter or oscilloscope is required to identify whether the voltage and current of the USB pin of the touch MCU of the Android all-in-one machine are normal and whether the data signal is stable, which brings certain inconvenience to the user's operation.

[0049] Moreover, in the development of a series of Android all-in-one products, there may be differences in touch screen specifications, touch screen consistency, sizes of different products, touch MCU models of different products, and brand types of different products. The Windows PC upgrade program provided by the supplier usually does not have verification methods such as version, touch MCU model, product size, brand type, and upgrade file integrity; this may cause different models of Android all-in-one machines to use the same upgrade program when upgrading the touch MCU, which cannot be accurately upgraded, resulting in differences or failures in product touch performance, and may even cause the touch MCU to be scrapped, adding huge costs to the subsequent product after-sales.

[0050] The disclosed embodiments provide a touch control device and a method for upgrading a touch control MCU (touch control microprocessor) of the touch control device. Figure 1 FIG. 1 is a schematic diagram of a touch device in one embodiment of the present disclosure. Figure 1 The touch control device includes a touch control MCU and a main control module MA which are electrically connected to each other; the touch control MCU is used to realize touch control of the touch control device. In an example, the touch control device also has a display layer PNL and a touch control layer TSL; the touch control MCU receives a touch signal generated by the touch layer TSL in response to a touch action, and sends a corresponding control instruction to the main control module MA according to the touch signal, and the main control module MA can control the touch control device according to the control instruction, for example, control the display layer PNL to display a new picture.

[0051] In one example, the touch device may be an all-in-one desktop conferencing machine.

[0052] Figure 2 In one embodiment of the present disclosure, a method for upgrading a touch MCU of a touch device is disclosed.

[0053] See also Figure 2 , the upgrade methods of touch MCU include:

[0054] Step S110, the main control module MA determines the target upgrade file according to the configuration parameters of the touch control MCU; the configuration parameters of the touch control MCU meet the pairing parameters of the target upgrade file;

[0055] Step S120: the main control module MA writes the target upgrade file into the touch control MCU, so that the touch control MCU is upgraded according to the target upgrade file.

[0056] The touch MCU upgrade method provided by the present disclosure does not need to be upgraded by disassembling the touch MCU, but is upgraded by the main control module MA of the touch device; this can avoid the damage that may be caused when the touch device is disassembled. At the same time, when upgrading the touch MCU, there is no need to use a USB extension cable to connect the pins of the touch MCU, which also simplifies the complexity and risk of damage of the touch MCU upgrade operation. In addition, the touch MCU is upgraded by the main control module MA of the touch device, which provides convenience for the remote upgrade of the touch MCU, is conducive to improving the timeliness of the touch MCU upgrade, is conducive to the timely maintenance and upgrade of the touch device, and greatly reduces the maintenance cost. Not only that, the main control module MA can also determine the target upgrade file according to the configuration parameters of the touch MCU, ensure that the upgrade file matches the touch MCU, avoid the problems caused by using inappropriate upgrade files to upgrade the touch MCU, and ensure the quality of the upgrade, and improve the upgrade efficiency, thereby improving the user's after-sales experience.

[0057] In one embodiment of the present disclosure, the main control module MA is a SOC (system on chip). The SOC can be arranged on a system mainboard of the touch control device. The touch control MCU can be integrated with the SOC on the same circuit board, or can be arranged on different circuit boards.

[0058] In one embodiment of the present disclosure, a touch control upgrade application runs in the main control module MA, and the touch control upgrade application is used to upgrade the touch control MCU. For example, the touch control upgrade application enables the touch control device to implement the touch control MCU upgrade method provided in the embodiment of the present disclosure.

[0059] In the touch control device provided in this embodiment, the main control module has an executable computer program (ie, a touch control upgrade application), and the main control module implements the touch control MCU upgrade method provided in the embodiment of the present disclosure when executing the computer program.

[0060] In one embodiment of the present disclosure, the upgrade method further includes: the main control module MA determines the touch MCU from the UID (Human Interface Device) list through VID (Vendor ID) and PID (Product ID). In this way, the main control module MA can quickly and accurately determine the touch MCU, reduce manual operations, and improve the efficiency of touch MCU upgrades. Not only that, even if the Android all-in-one machine dynamically uses multiple USB devices during the boot process or during use, the main control module MA can also accurately identify the touch MCU.

[0061] In one embodiment of the present disclosure, the main control module MA is configured to read one or more upgrade files; for example, the touch upgrade application can read one or more upgrade files. Figure 3 In the example, the touch upgrade application can read m upgrade files. Optionally, the read upgrade files can be stored in the touch device (for example, in the memory of the touch device), in an external hardware device (for example, in an external USB flash drive), or in a remote server or other location.

[0062] In an implementation manner of the present disclosure, the main control module MA determines the target upgrade file according to the configuration parameters of the touch control MCU, including: the main control module MA reads an upgrade file and determines whether the upgrade file can be used as the target upgrade file.

[0063] Furthermore, if the upgrade file cannot be used as the target upgrade file, the main control module MA prompts that the touch MCU upgrade has failed.

[0064] In another embodiment of the present disclosure, the main control module MA determines the target upgrade file according to the configuration parameters of the touch control MCU, including: the main control module MA reads multiple upgrade files, and determines one by one whether each upgrade file can be used as a target upgrade file; if all upgrade files are not determined as target upgrade files, the main control module MA prompts that the touch control MCU upgrade has failed.

[0065] In one embodiment of the present disclosure, the upgrading method further includes:

[0066] Step S210, the main control module MA reads the MD5SUM value of at least one upgrade file, and calculates the MD5SUM value of the upgrade file; if the MD5SUM value of the read upgrade file is different from the calculated MD5SUM value of the upgrade file, the upgrade file cannot be selected as the target upgrade file. In this way, it can be ensured that the target upgrade file is a complete and correct upgrade file, avoiding the use of damaged or erroneous upgrade files to upgrade the touch MCU.

[0067] For example, see Figure 3, the upgrade file has a property file (such as update.txt), and the property file records the MD5SUM value of the upgrade file. The main control module MA can calculate the MD5SUM value of the upgrade file, and compare the calculated value of the MD5SUM value with the read value to implement the MD5 check of the upgrade file. If the calculated MD5SUM value of the upgrade file is consistent with the MD5SUM value read from the property file, it is considered that the upgrade file has passed the MD5 check. If the calculated MD5SUM value of the upgrade file is inconsistent with the MD5SUM value read from the property file, the upgrade file has not passed the MD5 check, and it can be considered that there are errors in the upgrade file, such as missing some files or some files are damaged, etc. At this time, the upgrade file cannot be used as the target upgrade file.

[0068] In one example, if the upgrade file fails to pass the MD5 check, the upgrade file can be re-acquired, or if the target upgrade file cannot be determined, the upgrade file that fails the MD5 check can be re-acquired. Optionally, the upgrade file that fails the MD5 check can be re-downloaded to a local device through a remote network, such as to a memory of the touch device or an external memory connected to a storage device (such as a touch MCU, a mobile hard disk, or a memory in the same local area network).

[0069] In one embodiment of the present disclosure, see Figure 4 The configuration parameters of the touch MCU include at least one of the software version number, the touch MCU model, the device brand (such as the device brand signature), and the device size (such as the size type); the pairing parameters of the upgrade file include at least one of the software version number, the touch MCU model, the device brand, and the device size.

[0070] The main control module MA determines the target upgrade file according to the configuration parameters of the touch control MCU, including at least one of the following steps S301-304.

[0071] Step S301: When the software version number in the pairing parameter is not higher than the software version number in the configuration parameter, the upgrade file is not selected as the target upgrade file.

[0072] Step S302: When the touch control MCU model in the pairing parameters is inconsistent with the touch control MCU model in the configuration parameters, the upgrade file is not selected as the target upgrade file.

[0073] Step S303: When the device brand in the pairing parameters is inconsistent with the device brand in the configuration parameters, the upgrade file is not selected as the target upgrade file.

[0074] Step S304: When the device size in the pairing parameters is inconsistent with the device size in the configuration parameters, the upgrade file is not selected as the target upgrade file.

[0075] In an example, the touch control MCU has a parameter partition, and the parameter partition stores configuration parameters of the touch control MCU.

[0076] In one example, the main control module MA reads the configuration parameters of the touch control MCU from the parameter partition of the touch control MCU. For example, a touch upgrade application running on a SOC can read the configuration parameters of the touch control MCU from the parameter partition of the touch control MCU.

[0077] In an example, the upgrade file contains a file recording the pairing parameters, and the main control module MA can read the pairing parameters of the upgrade file from the file recording the pairing parameters.

[0078] In an example, the pairing parameters are recorded in the property file of the upgrade file, and the main control module MA can read each pairing parameter from the property file.

[0079] In one example, the configuration parameters of the touch MCU include software version number, touch MCU model, device brand, and device size; the pairing parameters of the upgrade file include software version number, touch MCU model, device brand, and device size. When determining the target upgrade file, the main control module MA needs to match the touch MCU and the upgrade file in terms of software version number, touch MCU model, device brand, and device size. For example, it is necessary to make the software version number of the configuration parameters higher than the software version number of the pairing parameters; the touch MCU model of the configuration parameters is consistent with the touch MCU model of the pairing parameters; the device brand of the configuration parameters is consistent with the device brand of the pairing parameters; and the device size of the configuration parameters is consistent with the device size of the pairing parameters. In this way, multiple security checks can be performed on the upgrade file.

[0080] In one embodiment of the present disclosure, the configuration parameters of the touch-control MCU can be matched with the pairing parameters of the upgrade file to determine the upgrade file that matches the touch-control MCU; then, an MD5 check is performed on the upgrade file that matches the touch-control MCU, and the upgrade file that passes the MD5 check and matches the touch-control MCU is the target upgrade file.

[0081] In another embodiment of the present disclosure, the upgrade file may be first verified by MD5, and then the upgrade file that passes the MD5 verification is matched with the touch MCU. The upgrade file that passes the MD5 verification and matches the touch MCU is the target upgrade file.

[0082] In one embodiment of the present disclosure, the touch control MCU has a boot partition and an application partition; in step S120, the main control module MA writes the target upgrade file into the application partition of the touch control MCU; after the boot partition of the touch control MCU updates the startup parameters, the main control module MA controls the touch control MCU to restart.

[0083] In this implementation, after the main control module MA writes the target upgrade file into the application partition of the touch control MCU, the boot loader in the boot partition of the touch control MCU can verify the target upgrade file written into the application partition, and update the startup parameters after the verification passes. After the boot partition updates the startup parameters, the main control module MA can control the touch control MCU to restart. If the touch control MCU restarts successfully under the guidance of the boot partition, the touch control MCU is successfully upgraded, and the touch control MCU updates the parameter partition, especially the touch control MCU updates the software version number in the parameter partition.

[0084] In the related art, when upgrading the touch MCU, it is not only necessary to disassemble the machine, but also to power on the entire machine to start the touch MCU after importing the upgrade file, that is, manually restart the touch MCU. This leads to low efficiency in upgrading the touch MCU. In the example provided in the embodiment of the present disclosure, after the boot partition of the touch MCU updates the startup parameters, the main control module MA can automatically control the restart of the touch MCU without restarting the entire machine; in other words, the touch device does not need to be powered off and disassembled during the touch MCU upgrade process, and the touch MCU can be restarted when the main control module MA is continuously powered on instead of restarting during the power-on process of the entire machine, which greatly improves the efficiency of the touch MCU upgrade.

[0085] In one embodiment of the present disclosure, the main control module MA sends an upgrade instruction to the touch control MCU before writing the target upgrade file to the touch control MCU; after receiving the upgrade instruction, the touch control MCU receives the target upgrade file sent by the main control module MA.

[0086] In one embodiment of the present disclosure, the main control module MA can control the restart of the touch control MCU by the following method:

[0087] The main control module MA loads a restart instruction to the touch control MCU, and the restart instruction restarts the touch control MCU; or, the main control module MA stops loading the chip power supply voltage to the touch control MCU and then reloads the chip power supply voltage to the touch control MCU.

[0088] As an example, see Figure 5 The touch control device has a boost circuit, and the boost circuit is electrically connected to the chip power supply voltage (VCC) pin of the touch control MCU and the general pin (GPIO) of the main control module MA.

[0089] After the main control module MA stops loading the chip power supply voltage to the touch control MCU, reloading the chip power supply voltage to the touch control MCU includes:

[0090] The main control module MA loads a low level to the common pin of the boost circuit, and after maintaining the low level for 1 to 5 seconds, reloads the chip power supply voltage (eg, a voltage of 5V) to the boost circuit.

[0091] For example, in Figure 5 In the example, the boost circuit includes a pull-up resistor and a diode, the first end of the pull-up resistor is used to load VDD, the second end of the pull-up resistor is electrically connected to the cathode of a diode (such as a voltage stabilizing diode or an anti-static diode), and the anode of the diode is used to load GND. The second end of the pull-up resistor is electrically connected to the general pin of the main control module MA and the chip power supply voltage pin of the touch MCU.

[0092] In one example, see Figure 5 The touch control MCU is electrically connected to the main control module MA through the USB bus. The D+ pin of the touch control MCU is electrically connected to the D+ port of the main control module MA through the D+ line of the USB bus, and the D- pin of the touch control MCU is electrically connected to the D- port of the main control module MA through the D- line of the USB bus.

[0093] In one example, see Figure 5 The touch control device also includes an ESD protector, which is electrically connected to a D+ pin, a D- pin, and a chip power supply voltage pin of the touch control MCU, thereby protecting the touch control MCU.

[0094] In an implementation manner of the present disclosure, the upgrade method further includes: the main control module MA monitors the log of the touch control MCU and outputs it.

[0095] For example, the main control module MA can determine whether the boot partition has updated the startup parameters by monitoring the log of the touch control MCU; after the boot partition updates the startup parameters, the main control module MA controls the touch control MCU to restart.

[0096] For another example, the main control module MA can determine whether the touch MCU restart is successful by monitoring the touch MCU log. If the touch MCU restarts successfully, the touch MCU upgrade is successful. If the touch MCU restarts unsuccessfully, especially if the touch MCU fails to restart multiple times in a row, the touch MCU upgrade fails.

[0097] As follows, Figure 6The example shown in the figure is used to introduce and illustrate the method for upgrading the touch MCU of the touch device provided by the present disclosure. In this example, only one upgrade file is provided. Figure 6 , on the touch device installed with the touch upgrade application, the touch upgrade application runs in the SOC.

[0098] S1. During the upgrade, the touch upgrade application first obtains the dynamic HID (Human Interface Device) list of USB devices, identifies the touch MCU through the touch MCU's unique VID (Vendor ID, manufacturer identification code) and unique PID (Product ID, product identification code), and establishes a USB channel with the touch MCU.

[0099] S2. Read the MD5SUM value and pairing parameters in the property file of the upgrade file. The pairing parameters include the software version number, touch MCU model, device brand, and device size.

[0100] S3: Calculate the MD5SUM value of the upgrade file and determine whether the calculated value and the read value of MD5SUM are the same; if they are the same, the upgrade file passes the MD5 check. If it does not pass the MD5 check, it will prompt that the check failed and the touch MCU upgrade is terminated.

[0101] S4: Read the software version number from the parameter partition of the touch MCU and compare it with the software version number in the pairing parameter of the upgrade file. If the software version number in the property file is higher than the software version number in the parameter partition, continue the matching process. If the software version number in the property file is not higher than the software version number in the parameter partition, it will prompt that the verification failed and the upgrade of the touch MCU is terminated.

[0102] S5: Read the touch MCU model, device brand, and device size from the parameter partition of the touch MCU, and compare them with the touch MCU model, device brand, and device size in the pairing parameters to determine whether they are the same. If they are the same, the match is successful, the upgrade file is the target upgrade file, and the touch upgrade application sends an upgrade command to the touch MCU; if they are not the same, the match is unsuccessful, and the verification fails, and the touch MCU upgrade ends.

[0103] S6: After the touch upgrade application sends an upgrade instruction to the touch MCU, it starts to transmit the target upgrade file; the touch MCU responds to the upgrade instruction, starts to receive the target upgrade file, and can save the upgrade file in the application partition.

[0104] S7: After the target upgrade file is written into the application partition, the boot partition updates the startup parameters. Specifically, the boot loader in the boot partition updates the startup parameters.

[0105] S8: The SOC monitors the log of the touch control MCU and controls the touch control MCU to restart after determining that the boot partition has updated the startup parameters.

[0106] S9: If the touch MCU restarts successfully, the software version number in the parameter partition is updated. At the same time, the SOC monitors the restart result of the touch MCU; if the touch MCU restarts successfully, it prompts that the touch MCU upgrade is successful and the touch MCU upgrade ends; if the touch MCU restarts unsuccessfully, it prompts that the touch MCU upgrade fails and the touch MCU upgrade ends.

[0107] In this example, the touch device adopts a software-hardware integration method and uses a touch upgrade application to securely upgrade the touch MCU. This is conducive to a more stable and faster upgrade of the touch MCU program, and is conducive to the application on Android all-in-one machines with high precision and high standards for touch technology.

[0108] It should be noted that although the upgrade method of the touch MCU provided by the embodiment of the present disclosure is described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc., which shall all be considered as part of the present disclosure.

[0109] It is understandable that the touch MCU upgrade method disclosed in the present invention can be implemented as a system, method or program product. Therefore, various aspects of the present invention can be specifically implemented in the following forms, namely: a complete hardware embodiment, a complete software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software.

[0110] It is understandable that the touch MCU upgrade method provided by the present disclosure can be implemented by software (such as a touch upgrade application) or by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable the main control module of the touch device to execute the touch MCU upgrade method according to the embodiment of the present disclosure.

[0111] In the embodiments of the present disclosure, a computer-readable storage medium is also provided, on which a computer program capable of implementing the above-mentioned method of the present specification is stored, that is, a program product is stored. In some possible embodiments, the main control module of the touch device can execute the computer program in the computer-readable storage medium to implement the upgrade method of the touch MCU provided in the embodiments of the present disclosure. The computer program can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited to this. In this document, the readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, device or device. The program product can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more conductors, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fibers, a portable compact disk-read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0112] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0113] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0114] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0115] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to an exemplary embodiment of the present invention, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0116] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A method for upgrading a touch MCU of a touch device, characterized in that: The touch control device also includes a main control module electrically connected to the touch control MCU; The upgrading method comprises: The main control module determines the target upgrade file according to the configuration parameters of the touch control MCU; the configuration parameters of the touch control MCU meet the pairing parameters of the target upgrade file; The main control module writes the target upgrade file into the touch control MCU, so that the touch control MCU is upgraded according to the target upgrade file.

2. The upgrading method according to claim 1, characterized in that: The main control module is configured to read one or more upgrade files; The upgrading method further comprises: The main control module reads the MD5SUM value of at least one upgrade file, and calculates the MD5SUM value of the upgrade file; If the read MD5SUM value of the upgrade file is different from the calculated MD5SUM value of the upgrade file, the upgrade file cannot be selected as the target upgrade file.

3. The upgrading method according to claim 1, characterized in that: The main control module is configured to read one or more upgrade files; the configuration parameters of the touch MCU include at least one of a software version number, a touch MCU model, a device brand, and a device size; the pairing parameters of the upgrade file include at least one of a software version number, a touch MCU model, a device brand, and a device size; The main control module determines the target upgrade file according to the configuration parameters of the touch control MCU, including: When the software version number in the pairing parameter is not higher than the software version number in the configuration parameter, the upgrade file is not selected as the target upgrade file; and / or, when the touch control MCU model in the pairing parameter is inconsistent with the touch control MCU model in the configuration parameter, the upgrade file is not selected as the target upgrade file; and / or, when the device brand in the pairing parameter is inconsistent with the device brand in the configuration parameter, the upgrade file is not selected as the target upgrade file; And / or, when the device size in the pairing parameter is inconsistent with the device size in the configuration parameter, the upgrade file is not selected as the target upgrade file.

4. The upgrading method according to claim 1, characterized in that: The touch control MCU has a parameter partition, and the parameter partition stores configuration parameters of the touch control MCU; The main control module determines the target upgrade file according to the configuration parameters of the touch control MCU, including: The main control module reads the configuration parameters of the touch control MCU from the parameter partition of the touch control MCU.

5. The upgrading method according to claim 1, characterized in that: The touch control MCU has a boot partition and an application partition; The main control module writes the upgrade file into the touch control MCU so that the touch control MCU is upgraded according to the target upgrade file, which includes: The main control module writes the target upgrade file into the application partition of the touch control MCU; After the boot partition of the touch control MCU updates the startup parameters, the main control module controls the touch control MCU to restart.

6. The upgrading method according to claim 5, characterized in that: The main control module controls the touch control MCU to restart, including: The main control module loads a restart instruction to the touch control MCU, and the restart instruction causes the touch control MCU to restart; or, the main control module stops loading the chip power supply voltage to the touch control MCU and then reloads the chip power supply voltage to the touch control MCU.

7. The upgrading method according to claim 6, characterized in that: The touch control device has a boost circuit, and the boost circuit is electrically connected to the chip power pin of the touch control MCU and the universal pin of the main control module; After the main control module stops loading the chip power supply voltage to the touch control MCU, reloading the chip power supply voltage to the touch control MCU includes: The main control module causes the common pin of the boost circuit to be loaded with a low level, and after maintaining the low level for 1 to 5 seconds, the chip power supply voltage is reloaded to the boost circuit.

8. The upgrading method according to any one of claims 1 to 7, characterized in that: The upgrading method further comprises: The main control module determines the touch control MCU from the UID list through the VID and PID.

9. The upgrading method according to any one of claims 1 to 7, characterized in that: The upgrading method further comprises: The main control module monitors the log of the touch control MCU and outputs it.

10. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium; a main control module of a touch-sensitive device can execute the computer program in the computer-readable storage medium to implement the upgrading method according to any one of claims 1 to 9.

11. A touch control device, comprising a main control module and a touch control MCU electrically connected to each other; the main control module has an executable computer program, and the main control module implements the upgrade method according to any one of claims 1 to 9 when executing the computer program.

Images