Understanding the I2C protocol and how it maps to Arduino pins is essential for anyone looking to connect multiple peripheral devices efficiently. Unlike serial communication that点对点连接工作，I2C uses a clever addressing system to allow a single master device to talk to many slaves over just two wires. This guide breaks down the hardware implementation, pin configuration, and best practices for integrating sensors, displays, and other modules into your projects.
Hardware Overview of I2C on Arduino
The I2C bus, also known as TWI (Two-Wire Interface) on Atmel-based boards, relies on two specific lines: SDA (Serial Data) and SCL (Serial Clock). These lines are open-drain, meaning they require pull-up resistors to function correctly. If you are using a modern Arduino Uno, Nano, or Mega, these pull-ups are often built-in, but external resistors may be necessary for longer wires or lower-voltage systems to ensure signal integrity.
Default Pin Mappings for Common Boards
Not all Arduino boards assign I2C pins to the same physical location, so verifying the layout for your specific hardware is crucial before wiring.
Locating the SDA and SCL Lines
On Uno and Nano models, the pins are labeled A4 and A5, but they are also broken out onto the digital header row as D18 and D19 respectively. For the Arduino Mega, you will find dedicated pins specifically marked "SDA" and "SCL" near the USB port, which is the most reliable connection point. Leonardo and Micro boards offer dedicated pins on the ICSP header, making them ideal for shield stacking without pin conflicts.
Wiring Multiple Devices
The true strength of I2C is its ability to support multiple devices on the same bus. You can connect several sensors or displays in parallel, wiring the SDA to SDA and SCL to SCL across all modules. However, every device must have a unique address to avoid data collision. If you encounter address conflicts, you can use address selectors provided by the module, or employ an I2C multiplexer to isolate communication channels.
Using the Wire Library
Arduino’s built-in Wire library abstracts the complex timing of the protocol, allowing you to send and receive data with simple function calls. To initiate communication, you include the library and begin transmission within the setup function. The master device initiates every transaction, generating the clock signal, while slave devices respond only when their specific address is called. This structure makes it easy to write clean, readable code for reading data from a gyroscope or sending commands to an OLED screen.
