Skip to main content

// NVMe-MI over I3C

Bring up and debug
NVMe-MI over I3C.

Out-of-band SSD management is moving to an I3C sideband: EDSFF drives a BMC can inventory, monitor, and update without touching the host. Binho gives you the tools to bring it up, decode the full stack, and debug what breaks.

// out-of-band management

Manage every drive. Without the host.

NVMe-MI, the NVM Express Management Interface, is the standard way a BMC inventories, monitors, updates, and configures NVMe SSDs out of band: over a dedicated sideband, with no involvement from the host CPU or the PCIe data path.

NVMe-MI 2.0 adds an I3C binding for that sideband, and the industry is moving with it. The EDSFF form factors (E1.S, E1.L, and E3) adopted I3C for sideband management as the natural upgrade from SMBus: 12.5 MHz instead of 1 MHz, dynamic addressing, and in-band interrupts so a drive can raise an alert the instant something changes. Under the hood, NVMe-MI rides on MCTP over I3C.

// the stack

One health poll rides three layers.

A request starts life as an NVMe-MI command, becomes MCTP packets, and ends up as I3C private writes on the sideband. Every layer has to be right for the drive to answer.

// application layer

NVMe-MI commands

NVMe-MI

The management payload itself: poll Controller Health Status, read NVMe-MI Data Structures for inventory, get and set configuration, and tunnel NVMe Admin commands, all out of band, with no involvement from the host.

Controller Health StatusRead NVMe-MI DSConfig Get / SetAdmin passthrough

// message / transport layer

MCTP endpoints and messages

MCTP

NVMe-MI rides on MCTP. MCTP addresses each drive by Endpoint ID, splits messages into packets carrying start / end-of-message flags and sequence numbers, and protects every packet with a CRC-8 PEC. Baseline MTU is 69 bytes: a 4-byte header, 64 bytes of payload, and 1 PEC byte.

Endpoint ID (EID)SOM / EOMSequence numbersPEC (CRC-8)

// physical sideband

The I3C sideband

I3C

I3C is the sideband the drive answers on, at up to 12.5 MHz, with dynamic address assignment and in-band interrupts so a drive can raise an asynchronous event the moment something changes. EDSFF adopted I3C for sideband as the natural upgrade from SMBus.

DAAIBI eventsEDSFF sideband12.5 MHz

// our edge

NVMe-MI is only as solid as the I3C beneath it.

We don't watch from the sidelines. Plugfest after plugfest, our team is in the room where vendor I3C implementations come together: finding edge cases, debugging quirks, and validating real silicon against the spec.

Binho at the MIPI I3C Plugfest in Taipei, 2024
MIPI I3C Plugfest · Taipei, 2024
Martin from Binho at the MIPI I3C Plugfest in Warsaw, 2025
Martin · MIPI I3C Plugfest · Warsaw, 2025

// track record

We've been doing this for years.

Long enough to know where the gotchas live.

MIPI Alliance

// 01 · standards

We help write the spec.

Binho is a MIPI Alliance Contributor Member, actively shaping I3C, the sideband NVMe-MI over I3C is built on.

200+

// 02 · tools

We build the tools.

200+ semiconductor companies use Binho tools to develop, validate, and ship devices with I3C protocol support.

4

// 03 · plugfests

We prove it in the field.

We've verified our tools at the past 4 MIPI I3C Plugfests, and helped others verify theirs too.

// trusted by engineering teams at

+ hundreds more

Ready to bring up NVMe-MI over I3C?

From first drive bring-up to production regression, our I3C team knows where this stack breaks.