Support for Waveshare 3.5 Spotpear

[sudobrew]

Hello, I have been attempting to set up a Waveshare 3.5 Spotpear , but all I have been getting is a blank bright white screen. I'm was hoping someone with a bit more experience would have more insight.

http://www.amazon.com/Waveshare-Raspberry-Resistive-Interface-Rapsberry-pi/dp/B00OZLG2YS

From the manufacturer: 1,17 - 3.3V 2,4 - 5V 3,5,7,8,10,12,13,15,16 - NC 6,9,14,20,25 - GND 11 - TP_IRQ (Touch Panel interrupt) 18 - LCD_RS (Instructions / Data Register Selection) 19 - LCD_SI / TP_SI (SPI data input) 21 - TP_SO (SPI data output) 22 - RST (Reset) 23 - LCD_SCK / TP_SCK (SPI clock) 24 - LCD_CS (LCD chip selection) 26 TP_CS (Touch Panel chip selection)

I have tried a few variations of: sudo modprobe fbtft_device custom name=fb_ili9341 speed=48000000 gpios=dc:18,reset:22 bgr=1 rotate=270 width=480 height=320

But so far all I get is the HDMI to freeze and the LCD remains bright white.

I was following this forum: https://github.com/notro/rpi-firmware/issues/6 but the solutions provided don't seem to work with this different display. I have the image provided from the manufacturer, but I would rather use the standard Raspian image.

[mikertr]

@twkrol Progress!! Thank you for answering questions. My display will inconsistently show boot messages for a short while, eventually start a slow flicker, and ultimately go to just a backlight. I've read that some of the LCD issues can be power-related, but I'm using a 5 volt, 2 amp power supply. Here's the end of my boot log:

[    4.681631] bcm2708_spi 3f204000.spi: DMA channel 2 at address 0xf3007200 wi$
[    4.707234] bcm2708_spi 3f204000.spi: DMA channel 4 at address 0xf3007400 wi$
[    4.795012] bcm2708_spi 3f204000.spi: SPI Controller at 0x3f204000 (irq 80)
[    4.806292] bcm2708_spi 3f204000.spi: SPI Controller running in dma mode
[    4.954272] random: nonblocking pool is initialized
[    5.194456] usbcore: registered new interface driver rtl8192cu
[    6.626059] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    7.021541] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    7.656646] fbtft_device:  SPI devices registered:
[    7.664539] fbtft_device:      spidev spi0.0 500kHz 8 bits mode=0x00
[    7.673889] fbtft_device:      spidev spi0.1 500kHz 8 bits mode=0x00
[    7.683234] fbtft_device:  'fb' Platform devices registered:
[    7.691823] fbtft_device:      bcm2708_fb id=-1 pdata? no
[    7.700047] fbtft_device: Deleting spi0.0
[    7.707968] flexfb spi0.0: fbtft_request_gpios: 'reset' = GPIO25
[    7.716935] flexfb spi0.0: fbtft_request_gpios: 'dc' = GPIO24
[    7.725579] flexfb spi0.0: flexfb_verify_gpios_dc()
[    7.733047] flexfb spi0.0: fbtft_init_display()
[    7.739985] flexfb spi0.0: fbtft_reset()
[    7.866317] flexfb spi0.0: init: write(0xB0) 0x00
[    7.873526] flexfb spi0.0: init: write(0x11)
[    7.880157] flexfb spi0.0: init: mdelay(250)
[    8.136609] flexfb spi0.0: init: write(0x3A) 0x55
[    8.143569] flexfb spi0.0: init: write(0xC2) 0x44
[    8.150435] flexfb spi0.0: init: write(0xC5) 0x00 0x00 0x00 0x00
[    8.158582] flexfb spi0.0: init: write(0xE0) 0x0F 0x1F 0x1C 0x0C 0x0F 0x08 0$
[    8.174224] flexfb spi0.0: init: write(0xE1) 0x0F 0x32 0x2E 0x0B 0x0D 0x05 0$
[    8.190239] flexfb spi0.0: init: write(0xE2) 0x0F 0x32 0x2E 0x0B 0x0D 0x05 0$
[    8.205796] flexfb spi0.0: init: write(0x36) 0x28
[    8.212997] flexfb spi0.0: init: write(0x11)
[    8.219651] flexfb spi0.0: init: write(0x29)
[    8.393497] flexfb spi0.0: Display update: 1793 kB/s (167.182 ms), fps=0 (0.$
[    8.403604] flexfb spi0.0: fbtft_register_backlight()
[    8.411193] flexfb spi0.0: fbtft_register_backlight(): led pin not set, exit$
[    8.519980] graphics fb1: flexfb frame buffer, 480x320, 300 KiB video memory$
[    8.535180] fbtft_device:  GPIOS used by 'flexfb':
[    8.541901] fbtft_device:    'reset' = GPIO25
[    8.548154] fbtft_device:    'dc' = GPIO24
[    8.554114] fbtft_device:  SPI devices registered:
[    8.560762] fbtft_device:      spidev spi0.1 500kHz 8 bits mode=0x00
[    8.568997] fbtft_device:      flexfb spi0.0 16000kHz 8 bits mode=0x00
[   12.394163] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   16.162228] Adding 102396k swap on /var/swap.  Priority:-1 extents:2 across:$

