Will a UNO R3 2.8" TFT touch screen with SC card socket work with the Raspberry Pi 2 B?
Will a UNO R3 2.8" TFT touch screen with SC card socket work with the Raspberry Pi 2 B?
So I looked at the libraries and the link etc, while there is some confusion as to the exact chip on the display, one thing is clear
Well 2 actuallly
1. it does apear to be working in 8 bit mode as I suspected, if you initialize the display with the assumption it is working in 16bit mode then of course it will fail, if you look at the libraries and get right down into the WriteCommand or WriteData (This is all modified from Adafruit and other libraries,) it is sending each 16 bit command twice over the 8 bits doing a shift of course for the upper bits. this is no slower than the AVR using 16bits (Assuming it even had 16bits available) so not really an issue, though on all but the smallest displays this will be slow, the PI has more than enough pins to replicate this, the other pins in use are pretty standard, a registry select to determin if your writing a command or data, a WR pin for guess what 
, a reset pi and the chip select. this is all pretty basic and common
2. The touch is not too great in that it seems to be re-using pins from the Data to read the touch screen, this will work but adds a little complexity to the library, using the TSC2046 would have been nicer, but it still should work ok, just lower resolution
to work with the PI you will need to perform the pin manipulation as seperate pins as im not aware of a group pin command, the Touch will require the addition of a touch controller if even possible as the board seems to be wiring the touch and some data LCD pins together, maybe hacking the board could seperate them but if your going to all that trouble then simply but a display already for the PI or atleast one using a 2046 touch controller and SPI based LCD interface
see my latest post for example (This is windows 10 for IoT but the principals are the same, and there is a schematic for the interface int he comments) Raspberry Pi 2, 480*320 Colour LCD Displays on a Windows 10 IoT and a really cool demo
The comments on Amazon about FAKE may well be FAKE in them selves as most controller chips can work in 8, 16, 18, and even 24bit modes as well as SPI or I2C in some cases, its all about knowing what your doing with the chip, the people crying out FAKE on amazon on the face of it do not apear to know what their talking about and understand exactly what you can do with these chips, they probably grabed the first driver they found for the chip and it failed because it is more popular to use 16bit or a SPI interface. the link to my post above is an example of a varient where the chip is operating in 16bit paralel mode but the micro is talking to it via a SPI bus and a couple of shift registers (This approach will also work great for an AVR too, even better than the way the posters panel is configured
So I looked at the libraries and the link etc, while there is some confusion as to the exact chip on the display, one thing is clear
Well 2 actuallly
1. it does apear to be working in 8 bit mode as I suspected, if you initialize the display with the assumption it is working in 16bit mode then of course it will fail, if you look at the libraries and get right down into the WriteCommand or WriteData (This is all modified from Adafruit and other libraries,) it is sending each 16 bit command twice over the 8 bits doing a shift of course for the upper bits. this is no slower than the AVR using 16bits (Assuming it even had 16bits available) so not really an issue, though on all but the smallest displays this will be slow, the PI has more than enough pins to replicate this, the other pins in use are pretty standard, a registry select to determin if your writing a command or data, a WR pin for guess what , a reset pi and the chip select. this is all pretty basic and common
2. The touch is not too great in that it seems to be re-using pins from the Data to read the touch screen, this will work but adds a little complexity to the library, using the TSC2046 would have been nicer, but it still should work ok, just lower resolution
to work with the PI you will need to perform the pin manipulation as seperate pins as im not aware of a group pin command, the Touch will require the addition of a touch controller if even possible as the board seems to be wiring the touch and some data LCD pins together, maybe hacking the board could seperate them but if your going to all that trouble then simply but a display already for the PI or atleast one using a 2046 touch controller and SPI based LCD interface
see my latest post for example (This is windows 10 for IoT but the principals are the same, and there is a schematic for the interface int he comments) Raspberry Pi 2, 480*320 Colour LCD Displays on a Windows 10 IoT and a really cool demo
The comments on Amazon about FAKE may well be FAKE in them selves as most controller chips can work in 8, 16, 18, and even 24bit modes as well as SPI or I2C in some cases, its all about knowing what your doing with the chip, the people crying out FAKE on amazon on the face of it do not apear to know what their talking about and understand exactly what you can do with these chips, they probably grabed the first driver they found for the chip and it failed because it is more popular to use 16bit or a SPI interface. the link to my post above is an example of a varient where the chip is operating in 16bit paralel mode but the micro is talking to it via a SPI bus and a couple of shift registers (This approach will also work great for an AVR too, even better than the way the posters panel is configured
