sainsmart 3.2 tft lcd raspberry pi wiki manufacturer

The 3.2 inch TFT LCD module is a special design for Raspberry Pi for portable application. It features a 3.2” display with 320x240 16bit color pixels and resistive touch screen. The LCD is well mated with Pi board and interface with Pi via the high speed SPI port, and support console, X windows, displaying images or video etc. It also provides 4 press buttons for user defined functions.

RPi LCD needs to use a SPI interface, but in the original image file of Raspberry Pi, the displayer is driven via a HDMI port. So the original image is not applicable for RPi LCD, and you should install the LCD driver to your Pi or use the Ready-to-use image file provided by Sainsmart,click here.

Download the LCD driver and extract it to your Raspbian OS (e.g. copy the driver to your Pi by sftpor using U disk). Then run the following command via putty:

This LCD can be calibrated using a program called xinput_calibrator which is pre-installed on the offer image. However, it was not pre-installed on original Raspbian OS. So in this case, you should get and install the program manually with

After running these commands, there will be a prompt for four-point calibration shown in the LCD screen. Click the points one by one to finish the touch calibration. Then, the new calibration data will be displayed in the terminal, as shows below. Please get these data for future use.

SainSmart 3.2" TFT LCD Display is a LCD touch screen module. It has 40pins interface and SD card and Flash reader design. It is a powerful and mutilfunctional module for your project.The Screen include a controller SSD1289, it"s a support 8/16bit data interface , easy to drive by many MCU like STM32 ,AVR and 8051. It is designed with a touch controller in it . The touch IC is ADS7843 , and touch interface is included in the 40 pins breakout. It is the version of product only with touch screen and touch controller.

The RPi LCD can be driven in two ways: Method 1. install driver to your Raspbian OS. Method 2. use the Ready-to-use image file of which LCD driver was pre-installed.

2) Connect the TF card to the PC, open the Win32DiskImager software, select the system image downloaded in step 1 and click‘Write’ to write the system image. ( How to write an image to a micro SD card for your Pi? See RPi Image Installation Guides for more details)

3) Connect the TF card to the Raspberry Pi, start the Raspberry Pi. The LCD will display after booting up, and then log in to the Raspberry Pi terminal,(You may need to connect a keyboard and HDMI LCD to Pi for driver installing, or log in remotely with SSH)

1. Executing apt-get upgrade will cause the LCD to fail to work properly. In this case, you need to edit the config.txt file in the SD card and delete this sentence: dtoverlay=ads7846.

This LCD can be calibrated through the xinput-calibrator program. Note: The Raspberry Pi must be connected to the network, or else the program won"t be successfully installed.

2) Log into the command line interface for Raspberry Pi（Initial user name: pi, Password: raspberry）, Get the latest drive from GitHub (the raspberry pie needs to connect to the Internet), Execute the following commands:

Thanks for bringing this to my attention. It appears that the upgrade package overwrites the FBTFT drivers, in particular, the Raspberry Pi bootloader. This seems to solve the problem:

I just tested this, and it looks like the difference is how SPI is enabled. In the RPi 2 it’s enabled in raspi-config, not commented out in the blacklist file. I just updated the post so it should work now!

Looks like the only difference is in how SPI is enabled. In the new release of Raspbian, SPI is enabled in the raspi-config menu under advanced settings. In older versions of Raspbian, it is enabled by commenting out the line in the blacklist file

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait fbtft_device.custom fbtft_device.name=waveshare32b fbtft_device.gpios=dc:22,reset:27 fbtft_device.bgr=1 fbtft_device.speed=48000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=0

Unfortunately, their “driver” is an SD card image containing a complete installation of Raspbian which has been preconfigured to use their display. Which is fine if you’re setting up a brand new system that doesn’t need to be a specific distro, but if you’re trying to add the display to an existing Raspberry Pi, already configured the way you want it, with software installed and data present, or if you want to use a specific distro such as Octopi, then it’s not terribly helpful.

Hello..I tired to interface this lcd “https://www.crazypi.com/raspberry-pi-products/Raspberry-Pi-Accessories/32-TOUCH-DISPLAY-RASPBERRY-PI” to my Raspberry pi model B+.I got a DVD containing image for LCD in the package.I burned it to the SD card and plugged in the display.But my lcd is completly blank.But green inidcation led (ACT LED) in board is blinking.Why my LCD is Blank ?

My Touchscreen is now working fine.The problem was for the ribbon cable on the back side of LCD.It was not connected properly.I just tighted the cable and it worked fine.Hope it will be useful tip.

Thank you for this great tutorial. I looked everywhere for this information. I have an eleduino 3.5 version A. I was able to get it working on my Pi 2 by following your tutorial and using flexfb as the screen type. I got the other settings from the image that came with the product. I did find that the ts_calibrate didn’t recognize the screen so I installed xinput-calibrator and it worked fine.

Just got my Pi2 running Wheezy, working with the Eleduino 3.5 LCD without running the OEMs image… kinda. I didn’t want to rebuild the application environment again, so was avoiding flashing the SD.

Unzipped it and looked around. From a shell script inside i kinda figured out what it was doing. I didn’t like what I saw, so I manually made changes omitting the parts I didn’t like (it rm -r my /lib/modules directory… omitted that part) and copied 2 files and 1 directory from the OEMs archive to the file system of my Pi2.

[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa21041 bcm2709.serial=0x631a4eae smsc95xx.macaddr=B8:27:EB:1A:4E:AE bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait fbtft_device.custom fbtft_device.name=flexfb fbtft_device.gpios=dc:22,reset:27 fbtft_device.bgr=1 fbtft_device.speed=48000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=0

thank you for your great tutorial, it got me on the right way. unfortunataly i only see some boot messages on the lcd and then it turns black. maybe you could give me a hint on how to get it working entirely.

i have a watterott display (https://github.com/watterott/RPi-Display) and changed the device-name to “rpi-display”. i use a rsapberrypi 2 and hae the latest raspian image installed.

Did you check to see if your device is supported yet? The device name should be specific for your screen, as listed in the fbtft file linked to in the beginning of the post

I too have a raspberry pi 2, and a waveshare spotpear 3.2 RPi lcd (v3) and I just can’t get it to work! I suspect I have a faulty LCD, but thought I’ll try this forum for help before I sent it back.

Soon as the pi is powered, the LCD lights up all white, with a few vertical pixels coloured at one of the edges, and nothing else. I don’t think that should happen – not at least before the BOIS has started up.

Anyway, point 1, says to change to dev/fb1 – I don’t have fb1. Only fb0 appears to be there. is that a clue what could be wrong? I have enabled SPI (is there a command to tell if its enabled?) I have also ran spidev to troubleshot (though I haven’t a clue what I means)

Any ideas what going wrong? I am using the latest “2015-02-16-raspbian-wheezy_zip”. Enabled SPI. done all the steps. Even changed mmcblk0p2 to mmcblk0p6 as suggested by Dabomber60 (but that freezes for me)

[ 0.000000] Linux version 3.18.5-v7+ (pi@raspi2) (gcc version 4.8.3 20140106 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2014.01 – Linaro GCC 2013.11) ) #1 SMP PREEMPT Fri Feb 6 23:06:57 CET 2015

It seems all appears to be working – just the LCD is still all white with a single line of coloured pixels on edge) and nothing else. Is there a way to output, like jeff G script, of touch points?