[midnightradio]

I was spending a lot of time with a trouble on waveshare 3.5inch LCD by just following a wrong procedure (http://www.circuitbasics.com/setup-lcd-touchscreen-raspberry-pi/) assuming that it may be the same as "waveshare32b". This was my last shot before returning the troublesome LCD and finally the issue has been resolved. Thanks a lot!

[twkrol]

Great! It's worth noting, that waveshare32b DOESN'T work for SpotPear 3,5 or 4".

[midnightradio]

It was little bit early to yell out a cheer as touch screen is not working.

Though I put following line in /dev/modules, my raspi seems not detecting the touch device.

ads7846_device model=7846 cs=1 gpio_pendown=17  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

Also I tried with "model=7843" following what @jharig23 mentioned, but the same result.

pi@raspberrypi ~ $ sudo modprobe ads7846_device model=7846
FATAL: Module ads7846_device not found.
pi@raspberrypi ~ $ sudo modprobe ads7846_device model=7843
FATAL: Module ads7846_device not found.
pi@raspberrypi ~ $ lsmod
Module                  Size  Used by
ads7846                10632  0 
fbtft_device           34613  0 
flexfb                 14438  2 
fbtft                  34434  2 flexfb,fbtft_device
syscopyarea             3153  1 fbtft
sysfillrect             3584  1 fbtft
sysimgblt               2278  1 fbtft
fb_sys_fops             1565  1 fbtft
snd_bcm2835            21157  0 
snd_pcm                90778  1 snd_bcm2835
snd_seq                61097  0 
snd_seq_device          7209  1 snd_seq
snd_timer              23007  2 snd_pcm,snd_seq
snd                    66285  5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device
spi_bcm2708             6018  0 
evdev                  11000  2 
uio_pdrv_genirq         3666  0 
uio                     9897  1 uio_pdrv_genirq
pi@raspberrypi ~ $ 

[jharig23]

I must agree that this little screen is not so fun. I spoke to soon with my earlier comment, @midnightradio. Did you perhaps try

sudo modprobe ads7846
sudo modprobe ads7846_device model=7846

Maybe you need to load the ads7846 module first?

I can see touch events with evtest, but I'm not able to get x11 to recognize it.

[midnightradio]

Thanks @jharig23 , but...

pi@raspberrypi ~ $ sudo modprobe ads7846
pi@raspberrypi ~ $ sudo modprobe ads7846_device model=7846
FATAL: Module ads7846_device not found.
pi@raspberrypi ~ $ 

Even there's nothing about ads7846 in dmesg.

pi@raspberrypi ~ $ dmesg | grep ads7846

[dollerbill]

The 7 steps that sudobrew listed, are these done from a fresh Raspbian install? Or do you already need to have compiled fbtft?

And will this process work for an Adafruit 3.5" TFT? I have used the AF image and am running into issues, so I would like to try out fbtft

[midnightradio]

@dollerbill In my case, it had done on fresh Raspbian (Feb. version) but I guess the 4th step would make you Pi load up the driver no matter how fresh you Pi is. Just give it a try and let us it works for the device. :-)

[HomeServerPro]

Sorry for my english.

