I2C/SPI Bus Speed & Pull-up Resistor Sizing

Sizing pull-up resistors for an I2C bus looks easy—until your circuit misbehaves. Too much resistance, and the bus drags its feet coming up to a logic high. Go too low, and the chips can’t reliably pull the line down, sometimes stalling entirely. This calculator gives you practical pull-up values based on your supply voltage, total bus capacitance, I2C speed, and device count. It's handy when you’re building anything with multiple nodes sharing a single bus—works for embedded boards, factory equipment, or robots that need clean, reliable signaling. Core formulas, a working example, and plain explanations are included here.

What is I2C pull-up resistor sizing?

This is the business of choosing resistor values for the SDA and SCL lines so that both logic high and logic low are reliable at your target speed. How you pick the value depends on your voltage, how long and loaded your bus is, and how fast you want I2C to run.

Simple Explanation

You can picture the bus lines like springs—the devices pull them low, but only the pull-up resistors can bring them back up to logic high. If the resistor’s too large, it acts like a weak spring: signals take their time rising, and you struggle at faster speeds. Too small a resistor is like a strong spring—the devices may not be able to pull the signal all the way down. The trick is to find a middle ground that gets you sharp edges but doesn’t load the drivers more than they can handle.

📐 Browse all 384 free engineering calculators

How to Use This Calculator

1. Enter your supply voltage in volts (e.g., 3.3V or 5V).
2. Enter the total bus capacitance in picofarads — include trace, device, and connector capacitance.
3. Select your I2C speed mode and enter the number of devices on the bus.
4. Click Calculate to see your result.

I2C Bus Circuit Diagram

I2C Pull-up Resistor Calculator

📹 Video Walkthrough — How to Use This Calculator

Mathematical Formulas

Simple Example

Inputs: 3.3V supply, 100 pF bus capacitance, Fast Mode (400 kHz), 2 devices.

R_min = (3.3V − 0.4V) / (2 × 3 mA) = 2.9V / 6 mA = 483 Ω

R_max = 300 ns / (2.2 × 100 pF) = 1,364 Ω

Recommended: √(483 × 1364) = 811 Ω — reach for the nearest standard value of 820 Ω.

Understanding I2C Pull-up Resistor Design

I2C gets bi-directional communication over two wires by using open-drain (or open-collector) outputs and external pull-up resistors. If you don't get these resistors right, you get slow edges, possible stuck signals, or communications that seem to work until you bump up the speed. This calculator helps you strike the right balance between current draw and timing on the bus.

Fundamental I2C Bus Operation

Any I2C device on the bus can pull a line low, so you end up with a shared wired-AND arrangement. The pull-up resistors are the only things that return the lines to high. They're what hold the bus at logic '1' until a device actively drags it down. Get the value wrong and you'll run into crosstalk, noise susceptibility, or slow timing.

Those resistors set up both the steady-state voltage and how quickly the line can transition up to logic high. If you overdo it and use too large a resistor, you can't reach the speed specs; too small, and the devices heat up or can't reliably pull low.

Current Sinking Requirements

The spec for I2C says each device needs to be able to sink 3 mA (for standard devices), which is only meaningful when you size the pull-ups appropriately. As you keep adding devices to the bus, the total sinking current goes up. You'll need to check the combined effect so the logic low stays safely under threshold, even at maximum current load. Push the resistor value too low and some devices—especially at lower voltages or with weak drivers—just won't work reliably.

Rise Time and Signal Integrity

Signal rise time is set by the RC time constant of pull-up resistance and total bus capacitance. Faster rise times mean you can crank up the clock speed, but that always comes at the cost of using lower-value resistors (and so higher current draw).

Add up all sources of capacitance: every centimeter of PCB trace (~1-2 pF/cm), every device pin (typically 3-10 pF, check the datasheet), and any connector involved. The formulas and calculator assume you’ve captured that total accurately—if you underestimate, signals will rise even slower than you expect.

Speed Mode Considerations

Each I2C mode has a maximum rise time you can't exceed:

• Standard Mode (100 kHz): Spec allows rise time up to 1000 ns, so you can use higher pull-up values and save power.
• Fast Mode (400 kHz): Has a 300 ns rise time limit, so you'll need to fit a lower pull-up value.
• Fast Mode Plus (1 MHz): Allows just 120 ns—minimize capacitance and keep resistance low, or you won’t make timing.
• High Speed (3.4 MHz): Only 40 ns for the rise. Standard resistors won’t cut it here; active pull-up circuits are often required.

Practical Design Example

Suppose you have a system using FIRGELLI linear actuators with I2C position feedback, powered at 5V, bus capacitance at 150 pF, running Fast Mode (400 kHz), and 3 devices attached:

Minimum Resistance: R_min = (5V - 0.4V) / (3 × 3mA) = 4.6V / 9mA = 511Ω

Maximum Resistance: R_max = 300ns / (2.2 × 150pF) = 300ns / 330pF = 909Ω

Recommended Value: √(511Ω × 909Ω) = 682Ω (nearest standard value: 680Ω)

This balance lets you run I2C at Fast Mode speeds without burning unnecessary power or running the risk of signals getting sluggish.

Advanced Design Considerations

Watch out for temperature drift with resistors: most standard parts change by ±100–200 ppm/°C, which can be a 5–10% swing in value over a wide temperature range. If your bus margins are tight, look for better grade resistors or designs that account for this. The faster your bus or the tighter your specs, the more likely temperature swings become an issue.

Lower resistance means more current, which matters in anything that runs off batteries. You can reduce power by moving to a slower bus speed, letting you use a higher resistor (at the cost of communication speed).

If you mix voltage rails (say, 3.3V logic and 5V logic) directly on one I2C bus, you’ll hit level compatibility problems. You’ll need proper level-shifting circuitry or an I2C buffer chip. Don’t just hook devices of different logic families together, or you'll get intermittent faults that are hard to debug.

PCB Layout and Routing

Keep I2C trace runs as short as you can, avoid running them next to noisy signals, and try to route SDA and SCL together. Always return pull-ups to the same VCC the bus is running on, and try to keep the resistors close to the bus and supply, not scattered across the board. This helps avoid ground loops and small voltage drops that, over long runs, can add up.

Removable devices and long cables can bring reflection problems, especially at Fast Mode Plus and up. If you're seeing ringing or edge distortion, add series termination resistors (100–200Ω) to dampen those reflections.

Troubleshooting Common Issues

Poor resistor values show up in different ways. If resistance is too high, your waveforms rise slowly, making the bus noisy and unreliable at higher speeds. Too low, and either your parts can’t drive the signal low enough or you’re burning too much power for battery use.

The best troubleshooting tool is an oscilloscope. Watch your signals—make sure they're transitioning cleanly and hitting acceptable rise/fall times and voltage levels according to I2C logic thresholds.

Frequently Asked Questions

📐 Explore our full library of 384 free engineering calculators →