Electronic devices can include various components for performing different tasks. For example, the components can include a processor, a memory, an embedded controller, an input/output (I/O) device, and other components. Various code (in the form of machine-readable instructions including firmware and/or software) are executable on the embedded controller, the processor, and other components.
Some implementations of the present disclosure are described with respect to the following figures.
Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements. The figures are not necessarily to scale, and the size of some parts may be exaggerated to more clearly illustrate the example shown. Moreover, the drawings provide examples and/or implementations consistent with the description; however, the description is not limited to the examples and/or implementations provided in the drawings.
In the present disclosure, use of the term “a,” “an”, or “the” is intended to include the plural forms as well, unless the context clearly indicates otherwise. Also, the term “includes,” “including,” “comprises,” “comprising,” “have,” or “having” when used in this disclosure specifies the presence of the stated elements, but do not preclude the presence or addition of other elements.
Machine-readable instructions executable by various components of an electronic device may be corrupted for a number of reasons. For example, an unauthorized entity, such as malware, may modify the instructions or data used by the instructions to cause the instructions to no longer be operational or to operate in an unintended manner. Corruption of instructions can also be due to other causes, including failure to update the instructions with a latest code update, errors introduced by defective hardware or a program, and so forth.
Examples of electronic devices include any or some combination of the following: computers (e.g., desktop computers, notebook computers, tablet computers, server computers, etc.), handheld devices (e.g., smartphones, game appliances, etc.), wearable devices (e.g., smart watches, head-mounted devices, smart eyeglasses, etc.), Internet-of-Things (IoT) devices, controllers in vehicles, storage systems, communication nodes, and so forth.
If the machine-readable instructions (e.g., firmware) of certain components of an electronic device become corrupted, then the electronic device may not be able to boot successfully and thus can become non-operational. For example, an electronic device may include core hardware logic that performs certain functionalities for the electronic device. For example, the core hardware logic can include any or some combination of the following: an input/output (I/O) control logic to manage interaction with I/O components of the electronic device, a display control logic to control display of images at a display device, a memory control logic to manage access of a memory, a storage control logic to manage access of a persistent storage such as a disk-based storage or solid state drive, and so forth.
The core hardware logic of the electronic device can also be referred to as a “chipset” of the electronic device, where the chipset can include one integrated circuit (IC) chip or multiple IC chips, depending on the implementation.
Certain components of the core hardware logic can execute machine-readable instructions, such as firmware and/or software. One such component includes a management engine of the core hardware logic. Examples of management engines include the Management Engine (ME) from Intel, the Secure Processor from Advanced Micro Devices (AMD), and so forth. More generally, the core hardware logic can include a core controller (e.g., the ME or Secure Processor) that performs certain basic tasks in an electronic device to enable operation of the electronic device.
An example of a task that can be performed by firmware executed on the core controller include configuration of settings of a processor, such as configuring a clock of the processor, configuring a voltage of the processor, configuring power management control by the processor, and so forth. In other examples, the firmware executed on the core controller can also provide security for the electronic device (such as by storing an encryption key in a storage), enable remote management of the electronic device (in which an entity that is coupled to the electronic device over a network can manage the electronic device), and so forth.
If the firmware of the core controller becomes corrupted for any reason, then the core controller would not be able to perform its tasks during startup of an electronic device. As a result, the processor of the electronic device would not be configured properly (because the core controller has experienced a fault), and thus the processor may remain non-operational. As a result, boot code of the electronic device cannot start, and the electronic device will not operate.
In accordance with some implementations of the present disclosure, an electronic device includes a controller (e.g., an embedded controller), which is separate from the processor of the electronic device. The embedded controller is able to detect corruption of machine-readable instructions (e.g., firmware) executable by a core hardware logic (such as by a core controller). In response to detecting the corruption of the machine-readable instructions of the core hardware logic, the embedded controller can retrieve a recovery code and load the recovery code to the core hardware logic. The core hardware logic can execute the recovery code to allow the core hardware logic to perform certain basic tasks, including configuring the processor to enable functioning of the processor. Once the functioning of the processor is enabled, a boot code of the electronic device can execute on the processor, and the boot code can perform a full recovery process to recover from the corruption of the machine-readable instructions of the core hardware logic, including retrieving a full recovery image for the core hardware logic.
The chipset 104 includes a core controller 108. The core controller 108 can perform various tasks as noted above. One of the tasks that can be performed by the core controller 108 is configuring settings of the processor 106, to enable the processor 106 to operate during startup of the electronic device 100.
In some examples, the embedded controller 102 can be used to perform specific predefined tasks. In some examples, the tasks of the embedded controller 102 are performed by embedded controller (EC) code (that is part of EC information) 118, in the form of machine-readable instructions such as EC firmware or EC software, executed on the embedded controller 102. In other examples, the tasks of the embedded controller 102 can be performed by a hardware processing circuit of the embedded controller 102. Examples of tasks that can be performed by the embedded controller 102 include any one or some combination of the following: power supply control in the electronic device 100 (for controlling a power supply that supplies power supply voltages to various components in the electronic device 100), charging and control of a battery in the electronic device 100, thermal monitoring (to monitor a temperature in the electronic device 100), fan control (to control a fan in the electronic device 100), and interaction with a user input device (such as performing a scan of a keyboard of the electronic device 100 or interaction with a pointing device such as a mouse, touchpad, touchscreen, and so forth). In other examples, the embedded controller 102 can perform additional or alternative tasks. The embedded controller 102 can be implemented with a microcontroller, an application-specific integrated circuit (ASIC), a programmable gate array (PGA), or any other type of programmable circuit.
The electronic device 100 further includes an embedded controller (EC) storage device 110, a shared storage device 112, and a mass storage device 114. In some examples, the EC storage device 110 is a private storage device for the embedded controller 102. In such examples, the data in the EC storage device 110 is accessible by the embedded controller 102, but not accessible by any other component of the electronic device 100, including the processor 106 and the chipset 104.
The shared storage device 112 is accessible by multiple components, including the embedded controller 102, the chipset 104, and the processor 106. Access of the shared storage device 112 can be performed over a shared bus 115.
The mass storage device 114 is a storage device that has a larger capacity than the shared storage device 112 or the EC storage device 110. Each of the EC storage device 110, the shared storage device 112, and the mass storage device 114 can be implemented using a nonvolatile memory. A nonvolatile memory can include one nonvolatile memory device, or multiple nonvolatile memory devices. Examples of nonvolatile memory devices include a flash memory device, a phase change memory device, a memristor memory device, and so forth. In further examples, a nonvolatile memory can also be implemented using a disk-based storage device. In further examples, the data in the mass storage device 114 may also be accessible by the processor 106 and the embedded controller 102. In such further examples, the embedded controller 102 is able to access the data in the mass storage device 114 even when the processor 106 is non-operational, such as during the initial stages of startup of the electronic device 100, or due to a corruption in the electronic device 100.
The shared storage device 112 can be used to store various different information, including a core controller information 116, the EC information 118, and boot code 120. The core controller information 116 includes core controller code (in the form of machine-readable instructions) and core controller data that is useable by the core controller code. In some examples, the core controller code includes core controller firmware executable by the core controller 108. The EC information 118 includes EC code (in the form of machine-readable instructions) and EC data useable by the EC code. The EC code can include EC firmware executable by the embedded controller 102.
Although
During startup of the electronic device 100, the core controller 108 is able to retrieve the core controller code (part of the core controller information 116) from the shared storage device 112 over the shared bus 115, for execution on the core controller 108 to perform tasks of the core controller 108. Prior to the loading of the core controller code on the core controller 108, the embedded controller 102 can first verify the integrity of the core controller code and the core controller data.
The embedded controller 102 includes a core recovery logic 122 to perform verification of the core controller information 116. The core recovery logic 122 can be implemented using a portion of the hardware processing circuit of the embedded controller 102, or alternatively, can be implemented as machine-readable instructions executable by the embedded controller 102.
Verifying a piece of information can refer to cryptographically validating that the piece of information has not been changed and/or confirming that the piece of information is from a trusted source. In some examples, a cryptographic-based verification technique can include a Rivest, Shamar, and Adleman (RSA) verification technique that employs cryptographic encryption. The RSA verification technique involves use of a public key and a private key. The public key is known to multiple entities, but the private key is only known to a single entity. Data encrypted with a private key can be decrypted using the corresponding public key. Alternatively, data can be encrypted using the private key, but decrypted using the public key.
For example, the core controller information 116 stored in the shared storage device 112 can be encrypted using a public key or a private key. To verify the integrity of the core controller information 116, the embedded controller 102 can decrypt the encrypted core controller information 116 using the corresponding private key or public key. If decryption is successful, then the core controller information 116 is verified.
In other examples, other cryptographic-based verification techniques can be employed, such as a Secure Hashing Algorithm (SHA), and so forth.
In further examples, to verify the source and integrity of a piece of information, a signature can be stored in association with the piece of information (either part of the piece of information or as metadata associated with the piece of information). In some examples, the verification of the core controller information 116 can be accomplished by decrypting the associated signature using an encryption key accessible by the embedded controller 102. Decrypting the signature produces a respective value (e.g., a hash value) that can be compared with a corresponding calculated value (e.g., hash value) of the core controller information 116. If the foregoing values match, then the integrity and source of the core controller information 116 is verified.
If the core recovery logic 122 is unable to verify the core controller information 116, then that is an indication that the core controller information 116 is corrupted. The core recovery logic 122 can, in response to detection of corruption of the core controller information 116, initiate a recovery process for the core controller 108.
The EC storage device 110 stores a core recovery code 124. Note that the core recovery code 124 can be a copy of a core recovery code 125 that is a portion of the core controller code (in the core controller information 116) stored in the shared storage device 112. At some point during initial operation of the electronic device 100, which can be during initialization at the factory, initialization by a user, etc., the embedded controller 102 can copy the recovery code portion 125 of the core controller code to the EC storage device 110, for storage as the core recovery code 124.
In response to detection of corruption of the core controller information 116, the core recovery logic 122 prevents the core controller code in the shared storage device 112 from being loaded onto the core controller 108 for execution. For example, the core recovery logic 122 can disable the ability of the chipset 104 to access the shared storage device 112 in response to detection of corruption of the core controller information 116.
To trigger recovery from the corruption of the core controller information 116, the core recovery logic 122 retrieves the core recovery code 124 from the EC storage device 110, and replaces the core recovery code 125 in the shared storage device 112 with the core recovery code 124. The replaced core recovery code 125 (as replaced with the core recover code 124) is loaded by the core controller 108 when the core controller 108 is booted. The replaced core recovery code 125 when executed by the core controller 108 causes the core controller 108 to perform various basic tasks, including configuring the settings of the processor 106 so that the processor 106 can function.
Once the processor 106 is configured, the core controller 108 allows the remaining startup process of the electronic device 100 to proceed, including loading of the boot code 120 for execution on the processor 106.
In some examples, the replaced core recovery code 125 when executed by the core controller 108 can set a flag, such as a recovery flag 126 in the shared storage device 112, to indicate that a core controller recovery process is in progress. The core controller recovery process refers to a process of recovering from corruption of instructions executable by the core controller 108.
A “flag” can refer to any information element, in the form of a bit or a combination of bits, that is settable to different values. If the recovery flag 126 is set to a first value, then that indicates that the core controller recovery process is in progress. If the recovery flag is set to a second value different from the first value, that indicates that a normal startup process of the electronic device 100 is in progress.
When the boot code 120 executes on the processor 106, the boot code 120 determines the state of the recovery flag 126. If the recovery flag 126 is set to the first value, then the boot code 120 performs the core controller recovery process. In the core controller recovery process, the boot code 120 retrieves a full core controller code image 128 from the mass storage device 114. The full core controller code image 128 is a known uncorrupted version of core controller code.
The boot code 120 can replace the corrupted core controller information 116 in the shared storage device 112 with the full core controller code image 128. Once replaced, the full core controller code image 128 becomes the core controller information 116 of the electronic device 100, and the core controller code of the core controller information 116 can be executed by the core controller 108 to perform further tasks of the core controller 108.
Subsequently, the boot code 120 can complete the remaining boot process, which includes initializing various hardware components of the electronic device 100, and loading an operating system (OS) 130 for execution on the processor 106.
The core recovery logic 122 verifies (at 204) the integrity of the core controller information 116 stored in the shared storage device 112. The core recovery logic 122 determines (at 206) whether the core controller information 116 is corrupted based on whether or not the core controller information 116 is successfully verified. If the core controller information 116 is successfully verified, then the core controller information 116 is not corrupted. However, if the core controller information 116 is not successfully verified, then the core controller information 116 is corrupted.
If the core controller information 116 is not corrupted, then the core recovery logic 122 allows (at 208) the remainder of a startup process to continue, including loading of the core controller code onto the core controller 108 for execution by the core controller 108, followed by loading of the boot code 120 for execution on the processor 106 to perform boot tasks.
If the core recovery logic 122 determines (at 206) that the core controller information 116 is corrupted, then the core recovery logic 122 retrieves (at 210) the core recovery code 124 from the EC storage device 110, and replaces the core recovery code 125 (that is part of the core controller information 116) with the retrieved core recover code 124. The replaced core recovery code 125 is loaded (at 212) by the core recovery logic 122
The replaced core recovery code 125 executed by the core controller 108 configures (at 214) the processor 106 to enable functioning of the processor 106. After the processor is enabled, the boot code 120 is executed (at 216) by the processor 106.
The boot code 120 executed on the processor 106 determines (at 218) the value of the recovery flag 126, and if the recovery flag 126 is set to the first value that indicates that the core controller recovery process is in progress, the boot code 120 retrieves (at 220) the full core controller code image 128 from the mass storage device 114. The boot code 120 replaces (at 222) the corrupted core controller information 116 in the shared storage device 112 with the full core controller code image 128. The recovered core controller code is then loaded (at 224) for execution by the full core controller 108, which performs the remaining tasks of the core controller 108, followed by performing (at 226) the boot process by the boot code 120.
If the boot code 120 determines (at 218) that the value of the recovery flag 126 is set to the second value that indicates a normal startup process, the boot process is performed (at 226) by the boot code 120.
A controller 306 (e.g., an embedded controller) separate from the hardware processor 302 is able to perform various tasks. The tasks include an instructions corruption detection task 308 to detect corruption of the instructions, and a recovery code using task 310 to, in response to detecting the corruption, use a recovery code to trigger recovery of the core hardware logic from the corruption of the instructions.
The recovery code is executable on the core hardware logic 304 to enable functioning of the hardware processor 302, by configuring the hardware processor 302. As discussed above, the recovery code can be retrieved from an EC storage device (e.g., 110 in
The machine-readable instructions further include recovery code loading instructions 404 to, in response to detecting the corruption of the information, retrieve a recovery code from a controller storage accessible by the controller, and replace a recovery code in the information. The machine-readable instructions further include recovery code execution instructions 406 to execute the replaced recovery code by the core hardware logic to configure a processor separate from controller. The machine-readable instructions additionally include boot code execution instructions 408 to, after the configuring of the processor, execute a boot code on the processor.
The process of
After enabling of the functioning of the processor by the core hardware logic, the process of
The storage medium 400 of
In the foregoing description, numerous details are set forth to provide an understanding of the subject disclosed herein. However, implementations may be practiced without some of these details. Other implementations may include modifications and variations from the details discussed above. It is intended that the appended claims cover such modifications and variations.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2019/017459 | 2/11/2019 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2020/167283 | 8/20/2020 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4503535 | Budde et al. | Mar 1985 | A |
5269022 | Shinjo et al. | Dec 1993 | A |
5327531 | Bealkowski et al. | Jul 1994 | A |
5432927 | Grote et al. | Jul 1995 | A |
5469573 | McGill, III et al. | Nov 1995 | A |
5564054 | Bramnick et al. | Oct 1996 | A |
5713024 | Halladay | Jan 1998 | A |
5745669 | Hugard et al. | Apr 1998 | A |
5778070 | Mattison | Jul 1998 | A |
5819087 | Le et al. | Oct 1998 | A |
5822581 | Christeson | Oct 1998 | A |
5828888 | Kozaki et al. | Oct 1998 | A |
5918047 | Leavitt et al. | Jun 1999 | A |
5987605 | Hill et al. | Nov 1999 | A |
6205527 | Goshey et al. | Mar 2001 | B1 |
6223336 | Tojima | Apr 2001 | B1 |
6275930 | Bonamico | Aug 2001 | B1 |
6539473 | Hubacher et al. | Mar 2003 | B1 |
6594785 | Gilbertson et al. | Jul 2003 | B1 |
6651188 | Harding et al. | Nov 2003 | B2 |
6665813 | Forsman et al. | Dec 2003 | B1 |
6711675 | Spiegel et al. | Mar 2004 | B1 |
6934881 | Gold et al. | Aug 2005 | B2 |
7069445 | Cheston et al. | Jun 2006 | B2 |
7100087 | Yang et al. | Aug 2006 | B2 |
7136994 | Zimmer et al. | Nov 2006 | B2 |
7193895 | Jin et al. | Mar 2007 | B2 |
7203808 | Rothman et al. | Apr 2007 | B2 |
7340595 | Blinick et al. | Mar 2008 | B2 |
7383431 | Takamizawa et al. | Jun 2008 | B2 |
7409539 | Arnez et al. | Aug 2008 | B2 |
7483810 | Jackson et al. | Jan 2009 | B2 |
7613872 | Dayan et al. | Nov 2009 | B2 |
7698698 | Skan | Apr 2010 | B2 |
7734945 | Levidow et al. | Jun 2010 | B1 |
7818622 | Burks, III et al. | Oct 2010 | B2 |
7890726 | Falik et al. | Feb 2011 | B1 |
7900091 | Chou et al. | Mar 2011 | B2 |
7908470 | Cavanna | Mar 2011 | B1 |
7930532 | Lin et al. | Apr 2011 | B2 |
7930576 | Harris et al. | Apr 2011 | B2 |
8006125 | Meng et al. | Aug 2011 | B1 |
8082384 | Sareen et al. | Dec 2011 | B2 |
8086841 | Guo et al. | Dec 2011 | B2 |
8132253 | Martinez et al. | Mar 2012 | B2 |
8190950 | Chen et al. | May 2012 | B2 |
8230210 | Polyudov | Jul 2012 | B1 |
8255988 | Carpenter | Aug 2012 | B2 |
8316200 | Matsuoka et al. | Nov 2012 | B2 |
8332934 | Lee et al. | Dec 2012 | B2 |
8341386 | Lee et al. | Dec 2012 | B2 |
8392762 | Ramegowda et al. | Mar 2013 | B2 |
8429391 | Galbo et al. | Apr 2013 | B2 |
8489922 | Matthew | Jul 2013 | B2 |
8732527 | Tabone et al. | May 2014 | B2 |
8793477 | Horvath et al. | Jul 2014 | B2 |
9063836 | Swanson et al. | Jun 2015 | B2 |
9251380 | Au et al. | Feb 2016 | B1 |
9411688 | Poolla et al. | Aug 2016 | B1 |
9417967 | Huang et al. | Aug 2016 | B2 |
9542195 | Astarabadi et al. | Jan 2017 | B1 |
9575768 | Kim | Feb 2017 | B1 |
9734339 | Jeansonne et al. | Aug 2017 | B2 |
9785596 | Hodge et al. | Oct 2017 | B2 |
9852298 | Jeansonne et al. | Dec 2017 | B2 |
9880908 | Jeansonne et al. | Jan 2018 | B2 |
9990255 | Jeansonne et al. | Jun 2018 | B2 |
10089472 | Jeansonne et al. | Oct 2018 | B2 |
20010008011 | Oba | Jul 2001 | A1 |
20020002652 | Takahashi | Jan 2002 | A1 |
20020078338 | Lay et al. | Jun 2002 | A1 |
20020144177 | Kondo et al. | Oct 2002 | A1 |
20030079007 | Merkin | Apr 2003 | A1 |
20030126511 | Yang et al. | Jul 2003 | A1 |
20030212936 | Neuman et al. | Nov 2003 | A1 |
20030221114 | Hino et al. | Nov 2003 | A1 |
20040025002 | Cepulis et al. | Feb 2004 | A1 |
20040030877 | Frid | Feb 2004 | A1 |
20040068334 | Tsai et al. | Apr 2004 | A1 |
20040076043 | Boals et al. | Apr 2004 | A1 |
20040133790 | Hensley | Jul 2004 | A1 |
20040153846 | Lee | Aug 2004 | A1 |
20040193862 | Lin | Sep 2004 | A1 |
20040268079 | Riedle et al. | Dec 2004 | A1 |
20050081090 | Lin | Apr 2005 | A1 |
20050108564 | Freeman et al. | May 2005 | A1 |
20050190699 | Smith et al. | Sep 2005 | A1 |
20050210180 | Rothman et al. | Sep 2005 | A1 |
20050251673 | Bosley et al. | Nov 2005 | A1 |
20050273588 | Ong et al. | Dec 2005 | A1 |
20060020844 | Gibbons et al. | Jan 2006 | A1 |
20060075395 | Lee et al. | Apr 2006 | A1 |
20060143431 | Rothman et al. | Jun 2006 | A1 |
20060161784 | Hunter et al. | Jul 2006 | A1 |
20060168435 | Svensson et al. | Jul 2006 | A1 |
20060225067 | Yang | Oct 2006 | A1 |
20060236198 | Lintz et al. | Oct 2006 | A1 |
20070088943 | Phelps et al. | Apr 2007 | A1 |
20070260866 | Wang et al. | Nov 2007 | A1 |
20080040596 | Mai et al. | Feb 2008 | A1 |
20080066075 | Nutter et al. | Mar 2008 | A1 |
20080072030 | Karpa | Mar 2008 | A1 |
20080086629 | Dellow | Apr 2008 | A1 |
20080086631 | Chow et al. | Apr 2008 | A1 |
20080090653 | Kuehling et al. | Apr 2008 | A1 |
20080098381 | Lin | Apr 2008 | A1 |
20080126779 | Smith | May 2008 | A1 |
20080126782 | Dayan et al. | May 2008 | A1 |
20080141016 | Chang et al. | Jun 2008 | A1 |
20080155331 | Rothman et al. | Jun 2008 | A1 |
20080172558 | Stakutis et al. | Jul 2008 | A1 |
20080195750 | Sadovsky et al. | Aug 2008 | A1 |
20080209553 | Lu et al. | Aug 2008 | A1 |
20080269954 | Lev et al. | Oct 2008 | A1 |
20080307134 | Geissler et al. | Dec 2008 | A1 |
20090049293 | Jiang | Feb 2009 | A1 |
20090063834 | Huang et al. | Mar 2009 | A1 |
20090089570 | Andrianov | Apr 2009 | A1 |
20090100287 | Chu et al. | Apr 2009 | A1 |
20090150598 | Jung et al. | Jun 2009 | A1 |
20090150662 | Desselle et al. | Jun 2009 | A1 |
20090158020 | Chen et al. | Jun 2009 | A1 |
20090158024 | Hung et al. | Jun 2009 | A1 |
20090172639 | Natu et al. | Jul 2009 | A1 |
20090217373 | Stillerman et al. | Aug 2009 | A1 |
20090240934 | Chou | Sep 2009 | A1 |
20090248955 | Tamada | Oct 2009 | A1 |
20090249113 | Chou et al. | Oct 2009 | A1 |
20090271602 | Burks, III et al. | Oct 2009 | A1 |
20090327684 | Zimmer et al. | Dec 2009 | A1 |
20100017589 | Reed et al. | Jan 2010 | A1 |
20100064127 | Lee | Mar 2010 | A1 |
20100070800 | Hanna | Mar 2010 | A1 |
20100082960 | Grobman et al. | Apr 2010 | A1 |
20100082968 | Beverly | Apr 2010 | A1 |
20100100720 | Wu et al. | Apr 2010 | A1 |
20100115187 | Wu et al. | May 2010 | A1 |
20100115256 | Challener et al. | May 2010 | A1 |
20100169551 | Yano et al. | Jul 2010 | A1 |
20100235617 | Chen | Sep 2010 | A1 |
20100299493 | McGee, III | Nov 2010 | A1 |
20110029742 | Grube et al. | Feb 2011 | A1 |
20110060899 | Hsieh et al. | Mar 2011 | A1 |
20110066837 | Lee et al. | Mar 2011 | A1 |
20110087872 | Shah et al. | Apr 2011 | A1 |
20110093675 | Lu et al. | Apr 2011 | A1 |
20110093741 | Liang et al. | Apr 2011 | A1 |
20120011393 | Roberts et al. | Jan 2012 | A1 |
20120072710 | Gupta et al. | Mar 2012 | A1 |
20120072897 | Selvam | Mar 2012 | A1 |
20120079174 | Nellans et al. | Mar 2012 | A1 |
20120210165 | Lambert et al. | Aug 2012 | A1 |
20120239920 | Yang | Sep 2012 | A1 |
20120297178 | Peng et al. | Nov 2012 | A1 |
20120303944 | Peng et al. | Nov 2012 | A1 |
20120324150 | Moshayedi et al. | Dec 2012 | A1 |
20130013905 | Held | Jan 2013 | A1 |
20130047031 | Tabone et al. | Feb 2013 | A1 |
20130159690 | Tsukamoto et al. | Jun 2013 | A1 |
20130232325 | Jang et al. | Sep 2013 | A1 |
20140115314 | Huang et al. | Apr 2014 | A1 |
20140237223 | Chudgar et al. | Aug 2014 | A1 |
20140281455 | Kochar | Sep 2014 | A1 |
20140325203 | Roche et al. | Oct 2014 | A1 |
20150095632 | Huang et al. | Apr 2015 | A1 |
20150242656 | Dasari et al. | Aug 2015 | A1 |
20150277930 | Sarangdhar | Oct 2015 | A1 |
20150301880 | Allu et al. | Oct 2015 | A1 |
20150324588 | Locke | Nov 2015 | A1 |
20150378815 | Goda et al. | Dec 2015 | A1 |
20150381647 | Huang et al. | Dec 2015 | A1 |
20160055069 | Jeansonne | Feb 2016 | A1 |
20160055113 | Hodge et al. | Feb 2016 | A1 |
20160055332 | Jeansonne et al. | Feb 2016 | A1 |
20160055338 | Jeansonne et al. | Feb 2016 | A1 |
20160063255 | Jeansonne et al. | Mar 2016 | A1 |
20160211977 | Kohiyama | Jul 2016 | A1 |
20160364570 | Stern | Dec 2016 | A1 |
20170249002 | Costa et al. | Aug 2017 | A1 |
20180089435 | Zander | Mar 2018 | A1 |
20180225167 | Bharadwaj et al. | Aug 2018 | A1 |
20190286436 | Liu | Sep 2019 | A1 |
20200104504 | Chaiken | Apr 2020 | A1 |
Number | Date | Country |
---|---|---|
1534685 | Oct 2004 | CN |
1612115 | May 2005 | CN |
1799028 | Jul 2006 | CN |
1928843 | Mar 2007 | CN |
100472657 | Mar 2009 | CN |
101458743 | Jun 2009 | CN |
101894054 | Nov 2010 | CN |
101965570 | Feb 2011 | CN |
102239472 | Nov 2011 | CN |
102971742 | Mar 2013 | CN |
2815350 | Sep 2018 | EP |
20090034104 | Apr 2009 | KR |
20090060774 | Jun 2009 | KR |
20100017874 | Feb 2010 | KR |
101038567 | Jun 2011 | KR |
480444 | Mar 2002 | TW |
I280487 | May 2007 | TW |
200809489 | Feb 2008 | TW |
200842567 | Nov 2008 | TW |
200931312 | Jul 2009 | TW |
200941344 | Oct 2009 | TW |
201007465 | Feb 2010 | TW |
201020785 | Jun 2010 | TW |
201133342 | Oct 2011 | TW |
WO-201 0135485 | Nov 2010 | WO |
WO-2012148422 | Nov 2012 | WO |
Entry |
---|
“TMS320C31 Embedded Control”, Texas Instruments, Feb. 1998, 184 pgs, http://www.ti.com/lit/an/spru083/spru083.pdf. |
Hodge et al., International Application No. PCT/US13/37725 entitled Redundant System Boot Code in a Secondary Non-Volatile Memory filed Apr. 23, 2013 (25 pages). |
Hoffman, Chris, Intel Management Engine, Explained: The Tiny Computer Inside Your CPU, How-To Geek, Dec. 21, 2017, 10 pages. |
HP Sure Start, Technical White Paper, Automatic firmware intrusion detection and repair, Feb. 2018, 14 pages. |
Intel, WkiChip, Management Engine (ME), last modified Jul. 23, 2018, 9 pages, https://en.wikichip.org/wiki/intel/management_engine. |
International Search Report and Written Opinion received in PCT Application No. PCT/US2013/037729, dated Jan. 22, 2014, 9 pgs. |
Jeansonne et al., International Application No. PCT/US13/37724 entitled Recovering From Compromised System Boot Code filed Apr. 23, 2013, 29 pages. |
Jeansonne et al., International Application No. PCT/US13/37727 entitled Configuring a System filed Apr. 23, 2013, 35 pages. |
Jeansonne et al., International Application No. PCT/US13/37728 entitled Event Data Structure To Store Event Data filed Apr. 23, 2013, 36 pages. |
Jeansonne et al., International Application No. PCT/US13/37729 entitled Repairing Compromised System Data in a Non-Volatile Memory filed Apr. 23, 2013, 25 pages. |
Jeansonne et al., International Application No. PCT/US 13/37733 entitled Retrieving System Boot Code From a Non-Volatile Memory filed Apr. 23, 2013, 26 pages. |
Jeansonne et al., International Application No. PCT/US13/37735 entitled Verifying Controller Code and System Boot Code filed Apr. 23, 2013, 36 pages. |
Lee, Matthew, “Embedded Controller Usage in Low Power Embedded Designs an Overview”, Sep. 2011, 19 pgs, http://download.intel.com/design/intarch/papers/326133.pdf. |
Margaret Rouse, Definition from Whatis.com, NAND flash memory, Apr. 18, 2013, 7 pages. |
Margaret Rouse, Definition from Whatis.com, NOR flash memory, Nov. 13, 2017, 8 pages. |
Patelay, Wolfgang, “A Single-chip Solution for System-supervisory Functions”, Jun. 18, 2010, 44 pgs, http://www.embedded-control-europe.com/digitalissues/ecejun10/files/ecejun10.pdf. |
Regenscheid, Andrew, NIST Special Publication 800-193, Platform Firmware Resiliency Guidelines, May 2018, 45 pages. |
Regenscheid et al., “BIOS Integrity Measurement Guidelines (Draft)”, Dec. 2011, 47 pgs, http://csrc.nist.gov/publications/drafts/800-155/draft-SP800-155_Dec2011.pdf. |
Wikipedia, Amd Platform Security Processor, last edited Nov. 7, 2018, 2 pages. |
Wikipedia, Flash memory, last edited Jan. 3, 2019, 19 pages. |
Wikipedia, Intel Active Management Technology, last edited Oct. 13, 2018, 11 pages. |
Wikipedia, Intel Management Engine, last edited Dec. 17, 2018, 8 pages. |
Yin et al; Verification-based Multi-backup Firmware Architecture, an Assurance of Trusted Boot Process for the Embedded Systems, 2011 International Joint Conference of IEEE TrustCom, Nov. 16-18, 2011, 1188-1195. |
Number | Date | Country | |
---|---|---|---|
20210365320 A1 | Nov 2021 | US |