retropie for tft display quotation

OK so we have proven the screen works, we need to make things more interesting. Firstly, you might have noticed that if you were to restart the pi, you will need to type your modprobe line in again to restart the screen. now this is no fun for a tiny handheld, so lets make the screen work every time.

You need to add the spi line, so that we are sure the connection port is ready for use, and then the tft device starts the screen. but we need to add in all of those extra settings that we had to type before. there is a place for this and it is another file. type this

now try restarting the pi (I normally type sudo init 6) and let the pi restart. Fingers crossed your screen will light during the reboot process. If not, check your files for typo"s, and check dmesg for any errors.

Ok after days of trying to get this 1.8" spi tft waveshare controller ST7735S screen to work iv had nothing but headache .iv beeing reading so many forums and post that im going mad.

Luckily, I finally got the chance to test your test for real today. Man, I absolutely ADORE this theme. It"s in my top 3 favorite themes as of yet. Can"t wait to see it appear in the official RetroPie repo! It looks unbelievable on my TFT. Weird detail, but I like how vibrant the grid in the background looks. It"s much more noticeable than the grid in your standard CRT theme (even when connected to HDMI), in comparison. It"s a shame you"re missing a few systems in there, like the 32x, dreamcast, N64 and DOS. Since there is no text, it"s hard to pick the right system if they"re missing ;)

Edit: last thing I noticed, my boxarts don"t seem to be re-aligned in z (the suggestion you implemented), but it does re-align the videos. Is the re-alignment for videos and screenshots only, or is this a bug?

This LCD its a clone of the Waveshare 3.5 and we can use the same drivers. But all guides on various forums are made on a fresh Raspian OS install. This guide is for install correctly this LCD on a fresh install of RETROPIE, actually the 4.0.2. Here we go:

With the 4.0.2 u dont need to expand file sistem because this last version will do it for u at the first boot! U just have to setup a gamepad, check your IP and force the audio in 3.5mm jack

(this is very important because most guide are for 3.2 inch so if u have the waveshare 3.2 u must exchange the word "waveshare35a " in "waveshare32b" but no one say that xD)

Thanks for all in advance and i hope my guide will be usefull. U can see this guide on my Youtube channel. If u found a solution about the speed u can comment there on my channel too and here XD

It seems to be a clone one. I don"t have the drivers. I have tested a lot of drivers but i cannot get Retropie to show up in the screen. Only the linux boot up and text console.

@davej the few i have found on aliexpress have pinouts for the display. The all seem to be pretty similar with the SPI and DPI pins available, normally with a few extras for touch

Going by the pinout you linked to, it has a 16 bit MCU interface rather than a DPI one. DPI uses things like VSYNC, HSYNC and DOTCLOCK. The RD, /WR and RS labels in the pinout indicate the MCU interface. The existing driver copes with outputting to an MCU interface (it calls it parallel) but the ILI3941 driver assumes SPI. I"m not familiar with the fbtft driver though so can"t be much help there.

In case you haven"t realised, I"ve been playing with a ILI9341 screen for a microcontroller project. The microcontroller doesn"t have enough memory for a frame buffer so I can"t even use the fbtft driver for inspiration. Updating the screen is a real pain - particularly drawing diagonal lines.

Yes, you can put retropie on a jessie install, but it still won"t get your tft working with retropie, it won"t output to the tft. You need to mirror the framebuffer for that.

With the latest kernels it"s a simple setup to get retropie up and running, provided there is a dt overlay for your tft controller. The adafruit guide works for their own pitft screens and all those other cheap tfts with the same controllers, although they can easily use dt overlays which are already built into the latest kernels. It"s not a good idea to follow their guide. For reasons best known to adafruit, they lock you in to a proprietary bootloader that you can"t ever update/upgrade without killing your setup. (they might have updated their guide now.)

With that being said, luckily your waveshare 32b tft has an overlay written for it, but it"s not provided in the install. You"ll have to get it copied over. I know there are a lot of outdated and confusing guides scattered all over, and how frustrating it can be to try getting one of these tfts working with retropie, so here"s how to get your display set:

So i"ve found this screen on Amazon for a decent price but im unsure if it"ll work with Retropie. According to the page it says drivers are only available for Raspian. So my question is will Raspian drivers work on Retropie? Also, could I use this on a Raspberry Pi Zero W? Thanks.

