Full-link debugging system and method for touch screen module

Abstract

The invention discloses a full-link debugging system of a touch screen module, which is characterized in that the touch screen module, a debugging board and a mainboard of the system are sequentially connected in series through a bus to form a data information transmission link; the debugging board is connected with the debugging analysis device through a debugging interface to form a debugging information transmission link; the power supply battery is connected with the mainboard; the debugging board forwards original touch data from the touch screen module to the main board, and a driving layer of the main board analyzes and processes the original touch data and then sends data information which is verified to be qualified to an upper-layer application to be displayed; the debugging analysis device determines to-be-optimized configuration parameters of the equipment tree according to the received communication indexes and issues the to-be-optimized configuration parameters to the mainboard through the debugging board, and the mainboard outputs optimization result parameters through the debugging board after applying the to-be-optimized configuration parameters of the equipment tree. In addition, the invention also discloses a corresponding method. By adopting the technical scheme, the debugging efficiency of the touch screen module is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of touch screen debugging, in particular to a full-link debugging system of a touch screen module and a method thereof. BACKGROUND

[0002] As a key component of human-computer interaction, the performance of the touch screen module directly affects the user experience. In the production test and later maintenance, the parameters of the touch screen module need to be debugged and optimized to ensure that the response speed, accuracy and stability meet the requirements.

[0003] At present, the touch screen module manufacturers usually only debug the touch screen module as a single component, and complete it on the whole machine product, so that the terminal user often encounters problems such as mis-touch and disconnection when using the whole machine product with the touch screen module. The reason is that this single debugging method usually depends on independent test equipment or simple point-to-point connection, the debugging process is disconnected with the actual running environment of the equipment, and the real performance after the integration of the whole machine cannot be reflected, and the debugging parameters need to be reprogrammed or restarted after the equipment, which is low in efficiency. SUMMARY

[0004] The present application provides a full-link debugging system of a touch screen module and a method thereof, which avoids the low efficiency caused by the single component debugging method of the prior art.

[0005] The present application provides a full-link debugging system of a touch screen module, which comprises a touch screen module, a debugging board, a mainboard, a debugging analysis device and a power supply battery. The touch screen module, the debugging board and the mainboard are connected in series through a bus to form a data information transmission link. The debugging board is connected with the debugging analysis device through a debugging interface to form a debugging information transmission link. The power supply battery is connected with the mainboard to supply power to the touch screen module, the debugging board and the mainboard. When transmitting data information, the debugging board forwards the original touch data from the touch screen module to the mainboard, and the driving layer of the mainboard analyzes and processes the original touch data and sends the data information that passes the verification to the upper layer application to display; when transmitting debugging information, the debugging board collects and caches the communication indicators of the touch screen module side and the mainboard side and reports them to the debugging analysis device, the debugging analysis device determines the device tree optimization configuration parameters according to the received communication indicators and sends them to the mainboard through the debugging board, and the mainboard outputs the optimization result parameters through the debugging board after applying the device tree optimization configuration parameters.

[0006] In addition, the debugging board comprises: The acquisition module is used to acquire a first data communication indicator and a second data communication indicator. The first data communication indicator is the communication indicator when the debugging board receives and forwards the original touch data from the touch screen module, and the second data communication indicator is the communication indicator when the motherboard parses and processes the original touch data at the driver layer. The caching module is used to cache the first data communication indicator and the second data communication indicator. The reporting module is used to report the first data communication indicator and the second data communication indicator to the debugging and analysis device.

[0007] In addition, the debugging and analysis device includes: The analysis module is used to determine the configuration parameters of the device tree to be optimized based on the first data communication indicator and the second data communication indicator. The distribution module is used to distribute the configuration parameters of the device tree to be optimized to the motherboard through the debugging board.

[0008] In addition, the motherboard includes: The device tree management module is used to load and parse the device tree update file containing the device tree configuration parameters to be optimized, and to create device tree nodes; An initialization module is used by the registered touchscreen module driver to reinitialize the touchscreen module device based on the device tree node.

[0009] Correspondingly, a full-link debugging method for touchscreen modules is also provided. The system to which the method is applied includes a touchscreen module, a debugging board, a motherboard, and a debugging analysis device. The method includes: During data transmission, the debugging board receives raw touch data from the touch screen module and forwards it to the motherboard. The motherboard's driver layer parses and processes the raw touch data and sends the verified data to the upper-layer application for display. During the debugging information transmission, the debugging board collects and reports the communication indicators from the cached touch screen module side and the motherboard side to the debugging analysis device. The debugging analysis device determines the device tree configuration parameters to be optimized based on the received communication indicators and sends them to the motherboard through the debugging board. When optimizing configuration parameters, the motherboard applies the configuration parameters to be optimized from the device tree and then outputs the optimization result parameters through the debug board.

