Embedded Controller OS-Specific Chip Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Information Handling Systems (IHS) face challenges in diagnostics, recovery, and serviceability due to reduced functionality during hardware failures, often requiring costly whole unit service dispatches, as different Operating Systems (OS) have distinct hardware and firmware component requirements, limiting pre-boot services.

Innovation Solution

The implementation of an Embedded Controller (EC) with multiple OS-specific chips allows for dynamic switching between boot procedures, enabling pre-OS recovery and service environments by activating appropriate OS-specific chips based on user interface devices, thereby providing modular hardware architecture and pre-OS tools without modifying existing firmware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If an IHS uses OS-specific hardware and firmware components with reduced functionality, then the system can be optimized for specific operating systems, but diagnostics and recovery capabilities are limited when hardware failures occur

Engineering Contradiction:
ImproveOS-specific optimizationVSAvoidDiagnostics and recovery capability
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The patent segments the boot firmware into multiple independent images stored in the same flash memory, with each image tailored to a specific operating system. The Embedded Controller can selectively load different firmware images based on detected hardware configurations or failure scenarios, enabling both OS-specific optimization and cross-OS recovery capabilities without requiring separate hardware for each scenario.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If an IHS is configured with reduced functionality pre-OS environment, then the system can support specific OS requirements, but serviceability and field-replaceable component diagnostics are compromised

Engineering Contradiction:
ImproveOS-specific hardware supportVSAvoidServiceability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements a universal flash memory component that can store multiple OS-specific firmware images and a pre-OS service environment. The Embedded Controller acts as a universal manager that can load and execute different firmware images based on the detected operating system or failure scenario, providing both OS-specific functionality and universal serviceability through a single hardware component.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If different OS-specific chips are used, then each OS can have optimized boot procedures, but the device complexity increases

Engineering Contradiction:
ImproveMultiple OS boot supportVSAvoidNumber of OS-specific chips
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple OS-specific firmware images into a single flash memory device, eliminating the need for separate physical chips for each operating system. The Embedded Controller combines the functionality of multiple OS-specific boot loaders into one unified component that can dynamically select and load the appropriate firmware image based on hardware detection or user input, reducing device complexity while maintaining multiple OS support.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10789074B2Providing pre-boot services in an information handling system having operating system-specific hardware and/or firmware components
Publication Date: 2020.09.29 DELL PROD LP
  • US10789074B2 patent drawing
  • US10789074B2 patent drawing
  • US10789074B2 patent drawing

AI summary

Systems and methods for providing pre-boot services in an Information Handling System (IHS) having Operating System (OS)-specific hardware and/or firmware components. In some embodiments, an IHS may include an Embedded Controller (EC), a first Operating System (OS)-specific chip coupled to the EC, and a second OS-specific chip coupled to the EC, where the EC is configured to cause the IHS to: in a first mode of operation, perform a first boot procedure using the first OS-specific chip; and in a second mode of operation, perform a second boot procedure using the second OS-specific chip.