WO2019061049A1

WO2019061049A1 - System and method for debugging driver of liquid crystal display module

Info

Publication number: WO2019061049A1
Application number: PCT/CN2017/103596
Authority: WO
Inventors: 叶智军
Original assignee: 深圳传音通讯有限公司
Priority date: 2017-09-27
Filing date: 2017-09-27
Publication date: 2019-04-04

Abstract

A method for debugging a driver of a liquid crystal display module comprises: a PC terminal inputting original parameters to a driver file of a liquid crystal display module of a mobile terminal (S330); the PC terminal editing a batch script as required (S340); and performing batch reading/writing of the original parameters. Also provided is a system for debugging a driver of a liquid crystal display module. The above method and system create a plurality of index nodes, data nodes and original parameter nodes in a driver file to perform operations on a plurality of indices, store data and read original parameters without relying on a specific platform, can be transferred to any platform, and employ simple coding principles and straightforward code.

Description

Liquid crystal display module driving debugging system and debugging method

Technical field

The invention relates to a mobile terminal driving debugging technology, in particular to a liquid crystal display module driving debugging system and a debugging method.

Background technique

LCM (LCD Module) is an LCD display module, a liquid crystal module, and a liquid crystal display module. It refers to assembling liquid crystal display devices, connectors, peripheral circuits such as control and driving, PCB circuit boards, backlights, and structural components. Component. LCM provides users with a standard LCD display driver interface, and the user operates according to the interface requirements to control the LCD to display correctly. LCM is a highly integrated LCD product. For small-size LCD displays, LCM can be easily connected to various microcontrollers. For large-size or color LCD displays, it usually takes up a considerable portion of the resources of the control system. Control cannot be achieved at all, and the amount of data processed is huge. LCM products can effectively solve the above problems. With the rapid development of information industry technology, the demand for LCM has increased rapidly, especially for small and medium-sized liquid crystal display modules, which have a wide range of applications.

In order for LCM to work properly, there must be a set of initial code optimized for layer-by-layer trial production; in addition to the basic functional guarantees, many important features are also closely related to the initial code, such as the typical FLICKER (flashing) and gamma. As the LCM driver debugger, you will definitely be exposed to the LCM initial code debugging. A commonly used LCM detection and debugging method is as follows:

S101. Control access switching of test signals. The access port of the detecting unit is connected to the signal access port, and the signal frequency dividing circuit for frequency-dividing the tested test signal is connected with the signal access port for implementing multiple access test signals. The signal switching device for switching processing uses the grading driving unit to perform frequency division grading control on the signal frequency dividing circuit, thereby realizing one-by-one detection process of color block and color display definition of the LCM substrate corresponding to each test signal.

S102, control program and communication of control signals. The control system and the host computer are connected through the parallel PCI bus to realize communication between the control program and the control signal.

S103. Control and debug the LCM detection unit test program and the test algorithm. Debugging of the control program for access control of test signals and the detection of LCM by the DSP control system The corresponding test program and the test algorithm are exchanged to adapt to the detection requirements of different LCM substrates. The analog-to-digital conversion circuit is used to realize the conversion of the control information of the drive unit by the DSP control system, and several CAN interfaces are set for receiving the host computer to the DSP. The control commands of the module and the real-time control of the corresponding algorithm.

S104. PC error correction display of the detected data. The detection data is stored in real time, and the above-mentioned detection data is compared with the qualified database of each detection data, the error data is found, the control switching module performs error correction monitoring display, and the error data is displayed on the monitoring display screen in real time.

S105: Adjust the LCM according to the detection result, and perform adjustment and testing repeatedly until the debugging of the LCM is completed.

For small and medium size LCD modules, contrast and FLICKER debugging has always been one of the most important debugging projects. The contrast of liquid crystal display modules and FLICKER debugging, the current practice is to manually Set the corresponding adjustment contrast and FLICKER register value in the driver IC of the liquid crystal display module to achieve the purpose of debugging the contrast of the liquid crystal display module and FLCIKER. The disadvantages are: first, the manual debugging speed is slow; second, the debugging result is not reliable.

