UART to I2C Bridge: Wiring, Code, and Debugging the SC16IS750

When you run out of hardware UART ports on an ESP32 or need to route a serial GPS module over a shared I2C bus to a Raspberry Pi, you need a UART to I2C bridge. This isn't a simple wire crossover; it requires a dedicated bridge IC like the NXP SC16IS750 to translate asynchronous serial data into synchronous, register-based I2C packets. Below is the bench-tested guide to wiring, coding, and debugging this translation layer.

The Physical Layer: Wiring UART to I2C Bridge ICs

Before writing a single line of code, you must respect the physical realities of both buses. I2C is a synchronous, multi-drop bus that requires external pull-up resistors. UART is an asynchronous, point-to-point bus that relies on agreed-upon timing (baud rate) and crossed TX/RX lines. The bridge IC sits in the middle, buffering UART bytes into an internal FIFO and exposing them as I2C registers.

Protocol Translation: Bridging the Asynchronous Gap

The NXP SC16IS750 handles the heavy lifting. It uses a 14.7456 MHz crystal to generate precise UART baud rates, completely independent of the I2C clock speed. Your microcontroller acts as the I2C master, writing to the bridge's Line Control Register (LCR) to set the baud rate, and reading from the Receive Holding Register (RHR) to fetch UART bytes.

Below is the exact wiring required to interface an ESP32 DevKit V1 with the SC16IS750 breakout, followed by a minimal, non-blocking exchange example.

// ESP32 DevKit V1 - UART to I2C Bridge via SC16IS750
// Requires: Adafruit SC16IS750 Library
#include <Wire.h>
#include <Adafruit_SC16IS750.h>

// Default I2C address for SC16IS750 (A0 and A1 pins grounded)
#define SC16IS750_ADDR 0x48 

Adafruit_SC16IS750 uart_bridge = Adafruit_SC16IS750();

void setup() {
  Serial.begin(115200);
  
  // Initialize I2C bus on ESP32 default pins (21=SDA, 22=SCL)
  Wire.begin();
  
  if (!uart_bridge.begin(SC16IS750_ADDR, &Wire)) {
    Serial.println("FATAL: SC16IS750 not found. Check I2C wiring and pull-ups.");
    while (1) { delay(10); }
  }
  
  // Configure the UART side of the bridge
  uart_bridge.begin(9600); // Set baud rate for the attached UART device
  Serial.println("Bridge initialized. Listening for UART data...");
}

void loop() {
  // Non-blocking read from the bridge's internal FIFO
  if (uart_bridge.available()) {
    char c = uart_bridge.read();
    Serial.print(c); // Forward to ESP32 hardware USB serial
  }
  
  // Pass-through: Send USB serial commands out through the bridge
  if (Serial.available()) {
    uart_bridge.write(Serial.read());
  }
}

Debugging the Bridge: Sniffing and Fixing Classic Failures

When a UART to I2C bridge fails, the symptom is usually silent hangs or garbage data. Because you are crossing two different physical layers, you must isolate the fault domain. Here are the three most common failures and how to fix them.

1. The Missing Pull-Up (I2C Bus Hang)
If your code hangs on Wire.endTransmission() or the bridge fails to initialize, your I2C bus is likely missing pull-up resistors. Measure SDA and SCL with a multimeter relative to GND while the bus is idle. Both should read a solid 3.3V. If they read 0V or float around 1.2V, the bus is stuck or floating. Solder 4.7 kΩ resistors between the SDA/SCL lines and the 3.3V rail.

2. Address Clash on the Bridge IC
The SC16IS750 has two address pins (A0 and A1). If you leave them floating, they often default to ground, yielding an I2C address of 0x48. If you put two bridge breakouts on the same bus without configuring these pins, they will clash. Use the i2cdetect -y 1 command on a Raspberry Pi, or an I2C scanner sketch on Arduino, to verify the address.

3. Baud Rate Mismatch and Garbage Characters
If your serial monitor outputs scrambled symbols (e.g., ÿÿÿ), the UART baud rate on the bridge does not match the peripheral device. The SC16IS750 derives its baud rate from its onboard crystal (typically 14.7456 MHz). If you are using a clone board with a 1.8432 MHz crystal, the internal baud rate divisor math in standard libraries will be wrong, resulting in a massive timing skew. Verify the crystal frequency printed on the metal can and adjust the library's clock speed definition if necessary.

How to Sniff the Bus:
To definitively debug a translation failure, use a logic analyzer (like a Saleae Logic Pro 8 or DSLogic Plus). Connect channels 0-1 to SDA/SCL and channels 2-3 to UART TX/RX. Set the analyzer to trigger on the I2C Start condition. Decode both protocols simultaneously in the software. This allows you to see exactly which I2C register write correlates to the malformed UART byte on the wire.