ShopLearnFluxgrid
Support
Lonely Binary
ESP32TinkerBlockProductsFundamentalsTools
AccountCart
I2C
The bus3
01Why a bus02Who starts the talk03The clock
Addresses3
04Addresses05Scanning the bus06Two chips, one address
Talking to a chip2
07Registers: the drawers inside08Reading a temperature
The two wires4
09Why pull-up resistors10How big a pull-up11Too many pull-ups125 V and 3.3 V
All fundamentals →
Fundamentals/I2C/Addresses
Chapter · I2C

Addresses

Every module has a number. How the ESP32 uses it, how to find every number on a bus, and what happens when two modules share one.

3 articlesabout 12 minutesNo board required
  1. 04Addresses4 minEvery chip on an I2C bus has a seven-bit number, its address, and the controller puts it at the front of every message. The chip with that number answers and every other chip lets the message go by.
  2. 05Scanning the bus4 minA scan calls every address from 0x08 to 0x77 and listens on the ninth clock of each, where a chip that heard its own address pulls SDA low. It is the first thing to run when a module does not answer.
  3. 06Two chips, one address4 minTwo chips at one address both answer, at the same moment, on one wire. The scan shows one device, and every read returns a number built from both, with no error anywhere to say so.

Start at 04 and read down — the order is the order things get easier in. Or take the one with your part in it; every article stands on its own, and links back to whatever it needs.

← Previous chapterThe bus3 articlesNext chapter →Talking to a chip2 articles
Lonely Binary

From Zeros to Heroes, One Bit at a Time.

Sydney, Australia · office@lonelybinary.com

Shop
BoardsKitsSensors & InputDisplaysBest SellersWholesale
Learn
ESP32TinkerBlockProduct handbooksFundamentalsDownloadsProduct codes
Fluxgrid
Get startedCheat sheetDocsLibrary on GitHubPrivacy policy
Help
Contact usDeliveryReturnsWarranty
© 2026 Lonely BinaryTermsRefund policy