As shown in FIG. 1 , it is a contrast and FLICKER debugging system of a commonly used liquid crystal display module. The debugging system includes: a liquid crystal display module 110 to be subjected to contrast and FLICKER debugging; and a liquid crystal display module 110 connected thereto. And the ARM debugging board 120 for performing contrast and FLICKER debugging on the liquid crystal display module 110 according to the received first instruction and configuration parameter; and testing the contrast of the panel of the liquid crystal display module through the test probe according to the received second instruction An optical parameter tester 130 of the FLICKER value; and a connection with the ARM debug board 120 and the optical parameter tester 130, and transmitting the first instruction and parameters to the ARM debug board 120, and transmitting the second command to the optical parameter test The host 140 of the meter 130. The ARM debugging board 120 is connected to the liquid crystal display module 110 through a PCB conversion board 150, and is connected to the host 140 through a serial line. The optical parameter tester 130 is connected to the host 140 via a USB cable. The host 140 includes a configuration parameter sending module 141 for transmitting the configuration parameter to the ARM debug board, and a method for transmitting the first command to the ARM debug board 120 to instruct the ARM debug board 120 to display the liquid crystal display mode according to the configuration parameter. The group 110 performs a first command sending module 142 for contrast and FLICKER debugging, and a contrast for transmitting the second command to the optical parameter tester 130 to instruct the optical parameter tester 130 to test the panel of the liquid crystal display module 110. And the second command transmission mode of the FLICKER value Block 143, and a test result display module 144 for analyzing and displaying the test results returned by the optical parameter tester 130. The liquid crystal display module FLICKER debugging system adopts the host 140 for automatic testing and debugging, instead of manual debugging, the relative manual operation improves the contrast ratio of the liquid crystal module and the debugging speed of the FLICKER value, but the liquid crystal display module FLICKER debugging system needs to be first The host 140 compiles, and for different platforms, it needs to be compiled in a targeted manner, and the compilation work is complicated and complicated.

Currently, the most primitive and time-consuming debugging method is divided into three steps: compiling, downloading, and testing. In order to avoid this inefficient debugging method, the platform code generally integrates a debugging interface for real-time debugging.

As shown in Figure 2, it is the current method of debugging the LCM under the MTK platform. In order to improve the practicability of the MTK platform, the MTK platform code integrates a set of LCM debugging interface named "fbconfig", and cooperates with the PC platform-side tool Panel Master to realize real-time debugging of the LCM initial code. The tool is simple and easy to use, but it is also very obvious. The interface code of the MTK platform is too complicated and difficult to understand. It is too difficult for the technician to modify the interface code, and the tool for debugging the windows side and the MTK platform should be used. Master has no source code, technicians can't modify it on the existing debugging interface of MTK platform, only a new interface can be opened to meet the demand, the workload is high, the difficulty is large, time-consuming and laborious, and the technician can not improve the debugging through the debugging interface. The purpose of efficiency.

In summary, the main problems of the existing LCM debugging interface are:

1) The platform dependency is too strong, the debug interface is completely dependent on the platform and cannot be ported to other platforms;

2) The code is large and complicated and difficult to understand;

3) The machine being debugged needs to download the complete root version software, which not only compiles time-consuming, but also downloads the machine with the full root version of the software. The operation is very smooth;

4) The mobile phone cannot sleep after writing the initial parameters of LCM, otherwise the LCM parameters will return to the original state when waking up;

5) The initial parameters cannot be read.

Disclosure of invention

The invention provides a liquid crystal display module driving debugging system and a debugging method, which have wide application range, simple script writing, and solve the problem that the debugging device is stuck.

To achieve the above object, the present invention provides a method for driving and debugging a liquid crystal display module, which is characterized in that the debugging method comprises:

The PC end inputs the original parameters in the driving file of the liquid crystal display module of the mobile terminal;

The PC side writes batch scripts according to requirements, and reads and writes raw parameters in batches.

The input of the original parameters in the driver file of the liquid crystal display module of the mobile terminal by the PC end includes:

Creating and defining a kernel file node for operating an array index, storing data, and reading raw parameters in a liquid crystal display module driver file;