Hello!! i"m a new user of retropie. I got one raspberry pi3 model B with 32GB micro sd. I got one 5v 2.5A power supply adapter. I have retropie 4.3 made from a Pre made SD Image on RetroPie website. I also have one snes usb controler and one 3.5 Inch 320 X 480 TFT LCD Display Touch Board For Raspberry Pi 2 Raspberry Pi 3 Model B. I have made the setup of retropie and download some roms. In my tv all work perfect!! I follow this instructions and i setup my screen:

The best way is to buy a new screen that is bigger. Else you could try my Viper frontend, which is in works currently. Even i was unhappy with the performance of ES on smaller screens. Here are some of the photos of my frontend. The screen is 320x240 @ 2.2inch.

I used a SainSmart 3.2" TFT LCD Module touch screen display. I believe it"s a re-badge or clone of the WaveShare32 TFT touch screen display. I got it from my local Micro Center.

First I disconnected the flex cable and separated the driver board from the actual TFT display. They"re held together with double sided mounting tape, so that part was easy.

Then I used a dremel tool to cut right along the 4 slim tactile button switches on the side of the driver board. This both resized the width of the board to the same width as the display as well as removed the buttons.

Then I soldered wires from the appropriate pinouts directly to the GPIO on pi zero based on the pinout specs available on the page linked above. The manual linked on the same page also has more pinout details. I put electrical tape on the opposite side of the pin holes on the driver board to prevent any contact with the back of the TFT display.

Lastly, I removed the mounting tape, reattached the driver board to the back of the TFT display using double sided masking tape to reduce the thickness of the display, and reconnected the flex cable.

Drivers are included in raspbian jessie which makes enabling the display so much easier. You simply have to place the parameters below into the config.txt file in the boot folder.

The first set of parameters setup the display resolution. The second to last parameter enables SPI. The last parameter specifies the hardware overlay for the display so the correct kernel modules are loaded along with maxing out the speed and frames per second for the display. I also had to specify rotating the display 270 degrees since I have the display turned around for shorter wiring between the pi zero and the display in the GBA case. More info on the software side of things can be found here.

Since The SainSmart 3.2" TFT LCD Module has a resistive touch screen , I highly recommend you also blacklist the ads7846 touch input kernel module. Otherwise, the kernel will get continuous interrupts from any pressure between the touch screen and the back of the front of the GBA which will affect both input and game performance.

Had access to logic analyzer, and also found out what other sources have documented, that sending each byte (8 bits) has an extra 1 bit idle time overhead on the bus when DMA is not used (which is not possible to be used in this update method), meaning that overall throughput is then a factor of 8/9 less, translating to theoretical maximum of 59.26Mbit/sec. In practice I find that the maximum I"m able to achieve is around 50Mbit/sec. The difference seems to be caused by that whenever a new display command is sent, there"s an around one byte long stall to wait for the SPI FIFO to flush. Not too bad though, simpler games run well at 60fps progressive, and in the more complex ones the worst case performance was in Sonic the Hedgehog, which updated at 74fps interlaced at worst, i.e. the content updates at 60fps, where ~14 frames per second are progressive, and ~46 frames per second revert to interlaced.

