Touchscreen Driver GPIO Debug Logging for Real-Time Remote Diagnosis

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional debugging techniques are inadequate for real-time and remote debugging of automotive touchscreens, particularly for touch and display driver integration (TDDI) and system-on-chip (SoC) devices, as they require handshaking and are not adaptable for remote or real-time error detection and resolution.

Innovation Solution

A debugging system comprising a driver and a host with direct, unidirectional GPIO communication via UART protocol, allowing real-time and remote transfer of debug logs without handshaking, enabling remote debugging and firmware updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional debugging techniques are used, then debugging can be performed with traditional methods, but real-time and remote debugging capability is lost

Engineering Contradiction:

Improvedebugging capabilityVSAvoidremote debugging accessibility

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary communication mechanism using GPIO pins and UART protocol as a mediator between the driver and host. This intermediary layer enables remote debugging by transmitting debug logs through a serial communication interface, allowing developers to access system status and error information without direct physical access to the device.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If handshaking protocol is used between driver and host, then communication reliability is improved, but real-time debugging speed is reduced

Engineering Contradiction:

Improvecommunication reliabilityVSAvoiddebug log transfer speed

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The patent extracts the handshaking protocol from the debug log transmission process. By separating the data transmission function from the handshaking control, the system allows debug logs to be transmitted continuously through GPIO/UART without waiting for handshaking acknowledgments, thereby achieving real-time debugging speed while maintaining communication reliability through separate error handling mechanisms.

Inventive Principle:

Principle #2Taking out (Extraction)

3Ease of manufacture

If traditional debugging methods are used, then existing debugging infrastructure can be utilized, but adaptability to TDDI and SoC devices is insufficient

Engineering Contradiction:

Improvedebugging infrastructure compatibilityVSAvoidadaptability to TDDI and SoC

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal debugging interface using standard GPIO pins and UART protocol that can be applied across different device types including TDDI and SoC devices. This multi-functional approach allows the same debugging mechanism to work with various integrated circuit architectures, enhancing adaptability while utilizing existing debugging infrastructure and communication protocols.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP4455889A1Debugging system and a driver adaptable thereto

Publication Date: 2024.10.30 HIMAX TECH LTD

Figure 1
Figure 2A~2C
Figure 3

AI summary

A driver adaptable to a debugging system includes a driver controller, and a driver general-purpose input and output (GPIO) controlled by the driver controller. The driver GPIO directly transfers a debug log of status messages of a touchscreen to a host general-purpose input and output (GPIO) of a host without handshaking between the driver and the host.