OLED display with I2C (SSD1306) in Arduino - Step-by-Step Execution

Concept Flow - OLED display with I2C (SSD1306)

Start Setup

↓

Initialize I2C

↓

Initialize OLED Display

↓

Clear Display

↓

Write Text or Graphics

↓

Display Update

↓

Loop or End

The program sets up I2C, initializes the OLED, clears it, writes content, and updates the display repeatedly.

Execution Sample

Arduino

#include <Wire.h>
#include <Adafruit_SSD1306.h>

Adafruit_SSD1306 display(128, 64, &Wire);

void setup() {
  Wire.begin();
  display.begin(SSD1306_SWITCHCAPVCC, 0x3C);
  display.clearDisplay();
  display.setTextSize(1);
  display.setTextColor(SSD1306_WHITE);
  display.setCursor(0,0);
  display.println("Hello, OLED!");
  display.display();
}

void loop() {}

This code initializes the OLED display over I2C and shows the text 'Hello, OLED!' once.

Execution Table

Step	Action	I2C Init	OLED Init	Display Buffer	Display Output
1	Start setup()	Not started	Not started	Empty	Blank screen
2	Initialize I2C & OLED	I2C started	OLED initialized	Empty	Blank screen
3	Clear display buffer	I2C active	OLED ready	Empty	Blank screen
4	Set text size to 1	I2C active	OLED ready	Empty	Blank screen
5	Set text color to white	I2C active	OLED ready	Empty	Blank screen
6	Set cursor to (0,0)	I2C active	OLED ready	Cursor at (0,0)	Blank screen
7	Print 'Hello, OLED!'	I2C active	OLED ready	'Hello, OLED!' in buffer	Blank screen
8	Display buffer on screen	I2C active	OLED ready	'Hello, OLED!' in buffer	'Hello, OLED!' visible
9	Enter loop()	I2C active	OLED ready	'Hello, OLED!' in buffer	'Hello, OLED!' visible

💡 Loop runs indefinitely; display shows 'Hello, OLED!'

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 7	Final
I2C Status	Not started	Started	Active	Active	Active
OLED Status	Not started	Initialized	Ready	Ready	Ready
Display Buffer	Empty	Empty	Empty	'Hello, OLED!'	'Hello, OLED!'
Display Output	Blank	Blank	Blank	Blank	'Hello, OLED!'

Key Moments - 3 Insights

Why does the display stay blank until display.display() is called?

The display buffer holds the text but does not show it until display.display() sends the buffer to the screen, as shown in step 8 of the execution_table.

What happens if we don't call display.clearDisplay() before writing?

Old content remains in the buffer, so new text overlaps or mixes with old, causing messy output. Step 3 clears the buffer to avoid this.

Why do we set cursor position before printing text?

The cursor tells where text starts on the screen. Without setting it (step 6), text might print in unexpected places.

Visual Quiz - 3 Questions

Look at the execution_table at step 7, what is in the display buffer?

A 'Hello, OLED!'

B Empty

C Cursor position only

D Display output

💡 Hint

Check the 'Display Buffer' column at step 7 in the execution_table.

At which step does the text actually appear on the OLED screen?

A Step 3

B Step 7

C Step 8

D Step 6

💡 Hint

Look at the 'Display Output' column in the execution_table to see when text becomes visible.

If we skip display.clearDisplay(), what will happen to the display buffer?

A It will be empty

B Old content remains and mixes with new

C Cursor resets to (0,0)

D Display output updates immediately

💡 Hint

Refer to key_moments explanation about clearing the display buffer before writing.

Concept Snapshot

Include Wire and Adafruit_SSD1306 libraries
Initialize display with display.begin(SSD1306_SWITCHCAPVCC, 0x3C)
Clear buffer with display.clearDisplay()
Set text size, color, and cursor
Print text to buffer with display.println()
Show buffer on screen with display.display()

Full Transcript

This example shows how to use an OLED display with I2C using the SSD1306 driver on Arduino. First, the program starts by initializing the I2C communication and the OLED display. Then it clears the display buffer to remove any old content. Next, it sets the text size and color, and positions the cursor at the top-left corner. The text 'Hello, OLED!' is printed into the display buffer but not shown yet. Finally, calling display.display() sends the buffer to the screen, making the text visible. The loop function runs empty, so the display stays showing the text. Key points include clearing the display before writing new content and understanding that printing text only changes the buffer until display.display() is called.

Practice

1. What is the main advantage of using an OLED display with I2C (SSD1306) in Arduino projects?

easy

A. It uses only two wires for communication, simplifying connections.

B. It requires no power supply to operate.

C. It can display full-color images without extra hardware.

D. It automatically connects to Wi-Fi networks.

Solution

1. Step 1: Understand I2C communication basics

   I2C uses two wires (SDA and SCL) to communicate between devices, reducing wiring complexity.