I have Wavefront TFT and this settings. TFT and touchscreen works fine in Raspbian desktop and apps except Python. In Python apps I have inverted X coordinates (Y coordinates works right) and touch area double smaller in both coordinates (looks like 320x240 but screen is 480x320, in diffrent words if I move stylus - cursor moves wiith double speed).

Any help please?

Solved! But don't understand why?

[romanesko]

Thank you! It works just fine But… I'm using JavaFX that outputs directly to the FB and even though the LCD is FB0 according to udev it still doesn't want to display on it.

[djctwo]

I bought this screen for my rPi2 and am completely lost; on top of that new to all of this and linux. Is there an image out there with all of this configuration already compiled where you can just burn it to a sd card and be done with it? I know, lazy right! I just wanna see this screen work and have no idea how to begin.

[championbarca]

I am trying @sudobrew above mentioned 7 steps, but my rasp2 always gets stuck after reboot, whatever i do. Showing black screen and flashing cursor. This is mostly after 2nd step of changing fb0 to fb1. Please guide me in this regard.

[haydockjp]

Thank you for this!

[juhovh]

I got everything (screen and touch input) working pretty smoothly in an hour or two based solely on the information in this thread. If I have time I'll write a small blog post trying to wrap it up, but anyway thank you to everyone involved! Saved a lot of time.

[championbarca]

Hi @juhovh, will you be able to help me in my case? Do you have rasp2 ?

[juhovh]

@vineetmhapsekar unfortunately I do not have rasp2

[DonaldTrump44]

I finally got everything working on my Pi2. The only thing I want to know is if I can use TV screen & touch screen at the same time?

[championbarca]

Hi @tony486, Please help me with steps you followed.

[DonaldTrump44]

@vineetmhapsekar : (For Rpi2 & Waveshare spotpear 3.5 inch screen (A) )

-----Step 1:Enable SPI

sudo raspi-config

----Step2:

sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf

(Change fb0 to fb1)

----Step3:

sudo REPO_URI=https://github.com/notro/rpi-firmware rpi-update sudo reboot

----Step4: use this /etc/modules file (the one from @sudobrew's post doesn't work):

spi-bcm2708

flexfb width=480 height=320 regwidth=16 init=-1,0xb0,0x0,-1,0x11,-2,250,-1,0x3A,0x55,-1,0xC2,0x44,-1,0xC5,0x00,0x00,0x00,0x00,-1,0xE0,0x0F,0x1F,0x1C,0x0C,0x0F,0x08,0x48,0x98,0x37,0x0A,0x13,0x04,0x11,0x0D,0x00,-1,0xE1,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0xE2,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0x36,0x28,-1,0x11,-1,0x29,-3

fbtft_device debug=3 rotate=0 name=flexfb speed=16000000 gpios=reset:25,dc:24

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

-----Step5:

sudo nano /boot/cmdline.txt

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:24,reset:25 fbtft_device.bgr=1 fbtft_device.speed=16000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=0

--------Step6:

Reboot

[championbarca]

Hi @tony486, Thanks for your quick response. I am stuck at Step 3, when i do reboot with HDMI display it goes black and blinking cursor. Do i need to try on LCD?

[DonaldTrump44]

@vineetmhapsekar did you tried on a fresh raspbian install? Try to skip step3 to see if it work, I think the latest raspbian include FBTFT driver

[juhovh]

@tony486 I think step3 should actually be step6...

[juhovh]

In case someone is interested, I wrote a step-by-step blog post of how I configured my screen. You can find it from http://futurice.com/blog/id-like-to-have-some-lcd-on-my-pi

The values @twkrol gave for the screen orientation didn't seem to be totally correct for me. It seems the 3 most significant bits control the screen orientation and acceptable values are: 1, 2, 3, 4. Therefore the correct numbers in hex are: 0x28, 0x48, 0x68, 0x88. Hope this is helpful for someone, at least it was fun for me.

[twkrol]

@juhovh great post on your blog :) explains everything. Must read for everyone running Waveshare LCD.

[juhovh]

Thanks for the comment. I have to take it back a little bit, 0x68 is actually mirrored and 0xE8 was the correct value, so it was 1, 2, 4, 7 after all. The 0x84 value is funny because it looks right, but modifies the colors somehow. I will probably keep playing with these a bit.

[dpeach]