Create a data structure and initialize the value of the data structure to match the original parameters;

Create a variable to store the value entered by the user;

The boot image of the eng version is compiled and downloaded to the mobile terminal of the liquid crystal display module being debugged.

The above kernel file node contains an array index node, a data node, and an original parameter node.

The above array index node permission defines the read and write, prints the array index of the current data structure when reading, and modifies the array index of the current data structure when writing.

The above data node permission defines the permission for reading and writing. When reading, the data in the current array index in the data structure is printed, and the value of the data structure at the current array index is modified when writing.

The above-mentioned original parameter node permissions are defined as read-only to print the original initialization parameters.

The debugging method further includes: before inputting the original parameters of the liquid crystal display module of the mobile terminal in the configuration file, the PC end establishes a connection with the mobile terminal.

The connection between the debugging control terminal and the mobile terminal includes:

Install the adb tool on the PC side;

The mobile terminal is connected to the PC via USB.

The above debugging method further includes: before inputting the original parameters of the liquid crystal display module of the mobile terminal in the configuration file, the mobile terminal downloads the root version of the boot image.

A liquid crystal display module driving debugging system for driving and debugging a liquid crystal display module, characterized in that the debugging system comprises:

An original parameter input module, which is connected to the mobile terminal, and inputs original parameters in a driving file of the liquid crystal display module;

A scripting module that connects to the mobile terminal, writes a batch script according to requirements, and reads and writes raw parameters of the driver file of the liquid crystal display module in batches.

Liquid crystal display module driving debugging system and debugging method and liquid crystal display of prior art Compared with the module debugging technology, the invention has the advantages that the driving file of the liquid crystal display module is configured, and the array index node, the data node and the original parameter node are created in the driving file for operating the array index, storing the data, and reading the original. Parameters, independent of the specific platform, can be ported to all platforms;

The invention also writes a batch processing script for batch reading and writing original parameters through the adb tool, the compiling principle is simple, and the code is easy to understand;

The mobile terminal debugged in the driver debugging method of the present invention only needs to download the boot image of the root version, and the boot image is compiled at a fast speed, thereby avoiding the problem that the full root version of the machine operates in a stuck state;

The invention compiles the boot image and writes the batch script through the adb tool, so that the script is written once, and is always valid, and only the restart will return to the original state, thereby improving the debugging efficiency.

The present invention creates and defines array index nodes, data nodes, and raw parameter nodes in the driver file to read the original and modified parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

1 is a system diagram of a contrast ratio of a prior art liquid crystal display module and a FLICKER debugging system;

2 is a flow chart of a method for debugging an LCM in a prior art MTK platform;

3 is a flow chart of a method for driving and debugging a liquid crystal display module according to the present invention;

4 is a flow chart of Embodiment 1 of a debugging flow in a method for driving and debugging a liquid crystal display module according to the present invention;

5 is a flow chart of Embodiment 2 of a debugging flow in a method for driving and debugging a liquid crystal display module according to the present invention;

6 is a block diagram of a first embodiment of a liquid crystal display module driving and debugging system suitable for driving and debugging a liquid crystal display module according to the present invention;

FIG. 7 is a block diagram of a second embodiment of a liquid crystal display module driving and debugging system suitable for driving and debugging a liquid crystal display module according to the present invention.

The best way to implement the invention

Specific embodiments of the present invention are further described below in conjunction with the accompanying drawings.

As shown in FIG. 3, the present invention discloses a liquid crystal display module driving debugging method, and the debugging method Specifically, it includes the following steps:

S310. The mobile terminal that needs to debug the liquid crystal display module driver downloads the root version of the boot image.

The mobile terminal can be a smart mobile device such as a smart phone or a tablet computer. In this embodiment, the Android system is taken as an example.

Boot.img is usually called "kernel", which belongs to the underlying file of the system. The boot image of Android system is not a file system in the ordinary sense, but a special Android custom format, which is boot header, compressed kernel, ramdisk and second. The stage loader (optional) is composed. It contains a channel for connecting the mobile phone system software and hardware. It includes cameras, cpu, gpu and other drivers. Generally speaking, the kernel provided by the official is relatively stable compared to the kernel of the third party. Generally, the upgrade of the kernel is the real upgrade of the system; the kernel file records the core functions of the underlying system and the role of connecting the hardware driver. Optimization can bring a qualitative leap to the system. The boot.img file can be modified. It is usually recommended to modify it in the Linux environment. Of course, we can also use the Windows system to decompress and simply modify some parameters.

