Firmware configuration method, computer program product and electronic equipment

Abstract

The invention provides a firmware configuration method, a computer program product and electronic equipment, and the method comprises the following steps: in a startup stage of the electronic equipment, an embedded controller obtains first capability state information of a processor; the capability state information of the processor indicates whether the processor has the hardware capability required for realizing the out-of-band management function or not; the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller based on the first capability state information so as to configure the power supply protocol firmware to operate in a first working mode or a second working mode matched with the first capability state information; wherein in the first working mode, the electronic equipment supports to realize the out-of-band management function; in the second working mode, the electronic equipment does not support the implementation of the out-of-band management function.

Description

Technical Field

[0001] This application relates primarily to the field of electronic equipment technology, and in particular to a firmware configuration method, a computer program product, and an electronic device. Background Technology

[0002] vPro is a hardware platform technology for enterprise-level management. It provides remote management, hardware-level security protection, and high-performance computing capabilities for commercial computers in scenarios such as enterprise offices, finance, and healthcare. This requires the coordinated implementation of hardware and software such as processors, chipsets, network cards, and firmware that support vPro.

[0003] In cases where the electronic device has hardware that supports vPro, it is necessary to manually flash a vPro-compatible firmware file to update the firmware of the PD (Power Delivery) chip in order for the electronic device to support vPro and meet customer needs. This process is time-consuming and labor-intensive, and is prone to firmware errors due to manual operation, resulting in the customer receiving an electronic device that does not support vPro and cannot meet their usage requirements. Summary of the Invention

[0004] In view of the above problems, this application provides the following solution:

[0005] The first aspect of this application provides a firmware configuration method, the method comprising:

[0006] During the power-on phase of an electronic device, the embedded controller acquires the processor's first capability status information; the processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions.

[0007] Based on the first capability status information, the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to operate in a first working mode or a second working mode that matches the first capability status information.

[0008] In the first operating mode, the electronic device supports the implementation of the out-of-band management function;

[0009] In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

[0010] In one possible implementation, the embedded controller sends configuration instructions for the power supply protocol firmware to the power supply controller based on the first capability status information, including:

[0011] The embedded controller compares the first capability status information with the second capability status information that was previously acquired and stored.

[0012] In response to the difference between the first capability status information and the second capability status information, the embedded controller sends a first configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to be in a first operating mode or a second operating mode that matches the first capability status information, and updates the stored second capability status information to the first capability status information.

[0013] In one possible implementation, the method further includes:

[0014] The embedded controller reads the currently stored third capability status information in response to the electronic device switching from a completely power-off state to a soft power-off state.

[0015] Send a second configuration instruction to the power supply controller for the power supply protocol firmware to configure the power supply protocol firmware to be in the first operating mode or the second operating mode that matches the third capability status information.

[0016] In one possible implementation, configuring the power supply protocol firmware to be in a first operating mode or a second operating mode that matches the capability status information of the currently deployed processor includes:

[0017] The power supply controller controls the power supply protocol firmware to select and execute a firmware file that matches the capability status information of the currently deployed processor from the configured first firmware file and second firmware file.

[0018] If the power supply protocol firmware executes the first firmware file, it enters the first working mode;

[0019] If the power supply protocol firmware executes the second firmware file, it enters the second working mode.

[0020] A second aspect of this application also provides a firmware configuration method, the method comprising:

[0021] During the power-on phase of an electronic device, the system firmware chip determines the processor's first capability status information; the processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions.

[0022] The system firmware chip sends the first capability status information to the embedded controller, so that the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller based on the first capability status information, so as to configure the power supply protocol firmware to be in a first working mode or a second working mode.

[0023] In the first operating mode, the electronic device supports the implementation of the out-of-band management function;

[0024] In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

[0025] In one possible implementation, the method further includes any of the following:

[0026] The system firmware chip determines that the electronic device has replaced its processor, reads the type information of the replaced processor, and determines the fourth capability status information of the processor.

[0027] In response to the first power-on of the electronic device, the system firmware chip reads the processor type information to determine the processor's first capability status information.

[0028] A third aspect of this application also provides a computer program product, including computer-readable instructions that run on an electronic device, causing the electronic device to perform the following steps:

[0029] During the power-on phase of the electronic device, the embedded controller acquires the processor's first capability status information; the processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions.

[0030] Based on the first capability status information, the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to operate in a first working mode or a second working mode that matches the first capability status information.

[0031] In the first operating mode, the electronic device supports the implementation of the out-of-band management function;

[0032] In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

[0033] A fourth aspect of this application also provides an electronic device, the electronic device comprising: a system firmware chip, an embedded controller, a processor, and a power supply controller deployed on a motherboard, wherein:

[0034] The system firmware chip is used to communicate with the embedded controller and the processor respectively, determine the first capability status information of the processor, and send the first capability status information to the embedded controller; the capability status information of the processor indicates whether the processor has the hardware capability required to implement out-of-band management functions.

[0035] The embedded controller is configured to send configuration instructions for the power supply protocol firmware to the power supply controller based on the first capability status information.

[0036] The power supply controller is configured, in response to the configuration command, to configure the power supply protocol firmware to be in a first working mode or a second working mode that matches the first capability status information.

[0037] In the first operating mode, the electronic device supports the implementation of the out-of-band management function;

[0038] In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

[0039] In one possible implementation, the electronic device further includes:

[0040] An integrated southbridge chip is used to deploy management engine firmware and, based on the first capability status information, to achieve switching control between the first working mode and the second working mode;

[0041] If the processor does not have the hardware capability required to implement out-of-band management functions, the integrated southbridge chip switches to the second operating mode so that the management engine firmware refuses to implement the out-of-band management functions.

[0042] In one possible implementation, the signal repeater firmware deployed in the signal repeater chip of the electronic device is configured to the first operating mode;

[0043] The embedded controller is communicatively connected to the power supply controller via a system management bus;

[0044] The system firmware chip communicates with the embedded controller via a serial peripheral interface. Attached Figure Description

[0045] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0046] Figure 1 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 1 of this application;

[0047] Figure 2 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 2 of this application;

[0048] Figure 3 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 3 of this application;

[0049] Figure 4 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 4 of this application;

[0050] Figure 5 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 5 of this application;

[0051] Figure 6 This is a schematic diagram of the hardware structure of an electronic device provided in Embodiment 1 of this application. Detailed Implementation

[0052] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is only for explaining specific embodiments and is not intended to limit the application. The embodiments of this application are described below with reference to the accompanying drawings. It will be understood by those skilled in the art that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0053] The terms "first," "second," etc., used throughout this application and in the foregoing figures are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0054] To address the technical problems described in the background section, this application provides a firmware configuration method. The firmware configuration method of this application embodiment will be described in detail below with reference to the accompanying drawings.

[0055] Reference Figure 1 This is a flowchart illustrating a firmware configuration method proposed in Embodiment 1 of this application. This method is applicable to electronic devices, such as smartphones, laptops, desktop computers, or smart medical devices. Figure 1 As shown, the firmware configuration method may include, but is not limited to:

[0056] Step S11: During the power-on phase of the electronic device, the embedded controller acquires the processor's first capability status information; the processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions.

[0057] In step S12, the embedded controller sends a configuration command for the power supply protocol firmware to the power supply controller based on the first capability status information, so as to configure the power supply protocol firmware to run in a first working mode or a second working mode that matches the first capability status information; in the first working mode, the electronic device supports the implementation of out-of-band management functions; in the second working mode, the electronic device does not support the implementation of out-of-band management functions.

[0058] In practical applications, electronic devices possess or support vPro platform technology (at this time, the electronic device can be called a vPro platform device, which is usually aimed at enterprise, commercial, and IT batch management markets) to achieve functions such as out-of-band management (such as remote power-on, fault diagnosis and system recovery), hardware-level security, hardware shield, and stable images. This requires the electronic device to be equipped with a complete hardware kit that supports vPro platform functions, and to work in conjunction with software that supports vPro platform functions. If one of the processors or its firmware (FW) among the collaborating parties does not support vPro, the electronic device will not support vPro, and the electronic device can only be used as a non-vPro device (which is usually aimed at home, small office, and individual user markets).

[0059] In particular, the processor installed when the electronic device is shipped, according to customer order requirements or market demand (in this application, it may refer to a CPU or other processor / hardware that must be built on the vPro platform; this application only uses a CPU as an example for illustration), may or may not support the vPro platform (i.e., non-vPro), in order to configure the corresponding version of the firmware and perform the corresponding type of certification on the electronic device. For example, for processors that support vPro, vPro certification is obtained before shipment, so that the electronic device operates in the working mode corresponding to the certified vPro platform.

[0060] Therefore, it is evident that the Power Delivery Firmware (PDFW) shipped with electronic devices does not support vPro platform functionality. The electronic devices are certified as non-vPro. If the processor is replaced / installed with a processor supporting vPro platform functionality, and the electronic device is to be used as a vPro device, the PD firmware version needs to be changed to a version supporting vPro platform functionality. This can be achieved through firmware flashing updates, updating the firmware from incompatible to compatible code to enable vPro platform functionality. However, the PD firmware flashing update process is prone to errors, leading to malfunctions in the electronic device. Furthermore, this method of switching between non-vPro and vPro functionality is cumbersome and cannot be implemented by most customers, thus reducing the customer experience.