Thank you sudobrew for your steps.

I have the display running on a Raspberry Pi A+. I have not enabled the touchscreen because my use for this device will require that there be no user input, so I haven't even tried to get that working.

[gat45]

hello little m which help fair walk rasbmc I exceed the

  thank you (maybe a picture with xbmc is avaialble)? thank you

[jeeceebee54]

@midnightradio If you always have the message: FATAL: Module ads7846_device not found. You must search about "dtoverlay". https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README

And type one command like this, in the end of /boot/config.txt file:

dtoverlay=ads7846,speed=1000000,penirq=17,swapxy=1

[mruslanhafiz]

Hello guys I've been following this post and managed to turned on Waveshare lcd TFT 3.5" on my raspberry pi. however my touchscreen didn't work and when i'm trying to run this command :

sudo modprobe ads7846_device model=7846 cs=1 speed=2000000 gpio_pendown=25 pressure_max=255 x_plate_ohms=60

it gives me this message : FATAL: Module ads7846_device not found.

according to this post https://github.com/notro/fbtft/issues/260

The latest kernel doesn't have ads7846_device anymore, so i'm trying the solution from @jeeceebee54 and this post

https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README

by @notro and add some dtoverlay on my /boot/config.txt like this :

dtoverlay=ads7846:cs=1,speed=2Mhz,penirq=60,penirq_pull=0,xmin=200,ymin=200,xmax=3900,ymax=3900,pmin=0,pmax=255,xohms=60,swapxy=0

i've reboot my pi but my touch screen still didn't work, and on the boot screen these message shown: [ 8.363826] ads7846: probe of spi0.1 failed with error -22 and [ 12.648999] fbtft_device: SPI devices registered: [ 12.658735] fbtft_device: ads7846 spi0.1 2000kHz 8 bits mode=0x00

please help me

thank you

[jeeceebee54]

Hello,

I think that your parameters are wrong. Try this command, its OK for me:

dtoverlay=ads7846,speed=1000000,penirq=17

penirq is very important. Its the GPIO number use for the touchscreen interrup on the waveshare 3.5.

the others parameters are optionals. You can use: swapxy, xmin, xmax, ymin, ymax for the touch calibration and x,y orientation.

