Fastest FPS on Your Raspberry Pi SPI LCD Screen - RetroPie playable on a cheap LCD panel

[@ashketchum1244]

hey mate, i bought a 8$ screen like this from aliexpress expecting it to be terrible to my surprise after using your tutorial it's a pretty smooth 30-60fps in game. it's laggy in the home menu for some reason, but doesn't matter if the game plays perfect! thanks for this

[@BytesNBits]

Great to hear you got it working.

[@arthurperini]

Great video. I've started to use tensor flow routines with Coral accelerator, but the results with a LCD 3.5 similar to it was terrible I'm going to try this driver.

[@BytesNBits]

Great. It should improve the display quite a bit.

[@gamecat666]

EXCELLENT video, thanks a lot. I was searching for a better driver for these screens but this was the best resource I found. I wasnt sure if a waveshare 35a worked with this driver but this proves it does. I tried mine on a Pi1 (just out of sheer curiousity) and I dont get anywhere near as good results as you do, even without using emulators. Maybe it just doesnt have the horsepower to drive the screen this fast.

[@BytesNBits]

Hi. Glad it helped. Have a look at my overclocking video for the Raspberry Pi. That might help out a bit on the RPi V1 setup. Have fun!

[@Iskelderon]

Thanks, this sounds to be perfect for a project I'm planning to build later this year. A ghostbusters cartoon PKE Meter that displays mostly just vector-based graphs and the like, but in some modes will also show static graphics and short video elements that only cover a fraction of the overall screen (think animated pre-rendered logos). Since it's not full-screen changes like a game, I should be able to hit a target of 24-30 frames on a Pi Zero 1.

[@BytesNBits]

Sounds great! Give it a go.

[@horsejohnson7959]

Static is a good example of what this won't work well on because practically every pixel is changing

[@horsejohnson7959]

Static is a good example of what this won't work well on because practically every pixel is changing

[@Iskelderon]

@@horsejohnson7959 The way the video describes it, it actually benefits from just such use cases with as little delta changes as possible, kinda like video compression. In other words, this very kind of project where there's just reasonably small changes to regions because it will lessen the calculation load.

[@douphowto]

Very useful thanks, let the tweaking commence.

[@BytesNBits]

Glad it was helpful!

[@horsejohnson7959]

This is basically streaming but it's a genius optimization in any implementation

[@BytesNBits]

Yes. A great piece of software.

[@powerguidissimo1]

Tenho exatamente essa tela do seu video, estava a anos parada sem uso, agora com sua ajuda irei retomar o projeto do meu videogame portatil, muito obrigado pelo video.

[@BytesNBits]

Excelente. Fico feliz que tenha achado útil. Boa sorte com o projeto!

[@elbedouirayen7938]

Thank u for the video please i have a problem, after ctrl+c and reboot lcd didn't work even hdmi screen is working well, what should i do please?

[@BytesNBits]

Did you redo the steps in the video to get the driver software enabled. The reboot might have stopped it so it will need restarting.

[@palaciosele]

​@@BytesNBitsI am facing the same issue. When I run the fbcp-ili9341 file, the screen is working and replicates the code that is outputed by the HDMI, but turns to white as soon as I press ctrl + c. What could be the cause of this? I am using a rpi 4B. Thank you in advance, and for the great tutorials!

[@leontechtalks]

I got it to run at around 74 FPS with this mod. It’s showing that it’s running at that framerate, but it looks like it’s running at 50.

[@BytesNBits]

Go for it!

[@bens4446]

Great work. Any reason why this wouldn't work with batocera?

[@BytesNBits]

This should work with anything. It's a screen driver rather than linked to RetroPie. Note that the driver used in the video does not work with the latest Pi OS. You need to use a 2023 release as they changed the base video software.

[@ЕгорУльянкин-я1ж]

is this will work with waveshare 35b v2 ?

[@BytesNBits]

If it uses the same driver chip then yes

[@abhi9av_9808]

I have used a same LCD as yours, what gpio pins can I still use to connect buttons of a custom-made controller. I will be using your tutorial to do so.

