Patent Description:
Electronic processing systems may include basic input/output system (BIOS) and an operating system (OS). Firmware may be control code that is included in various components of the electronic processing system or devices attached to the electronic processing system.

Turning now to <FIG>, an embodiment of an electronic processing system <NUM> may include a processor <NUM>, memory <NUM> communicatively coupled to the processor <NUM>, and logic <NUM> communicatively coupled to the processor <NUM> to determine version information for a new firmware component, read dependency information corresponding to the firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component. In some embodiments, the logic <NUM> may be configured to store the self-descriptive dependency information corresponding to the new firmware component. For example, the self-descriptive dependency information may include one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components. In some embodiments, the logic <NUM> may be configured to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component. For example, the logic <NUM> may also be configured to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components and/or to provide the dependency information to an operating system (e.g., the operating system of the electronic processing system <NUM>).

Embodiments of each of the above processor <NUM>, memory <NUM>, logic <NUM>, and other system components may be implemented in hardware, software, or any suitable combination thereof. For example, hardware implementations may include configurable logic such as, for example, programmable logic arrays (PLAs), field programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), or fixed-functionality logic hardware using circuit technology such as, for example, application specific integrated circuit (ASIC), complementary metal oxide semiconductor (CMOS) or transistor-transistor logic (TTL) technology, or any combination thereof.

Alternatively, or additionally, all or portions of these components may be implemented in one or more modules as a set of logic instructions stored in a machine- or computer-readable storage medium such as random access memory (RAM), read only memory (ROM), programmable ROM (PROM), firmware, flash memory, etc., to be executed by a processor or computing device. For example, computer program code to carry out the operations of the components may be written in any combination of one or more operating system (OS) applicable/appropriate programming languages, including an object-oriented programming language such as PYTHON, PERL, JAVA, SMALLTALK, C++, C# or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. For example, the memory <NUM>, persistent storage media, or other system memory may store a set of instructions which when executed by the processor <NUM> cause the system <NUM> to implement one or more components, features, or aspects of the system <NUM> (e.g., the logic <NUM>, determining version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, reading dependency information corresponding to the firmware component, determining if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information, etc.).

Turning now to <FIG>, an embodiment of a semiconductor package apparatus <NUM> may include a substrate <NUM>, and logic <NUM> coupled to the substrate <NUM>, where the logic <NUM> is at least partly implemented in one or more of configurable logic and fixed-functionality hardware logic. The logic <NUM> coupled to the substrate <NUM> may be configured to determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, read dependency information corresponding to the firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component. In some embodiments, the logic <NUM> may be configured to store the self-descriptive dependency information corresponding to the new firmware component. For example, the self-descriptive dependency information may include one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components. In some embodiments, the logic <NUM> may be configured to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component. For example, the logic <NUM> may also be configured to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components and/or to provide the dependency information to an operating system.

Embodiments of logic <NUM>, and other components of the apparatus <NUM>, may be implemented in hardware, software, or any combination thereof including at least a partial implementation in hardware. For example, hardware implementations may include configurable logic such as, for example, PLAs, FPGAs, CPLDs, or fixed-functionality logic hardware using circuit technology such as, for example, ASIC, CMOS, or TTL technology, or any combination thereof. Additionally, portions of these components may be implemented in one or more modules as a set of logic instructions stored in a machine- or computer-readable storage medium such as RAM, ROM, PROM, firmware, flash memory, etc., to be executed by a processor or computing device. For example, computer program code to carry out the operations of the components may be written in any combination of one or more OS applicable/appropriate programming languages, including an object-oriented programming language such as PYTHON, PERL, JAVA, SMALLTALK, C++, C# or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.

Turning now to <FIG>, an embodiment of a method <NUM> of firmware dependency checking may include operations of determining version information for a new firmware component at block <NUM>, reading dependency information corresponding to the firmware component at block <NUM>, and determining if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information at block <NUM>. Some embodiments of the method <NUM> may include operations of storing self-descriptive dependency information corresponding to the new firmware component at block <NUM>. For example, the self-descriptive dependency information may include one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware at block <NUM>. Some embodiments of the method <NUM> may include operations of determining if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information at block <NUM>, and updating the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components at block <NUM>. For example, the method <NUM> may also include operations of providing the dependency information to an operating system at block <NUM>.