-----Original Message----- From: mruslanhafiz notifications@github.com To: notro/fbtft fbtft@noreply.github.com Cc: jeeceebee54 jcbertrand@md.fitech.fr Date: Sun, 05 Apr 2015 00:01:50 -0700 Subject: Re: [fbtft] Support for Waveshare 3.5 Spotpear (#215)

Hello guys I've been following this post and managed to turned on Waveshare lcd TFT 3.5" on my raspberry pi. however my touchscreen didn't work and when i'm trying to run this command : sudo modprobe ads7846_device model=7846 cs=1 speed=2000000 gpio_pendown=25 pressure_max=255 x_plate_ohms=60 it gives me this message : FATAL: Module ads7846_device not found. according to this post

260 [https://github.com/notro/fbtft/issues/260]

The latest kernel doesn't have ads7846_device anymore, so i'm trying the solution from @jeeceebee54 [https://github.com/jeeceebee54] and this post https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README [https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README] by @notro [https://github.com/notro] and add some dtoverlay on my /boot/config.txt like this : dtoverlay=ads7846:cs=1,speed=2Mhz,penirq=60,penirq_pull=0,xmin=200,ymin=200,xmax=3900,ymax=3900,pmin=0,pmax=255,xohms=60,swapxy=0 i've reboot my pi but my touch screen still didn't work, and on the boot screen these message shown: [ 8.363826] ads7846: probe of spi0.1 failed with error -22 and [ 12.648999] fbtft_device: SPI devices registered: [ 12.658735] fbtft_device: ads7846 spi0.1 2000kHz 8 bits mode=0x00 please help me thank you — Reply to this email directly or view it on GitHub [https://github.com/notro/fbtft/issues/215#issuecomment-89729502].

---

Ce message a été vérifié par l'antivirus de MDaemon.

Par précaution, n'ouvrez pas de pièces jointes de correspondants inconnus.

---

---

Ce message a été vérifié par l'antivirus de MDaemon.

Par précaution, n'ouvrez pas de pièces jointes de correspondants inconnus.

---

[mruslanhafiz]

Hello @jeeceebee54. I have replaced my dtoverlay settings in /boot/config.txt with yours and my touchscreen is working now. thank you so much

but it looks like i need to do some calibration because the touch feature was not very accurate on my screen. after the setting are you using some calibrator such as xinput_calibrator or just modify the dtoverlay parameters to calibrate the touch to be more accurate?

[jeeceebee54]

Use a calibrator link xinput_calibrator And follow the instructions. Normally all must be OK. Bye

-------- Message d'origine --------

De : mruslanhafiz notifications@github.com

Date :05/04/2015 10:15 (GMT+01:00)

A : notro/fbtft fbtft@noreply.github.com

Cc : jeeceebee54 jcbertrand@md.fitech.fr

Objet : Re: [fbtft] Support for Waveshare 3.5 Spotpear (#215)

Hello @jeeceebee54. I have replaced my dtoverlay settings in /boot/config.txt with yours and my touchscreen is working now. thank you so much but it looks like i need to do some calibration because the touch feature was not very accurate on my screen. after the setting are you using some calibrator such as xinput_calibrator or just modify the dtoverlay parameters to calibrate the touch to be more accurate? — Reply to this email directly or view it on GitHub. --- Ce message a été vérifié par l'antivirus de MDaemon. Par précaution, n'ouvrez pas de pièces jointes de correspondants inconnus. --- --- Ce message a été vérifié par l'antivirus de MDaemon. Par précaution, n'ouvrez pas de pièces jointes de correspondants inconnus. ---

[midnightradio]

@jeeceebee54 Thanks for providing solution, it seems like the solution though I cannot try right now having only the board with no other peripheral devices. However, as you suggested, I just sshed and put the line at the end of the file and rebooted, but still got the message, "FATAL: Module ads7846_device not found.", for running the command, "sudo modprobe ads7846_device model=7846".

I should try with LCD screen by touching it, which I can't right now. Maybe it will work regardless of the error message, hopefully.

[moerphin]

Hi!

First of all, happy easter!

Somebody can help me? I have a rpi B model (one of the firsts, with 256MB memory), and a Waveshare Spotpear 3.2" (v3) touchscreen. After couple of days finally I can see the fb device (/dev/fb1), but I have no screen on the display, it only has white light. Some info:

#ls -al /dev/fb*
crw-rw---T 1 root video 29, 0 Jan  1  1970 /dev/fb0
crw-rw---T 1 root video 29, 1 Apr  6 10:24 /dev/fb1

#cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 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

#cat /usr/share/X11/xorg.conf.d/99-fbturbo.conf
Section "Device"
        Identifier      "Allwinner A10/A13 FBDEV"
        Driver          "fbturbo"
        Option          "fbdev" "/dev/fb1"

    Option          "SwapbuffersWait" "true"
EndSection

#cat /etc/modules
snd-bcm2835
spi-bcm2708
fbtft_device name=waveshare32b gpios=dc:22,reset:27 speed=48000000

waveshare32b 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,0x36,0x28,-1,0x3A,0x55,-1,0xB1,0x00,0x18,-1,0xB6,0x08,0x82,0x27,-1,0xF2,0x00,-1,0x26,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,0x11,-2,120,-1,0x29,-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

When I start X (startx) I got an error: _FATAL: Module g2d23 not found.

Can you help me?

[MolarAmbiguity]

@moerphin: try this issue: https://github.com/notro/rpi-firmware/issues/6

[maty87]

Hi I new to pi I got a wave share spot pear 4 led been lookin around not sure what guide to follow running pi b+ with noobs dual install of raspbian and xbmc i can get the display to work with provided image but wanna use my pi supplied image

[MolarAmbiguity]

@maty87: do the instructions from either of these links work?

https://github.com/notro/fbtft/issues/253

http://raspberrypi.stackexchange.com/questions/27714/how-to-install-waveshare-spotpear-4-inch-lcd-in-raspberrypi-2

If you can't get it working, I would suggest making a new issue. Make sure to follow any instructions carefully.

[maty87]

Hi when doin the 1st step Touchscreen Setup and Configuration

First we need to configure the fbturbo video driver to output the display of the Raspberry Pi to the SPI bus instead of the HDMI bus. At the command prompt, enter: sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf I get it come up but its empty nothing in it atall

[maty87]

I followed these steps but on reboot it just hung on the following screen on boot

rebuilding rasbian now all I know about my screen is as it says on back 4INCH RPI LCD(A) WAVESHARE SPOTPARE

[maty87]

I know the screen works with the supplied image but don't wanna use theres cus i wanna use mine so i can chose to boot rasp or openelec would it be possibleto give someone my image supplied and them make an install? or give me an easy to follow guide

[MolarAmbiguity]

When you did sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf were sure you were using the pi? You either need to be using a keyboard and screen connected to it, or connected via ssh.

Sadly there isn't currently an easy guide to setup your screen, maybe you could update the wiki once you've figured it out?

Also please make a new issue for this, especially since you are trying to post in two issues at the same time. This issue is already crazily long.

[maty87]

my set up is hdmi screen connected with keyboard with track ball built in for mouse (not that that matters lol) connected to router and my pi screen placed direct to board

[maty87]

what is ssh?

[MolarAmbiguity]

ssh is a way to connect to a computer over a network. You only get command line access though. On linux you just do ssh user@ip. On windows you will need extra programs to use ssh.

Anyway, so when you open up the terminal from the raspi desktop and type sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf you get an empty file.

Also please make another issue, as per my previous message. I would also suggest reading (I know it's really long) through the entirety of this issue.

[sazp96]

Hello folks, I'm trying to use this screen with an Arduino and will be porting the controller libraries. But first, I need to know what controller that is :)

@twkrol and @jeeceebee54, do you know what is the LCD controller used by this Waveshare LCD?

[kenei17]

THANKS to all the guys who worked on this!!! Come to La Rochelle, the beer is for me ^^

@juhovh: Your post on the blog ( http://futurice.com/blog/id-like-to-have-some-lcd-on-my-pi) is THE guide to follow. I was stuck with the install dvd in the package with the screen, he was full scratched... i follow lots of "how-to guide" on the web, all comes to an end...2 days during... Then i found this post, and...

Taaa daaaaaaaa !!! Finally works!!!

Just have to figure how to switch lcd to hdmi now.

Peace.

[bezeefly]

Thanks to all you guys that shared valuable information on this page.

I followed the step-by-step instructions guide on @juhovh blog post (http://futurice.com/blog/id-like-to-have-some-lcd-on-my-pi). It worked perfectly!

I installed it on a Raspberry Pi 2, with Raspbian stand-alone image (release date 2015-05-05), and Waveshare Spotpear 3.5 inch (A) LCD Touch Screen.

[mjimack360omg]

Hey Notro can you take a look at my proplem at https://github.com/notro/fbtft/issues/290#issuecomment-113055931?

[pidgeonman]

Hi guys. I followed all advice here and got my display working, so thanks a lot!

I've one question now: is it posible to dim or turn off the backlight or the display altogether after a certain period of inactivity? I'm planning to use this as a home server display, so it should be on forever.

Thanks!

[syl01]

Help Needed... I purchase Waveshare 3.5 Spotpear a week ago and I have done everything exactly all the settings but somehow my touch screen just not working. Any other suggestion ? Can anyone help me to debug ? Thank you... :-)

Update firmware with: sudo REPO_URI=https://github.com/notro/rpi-firmware rpi-update

Enable SPI in raspi-config.

/etc/modules: flexfb nobacklight regwidth=16 init=-1,0xb0,0x0,-1,0x11,-2,250,-1,0x3A,0x55,-1,0xC2,0x44,-1,0xC5,0x00,0x00,0x00,0x00,-1,0xE0,0x0F,0x1F,0x1C,0x0C,0x0F,0x08,0x48,0x98,0x37,0x0A,0x13,0x04,0x11,0x0D,0x00,-1,0xE1,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0xE2,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0x36,0x28,-1,0x11,-1,0x29,-3 width=480 height=320 fbtft_device name=flexfb speed=16000000 gpios=reset:25,dc:24

/boot/cmdline.txt: add: fbcon=map:1 fbcon=font:ProFont6x11

/usr/share/X11/xorg.conf.d/99-fbturbo.conf: change fb0 to fb1

/boot/config.txt add line: dtoverlay=ads7846,speed=500000,penirq=17,swapxy=1