logo Think-Embedded
Communication Protocols — Phase 1
Phase 1 • Communication Fundamentals 5 min read

Synchronous vs Asynchronous Communication

Communication between electronic components depends not only on voltage levels but also on timing. For data to be transferred correctly, the sender and receiver must stay synchronized so that each bit is transmitted and read at the right moment. This synchronization can be achieved either through a shared clock signal that controls the timing of communication or through predefined timing settings agreed upon by both devices. Based on how this synchronization is maintained, digital communication is classified into Synchronous Communication and Asynchronous Communication.

What is Synchronous Communication?

In synchronous communication, both devices share a dedicated, physical clock signal wire. This clock signal keeps the sender and receiver in perfect sync throughout the entire data transfer, removing any timing uncertainty.

The shared clock tells both devices:

  • Exactly when to place a bit on the data line (write data),
  • Exactly when to sample the voltage level of the line (read data),
  • When the data on the wire is stable and valid.

The concept becomes much easier to understand when visualized. The diagram below shows how a shared clock signal coordinates data transmission between a transmitter and receiver.

Fig 1 — Synchronous Communication Using a Shared Clock Signal
HOST (MCU) TRANSMITTER Generates Clock & Places Data Clock Data 1 0 1 1 0 0 1 0 ▲ SAMPLING INSTANTS Sample Point Valid Data Window DEVICE (Sensor) RECEIVER Samples Data on Clock Edge Shared Timing Reference LEGEND Clock Wire Data Wire Clock Edge Arrives Read Data Receiver Samples Next Bit Transmitted KEY IDEA Clock = WHEN to read Data = WHAT to read
In synchronous communication, both devices share the same clock signal. The transmitter places data on the data line, and the receiver samples it on each clock edge. This shared timing reference eliminates synchronization uncertainty.

How Synchronous Communication Works

The communication is usually orchestrated by a host device such as a microcontroller. The host generates a periodic clock signal and sends it to the receiving peripheral through a dedicated clock wire. Both devices use this clock as a common timing reference.

Before each clock edge, the transmitter places a bit on the data line. When the clock edge arrives, the receiver samples the voltage level of the data line and interprets it as a logic 0 or logic 1. Because both devices follow the same clock, timing errors are minimized and data can be transferred at very high speeds.

Real-World Example: Suppose a microcontroller needs to read temperature data from a sensor using SPI. The microcontroller generates the clock signal (SCLK) and sends it to the sensor. Every clock pulse tells both devices when to transmit and sample the next bit, ensuring the temperature value is transferred correctly.

What is Asynchronous Communication?

In asynchronous communication, devices do not share a common clock signal. There is no physical clock wire connecting them.

Instead, both devices must be independently configured to agree on two critical rules before communication starts:

  • Baud Rate: The speed of data transfer, measured in bits per second (e.g., 9600 bps or 115200 bps). This determines how long each bit will remain on the wire.
  • Frame Configuration: The exact format of data packets, including how many data bits are in a packet (typically 8) and which control bits are present.

Without a shared clock, timing is coordinated through strict agreement on transmission speed. The diagram below shows how the receiver detects the start of transmission and samples each incoming bit

Fig 2 — Asynchronous Communication (Baud Rate Synchronization)
HOST (MCU) TRANSMITTER Generates Data at Set Baud Rate No Clock Wire Data 1 0 1 1 0 0 1 Idle State START DATA BITS (1 0 1 1 0 0 1) STOP ▼ SAMPLING INSTANTS (CENTER OF BITS) DEVICE (Receiver) RECEIVER Samples Data using Local Clk Shared Baud Rate Configuration LEGEND Data Wire (TX) Start Bit Detected Starts Timer Receiver Local Clk Samples Bit At Bit Midpoint KEY IDEA Baud = WHEN to read Start = WHERE to start
No shared clock line is present. Instead, both MCUs generate matching internal clocks at 115200 Baud. The receiver detects the START bit, and starts sampling data at strict intervals (at the center of each bit period) to ensure reliable communication despite clock differences.

How Asynchronous Communication Works

Because there is no clock line to dictate timing, the receiving device listens to the idle data wire (which sits HIGH at logic 1).

When the transmitter wants to send data, it drives the line LOW (logic 0). This transition is called the Start Bit. Detecting this falling edge alerts the receiver that data is arriving.

The receiver immediately boots up its internal baud rate timer. Using the agreed baud rate configuration, it calculates the exact width of each bit and samples the wire at the middle of each bit period. A Stop Bit (logic 1) at the end indicates the frame is complete and returns the line to the idle state.

Real-World Example: Suppose a microcontroller needs to send sensor readings to a computer's serial monitor using UART. The microcontroller transmits the text characters one-by-one over the TX line at a preconfigured speed of 115200 Baud. The computer's USB-to-UART bridge detects each character's Start Bit, uses its own local timer to sample the bits at the right moments, and successfully displays the text without a shared clock wire.

Synchronous vs Asynchronous Communication

Both methods offer distinct engineering trade-offs between hardware complexity, wiring requirements, and data throughput. The optimal choice depends entirely on the system's speed requirements and available physical interconnects.

Feature Synchronous Communication Asynchronous Communication
Synchronization Method Shared clock signal Agreed baud rate
Clock Requirement Required Not required
Throughput Highest Moderate
Hardware Complexity Higher Lower
Wiring Requirements Additional signal paths Minimal
Typical Protocols SPI, I²C UART

Why This Matters

Firmware engineers encounter these timing concepts whenever configuring hardware peripherals or debugging data lines. Knowing whether a bus requires a physical clock signal or relies on exact baud-rate timing dictates how to set up logic analyzers, select appropriate protocols for new sensors, and diagnose issues like clock edge misalignment or baud-rate drift.

Quick Summary

Synchronous Communication relies on a shared clock to coordinate high-speed data transfers between devices, forming the basis of protocols like SPI and I²C. In contrast, Asynchronous Communication uses independent timing agreements like baud rates to transmit data without a clock wire, typical of a UART interface. Choosing the right method is a fundamental design decision balancing wiring simplicity against data throughput.