Serial Buses for Embedded and IoT Engineers
Serial buses are the wired interfaces that let a microcontroller talk to sensors, displays and other chips using few pins. UART sends asynchronous byte streams between two devices, I2C uses two shared lines with addressed devices, and SPI uses a clock plus separate data lines and chip selects for fast transfers.
Stage: Microcontrollers · Part of the Embedded and IoT Engineer roadmap · Last reviewed 19 November 2026
What to learn in Serial Buses
- Configure UART with a baud rate and frame format and print debug output
- Read a sensor over I2C by sending its address and register and reading bytes back
- Transfer data over SPI and choose the right clock polarity and phase mode
- Pick between UART, I2C and SPI for a device based on speed, wiring and bus sharing
- Decode a bus capture with a logic analyser to find a wiring or timing fault
Serial Buses interview questions
Why does I2C need pull-up resistors?
I2C lines are open-drain: devices only pull the line low and cannot drive it high. External pull-up resistors return the line to high when released. Their value affects rise time and so the maximum reliable speed.
When would you choose SPI over I2C?
Choose SPI when you need higher throughput, for example for displays, SD cards or fast ADCs. It runs at tens of MHz with full duplex but needs a chip-select line per device. I2C uses fewer wires and addresses many devices, but is slower.
Where Serial Buses fits in the Embedded and IoT Engineer roadmap
Serial Buses belongs to the Microcontrollers stage (intermediate level), which takes about 47 hours. Talk to hardware.
Other units in this stage
Back to the full Embedded and IoT Engineer roadmap