The S320 and the PC end establish a communication connection with the mobile terminal driven by the liquid crystal display module.

S321, install the adb tool in the PC.

The full name of the adb tool is called Android Debug Bridge, which is the function of the Android system debugging bridge. As a developer, it is commonly used in this tool. With the adb tool, we can manage the status of the device or phone emulator. You can also do a lot of phone operations, such as installing software, uninstalling software, upgrading systems, running shell commands, and more. The adb tool is a bridge between the Android phone and the PC, allowing users to fully operate the phone on the computer.

S322. The mobile terminal and the PC end are connected through a USB interface.

S330 and the PC end input original parameters in a driving file of the liquid crystal display module of the mobile terminal.

S331. The PC side creates and defines three kernel file nodes for operating the array index, storing data, and reading the original parameters in the liquid crystal display module driver file. The three kernel file nodes are: array index node, data node and original parameter node, array index node, data node and original parameter node are defined as follows:

The array index node permission defines the read and write, prints the array index of the current data structure when reading, and modifies the array index of the current data structure when writing.

The data node permission defines the permission for reading and writing, and when reading, the current array is printed out in the data structure. The data that is referenced, the value of the data structure at the current array index is modified when writing.

The original parameter node permissions are defined as read-only to print the original initialization parameters.

S332: The PC end creates a data structure and initializes the value of the data structure to be consistent with the original parameters driven by the debug liquid crystal display module.

S333. The PC side creates a variable for storing the value input by the user.

S334, the PC side compiles the boot image of the eng version, and downloads to the mobile terminal driven by the debug liquid crystal display module through the USB connection.

S340, the PC side writes batch scripts according to requirements.

The S350 and the PC end send a batch processing script to the mobile terminal, and read and write the original parameters of the liquid crystal display module driver of the mobile terminal in batches, and perform debugging of the liquid crystal display module driver.

The debugging process of the S350 specific liquid crystal display module driver has the following two embodiments.

As shown in FIG. 4, it is a first embodiment of a debugging method for driving a liquid crystal display module. The debugging method specifically includes the following steps:

S401: Acquire original parameters in a driver file related to checking a liquid crystal display module (LCM) debugging effect of the mobile terminal.

Here, the driver file can be a txt document, that is, the file format of the driver file is .txt; the original driver file of the file format has the advantages of small size, simple and convenient storage, and strong versatility.

Here, the original parameters are generally provided by the manufacturer of the target terminal, and the specific form thereof is not limited.

Specifically, the target folder may be created in a specified directory of the mobile terminal, the driver file is stored in the target folder, the driver file is obtained from the target folder in the specified directory, and the original parameters in the driver file are read; In the way, when the original parameters are obtained, they can be directly read from the target folder in the specified directory, so that the original parameters can be quickly obtained.

Among them, the specified directory can be selected according to actual needs, and the file name of the target folder can be arbitrarily set.

In addition, the original parameters in the original driver file related to the display screen debugging effect of the target terminal can be acquired through the pre-developed terminal application.

S402: Convert the original parameter into a driving format required by the operating platform of the mobile terminal, and obtain a liquid crystal display module driving content of the mobile terminal.

Here, the display driving content refers to the code content after converting the original parameters.

In the original parameters, there will usually be spaces, tabs, and newlines. These are the destination terminals. Line platforms are not required, so it is generally necessary to remove spaces, tabs, and line breaks first.

In one embodiment, the original parameter is converted into a driving format required by the operating platform of the mobile terminal, and the step of obtaining the driving content of the liquid crystal display module of the mobile terminal may include the steps of: removing spaces, tabs, and line breaks in the original parameters. The symbol is obtained by the liquid crystal display module of the mobile terminal.