[0010] In addition, the debugging board collects communication indicators from both the cached touchscreen module side and the motherboard side and reports them to the debugging analysis device. The debugging analysis device determines the device tree configuration parameters to be optimized based on the received communication indicators and sends them to the motherboard through the debugging board. The process includes the following steps: The debug board collects and caches the first data communication indicator, which is the communication indicator when the debug board receives and forwards the raw touch data from the touch screen module. The debug board collects and caches the second data communication index, which is the communication index of the motherboard when parsing and processing the original touch data at the driver layer. The debugging board reports the first data communication indicator and the second data communication indicator to the debugging analysis device; The debugging and analysis device determines the configuration parameters of the device tree to be optimized based on the first data communication index and the second data communication index, and sends the configuration parameters of the device tree to be optimized to the motherboard through the debugging board.

[0011] In addition, the process of the motherboard applying the device tree to optimize the configuration parameters includes the following steps: The motherboard loads a device tree update file containing the device tree configuration parameters to be optimized. The motherboard's operating system kernel parses the device tree update file and creates device tree nodes; The touchscreen module driver already registered within the motherboard reinitializes the touchscreen module device based on the device tree node.

[0012] In addition, the following steps are also included: The debugging board sends optimization result parameters to the touch screen module; The touchscreen module stores the optimization result parameters.

[0013] In addition, it also includes: The debug board encapsulates the optimization result parameters and the serial number of the touch screen module into a data packet and uploads it to the cloud server. The debug board generates a QR code containing the download link and verification code of the data packet and sends it to the debug analysis device.

[0014] Compared with the prior art, the present invention has the following advantages: The touch screen module debugging system provided in this embodiment of the invention connects a debugging board in series between the touch screen module and the motherboard. During data transmission, the debugging board receives the raw touch data from the touch screen module and forwards it to the motherboard. After the driver layer of the motherboard parses and processes the raw touch data, it sends the verified data information to the upper-layer application for display. This realizes full-link monitoring of touch data from acquisition, transmission to processing, and improves efficiency. Attached Figure Description

[0015] Figure 1 This is a block diagram of one embodiment of the full-link debugging system for a touch screen module according to the present invention; Figure 2This is a block diagram of a specific implementation of the debugging board of a full-link debugging system for a touch screen module according to the present invention; Figure 3 This is a block diagram illustrating a specific implementation of the debugging and analysis device of the full-link debugging system for a touchscreen module according to the present invention. Figure 4 This is a block diagram of the motherboard of the full-link debugging system for a touch screen module according to the present invention. Figure 5 This is a flowchart illustrating the first instance of a full-link debugging method for a touchscreen module according to the present invention. Figure 6 This is a flowchart illustrating the second embodiment of a full-link debugging method for a touchscreen module according to the present invention. Detailed Implementation

[0016] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0017] refer to Figure 1 The figure is a block diagram of an embodiment of a full-link debugging system for a touch screen module according to the present invention, including: a touch screen module 101, a debugging board 102, a motherboard 103, a debugging and analysis device 104, and a power supply battery 105.

[0018] The touchscreen module 101, the debugging board 102, and the motherboard 103 are connected via I / O. 2 The C-buses are connected in series to form a data transmission link. The touchscreen module 101 serves as the I-bus. 2 The C device sends raw touch data (including coordinates, pressure, timestamps, etc.) to the debugging board 102; the debugging board 102 acts as an I / O controller. 2 The C host device reads the touchscreen module data and uses it as I... 2 C is read from the device by the motherboard 103, thereby completing the data forwarding.

[0019] The debug board 102 and the debug analysis device 104 are connected via a USB or UART debug interface to form a debug information transmission link. The debug analysis device 104 can be a development PC (personal computer), laptop, or mobile device running dedicated debug software.

[0020] The power supply battery 105 is connected to the motherboard 103 to supply power to the motherboard 103. The motherboard 103 then supplies power to the debugging board 102 and the touch screen module 101 through the power management circuit to simulate the actual working state of the whole machine.

[0021] The debugging system of this invention can be used directly on the production line. The debugging board serves as both an interface for production testing and a monitoring node for later debugging, thereby improving production efficiency and realizing the integration of production and debugging of touch screen modules on the manufacturer's side.

