POST Debugging Using Phase Number and GUID for Driver Identification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing POST debugging methods face challenges in identifying interrupted firmware drivers due to redundant identification numbers from different vendors, leading to misunderstandings during the debugging process.

Innovation Solution

A method and apparatus that set a phase number and obtain a GUID for selected drivers, allowing recognition of interrupted drivers by storing or outputting these identifiers, enabling accurate debugging by executing the drivers and utilizing a processing unit with a cache and volatile memory to manage driver execution and initialization phases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If driver identification numbers from different vendors are used in POST debugging, then driver execution can be tracked, but identification redundancy leads to misunderstanding of interrupted firmware

Engineering Contradiction:

Improvedriver identification accuracyVSAvoiddriver identification clarity

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent changes the identification parameter from vendor-specific driver IDs to a standardized combination of phase number and GUID. This parameter transformation eliminates redundancy while maintaining the ability to uniquely identify each driver instance across different vendors and execution phases.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent creates a universal identification mechanism using phase number and GUID that works across all vendor drivers. This multi-functional identifier system replaces multiple vendor-specific ID schemes, providing a single standardized method for identifying drivers regardless of their source or type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple vendor drivers are executed in POST, then comprehensive hardware testing is achieved, but redundant identification numbers cause debugging misunderstandings

Engineering Contradiction:

Improvemulti-vendor driver compatibilityVSAvoiddebugging clarity

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent transforms the identification system by changing from vendor-specific parameters to a universal phase-GUID parameter structure. This allows the system to maintain compatibility with multiple vendor drivers while simplifying the debugging operation through consistent, non-redundant identification.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent introduces phase number and GUID as intermediary identifiers that mediate between diverse vendor drivers and the debugging system. These intermediaries provide a common interface for driver identification, eliminating the confusion caused by direct use of vendor-specific identification numbers.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9465707B2POST (power-on-self-test) debugging method and apparatuses using the same

Publication Date: 2016.10.11 WISTRON CORP

AI summary

The invention introduces a POST (power-On-Self-Test) debugging method, executed by a processing unit, which contains at least the following steps. A phase number indicative of a current POST phase is set. A driver is selected from a scheduled queue. A GUID (Globally Unique Identifier) of the driver is obtained. The phase number and the GUID are stored or output, so as to recognize the phase of the driver being interrupted upon a break point of the driver. After that, the driver is executed.