Touch Screen for Raspberry Pi 5: DSI vs HDMI Setup and Kiosk Code

The best touch screen for Raspberry Pi 5 depends entirely on your bandwidth and latency requirements. For native, low-latency integration, use the Official Raspberry Pi 7" Touch Display (MIPI DSI). For plug-and-play simplicity without worrying about fragile FPC ribbon cables, use an HDMI+USB capacitive panel like the Waveshare 7" 1024x600. The Pi 5's upgraded VideoCore VII GPU and dual MIPI combo-ports change the wiring rules compared to the Pi 4, making proper interface selection critical for stable kiosk deployments.

Choosing the Right Touch Screen for Raspberry Pi 5

Before buying a display, you need to understand the Pi 5's physical interfaces. Unlike the Pi 4, which had dedicated DSI and CSI ports, the Pi 5 uses two identical 22-pin MIPI combo-connectors that support either displays (DSI) or cameras (CSI) via software configuration. Furthermore, Raspberry Pi OS 'Bookworm' defaults to the Wayland display server, which handles touch events differently than the legacy X11 server.

Hardware Setup and Pin Mapping

For this build, we are pairing the Official Raspberry Pi 7" Touch Display with a Bosch BME280 I2C environmental sensor to create a wall-mounted climate kiosk. The official display handles its own touch data via the DSI ribbon's embedded I2C lines, so we only need to map the external sensor to the Pi 5's GPIO header.

Parts List

• Compute: Raspberry Pi 5 (8GB variant recommended for Wayland compositing overhead)
• Display: Official Raspberry Pi 7" Touch Display (V2.1 or newer)
• Power: 27W USB-C PD Power Supply (Pi 5 requires PD 5V/5A for full peripheral current)
• Sensor: BME280 Breakout Board (3.3V logic, I2C address 0x76 or 0x77)
• Wiring: 4x Silicone stranded jumper wires (24 AWG)

Pi 5 GPIO to BME280 Pin Mapping

Wiring Steps:

1. De-energize: Unplug the 27W USB-C power supply. Never hot-swap I2C lines on the Pi 5; the PMIC is sensitive to voltage spikes on the GPIO rail.
2. Connect DSI: Plug the 15-pin display ribbon cable into the Pi 5's MIPI port closest to the USB-C port. Ensure the gold contacts face inward toward the center of the Pi board.
3. Wire I2C: Connect the BME280 SDA to Pi Pin 3, SCL to Pi Pin 5, VCC to Pin 1, and GND to Pin 6.
4. Verify Pull-ups: The Pi 5 has onboard 1.8kΩ pull-up resistors on GPIO 2 and 3. If your BME280 breakout also has pull-ups, the parallel resistance might drop too low. If you experience I2C bus lockups, desolder the pull-ups on the sensor breakout.

Building the Touch Kiosk: Python Code

This code targets the Raspberry Pi 5 (8GB) running Raspberry Pi OS Bookworm (64-bit, Wayland). We use Python's built-in tkinter for the GUI, which natively maps Wayland touch events to mouse clicks, and smbus2 for direct I2C register reads. This avoids the heavy overhead of full browser-based kiosk modes.

Prerequisite: Install the I2C library via terminal: sudo apt install python3-smbus2 i2c-tools

import tkinter as tk
from smbus2 import SMBus
import time
import sys

# --- PIN & ADDRESS DEFINITIONS ---
I2C_BUS_ID = 1
BME280_ADDR = 0x76  # Use 0x77 if your breakout has the alternate address strapped

# BME280 Registers for compensated reading (simplified for demo)
REG_TEMP_MSB = 0xFA
REG_CTRL_MEAS = 0xF4

# --- I2C SENSOR CLASS WITH ERROR HANDLING ---
class ClimateSensor:
    def __init__(self, bus_id, addr):
        self.bus_id = bus_id
        self.addr = addr
        self.bus = None
        self.connect()

    def connect(self):
        try:
            self.bus = SMBus(self.bus_id)
            # Set oversampling: temp x1, press x1, hum x1, forced mode
            self.bus.write_byte_data(self.addr, REG_CTRL_MEAS, 0x25)
        except OSError as e:
            print(f'Hardware Error: {e}')
            self.bus = None

    def read_temp_c(self):
        if not self.bus:
            return None
        try:
            # Trigger forced measurement
            self.bus.write_byte_data(self.addr, REG_CTRL_MEAS, 0x25)
            time.sleep(0.05) # Wait for measurement
            data = self.bus.read_i2c_block_data(self.addr, REG_TEMP_MSB, 3)
            # Raw ADC conversion (simplified, skipping full Bosch compensation algo for brevity)
            raw_temp = (data[0] << 12) | (data[1] << 4) | (data[2] >> 4)
            # Approximate conversion for demonstration
            return round((raw_temp / 1000.0) * 2.5 - 40.0, 1)
        except OSError as e:
            print(f'Read Error: {e}')
            return None