[0022] Furthermore, this embodiment of the invention connects a debugging board in series between the touch screen module and the motherboard. During data transmission, the debugging board receives the raw touch data from the touch screen module and forwards it to the motherboard. After the driver layer of the motherboard parses and processes the raw touch data, it sends the verified data information to the upper-layer application for display, thus realizing full-link monitoring of touch data from acquisition, transmission to processing.

[0023] refer to Figure 2 The figure is a block diagram of the specific implementation of the debugging board of the full-link debugging system for a touch screen module of the present invention. The debugging board 102 includes: a data acquisition module 201, a cache module 202 and a reporting module 203.

[0024] Acquisition module 201: Used to acquire first data communication indicators and second data communication indicators. The first data communication indicator includes I / O between the debug board and the touch screen module. 2 C-level communication metrics include bit error rate, signal strength, and response delay; second data communication metrics include I / O between the debug board and the motherboard. 2 The corresponding indicators of C communication. The acquisition module monitors I... 2 The C-bus physical layer signals and data link layer protocols are used to collect metrics.

[0025] Cache module 202: Employs a circular buffer or FIFO queue to cache collected communication metrics, preventing data loss. The cache module has an overflow protection mechanism; when the buffer is nearly full, it automatically discards the oldest data or triggers an emergency report.

[0026] Reporting module 203: Packages the cached communication metrics into debug information frames and reports them to the debug analysis device via the USB / UART interface. Reporting can be performed in periodic reporting or event-triggered reporting modes.

[0027] refer to Figure 3 The figure is a block diagram of the specific implementation of the debugging and analysis device of the full-link debugging system for a touch screen module of the present invention. The debugging and analysis device 104 includes: an analysis module 301 and a distribution module 302.

[0028] Analysis module 301: Receives communication metrics reported by the debug board and performs multi-dimensional analysis. The analysis module has a built-in rule engine; for example, if the bit error rate on the touchscreen module side is higher than threshold X1, it suggests enhancing filtering; if the response latency on the motherboard side is higher than threshold X2, it suggests increasing I... 2C. Clock frequency; if both ends of the spectrum deteriorate, it is recommended to check power supply noise or reduce the communication rate. The analysis results are then converted into specific device tree configuration parameters.

[0029] The distribution module 302 encapsulates the device tree configuration parameters generated by the analysis module into instruction frames, sends them to the debug board via the debug interface, and then forwards them to the main board. The distribution module supports parameter preview, batch distribution, and version management functions.

[0030] refer to Figure 4 The figure is a block diagram of the motherboard of the full-link debugging system for a touch screen module of the present invention. The motherboard 103 specifically includes: a device tree management module 401 and an initialization module 402.

[0031] Device Tree Management Module 401: Responsible for the dynamic management of the device tree. When new device tree configuration parameters are received, this module formats them into device tree overlay fragments, dynamically loads them through the Linux kernel's configfs or sysfs interface, and updates the device tree without restarting the system.

[0032] Initialization module 402: After the device tree node is updated, the initialization module notifies the touchscreen module driver to re-detect the device. The driver calls the probe function to read the new parameters in the device tree (such as touchscreen,report-rate-hz = ...). <120> ;), and accordingly reconfigure the touchscreen controller registers to complete hardware initialization.

[0033] It should be noted that, in addition to the device tree management module and initialization module listed above, the motherboard also includes other functional modules that a complete motherboard should have, such as the application subsystem, which will not be listed and elaborated here.

[0034] Another aspect of the present invention will now be described.

[0035] refer to Figure 5 This figure is a flowchart illustrating a first embodiment of a full-link debugging method for a touchscreen module according to the present invention. The process includes: S501, during data transmission, the debugging board receives raw touch data from the touch screen module and forwards it to the motherboard. The motherboard's driver layer parses and processes the raw touch data and sends the verified data information to the upper-layer application for display. S502, during the debugging information transmission, the debugging board collects and caches the communication indicators of the touch screen module side and the motherboard side respectively and reports them to the debugging analysis device. The debugging analysis device determines the device tree configuration parameters to be optimized based on the received communication indicators and sends them to the motherboard through the debugging board. S503, when optimizing configuration parameters, the motherboard outputs the optimization result parameters through the debug board after applying the configuration parameters to be optimized in the device tree.

[0036] This invention embodiment connects a debugging board in series between the touch screen module and the motherboard. During data transmission, the debugging board receives the raw touch data from the touch screen module and forwards it to the motherboard. After the motherboard's driver layer parses and processes the raw touch data, it sends the verified data information to the upper-layer application for display. This achieves full-link monitoring of touch data from acquisition, transmission to processing, and can accurately obtain the communication indicators of each link.

