Granted Patent B2

US 12,306,952 · App. 17/793,664 · Granted May 20, 2025

Inventors: Glen Douglas Dower (Fort Collins, CO); Peter Seiler (Fort Collins, CO)

Assignee: Hewlett-Packard Development Company, L.P.

G06F21/575G06F21/572G06F2221/033

Abstract

Claims (52)

1. A computing device comprising:

a hardware component;

a read-only memory (ROM) storing firmware code for the hardware component and second firmware code for a second hardware component; and

a firmware controller directly physically connected to the hardware component, the second hardware component, and the ROM, the firmware controller to expose (i) a virtual ROM link to the hardware component over which the hardware component is to access the firmware code and (ii) a second virtual ROM link to the second hardware component over which the second hardware component is to access the second firmware code,

wherein the firmware controller is to:

perform secure boot authentication of the firmware code stored on the ROM prior to permitting the hardware component to access the firmware code over the virtual ROM link;

perform secure boot authentication of the second firmware code stored on the ROM prior to permitting the second hardware component to access the second firmware code over the second virtual ROM link;

control starting of the hardware component so that the hardware component remains unstarted until the firmware controller has successfully performed the secure boot authentication of the firmware code;

control starting of the second hardware component so that the second hardware component remains unstarted until the firmware controller has successfully performed the secure boot authentication of the second firmware code; and

stagger starting of the hardware component and the second hardware component as the firmware controller successfully performs the secure boot authentication of the firmware code and the secure boot authentication of the second firmware code.

2. The computing device of claim 1 , wherein the hardware component accesses the firmware code over the virtual ROM link as if the hardware component were directly physically connected to the ROM,

and wherein the hardware component is not directly physically connected to the ROM.

3. The computing device of claim 1 , wherein the virtual ROM link mimics a direct physical connection between the hardware component and the ROM,

and wherein the hardware component is not directly physically connected to the ROM.

4. The computing device of claim 1 , further comprising a plurality of physical lines between the firmware controller and the hardware component and the second hardware component and shared by the hardware component and the second hardware component,

wherein the firmware controller exposes the virtual ROM link and the second virtual ROM link to the hardware component and the second hardware component, respectively, over the plurality of physical lines.

5. The computing device of claim 1 , further comprising:

a plurality of first physical lines between the firmware controller and the hardware component over which the firmware controller exposes the virtual ROM link; and

a plurality of second physical lines between the firmware controller and the second hardware component over which the firmware controller exposes the second virtual ROM link,

wherein the second hardware component is not connected to any of the plurality of first physical lines and the hardware component is not connected to any of the plurality of second physical lines.

6. The computing device of claim 1 , wherein the firmware controller comprises:

a first processing core that exposes the virtual ROM link to the hardware component; and

a second processing core that exposes the second virtual ROM link to the second hardware component.

7. The computing device of claim 1 , wherein the computing device further comprises a mainboard on which the hardware component, the ROM, and the firmware controller are disposed as respective integrated circuits (ICs).

8. A computing device comprising:

a hardware component;

a read-only memory (ROM) storing firmware code for the hardware component and second firmware code for a second hardware component; and

a firmware controller directly physically connected to the hardware component, the second hardware component, and the ROM, the firmware controller to expose (i) a virtual ROM link to the hardware component over which the hardware component is to access the firmware code and (ii) a second virtual ROM link to the second hardware component over which the second hardware component is to access the second firmware code,

wherein the firmware controller is to:

perform secure boot authentication of the firmware code stored on the ROM prior to permitting the hardware component to access the firmware code over the virtual ROM link;

perform secure boot authentication of the second firmware code stored on the ROM prior to permitting the second hardware component to access the second firmware code over the second virtual ROM link;

restrict starting of the hardware component until the firmware controller has successfully performed the secure boot authentication of the firmware code;

restrict starting of the second hardware component until the firmware controller has successfully performed the secure boot authentication of the second firmware code; and

stagger starting of the hardware component and the second hardware component after the firmware controller successfully performs the secure boot authentication of the firmware code and the secure boot authentication of the second firmware code.

9. The computing device of claim 8 , wherein the hardware component accesses the firmware code over the virtual ROM link as if the hardware component were directly physically connected to the ROM, and wherein the hardware component is not directly physically connected to the ROM.

10. The computing device of claim 8 , wherein the virtual ROM link mimics a direct physical connection between the hardware component and the ROM, and wherein the hardware component is not directly physically connected to the ROM.

11. The computing device of claim 8 , wherein the firmware controller is to perform secure boot authentication of the firmware code prior to permitting the hardware component to access the firmware code over the virtual ROM link.

12. The computing device of claim 8 , wherein the firmware controller is to perform secure boot authentication of the second firmware code prior to permitting the second hardware component to access the second firmware code over the second virtual ROM link.

13. A firmware controller comprising:

a plurality of component terminals to directly physically connect the firmware controller to a hardware component and a second hardware component;

a plurality of read-only memory (ROM) terminals to directly physically connect the firmware controller to a ROM storing firmware code for the hardware component and second firmware code for the second hardware component; and

hardware logic to expose (i) a virtual ROM link to the hardware component over which the hardware component is to access the firmware code and (ii) a second virtual ROM link to the second hardware component over which the second hardware component is to access the second firmware code,

wherein the firmware controller is to:

perform secure boot authentication of the firmware code stored on the ROM prior to permitting the hardware component to access the firmware code over the virtual ROM link;

perform secure boot authentication of the second firmware code stored on the ROM prior to permitting the second hardware component to access the second firmware code over the second virtual ROM link;

control starting of the hardware component so that the hardware component remains unstarted until the firmware controller has successfully performed the secure boot authentication of the firmware code;

control starting of the second hardware component so that the second hardware component remains unstarted until the firmware controller has successfully performed the secure boot authentication of the second firmware code; and

stagger starting of the hardware component and the second hardware component as the firmware controller successfully performs the secure boot authentication of the firmware code and the secure boot authentication of the second firmware code.

14. The firmware controller of claim 13 , wherein the hardware component accesses the firmware code over the virtual ROM link as if the hardware component were directly physically connected to the ROM, and wherein the hardware component is not directly physically connected to the ROM.

15. The firmware controller of claim 13 , wherein the virtual ROM link mimics a direct physical connection between the hardware component and the ROM, and wherein the hardware component is not directly physically connected to the ROM.

16. The firmware controller of claim 13 , wherein the hardware logic is to perform secure boot authentication of the firmware code prior to permitting the hardware component to access the firmware code over the virtual ROM link.

17. The firmware controller of claim 13 , wherein the hardware logic is to perform secure boot authentication of the second firmware code prior to permitting the second hardware component to access the second firmware code over the second virtual ROM link.

Assignments (1)

Continuity (1)

References Cited (16)