Open up almost any connected device on your desk, from a smart thermostat to a fitness band to a hobbyist ESP32 board, and you will find a quiet workhorse linking its chips together: the I2C bus. It is one of the most widely used communication protocols in embedded systems, and it has been doing the same elegant job since 1982. The remarkable part is how little it needs to do that job. Two wires. That is it.
A protocol built to save wires
In the early 1980s, engineers at Philips Semiconductors (now NXP) faced a practical headache. Television sets and other consumer electronics were packing more and more integrated circuits onto a single board, and every chip that needed to talk to a central controller demanded its own set of connections. Wiring grew tangled, boards grew larger, and costs climbed. The team's answer, introduced in 1982, was the Inter-Integrated Circuit bus, universally shortened to I2C.
The idea was to put every chip on the board onto a shared pair of lines: one for data (SDA) and one for the clock (SCL). Instead of point-to-point wiring for each component, a single microcontroller could now coordinate sensors, displays, memory, and other peripherals over the same two conductors. Fewer pins, smaller boards, lower cost. It was the kind of simplification that quietly changes an entire industry.