[0037] In addition, the debugging and analysis device dynamically generates device tree optimization parameters based on real-time collected communication indicators, and sends them to the motherboard through the debugging board. The new parameters take effect on the motherboard without restarting, thus achieving non-stop debugging.

[0038] In addition, communication indicators during the touch data transmission process are collected by the debugging board. Then, the debugging analysis device analyzes the communication indicators and determines the parameters to be optimized in the device tree. The results are then sent to the motherboard for updating. The optimized parameters can be fed back to the debugging analysis device to verify the optimization effect and iteratively optimize. This forms a complete closed loop of "communication indicator collection → indicator analysis → parameter generation → application deployment → effect feedback", realizing closed-loop optimization of the touch screen module debugging process.

[0039] refer to Figure 6 The figure is a flowchart illustrating a second embodiment of a full-link debugging method for a touchscreen module according to the present invention. The process includes: S601, the touchscreen module generates raw touch data, which is then transmitted via I... 2 The C bus sends data to the debug board; S602, the debugging board receives and forwards raw touch data to the motherboard, and at the same time collects and caches the first communication indicators from the touch screen module side. The first communication indicators refer to key indicators such as signal-to-noise ratio (SNR), reporting rate, and response latency. S603, the motherboard driver layer parses data, and after verification, submits it to the upper-layer application (such as GUI) for display; S604, the debug board collects and caches the second communication indicators from the motherboard. The second communication indicators refer to the communication indicators of the data processed by the touch screen module driver in the motherboard, such as key indicators like signal-to-noise ratio (SNR), reporting rate, and response latency. S605, the debugging board reports two types of indicators (i.e., the first communication indicator and the second communication indicator) to the debugging analysis device; S606, the debugging and analysis device determines the configuration parameters of the device tree to be optimized based on the received first and second communication indicators; S607, the debugging and analysis device sends the device tree configuration parameters to be optimized to the motherboard through the debugging board; In S608, the motherboard's operating system kernel updates the device tree nodes based on the device tree configuration parameters to be optimized. In S609, the motherboard's touchscreen driver reinitializes the device based on the new node in the device tree. This dynamic updating of the device tree allows the debugging board to immediately respond and dynamically adjust the filtering algorithm parameters and scanning frequency in the driver when it detects specific interference (such as charging noise) in the "whole machine debugging environment" of this embodiment. This means that the same driver code can automatically adapt to modules from different suppliers, different whole machine environments, or different operating states of the same whole machine by loading different device tree configurations, greatly improving compatibility and robustness.

[0040] It should be noted that, in the debugging method of this embodiment of the invention, after the debugging loop is closed, the debugging software uses a debugging board or I... 2 The C command writes optimized key configuration parameters (such as device tree fragments) to a specific address in a small piece of non-volatile memory (such as EEPROM) or Flash memory inside the touchscreen controller chip. Then, when the touchscreen module arrives at the OEM and is powered on for the first time, the driver on the motherboard adds an automatic read step during initialization: actively reading the data from the touchscreen module's I / O pin. 2 C requested this configuration and made dynamic adjustments accordingly.

[0041] In addition, the optimized parameters can be bound to the unique serial number (SN) or model code of the touchscreen module and uploaded to a cloud database. Simultaneously, a QR code containing a download link and a hash checksum can be generated and affixed to the touchscreen module. When the touchscreen module arrives at the OEM and is assembled with the complete system, workers scan the QR code on the module, or the production line testing system automatically reads the module's SN. The OEM's production line client software automatically reads the corresponding configuration file from the cloud server and automatically flashes it into the system image of the motherboard being assembled.

[0042] This invention creates a complete machine testing environment on the side of the touch screen module manufacturer, namely pre-machine debugging, which compresses the traditional serial process of "module testing - complete machine debugging - problem rework" (average 15 days) into a parallel process (≤7 days), improving efficiency by more than 50%. In the complete machine environment, hidden problems (such as accidental touches and disconnections) are discovered early, reducing the return rate. The dynamic debugging technology reduces the cost of solving a single problem by 60% (traditional remote debugging requires 2-3 iterations, while this invention completes it in one go).