[@BytesNBits]

I gave a pin assignment diagram in the project page - bytesnbits.co.uk/gpio-controller-raspberry-pi-retropie/

[@phillangstrom8693]

ok i tried using the 32b version of raspbian and it still has some extra lines after the green ones but they don't seem to be errors yet when i initialize the driver it go's to a blank dark screen i did try a couple other drivers but the only one that installed with all green still errors during initialization and said make sure hdmi hotplug was enabled in config.txt but that was one of the first things i did this time before installing the driver

[@BytesNBits]

This video needs to be updated. Raspian removed the Linux drivers that the LCD driver relies on earlier this year. To get this to work you need to use a version of raspian from 2023. Hope this helps.

[@davidesaulozagarcia2904]

​@@BytesNBits Will the new video be out soon? You explain it very clearly, but it didn't work for me, and I have exactly the same screen.

[@hosniarafet2054]

You are amazing

[@BytesNBits]

Thank you.

[@Dr.Obscurus]

Got it working till running main loop when I reboot it doesn't show up on lcd. Pls help

[@BytesNBits]

Make sure you add the start up script - kzbin.info/www/bejne/q6uXpJRoaahnnc0

[@Dr.Obscurus]

@@BytesNBits thanks. It works wonderfully now. I could barely run super mario world but not it works great. Great tutorial

[@mintcarcreative2424]

Everytime I hit Ctrl C it doesn’t take me back to the command prompt and the tft screen stops mirroring the display? What am I doing wrong?

[@BytesNBits]

Hi. I think the Ctrl C is getting picked up by the screen driver software and exiting that. Have you set it to run at startup rather than manually starting it? That should drop it into the background.

[@TamactiJun74]

Quando scrivi make -j dopo tutto il procedimento mi da errore…….perche ?

[@BytesNBits]

I'm not sure. Did you follow all the steps and did the source code download OK. Have you got the compiler installed and updated.

[@romiolover6852]

Great, Thank you a lot, but i wonder if the touch is still working with this new driver ?

[@BytesNBits]

Hi. To be honest I haven't tried it out in desktop mode. Hopefully the touch function is separate from the screen driver - I think it is.

[@SerVanzu]

My display is fine in retropie, but whenever i boot an actually game it freezes up. Any idea what causes this?

[@BytesNBits]

You might have the speeds turned up too high. I found that at the very top speeds Retropie seemed only just stable but gaming screens fell apart.

[@SerVanzu]

@@BytesNBits Should I up the clock divisor then? or do you mean something else by speed.

[@BytesNBits]

@@SerVanzu Yes. Increase the divisor to decrease the serial speed.

[@helloworld669]

Im getting unrecognized command-line option error

[@helloworld669]

It stopped at 53%

[@BytesNBits]

Which part did it crash on?

[@alessiocirella3135]

hi there! i first want to thank you for the great video and explanation. i then kindly wanted to ask you how can I solve the "unrecognized command line option" error in cmake. I know this video is a bit old, and so is the project on github, so i first thought there was a conflict between versions... but I don't know if that's right. These are the errors I get: c++: error: unrecognized command-line option ‘-marm’ c++: error: unrecognized command-line option ‘-mfloat-abi=hard’ c++: error: unrecognized command-line option ‘-mhard-float’ c++: error: unrecognized argument in option ‘-mabi=aapcs-linux’ c++: note: valid arguments to ‘-mabi=’ are: ilp32 lp64 c++: error: unrecognized argument in option ‘-mtls-dialect=gnu2’ c++: note: valid arguments to ‘-mtls-dialect=’ are: desc trad and they seem to repeat many times in the output. so any help is appreciated!

[@BytesNBits]

These look like make file errors. Did you follow the instructions in the video? As you say the video needs updating so it may well be a version issue.

[@rustom767]

it's because your running 64-bit OS this driver on works for 32-bit

[@clicksandbeeps61]

