Enabling CLCD screen on Recalbox Tutorial
-
Hey guys, i found this topic
https://forum.recalbox.com/topic/8689/script-clcd-display-on-recalbox
And ive been trying since yesterday to get this thing working on a pi4 as i got it working on Pi OS but wanted it for recalbox but idk if its just outdated as it was last mentioned for a pi3 or what but does anyone or can anyone give a updated tutorial on this by chance as there is legit nothing on google about this except for when on pi.
I tried this instructions from this topic but get errors during script install and manual dont work and says im missing Dev i2c-1 stuff but ive followed instructions to the letter and just nothing.
Would appreciate any help, thank you.
-
@slider6996 The official documentation is this:
https://wiki.recalbox.com/en/tutorials/video/tft/lcd-display-with-i2cBut, I really can't remember when was the last time a user mentioned this screen, it seems it's not very popular, and since we don't have all kinds of hardware, we rely on user feedback to see if some work, so you need to test.
-
@zing i appreciate the link, i just got back into town so once i get unpacked and settled ill have a look. Hoping there is someone who has done this as there is legit no video of any kind on how to enable this feature and love the idea behind it and case i bought is specifically for this so hope to get it working.
-
@zing Alright so some of the instructions in link was different from the script page but im assumingits because the script was reffering to a Pi3 so i followed the offical ones and was hopeful when i saw the lines to add was different from the script line as i assumed that was the issue right there but still wont work as when i get to this step "on newer Raspberry models (pi4, pi3, pi2): i2cdetect -y 1" that command just never works, it worked when i tested the screen using a OS version of Pi to boot into the OS and all but on recall box that command just never works as i get this messsage "# i2cdetect -y 1
Error: Could not open file/dev/i2c-1' or
/dev/i2c/1': No such file or directory" So is the correct spot for "#Activate I2C
dtparam=i2c1=on
dtparam=i2c_arm=on" to be put at the very bottom under where it sayscustom config
[all]
#Activate I2C
dtparam=i2c1=on
dtparam=i2c_arm=onIs that how it is suppose to look or does that go some where else? Thats only other thing i can think of cause like i said screen for sure works as i even went back to pi OS to test and all was good.
-
Ok so after some more testing i think ive found the issue i just dont know how it became a issue or how to fix. So i put the pi OS image back in and looked at the /dev files in there and it has the 12c file and 12c-1 file there but in the recalbox image it only has 12c-11 and 12c-12? I was like ok i can just copy the file over from the Pi OS but in short thats impossible so idk how to enable the recalbox to create the same file as the Pi OS as thats what is needed it seems for me to make it work but like i posted above, u can see the steps i did and its not a hard to follow guide so not sure what the issue is unless someone needs to look at my config file and cmd file to confirm its correct?
-
It's not the same screen that appears in the tutorial, and I don't have any other feedback saying it's compatible with Recalbox, the only report we have is from the other model and it's a very old report.
So i put the pi OS image back in and looked at the /dev files in there and it has the 12c file and 12c-1 file there but in the recalbox image it only has 12c-11 and 12c-12?
Which again indicates that this model is not compatible. And, an average user cannot install anything on the Recalbox system, a developer can, but needs to recompile the entire system most of the time...
I'm not a developer, and even our developers probably don't have this hardware to do the proper testing, so I don't think I can help you much from here.
If you have knowledge, interest, and will, you can try to recompile the system yourself, there are some instructions in the official gitlab (but I should warn you that we don't support this kind of situation, I myself don't even have enough knowledge to give this kind of support):
https://gitlab.com/recalbox/recalboxSome other options:
- Open an issue in gitlab (check if there is not already a similar issue open), and wait for a response from one of the developers
https://gitlab.com/recalbox/recalbox/-/issues - Go to our official Discord channel and see if anyone has any other ideas (there's a chance a developer will answer you)
https://discord.com/invite/NbQFbGM - Invest financially in the project by becoming a Patron Recalbox, and have some special advantages, such as access to an exclusive discord channel:
https://www.patreon.com/recalbox?utm_source=recalbox&utm_medium=website
- Open an issue in gitlab (check if there is not already a similar issue open), and wait for a response from one of the developers
-
@zing Alright will do and i totally understand, appreciate the help so far.
-
This post is deleted! -