The HECI bus allows the host operating system (OS) to communicate directly with the Management Engine (ME) integrated in the chipset. This bi-directional, variable data-rate bus enables the host and ME to communicate system management information and events in a standards-compliant way, essentially replacing the System Management Bus (SMBus). The bus consists of four wires: a request and grant pair along with a serial transmit and receive data pair.
Original equipment manufacturers (OEMs) have historically provided active management technologies through the use of proprietary on-board controllers, such as Baseboard Management Controllers. These solutions typically suffer two main disadvantages due to their proprietary nature. High BOM costs are usually incurred due to the need for additional components and routing. High product lifecycle costs are incurred due to the non-standard implementation, which increases software and hardware design and validation costs while remaining relatively inflexible to future changes. On the other hand, the inflexibility is even greater with HECI due to coupling HECI with a chipset, and having to redevelop HECI software for each different chipset as opposed to one common BMC software for multiple chipsets.
HECI and the previously used SMBus have the following aspects in common: the Host OS is able to control system management devices such as: on-board fan controllers, remote wake devices such as Wake-on-LAN, power supply devices such as Smart Battery Data. Builtin HECI functionality and third-party management cards can allow the Host OS to directly initiate management events (such as remote wake, or, out-of-band throttling to decrease thermal and power profile) in case HECI is supported by the running OS. Example devices are network cards and graphics cards. Besides that, both HECI and other ME technologies are chipset/ME vendor-specific.
The Intel® Chipset Device Software installs Windows* INF files to the target system. These files outline to the operating system how to configure the Intel® chipset components in order to ensure that the following features function properly: - Core PCI and ISAPNP Services - PCIe* Support - IDE/ATA33/ATA66/ATA100 Storage Support - SATA Storage Support - USB Support - Identification of Intel® Chipset Components in the Device Manager
Other than the common sense of installing the chipset first, so as to have access to all peripherals, or some rare exceptions that will come with notifications, the order of driver installation makes no difference at all, so no worries.
Thanks guys!! Can I trouble you for your feedback on something else. Every few months I clean install the Windows operating system on my PC. Is it the same for you in that sometimes the Windows 8 setup picks up all of the devices (it usually only misses one..a Bluetooth peripheral device with a question mark. That's easily sorted by installing Wireless drivers from Dell site). Then on other occasions it'll leave the occasional exclamation mark usually listed in Other Devices but not always. That disappears when the chipsets are installed. Most of the time I never get these at all but its happened a couple of times lately. Im wondering if its caused because Im installing from Windows 8 DVD and not from a factory image.
Correction 2017-05-12: Intel has contacted us with two corrections to the details of this post. (1) Management Engines are not physically located on the CPU die itself, but in other parts of Intel's chipsets; (2) the LMS-based local privilege escalation was a second consequence of the first code vulnerability, rather than a second vulnerability or bug of its own. We have accordingly edited the language of this post in a couple of places, but do not believe these updates affect its conclusions.
The Intel Management Engine (Intel ME) is an isolated and protected computingresource (Co-processor) residing inside certain Intel chipsets. The Intel MEprovides support for computer/IT management and security features.The actual feature set depends on the Intel chipset SKU.
Dell has ALL the drivers for your system. Go to the Dell website at the link given before and download the necessary drivers. If you need a chipset driver then click on theChipset tab!
Intel chipsets include a "Management Engine" (ME), which is a small microprocessor that runs independently of the system CPU and operating system. A flaw was found in the Intel AMT ( Active Management Technology ) running on the ME; the flaw allows remote attackers to "escalate privileges" and evade OS level detection.
Most PCs ship a 5MiB version of ME firmware. It is possible to use a smaller version (2MiB), but you have to make sure that it matches the chipset you are running on. You may want to use a smaller version to increase the maximum payload size by 3MiB. Search on the web for BIOS updates of different vendors with the same chipset and extract the ME using available tools. Once you found a smaller ME, you have to update your Intel flash descriptor and decrease the region that is used for ME.
If you are using an Intel laptop or laptop with Intel chipsets, then you may find the Intel Management Engine Components program. It is an embedded microcontroller - integrated on certain Intel chipsets - running a lightweight microkernel operating system. This program offers the Intel Management Engine Components Driver from the Intel processor-based computer systems.
It provides many features and services for Intel processor-based computers. For instance, the Intel R Management Engine Components can monitor your installed Intel hardware like chipsets, hard disks, and other components. Furthermore, it notifies you if there are updated drivers, issues, or other useful information about these components installed by the computer manufacturer automatically during the OS installation.
Innovation Engine (IE) is a tiny microcontroller coprocessor integrated within Intel's server chipsets that provides the framework necessary for system designers to create their own highly customized firmware. From an architectural standpoint, IE is very similar to Intel's Management Engine (ME), but is designed as an "open engine", allowing system designers to develop their own differentiating firmware. IE complements ME and are both present starting with the introduction of the Lewisburg chipset.
Intel introduced Innovation Engine (IE) starting with the Lewisburg chipset (i.e., Skylake-SP parts). IE is integrated along with ME into the chipset. Whereas ME is designed specifically for Intel's features, IE is designed specifically for system designers. That is, Intel only provides the hardware to operate IE but unless the system designers develop specific firmware for it, it does not do anything.
Yet another utility for collecting information about Intel ME comes from the Coreboot project and is called intelmetool. intelmetool will attempt to discover Intel ME and list the capabilities, including if manufacturing mode is enabled (or not). The instructions below show you how to download, compile and run intelmetool: 2b1af7f3a8