Didn’t work with mine :( Sprung up an error code Checked the controller my lcd uses And none of the builds matched my controller :( However, did manage to follow your other tutorial to make my display faster! Another thing you can do is overclock the pi with the 800mghz command, and then you can have a slightly-higher-than 24000000 rate, making it slightly faster.

[@BytesNBits]

Shame about the driver. I hope you're getting a reasonable frame rate.

[@samuelebaiano6505]

help please, i got a lot of errors when i tried to do make -j... what i have to do? SOLVED: DO NOT use 64 bit version of rasbian os

[@BytesNBits]

Good to hear you found the solution.

[@samuelebaiano6505]

@@BytesNBits but now the problem is that it doesn't work on retropie os... And your video is on retropie... Wtf? I see white screen, doing the same steps worked for me on raspbian

[@mangobob1184]

How to make screen run smoother?

[@BytesNBits]

This is about as good as it gets. The driver in this video is optimising the frames to get the framerate up. If you want better you'll need to move to an HDMI display.

[@rghazt]

I cant do hash button

[@BytesNBits]

Is it just your keyboard doesn't have one or are you having a problem getting it to register?

[@rghazt]

@@BytesNBits keybord

[@melanie.martinez.is.so.slay.]

had to reinstall retropie because it broke thanks mate

[@BytesNBits]

This video needs to be updated. Raspian removed the Linux drivers that the LCD driver relies on earlier this year. To get this to work you need to use a version of raspian from 2023. Hope this helps.

[@Dr.Obscurus]

Would it be portable though?

[@BytesNBits]

If you add a battery pack it will be fine. Probably not great battery life but it will be portable.

[@katokira260]

cool you save me does this effect on cpu ?

[@BytesNBits]

Hi. It will have some effect on the overall RPi speed as there are a lot more calculations going on. Hard to say how much. You'd need to play around.

[@umutkayacan7659]

nice

[@BytesNBits]

Thanks

[@jarkin94]

Hi great video, very helpful! struggling with getting the screen to boot each time the pi is restarted. I am running PINN and then booting into RetroPi, i have added the "sudo /home/pi/fbcp-ili9341/build/fbcp-ili9341 &" line to my rc.local file but hasnt worked. once the pi has booted if i SSH in and run "sudo /home/pi/fbcp-ili9341/build/fbcp-ili9341 &" the screen starts. Any ideas on how to correct this?

[@BytesNBits]

I suspect either your rc.local file isn't being run or something after that is resetting the display. You'd need to trace through to find out what's happening.

[@phillangstrom8693]

i get to this point {make -j} and it starts a few lines then errors down the rest of the page c++: error: unrecognized command-line option ‘-marm’ c++: error: unrecognized command-line option ‘-mhard-float’ c++: error: unrecognized argument in option ‘-mabi=aapcs-linux’ c++: note: valid arguments to ‘-mabi=’ are: ilp32 lp64 c++: error: unrecognized argument in option ‘-mtls-dialect=gnu2’ c++: note: valid arguments to ‘-mtls-dialect=’ are: desc trad c++: error: unrecognized argument in option ‘-mabi=aapcs-linux’ c++: note: valid arguments to ‘-mabi=’ are: ilp32 lp64 c++: error: unrecognized argument in option ‘-mtls-dialect=gnu2’ c++: note: valid arguments to ‘-mtls-dialect=’ are: desc trad c++: error: unrecognized command-line option ‘-marm’ c++: error: unrecognized argument in option ‘-mabi=aapcs-linux’ c++: note: valid arguments to ‘-mabi=’ are: ilp32 lp64 c++: error: unrecognized argument in option ‘-mtls-dialect=gnu2’ c++: note: valid arguments to ‘-mtls-dialect=’ are: desc trad i should mention i am trying this on raspbian 64

[@BytesNBits]

The LCD driver does rely on a bit of Linux that had been replaced in the latest raspian versions. You might need to install a 2023 version to get this to work. I need to update this video but I don't think a new driver has been written yet.

[@davidesaulozagarcia2904]

@@BytesNBits Could you explain how to install a 2023 version?