Pre-Boot SoC Configuration GUI for Heterogeneous Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack efficient and platform-agnostic methods for configuring a System-on-Chip (SoC) during the boot process of an Information Handling System (IHS), particularly for heterogenous computing platforms, which can vary significantly in hardware and software components.

Innovation Solution

The system employs a Basic Input Output System (BIOS) to select and render graphical user interface elements during the boot device selection phase, based on SoC identifiers, enabling users to change settings before the Operating System takes control, using pre-boot program instructions to manage settings like processor thresholds, security parameters, and accessibility features.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standardized configuration method is implemented for SoC during boot, then platform-agnostic configurability is improved, but device complexity increases due to need to support multiple SoC types and identifiers

Engineering Contradiction:
Improveplatform-agnostic configurabilityVSAvoidconfiguration system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The BIOS configuration system is designed to universally support multiple SoC types through a common interface. The system uses SoC identifiers to automatically detect and adapt to different processor types (CISC, RISC, heterogeneous architectures) while presenting a unified configuration methodology that works across all platforms, eliminating the need for platform-specific configuration tools.

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

Solution Approach 2:

The system dynamically changes configuration parameters based on the detected SoC identifier. Different graphical elements, settings, and configuration options are selected and rendered according to the specific SoC type, allowing a single standardized interface to adapt its behavior to match the underlying hardware capabilities.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If pre-boot configuration options are added to BIOS, then user interaction and security configuration are improved, but boot time increases due to additional GUI rendering and element selection

Engineering Contradiction:
Improveuser configuration capabilityVSAvoidboot time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-rendering configuration graphical elements and pre-configuring default settings based on the detected SoC identifier before the user needs to make changes. This allows the configuration interface to be ready and functional immediately when the user accesses it during boot, minimizing the time required for configuration setup.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides partial configuration capabilities during boot by offering only the most critical and commonly needed settings (processor thresholds, security parameters, accessibility features) rather than all possible configuration options. This selective approach reduces the amount of GUI elements that need to be rendered and processed, thereby reducing boot time while maintaining essential user interaction capabilities.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If security metrics are used to control GUI elements, then system security is improved, but device complexity increases due to additional security evaluation mechanisms

Engineering Contradiction:
Improvesystem securityVSAvoidsecurity evaluation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service security evaluation where the BIOS automatically assesses security metrics related to the detected SoC and autonomously determines which configuration graphical elements should be rendered. This eliminates the need for complex external security evaluation systems or manual security configurations, as the BIOS itself performs the security assessment and applies appropriate access controls.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250377901A1Systems and methods for configuring a system-on-chip during boot of an information handling system
Publication Date: 2025.12.11 DELL PROD LP
  • US20250377901A1 patent drawing
  • US20250377901A1 patent drawing
  • US20250377901A1 patent drawing

AI summary

Systems and methods for configuring a System-on-Chip (SoC) during boot of an Information Handling System (IHS). In an illustrative, non-limiting embodiment, an IHS may include a SoC and a memory coupled to the SoC, the memory having program instructions stored thereon that, upon execution, cause the IHS to: during pre-boot, select one or more elements of a Graphical User Interface (GUI) by a Basic Input Output System (BIOS) based, at least in part, upon an identifier of the SoC, where the one or more elements enable a user to change one or more settings of the SoC before any Operating System (OS) takes control of the IHS; and render the GUI to the user.