raspberry pi lcd touch screen case white free sample

Keep your RPi board and LCD safe with this freestanding and portable Raspberry Pi case from DesignSpark. Specially developed to take your Pi 7in. LCD touch screen plus your Pi board, you can use this handy little case for the Pi 2 Model B, Pi 3 Model B and Pi Model B+. The main enclosure consists of an RPi LCD touch screen and board casing complete with snap-together removable rear cover. Formed from tough, long-lasting ABS, cuts-outs let you access all the connections and USB ports with ease. With an eye to aesthetics, the enclosure also creates a stylish bezel around your Pi LCD display.

I finally received my 3.5" KeDei 480x320 16bit/18bit version 3.0 TFT LCD touchscreen from Hong Kong. It only connects through the GPIO pins. I plugged it into my Raspberry Pi 2 and I was met with a white screen when I tried both the Ubuntu and Raspbian images.

I have updated Raspbian, I know that my good power supply is good, and I tried enabling the SPI kernel module through the Raspberry Pi Configuration GUI since the touchscreen says that it connects via SPI. The only thing that I think could be wrong now is that the drivers are not installed or that I don"t have the right kernel.

If I can get the touchscreen to function on either the Ubuntu or the Raspbian image, then I will just take the one that works. Though if both could work flawlessly I think I would prefer using the Ubuntu image since I am more familiar with it.

2. The adapter board communicates to the RPi using the 15pin cable. From the RPi schematics, the connector for this cable has signals for DSI and I2C. Is it correct to say that on the adapter board has a controller that accepts MIPI-DSI data from the RPi and translates that data to drive the LCD over the 50 pin cable? Is the controller also responsible for sending touch data from the screen to the RPi over I2C as well?

2. The adapter board communicates to the RPi using the 15pin cable. From the RPi schematics, the connector for this cable has signals for DSI and I2C. Is it correct to say that on the adapter board has a controller that accepts MIPI-DSI data from the RPi and translates that data to drive the LCD over the 50 pin cable? Is the controller also responsible for sending touch data from the screen to the RPi over I2C as well?

It currently uses the panel-raspberrypi-touchscreen driver to control the backlight and power (over I2C) and configure the TC358762 DSI to DPI bridge chip (via DSI commands).

The pair don"t play perfectly though as the TC358762 driver goes and turns the power off on the touchscreen driver. Mainline Linux developers have just reworked things to have separate TC358762, and regulator/backlight driver. The touchscreen driver should then be able to hook into the regulator and keep the power on, but it"s not quite working at the moment.

It currently uses the panel-raspberrypi-touchscreen driver to control the backlight and power (over I2C) and configure the TC358762 DSI to DPI bridge chip (via DSI commands).

The pair don"t play perfectly though as the TC358762 driver goes and turns the power off on the touchscreen driver. Mainline Linux developers have just reworked things to have separate TC358762, and regulator/backlight driver. The touchscreen driver should then be able to hook into the regulator and keep the power on, but it"s not quite working at the moment.

There are several threads on here about getting other panels up and running with cm4. Ili9881, st7701, and a couple of other devices are being discussed. Personally I"ve had the tc358762 of the original pi panel and an Ili9881 panel working, and I"m working on others.

https://github.com/raspberrypi/linux/pull/3985 for an example overlay using the ILI9881. The Pi panel overlay is merged as arch/arm/boot/dts/overlays/vc4-kms-dsi-7inch-overlay.dts

It currently uses the panel-raspberrypi-touchscreen driver to control the backlight and power (over I2C) and configure the TC358762 DSI to DPI bridge chip (via DSI commands).

The pair don"t play perfectly though as the TC358762 driver goes and turns the power off on the touchscreen driver. Mainline Linux developers have just reworked things to have separate TC358762, and regulator/backlight driver. The touchscreen driver should then be able to hook into the regulator and keep the power on, but it"s not quite working at the moment.

I recently upgraded an old pi2 to a pi4 and noticed that I had to use kms now for the console (kivy application with the 7inch touchscreen). I got it running with fkms without any issues but wanted to try "real" kms as well.

in the config, the system boots up but then the display turns white and fades out and no longer displays anything. It does not make a difference if I then load the touchscreen driver.

