Debugging system and driver to be applied to the same

The debug system addresses the inefficiencies of conventional debugging by allowing direct log transmission and remote debugging through a driver-host architecture, improving error detection and firmware updates in electronic systems.

JP2024160042AActive Publication Date: 2024-11-11HIMAX TECH LTD
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2024016332
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-04-29
Filing Date
2024-02-06
Publication Date
2024-11-11
Estimated Expiration
2044-02-06

AI Technical Summary

Technical Problem

Conventional debugging techniques are inadequate for addressing errors and failures in electronic systems, particularly in TDDI circuits and complex SoC devices, and do not support immediate or remote debugging.

Method used

A debug system with a driver and host architecture that enables direct transmission of debug logs via drive and host generic I/Os, eliminating the need for handshake signals, utilizing UART protocol for asynchronous communication.

Benefits of technology

Enables immediate and remote debugging by directly transmitting debug logs, facilitating error detection and firmware updates, enhancing debugging efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024160042000001_ABST
    Figure 2024160042000001_ABST
Patent Text Reader

Abstract

To provide a debugging system and a driver to be applied to the same.SOLUTION: A driver to be applied to a debugging system includes a drive controller and a drive universal input / output controlled by the drive controller. The drive universal input / output directly transmits a debug log of a status message of a touch screen to a host universal input / output of a host, and there is no need to exchange a handshake signal between the driver and the host.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a debugging system, and more particularly to a debugging system for use in an in-vehicle touch screen. [Background technology]

[0002] In-vehicle touchscreens are becoming increasingly popular and are gradually replacing traditional physical buttons in vehicles, allowing users to control various vehicle functions such as navigation, radio, weather forecast, and various settings in a more flexible and flexible manner. Summary of the Invention [Problem to be solved by the invention]

[0003] However, electronic systems are more prone to errors and failures than physical buttons, and therefore require debugging (i.e., searching for and resolving errors or problems that prevent correct operation) to ensure proper operation and meet user needs. Unfortunately, traditional debugging techniques are unable to resolve issues immediately or remotely, especially for touch and display driver integration (TDDI) circuits. TDDI circuits are a technology that integrates a display driver and a touch control driver onto a single chip. In addition to TDDI circuits, other technologies also required new debugging methods. For example, system-on-chip (SoC) devices have become increasingly complex, making it difficult to debug using traditional debugging methods.

[0004] The inventors therefore believed that the shortcomings of the conventional debugging system could be improved, and as a result of extensive research, they came up with the proposal of the present invention, which effectively improves the above-mentioned problems through a rational design.

[0005] The present invention has been made in view of the above circumstances, and aims to solve the above problems as an example of an objective of the present invention. That is, an objective of the present invention is to provide a debugging system that remotely and instantly acquires a debug log of a status message and performs debugging remotely. [Means for solving the problem]

[0006] In order to solve the above problems, a debug system according to one aspect of the present invention includes a driver and a host. The driver controls a touch screen and includes a drive generic input / output. The host receives a debug log of a status message from the driver and includes a host generic input / output. The drive generic input / output directly transmits the debug log to the host generic input / output, and there is no need to exchange handshake signals between the driver and the host. [Brief description of the drawings]

[0007] [Figure 1] 1 is a block diagram showing a debugging system according to an embodiment of the present invention; [Figure 2A] 2 illustrates a data format of a universal asynchronous receiver-transmitter (UART) protocol according to one embodiment of the present invention. [Figure 2B] 1 is a waveform illustrating the transmission of the alphabet "A" using a universal asynchronous receiver-transmitter (UART) protocol according to one embodiment of the present invention. [Figure 2C] Several baud rates are given, along with associated durations. [Diagram 3] 1 is a block diagram showing a debugging system according to an embodiment of the present invention (in a state in which the mechanism of FIG. 1 is not used). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the embodiments of the present invention will be described in detail. However, the present invention is not limited to these, and various modifications are possible within the scope of the description. The technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments.

[0009] 1 is a block diagram showing a debugging system 100 according to an embodiment of the present invention. The debugging system 100 according to the present embodiment is applicable to an in-vehicle touch screen, allowing users to control various vehicle functions, such as navigation, radio, weather forecast, and settings for car applications.

[0010] The debug system 100 comprises a driver 11 for controlling an (in-vehicle) touch screen 12. In this embodiment, the driver 11 comprises a touch and display driver integration (TDDI) circuit in which a touch control driver and a display driver are combined in a single chip, and is used to control a touch screen 12 such as the in-vehicle touch screen of this embodiment.

[0011] The driver 11 according to this embodiment includes a drive controller 111, such as a microcomputer unit (MCU) applied in an embedded design. The driver 11 includes a drive memory device 112, such as a static RAM (SRAM), which is used to store data received from or transmitted to the drive controller 111. The driver 11 includes a drive general-purpose input and output (GPIO) 113 controlled by the drive controller 111. The general-purpose input and output is a (digital) signal pin of the drive controller 111 that serves as a controllable input or output.

[0012] The debug system 100 includes a host 13 (e.g., a PC) that is used to receive a debug log containing status (or error) messages (from the driver 11) to assist the developer in identifying and fixing errors. In this embodiment, the host 13 is an in-vehicle system or application processor (AP) for vehicle applications.

