LIBRARYThe on-chip comms peripherals.

The serial buses a board uses to talk to sensors and other chips, UART, SPI, and I2C, live inside the microcontroller as hardware peripherals. You configure a block, hand it your data, and it clocks the bits out with exact timing. The chip does the hard, fast part so your code does not have to.

Hardware peripheral versus bit-banging

You could toggle a plain GPIO up and down in software to imitate a bus, which is called bit-banging. It works, but it ties up the CPU for every bit and the timing is only ever as steady as your code. A hardware peripheral is a dedicated block that generates the clock and shifts the bits itself, so it frees the CPU and gets the timing exactly right, and far faster than software could.

The three common buses

UART is a simple two-wire link (transmit and receive) with no shared clock, used for consoles and many modules. SPI is a fast bus with a shared clock, data in and out, and a chip-select line per device, used for displays and precision ADCs. I2C is a two-wire bus (a clock and a data line) that addresses many chips on the same pair, used for small sensors. The ESP32 has hardware blocks for all three.

Pin muxing: route a block to your pins

The ESP32 does not hard-wire each peripheral to fixed pins. A pin mux, short for multiplexer, lets you route a peripheral's signals out to almost any GPIO you choose, so you pick pins that suit your board layout and then assign the bus to them in firmware. Watch the usual caveats when you choose: keep a bus off the strapping pins and off the pins reserved for USB or the on-module flash.

Choosing which pins carry a bus ties straight into reading the pinout, which is the next lesson: some pins can take a peripheral cleanly, and some carry reset-time or USB duties you must not disturb.