Embodiments of the method <NUM> may be implemented in a system, apparatus, computer, device, etc., for example, such as those described herein. More particularly, hardware implementations of the method <NUM> may include configurable logic such as, for example, PLAs, FPGAs, CPLDs, or in fixed-functionality logic hardware using circuit technology such as, for example, ASIC, CMOS, or TTL technology, or any combination thereof. Alternatively, or additionally, the method <NUM> may be implemented in one or more modules as a set of logic instructions stored in a machine- or computer-readable storage medium such as RAM, ROM, PROM, firmware, flash memory, etc., to be executed by a processor or computing device. For example, computer program code to carry out the operations of the components may be written in any combination of one or more OS applicable/appropriate programming languages, including an object-oriented programming language such as PYTHON, PERL, JAVA, SMALLTALK, C++, C# or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.

For example, the method <NUM> may be implemented on a computer readable medium as described in connection with Examples <NUM> to <NUM> below. Embodiments or portions of the method <NUM> may be implemented in firmware, applications (e.g., through an application programming interface (API)), or driver software running on a BIOS or an OS.

Some embodiments may be physically or logically implemented as one or more modules or components. Turning now to <FIG>, an embodiment of a firmware updater apparatus <NUM> may include a firmware scanner <NUM>, a dependency checker <NUM>, and an updater <NUM>. The firmware scanner <NUM> may be configured to determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, and to read dependency information corresponding to the firmware component. The dependency checker <NUM> may be configured to determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component. In some embodiments, the apparatus <NUM> and/or the new firmware component may store the self-descriptive dependency information corresponding to the new firmware component. For example, the self-descriptive dependency information may include one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components. In some embodiments, the dependency checker <NUM> may be configured to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component. For example, the updater <NUM> may be configured to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components. In some embodiments, the firmware scanner <NUM> may also be configured to provide the dependency information to an operating system.

Embodiments of the firmware scanner <NUM>, the dependency checker <NUM>, the updater <NUM>, and other components of the firmware updater apparatus <NUM>, may be implemented in hardware, software, or any combination thereof including at least a partial implementation in hardware. For example, hardware implementations may include configurable logic such as, for example, PLAs, FPGAs, CPLDs, or fixed-functionality logic hardware using circuit technology such as, for example, ASIC, CMOS, or TTL technology, or any combination thereof. Additionally, portions of these components may be implemented in one or more modules as a set of logic instructions stored in a machine- or computer-readable storage medium such as RAM, ROM, PROM, firmware, flash memory, etc., to be executed by a processor or computing device. For example, computer program code to carry out the operations of the components may be written in any combination of one or more OS applicable/appropriate programming languages, including an object-oriented programming language such as PYTHON, PERL, JAVA, SMALLTALK, C++, C# or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.