I am making a Pi Zero W GBA and have had much trouble finding a proper screen for the project. I need a screen 2.8"-3.5" it needs to be powered by the Pi. Otherwise I will have to use the same battery that I will use for the Pi (haven"t started looking for this yet) and just modify the power from it to the screen to make sure it gets the correct amount, I really don"t want to do it this way but I will if necessary.

I don"t know whether or not to connect the display to the HDMI (I will solder it if I use the HDMI option) or via the GPIO pins, I would like to know the specifics of using the GPIO pins for it (like will it look okay for playing GBA games, color depth and resolution wise? ).

I have a brand new working GBA which I plan to use the shell/case and part of the board (the part for the buttons) unless I decide to send off and have custom PCBs made for that, I"m still thinking about this. I"m planning on using the Pi Zero W for it"s size and wireless capability (I plan on keeping it inside the gba at all times).

I don"t want to hijack @moosepr"s post with me trying to figure out this display, but can someone get me some tips on what to check for on why my display isn"t working?

I tried to use this blog post to wire it up. The pins aren"t labeled exactly the same as the Adafruit display, but I think I have them connected properly.

if i remember right, you need to go into the raspiconfig, and enable spi, disable overscan, and enable device tree, then you should be able to run the command "sudo modprobe fbtft_device pitft22" to actually get the screen active (the backlight should light). You can test it with the command "con2fbmap 1 1" which should pop your terminal session onto the tft screen (run "con2fbmap 1 0" to get it back)

I"ve tried Googling that error and I"ve not found anything helpful, so if anyone has any insight or can point me to somewhere with some good troubleshooting I"d really appreciate it. I may have it hooked up wrong (very possible) or I have to run a command/install something (very possible) or my display is a dud (I have no way to know).

※Price Increase NotificationThe TFT glass cell makers such as Tianma,Hanstar,BOE,Innolux has reduced or stopped the production of small and medium-sized tft glass cell from August-2020 due to the low profit and focus on the size of LCD TV,Tablet PC and Smart Phone .It results the glass cell price in the market is extremely high,and the same situation happens in IC industry.We deeply regret that rapidly rising costs for glass cell and controller IC necessitate our raising the price of tft display.We have made every attempt to avoid the increase, we could accept no profit from the beginning,but the price is going up frequently ,we"re now losing a lot of money. We have no choice if we want to survive. There is no certain answer for when the price would go back to the normal.We guess it will take at least 6 months until these glass cell and semiconductor manufacturing companies recover the production schedule. (Mar-03-2021)

All the accessories listed below tier pricing need to pay.We won"t deliver until you select. Power adaptor should be 5V/2000mA in output and center pin for positive voltage and the outer shield for negative voltage .The temperature for controller RTD2660 would increase during working.That"s normal phenomenon,not quality problem.

ER-TFTV043A1-7 is 800x480 dots 4.3" color tft lcd module display full viewing angle with small HDMI signal driver board,optional 4-wire resistive touch panel with USB driver board and cable, optional capacitive touch panel with USB controller board and cable, optional remote control,superior display quality,super wide view angle.It can be used in any embedded systems,car,industrial device,security and hand-held equipment which requires display in high quality and colorful video. It"s also ideal for Raspberry PI by HDMI.

Note: AndrewFromMelbourne/raspidmx has been replaced with bverc/raspidmx due to added features required by retropie-status-overlay. Will be changed back pending pull request.

Understanding that many people have problems configuring their Kuman TFT display on the Raspberry Pi together with RetroPie, I have decided to make this step-by-step of how to install the Kuman TFT 3.5" display which you can connect directly to the GPIO ports of the Raspberry Pi and run your applications. A lot of people have been buying this Kuman display from Amazon and other online markets for its economical price but it is not an easy display to install for certain applications, compared to other displays that come with integrated HDMI ports that will surely be a lot easier to manipulate and start working. If you want to see original post, clickhere.

The previous command will open the RetroPie configuration file where in the end you have to look for something like SPEED and FPS and change the values to something like:dtoverlay=tft35a,speed=62000000,fps=40

While googling for any info about lcd controller I came across this page: http://heikki.virekunnas.fi/2015/raspberry-pi-tft/, author managed to get from manufacturer patch file for kernel sources and tested it with 4.1.y - on which lcd worked. But still LCD replace HDMI, but I want to use this screen as additional for user interaction, while the bigger on HDMI as presentation monitor.

Since, fbtft has been merged with rpi kernel, so the fb drivers (including ili9341.c) was moved to fbtft_device driver (so the author of page can"t compile latest kernel with driver+patch).

[ 4.838806] input: MOSART Semi. Rapoo 2.4G Wireless Touch Desktop as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:24AE:1000.0001/input/input1

[ 4.902783] input: MOSART Semi. Rapoo 2.4G Wireless Touch Desktop as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:24AE:1000.0002/input/input2

- Controller is not ILI9341/ILI9325 - those are for smaller displays (320x240, etc...), I guess this might be ILI9486/9488 because they are for 480x320 displays. But when I compared init with DS it does not fit right so LCD can have a clone of ILI9486/9488 ...

- Module use only SPI interface and two CE signals (CE0 for touch controller, CE1 for LCD shift registers - compared to others lcd modules, in KeDei module this is swapped),