2. Step 2: Relate to OLED display advantages

   OLED displays with I2C use these two wires, making connections simpler compared to parallel interfaces.

3. Final Answer:

   It uses only two wires for communication, simplifying connections. -> Option A

4. Quick Check:

   I2C = 2 wires [OK]

Hint: Remember I2C means just two wires for data and clock [OK]

Common Mistakes:

• Thinking OLED needs many wires like parallel displays
• Assuming OLED works without power
• Confusing I2C with Wi-Fi or color capabilities

2. Which of the following is the correct way to initialize the SSD1306 OLED display using the Adafruit_SSD1306 library in Arduino?

easy

A. display.init(0x3C, SSD1306_SWITCHCAPVCC);

B. display.start(SSD1306_I2C, 0x3C);

C. display.setup(0x3C);

D. display.begin(SSD1306_SWITCHCAPVCC, 0x3C);

Solution

1. Step 1: Recall Adafruit_SSD1306 initialization syntax

   The correct method is display.begin() with parameters for power mode and I2C address.

2. Step 2: Match parameters to correct order

   SSD1306_SWITCHCAPVCC is the power mode, and 0x3C is the common I2C address for the display.

3. Final Answer:

   display.begin(SSD1306_SWITCHCAPVCC, 0x3C); -> Option D

4. Quick Check:

   Use display.begin() with power and address [OK]

Hint: Use display.begin() with power mode and I2C address [OK]

Common Mistakes:

• Using wrong method names like start or init
• Swapping parameter order
• Omitting power mode parameter

3. What will be the output on the OLED display after running this Arduino code snippet?

display.clearDisplay();
display.setTextSize(1);
display.setTextColor(SSD1306_WHITE);
display.setCursor(0,0);
display.println("Hello");
display.display();

medium

A. The text 'Hello' appears at the top-left corner of the display.

B. The display remains blank because display.display() is missing.

C. The text 'Hello' appears in the middle of the display.

D. The code causes a compile error due to missing initialization.

Solution

1. Step 1: Analyze display commands

   clearDisplay() clears screen, setCursor(0,0) sets top-left position, println("Hello") writes text.

2. Step 2: Understand display() function

   display() sends buffer to screen, so text appears after calling it.

3. Final Answer:

   The text 'Hello' appears at the top-left corner of the display. -> Option A

4. Quick Check:

   setCursor(0,0) + println("Hello") + display() = 'Hello' top-left [OK]

Hint: Remember to call display() to show changes on screen [OK]

Common Mistakes:

• Forgetting display.display() to update screen
• Assuming text appears without setCursor
• Thinking text appears centered by default

4. Identify the error in this Arduino code snippet for SSD1306 OLED display:

display.begin(SSD1306_SWITCHCAPVCC, 0x3C);
display.setTextSize(2);
display.setTextColor(SSD1306_WHITE);
display.println("Hi");
display.display();

medium

A. Incorrect I2C address used in display.begin().

B. Missing display.clearDisplay() before drawing text.

C. setTextSize() cannot be set to 2.

D. display.display() should be called before println().

Solution

1. Step 1: Check for display buffer clearing

   Without clearDisplay(), old content may remain, causing overlapping text.

2. Step 2: Verify other commands

   I2C address 0x3C is common and valid; setTextSize(2) is allowed; display() must be after drawing.

3. Final Answer:

   Missing display.clearDisplay() before drawing text. -> Option B

4. Quick Check:

   Always clearDisplay() before drawing new content [OK]

Hint: Always clear display before drawing new text [OK]

Common Mistakes:

• Skipping clearDisplay() causing messy screen
• Changing I2C address without checking hardware
• Calling display() too early

5. You want to display a scrolling message on the SSD1306 OLED using I2C. Which approach correctly combines clearing the display, setting cursor, and updating the screen inside a loop?

hard

A. Inside loop: display(); clearDisplay(); setCursor(0,0); println(message); delay(200);

B. Inside loop: setCursor(0,0); println(message); display(); clearDisplay(); delay(200);

C. Inside loop: clearDisplay(); setCursor(0,0); println(message); display(); delay(200);

D. Inside loop: println(message); setCursor(0,0); clearDisplay(); display(); delay(200);

Solution

1. Step 1: Understand display update cycle

   Each loop iteration must clear previous content, set cursor, write new text, then update display.

2. Step 2: Verify correct order of commands

   clearDisplay() first clears buffer, setCursor() positions text, println() writes, display() sends buffer to screen, delay() controls speed.

3. Final Answer:

   Inside loop: clearDisplay(); setCursor(0,0); println(message); display(); delay(200); -> Option C

4. Quick Check:

   Clear, set cursor, print, display, delay = scrolling [OK]

Hint: Clear before print, then display inside loop for scrolling [OK]

Common Mistakes:

• Calling clearDisplay() after display() causing blank screen
• Setting cursor after printing text
• Forgetting delay causing too fast updates