How to Wire a Level Shifter for I2C: 3.3V to 5V Bus Translation

When mixing 5V microcontrollers (like the classic Arduino Uno or Mega) with modern 3.3V I2C sensors (like the BME280 or MPU6050), you cannot simply wire them together. Feeding 5V logic into a 3.3V sensor's SDA/SCL pins will forward-bias its internal ESD protection diodes, eventually frying the silicon. The direct answer is to use a bi-directional level shifter for I2C—specifically, a dual N-channel MOSFET module like the BSS138, which safely translates the open-drain bus voltages between the two domains for about $1.50.

The Physical Layer: I2C Bus Mechanics and Voltage Translation

Unlike SPI or UART, which use push-pull outputs that actively drive pins high and low, I2C uses an open-drain architecture. Devices on the bus can only pull the SDA and SCL lines low (to ground); they cannot drive them high. To achieve a logic high, external pull-up resistors tie the lines to the positive supply voltage. If that supply is 5V, every 3.3V device on the bus sees 5V on its input pins during the idle state.

A MOSFET-based level shifter solves this by isolating the 5V pull-up domain from the 3.3V pull-up domain, using the MOSFET's gate threshold to pass the low-side signal across the boundary without passing the high-side voltage.

I2C Bus Mechanics and Limits (NXP UM10204 Specification)

Parameter	Standard Mode	Fast Mode	Fast Mode Plus
Bus Wires	2 (SDA, SCL) + GND	2 (SDA, SCL) + GND	2 (SDA, SCL) + GND
Max Speed	100 kHz	400 kHz	1 MHz
Max Bus Capacitance	400 pF	400 pF	550 pF
Practical Distance	~1 meter	~30 cm	~10 cm
Addressing	7-bit (128 addrs)	7-bit / 10-bit	7-bit / 10-bit

Because I2C is heavily constrained by bus capacitance and speed, choosing the right level shifter IC is critical. Not all logic translators handle open-drain I2C correctly.

Logic Level Shifter IC Comparison for I2C

IC / Module	Architecture	Directionality	Max I2C Speed	I2C Suitability	Typical Cost
BSS138 (Dual MOSFET)	Passive N-channel	Bi-directional	400 kHz (1MHz w/ low C)	Excellent (Standard choice)	$1.50
PCA9306 (NXP)	Active pass-transistor	Bi-directional	400 kHz	Excellent (Dedicated I2C)	$2.50
TXS0108E (TI)	Edge-accelerated	Bi-directional	N/A (Fails on I2C)	Poor (Internal one-shots fight pull-ups)	$3.00
CD4050B (CMOS)	Buffer	Unidirectional	100 kHz	Fails (Cannot translate SDA both ways)	$0.50

Wiring the BSS138 Bi-Directional Logic Level Converter

The most common bench module uses the BSS138 dual N-channel MOSFET. It features four channels, but I2C only requires two (SDA and SCL). The module has a low-voltage (LV) side and a high-voltage (HV) side.

Physical Wiring Steps:

1. Power the LV Side: Connect your 3.3V source (e.g., the 3.3V pin on an Arduino or a dedicated LDO) to the LV pin. Connect GND to GND.
2. Power the HV Side: Connect your 5V source to the HV pin. Connect GND to GND. (Both sides must share a common ground).
3. Route the Signals: Connect the 3.3V sensor's SDA to LV1 and SCL to LV2. Connect the 5V microcontroller's SDA to HV1 and SCL to HV2.

The Pull-Up Resistor Problem

Most off-the-shelf BSS138 breakout boards come pre-soldered with 10kΩ pull-up resistors on both the LV and HV sides. While 10kΩ works fine for 100 kHz Standard Mode with short wires, it is often too weak for 400 kHz Fast Mode. The TI SLVA689 application note defines the maximum pull-up resistance based on bus capacitance ($C_b$) and required rise time ($t_r$):

R_p(max) = t_r / (0.8473 × C_b)

For Fast Mode (400 kHz), the maximum allowed rise time is 300 ns. If your bus capacitance (wires + sensor pins) is 200 pF, the maximum pull-up resistor is 1.77 kΩ. A 10kΩ resistor will result in a sluggish, rounded rising edge that the microcontroller will misinterpret as a logic low, causing silent data corruption.

