eSPI Protocol

eSPI (Enhanced Serial Peripheral Interface) is the Intel-defined bus that links a PC or server chipset to its embedded controller, BMC or Super I/O, replacing the older LPC bus: a clock and two or four IO lines (single, dual or quad IO) at 1.8 V and up to 66 MHz, carrying four logical channels over one link. To capture and decode it, use the Promira eSPI Bus Analyser Kit, which monitors all four channels in single, dual and quad IO without driving the bus.

1.8 VIO level, compared with 3.3 V on LPC
20 to 66 MHzClock rates 20, 25, 33, 50 and 66 MHz
Single, dual, quadIO modes on IO[3:0]
4 channelsPeripheral, virtual wire, out-of-band, flash
CRC on every packetAlways sent; checking is switched on by the controller
Intel specificationEnhanced Serial Peripheral Interface Base Specification

How the eSPI Bus Is Wired

The chipset or SoC is the controller. It drives the clock and shares the IO lines with each target, and each target has its own chip select. Targets use an ALERT# line, or an in-band alert on IO1 when only one target is present, to ask the controller to poll them, because only the controller can start a transaction. A reset line holds the eSPI interfaces in a known state while the platform powers up.

eSPI wiring: chipset controller, two targets, shared clock and IO lines, one chip select per targetThe chipset or SoC is the eSPI controller. It drives the clock and shares four IO lines with two targets, an embedded controller and a BMC, each with its own chip select and alert line. Four logical channels run over the one link: peripheral, virtual wire, out-of-band and flash access. A protocol analyser taps the link and only listens.Controllerchipset (PCH) or SoCCLKIO[3:0]CS0#, ALERT0#CS1#, ALERT1#Embedded controllertarget 0BMC or Super I/Otarget 1Protocol analyserlistens, never drivesPeripheralVirtual wireOut-of-bandFlash accessFour channels share one physical link
One controller, two targets. Clock and IO lines are shared; chip select and alert are per target. Four logical channels share the link.

Electrically, eSPI looks like Quad SPI at 1.8 V. Pin counts drop compared with LPC mainly because sideband signals travel as in-band virtual wire messages. Logically, it is very different: every transfer is a packet with a CRC, the target always answers with a status word, and the channel number tells the receiver what kind of traffic it is.

The Four eSPI Channels

ChannelWhat It CarriesReplaces
PeripheralI/O and memory cycles to the target, such as the embedded controller's ports and ACPI registersLPC I/O and memory cycles
Virtual wireSideband signals sent as messages: sleep states, platform reset, SMI and SCI events, interruptsDedicated GPIO and sideband pins
Out-of-band (OOB)SMBus-style messages tunnelled between the chipset and the target, for example for a BMCSeparate SMBus links
Flash accessShared access to the system SPI flash, from controller to target or target to controller depending on the flash sharing modeSeparate flash wiring to the EC

How an eSPI Transaction Works

eSPI transaction phasesChip select goes low. The controller sends the command phase: opcode, header, any data and a CRC. Two turn-around clocks follow while the bus changes direction. The target then sends the response phase: a response code, header, any data, status and a CRC. Chip select returns high.CS#IOCommandopcode, header, data, CRCcontroller drivesTAR2 clocksResponseresponse code, header, data, status, CRCtarget drives
Every transaction is a command from the controller, a two-clock turn-around, then a response from the target, all inside one chip-select window.
  1. Select: the controller pulls one chip select low. Only one target is selected at a time.
  2. Command phase: the controller sends an opcode that names the channel, a header giving the cycle type, tag and length, any data, and a CRC.
  3. Turn-around: two clocks while the IO lines change direction.
  4. Response phase: the target answers with a response code (accept, defer, wait states or error), any data, a status word showing which of its queues have traffic waiting, and a CRC.
  5. Deselect: chip select returns high. If the status shows pending data, the controller follows up with a read of that channel.

After reset the link starts in single IO at 20 MHz. The controller reads each target's capabilities and then raises the clock and IO width, so a capture from power-on shows the configuration being negotiated before normal traffic.

Where eSPI Is Used

  • Laptops and desktops: the embedded controller that handles the keyboard, battery, fans, lid switch and power sequencing talks to the chipset over eSPI.
  • Servers: the BMC uses eSPI for host communication, virtual wires and, often, access to the host's boot flash.
  • Industrial and embedded x86 boards: Super I/O chips for legacy serial ports, hardware monitoring and watchdogs.
  • Firmware development: BIOS and EC teams bringing up power sequencing, sleep states and flash sharing.

Common eSPI Faults and How to Find Them

SymptomLikely CauseWhat to Check
Platform hangs early in bootThe target never completes the capability exchange, or answers with an errorCapture from reset and read the configuration cycles and response codes
Sleep or wake failsA virtual wire such as a sleep-state or platform reset indication is missing or sent in the wrong orderFilter the virtual wire channel and compare the sequence with the platform design guide
Intermittent CRC errorsSignal integrity at the chosen clock and IO widthCheck whether errors stop at a lower frequency or single IO; probe edges with a scope
EC cannot read the shared flashFlash sharing mode set differently on the chipset and the ECDecode the flash access channel and confirm which side issues the requests
Long stalls between transactionsTarget answering with repeated wait or defer responsesLook at response codes and timestamps to see which cycles are deferred

Tools for Analysing and Decoding eSPI

Watch tools listen to the link between the chipset and its targets and decode every packet. Because eSPI runs at 1.8 V and up to 66 MHz in quad IO, a general-purpose logic analyser needs a dedicated eSPI decoder and enough sample rate to be useful; a protocol analyser built for eSPI is the practical choice.

ProductRoleCapabilityPrice ex VAT
Total Phase Promira eSPI Bus Analyser KitWatchPromira platform with the eSPI Analysis application: monitors 20 to 66 MHz in single, dual and quad IO; decodes peripheral, virtual wire, OOB and flash channels; two chip selects, two alert lines and two reset lines€2.664,95
eSPI Analysis Application (TP601010)WatchThe same eSPI analysis licence, for a Promira you already own€1.520,95 plus the Promira

The Promira also runs I2C and SPI analysis and host applications, so one unit, with the right licences, can also monitor SMBus and SPI flash traffic up to 40 MHz on the same board. See the full Total Phase I2C, SPI and eSPI tools range, or ask us which licences fit your platform.

Frequently Asked Questions

What Is the Difference Between eSPI and SPI?

eSPI reuses the SPI pins and quad IO signalling at 1.8 V, but adds packets, CRCs, response codes and four logical channels. A plain SPI decoder will show the bits but not the transactions; you need an eSPI-aware decoder.

Why Did eSPI Replace LPC?

LPC needs a 33 MHz, 3.3 V, 4-bit multiplexed bus (7 required pins, up to 13 in all) plus separate sideband signals. eSPI runs at 1.8 V, carries those sideband signals as virtual wires, and adds out-of-band and flash access channels, so the chipset needs fewer pins.

Can a Logic Analyser Decode eSPI?

Only with enough sample rate for a 66 MHz clock and a decoder that understands eSPI packets and channels. For bring-up and debugging, a dedicated eSPI analyser shows transactions, response codes and channel traffic directly.

What Clock Speed Does eSPI Start At?

After reset, eSPI starts in single IO mode at 20 MHz. The controller then reads the target capabilities and switches to the agreed frequency and IO width.

Where to Start with eSPI

More Protocols

By John Legg CEng, Director, Debug Store. Updated 3 November 2026.