# --- GUI SETUP ---
class TouchKiosk(tk.Tk):
    def __init__(self, sensor):
        super().__init__()
        self.sensor = sensor
        self.title('Pi 5 Climate Kiosk')
        self.attributes('-fullscreen', True)
        self.configure(bg='#1e1e24')
        
        # Bind touch/click to exit
        self.bind('', self.on_touch)

        self.temp_label = tk.Label(self, text='-- °C', font=('Helvetica', 96, 'bold'), 
                                   fg='#00ffcc', bg='#1e1e24')
        self.temp_label.pack(expand=True)

        self.status_label = tk.Label(self, text='Touch anywhere to exit', 
                                     font=('Helvetica', 16), fg='#888888', bg='#1e1e24')
        self.status_label.pack(side='bottom', pady=40)

        self.update_reading()

    def update_reading(self):
        temp = self.sensor.read_temp_c()
        if temp is not None:
            self.temp_label.config(text=f'{temp} °C', fg='#00ffcc')
        else:
            self.temp_label.config(text='SENSOR ERR', fg='#ff3333')
        
        # Schedule next read in 2000ms
        self.after(2000, self.update_reading)

    def on_touch(self, event):
        # Debounce / simple exit logic for touch screens
        self.status_label.config(text='Exiting Kiosk...')
        self.after(500, self.destroy)

if __name__ == '__main__':
    sensor = ClimateSensor(I2C_BUS_ID, BME280_ADDR)
    app = TouchKiosk(sensor)
    try:
        app.mainloop()
    except KeyboardInterrupt:
        sys.exit(0)

Debugging: Touch and Display Failures

The transition to Wayland in Raspberry Pi OS Bookworm broke hundreds of legacy X11 touch tutorials. If your screen is blank or touch is unresponsive, do not immediately blame the hardware. Follow this decision path.

First Three Things to Check When It Fails

1. Verify I2C Bus Activity: Run i2cdetect -y 1 in the terminal. If you don't see 76 or 77 in the grid, your sensor is unpowered, wired to the wrong pins, or lacks pull-up resistors.
2. Confirm Wayland Session Type: Run echo $XDG_SESSION_TYPE. If it returns tty or x11, your environment variables are misconfigured for the default Bookworm Wayland compositor, which will break touch event routing in tkinter.
3. Inspect FPC Ribbon Seating: Unplug the Pi and check the MIPI DSI ribbon. The gold pins must face the center of the Pi 5 PCB. If they face outward, the display will remain completely black, and the backlight may flash.

Exact Error Strings and Ranked Causes

Extending or Simplifying the Build

Depending on your deployment environment, you may need to scale this project up or strip it down.

How to Simplify (The Browser Kiosk Route)

If you don't need custom Python logic and just want to display a web-based dashboard (like Grafana or Home Assistant), ditch the Python code entirely. Install Chromium, create a desktop shortcut in ~/.config/wayfire.ini (for Wayland) or ~/.config/lxsession/LXDE-pi/autostart (for X11), and append --kiosk --incognito http://your-local-ip:8123. This offloads all touch-event translation to the Chromium engine, which is heavily optimized for Wayland touch scrolling.

How to Extend (Adding MQTT Telemetry)

To push the BME280 data to a home automation broker while maintaining the touch UI, integrate the paho-mqtt library. Add a background thread to the Python script so the MQTT publish loop doesn't block the tkinter mainloop.

import paho.mqtt.client as mqtt
import threading

# Add inside TouchKiosk __init__:
self.mqtt_client = mqtt.Client()
self.mqtt_client.connect('192.168.1.50', 1883, 60)
self.mqtt_client.loop_start()

# Modify update_reading:
if temp is not None:
    self.mqtt_client.publish('home/climate/pi5_temp', temp)

For deeper technical specifications on the Pi 5's MIPI lanes and I2C timing constraints, refer to the Raspberry Pi Display Documentation and the Bookworm OS Release Notes. If you opt for third-party HDMI touch panels, the Waveshare Wiki provides essential config.txt overscan overrides that the official displays handle automatically via EDID.