Code, Sniffing, and Classic I2C Failure Modes

Even with perfect voltage translation, I2C is notoriously fragile. Before writing complex driver code, you must verify the physical bus.

How to Sniff and Debug the Bus

The first step in any I2C debug session is running an address scan. On an Arduino, use the standard Wire.scan() I2C scanner sketch. On a Raspberry Pi, use i2cdetect -y 1 in the terminal. If the device shows up as UU or returns blank, move to hardware sniffing.

Connect a logic analyzer (like a Saleae Logic 8 or a cheap $10 24MHz clone running PulseView/Sigrok). Decode the I2C protocol in software. If you see a start condition but no ACK (Acknowledgement) bit, the sensor is either unpowered, at the wrong address, or the SDA line is failing to pull low. For analog verification, use an oscilloscope to measure the rise time of the SCL line; if the rising edge looks like a slow shark fin rather than a sharp square wave, your bus capacitance is too high for your pull-up resistors.

The Classic I2C Failure Modes

• Address Clash: I2C sensors often have hardcoded addresses. If you wire two BME280 sensors to the same bus, they both default to 0x76 or 0x77. You must physically cut a trace or bridge a solder jumper on the module's PCB to change the secondary address.
• Missing or Weak Pull-Ups: If you forget to enable internal pull-ups in software (on platforms that allow it) or omit external resistors, the bus floats. The lines will read erratic noise, and the master will receive garbage data or hang indefinitely.
• Clock Stretching Mismatches: Some 3.3V sensors hold the SCL line low to stall the master while they process data (clock stretching). If your 5V master (or a specific software library) does not support clock stretching, it will read the sensor prematurely and throw a checksum error.

Minimal Working Exchange: Arduino Uno to 3.3V BME280

Below is a complete, minimal example of an Arduino Uno (5V) reading the Chip ID register of a BME280 (3.3V) through a BSS138 level shifter. The BME280 Chip ID register is at 0xD0 and should return 0x60.

Pin Mapping: Arduino Uno → BSS138 → BME280

Arduino Uno (5V)	BSS138 Module	BME280 Sensor (3.3V)
5V Pin	HV (High Voltage)	-
3.3V Pin	LV (Low Voltage)	VIN / VCC
GND	GND (Both sides)	GND
A4 (SDA)	HV1	-
A5 (SCL)	HV2	-
-	LV1	SDI / SDA
-	LV2	SCK / SCL

#include <Wire.h>

// BME280 default I2C address
#define BME280_ADDR 0x76 
// Chip ID register address
#define REG_CHIP_ID 0xD0 

void setup() {
  Serial.begin(115200);
  
  // Initialize I2C at 100kHz (Standard Mode)
  // Increase to 400000 for Fast Mode if pull-ups are upgraded to 2.2k
  Wire.begin(); 
  Wire.setClock(100000); 

  Serial.println("Scanning I2C bus via BSS138 level shifter...");
}

void loop() {
  byte chipID = 0;
  
  // Begin transmission to the sensor
  Wire.beginTransmission(BME280_ADDR);
  Wire.write(REG_CHIP_ID); // Point to the Chip ID register
  
  // End transmission and check for ACK
  byte error = Wire.endTransmission(false); // false = repeated start
  
  if (error == 0) {
    // Request 1 byte of data from the sensor
    Wire.requestFrom(BME280_ADDR, (byte)1);
    if (Wire.available()) {
      chipID = Wire.read();
    }
    
    if (chipID == 0x60) {
      Serial.println("Success: BME280 detected. Chip ID: 0x60");
    } else {
      Serial.print("Warning: Device found, but unexpected Chip ID: 0x");
      Serial.println(chipID, HEX);
    }
  } else {
    Serial.print("I2C Error: No ACK received. Error code: ");
    Serial.println(error);
    Serial.println("Check BSS138 wiring, pull-up resistors, and sensor power.");
  }
  
  delay(2000);
}

By respecting the open-drain physics, sizing your pull-up resistors against bus capacitance, and verifying the physical layer with a logic analyzer before trusting your code, you eliminate 95% of the headaches associated with mixed-voltage I2C designs.