config.txt display_default_lcd adafruit 2.8 tft lcd display in stock

This screen is located on this site. Since overlays already exist for this display in the /boot/overlays directory, it will be supported with a simple configuration.

If you are using the GPIO controllers, you can instead change the GPIO pin configuration by using pin 4 or 5 to set the pin used, avoiding the pins used by your display. See here for details.

This 2.8" screen works well but may be too small and too expensive (35€) as far as Chinese clones are concerned. So let"s configure a 3.2" TFT screen from Waveshare that can be found on Banggood for less than 15€.

The screen is the following: a 3.2" TFT LCD touchscreen display module for the Raspberry Pi B+, B, A+. Its resolution is the same as the 2.8": 320x240. It is in fact a Waveshare screen.

Get the files waveshare35a-overlay.dtb and waveshare32b-overlay.dtb for the WaveShare 3.2" 320x240 display and the WaveShare 3.5" 320x480 display respectively. For the new version 4.4 kernels, we need to rename the dtb files to dtbo files to match the new overlay tree name. Rename waveshare35a-overlay.dtb to waveshare35a.dtbo and waveshare32b-overlay.dtb to waveshare32b.dtbo and copy them to the /boot/overlays directory.

If you are using the GPIO controllers, you can instead change the GPIO pin configuration by using pin 4 or 5 to set the pin used, avoiding the pins used by your display. See here for details.

This display cannot be used for arcade games with Recalbox. The SPI bus does not have enough bandwidth to handle this higher resolution of 480x320. If you increase the bus speed, the display becomes unstable (colors, flickering). During my tests, I could only get 20-25 FPS. This display is usable with an X server with a slow frame rate but not in arcade mode which requires a higher frame rate.

As described on this site, it is not recommended to use this screen for gaming. With twice as many pixels to push on the screen, the PiTFT 3.5" is significantly slower than its more compact brothers and we strongly advise against it for games. Now you know!

If you are using the GPIO controllers, you can instead change the GPIO pin configuration by using pin 4 or 5 to set the pin used, avoiding the pins used by your display. See here for details.

In my humble opinion, if you have the 3.5" (C) LCD for Raspberry Pi (480x320; 125Mhz), it should work, but with the 3.5" (B) LCD for Raspberry Pi (480x320; IPS), you won"t be able to get 60fps!