OLED display with I2C (SSD1306) in Raspberry Pi - Time & Space Complexity

Time Complexity: OLED display with I2C (SSD1306)

O(n)

Understanding Time Complexity

When working with an OLED display using I2C, it's important to understand how the time to update the screen changes as the amount of data grows.

We want to know how the program's running time changes when sending more pixels or commands to the display.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

import board
import busio
from adafruit_ssd1306 import SSD1306_I2C

# Initialize I2C and display
i2c = busio.I2C(board.SCL, board.SDA)
display = SSD1306_I2C(128, 64, i2c)

display.fill(0)  # Clear display
for y in range(64):
    for x in range(128):
        display.pixel(x, y, 1)  # Turn pixel on

display.show()  # Update display

This code turns on every pixel on a 128x64 OLED display using I2C communication.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Setting each pixel on the display inside nested loops.
• How many times: 128 (width) x 64 (height) = 8192 times.

How Execution Grows With Input

As the display size grows, the number of pixels to set grows with the total number of pixels.

Input Size (pixels)	Approx. Operations
10x10 = 100	100 pixel sets
100x100 = 10,000	10,000 pixel sets
1000x1000 = 1,000,000	1,000,000 pixel sets

Pattern observation: The operations grow proportionally with the number of pixels, so doubling width and height quadruples the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to update the display grows directly with the number of pixels you want to change.

Common Mistake

[X] Wrong: "Updating the display takes the same time no matter how many pixels I change."

[OK] Correct: Each pixel update requires time to update the internal buffer, so more pixels mean more time spent preparing data before sending over I2C.

Interview Connect

Understanding how hardware communication scales with data size helps you write efficient code and explain performance in real projects.

Self-Check

"What if we only update a small portion of the display instead of all pixels? How would the time complexity change?"

Practice

1. What is the main purpose of the show() method when using an SSD1306 OLED display with I2C on a Raspberry Pi?

easy

A. To update the display with the current buffer content

B. To clear the display screen

C. To initialize the I2C communication

D. To set the brightness of the OLED display

Solution

1. Step 1: Understand the display buffer concept

   The OLED display uses a buffer to store what will be shown on the screen before updating.

2. Step 2: Role of show() method

   The show() method sends the buffer content to the OLED, updating the visible display.

3. Final Answer:

   To update the display with the current buffer content -> Option A

4. Quick Check:

   show() updates screen [OK]

Hint: Remember: show() sends buffer to screen [OK]

Common Mistakes:

• Confusing show() with clear()
• Thinking show() initializes I2C
• Assuming show() changes brightness

2. Which of the following is the correct way to clear the OLED display buffer before drawing new content in Python using the SSD1306 library?

easy

A. oled.reset()

B. oled.clear()

C. oled.fill(0)

D. oled.erase()

Solution

1. Step 1: Identify the method to clear the buffer

   The SSD1306 library uses fill(0) to fill the buffer with zeros, effectively clearing it.

2. Step 2: Confirm other options are incorrect

   Methods like clear(), reset(), or erase() are not standard in this library.

3. Final Answer:

   oled.fill(0) -> Option C

4. Quick Check:

   Clear buffer = fill(0) [OK]

Hint: Use fill(0) to clear screen buffer [OK]

Common Mistakes:

• Using non-existent clear() method
• Confusing fill(1) with clearing
• Trying reset() which is not in library

3. Given the following Python code snippet for an SSD1306 OLED display, what will be the visible output on the screen?

oled.fill(0)
oled.text('Hi', 0, 0)
oled.show()

medium

A. The text 'Hi' appears at the bottom-right corner

B. The screen remains blank

C. An error occurs because text() needs more arguments

D. The text 'Hi' appears at the top-left corner

Solution

1. Step 1: Analyze the code sequence

   The buffer is cleared with fill(0), then 'Hi' is drawn at coordinates (0,0).

2. Step 2: Understand coordinate system and show()

   Coordinates (0,0) place text at top-left. Calling show() updates the display.

3. Final Answer:

   The text 'Hi' appears at the top-left corner -> Option D

4. Quick Check:

   Text at (0,0) shows top-left [OK]

Hint: Text at (0,0) is top-left on OLED [OK]

Common Mistakes:

• Assuming text() needs more arguments
• Thinking (0,0) is bottom-right
• Forgetting to call show() to update

4. You wrote this code to display 'Hello' on the OLED but nothing appears:

oled.text('Hello', 10, 10)
oled.fill(0)
oled.show()

What is the problem?

medium

A. Coordinates (10,10) are outside the display range

B. Calling fill(0) after text() clears the buffer

C. Missing oled.init() before drawing

D. Text string must be uppercase

Solution

1. Step 1: Check the order of commands

   Text is drawn first, then fill(0) clears the buffer, erasing the text.

2. Step 2: Understand correct sequence

   Clear buffer first with fill(0), then draw text, then call show().

3. Final Answer:

   Calling fill(0) after text() clears the buffer -> Option B

4. Quick Check:

   Clear after draw erases text [OK]

Hint: Clear buffer before drawing, not after [OK]

Common Mistakes:

• Thinking coordinates are invalid
• Assuming init() is needed every time
• Believing text case matters

5. You want to display a scrolling message on the SSD1306 OLED using I2C on Raspberry Pi. Which approach correctly updates the display to show new text smoothly without leftover pixels?

hard

A. Clear buffer with fill(0), draw new text, then call show() each frame

B. Draw new text over old text without clearing, then call show()

C. Only call show() once after all text frames are drawn

D. Use oled.clear() after show() to erase old text

Solution

1. Step 1: Understand how to avoid leftover pixels

   Clearing the buffer before drawing new text removes old pixels that would remain otherwise.

2. Step 2: Proper update sequence for smooth scrolling

   Each frame: clear buffer with fill(0), draw new text, then call show() to update display.

3. Final Answer:

   Clear buffer with fill(0), draw new text, then call show() each frame -> Option A

4. Quick Check:

   Clear before draw + show() = smooth update [OK]

Hint: Always clear buffer before drawing new frame [OK]

Common Mistakes:

• Not clearing buffer causes ghosting
• Calling show() only once delays updates
• Using non-existent clear() method