3.5 inch 320x480 IPS Capacitive Touch Screen LCD Module SPI Serial ST7796U Driver for Arduino R3/Mega2560

This 4.0-inch display is a fantastic option, especially if you're looking for something larger than the usual 2.5" to 3.5" screens. The 320x480 resolution provides sharp visuals, and the capacitive touch (FT6336U) is highly responsive and accurate with no calibration needed. Key Highlights: ✅ 4-wire SPI for the ST7796 display and I2C for the FT6336U capacitive touch—a great setup that ensures fast refresh rates and smooth performance. ✅ Use TFT-eSPI library support for video, though some customization is needed. ✅ FT6336U library for touch, which works flawlessly. ✅ 14-line ribbon connector with labeled pins—a fantastic inclusion! My dev board had all the display pins lined up but not the touch, so I had to use the ribbon to connect the touch functionality while still mounting the display. The fact that they included the ribbon cable is a huge plus. ✅ SD card slot (though I haven't tested it). If you're looking for the best 4-wire SPI screen with great refresh rates, this is the one to get. Highly recommended for anyone needing a solid display. Comes with documentation (better than most), but is still confusing. Just follow the advice of the reviews. 4.5 stars (rounded up to 5). Not perfect, but I haven't seen any better SPI displays.

This version of the Hosyund 4.0in 320x480 display fixes the 2 things I disliked about the original version (red PCB) - the additional header used for accessing the SD card, and using an SD card instead of a microSD card. This board is pin compatible with the old one on header J2 for the display and SPI (pins VCC through SDO(MISO)). I don't use touchscreen normally, so I can't confirm they are the same. Instead of having a separate SPI header for the SD card like the old version, this board adds the microSD chip select pin (SD_CS) to the main header, eliminating the 4 pin header for the SD card. This version uses a microSD card instead of an SD card. This saves a lot of space around the board when packaging it in a project. The microSD card is under the board, on the old version the SD card stuck out about 1/2" outside the edge of the board and took up a lot more space. Like the red board version, the display is clear, bright, and easy to read in bright environments. This display can be tricky to get set up. I use the Bodmer TFT_eSPI library. Search for that, there are videos and documentation available to help you get started. Great display, great price!

I was impressed with the overall quality of the unit. The screen had good color, decent brightness, and the touchscreen seems accurate. It was easy to set up from the seller's website, Arduino libraries were easy to find and install. Unfortunately, I'll be returning the screen due to a faulty card reader. The display and touch still work, but I'm concerned with longevity, so I'll be getting something a little better.

Support is non existent, contrary to the statement in the description. It does work with UNO R3, but most of the examples exceed the flash memory capacity of the UNO, so they will not compile and upload. I tried to also use with an UNO R4, but the libraries are not compatible with it. It also works on an UNO Leonardo, but had the same memory limits as a UNO R3. Going to give it a try with an ESP-32. If that doesn't work, it will be sent back. I have Googled for a solution to the libraries issue on the R4, but nothing I've found will work. The warning about the wiring library is the issue and there does not appear to be a fix for it with this Display.

Nice crisp display, better than I expected, especially for that price. As an old guy who really appreciates having a bigger screen to work with on my little projects, this gets my top recommendations.