[0043] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A full-link debugging system for a touchscreen module, characterized in that, The system includes: a touch screen module, a debugging board, a motherboard, a debugging and analysis device, and a power supply battery; The touch screen module, debugging board and motherboard are connected in series via a bus to form a data information transmission link; The debugging board and the debugging analysis device are connected through a debugging interface to form a debugging information transmission link; The power supply battery is connected to the motherboard and is used to power the touch screen module, the debugging board and the motherboard. During data transmission, the debugging board forwards raw touch data from the touchscreen module to the motherboard. The motherboard's driver layer parses and processes the raw touch data and sends the verified data to the upper-layer application for display. During debugging information transmission, the debugging board collects and caches communication indicators from both the touchscreen module and the motherboard and reports them to the debugging analysis device. The debugging analysis device determines the device tree configuration parameters to be optimized based on the received communication indicators and sends them to the motherboard through the debugging board. After applying the device tree configuration parameters to be optimized, the motherboard outputs the optimization result parameters through the debugging board.

2. The end-to-end debugging system for a touchscreen module according to claim 1, characterized in that, The debugging board includes: The acquisition module is used to acquire a first data communication indicator and a second data communication indicator. The first data communication indicator is the communication indicator when the debugging board receives and forwards the original touch data from the touch screen module, and the second data communication indicator is the communication indicator when the motherboard parses and processes the original touch data at the driver layer. The caching module is used to cache the first data communication indicator and the second data communication indicator. The reporting module is used to report the first data communication indicator and the second data communication indicator to the debugging and analysis device.

3. The end-to-end debugging system for a touchscreen module according to claim 2, characterized in that, The debugging and analysis device includes: The analysis module is used to determine the configuration parameters of the device tree to be optimized based on the first data communication indicator and the second data communication indicator. The distribution module is used to distribute the configuration parameters of the device tree to be optimized to the motherboard through the debugging board.

4. The end-to-end debugging system for a touchscreen module according to any one of claims 1-3, characterized in that, The motherboard includes: The device tree management module is used to load and parse the device tree update file containing the device tree configuration parameters to be optimized, and to create device tree nodes; An initialization module is used by the registered touchscreen module driver to reinitialize the touchscreen module device based on the device tree node.

5. A full-link debugging method for a touchscreen module, the system to which the method is applied includes a touchscreen module, a debugging board, a motherboard, and a debugging analysis device, the method comprising: During data transmission, the debugging board receives raw touch data from the touch screen module and forwards it to the motherboard. The motherboard's driver layer parses and processes the raw touch data and sends the verified data to the upper-layer application for display. During the debugging information transmission, the debugging board collects and reports the communication indicators from the cached touch screen module side and the motherboard side to the debugging analysis device. The debugging analysis device determines the device tree configuration parameters to be optimized based on the received communication indicators and sends them to the motherboard through the debugging board. When optimizing configuration parameters, the motherboard applies the configuration parameters to be optimized from the device tree and then outputs the optimization result parameters through the debug board.

6. The end-to-end debugging method for a touchscreen module according to claim 5, characterized in that, The debugging board collects communication metrics from both the cached touchscreen module side and the motherboard side and reports them to the debugging and analysis device. The debugging and analysis device determines the device tree configuration parameters to be optimized based on the received communication metrics and sends them to the motherboard through the debugging board. The process includes the following steps: The debug board collects and caches the first data communication indicator, which is the communication indicator when the debug board receives and forwards the raw touch data from the touch screen module. The debug board collects and caches the second data communication index, which is the communication index of the motherboard when parsing and processing the original touch data at the driver layer. The debugging board reports the first data communication indicator and the second data communication indicator to the debugging analysis device; The debugging and analysis device determines the configuration parameters of the device tree to be optimized based on the first data communication index and the second data communication index, and sends the configuration parameters of the device tree to be optimized to the motherboard through the debugging board.

7. The end-to-end debugging method for a touchscreen module according to claim 5, characterized in that, The process of applying the device tree configuration parameters to be optimized to the motherboard includes the following steps: The motherboard loads a device tree update file containing the device tree configuration parameters to be optimized. The motherboard's operating system kernel parses the device tree update file and creates device tree nodes; The touchscreen module driver already registered within the motherboard reinitializes the touchscreen module device based on the device tree node.

8. The end-to-end debugging method for a touchscreen module according to any one of claims 5-7, characterized in that, It also includes the following steps: The debugging board sends optimization result parameters to the touch screen module; The touchscreen module stores the optimization result parameters.

9. The end-to-end debugging method for a touchscreen module according to any one of claims 5-7, characterized in that, Also includes: The debug board encapsulates the optimization result parameters and the serial number of the touch screen module into a data packet and uploads it to the cloud server. The debug board generates a QR code containing the download link and verification code of the data packet and sends it to the debug analysis device.

Images