Touch Firmware Selection by Host OS for Safer Boot Loader Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional touch firmware is general-purpose and supports multiple operating systems, leading to incorrect updates and inefficient management due to the need for comprehensive modifications across all systems, which can result in errors and inefficiencies.

Innovation Solution

A touch system with a nonvolatile memory storing multiple firmware versions tailored for specific operating systems, a boot loader to identify the host OS, and a volatile memory to upload the appropriate firmware for communication and coordinate calculation, ensuring compatibility and efficient management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If general-purpose firmware supporting multiple operating systems is used, then versatility across different OS is improved, but firmware management complexity and update error risk increase

Engineering Contradiction:
Improvefirmware compatibilityVSAvoidfirmware management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The firmware is segmented into OS-specific versions (first touch firmware for first OS, second touch firmware for second OS, etc.) stored in separate storage areas. The boot loader divides the single firmware functionality into multiple specialized firmware components, each optimized for a specific operating system, thereby reducing management complexity while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The boot loader acts as an intermediary between the multiple OS-specific firmwares and the host system. It automatically identifies the host OS and selects the appropriate firmware version, eliminating the need for manual firmware selection and reducing the risk of updating the wrong firmware. This mediator approach resolves the contradiction by providing automatic adaptation without requiring complex user management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive firmware updates covering all operating systems are performed, then all OS compatibility is maintained, but update time and processing overhead increase

Engineering Contradiction:
ImproveOS compatibilityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of updating all firmware versions comprehensively, the system performs partial updates by selectively applying updates only to the firmware version corresponding to the detected host OS. The boot loader identifies the active OS and updates only the relevant firmware (e.g., first touch firmware for first OS), avoiding unnecessary updates to other versions, thereby reducing update time while maintaining reliability for the current system.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The boot loader performs preliminary identification of the host OS before the firmware update process begins. By pre-determining which firmware version is needed based on the detected operating system, the system can prepare and apply the correct update package in advance, avoiding time-consuming trial-and-error updates and ensuring the correct firmware is updated first.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If all communication protocols and touch coordinate standards for various operating systems are included in one firmware, then broad support is achieved, but firmware size and modification complexity increase

Engineering Contradiction:
ImproveOS support coverageVSAvoidfirmware size
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The firmware functionality is segmented into separate OS-specific versions, each containing only the communication protocols and touch coordinate standards necessary for its designated operating system. The first touch firmware contains protocols for the first OS, the second touch firmware contains protocols for the second OS, and so on. This segmentation reduces the quantity of code in each firmware instance while maintaining overall versatility through multiple specialized versions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each firmware version is optimized with local quality tailored to its specific operating system target. The first touch firmware has communication protocols and coordinate standards specifically adapted for the first OS, the second touch firmware has protocols adapted for the second OS, etc. This localized optimization ensures each firmware is compact and efficient for its purpose without carrying unnecessary code for other systems.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12468548B2Touch sensing system and method for selectively operation touch firmware driver dependencies while applying updated from boot loader
Publication Date: 2025.11.11 SILICON WORKS CO LTD
  • US12468548B2 patent drawing
  • US12468548B2 patent drawing
  • US12468548B2 patent drawing

AI summary

The present disclosure relates to a touch system and a method for selectively operating firmware. In particular, it relates to a touch system and a method for selectively operating touch firmware in a touch device by storing a number of pieces of touch firmware supporting a number of host operating systems (OS) respectively in different storing areas of a nonvolatile memory, identifying a host OS installed in the host through communication with the host, and selectively operating the touch firmware supporting the identified host OS.