This is for the 4" 320x480 capacitive touch display with ST7796s. I first tested out the display itself, and found the TFT_eSPI to work well. For reading the touchscreen, I only really tested position and haven't looked into gestures yet, but I found that both RAK14014-FT6336U and the Arduino-FT6336U libraries worked equally well for what I tested. The RAK library actually used up a bit more program memory, about 240 bytes more, so if your processor is small in that department, might consider that. Here are some tidbits that I needed to learn through experimentation that might help others get running quicker: 1) SPI interface to the display runs well at 80MHz. I used ESP32 DEV, so no problem. 2) On ESP32, use default SPI pins in order to use hardware driver, which is fastest. 3) On I2C interface for touchpad, use default pins for SDA and SCLK. Easiest way to check which pins these are is to print out SDA and SCLK to the serial port. 4) The FT6336U interrupt pin is mostly useful to wake up the processor while in a sleep state. During normal operation, interrupts constantly come in and cannot easily be used to determine when a touch has happened. Need to poll the TD_STATUS register to see if non-zero and not use the interrupt line in normal operation. 5) TFT_eSPI is a very inclusive library, but you will need to alter it unless you have a board and pin setup combo that matches one of the many examples. This is not documented well. I recommend taking the SetupX_Template.h file in the User_Setups folder, configure it according to the comments in the file, save it as a new filename, and then you only need to change a single line in the standard library files from that point onwards, even if this library gets updated in the future. Then you can either copy this custom name file to the User_Setup.h file and overwrite the original. Or, everytime a new library version comes out, just edit the User_Setup_Select.h file to comment out the User_Setup.h and add a line to use the new file you created. Both ways work well. But expect that you will need to do this bit of customization to the library. 6) I2C address for the touchpad is as in the FT6336U library, address 0x38. You can also find example scanner sketches online which will confirm your board's touchpad I2C address. Overall, the display is a great value - nice and bright, large, and with a capacitive touchscreen that pretty much works out of the box without calibration.

Using it with Mega2560. The display is crisp and clear. The website for this product has some of the best documentation I've seen. Physical drawings, libraries, example programs, connection diagrams, technical specs, etc. Very happy with it but a couple of little issues to get it going... Issue #1: the demo programs declare either my_lcd or mylcd. Either spelling is fine, but they try to use both in the same sketch causing errors at compile. Edit the demo programs so you have either my_lcd or mylcd, not both. Issue #2 In each demo there are lines similar to this at the beginning. //LCDWIKI_SPI mylcd(130,130,10,9,8,A3); . You need to "uncomment" (remove the two slashes at the beginning of the line) ONE of those lines. For the 4.0 inch, I used the line where it says the module is not known and edited it to LCDWIKI_SPI mylcd(320,480,10,9,8,A3); Issue #3 The line in issue #2 assigns the LED control to pin A3 (assuming you are setting up for a Mega2560) but the library needs a uint_8 (8 bit unsigned integer) and does not understand what A3 means. If you follow the wiring connections in the file 4.0inch_SPI_MSP4030_MSP4031_UNO_Mega2560_Demo_Instructions_EN.pdf that comes with their demo package the LED control is connected to pin 5, so edit the line to read LCDWIKI_SPI mylcd(320,480,10,9,8,5); and everything works great. Issue #4 The Demo Instructions list Mega2560 pins A4 and A5 for the touch screen I2C connections, These are pin numbers for Arduino Uno and won't work on the 2560. Connect CTP_SCL to pin 21 and CTP_SDA to pin 20 on the Mega2560

Using this on a teensy 4.1. Had a few problems at first: ST7796 driver didn't work, so used Arduino_ILI9341 - works fine! Runs up to 110mhz spi on my teensy with good clean soldering and short cables. FT6336U didn't work at first - bad driver code from github (aselectroworks/Arduino-FT6336U - don't use this doesn't work - has a 10ms delay in the readbyte code e.t.c. lol), so cobbled together my own from github "strange-v/FT6X36" driver. Had trouble with that as well - had to delay 300ms on power up before using the FT - else it would't init at all. Also had problems with the FT cutting out while SPI display was updating - All these problems were caused because my CPT reset pin wasn't being used - did not connect it and so it was floating and SPI triggered it - just tie it to VCC if not using it. You can also tie the LCD reset to GND and CS to VCC with a 4.7k resistor if your only using 1 display. Now everything is working great - it's a great display with a nice slick and easy CPT touch interface! With LVGL I get 30fps no problem without using the fast t4 code library.

work as expected

Was going crazy trying to figure out why I couldn’t get this thing going. This thing has the newer ILI19488 chipset, eSPI_TFT has a profile for it. Follow the pin mapping in the profile preset, it works. To the seller: Seriously, update the listing, you wasted too much of my time. Screen looks great, documentation exists, the touchscreen seems to be hard to deal with, though i may have gotten a bad unit

Fonctionne parfaitement, toucher sensible et parfaitement opérationnel image parfaite