The blank space, the tab character, and the newline character can be used in any manner that can be implemented, and will not be described here.

In addition, the original parameters can be converted into the drive format required by the operating platform of the mobile terminal through a pre-developed terminal application.

S403. The liquid crystal display module driving content is transmitted from an application layer of the mobile terminal to a kernel layer of the mobile terminal.

Since the process of acquiring the original driver code and converting the original driver code occurs in the application layer of the mobile terminal, and the display effect debugging needs to be performed in the kernel layer of the mobile terminal, it is necessary to drive the liquid crystal display module of the mobile terminal. Content is transferred from the application layer of the mobile terminal to the kernel layer of the mobile terminal.

The content of the liquid crystal display module can be transmitted in any manner that can be implemented, and details are not described herein.

S404: Perform format conversion on the liquid crystal display module driving content transmitted to the kernel layer, and obtain the converted target driving code.

Specifically, the liquid crystal display module driving content transmitted to the kernel layer can be converted from hexadecimal data to decimal data to obtain the converted target driving code; in this way, it is considered that the original parameters are often serial. The data is generally hexadecimal data, and the data format required for the driving function of the liquid crystal display module is decimal data. Therefore, the liquid crystal display module driving content transmitted to the kernel layer needs to be first converted into a liquid crystal display module. The data format required by the driver function is to convert the driving content of the liquid crystal display module from hexadecimal data to decimal data.

S405: Write a target driver code (ie, a batch script) to a chip controller of the liquid crystal display module of the mobile terminal.

The method of writing the target drive code to the chip controller of the liquid crystal display module adopts a common code writing method, and will not be described here. When the target drive code is written to the liquid crystal display module chip controller of the mobile terminal, Perform display effect debugging and display the display display effect parameters.

According to the solution of the above embodiment, the display screen of the target terminal is obtained and viewed. The raw parameters in the original driver file related to the test effect are converted into the driving format required by the operating platform of the mobile terminal, and the driving content of the liquid crystal display module of the mobile terminal is obtained, and the content of the liquid crystal display module is driven from the mobile terminal. The application layer transmits to the kernel layer of the mobile terminal, performs format conversion on the liquid crystal display module driving content transmitted to the kernel layer, obtains the converted target driving code, and writes the target driving code to the liquid crystal display module chip controller of the mobile terminal. Because the R&D staff does not need to modify the code process and compile and download the software process during the debugging process, the tester can use this method to confirm the parameters of the final effect of the display, reduce the labor cost, and improve the work efficiency.

As shown in FIG. 5, it is a second embodiment of the debugging method for driving the liquid crystal display module. The debugging method specifically includes the following steps:

S501: Receive a first instruction triggered by a user, where the first instruction includes at least an address of a register of the liquid crystal display module to be tested.

The first instruction is a write instruction or a read instruction; if the first instruction is the write instruction, the first instruction includes at least an address of a register of the liquid crystal display module to be tested and a value of a register of the liquid crystal display module to be tested, and the write instruction is Write the value of the register of the liquid crystal display module to be tested to the register corresponding to the address of the register of the liquid crystal display module to be tested. If the first instruction is the read command, the first instruction includes at least an address of a register of the liquid crystal display module to be tested, and the read command is used to read a value of a register corresponding to the address of the register of the liquid crystal display module to be tested.

Specifically, if the user wants to read the data information of the screen of the mobile terminal, the read command may be input on the public interface, and the address of the register of the liquid crystal display module to be tested is carried in the read command, if the user wants to screen the mobile terminal The contents of the register are operated, and a write command can be input on the common interface, and the address of the register of the liquid crystal display module to be tested and the value of the register of the liquid crystal display module to be tested are carried in the write command.

S502: Receive a second instruction triggered by a user, where the second instruction includes at least a communication method of the liquid crystal display module to be tested.

Specifically, there are two communication modes of the liquid crystal display module to be tested, one is parallel and the other is mipi. If the user needs to test the liquid crystal display module to be tested, select one of the above two communication modes in advance to the public interface. For example, if the communication mode of the screen to be tested is parallel, the second instruction is input to the public interface, and the second instruction includes a parallel communication mode. If the communication mode of the current screen to be tested is mipi, the public The interface inputs a second instruction, the second instruction including a mipi way of communication.