I had the same one, I finally found a driver for it here: http://www.waveshare.net/wiki/3.2inch_RPi_LCD_(B) you will need to translate the page, but unpack the driver then run sudo ./LCD-show/LCD32-show. It should reboot and all will be good with the screen :)

Can anyone let me know if the default OS image sent with the screen works with pi2 or just Pi B/B+ as i think my screen maybe broken but can’t confirm it yet as i have not had it working at all

My system: Raspberry Pi 2 Model B with Raspian Wheezy from Febuary 2015. LCD display of Sainsmart 3.2 http://www.conrad.de/ce/de/product/1283498/Raspberry-Pi-Display-Modul-Touch-Display-81-cm-32/?ref=home&rt=home&rb=1

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 cgroup_enable=memory elevator=deadline rootwait fbtft_device.custom fbtft_device.name=sainsmart32_spi fbtft_device.gpios=dc:24,reset:25 fbtft_device.bgr=1 fbtft_device.speed=48000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=90

sainsmart32_spi width=320 height=240 buswidth=8 init=-1,0xCB,0x39,0x2C,0x00,0x34,0x02,-1,0xCF,0x00,0XC1,0X30,-1,0xE8,0x85,0x00,0x78,-1,0xEA,0x00,0x00,-1,0xED,0x64,0x03,0X12,0X81,-1,0xF7,0x20,-1,0xC0,0x23,-1,0xC1,0x10,-1,0xC5,0x3e,0x28,-1,0xC7,0x86,-1,0×36,0x28,-1,0x3A,0x55,-1,0xB1,0x00,0x18,-1,0xB6,0x08,0x82,0x27,-1,0xF2,0x00,-1,0×26,0x01,-1,0xE0,0x0F,0x31,0x2B,0x0C,0x0E,0x08,0x4E,0xF1,0x37,0x07,0x10,0x03,0x0E,0x09,0x00,-1,0XE1,0x00,0x0E,0x14,0x03,0x11,0x07,0x31,0xC1,0x48,0x08,0x0F,0x0C,0x31,0x36,0x0F,-1,0×11,-2,120,-1,0×29,-1,0x2c,-3

ads7846_device model=7846 cs=1 gpio_pendown=23 speed=2000000 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=300 x_max=3800 y_min=700 y_max=3400

The LCD display shows the raspberry correctly. However, the touch screen input does not work. The mouse pointer can I move correctly with your finger, but I can not select things (function of the left mouse button).

Thank you so much for this great tutorial. I have my WaveShare SpotPear 3.2″ V4 working fine on my Raspberry Pi 2. If you are having problems with this specific hardware, skip step 5.

Can someone upload SD card image that works with RBP2 ? My idea is to use Eleduino TFT as additional screen and play movies via HDMI.. is it possible?

Do not follow this article when you don’t know what kind of LCD module. In my case, I follow all of this and my raspberry pi cannot boot anymore. I will try to recover, but I think I should format my SD card and reinstall OS.

Expecting this would builtin driver module within kernel and help with avoiding mistakenly overwriting anything. But with this is cause LCD screen to go blank white and no boot activity. Also noticed on HDMI it get stuck on Initial rainbow screen and stuck on that.

Also can you someone explain what exactly happen when do rpi-update? Want to understand what this step actualy doing and help me to debug any such situation and able to help others.

Does anyone tried splash boot screen with waveshare v4 LCD and Rpi2? I tried to follow some example from https://github.com/notro/fbtft/wiki/Bootsplash but no success.

Great tutorial thanks; got an X session working great 1st time. Has anybody managed to get Kodi/XMBC working on the LCD either Kodi standalone, Raspbmc or Xbian?

in the video you say to change the existing line to “snd-bcm2836” for the rasppi2 which isn’t listed in the written part of the instructions (part 4).. this should be added (I believe it caused me to have to re-image the OS again, the Pi wouldn’t boot to anything just using the written steps)

fbtft_device name=waveshare32b gpios=dc:22,reset:27 speed=48000000 width=320 height=240 buswidth=8 init=-1,0xCB,0x39,0x2C,0x00,0x34,0x02,-1,0xCF,0x00,0XC1,0X30,-1,0xE8,0x85,0x00,0x78,-1,0xEA,0x00,0x00,-1,0xED,0x64,0x03,0X12,0X81,-1,0xF7,0x20,-1,0xC0,0x23,-1,0xC1,0x10,-1,0xC5,0x3e,0x28,-1,0xC7,0x86,-1,0×36,0x28,-1,0x3A,0x55,-1,0xB1,0x00,0x18,-1,0xB6,0x08,0x82,0x27,-1,0xF2,0x00,-1,0×26,0x01,-1,0xE0,0x0F,0x31,0x2B,0x0C,0x0E,0x08,0x4E,0xF1,0x37,0x07,0x10,0x03,0x0E,0x09,0x00,-1,0XE1,0x00,0x0E,0x14,0x03,0x11,0x07,0x31,0xC1,0x48,0x08,0x0F,0x0C,0x31,0x36,0x0F,-1,0×11,-2,120,-1,0×29,-1,0x2c,-3

ads7846_device model=7846 cs=1 gpio_pendown=17 speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900

After following this tut to the letter on a brand new image of Raspian, I find that the touch driver does not function. Anyone experience the same? Basically all I did was image a current copy of rasping, did a apt-get upgrade, and then did this tutorial. Then the touch driver does not work, meaning the pointer does not respond.

The reason I did this was because on a production version of my system I added the 3.2 screen and it worked great except for the x-axis. So I wanted to see if there was something in my system that was interfering or if this is another error. Now with a raw rasping the driver does not work at all. I wonder if the touch pin has changed since the kernel is using BCM pins instead of GPIO pin numbers?

I have exactly the same problem. I also installed a new version of Raspbian, and the LCD part works fine (except all the windows are way too large), but the touch part doesn’t work at all… I’m using Waveshare Spotpear 3.2″ V4.

I remember that I plugged in the screen wrongly one time, before configuring any of the GPIO pins. Can this have damaged the screen? Still it’s weird that the display part works well and the touch part not at all.

I do not think that has anything to do with it. Other than power pins, the rest are communication. If it still works then you are good. No, there is something else. I do suspect it us related to the BCM pin numbering. The real question is… Why isnt the eeveloper responding? I have since abandoned this TFT because of his lack of response.

Touch actually goes through one of the SPI pins I think. Either the driver is toast with the required kernel update or the driver is using the wrong pin. It is very likely the this works well with previous raspian versions, but not with the new B+ and with the new kernel.

I am trying to use the sainsmart 2.8″ lcd sold through microcenter, using the sainsmart32_spi … seems to have the same pinouts, should I be able to get this to work? I am stuck at the white out screen on the lcd, doesn’t seem to recognize the module either.