[0061] To address the aforementioned issues, this application proposes configuring PD firmware in electronic devices that simultaneously supports both non-vPro and vPro platform functions. This allows the PD firmware to execute program code supporting vPro platform functions, enabling a first operating mode (i.e., vPro mode) and thus allowing the electronic device to implement vPro platform functions. Conversely, if the PD firmware executes program code that does not support vPro platform functions (i.e., non-vPro platform functions), it enables a second operating mode (i.e., non-vPro mode, which can be the PD's traditional / standard mode), allowing the electronic device to implement non-vPro platform functions. In this way, the PD firmware can directly switch to the matching operating mode based on whether the processor installed in the electronic device supports or does not support vPro, i.e., execute the corresponding program code to meet the platform functions required for electronic device certification.

[0062] Therefore, if the processor actually installed in the electronic device supports vPro, the method proposed in this application controls the PD firmware to be in a first working mode, enabling the electronic device to implement vPro platform functions. Conversely, if the processor actually installed in the electronic device does not support vPro, the method proposed in this application controls the PD firmware to be in a second working mode, enabling the electronic device to implement non-vPro platform functions. This eliminates the need for customers / maintenance personnel to manually change the PD firmware version. This process can be completed without the customer's awareness, improving the customer experience and solving the problems associated with flashing and updating PD firmware program code, thus meeting the customer's needs for using different platform functions of the electronic device.

[0063] The core difference between whether a processor supports vPro and not is whether the processor has the hardware capabilities required to implement out-of-band management. Therefore, in order to detect whether the processor in the current electronic device supports vPro, that is, to determine whether the electronic device is actually equipped with a processor that supports vPro or a processor that does not support vPro, and to decide which working mode the PD firmware should enable, this application can directly detect the processor's capability status information during the power-on phase of the electronic device. This information is used to indicate whether the processor currently installed in the electronic device has the hardware capabilities required to implement out-of-band management functions (i.e., whether the processor supports vPro platform functions), thereby enabling the switching configuration of the first and second working modes of the PD firmware.

[0064] In one possible implementation, the different capability status information of the processor can be different status flags. For example, the status flag "1" (or the status identifier TRUE) indicates that the processor supports vPro platform functions, that is, the processor has the hardware capabilities required to implement out-of-band management functions. The status flag "0" (or the status identifier FALSE) indicates that the processor does not support vPro platform functions, that is, the processor does not have the hardware capabilities required to implement out-of-band management functions. This application does not limit the content of different status flags.

[0065] In another possible implementation, the processor's different capability status information can also be descriptive information expressing its actual hardware capabilities or whether it supports out-of-band management functions, such as text / code description information. This application does not limit the data format of the capability status information. Optionally, the capability status information can also be target attribute information configured for the processor, such as type / version information indicating whether the processor has the hardware capabilities required to implement out-of-band management functions. This application does not limit the content of the processor's capability status information and can be determined as appropriate.

[0066] In the firmware configuration method proposed in this application, an independently powered embedded controller (EC) obtains the processor's capability status information and sends configuration commands for the PD firmware to the power supply controller (PD controller) accordingly. This configures the PD firmware to operate in a mode matching the capability status information, ensuring that the actual operating mode of the PD firmware is compatible with processors that support or do not support vPro. This enables the electronic device to implement the corresponding platform functions, i.e., vPro platform functions or non-vPro platform functions. This application does not restrict how the EC obtains the processor's capability status information or the communication mechanism between the EC and the PD firmware / controller.

[0067] Since the EC power supply is independent of whether the electronic device's operating system is powered on, in sleep mode, or completely powered off (S5), in scenarios such as replacing or upgrading the processor of an electronic device, during the power-on process of the electronic device, which may be in the system loading and booting stage (when the operating system has not yet started running), the EC can execute the firmware configuration method proposed in this application to automatically switch and adjust the working mode of the PD firmware to match the processor's hardware capabilities. After the operating system successfully starts running, the PD firmware can directly run in this working mode, enabling the electronic device to perform the corresponding platform functions and meet the actual needs of customers.

[0068] It should be noted that other firmware in electronic devices, such as the system ME (Intel Management Engine) firmware and Retimer firmware (used for protocol negotiation and switching, signal integrity optimization, power management, etc.), all support vPro by default. The Retimer firmware does not distinguish between vPro and non-vPro. Depending on whether a vPro-supporting or non-vPro processor is installed, because the ME operates independently of the device's operating system and CPU core, even if the computer is powered off, in sleep mode, or even if the operating system has crashed, the ME remains active in the background as long as the electronic device is connected to power and network. Therefore, the ME can automatically switch to the matching management mode to manage and control the activation and deactivation of the electronic device's vPro function. The ME's management and control of the vPro function does not affect other functions of the electronic device. Therefore, in practical applications, the ME is used to receive, process, and execute various out-of-band management functions; the implementation process is not detailed in this application.

[0069] In summary, given that the electronic device possesses the hardware foundation of the vPro platform, especially with a processor supporting vPro platform functionality, the firmware configuration method proposed in this application automatically and reliably configures the target operating mode of the PD firmware to the first operating mode (i.e., the PD firmware automatically executes vPro program code). This allows the electronic device to directly implement out-of-band management functions, i.e., vPro platform functionality, after successful power-on. Out-of-band management functions refer to management operations that do not depend on the device's main operating system, allowing IT administrators to remotely control, diagnose, and repair the computer in an out-of-band environment.

[0070] Similarly, when electronic devices lack the hardware foundation of the vPro platform, especially when they are equipped with processors that do not support vPro platform functions, the EC automatically controls the firmware (PD firmware) in the PD controller to enter the second operating mode (i.e., the PD firmware automatically executes non-vPro program code). This allows the electronic device to directly achieve the functions of the standard power supply mode after successful power-on. This configuration process is completed directly during the power-on phase, without the customer's awareness or need for manual operation, greatly enhancing the convenience and flexibility of configuration and improving the customer experience.

[0071] Reference Figure 2 This is a flowchart illustrating a firmware configuration method proposed in Embodiment 2 of this application. This embodiment describes an optional implementation method of how the EC, based on the processor's capability status information, flexibly configures the PD firmware's operating mode to match the capability status information in the firmware configuration method described above. Figure 2 As shown, this optional implementation method may include, but is not limited to:

[0072] Step S21: During the power-on phase of the electronic device, the embedded controller acquires the processor's first capability status information.

[0073] Step S22: The embedded controller compares the first capability status information with the second capability status information that was previously acquired and stored.

[0074] Based on the description of the processor's capability status information in the above embodiments, the first capability status information indicates whether the processor currently configured in the electronic device has the hardware capabilities required to implement out-of-band management functions. The second capability status information only indicates whether the processor installed in the electronic device had the hardware capabilities required to implement out-of-band management functions when the electronic device last entered the power-on phase (this application does not limit the state from which it enters the power-on phase). If the customer replaced the processor during these two power-on periods, or if a processor malfunction caused a change in its hardware capabilities, the hardware capabilities of the processor before and after this event may be the same or different. This directly affects whether it is necessary to switch the working mode of the PD firmware (i.e., the working mode during the last power-on operation) to ensure that the electronic device works normally and that its implemented platform functions meet the requirements of processor replacement.

[0075] Based on this, the EC can perform a consistency check between the processor capability status information obtained during this power-on (i.e., the first capability status information) and the processor capability status information obtained or determined during the previous power-on (i.e., the second capability status information). This checks whether the current hardware capabilities of the processor match the current working mode configured in the PD firmware (i.e., the working mode during the previous power-on). If there is a mismatch, the EC can adjust the working mode of the PD firmware in a timely manner during this power-on to ensure that the actual working mode of the PD firmware matches the actual hardware capabilities of the processor. This avoids abnormal situations caused by the mismatch and improves the customer experience.

[0076] In some embodiments, as analyzed above, each time the EC obtains the processor's capability status information, the BIOS (Basic Input / Output System) chip (system firmware chip) can read the processor's type / version information, determine the processor's current capability status information based on this type / version information, and then send the capability status information to the EC. Alternatively, the EC can actively read the capability status information determined by the BIOS chip; this application does not limit the communication method between the BIOS chip and the EC.

[0077] Step S23: In response to the difference between the first capability status information and the second capability status information, the embedded controller sends a first configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to be in a first working mode or a second working mode that matches the first capability status information.

[0078] Following the above analysis, the EC compares the first capability status information with the second capability status information and determines that they are different. This indicates that the processor's hardware capabilities are incompatible with the current operating mode of the PD firmware, making it impossible to reliably implement functions based on the processor's hardware capabilities, especially the out-of-band management functions supported by the vPro processor. To address this, there is no need to replace the processor; the EC can directly control the PD controller to switch the PD firmware's operating mode to match the processor's actual hardware capabilities.

[0079] Therefore, when the EC determines that the first capability status information is different from the second capability status information, it can send a first configuration command to the PD controller to control the PD firmware to be in a working mode that matches the first capability status information. The PD controller responds to the first configuration command to realize the switching configuration of the working mode of the PD firmware. This application does not describe in detail the communication principle between the EC, the PD controller, and the PD firmware.

[0080] In some embodiments, configuring the PD firmware to a first operating mode or a second operating mode can be achieved by executing different firmware files. Therefore, the PD firmware is pre-configured with a first firmware file for executing the first operating mode, such as program code implementing vPro platform functions; and a second firmware file for executing the second operating mode, such as program code implementing non-vPro platform functions. This application does not limit the content of these two types of firmware files. Thus, the method for configuring the PD controller to operate the PD firmware in the first or second operating mode can include:

[0081] The power supply controller (PD controller) controls the power supply protocol firmware (PD firmware) to select and execute a firmware file that matches the capability status information of the currently deployed processor from the configured first firmware file and second firmware file. If the power supply protocol firmware executes the first firmware file, the PD firmware is configured to a first operating mode; if the power supply protocol firmware executes the second firmware file, the PD firmware is configured to a second operating mode. This application does not limit the implementation method of switching between these two firmware files.

[0082] In one possible implementation, both the first and second firmware files can be loaded into the PD firmware as independent firmware files. Following the method described above, one firmware file can be selected for execution to switch the PD firmware's operating mode. In another possible implementation, the differences between the first and second firmware files can be stored independently, while the duplicate information is retained as shared information. This allows for automatic selection and execution of the corresponding program code when a specific firmware file is chosen, saving storage resources.

[0083] In step S24, the embedded controller updates the stored second capability status information to the first capability status information.

[0084] Based on the above analysis, if the EC determines that the first capability status information and the second capability status information are different, in order to record the actual capability status information of the current processor, it is necessary to update the stored second capability status information to the first capability status information, so that the EC stores the first capability status information for comparison with the capability status information acquired next time, in order to configure the working mode of the PD firmware at the next boot. The implementation process is similar and will not be described in detail in this application.

[0085] It should be understood that if the EC determines that the first capability status information and the second capability status information are different, it means that the hardware capabilities of the processor at this time match the current working mode of the PD firmware. There is no need to adjust the configuration of the PD firmware. The normal boot process can be executed, that is, the system boot process can continue to be executed. After the operating system starts running, the PD firmware will continue to run the firmware file corresponding to the original working mode.

[0086] Reference Figure 3 This is a flowchart illustrating a firmware configuration method proposed in Embodiment 3 of this application, applied to an embedded controller (EC) of an electronic device, such as... Figure 3 As shown, the firmware configuration method executed by the EC proposed in this embodiment may include, but is not limited to:

[0087] Step S31: During the power-on phase of the electronic device, the embedded controller acquires and stores the processor's third capability status information.

[0088] Step S32: In response to the electronic device switching from a fully powered-off state to a soft-shutdown state, the embedded controller reads the currently stored third capability status information.

[0089] In step S33, the embedded controller sends a second configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to be in a first operating mode or a second operating mode that matches the third capability status information.

[0090] Based on the above description of the EC, since the EC power supply is independent of whether the electronic device's operating system is powered on, in sleep mode, or completely powered off, and power outages do not affect its stored content, a normally functioning EC can execute the firmware configuration method proposed in this application when the electronic device switches between different power management states. This enables the configuration of the PD firmware working mode, reliably realizing the platform function for actual authentication of the electronic device and meeting the actual needs of customers.

[0091] In some embodiments, during the BIOS boot process, if the electronic device enters the G3 (complete power-off state, the system has no power supply) state during the execution of the firmware configuration method described in the above embodiments, the independently powered EC is running normally and can still store the processor capability status information obtained this time, or update the storage after comparison as described above. The currently stored capability status information can be recorded as the third capability status information, which may be the first capability status information or the second capability status information mentioned above. This application does not limit this.

[0092] However, in G3 state, the capability status information cached by the BIOS during power loss is lost. Therefore, when the electronic device returns from G3 to S5 (soft shutdown state, where the system is in its lowest power consumption state, but some components (such as Wake-on-LAN, clock, etc.) may still retain power, allowing the system to be woken up by specific events (such as Wake-on-LAN, keyboard input, etc.), the BIOS still cannot function properly and cannot re-acquire the processor's capability status information. To correctly configure the PD firmware's operating mode, the EC will read its own stored third capability status information (i.e., the actual capability status information previously read and stored). During the period when the electronic device returns from G3 to S5, the processor has not been replaced, and this third capability status information can reliably indicate whether the current processor has the hardware capabilities required to implement out-of-band management functions.

[0093] Therefore, the EC can send a corresponding configuration command for the PD firmware to the PD controller based on the third capability status information, denoted as the second configuration command. The PD control command responds to the second configuration command, configuring the PD firmware to be in a first or second working mode that matches the third capability status information. This implementation process can be referred to the description of the corresponding part of the above embodiment, and will not be repeated here. In this way, even if the electronic device experiences a power outage during the G3 power-on process and then returns to the S5 state, it can still configure the PD firmware working mode so that the subsequent power-on process can continue after the configuration is completed.

[0094] Reference Figure 4 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 4 of this application, as shown below. Figure 4 As shown, the firmware configuration method proposed in this embodiment may include, but is not limited to:

[0095] Step S41: During the power-on phase of the electronic device, the system firmware chip determines the first capability status information of the processor; the capability status information of the processor indicates whether the processor has the hardware capability required to implement out-of-band management functions.

[0096] In step S42, the system firmware chip sends the first capability status information to the embedded controller;

[0097] In this embodiment of the application, when the electronic device is powered on and the BIOS chip starts running, the firmware configuration method proposed in this application can be executed before the operating system starts to complete the configuration of the working mode of the PD firmware so that it matches the actual hardware capabilities of the processor.

[0098] Optionally, based on the above analysis, the system firmware chip, in response to the first power-on of the electronic device, reads the processor type information to determine the processor's first capability status information. Additionally, if it is determined that the electronic device has a replaced processor, the system firmware chip reads the type information of the replaced processor to determine its fourth capability status information, indicating whether the replaced processor possesses the hardware capabilities required to implement out-of-band management functions.

[0099] Optionally, the processor identification information, such as the manufacturer ID, model number, and family name, can be read and compared with its internally stored identification information to determine whether the processor has been replaced. Alternatively, the BIOS can check the current CPU's microcode version at each boot and compare it with its own internal version. Verification can also be performed by detecting power management parameters such as processor power consumption, current, or voltage requirements to determine if the processor has been replaced. This application does not limit the implementation method of how the BIOS detects whether an electronic device has had its processor replaced.

[0100] Step S43: The embedded controller sends a configuration command for the power supply protocol firmware to the power supply controller based on the first capability status information.

[0101] In step S44, the power supply controller responds to the configuration command and configures the power supply protocol firmware to be in a first working mode or a second working mode; in the first working mode, the electronic device supports out-of-band management functions; in the second working mode, the electronic device does not support out-of-band management functions.

[0102] The implementation process of steps S43 and S44 can be referred to the description of the firmware configuration method from the EC side in the above embodiments, and will not be repeated here in this application embodiment.

[0103] Reference Figure 5 This is a schematic diagram of the signaling flow of a firmware configuration method proposed in Embodiment 5 of this application. This embodiment uses a BIOS chip as the system firmware chip and a CPU as the processor for illustration. Figure 5 As shown, the firmware configuration method proposed in this embodiment may include, but is not limited to:

[0104] Step S51: In response to the power-on request of the electronic device, it is determined that both the management engine ME and the PD firmware support the vPro platform function; the PD firmware is configured to the first working mode.

[0105] Step S52: The BIOS chip reads the fourth capability status information of the processor CPU;

[0106] Step S53: The BIOS chip determines whether the CPU supports vPro platform functions based on the fourth capability status information. If yes, proceed to step S54; otherwise, proceed to step S55.

[0107] In step S54, the BIOS chip sends the fourth capability status information to the EC storage and executes the boot process;

[0108] In step S55, the BIOS chip sends the fourth capability status information to the EC;

[0109] Step S56: The EC sends a third configuration command for the PD firmware to the PD controller based on the fourth capability status information.

[0110] In step S57, the PD controller responds to the third configuration command and configures the PD firmware to switch from the first working mode to the second working mode;

[0111] The implementation process of steps S51-S57 can be referred to the description of the corresponding parts of the above embodiments. The acquisition and processing process of the fourth capability status information here is equivalent to the acquisition and processing method of the first capability status information in the above embodiments, and will not be described in detail here.

[0112] It should be understood that if the ME and PD firmware are set by default to not support vPro platform functions, the subsequent processing is similar. The difference is that when the processor is actually detected to support vPro platform functions, the PD firmware is controlled to switch from the second working mode to the first working mode. The implementation process is not detailed in this application.

[0113] Step S58: EC determines whether the electronic device has entered the S5 state from the G3 power-off state. If not, continue the power-on process; if yes, proceed to step S59.

[0114] Step S59, EC reads the currently stored fifth capability status information;

[0115] Step S510: The EC sends a fourth configuration command for the PD firmware to the PD controller based on the fifth capability status information.

[0116] In step S511, the PD controller responds to the fourth configuration command and configures the PD firmware to be in either the first or second operating mode that matches the fifth capability status information.

[0117] Based on the description of the corresponding part of Embodiment 3 above, the situation where the electronic device enters the S5 state from the G3 power-off state may occur during the execution of any of the above steps in the power-on process. Therefore, step S58 is not limited to being executed after step S57. During the execution of any of the above steps, the EC detects this situation. Since the PD firmware retains the configuration of the previous working mode after the electronic device is powered off, the EC sends the processor capability status information read and sent by the previous BIOS to the PD controller, or generates corresponding configuration instructions and sends them to the PD controller, so as to realize the switching configuration of the working mode of the PD firmware. This allows the PD firmware to run according to the configured working mode after the electronic device's operating system starts running, ensuring that it matches the hardware capabilities of the processor in the electronic device, solving problems such as abnormal operation of the electronic device due to mismatch between the two, and improving the customer experience.

[0118] The above describes a firmware configuration method provided by an embodiment of this application. The following describes an electronic device that performs the above firmware configuration method.

[0119] Reference Figure 6 This is a schematic diagram of the hardware structure of an electronic device provided in Embodiment 1 of this application, as shown below. Figure 6 As shown, the electronic device may include, but is not limited to: a system firmware chip 62, an embedded controller (EC) 63, a processor 64, and a power supply controller (PD controller) 65 deployed on the motherboard 61, wherein:

[0120] The system firmware chip 62 can be used to communicate with the embedded controller 63 and the processor 64 respectively, determine the first capability status information of the processor 64, and send the first capability status information to the embedded controller 63; the capability status information of the processor 64 indicates whether the processor 64 has the hardware capability required to implement out-of-band management functions.

[0121] In this embodiment, the system firmware chip 62 can be a BIOS chip, or a UEFI (Unified Extensible Firmware Interface) chip used to replace the BIOS chip, i.e., a hardware chip on the motherboard 61 that stores the system firmware. This system firmware is configured to initialize the hardware components of the electronic device and guide the program running the operating system during the pre-boot phase. The firmware configuration method proposed in this application can be implemented during this pre-boot phase. The implementation process of each step performed by the system firmware chip 62 during the firmware configuration method implementation can be referred to the description of the method embodiment above, and will not be repeated in this embodiment.

[0122] Optionally, the system firmware chip 62 can communicate with the embedded controller 63 via a serial peripheral interface (SPI), such as ESPI (Enhanced Serial Peripheral Interface), so that the BIOS chip and the EC chip can transmit capability status information through a master-slave communication protocol. The implementation process is not described in detail in this application.

[0123] The embedded controller 63 can be used to send configuration instructions for the power supply protocol firmware to the power supply controller 65 based on the first capability status information;

[0124] The power supply controller 65 is configured, in response to a configuration command, to configure the power supply protocol firmware to be in a first operating mode or a second operating mode that matches the first capability status information.

[0125] Regarding the implementation process of the firmware configuration method, the respective execution steps of the embedded controller 63 and the power supply controller 65 can be referred to the description of the method embodiment above, and will not be repeated in this embodiment. The power supply protocol firmware (PD firmware) can be firmware code stored in the power supply controller 65. Its two configured working modes are equivalent to different logical branches of the PD firmware executed by the power supply controller 65 to run either the first code supporting vPro platform functions or the second code not supporting vPro (i.e., non-Pro) platform functions. The implementation process will not be detailed in this application.

[0126] As can be seen, after determining whether the processor supports vPro based on the above analysis, the PD controller can determine whether the PD firmware is configured as the first working mode or the second working mode based on the actual capability status information of the processor when the device is first powered on. That is, it executes the corresponding firmware code and retains the previously set working mode after power failure.

[0127] Optionally, the embedded controller 63 communicates with the power supply controller 65 via a system management bus (SMBUS). The embedded controller 63 can also transmit capability status information to the power supply controller 65 through a specific interface (such as GPIO, I2C or other protocols). This application does not limit the communication method between the two.

[0128] In some embodiments, the electronic device may further include: an integrated southbridge chip (PCH, Platform Controller Hub) for deploying the management engine ME firmware, which, based on first capability status information, controls the switching between a first operating mode and a second operating mode. Wherein, if the processor 64 lacks the hardware capabilities required to implement out-of-band management functions, the integrated southbridge chip switches to the second operating mode, causing the management engine ME firmware to refuse to implement out-of-band management functions.

[0129] In practical applications, the PCH serves as the hub connecting the processor CPU and other peripheral devices. It needs to provide an interface for communication with the ME (such as the eSPI bus) and support the security and management functions required for vPro platform functionality. As a pair supporting vPro platform functionality, the processor CPU and PCH are not detailed in this application regarding their respective processing methods for implementing vPro platform functionality. Therefore, the processor 64 in this application can be a CPU, and may also include other types of processors or hardware chips as needed to support the implementation of vPro platform functionality; these will not be detailed here.

[0130] Optionally, the repeater firmware (Retimer FW) deployed in the repeater chip of the electronic device is configured in the first operating mode, that is, to support vPro platform functions by default, in order to meet additional reliability and security requirements when implementing out-of-band management functions. The Retimer is a hardware component in a high-speed serial interface (such as Thunderbolt 3 / 4, USB4), mainly used to solve signal attenuation and timing deviation problems. The Retimer firmware is software running inside the Retimer chip, responsible for dynamically configuring hardware behavior, such as out-of-band management channel maintenance, protocol and power management, and field firmware updates. The implementation process is not detailed in this application.

[0131] It should be understood that, Figure 6 The structure of the electronic device shown does not constitute a limitation on the computer device in the embodiments of this application. In practical applications, the electronic device may include more than Figure 6 The application may include more or fewer components, or combinations of certain components, such as at least one volatile memory, and may also include at least one non-volatile memory or other storage media, displays, various sensors or other input / output components, etc., which will not be described in detail here.

[0132] This application also provides a computer program product including computer-readable instructions, which, when executed on an electronic device, cause the electronic device to implement any of the firmware configuration methods provided in this application.

[0133] This application also provides a computer-readable storage medium that carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the firmware configuration methods provided in this application.

[0134] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0135] In the above embodiments, all or part of the implementation can be achieved through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented in the form of a computer program product, all or part of it. The various embodiments in this specification are described in a progressive or parallel manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the products, media, and electronic devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.

Claims

1. A firmware configuration method, the method comprising: During the power-on phase of an electronic device, the embedded controller acquires the processor's initial capability status information; The processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions; Based on the first capability status information, the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to operate in a first working mode or a second working mode that matches the first capability status information. In the first operating mode, the electronic device supports the implementation of the out-of-band management function; In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

2. The method according to claim 1, wherein the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller based on the first capability status information, including: The embedded controller compares the first capability status information with the second capability status information that was previously acquired and stored. In response to the difference between the first capability status information and the second capability status information, the embedded controller sends a first configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to be in a first operating mode or a second operating mode that matches the first capability status information, and updates the stored second capability status information to the first capability status information.

3. The method according to claim 1, further comprising: The embedded controller reads the currently stored third capability status information in response to the electronic device switching from a completely power-off state to a soft power-off state. Send a second configuration instruction to the power supply controller for the power supply protocol firmware to configure the power supply protocol firmware to be in the first operating mode or the second operating mode that matches the third capability status information.

4. The method according to any one of claims 1-3, wherein, Configuring the power supply protocol firmware to be in a first or second operating mode that matches the capability status information of the currently deployed processor includes: The power supply controller controls the power supply protocol firmware to select and execute a firmware file that matches the capability status information of the currently deployed processor from the configured first firmware file and second firmware file. If the power supply protocol firmware executes the first firmware file, it enters the first working mode; If the power supply protocol firmware executes the second firmware file, it enters the second working mode.

5. A firmware configuration method, the method comprising: During the power-on phase of an electronic device, the system firmware chip determines the processor's initial capability status information; The processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions; The system firmware chip sends the first capability status information to the embedded controller, so that the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller based on the first capability status information, so as to configure the power supply protocol firmware to be in a first working mode or a second working mode. In the first operating mode, the electronic device supports the implementation of the out-of-band management function; In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

6. The method according to claim 5, further comprising any one of the following: The system firmware chip determines that the electronic device has replaced its processor, reads the type information of the replaced processor, and determines the fourth capability status information of the processor. In response to the first power-on of the electronic device, the system firmware chip reads the processor type information to determine the processor's first capability status information.

7. A computer program product comprising computer-readable instructions that, when executed on an electronic device, cause the electronic device to perform the following steps: During the power-on phase of the electronic device, the embedded controller acquires the processor's first capability status information; the processor's capability status information indicates whether the processor has the hardware capabilities required to implement out-of-band management functions. Based on the first capability status information, the embedded controller sends a configuration instruction for the power supply protocol firmware to the power supply controller to configure the power supply protocol firmware to operate in a first working mode or a second working mode that matches the first capability status information. in, In the first operating mode, the electronic device supports the implementation of the out-of-band management function; In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

8. An electronic device, the electronic device comprising: The system firmware chip, embedded controller, processor, and power supply controller deployed on the motherboard include: The system firmware chip is used to communicate with the embedded controller and the processor respectively, determine the first capability status information of the processor, and send the first capability status information to the embedded controller; the capability status information of the processor indicates whether the processor has the hardware capability required to implement out-of-band management functions. The embedded controller is configured to send configuration instructions for the power supply protocol firmware to the power supply controller based on the first capability status information. The power supply controller is configured, in response to the configuration command, to configure the power supply protocol firmware to be in a first working mode or a second working mode that matches the first capability status information. In the first operating mode, the electronic device supports the implementation of the out-of-band management function; In the second operating mode, the electronic device does not support the implementation of the out-of-band management function.

9. The electronic device according to claim 8, further comprising: An integrated southbridge chip is used to deploy management engine firmware and, based on the first capability status information, to achieve switching control between the first working mode and the second working mode; If the processor does not have the hardware capability required to implement out-of-band management functions, the integrated southbridge chip switches to the second operating mode so that the management engine firmware refuses to implement the out-of-band management functions.

10. The electronic device according to claim 8, wherein: The signal repeater firmware deployed in the signal repeater chip of the electronic device is configured to the first operating mode; The embedded controller is communicatively connected to the power supply controller via a system management bus; The system firmware chip communicates with the embedded controller via a serial peripheral interface.

Images