I connected 7" Touch to Raspi4 and started it with a fresh SD with a 1,9 MB Raspian Image without modifications. The display was recognized as primary display and the desktop was there. So far so good.

I want to run that configuration with the TV as a second, independent, display. Thats why I was so happy when the Raspi 4 was released. I observed the last changes of jamesh before buster, and with the 4 and buster it seems to get a stable dual headed display option with CEC etc.

It is a Samsung UE55MU8009 4K TV. Maybe this one is a problem. In a german forum one reports a problem with that TV and the raspi 4 on 19. August. There was one answer on 19. August but not another answer from the Threadstarter, if that helped. So I think it helped him. I tried the tipps, and they didn"t solve the problem.

The problem is as follows. When I boot the Raspi with the DSI display, everything is fine, DSI shows the desktop and works. When I plug the white HDMI Cable of the Raspian Foundation to HDMI 0 (beside the USB C Power Port) in the Raspi and then in the HDMI 2 or 3 connector at the TV and do a reboot then, the reboot is made and I sit in front of two black displays. The Raspi can only be reached over SSH.

I tried a lot of different combinations in the /boot/config.txt file now (with Editor or raspi-config in desktop or console version), but I wasn"t able to get ONE display working, while the HDMI cable is connected.

That is something, that makes me wonder most. I can understand, that there are problems with the HDMI connection, but the DSI Device should ALWAYS be the default display (as long as not stated otherwise in the config.txt, as far as I have learned), and if the HDMI Device is displaying something or not, the desktop should display and be be accessable on the DSI Device. But no, both screens stay (nearly) black.

In fact I observed some different phaenomens in different combinations of HDMI parameters in config.txt. The DSI Device for example, shows most of the time a blinking cursor underline in the upper left corner. But it not reacts on any input on the direct attached usb keyboard. VNC Server is unreachable. In one or two of the combinations the DSI screen stayed complete black. Most of the tests showed the rainbow screen, and the four raspberrys and the splash on the DSI display before the described behaviour appeared.

On the TV side, there was one situation, where I observed the rainbow pattern on the TV, too! But after that, everything stayed black again. The TV switched in some tests to the correct HDMI port, but stayed there black. That means, I was on Tv input source cable-TV and had a Show running. When the Raspi rebooted the TV switched to HDMI 2. So something was happening on the cable, but no image was displayed.

You’ve been incredibly patient: thank you. The official Raspberry Pi touch display is on sale today, priced at $60 (plus local taxes and shipping): you can buy it at RS Components/Allied Electronics and at Premier Farnell/Newark. Other sellers will be receiving stock later this week.

Two years ago, I began the process of looking for a simple, embeddable display for the Raspberry Pi. I honestly believed it would only take us six months from start to end, but there were a number of issues we met (and other products diverted our attention from the display – like Rev 2.1, B+, A+, and Pi 2). But we’ve finally got there, and I thought you might be interested in learning about our journey.

HDMI is the system we all know and love, it allows us to communicate with monitors up to 4K and has a relatively low signal swing to reduce EMI. There are lots of other very useful bits of the specification such as CEC (a communication channel between the TV and the Pi that allows us to receive input from the TV), EDID (a method of automatically identifying the different formats the TV supports) and a hotplug signal allow the Pi to know when you plug in the cable. The only problem with HDMI is that the electronics required to convert from HDMI to the native panel interface can be quite expensive.

DPI (Display Parallel Interface) is a 24-bit parallel interface with a clock and various synchronisation signals totalling 28 signals, all of which switch at a rate of around 70MHz. This interface has been phased out of tablets/phones because the electromagnetic noise created and power consumed by all those wires. Although it is possible to directly talk to a DPI display through the GPIO connector on a Raspberry Pi it would leave no GPIOs left for people to connect other HATs. DPI displays are available everywhere though, and are relatively cheap!

DBI (Display Bus Interface) is an old display technology that usually has inbuilt frame storage to reduce tearing, due to the memory and hardware it makes DBI screens expensive.

So our solution to this problem was to employ both DSI (to avoid using up all the GPIOs) and DPI (easily available screens in suitable resolutions) and a bridge chip/conversion board to convert between the two.

When looking for a device, we needed to look for what are termed ‘Industrial’ LCD displays. These tend to have better-quality metrics and guaranteed availability.

