Embedded Controller Secure Diagnostics Messaging Between Firmware and UEFI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no mechanism available for communicating suspected hardware failures between the firmware, operating system, and Unified Extensible Firmware Interface (UEFI) in existing processor architectures, leading to user uncertainty and unnecessary support calls when hardware issues are misidentified as software problems.
Innovation Solution
A system utilizing an embedded controller to facilitate secure messaging between firmware, operating systems, and UEFI payloads, enabling the exchange of diagnostics information and allowing for differentiated corrective actions based on hardware or software errors, thereby eliminating user guesswork and reducing support calls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If no communication mechanism is available between firmware, operating system, and UEFI, then system security and isolation are maintained, but hardware failure information cannot be exchanged and user guidance is lost
Solution Approach 1:
The patent introduces an embedded controller as an intermediary component that mediates communication between the firmware, operating system, and UEFI payload. The embedded controller receives error information from firmware or operating system, stores it in a designated memory location, and enables the UEFI payload to retrieve and display this information to the user. This intermediary approach allows controlled information exchange without requiring direct communication channels between all components, thus maintaining system isolation while enabling necessary diagnostics.
2Loss of information
If hardware error information is communicated to UEFI payload, then accurate hardware failure detection is achieved, but system architecture complexity increases
Solution Approach 1:
The patent segments the error information handling process into distinct stages and components: (1) error detection by firmware or operating system, (2) error information storage in a designated memory location, (3) UEFI payload retrieval of the error information, and (4) user presentation of the error type. This segmentation allows each component to perform its function independently without requiring complex inter-component communication protocols, thereby reducing overall system complexity while enabling complete error information flow.
Data Source
AI summary
A system for secure processing of intra-processor data comprising firmware configured to operate on a processor. An operating system configured to operate on the processor. Payload configured to operate on the processor. An embedded controller coupled to the firmware, the operating system and the payload, wherein the embedded controller is configured to enable messaging between the firmware, the operating system and the payload.