S503. Send the first instruction to the register of the liquid crystal display module to be tested by using the communication method of the liquid crystal display module to be tested.

Preferably, the first instruction is sent to the register of the liquid crystal display module to be tested by the communication method of the liquid crystal display module to be tested, and includes: sending a write command to the parallel communication mode or the mipi communication mode to The register of the liquid crystal display module to be tested is sent to the register of the liquid crystal display module to be tested by the parallel communication mode or the mipi communication mode.

Specifically, if the first instruction is a write command, and the communication mode of the liquid crystal display module to be tested is a parallel communication mode or a mipi communication mode, the communication mode of the first instruction through the liquid crystal display module to be tested is a parallel communication mode. Or the mipi communication method is sent to the register of the liquid crystal display module to be tested. If the first instruction is a read command, and the communication mode of the liquid crystal display module to be tested is a parallel communication mode or a mipi communication mode, the communication mode of the first instruction through the liquid crystal display module to be tested is a parallel communication mode or The mipi communication method is sent to the register of the liquid crystal display module to be tested.

In the second embodiment, the first instruction triggered by the user receives at least the address of the register of the liquid crystal display module to be tested; the second instruction triggered by the user is received, and the second instruction includes at least the liquid crystal display module to be tested. The communication method is: sending the first instruction to the register of the liquid crystal display module to be tested through the communication method of the liquid crystal display module to be tested, thereby making a public interface for screen debugging by using a file system of the Linux operating system, which is applicable to All mobile terminal devices based on the Linux kernel can quickly and effectively debug through the public interface, saving time and effort, making the screen debugging based on the MTK platform-based mobile terminal products more convenient and faster.

As shown in FIG. 6 , the present invention also discloses a first embodiment of a liquid crystal display module driving and debugging system suitable for the above-mentioned liquid crystal display module driving and debugging method. The debugging system includes: an original parameter input module 601 and a script writing module 602. And debugging module 603.

The original parameter input module 601 is connected to the mobile terminal 604 for inputting the original parameters in the driving file of the liquid crystal display module.

The scripting module 602 is connected to the mobile terminal 604 for writing a batch script for debugging the liquid crystal display module according to requirements.

The debugging module 603 is connected to the mobile terminal 604 and the scripting module 602 for receiving the batch script, and batch reading and writing the original driving file of the liquid crystal display module of the mobile terminal 604 according to the batch processing script. Start parameters, thus completing the debugging of the liquid crystal display module driver.

The liquid crystal display module driving debugging system can be installed in the PC end or prepared as an independent hardware device.

As shown in FIG. 7 , it is a second embodiment of a liquid crystal display module driving and debugging system suitable for the above-mentioned liquid crystal display module driving and debugging method. The debugging system adopts a USB interface liquid crystal display module testing system, including a test PC end. And a test control circuit that works with the LCM being tested. The test PC has a driver that can identify the test control circuit, and provides an application programming interface API function to the application software to call, and the USB interface provides power to the test control circuit and transmits the data of the PC.

The test control circuit is provided with a microcontroller (MCU) 702 carrying firmware firmware, and a complex programmable logic device CPLD 703 with an interface connected to the tested LCM 3 interface, and the microcontroller MCU 702 is connected to the USB interface 701. The complex programmable logic device CPLD 703 is connected to the PB and PD data transmission ports of the microcontroller MCU 702, and decodes data transmitted from the PC end to the microcontroller MCU 702 through the USB interface 701, corresponding to different LCMs and LCMs. The working mode respectively forms a corresponding data format to drive the LCM, and displays the corresponding format of the video or picture on the LCM screen.

The initialization value of the tested LCM is sent to the corresponding register of the LCM driver chip by the user through the application software on the test PC side to initialize it.

The peripheral circuit of the microcontroller MCU 702 includes an E2PROM 704, a power conversion circuit 705, a reset circuit 706, a wake-up circuit 707 and a crystal oscillation circuit 708 respectively connected thereto. The power conversion circuit 705 is also connected to the USB interface 701 and the complex programmable logic device CPLD 703, respectively. And connected to the tested LCM interface. The microcontroller MCU 702 has PA, PC and PE control ports and PB, PD data transmission ports.