The SainSmart 3.2 sold by MicroCenter (20-111-971) is actually the exact same WaveShare SpotPear v3 documented here. So maybe your 2.8 would work if you tried a WaveShare driver?

Unfortunately I’ve tried that ( a few times actually) but the file still doesn’t exist. Thanks very much for the assistance anyway. I must be doing something wrong. My Raspian came from a Noobs installation, I’m wondering if I should try installing the OS from somewhere else. My LCD screen didn’t come with a CD or any docs so I’m completely in the dark here.

I have just found a way to get this file on my system! Apparently its part of the fbturbo installation. I found it here http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=45746&start=75 (under experimental enhanced x driver (rpifb).. Sorry if this is obvious to everyone but I am SUCH a noob at this!!

Ok, what am I doing wrong. I am using a fresh install of the newest raspbian, on a Pi 2. After doing the first two steps and rebooting I get the rainbow screen, then the boot up process, and then my screen just goes black with a flashing cursor in the top left. I am not able to enter any commands or anything…like the pi is halting just after boot up. Any thoughts/suggestions would be greatly appreciated. Thanks.

Well figured out that step 1 was causing my problems. I’m guessing it is shutting off my hdmi feed and trying to switch it over to the SPI, am I guessing right? If so, not sure how I’m suppose to complete the rest of the steps if my hdmi output gets turned off before the LCD is actually set up to work…that sounds kind of smartass-like, which is not my intention, just looking for some clarification on what is going on in that first step as I am fairly new to this stuff. Thanks.

Anyway, I was able to do the rest of the steps with no problem. LCD didn’t work, but I am using a Waveshare 3.5, which doesn’t look to be supported yet. Mostly I am trying to play around and see if I can get it working somehow. Anyone found a way to do this yet?

I am having an issue with getting the GUI back. Every time I use startx my pi just sits there for about two minutes saying “No protocol specified”, and then it just gives up. I went through this tutorial about four times now and am not certain why it is doing this. I have the exact same LCD as is in the tutotial (WaveShare 3.2b). any help would be great.

Hi I am making a project for school,using the raspberry pi b+ and waveshare spotpare 3.2b. Everything works except the touch input doesn’t work. Any help would be appreciated very much.

Thanks for the tutorial. It works, but I get the boot/command line stuff on the HDMI monitor and the LCD only comes on when I do startx. Is there a way to get everything to appear on the LCD screen?

I am trying to get this same screen to work with the image of RetroPie 2.6 and it won’t work. I have followed all the steps and nothing, please help I an kinda a noob.

I have a Tontec 7 inch touchscreen with a Raspberry Pi 2 B. After following the instructions the touch screen is functioning but not properly… The only are that works is the upper left (and only a small area of that). I tried changing the width and height in the modules but it didnt change anything. Also the xy seems to be reversed, I changed the swap_xy to 1 but again no change on the screen.

Now the OS freezes at the emulation station loading screen, and if I connect my lcd it gives me a lot of error messages which I can only see on the 3.2 inch screen.

hi i have the same screen with a raspberry pi 2 im trying to run retro pie but it wont show ..however it shows all the commands …but i cant get it to show the gui …if u guys can make an image or something please i have been in this pain for two weeks already thank you

well ,,i follow all instructions and still kernel panic ,,,,may i request from mr. Circuitbasics@Gmail.Com that have a contact with manufacture and just ask for 2-3 links for image files for different versions of pi till all this f discussions are finished,,i cant understand 10 guys said we run it and 40 guys said kernel panic ,,as an expert i did 50 times imaging and follow all changes fro this forum and other forums and still cant run it ,,,so sth is wrong …..just asking the manufacture for simple f image ,,that`s it ,,,,simpleeeeeeeeeeeeeeeee

well i did it at last on pi 2,,after reading 100 pages and reimaging 50 times ,,i finally find the solution ,,,,there is a simple line forgotten to be attached in setup instruction,,,well i give u clue for prodigies ,,there is a step left between step 3 and 4,,,,and a simple change in step 5 according to your pi version ,,,that`s it ,,nothing else,,,,

Damn.. I thought I was kickin ass haha. I am using the SainSmart 3.2″.. the backlight is lit up and the pi was booting and everything just fine but on the final reboot it gets hung and says “nonblocking pool is initialized” ?? No idea what that means. But it’s def just frozen at this point.. on my main screen, and just the backlight is on the SainSmart.

This was an excellent tutorial. I have gotten an output to the screen, but no touchscreen usage . I have the Waveshare SpotPear 3.2 Inch LCD V4 screen, but using Raspberry PI 2 with wheezy. Any ideas?

Thanks a lot for this article. Very clear and easy . I am new in pi’s world and my 3.2″ screen is working fine. I rotate 90 º and works. I can use mouse and so on.Not problems.

I filed the steps to calibrate the screen but it did not work.I think because it did not find the TFT pin, because I think the touch problem is the assigned pin to control it changed.

I actually used the driver from here http://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) , from a new wheezy build, did nothing except enable SPI in config, install driver, and change mmcblk0p2 to mmcblk0p6 in cmdline.txt and it all worked, no drama.

Hi I managed to set up my touch screen ok but I now have the issue that everything desktop fits fine but the windows I open are all huge and I can’t remember how to change the size and cannot see the option in desktop preferences any idea what I have to do and is it at all possible to install kodi to run through the raspbian is as this would be a lot my useful than having to keep swapping os on every boot up many thanks in advanced hope you can help me

Advice to all who have the drivers from the (touch)screen manufacturer and cannot obtain those otherwise: you can skip everything and go to the update steps skipping the kernel and kernel modules update (as mentioned by the author) so that you don’t override the preinstalled drivers. I have a Waveshare 3.5″ RPi v3 (not the 3.2″ supported by notro’s drivers) and actually managed without any problems to get notro’s drivers make it work. However I am still reading about the xinput and xinput-calibrator to figure out how to include it as a kernel module so that I can compile my own kernel and add it there.

i have raspberry pi 2 with 3.2 inch rpi lcd v4 waveshare spotpear.i have done as per your instructions.the display is working but touch screen not working.error shows waveshare32b module not found as well as touch screen module not found messages.

Hey! i did this and rotated it… It loads console perfectly, but when it goes into startx, i get a black background with only the wastebin/trashcan… how do i get the taskbar(or whatever that bar is called)? and the raspberry background?

Unfortunately I have lost the Touch facility on my Waveshare 3.5″ LCD Touchscreen? Can you offer any reasons as to why? I copied the Raspbian image to my Raspberry Pi from the Waveshare website first of all. The Touchscreen displays but is not reactive with any touch

I have purchased a raspberry pi B+ total kit and waveshare 3.2 TFT display online. In the package i have been given a pre-loaded NOOBS installed SD card. I did not even start anything yet. What should i do what r the things needed and how to connect the display i really want to know. I need help as i don’t know anything. Does the above solution help or will u suggest something………………..

Hi great article thanks. I am trying to get a waveshare 7 inch LCD with capacitive touch running it works with the suppled image but if you upgrade it breaks the capacitive touch. I have a sense-hat and GPS which require the latest kernel and RASPIAN image and the install program for the screen replaces the /lib/modules directory and the kernel with older ones. I need to be able to install the touch drivers into a new clean OS can anyone give me some pointers? Thanks

For anyone who have those unbranded cheap TFT touch modules and cannot get it to work with this guide, I had success on my 3.5″ with the following steps: http://pastebin.com/89qmFbPB

I have the WaveShare 3.5 (A) and cannot get it to work with the Kali Linux with TFT for Raspberry Pi. Have anybody gotten the A to work? (Not the B, theres instructions for the B already and dont work with A)

So I have the original image that came with my screen and it works fine with the LCD but my problem is that I want to use my LCD screen with other distros (at this time I am trying to use it with Kali Linux with TFT support by default https://www.offensive-security.com/kali-linux-vmware-arm-image-download/) What do I have to do to transfer the needed files from the original image that WORKS with the screen and use them with another image?

I originally bought this bundle http://www.amazon.com/gp/product/B013E0IJUK?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00 with an RPi LCD V3 and no extra documentation on the specifics on the chipset. I tried with the bftft drivers but since I have no idea what to call this screen I just suppose it isn’t supported.

After 4 lost days I just decided to get another screen, a Waveshare 3.2 (just like the one on this tutorial), I’ll follow these steps and see if it work for me.

I’m not sure if the Jessie kernel is compatible – can anyone please confirm or not ?? Adafruit states that their setup for TFT screens are Wheezy only ; is this a different setup ??

I am using the same LCD and followed your tutorial. Have your tested the guide lately? Are you certain that it works? I see the boot messages on console but I get white screen as GUI starts.

Oct 16 17:38:48 spare kernel: [ 12.544859] graphics fb1: fb_ili9340 frame buffer, 320×240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=50, spi0.0 at 48 MHz

After I rebooted in step 3, my raspberry pi won’t boot up again. It goes thru the process of booting and the text scrolls down and every thing says “ok”. Then instead of going to GUI it just guys to a black screen on my monitor with a blinking underscore in the top left corner. Anyway to get around this? or should I start over with a fresh disk image??

That is what happens to mine also.. So long story short —> THIS SITE NEEDS TO BE UPDATED OR SHUT DOWN <— There are a hundred people on here that have all lost everything on the pi drive, and spent all day (or more) working thru this tutorial 4 or 5 (dozen) times and nothing. Just have to reinstall the os over again and again.

Please check out my answer, it may help you if it works. I’m not in that case but I’m assuming that the desktop environment simply doesn’t automatically start running anymore… This can be changed in the raspi-setup

Try typing ‘startx’ if you problem isn’t solved (assuming you’re using Raspbian and LXDE), it should start the desktop environment you’re used to see. What you’re seeing is the Command Line Input interface (CLI), the most basic way to interact with a computer. Hope I helped you a little

I have tried to set up waveshare 32b on my Pi B using the latest Raspian download. I learned a lot in the process using Windows Putty, Nano etc. I have repeated the setup process several times from scratch and included the corrections for possible overwriting. My Waveshare SpotPear 3.2 inch RPi LCD V4 just shows a white screen. Any suggestions?

There was no disk included. I asked for drivers and was given a download link to the image file. After down loading this I tried it and still got just a white screen. The HDMI monitor locks partway though the boot. I can still log in to pi using putty from my PC.

Hi, I am using raspberry pi 2 with raspbian jessie installed. I the waveshare spotpear 3.2 v4. The above instructions are not working. and after completing the steps there was no display from hdmi or lcd. One things to notify is.: the etc/modules files only had i2c-dev and not snd-bcm2835.

I am trying to get this to work with Retro Pie 3.3.1 and the Waveshare3.2″ v4 but I only get the terminal on the lcd and emulation station starts on hdmi. to get it working with retro pie i just replaced startx with emulationstation. how do i get this to work?

Sir, Your post has very useful to me. i am using Tinylcd. but i cant get display. i am performing all the steps in your post. i cant get touch controller information from the product website and also i am using RASPberryPi B+ model. could u please give me best solution to my work. Than you.

what if OS is not Raspbian, any other distro like Yocto project, etc.? Could you please specify process without “rpi-update” that makes driver installation process more generic, not dedicated to Raspbian.

I completed all steps except for the last one (I want it to boot to console). However, when I reboot, it never completes the boot process. I start in recovery mode and check the cmdline.txt file and it is exactly how it appears on this page. I copied the kernel info as well, but I am not sure if it correct as I cannot get to it to check. Any suggestions? I might just reinstall the OS and start over…

i installed android OS in raspberry pi 2. can i use same LCD touch screen set up for android installed raspberry pi 2 which you are used for raspbian.

Is it normal the white back light during the whole process of initializing (I suspect that during the transportation trere is a deffect)? The problem is that I missed the step #1 and I performed it at the end. Unfortunately I don’t have any monitor available right now – neither “normal”, neither LCD :))))). Is it possible turning back the system or the only option is reinstallation of the Raspbian?

I have KeDei 3.5 inch TFT version 4.0 by Osoyoo. (released after January 1 2016) how do i get it working with vanilla Raspbian Jessie (do not want to install the image sent by the seller)

I’m trying to use an original Raspberry Pi model B with a cheap 3.5 inch 320×480 LCD which allegedly was manufactured to work with the Pi and has the correct fittings to fit over the GPIO pins. The operating system is the latest, downloaded yesterday and installed with NOOBS. I can’t get past step 2 of this guidance. When I reboot after using raspi-config I can see text generated as the Pi boots, then the HDMI fed screen goes blank apart from a flashing cursor in the top left hand corner. The LCD just remains white with nothing else on it. I have missed out step 1 and rebooted after step 2 and the screen functions as I would expect. Does anyone have any ideas please?

Thanks for the great tutorial. I do have a question. Once you install the drivers for the lcd are you effectively disabiling the hdmi port or is it still available to use and will the pi function with both displays. I have a pi 3

once you install the drivers it replaces the kernel by disabling hdmi output and enables it for LCD. i don’t think we have a solution to get em both working at the same time. ( you are encouraged to search for it )

Thanks for the guide, have been doing this with my son but once we leave raspi config and reboot all we get is a black screen with a flashing white horizontal line (dash). Can you help? I have looked in the comments at the end of the article but no one else appears to have this issue.

I have a raspberry pi 2 with waveshare screenn 3.5 inches. Isn’t it the same instructions. But it isnt working, all i get is a white screen, and the red led on the pi is on. The green LED isnot working.

My Rpi3 gets “ERROR: could not insert ‘spi_bcm2708’: No such device” after I enable SPI in the raspi-config.My Rpi3 is freezing on the rainbow screen after I reboot at the end of step 3. I’ve tried adding boot_delay=1 to config.txt.

if any interested, now i have a raspian image working on raspberry 3 with Waveshare 3.5, also with sdr support for dongles and FreqShow working perfectly on touch

ads7846_device model=7846 cs=1 gpio_pendown=17 speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900

No matter what I do, I can’t get this to work. It works perfectly fine on my Pi2, but when I follow and use the guide on my Zero, I always end up with the activity LED blinking 8 times (corrupt SD/filesystem error).

I’d like to find the driver software for my 7″ LCD with touch (official Pi unit) so that I can use it in buildroot. I wanted to make sure this kernel is the one before I started digging further.

I started through your tutorial and completed step 3 and rebooted. After the Raspberry screen and some of the boot text on my HDMI monitor, I now have a black HDMI monitor and a white screen on my LCD. Does this mean that the bootloader was overwritten or something else is wrong? How am I supposed to enter in the proposed fixes to the bootloader, when I can’t get the RPi to boot? Do I have to interrupt the boot process at some point to reinstall the bootloader or what?

Its a script. Download and instead of running sudo ./LCD4-show run cat ./LCD4-show to simply display what it does without actually running it. The commands are fairly simple modifying a few files. I actually saved the LCD-show.tar.gz on my own server for faster future download but also for backup as it saved me tons of hours (if that’s a measuring unit for time :) )

I used this link though (smaller file ~ 50 KB, fast download) http://www.waveshare.com/w/upload/4/4b/LCD-show-161112.tar.gz and replaced LCD4-show with LCD32-show in the last line.

I’m using RasPi Zero with latest (as of last week) Jessie Raspbian. Did you run the script? If it didn’t work and you have modified other files in the process of making it work, I would recommend installing a fresh installed image on a new card and running the script. Can you suspect the screen being faulty or got “burned” in the process?

i bought a 3.5 inch tft lcd screen from banggood. and i have installed raspian jessie, the latest version, in my sd card. but when i power on my Pi, only a white backlit screen comes. there are no images or graphics whatsoever.

The owner of this article should including a WARNING in the header that if someone follows the steps, they will install a deprecated driver (which is only visible as tiny text on its gethub page here https://github.com/notro/rpi-firmware). This driver after install will break Raspberry Pi and the SD card will need to be reimaged, for some less experienced users, this could also mean lost work if they failed to backup their code or resources. On windows, it requires installing Linux reader software and it takes a long time to fix this f**kup which could easily have been avoided if the author had and sense of responsibility.

I have done every thing right but the only major problem is that the screen is still white and my raspberrypi freezes after a line of code when booting up and I cant get in with SSH

Will your system work with my SainSmart 2.8″ 2.8 inch TFT LCD 240×320 Arduino DUE MEGA2560 R3 Raspberry Pi ? I would like to know before not be able to back out. Thanks, Lee

I know I will end up regretting this, but how do I change fb0 to fb1? I’m on the screen that has all the info, but no way to change it. Am I looking for a file? I have had my screen for MONTHS and I can’t do anything with my pi or the screen. I am >< close to smashing both. COMPLETE WASTE OF MONEY so far!!

hello. I really appreciate your blog post. I have a raspberry pi 3 B. I have been unable to get my waveshare 3.2 screen to work.I am at a complete loss for what to do. I do step 2 I change fb0 to fb1 and then follow your directions I don’t get the prompt to reboot; however, I do it manually with sudo reboot. that works fine then I complete step three and that works just fine; however once I reboot from getting those drivers and when I attempt to reboot it is unsuccessful and then my whole raspberry pi will not restart. then when I power it back on it will just shut back off. I then have to redo noobs onto a new SD card I would GREATLY appreciate anyones help

I ‘m actually using a LCD Waveshare3.2” , I followed your steps to setup the lcd touchscreen for my rpi and it work but I have a problem with the resolution because if I open a repertory I do not see the whole contents on the screen .

hi! thank you for this post…. I was wondering if all the raspberry pi’s gpio are being held by this screen or do we have any of those availables for use??

it worked. but the resolution is for bigger screens. i got the menubar small, but the rest appears too big , and out of screen. the wastebasket icon is 1/6 of my 3.2″ screen. wich HAS the resolution capability too display the whole desktop. But i’m a PI newby and dunno how to adjust the screen resolution on this display. anybody?

I did a 5inch LCD for my raspberry pi. I dont use the touchscreen so i didnt have to install any drivers. It works out of the box but doesnt cover the whole screen unless you open the terminal and do:

HI I have my RPI running Pi Presents on a view sonic TD2230 Touchscreen. It all works fine, touching the click areas can navigate you thru my presentation, The problem arises when you use multitouch gestures like you would on a iPhone. Pinch or expand etc… and then all touch ability goes away. I can still control the presentation via a mouse, but I don’t get touch control back until I either relaunch Pi Presents, or if I unplug and plug the usb cable going to the touchscreen.

Could you provide me with a os image of open elec that you already built for the waveshare spotpear v4 3.2 inch touchscreen,because I cannot make sense of your website’s instructions?

Much of this is outdated on Raspbian Stretch where device tree overlays (see https://www.raspberrypi.org/documentation/configuration/device-tree.md) provide for most of the configuration automatically.

In the case of the WaveShare driver, their setup script from their “LCD_show” repository will copy a device-tree overlay to /boot/overlays/ that provides most of the module config etc via boot-time device-tree patch.

After I did the step that “INSTALL THE FBTFT DRIVERS” and then reboot, my raspberry pi couldn’t boot successfully and the green light is always on, could you help me solve this problem? Thank you.

Total memory of 256 KB. Uses the ATmega16U2 (ATmega8U2 before Rev3) USB chip. Most shields that were designed for the Duemilanove, Diecimila, or Uno will fit, but a few shields will not fit because of interference with the extra pins.

Upgraded from Seeeduino Stalker V3.0 Lower power consumption (down to 100uA in sleep mode) Extra toggle switch for X-bee area 2 extra toggle switches for selecting the INT pin connected to RTC 3.3 V and 5 V dual mode

Serial communication on pin D0 (RX) and pin D1 (TX). used to receive (RX) and transmit (TX) TTL serial data. These pins are connected to the corresponding pins of the FTDI USB-to-TTL serial chip. By sliding the switch (S1), RX/TX pins can be re-routed to Bluetooth UART connector.

inviot U1 (arduino-compatible) all-in-one board with LCD, rotary encoder, RTC DS3231, EEPROM, buzzer, push buttons, RGB Led, NRF24 plug, and ESP8266 plug.Added features:

Japanese Arduino compatible kit using Uno board setting. Includes two mini-B USB sockets, 1602 LCD socket, 5 V or 3.3 V power selection, breadboard area.

Platino is an Arduino compatible board that supports 28-pin and 40-pin AVR devices. The board features multiple footprints for user interface elements like LCDs, pushbuttons, rotary encoders, LEDs and buzzer, supported by an extensive library. Bootloaders are available for all supported processors. On its backside are Arduino shield compatible connectors plus other extension connectors.

A low cost Arduino clone using the ATmega168/ATmega 328/ATmega 8 and designed for prototyping, it includes onboard peripherals such as an RGB LED, switches, IR LED, TSOP and LDR.

Fully Arduino compatible board, that fits perfectly on a Raspberry Pi, and can be programmed through the Raspberry Pi"s serial interface. It also breaks out the Raspberry Pi"s SPI and I²C interfaces, or can be used as a stand-alone Arduino when powered with the external power header.

Includes 14 color-coded 3-pin connectors for direct cable connection of servos, electronic bricks, etc., and six color-coded3-pin connectors to analog inputs for electronic bricks, etc. Provides improved 3.3 V regulator supplying 500 mA, and optional 3.3 V operation. Switching regulator provides 5 V 2 A from up to 20 V external supply.

Includes 6 color-coded 3-pin connectors for direct cable connection of servos, electronic bricks, etc., and 6 3-pin connectors to analog inputs for electronic bricks, etc. Provides improved 3.3 V regulator supplying 500 mA, and optional 3.3 V operation.

Can act as a host for an Android device and is compatible with the Android Open Accessory Development Kit, Micro SD card slot, D13 pin isolated with a MOSFET of which can also be used as an input.

Includes both 3.3 V and 5 V regulators for shields, D13 pin isolated with a MOSFET of which can also be used as an input. Can be connect to Arduino using CAT5 cable.

Arduino Due with onboard Ethernet, software-compatible with Arduino Ethernet shield, D13 pin isolated with a MOSFET of which can also be used as an input.

Uses Arduino Due form factor and largely compatible pin allocation. Runs at 5 V, but can be modified to run at 3.3 V. Triple-core, 32-bit, 200 MHz Aurix processor. 4 MB flash, 550 kB SRAM, 128 kB DataFlash. Optional CIC61508 safety monitor. Arduino IDE supported via add-in, plus Eclipse-based tools with multicore debugger.

MBZ Pro Mega is an Arduino compatible stand-alone board with a prototyping area and built-in Wi-Fi. Featuring a compact design, it helps to shrink Arduino projects and make it permanent.

This is a minimalist tracked platform based on the Arduino Duemilanove. Has an ATmega328 with Arduino bootloader, a dual H-bridge and additional prototyping space and headers. It is compatible with many shields, though four digital pins are used when operating the motor controller. Has an onboard voltage regulator, additional LEDs, a temperature sensor, and a light sensor. Part of the DFRobotShop Rover kit.

An Arduino Mega 2560 compatible board designed for auto-piloting and autonomous navigation of multirotor aircraft. Designed to be stacked with sensor bobs and boards with several breakout boards available.

These boards are compatible with the Arduino software, but they do not accept standard shields. They have different connectors for power and I/O, such as a series of pins on the underside of the board for use with breadboards for prototyping, or more specific connectors. One of the important choices made by Arduino-compatible board designers is whether or not to include USB circuitry in the board. For many Arduino tasks, the USB circuitry is redundant once the device has been programmed, so that circuitry can be placed in the cable between development PC and board, thus making each instance of the board less expensive, potentially smaller, and more power efficient.

Built around ATmega 2560 @ 16 MHz Massive GPIOs: 70 digital I/Os, 16 analog inputs and 4 UARTs, etc. Small form factor, 30% smaller than Arduino Mega 3.3 V and 5 V dual mode. Can be powered through a battery or through an AC to DC adaptor

BBFuino come with the ATmega328 controller, loaded with Optiboot (Arduino UNO"s bootloader), compatible with Arduino IDE and sample code, design to fit breadboard for prototyping and learning, lower down the cost by taking out the USB to UART IC, so the board has the basic component to operate.

The Crumbuino-Nano is a low-cost module comparable to the Arduino-Nano and can be used as Arduino-Nano in the Arduino-IDE. The Arduino bootloader is preloaded, hence the module is ready-to-use. The documentation shows the pin mapping of Arduino-naming to module pinout.

The Crumbuino-Mega is a low-cost module comparable to the Arduino-Mega 2560 and can be used as Arduino-Mega 2560 in the Arduino-IDE. The Arduino bootloader is preloaded, hence the module is ready-to-use. The documentation shows the pin mapping of Arduino-naming to module pinout.

A compact board with Molex connectors, aimed at environments where vibration could be an issue. DragonFly features the ATmega1280 and have all 86 I/O lines pinned out to connectors.

Freeduino USB Mega 2560, designed in India with Male headers (coming soon with Female Headers). Suitable for use in project, R&D, device and applicationsFreeduino USB Mega 2560 is a cost-effective and 100% pin and software compatible to the popular Arduino Mega 2560. Uses through hole components and has male headers.

A combination of an ATmega328P and an I²C based RGB backlit LCD interface (software compatible with the Adafruit RGB LCD shield), along with a USB serial programming interface done as a "backpack" module for the LCD.

The modified Arduino IDE allows the compiled user sketch to be uploaded onto the processor either with or without the proprietary GNSS software. NavSpark has 17 GPIO pins, which include two UARTs, 1 I²C, 1 SPI, 1 PWM, and a trigger. The first UART is usually used by the GNSS software to output NMEA 0183 data, although this can be disabled. This UART communicates over USB through a PL2303 serial converter and the transmit output is also made available on a pin. A 1 pulse per second signal is produced on a dedicated pin when a valid fix has been made.

There is a GPS-only version, a combined GPS/GLONASS version, and a GPS/Beidou version. An adaptor board adds a JST connector for a lithium-ion battery, a charger for the battery, and a microSD card slot connected to the SPI pins.

An Arduino Duemilanove compacted down to a breadboardable device (36 mm x 18 mm) that can be inserted into a standard 600 mil 28-pin socket, with USB capability, ATmega328P, and 6 onboard LEDs.

A miniature Arduino compatible board with all of the digital and analog I/O pins brought out into a single line of pins (SIP). Available as a kit, intended for use with a solderless breadboard.

SODAQ, an Arduino Compatible Solar Powered sensor board The Raspberry Pi-sized SODAQ board is built for Solar Powered Data Acquisition. It is fitted with a Lipo charge controller and 12 Grove sockets for plug and play prototyping. It runs at 3.3 V and 8 MHz. It also comes with a DS3231 Real Time Clock and 16 Mbit serial flash for data logging. Its "bee" socket can use a range of different modules, like Xbee, RFbee, Bluetoothbee and GPRSbee to make the board communicate. The latest version has the powerful ATmega1284P microcontroller with 128 KB program space and 16 KB RAM and is still Arduino IDE compatible.

Arduino compatible board designed specifically for RF mesh network experiments. It features 10 I/Os, a 10-pin ISP programming connector, a connector for a standard LCD display (in 4 bit mode) and a connector for a 2.4 GHz RF module.

Arduino Mega compatible board designed specifically for robots requiring large numbers of servos. A built in 3 A switchmode power supply allows servos to plug directly into the board. Pin spacing allows making custom shields from standard prototype board.

Teensy++ 2.0 microcontrollerA slightly more powerful version of the Teensy 2.0. It has 46 I/O pins; 8 KB RAM; 128 KB of flash; 10-bit ADC; UART, SPI, I²C, I²S, Touch and other I/O capability.

A very small board based on the Freescale MK20DX128VLH5 CPU. It has 34 I/O pins; 16 KB RAM; 128 KB of flash; 16-bit ADC; 3xUARTs, SPI, I²C, I²S, Touch and other I/O capability. Version 3.0 is not recommended for new designs.

Same form factor as Teensy 3.0. Based on the Freescale MK20DX256VLH7 CPU. It has 34 I/O pins; 64 KB RAM; 256 KB of flash; 2x16-bit ADC; 12-bit DAC; 3xUARTs, SPI, 2xI²C, I²S, CAN bus, Touch and other I/O capability. All digital pins are 5 volt tolerant. Teensy 3.2 adds a more powerful 3.3 volt regulator, with the ability to directly power ESP8266 Wi-Fi, WIZ820io Ethernet and other power-hungry 3.3 V add-on boards.

Form factor compatible with Teensy 3.0/3.1/3.2, with more pins directly available. Based on the NXP/Freescale MK64FX512VMD12 CPU. It has 58 I/O pins; 256 KB RAM; 512 KB of flash; 27 analog inputs on 2x16-bit ADC; 2x12-bit DAC; 17 timers (20 PWM outputs); 6xUARTs, 3xSPI, 3xI²C, 2xI²S, CAN bus, On-board Micro SD Card, Touch and other I/O capability. All digital pins are 5 volt tolerant.

Form factor compatible with Teensy 3.0/3.1/3.2, with more pins directly available. Based on the NXP/Freescale MK66FX1M0VMD18 CPU. It has 58 I/O pins; 256 KB RAM; 1024 KB of flash; 25 analog inputs on 2x16-bit ADC; 2x12-bit DAC; 19 timers (22 PWM outputs); 6xUARTs, 3xSPI, 3xI²C, 2xI²S, CAN bus, 2nd USB (Host mode supported); On-board Micro SD Card, Touch and other I/O capability. I/O pins are not 5 V tolerant.

The teensy 4.0 has an NXP i.MXRT1062 ARM Cortex-M7 at 600 MHz with 1024 KB RAM (512 KB is tightly coupled), 2048 KB flash (64K reserved for recovery & EEPROM emulation), two USB ports, both 480 Mbit/s, three CAN bus channels (one with CAN FD), two I²S Digital Audio, 1 S/PDIF Digital Audio, 1 SDIO (4 bit) native SD, SPI, all with 16 word FIFO, 3 I²C, all with 4 byte FIFO, 7 serial, all with 4 byte FIFO, 32 general purpose DMA channels, 31 PWM pins, 40 digital pins, all interrupt capable, 14 analog pins, 2 ADCs on chip, Cryptographic Acceleration, Random Number Generator, Pixel Processing Pipeline, Peripheral cross triggering and more in a tiny 1.4 by 0.7 inch teensy 3.0/3.1/3.2 form factor

A lower cost version of the Teensy 3.1/3.2. It has 27 I/O pins; 64 KB of flash; 12-bit DAC; 3xUARTs, 2xSPI, 2xI²C, I²S, Touch and other I/O capability. I/O pins are not 5 V tolerant. No FIFOs on serial 1 and serial2. Fewer hardware timers.

An open source enhanced Arduino-compatible board that uses an ATmega16/32/324/644 instead of an ATmega168. This provides 16/32/64 KB of flash, and 32 general I/O pins in a 40-pin DIP device.

uChip mounted on a breadboard Arduino Zero compatible, with narrow (0.3" row spacing) 16-pin DIP footprint (breadboard compatible). It features built-in buck (to power external circuitry) and boost (to power USB devices when operating as a USB host) converters and software selectable output voltage.

Pin compatible with Arduino but uses the ethernet enabled PIC microcontroller to connect to the Internet. Allows sending of email, display of javascript enabled webpages, and remote web based access and control from around the world.

32-bit MIPS-M4K PIC32MX processor boards (40-80 MHz). The Arduino libraries have been implemented natively for the PIC32MX and these kits run in a fork of the standard Arduino IDE, MPIDE

32-bit MIPS-M4K PIC32MZ processor boards (200 MHz). The Arduino libraries have been implemented natively for the PIC32MZ and these kits run in a fork of the standard Arduino IDE, MPIDE

HiFive1 boardUno form factor, 5 V and 3.3 V, 19 digital I/O (9 PWM), 0 analogue in. 16 MB QSPI flash (execute in place, with 16 KB icache), 16 KB SRAM. Arduino IDE support with 16/256/320 MHz presets and port of Arduino library. Also works with standard C/C++, stdio, GDB from the shell. Hardware multiply (4 cycles) and divide (32 cycles).

The EVAL-ADICUP3029 is an Arduino Uno form factor compatible platform based on the ultra low power ADuCM3029 32-bit ARM Cortex™-M3 microcontroller. The platform is designed to be a development and prototyping vehicle to get design ideas from concept to production with a minimal risk and faster time to market. The EVAL-ADICUP3029 is designed for IOT (Internet of Things) applications in mind, and therefore comes with on board Wi-Fi and Bluetooth 5.0 capabilities. A free version of CrossCore Embedded Studios (an Eclipse-based Analog Devices Interactive Development Environment) is supplied to the designer for debugging and application development. Add-on hardware modules, MCU drivers and software application examples help form a complete ecosystem that designers can leverage into their final product.

Chipino is an electronics prototyping platform based on a Microchip PIC microcontroller. It was designed to use the same footprint and connection scheme as the official Arduino boards to allow Arduino shields to be used with Chipino.

The PSoC 4 Pioneer Kit is a development platform enabling users to design with the ARM Cortex-M0 PSoC®4 device family. The kit features the PSoC 4200 device family as the main processor and includes a PSoC 5LP (ARM Cortex-M3 processor) to perform programming and debugging. The kit is supported using PSoC Creator, which is a free IDE for embedded development targeting the PSoC 3/4/5LP device families. In the summer of 2013 Cypress supported the kit with a 100 projects in 100 days campaign on the community forums at Element14.

Amicus18 is an embedded system platform based on PIC architecture (18F25K20). Can be programmed with any programming language, though the Amicus IDE is free and complete.

Board based on a PIC microcontroller, with native USB support and compatibility with the Arduino programming language plus an IDE built with Python and sdcc as compiler.

168 MHz Cortex-M4 (STM32F4) with up to 1,408 KB of code storage and 164 KB of RAM. On-board USB, Ethernet, Wi-Fi, SD card slot. Support for the .NET Micro Framework. Development environment is MS Visual Studio and C#. Pin compatible with Arduino shields although drivers are required for some shields.

72 MHz 32-bit ARM (GHI Electronics USBizi chips) micro-controller boards with support for the .NET Micro Framework. Pin compatible with Arduino shields, although drivers are required for some shields.

Breeze boards are prototyping platforms for 28-pin PIC microcontrollers. They come with a PIC18F25K22 (USB-UART interface) or PIC18F25J50 (direct USB interface), however almost any 28-pin PIC can be used with the platform.

"Arduino Blog- Arduino Mega: bigger, more powerful, still blue". Arduino.cc. 2009-03-26. Archived from the original on 2014-01-16. Retrieved 2013-01-18.

I have a couple of these displays. They are different from the Sainsmart, not the SSD1289 controller. It"s the ILI9327, the pin out is different from the other projects I have seen. It looks like it needs to be 16 bit parallel, and the notation on the board makes it hard for us NOOB"s to make the jump to know where to put the sinc signals.

19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the default Debian distribution unless stated otherwise. A suggested suffix markup scheme is as follows:

The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximately 100 mA. USB devices using more than 100 mA had to be connected via a powered hub. The Raspberry Pi"s PSU was chosen with a power budget of 700 mA of which 200 mA were assigned to the USB ports, so the Raspberry Pi"s (poly)fuses were designed only for devices up to 100 mA, and typical 140 mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100 mA limit. As a consequence the USB ports are only directly suitable for "single current unit" USB devices which, according to USB specifications, are designed to work with just 4.4 Volt. Not only do non single current unit devices draw more current (causing greater Voltage drops, and greater stress on the fuses), they also might require 4.75 Volt to work.

Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. [2] [3]

The FLIRC USB dongle allows the use of any remote control with your Raspberry Pi. Configure the device on your desktop PC, then simply plug into your Pi for a perfect media center companion. Available from Pi Supply and The Pi Hut

ZTE Rocket MF591 - Tested with T-mobile network and Model B+ running Raspbian with usb-modeswitch and Sakis3G script. (Followed guide to work: http://www.instructables.com/id/Raspberry-Pi-as-a-3g-Huawei-E303-wireless-Edima/?ALLSTEPS)

You will usually want the alsa package for sound. In the Debian image for Raspberry Pi (and possibly other distributions) USB sound cards are prevented from loading as the first sound card, which can be an annoyance if it"s the only device you have. To disable this behaviour edit /etc/modprobe.d/alsa-base.conf and comment out the last line; options snd-usb-audio index=-2 . If you are not user pi you may need to add your username to the audio group thus: sudo adduser yourusername audio (user pi usually belongs to this group anyway).

If you encounter problems setting up your USB soundcard check the RPi Wiki article in the linuxaudio.org Wiki: http://wiki.linuxaudio.org/wiki/raspberrypi

The FLIRC USB dongle allows the use of any remote control with your Raspberry Pi. Configure the device on your desktop PC, then simply plug into your Pi for a perfect media center companion. Available from Pi Supply, The Pi Hut and Buy Raspberry Pi Australia

DVB-T205, based on rtl2832u chipset, worked with this driver on older 3.2 kernel. Couldn"t get same device working reliably on current kernel. (On the older 3.2 kernel it worked with Saorview (Irish DTT service), both HD & SD.)

TV28T v2 USB DVB-T & RTL-SDR Receiver, RTL2832U & R820T Tuner, MCX Input. DVB-T works with OpenElec 4.2.1 connected to the PiHub, tvheadend backend + frontend, finds all expected, non-encrypted channels in the south of Germany. I did not try to use the remote.

Mystique SaTiX-S2 Sky USB: Scanning/watching SD and HD works via vdr and streamdev plugin, watching on the Raspberry Pi directly is laggy as hell. DVB-USB and I2C support must be enabled in the kernel. Needs drivers/firmware from here.

K-World UB499-2T Dual DVB-T USB Tuner. IT9137 chipset. With no other USB devices connected Raspberry Pi can just about power this stick. IR and supplied remote work with XBMC.

Technisat_SkyStar_USB_HD. Instructions: http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD Used the Raspberry Pi to receive and redirect it via network to another host. Didn"t try to play back the stream on the Raspberry Pi itself. Tested with Astra 19.2E radio and SD-TV channels

TT-TVStick CT2-4400 USB Fernbedienung rev2. DVB-T works with OpenElec 4.9.4 BETA connected to the PiHub, tvheadend backend + frontend, finds all expected, non-encrypted channels in the south of Germany. DVB-C also works, finds around >30 TVs and >100 radio stations. I did not try to use the remote, nor did I listen to any radio station. TV works, SD channels are ok, HD channels jitter. tvheadend backend crashes often within OpenElec 4.9.4 BETA, but restarts, so still buggy but looks good(BETA!). It did not work out of the box with the stable OpenElec 4.2.1.

Garmin eTrex Vista HCx: It works, but it may draw too much power. To get it working (software part): https://wiki.openstreetmap.org/wiki/USB_Garmin_on_GNU/Linux

GlobalSat BU-353 Does not require a powered hub, works fine when directly plugged into the Raspberry Pi. On Raspian, requires the gpsd and gpsd-client packages. For some reason, the gpsd daemon does not always start correctly on boot. You may need to do something like the following to manually restart it:

A USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC. The USB end connects to the PC and the UART header end connects to the USB. While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.

A USB to Serial (RS-232) adapter is used the other way around, ie. the USB end connects to the Raspberry Pi and the RS-232 end (DSUB-9 or DSUB-25 pin) to the other device which may be another computer, (old) modem or printer, or some electronic test equipment.

FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by lsusb as ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port. Appears as /dev/ttyUSB0, and requires the user to be a member of the dialout group (which pi is for Raspbian Wheezy). Initially tested using an old RS Datalinker setup in "loopback" mode via microcom upto 9600 baud, and gtkterm after installing that from source code. All handshake lines toggled as expected and no characters were lost. Subsequently gtkterm was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.

Based on the Prolific PL-2303HX chipset. Listed by lsusb as ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port. Appears as /dev/ttyUSBX with GUID dialout so your user has to be in that group. If not, sudo usermod -a -G dialout yourusername will add your user to the dialout group. Works great with screen /dev/ttyUSBX 115200 to connect from your workstation to your RPi.

CH340 Chipset - Currently not supported by RPi but there is a patch of kernel code here, but it is for a 2.X kernel. If you find you have bought one of these, then it may work under Windows, but as of writing there is no support for RPi. Otherwise you can have a go at getting the patch to work.

PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer. Worked fine under RISC OS Raspberry Pi with its in-built BJC-250 driver. Could not install the CUPS drivers etc. for Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I"d updated/upgraded Wheezy all was fine.(See notes at CPM-Spectre-Pi...USBtoParPrntAdapter for more info. and also a CUPS/Wheezy installation guide)

2.5" SATA HDD USB Adapter with silicone HDD sleeve. Model: USB-ADT-25SATA. Works on powered Hub, not directly to Raspberry Pi. Built-in "Y" power adapter. Does work direct on some ver2.0 boards if used with 5.25 power supply, or Y adapter

Initially would not work when plugged in directly to Raspberry Pi. Worked when connected via an unpowered Trust hub. Worked after Raspberry Pi was modified with 10K resistors over the USB polyfuses (warranty invalidated). Probably would work fine with powered hub.

To make it working deploy the Futronic libScanAPI on your Raspberry Pi (example code and instructions included): Media:ScanApi_armlinux_RPi_gnueabihf_gcc472_update1.zip ‎

Futronic has released an updated API. This works with their newer "H" model scanners (updated CMOS). This means the FS80H and FS81 (the OEM version of the FS80H) will now work with the RPi (I tested this myself).

Unbranded active converter known as the "blue cube". Based on the