Shared Non-Volatile Memory for BMC and BIOS Booting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computing systems typically require separate non-volatile memory modules for booting sequences of the BIOS and BMC, leading to suboptimal use of physical space on the motherboard and increased costs due to redundant hardware.
Innovation Solution
A computing system design that uses a single non-volatile memory module with distinct boot partitions for BIOS and BMC, where the BMC selects and switches between these partitions using a multiplexer, allowing shared access while ensuring no data collision during booting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate non-volatile memory modules are used for BIOS and BMC booting, then reliability is improved by ensuring dedicated storage for each controller, but device complexity increases and physical space on the motherboard is wasted
Solution Approach 1:
The patent merges the previously separate non-volatile memory modules for BIOS and BMC into a single shared non-volatile memory module. This consolidation reduces the total number of memory modules while maintaining dedicated booting functionality for both controllers through partitioning and switching mechanisms.
Solution Approach 2:
The shared non-volatile memory module is segmented into distinct partitions: a first non-volatile memory partition for BIOS booting and a second non-volatile memory partition for BMC booting. This segmentation ensures that each controller has dedicated storage space while sharing the same physical memory module.
2Reliability
If separate non-volatile memory modules are used for BIOS and BMC, then data collision is prevented during booting, but manufacturing cost increases due to redundant hardware
Solution Approach 1:
The patent introduces a dynamic switching mechanism using a multiplexer that routes booting sequences to the appropriate memory partition based on real-time conditions. The multiplexer switches between the first partition for BIOS booting and the second partition for BMC booting, preventing data collision while sharing a single memory module.
Solution Approach 2:
The multiplexer acts as an intermediary component that manages access to the shared non-volatile memory module. It mediates between the BIOS and BMC booting processes, ensuring that only one controller accesses the memory at a time, thus preventing data collision without requiring separate memory modules.
3Area of stationary object
If a single non-volatile memory module is shared between BIOS and BMC, then physical space is optimized and hardware cost is reduced, but access conflict may occur during simultaneous booting
Solution Approach 1:
The multiplexer provides dynamic access control to the shared non-volatile memory module, switching connections based on which controller (BIOS or BMC) needs to boot at any given time. This dynamic switching prevents access conflicts while enabling both controllers to share the same memory resource.
Solution Approach 2:
The single non-volatile memory module is designed with multi-functionality, serving both BIOS and BMC booting requirements through distinct partitions. The memory module universally supports both controllers' booting sequences, eliminating the need for separate dedicated memory modules.
Data Source
AI summary
A computing system is provided. The computing system includes a central processing unit (CPU), a baseboard management controller (BMC), and a boot non-volatile memory. The BMC selects a boot partition in the computing system. The boot non-volatile memory stores at least two boot partitions as a primary boot area including a basic input/output system (BIOS) image and a secondary boot area including a BMC image. The BMC switches between the secondary boot area to boot the BMC and the primary boot area to boot the BIOS. Only one of the primary boot area or the secondary boot area is accessible when the BIOS is booting or when the BMC is booting.