[0013] The host 13 according to this embodiment includes a host controller 131, such as a microcomputer unit (MCU) applied in an embedded design. The host 13 includes a host memory device 132, such as a dynamic random access memory (DRAM), which is used to store data received from or transmitted to the host controller 131. The host 13 includes a host general purpose input / output (GPIO) 133 controlled by the host controller 131. The general purpose input / output is a (digital) signal pin of the host controller 131 that serves as a controllable input or output.

[0014] According to one aspect of this embodiment, the drive generic input / output 113 (of the driver 11) transmits debug logs of status messages directly to the host generic input / output 133 (of the host 13) via a unidirectional bus, without the need for any handshake signals to be exchanged (in advance) between the driver 11 and the host 13.

[0015] In one embodiment, the status message is coded according to ASCII (American Standard Code for Information Interchange), which uses 8 bits to represent letters, numbers, and symbols. For example, the letter "A" is represented in ASCII (American Standard Code for Information Interchange) as 01000001 in binary (or 41 in hexadecimal, or 65 in decimal).

[0016] In this embodiment, the drive universal input / output 113 and the host universal input / output 133 adopt asynchronous serial communication such as a universal asynchronous receiver-transmitter (UART) protocol, and do not need to be synchronized by a clock frequency signal. The drive universal input / output 113 transmits a status message to the host universal input / output 133 one bit at a time, and includes a start bit and a stop bit. The status message is then displayed on the touch screen 12. FIG. 2A illustrates a data format of the universal asynchronous receiver-transmitter (UART) protocol according to an embodiment of the present invention. FIG. 2B illustrates a waveform of the alphabet "A" transmitted using the universal asynchronous receiver-transmitter (UART) protocol according to an embodiment of the present invention.

[0017] In this embodiment, the transmission of status messages employs the Universal Asynchronous Receiver Transmitter (UART) protocol with different transmission rates. Figure 2C shows the transmission rates and associated durations for several baud rates (or bits per second).

[0018] 3 is a block diagram showing a debug system 300 according to an embodiment of the present invention (without using the mechanism of FIG. 1). In operation, the inter-integrated circuit (I2C) 331 of the in-vehicle system 33 sends an access command to the inter-integrated circuit (I2C) 311 of the TDDI circuit 31. The inter-integrated circuit (I2C) 311 then parses or analyzes the access command, which is executed by the microcomputer unit (MCU) 312 of the TDDI circuit 31, and transmits a status message to the inter-integrated circuit (I2C) 331 of the in-vehicle system 33. The status message is displayed on the touch screen 32. Thus, the TDDI circuit 31 and the in-vehicle system 33 exchange handshaking signals (or access commands) to establish a communication connection before transmitting each of the status messages.

[0019] Compared with the debug system 300 (see FIG. 3), the debug system 100 (see FIG. 1) according to this embodiment immediately acquires a debug log of a status message. However, the debug system 300 can only passively acquire a status message because a handshake signal is exchanged between the TDDI circuit 31 and the in-vehicle system 33. After receiving the debug log, the debug system 100 according to this embodiment remotely detects an error and updates the firmware of the driver 11 as necessary. In this way, remote debugging is realized, but the debug system 300 can only perform on-site debugging.

[0020] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. [Explanation of symbols]

[0021] 100 Debugging System 11 Driver 111 Drive Controller 112 Drive Memory Device 113 Drive Universal Input / Output 12. Touchscreen 13 Host 131 Host Controller 132 Host Memory Device 133 Host Generic Input / Output 300 Debugging System 31 Touch display driver integrated circuit 311 Integrated Bus Circuit 312 Microcomputer Unit 32 Touchscreen 33 In-vehicle systems 331 Integrated Bus Circuit

Claims

1. a driver for controlling a touch screen, the driver including a driver generic type input / output; a host receiving a debug log of status messages from the driver, the host including a host generic input / output; The debug system according to claim 1, wherein the drive generic input / output transmits the debug log directly to the host generic input / output, eliminating the need for exchanging handshake signals between the driver and the host.

2. The driver is a drive controller for controlling the drive generic input / output; 2. The debugging system of claim 1, further comprising: a drive memory device for storing data received from the drive controller or data transmitted to the drive controller.

3. The host is a host controller for controlling the host generic input / output; 2. The debugging system of claim 1, further comprising: a host memory device for storing data received from the host controller or data transmitted to the host controller.

4. 2. The debugging system according to claim 1, wherein the status message is encoded in ASCII.

5. 2. The debugging system of claim 1, wherein the drive generic input / output and the host generic input / output adopt a Universal Asynchronous Receiver Transmitter (UART) protocol.

Citation Information

Patent Citations

  • Debugging method for program type display device

    JP1999015697A

  • Techniques for detecting race conditions

    JP2017503233A

  • Debugging applications at resource constrained virtual machines using dynamically installable lightweight agents

    US20070113218A1

  • Techniques to enable integrated circuit debug across low power states

    US20220018901A1

  • Embedded product, method for displaying embedded product information and computer readable medium

    US20220113850A1