Our first PCB to do the DSI to DPI conversion was completed back in mid-2013. The board used a Toshiba bridge chip to convert the DSI signals to DPI ones. I spent quite a bit of time getting the Raspberry Pi to talk to the bridge device, and then got it working and displaying an image (yay). We then took it to our local EMC test facility to investigate how easy it would be to pass CE and FCC electromagnetic compliance.

When electrical currents flow around a circuit board, they create electro-magnetic fields, which can be picked up by other electronic devices. Maybe you remember what used to happen to your CRT television when your mum turned on the hoover (sorry for those of you without any experience of analogue television). This was becoming a problem for television and radio receivers; when I was a kid and plugged in my Spectrum 48K, the radio wouldn’t work properly any more. So the powers that be introduced new rules about the amount of energy a device can output at various frequencies from 25MHz up to a couple of GHz. You have to make sure your electronic devices do not cause interference, and are not susceptible to electronic interference.

Unfortunately, DPI is 1.8V signal swing, and although much slower, it needs 28 signal wires, meaning 28x more paths with the same edges switching up and down at the same time. This gives us an output looking something like:

The next step was to understand why the EMI is so bad, so we tried redesigning the board so it looks like a HAT (it’s not actually a HAT because there is no EEPROM for device tree information), and added an Atmel device to control the power/reset and PWM for the backlight. We also went through three different iterations of adding chokes to improve the noise conducting down the power supply cable, and manipulating the route of the DPI signals to improve the path of the ground return.

The first displays are supplied as a kit which requires some initial construction. Alex Eames from RasPi.TV has helpfully provided a video showing how to do it.

The display module integrates the LCD display with a conversion board that should be plugged into the Raspberry Pi through the display connector. Be aware that the connector is the same as the camera connector, but the two are not compatible, so be careful to correctly identify the display connector first.

The 15-way FPC connector should already be plugged into the display conversion board with the silvered contacts face-up. You can then plug the connector into the Raspberry Pi with the silvered connectors inboard (facing towards the USB connectors).

Attach an official 2A Raspberry Pi power supply to the display board “PWR IN” connector, then attach a standard uUSB connector from the “PWR OUT” connector to the Raspberry Pi.

The Raspberry Pi will now automatically detect the display and use it as the default display (rather than HDMI), although HDMI will still be initialised. If you’d prefer for the HDMI display to stay as default then add:

Please note, you may need to increase the amount of memory allocated to the GPU to 128MB if the videos are 1080P, adjust the gpu_mem value in config.txt for this. The Raspberry Pi headline figures are 1080P30 decode, so if you are using two 1080P clips it may not play correctly depending on the complexity of the videos.

The Raspberry Pi display has an integrated 10-point touchscreen (a bit of an overkill, but it does seem to work well). The driver for this touchscreen outputs both standard mouse events and full multi-touch events, and therefore can work with X as a mouse (although not brilliantly – X was never designed to work with a touchscreen!).

Kivy is a Python GUI development system for cross-platform applications. It is designed to work with touchscreen devices (phones and tablets), but also runs on the Raspberry Pi. To install Kivy onto your Pi follow the instructions at

From the videos you can see how capable the interface is. I’m in the process of developing a touchscreen application for an installation at home to control a safety and heating monitoring system, so you’ll probably hear more about that at some point!

Pi OS Bullseye was released in November 2021. There are a number of issues rotating the camera in Bullseye. Raspistill and raspivid rotation are not supported. If you are having issues rotating the camera, please try Pi OS Buster. It is available in the Raspberry Pi imager under Raspberry Pi OS (other). Buster will be supported until 2024.

Route the long end of the white cable under the display board. Attach the long end to the camera as shown. Install the display board onto the display with the supplied gold m3 screws. The standoffs that came with the display can be used to attach HAT boards to the Raspberry Pi.  Attach the short white cable to the display board. Make sure the writing on the cable and blue tab is facing up like the photo.

Connect the wire to the GPIO pins. We suggest starting with low speed as it is quieter. If you get the temperature icon in the display, you can always move up to the high speed.

HAT boards can be attached with the standoffs that came with the display. Use the m2.5 nuts that came with the SmartiPi Touch to fasten the HAT board down.