Some embodiments may advantageously provide a system and/or method to support multiple firmware component update with self-descriptive dependency expressions. An extensible firmware interface (EFI) may provide an interface between firmware and an OS. The firmware may provide control/communication code between a hardware component/device and the EFI. The Unified Extensible Firmware Interface (UEFI) specification may define a software interface between an operating system and platform firmware (e.g., UEFI specification version <NUM>, published May <NUM> at www. org/sites/default/files/resources/ UEFI_Spec_2_7. In some systems, UEFI may replace the BIOS firmware interface (e.g., most UEFI firmware implementations provide legacy support for BIOS services). Some implementations of UEFI may support remote diagnostics and repair, even with no operating system installed. In some systems, the UEFI EFI System Resource Table (ESRT) may include a globally unique identifier (GUID) per updatable component. Some firmware elements on a platform may have a dependency on other firmware elements. Some embodiments may provide a means by which to express these dependencies and build upon existing standards to provide a solution for platforms with many updatable elements. Such updatable elements may include, for example, management engine (ME) firmware, converged security manageability engine (CSME) firmware, core microcode, an INTEL firmware support package, and modular host UEFI firmware (e.g., which may have a large number of separate binary modules).

Turning now to <FIG>, an embodiment of an electronic processing system may include an OS (e.g., such as WINDOWS, REDHAT, etc.). A firmware resource table <NUM> may provide a GUID, version information, and dependency information for a number of devices/components connected to the OS (e.g., a camera <NUM>, a G-sensor/ accelerometer <NUM>, other system components <NUM> with their own firmware, etc.). For example, the firmware resource table <NUM> may be similar to an UEFI ESRT (e.g., or the UEFI standard may be extended to accommodate the version dependency information). A firmware management protocol (FMP) capsule <NUM> may provide routing information, updated data, and/or an updated driver (e.g., an UEFI FMP capsule providing an updated UEFI driver) as part of a firmware update. For example, the OS may read the dependency information corresponding to a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component.

Security or other issues may prompt a firmware update (e.g., even in ME or CSME firmware). The end user or the original equipment manufacturer (OEM), however, may not want to have a component provider unilaterally update a binary module without having this update validated and delivered by the OEM or end user's full BIOS update. Updating ME or other firmware without an associated BIOS reference code update, for example, may cause problems with other system components. The same problem may occur for core microcode, because some microcode patches may make new hardware, like model specific registers (MSRs) appear, and the associated host firmware/BIOS may need to be updated in concert. Some systems may have numerous updatable firmware elements. Some component providers may release sets of firmware elements that must be updated together (e.g., as a best known configuration (BKC)).

Some embodiments may provide for a dependency between elements to be expressed in a software-visible way by updaters. Such dependency may even be exposed to OS updaters, such as a capsule updater. For example, WINDOWS may provide a MODEL BASED SERVICE (MBS) for firmware updates. LINUX may promote a firmware update project (FWUPD), and may provide a LINUX VENDOR FIRMWARE SERVICE (LVFS). Such projects and/or services may benefit from having dependency exposed to the OS as described in accordance with some embodiments herein.

Some embodiments may help ameliorate the OEM concerns on having component-based updates by providing a means by which to support a safe update of dependent modules on platforms and help remove friction for pushing updates in response to product response team (PRT) actions, both functional and security-based. Some embodiments may provide robust field-updatable hardware to avoid recalls but also support fast patching to avoid having customer exposure to security risks.

Firmware update may be an important feature in some electronic systems/platforms. Some industry standards may describe a firmware update process and/or security requirements. For example, the UEFI specification may define an EFI_SYSTEM_RESOURCE_TABLE to identify the system firmware and device firmware to operating system. The data structures may be represented as follows:
▪typedef struct {.

UINT32 FwResourceCount;
UINT32 FwResourceCountMax;
UINT64 FwResourceVersion;
//EFI_SYSTEM RESOURCE ENTRY Entries[];
} EFI_SYSTEM_RESOURCE_TABLE;.

typedef struct {
EFI_GUID FwClass;
UINT32 FwType;
UINT32 FwVersion;
UINT32 LowestSupportedFwVersion;
UINT32 CapsuleFlags;
UINT32 LastAttemptVersion;
UINT32 LastAttemptStatus;
} EFI_SYSTEM RESOURCE ENTRY;.

An OS may utilize the EFI_SYSTEM_RESOURCE_TABLE to manage the firmware of the system(s) and allow a provider and/or user perform firmware updates. A problem may occur in some system if utilization of the EFI_SYSTEM_RESOURCE_TABLE assumes that the identified firmware may be updated independently. In some systems, however, there might be multiple firmware components on one platform which may have some dependency on each other. For example, a system BIOS may need to work with a particular version of microcode. A client system BIOS may need to work with a particular version of ME firmware and a particular version of embedded controller (EC) firmware. A server system BIOS may need to work with a particular version of baseboard management controller (BMC) firmware. A system BIOS may need to work with a particular version of wireless network interface card (NIC) microcode, or BLUETOOTH LOW ENERGY (BLE) firmware. If a mistake is made, or the dependency is otherwise broken, the system may fail to boot, or experience other issues, and it may be hard to detect the problem.

For security considerations, there may be situations where the end user may need or prefer to update only one of the firmware components. But the end user may not know if it is proper to update only one of the firmware components or different firmware components need to be updated together. Some providers may recommend that the end user always updates all firmware on their system, or may hardcode some dependency check in the firmware code. Updating all of the firmware may avoid dependency problems between the new firmware, but could cause problems if the old platform does not work with all of the new firmware. Hardcoding some dependency checks may avoid some dependency issues, but the dependency information remains hidden and the hardcoding is inflexible for further extensions/updates. The hardcoded dependency check may not occur until after the update, requiring the end user to roll back the firmware after receiving an error.

Some embodiments may advantageously provide a way to describe the firmware version dependency clearly and expose such information to the OS. A commercial OS may present such information to the end user. A pre-check may be performed when the user wants to update the firmware in the OS environment, advantageously ensuring that dependencies are satisfied prior to updating the firmware. Some embodiments may provide an architecture way to report firmware dependency in addition to firmware version. Some embodiments may pass the dependency information to the OS and show the information to the end user. Some embodiments may advantageously inhibit or prevent a user/provider mistake in a very early phase to maintain the system/platform in a healthy state.

Some embodiments may provide a self-descriptive firmware dependency definition as an extension to a data structure. The version dependency information may be reported by each firmware component. In some embodiments, the data structures may be represented as follows:
typedef struct {
UINT32 FwVersionBegin;
UINT32 FwVersionEnd;
} EFI_SYSTEM_FIRMWARE_VERSION_RANGE;.

typedef struct {
EFI_GUID_FwClass;
UINT32 VersionRangeCount;
EFI_SYSTEM_FIRMWARE_VERSION_RANGE
VersionRange[VersionRangeCount];
} EFI_SYSTEM_FIRMWARE_DEPENDENCY;.

typedef struct {
EFI_GUID FwClass;
UINT32 FwVersion;
UINT32 DependencyCount;
EFI_SYSTEM_FIRMWARE_DEPENDENCY Dependency[DependencyCount];
} EFI_SYSTEM_RESOURCE_DEPENDENCY;.

For example, if the current BIOS firmware (FwClassBios, version <NUM>) depends on ME firmware (FwClassMe, version <NUM> and upper) and EC firmware (FwClassEc, between version <NUM> and version <NUM>, or between version <NUM> and version <NUM>), in some embodiments the dependency structure may be represented as follows:
EFI_SYSTEM_RESOURCE_DEPENDENCY BiosEntry = {. FwClass = FwClassBios;. FwVersion = <NUM>;. DependencyCount = <NUM>;. Dependency [<NUM>]. FwClass = FwClassMe;. Dependency[<NUM>]. VersionRangeCount= <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = 0xFFFFFFFF;. Dependency[<NUM>]. FwClass = FwClassEc;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = <NUM>;
}.

If the current ME firmware (FwClassMe, version <NUM>) depends on BIOS (FwClassBios, version >= <NUM>), in some embodiments the dependency structure may be represented as follows:
EFI_SYSTEM_RESOURCE_DEPENDENCY MeEntry = {. FwClass = FwClassMe;. FwVersion = <NUM>;. DependencyCount = <NUM>;. Dependency[<NUM>]. FwClass = FwClassBios;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency [<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = 0xFFFFFFFF;
}.

Turning now to <FIG>, an embodiment of a method <NUM> of self-descriptive firmware updating and dependency checking may include scanning each firmware in the new BIOS capsule package at block <NUM>, getting the new firmware version at block <NUM>, scanning each firmware component in the current boot environment at block <NUM>, getting the current firmware version at block <NUM>, comparing each new and current firmware component in the same firmware class at block <NUM>, and getting the highest version firmware in the same class at block <NUM>. The method <NUM> may then go through the dependencies described in each firmware resource at block <NUM>, and determine if the dependency is satisfied at block <NUM> until all the firmware components have been checked at block <NUM>. If any dependency is not satisfied at block <NUM>, the check may fail at block <NUM>. The fail may be reported and the firmware update may be aborted. If all the firmware dependencies passed the dependency check at block <NUM>, the method <NUM> may then report that the dependency check passed at block <NUM> and proceed with the firmware update at block <NUM>.

For example, if the new firmware capsule update image has the following representative structure:
EFI_SYSTEM_RESOURCE_DEPENDENCY BiosEntry = {. FwClass = FwClassBios;. FwVersion = <NUM>;. DependencyCount = <NUM>;. Dependency[<NUM>]. FwClass = FwClassMe;. Dependency [<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = 0xFFFFFFFF;. Dependency[<NUM>]. FwClass = FwClassEc;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = <NUM>;
}.

EFI_SYSTEM_RESOURCE_DEPENDENCY MeEntry = {. FwClass = FwClassMe;. FwVersion = <NUM>;. DependencyCount = <NUM>;. Dependency[<NUM>]. FwClass = FwClassBios;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = 0xFFFFFFFF;
}
then the new ME firmware will not be updated, because its BIOS dependency (version <NUM>) cannot be satisfied.

If the new firmware capsule update image has following representative structure:
EFI_SYSTEM_RESOURCE_DEPENDENCY BiosEntry = {. FwClass = FwClassBios;. FwVersion = <NUM>;. DependencyCount = <NUM>;. Dependency[<NUM>]. FwClass = FwClassMe;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = 0xFFFFFFFF;. Dependency[<NUM>]. FwClass = FwClassEc;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = <NUM>;
}
EFI_SYSTEM_RESOURCE_DEPENDENCY MeEntry = {. FwClass = FwClassMe;. FwVersion = <NUM>;. DependencyCount = <NUM>;. Dependency[<NUM>]. FwClass = FwClassBios;. Dependency[<NUM>]. VersionRangeCount = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionBegin = <NUM>;. Dependency[<NUM>]. VersionRange[<NUM>]. FwVersionEnd = 0xFFFFFFFF;
}
then both BIOS and ME will be updated, because dependency is satisfied.

<FIG> shows a firmware updater apparatus <NUM> (132a-132c) that may implement one or more aspects of the method <NUM> (<FIG>) and/or the method <NUM> (<FIG>). The firmware updater apparatus <NUM>, which may include logic instructions, configurable logic, fixed-functionality hardware logic, may be readily substituted for the logic <NUM> (<FIG>) the logic <NUM> (<FIG>), or the firmware updater apparatus <NUM> (<FIG>), already discussed. The firmware scanner 132a may be configured to determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, and to read dependency information corresponding to the firmware component. The dependency checker 132b may be configured to determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component. In some embodiments, the apparatus <NUM> and/or the new firmware component may store the self-descriptive dependency information corresponding to the new firmware component.

For example, the self-descriptive dependency information may include one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components. In some embodiments, the dependency checker 132b may be configured to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component. For example, the updater 132c may be configured to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components. In some embodiments, the firmware scanner 132a may also be configured to provide the dependency information to an operating system.

Turning now to <FIG>, firmware updater apparatus <NUM> (134a, 134b) is shown in which logic 134b (e.g., transistor array and other integrated circuit/IC components) is coupled to a substrate 134a (e.g., silicon, sapphire, gallium arsenide). The logic 134b may generally implement one or more aspects of the method <NUM> (<FIG>) and/or the method <NUM> (<FIG>). Thus, the logic 134b may determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, read dependency information corresponding to the firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component. In some embodiments, the logic 134b may store the self-descriptive dependency information corresponding to the new firmware component. For example, the self-descriptive dependency information may include one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components. In some embodiments, the logic 134b may determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component. For example, the logic 134b may also update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components and/or to provide the dependency information to an operating system. In one example, the apparatus <NUM> is a semiconductor die, chip and/or package.

<FIG> illustrates a processor core <NUM> according to one embodiment. The processor core <NUM> may be the core for any type of processor, such as a microprocessor, an embedded processor, a digital signal processor (DSP), a network processor, or other device to execute code. Although only one processor core <NUM> is illustrated in <FIG>, a processing element may alternatively include more than one of the processor core <NUM> illustrated in <FIG>. The processor core <NUM> may be a singlethreaded core or, for at least one embodiment, the processor core <NUM> may be multithreaded in that it may include more than one hardware thread context (or "logical processor") per core.

<FIG> also illustrates a memory <NUM> coupled to the processor core <NUM>. The memory <NUM> may be any of a wide variety of memories (including various layers of memory hierarchy) as are known or otherwise available to those of skill in the art. The memory <NUM> may include one or more code <NUM> instruction(s) to be executed by the processor core <NUM>, wherein the code <NUM> may implement one or more aspects of the method <NUM> (<FIG>) and/or the method <NUM> (<FIG>), already discussed. The processor core <NUM> follows a program sequence of instructions indicated by the code <NUM>. Each instruction may enter a front end portion <NUM> and be processed by one or more decoders <NUM>. The decoder <NUM> may generate as its output a micro operation such as a fixed width micro operation in a predefined format, or may generate other instructions, microinstructions, or control signals which reflect the original code instruction. The illustrated front end portion <NUM> also includes register renaming logic <NUM> and scheduling logic <NUM>, which generally allocate resources and queue the operation corresponding to the convert instruction for execution.

The processor core <NUM> is shown including execution logic <NUM> having a set of execution units <NUM>-<NUM> through <NUM>-N. Some embodiments may include a number of execution units dedicated to specific functions or sets of functions. Other embodiments may include only one execution unit or one execution unit that can perform a particular function. The illustrated execution logic <NUM> performs the operations specified by code instructions.

After completion of execution of the operations specified by the code instructions, back end logic <NUM> retires the instructions of the code <NUM>. In one embodiment, the processor core <NUM> allows out of order execution but requires in order retirement of instructions. Retirement logic <NUM> may take a variety of forms as known to those of skill in the art (e.g., re-order buffers or the like). In this manner, the processor core <NUM> is transformed during execution of the code <NUM>, at least in terms of the output generated by the decoder, the hardware registers and tables utilized by the register renaming logic <NUM>, and any registers (not shown) modified by the execution logic <NUM>.

Although not illustrated in <FIG>, a processing element may include other elements on chip with the processor core <NUM>. For example, a processing element may include memory control logic along with the processor core <NUM>. The processing element may include I/O control logic and/or may include I/O control logic integrated with memory control logic. The processing element may also include one or more caches.

Referring now to <FIG>, shown is a block diagram of a system <NUM> embodiment in accordance with an embodiment. Shown in <FIG> is a multiprocessor system <NUM> that includes a first processing element <NUM> and a second processing element <NUM>. While two processing elements <NUM> and <NUM> are shown, it is to be understood that an embodiment of the system <NUM> may also include only one such processing element.

The system <NUM> is illustrated as a point-to-point interconnect system, wherein the first processing element <NUM> and the second processing element <NUM> are coupled via a point-to-point interconnect <NUM>. It should be understood that any or all of the interconnects illustrated in <FIG> may be implemented as a multi-drop bus rather than point-to-point interconnect.

As shown in <FIG>, each of processing elements <NUM> and <NUM> may be multicore processors, including first and second processor cores (i.e., processor cores 1074a and 1074b and processor cores 1084a and 1084b). Such cores 1074a, 1074b, 1084a, 1084b may be configured to execute instruction code in a manner similar to that discussed above in connection with <FIG>.

Each processing element <NUM>, <NUM> may include at least one shared cache 1896a, 1896b (e.g., static random access memory/SRAM). The shared cache 1896a, 1896b may store data (e.g., objects, instructions) that are utilized by one or more components of the processor, such as the cores 1074a, 1074b and 1084a, 1084b, respectively. For example, the shared cache 1896a, 1896b may locally cache data stored in a memory <NUM>, <NUM> for faster access by components of the processor. In one or more embodiments, the shared cache 1896a, 1896b may include one or more mid-level caches, such as level <NUM> (L2), level <NUM> (L3), level <NUM> (L4), or other levels of cache, a last level cache (LLC), and/or combinations thereof.

While shown with only two processing elements <NUM>, <NUM>, it is to be understood that the scope of the embodiments are not so limited. In other embodiments, one or more additional processing elements may be present in a given processor. Alternatively, one or more of processing elements <NUM>, <NUM> may be an element other than a processor, such as an accelerator or a field programmable gate array. For example, additional processing element(s) may include additional processors(s) that are the same as a first processor <NUM>, additional processor(s) that are heterogeneous or asymmetric to processor a first processor <NUM>, accelerators (such as, e.g., graphics accelerators or digital signal processing (DSP) units), field programmable gate arrays, or any other processing element. There can be a variety of differences between the processing elements <NUM>, <NUM> in terms of a spectrum of metrics of merit including architectural, micro architectural, thermal, power consumption characteristics, and the like. These differences may effectively manifest themselves as asymmetry and heterogeneity amongst the processing elements <NUM>, <NUM>. For at least one embodiment, the various processing elements <NUM>, <NUM> may reside in the same die package.

The first processing element <NUM> may further include memory controller logic (MC) <NUM> and point-to-point (P-P) interfaces <NUM> and <NUM>. Similarly, the second processing element <NUM> may include a MC <NUM> and P-P interfaces <NUM> and <NUM>. As shown in <FIG>, MC's <NUM> and <NUM> couple the processors to respective memories, namely a memory <NUM> and a memory <NUM>, which may be portions of main memory locally attached to the respective processors. While the MC <NUM> and <NUM> is illustrated as integrated into the processing elements <NUM>, <NUM>, for alternative embodiments the MC logic may be discrete logic outside the processing elements <NUM>, <NUM> rather than integrated therein.

The first processing element <NUM> and the second processing element <NUM> may be coupled to an I/O subsystem <NUM> via P-P interconnects <NUM><NUM>, respectively. As shown in <FIG>, the I/O subsystem <NUM> includes a TEE <NUM> (e.g., security controller) and P-P interfaces <NUM> and <NUM>. Furthermore, I/O subsystem <NUM> includes an interface <NUM> to couple I/O subsystem <NUM> with a high performance graphics engine <NUM>. In one embodiment, bus <NUM> may be used to couple the graphics engine <NUM> to the I/O subsystem <NUM>. Alternately, a point-to-point interconnect may couple these components.

In turn, I/O subsystem <NUM> may be coupled to a first bus <NUM> via an interface <NUM>. In one embodiment, the first bus <NUM> may be a Peripheral Component Interconnect (PCI) bus, or a bus such as a PCI Express bus or another third generation I/O interconnect bus, although the scope of the embodiments are not so limited.

As shown in <FIG>, various I/O devices <NUM> (e.g., cameras, sensors) may be coupled to the first bus <NUM>, along with a bus bridge <NUM> which may couple the first bus <NUM> to a second bus <NUM>. In one embodiment, the second bus <NUM> may be a low pin count (LPC) bus. Various devices may be coupled to the second bus <NUM> including, for example, a keyboard/mouse <NUM>, network controllers/communication device(s) <NUM> (which may in turn be in communication with a computer network), and a data storage unit <NUM> such as a disk drive or other mass storage device which may include code <NUM>, in one embodiment. The code <NUM> may include instructions for performing embodiments of one or more of the methods described above. Thus, the illustrated code <NUM> may implement one or more aspects of the method <NUM> (<FIG>) and/or the method <NUM> (<FIG>), already discussed, and may be similar to the code <NUM> (<FIG>), already discussed. Further, an audio I/O <NUM> may be coupled to second bus <NUM>.

Note that other embodiments are contemplated. For example, instead of the point-to-point architecture of <FIG>, a system may implement a multi-drop bus or another such communication topology.

Example <NUM> may include an electronic processing system, comprising a processor, memory communicatively coupled to the processor, and logic communicatively coupled to the processor to determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, read dependency information corresponding to the firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the system of Example <NUM>, wherein the logic is further to store the self-descriptive dependency information corresponding to the new firmware component.

Example <NUM> may include the system of Example <NUM>, wherein the self-descriptive dependency information includes one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components.

Example <NUM> may include the system of Example <NUM>, wherein the logic is further to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the system of Example <NUM>, wherein the logic is further to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components.

Example <NUM> may include the system of any of Examples <NUM> to <NUM>, wherein the logic is further to provide the dependency information to an operating system.

Example <NUM> may include a semiconductor package apparatus, comprising a substrate, and logic coupled to the substrate, wherein the logic is at least partly implemented in one or more of configurable logic and fixed-functionality hardware logic, the logic coupled to the substrate to determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, read dependency information corresponding to the firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the apparatus of Example <NUM>, wherein the logic is further to store the self-descriptive dependency information corresponding to the new firmware component.

Example <NUM> may include the apparatus of Example <NUM>, wherein the self-descriptive dependency information includes one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components.

Example <NUM> may include the apparatus of Example <NUM>, wherein the logic is further to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the apparatus of Example <NUM>, wherein the logic is further to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components.

Example <NUM> may include the apparatus of any of Examples <NUM> to <NUM>, wherein the logic is further to provide the dependency information to an operating system.

Example <NUM> may include a method of firmware dependency checking, comprising determining version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, reading dependency information corresponding to the firmware component, and determining if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the method of Example <NUM>, further comprising storing the self-descriptive dependency information corresponding to the new firmware component.

Example <NUM> may include the method of Example <NUM>, wherein the self-descriptive dependency information includes one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components.

Example <NUM> may include the method of Example <NUM>, further comprising determining if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the method of Example <NUM>, further comprising updating the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components.

Example <NUM> may include the method of any of Examples <NUM> to <NUM>, further comprising providing the dependency information to an operating system.

Example <NUM> may include at least one computer readable medium, comprising a set of instructions, which when executed by a computing device, cause the computing device to determine version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, read dependency information corresponding to the firmware component, and determine if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the at least one computer readable medium of Example <NUM>, comprising a further set of instructions, which when executed by the computing device, cause the computing device to store the self-descriptive dependency information corresponding to the new firmware component.

Example <NUM> may include the at least one computer readable medium of Example <NUM>, wherein the self-descriptive dependency information includes one or more classes of firmware components on which the new firmware component is dependent together with a range of compatible versions for each of the one or more classes of firmware components.

Example <NUM> may include the at least one computer readable medium of Example <NUM>, comprising a further set of instructions, which when executed by the computing device, cause the computing device to determine if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the at least one computer readable medium of Example <NUM>, comprising a further set of instructions, which when executed by the computing device, cause the computing device to update the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components.

Example <NUM> may include the at least one computer readable medium of any of Examples <NUM> to <NUM>, comprising a further set of instructions, which when executed by the computing device, cause the computing device to provide the dependency information to an operating system.

Example <NUM> may include a firmware dependency checker apparatus, comprising means for determining version information for a new firmware component of a firmware based on corresponding self-descriptive dependency information of the new firmware component, means for reading dependency information corresponding to the firmware component, and means for determining if dependency is satisfied between the new firmware component and one or more other firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the apparatus of Example <NUM>, further comprising means for storing the self-descriptive dependency information corresponding to the new firmware component.

Example <NUM> may include the apparatus of Example <NUM>, further comprising means for determining if dependency is satisfied between the new firmware component and all other related firmware components based on the version information and the dependency information of the new firmware component.

Example <NUM> may include the apparatus of Example <NUM>, further comprising means for updating the firmware with the new firmware component if dependency is satisfied between the new firmware component and all other related firmware components.

Example <NUM> may include the apparatus of any of Examples <NUM> to <NUM>, further comprising means for providing the dependency information to an operating system.

Embodiments are applicable for use with all types of semiconductor integrated circuit ("IC") chips. Examples of these IC chips include but are not limited to processors, controllers, chipset components, programmable logic arrays (PLAs), memory chips, network chips, systems on chip (SoCs), SSD/NAND controller ASICs, and the like. In addition, in some of the drawings, signal conductor lines are represented with lines. Some may be different, to indicate more constituent signal paths, have a number label, to indicate a number of constituent signal paths, and/or have arrows at one or more ends, to indicate primary information flow direction. This, however, should not be construed in a limiting manner. Rather, such added detail may be used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit. Any represented signal lines, whether or not having additional information, may actually comprise one or more signals that may travel in multiple directions and may be implemented with any suitable type of signal scheme, e.g., digital or analog lines implemented with differential pairs, optical fiber lines, and/or single-ended lines.

Example sizes/models/values/ranges may have been given, although embodiments are not limited to the same. As manufacturing techniques (e.g., photolithography) mature over time, it is expected that devices of smaller size could be manufactured. In addition, well known power/ground connections to IC chips and other components may or may not be shown within the figures, for simplicity of illustration and discussion, and so as not to obscure certain aspects of the embodiments. Further, arrangements may be shown in block diagram form in order to avoid obscuring embodiments, and also in view of the fact that specifics with respect to implementation of such block diagram arrangements are highly dependent upon the platform within which the embodiment is to be implemented, i.e., such specifics should be well within purview of one skilled in the art. Where specific details (e.g., circuits) are set forth in order to describe example embodiments, it should be apparent to one skilled in the art that embodiments can be practiced without, or with variation of, these specific details. The description is thus to be regarded as illustrative instead of limiting.

The term "coupled" may be used herein to refer to any type of relationship, direct or indirect, between the components in question, and may apply to electrical, mechanical, fluid, optical, electromagnetic, electromechanical or other connections. In addition, the terms "first", "second", etc. may be used herein only to facilitate discussion, and carry no particular temporal or chronological significance unless otherwise indicated.

As used in this application and in the claims, a list of items joined by the term "one or more of" may mean any combination of the listed terms. For example, the phrase "one or more of A, B, and C" and the phrase "one or more of A, B, or C" both may mean A; B; C; A and B; A and C; B and C; or A, B and C.

Claim 1:
At least one non-transitory computer readable storage medium comprising a set of instructions which, when executed, cause a computing apparatus to:
access a firmware management protocol capsule (<NUM>), the firmware management protocol capsule (<NUM>) comprising dependency information associated with a first firmware component;
determine from the dependency information a version dependency corresponding to a second firmware component, wherein the version dependency includes a constraint on a version number of the second firmware component; and
determine whether the version dependency corresponding to the second firmware component is satisfied,
wherein to determine whether the version dependency corresponding to the second firmware component is satisfied, the instructions, when executed, cause the computing apparatus to determine whether a version number for an installed version of the second firmware component satisfies the constraint on the version number of the second firmware component, and
wherein the instructions, when executed, further cause the computing apparatus to update the first firmware component if the version dependency corresponding to the second firmware component is satisfied.