The firmware firmware of the microcontroller MCU 702 is a program that the microcontroller MCU 702 automatically downloads from the E2PROM 704 after the PC interface is the default device through the USB interface, and the initialization of the microcontroller MCU 702 is completed by the TD_Init() function. The transmission mode is established by the TD_Poll() function, which is used to enumerate the test control circuit to identify it by the operating device on the PC side, and establish a channel for transmitting data. The firmware of the microcontroller MCU 702 mainly includes a device descriptor table, a task assignment, a device request, and a USB interrupt, wherein task assignment is the focus. The transmission method established by the TD_Poll() function is the GPIF FIFO mode.

Microcontroller MCU 702 uses the integrated USB2.0 interface from Cypress The CY7C series control chip, which contains the firmware firmware, is written by the basic structure provided by Cypress.

The complex programmable logic device CPLD703 adopts the single-chip programmable peripheral chip PSD with the JTAG interface 709 of the model XC9536 produced by XILINX. The JTAG interface 709 is a 4-wire: TMS, TCK, TDI, TDO, which are mode selection, clock, data input, and data output lines, respectively.

Although the present invention has been described in detail by the preferred embodiments thereof, it should be understood that the foregoing description should not be construed as limiting. Various modifications and alterations of the present invention will be apparent to those skilled in the art. Therefore, the scope of the invention should be defined by the appended claims.

Claims

A liquid crystal display module driving debugging method, characterized in that the debugging method comprises:

The PC end inputs the original parameters in the driving file of the liquid crystal display module of the mobile terminal;

The PC side writes batch scripts according to requirements, and reads and writes raw parameters in batches.
The method for driving and debugging a liquid crystal display module according to claim 1, wherein the inputting the original parameters in the driving file of the liquid crystal display module of the mobile terminal by the PC end comprises:

Creating and defining a kernel file node for operating an array index, storing data, and reading raw parameters in a liquid crystal display module driver file;

Create a data structure and initialize the value of the data structure to match the original parameters;

Create a variable to store the value entered by the user;

The boot image of the eng version is compiled and downloaded to the mobile terminal of the liquid crystal display module being debugged.
The method for driving and debugging a liquid crystal display module according to claim 2, wherein the kernel file node comprises an array index node, a data node, and an original parameter node.
The method for driving and debugging a liquid crystal display module according to claim 3, wherein the array index node permission defines a read/write, prints an array index of the current data structure during reading, and modifies an array of the current data structure when writing. index.
The method for driving and debugging a liquid crystal display module according to claim 3, wherein the data node permission defines a right for reading and writing, and the data in the current array index in the data structure is printed when reading, and is modified at the time of writing. The value of the data structure at the current array index.
The method for driving and debugging a liquid crystal display module according to claim 3, wherein the original parameter node permission is defined as read-only to print the original initialization parameter.
The method for driving and debugging a liquid crystal display module according to claim 1, wherein the debugging method further comprises: establishing a connection between the PC end and the mobile terminal before inputting the original parameters of the liquid crystal display module of the mobile terminal in the configuration file. .
The method for driving and debugging a liquid crystal display module according to claim 7, wherein the establishing of the connection between the debug control terminal and the mobile terminal comprises:

Install the adb tool on the PC side;

The mobile terminal is connected to the PC via USB.
The method for driving and debugging a liquid crystal display module according to claim 1, wherein the debugging method further comprises: before inputting the original parameters of the liquid crystal display module of the mobile terminal in the configuration file, the mobile terminal downloads the boot of the root version. Image.
A liquid crystal display module driving debugging system suitable for driving and debugging a liquid crystal display module according to any one of claims 1-9, wherein the debugging system comprises:

An original parameter input module, which is connected to the mobile terminal, and inputs original parameters in a driving file of the liquid crystal display module;

A scripting module that connects to the mobile terminal, writes a batch script according to requirements, and reads and writes raw parameters of the driver file of the liquid crystal display module in batches.