Why I2C is used with Raspberry Pi - Visual Breakdown

Concept Flow - Why I2C is used with Raspberry Pi

Start Raspberry Pi

↓

Enable I2C Interface

↓

Connect I2C Devices (Sensors, Displays)

↓

Send/Receive Data via I2C Bus

↓

Process Data in Pi

↓

Use Data in Applications

↓

End

This flow shows how Raspberry Pi uses I2C to communicate with multiple devices by enabling the interface, connecting devices, exchanging data, and using it in programs.

Execution Sample

Raspberry Pi

import smbus
bus = smbus.SMBus(1)
address = 0x48
value = bus.read_byte(address)
print(f"Value from device: {value}")

This code reads a byte of data from an I2C device at address 0x48 connected to Raspberry Pi and prints it.

Execution Table

Step	Action	I2C Bus State	Device Address	Data Read	Output
1	Initialize SMBus(1)	Bus ready	-	-	-
2	Set device address	Bus ready	0x48	-	-
3	Read byte from device	Bus active	0x48	72	-
4	Print value	Bus idle	0x48	72	Value from device: 72
5	End program	Bus idle	-	-	-

💡 Program ends after reading and printing data from I2C device

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
bus	None	SMBus(1) object	SMBus(1) object	SMBus(1) object
address	None	0x48	0x48	0x48
value	None	None	72	72

Key Moments - 3 Insights

Why do we need to specify the device address before reading data?

Because the I2C bus can have many devices, specifying the address tells the Pi which device to talk to, as shown in step 2 of the execution_table.

What does the number 72 represent in the data read step?

It is the byte of data read from the device at address 0x48, representing sensor or device output, as seen in step 3 of the execution_table.

Why is the bus state 'idle' after printing the value?

Because after communication finishes, the bus is free for other devices or operations, shown in step 4 and 5 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'value' variable after step 3?

A None

B 72

C 0x48

D smbus.SMBus(1)

💡 Hint

Check the 'Data Read' and 'value' variable in variable_tracker after step 3

At which step does the Raspberry Pi specify which device to communicate with?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Device Address' column in execution_table

If the device address was changed to 0x50, which part of the execution_table would change?

A Step 2 Device Address

B Step 1 Bus State

C Step 4 Output

D Step 5 Exit Note

💡 Hint

Device address is set in step 2 as shown in execution_table

Concept Snapshot

I2C allows Raspberry Pi to talk to many devices using just two wires.
Enable I2C, connect devices with unique addresses.
Use smbus library to read/write data.
Specify device address before communication.
Data flows over shared bus, making wiring simple and efficient.

Full Transcript

This visual trace shows why Raspberry Pi uses I2C: to communicate easily with multiple devices using only two wires. The flow starts by enabling I2C, connecting devices, sending and receiving data, and using that data in programs. The sample code reads a byte from a device at address 0x48. The execution table traces each step: initializing the bus, setting the device address, reading data, printing it, and ending. Variables like 'bus', 'address', and 'value' change as the program runs. Key moments clarify why the device address is needed, what the data read means, and why the bus becomes idle after communication. The quiz tests understanding of variable values, steps for device addressing, and effects of changing the device address. The snapshot summarizes I2C's role and usage on Raspberry Pi simply and clearly.