Raspberry Pi 2 - Neosec TFT 3.5"

5 posts
by jaymeh » Sat Feb 14, 2015 10:51 pm
Hi All,

I recently purchased a touch screen Neosec 3.5" screen for my Raspberry Pi 2. I have been trying to get it to run properly however everything I seem to be trying isn't working well. The screen came with a disc including an image for the kernel with the drivers so this was the first thing I tried, the screen was just white.

I wondered if this was related to the fact that the kernal was built for a B+ model instead of the 2. I then had a look into fbtft and found a guide left by another member of the forums however they were using a different screen.


Upon following this guide under step 4 I changed the device name in the two places mentioned to tinylcd35 however this still seems to cause the screen to be white. I am unsure as to where I can go from here and would be very grateful for any suggestions.

Many thanks,
Posts: 3
Joined: Sat Feb 09, 2013 7:03 pm
by tony486 » Mon Feb 16, 2015 2:43 pm
Did you find a solution? I have the same problem, it seems that the images aren't working with the rpi2
Posts: 6
Joined: Sun Feb 15, 2015 5:01 pm
by jaymeh » Tue Feb 17, 2015 9:54 pm
I am still looking I am afraid. Resorting to trying an A+ model to see if I have any luck with that
Posts: 3
Joined: Sat Feb 09, 2013 7:03 pm
by huffy2404 » Thu Feb 19, 2015 4:23 am
Here is what I did to get mine to work on the Pi 2. This is all taken from the notro/fbtft github wiki located here: https://github.com/notro/fbtft/wiki

Get dtc compiler with overlay support:
Code: Select all
wget -c https://raw.githubusercontent.com/RobertCNelson/tools/master/pkgs/dtc.sh
chmod +x dtc.sh

Get the tinylcd35 overlay source:
Code: Select all
wget -c https://raw.githubusercontent.com/notro/fbtft/master/dts/overlays/rpi/tinylcd35-overlay.dts

Note that I am using the NeoSec 3.5" TFT Display + Touch Screen. This version does not include the touch pad or any extra buttons. I believe the tinylcd35 overlay source is set up for the version of the screen that includes the touch pad. In order to get the touch screen to work I had to modify the overlay source file as follows:

On line 88 change:
Code: Select all
interrupts = <3 2>; /* high-to-low edge triggered */
Code: Select all
interrupts = <5 2>; /* high-to-low edge triggered */

and on line 90 change:
Code: Select all
pendown-gpio = <&gpio 3 0>;
Code: Select all
pendown-gpio = <&gpio 5 0>;

From what I understand this is just needs to reflect the GPIO pin that is connected to the screen's PENIRQ.

Compile the overlay and save it in /boot/overlays/:
Code: Select all
sudo dtc -@ -I dts -O dtb -o /boot/overlays/tinylcd35-overlay.dtb tinylcd35-overlay.dts

Add the following to your /boot/config.txt file:
Code: Select all
# added for tinylcd 3.5 inch

Install a custom Xorg config:
Code: Select all
sudo mkdir -p /etc/X11/xorg.conf.d/
sudo wget https://gist.github.com/notro/63fc8f563b5f85010d30/raw/5e68d6c6df9471f973b3da5305e73a5017590a69/fbtft.conf -O /etc/X11/xorg.conf.d/fbtft.conf

Update the Pi firmware:
Code: Select all
sudo REPO_URI=https://github.com/notro/rpi-firmware rpi-update
sudo reboot

The screen should be black at this point. You can test by running:
Code: Select all
FRAMEBUFFER=/dev/fb1 startx
Code: Select all
con2fbmap 1 1

You can find information regarding calibration here: https://github.com/notro/fbtft/wiki/FBTFT-on-Raspian

I have only completed the tslib portion since that is all I intend to use, but there is info for X there as well.

I have successfully tested this on a Raspberry Pi 2 running both wheezy and jessie.

I hope this helps, but as usual, YMMV.
Posts: 5
Joined: Mon Feb 16, 2015 2:18 am
by tinylcd » Fri Feb 20, 2015 12:37 pm

Neosec 3.5 tft are been tested on Raspberry Pi 2

and they are working fine

incase if any one need guidance/support

do contact us

Posts: 214
Joined: Sat Oct 26, 2013 4:07 am