Hardware question

There’s change, and change is good! No video on hdmi…i’m pretty sure the reconfigured code doesn’t match the hardware lol. Will keep trying!

Holy $hit! @Kivutar is this what you meant when you said to see how the screen works? pi@raspberrypi:~ $ gpio readall ±----±----±--------±-----±–±--Pi 3—±–±-----±--------±----±----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | ±----±----±--------±-----±–±—+±—±–±-----±--------±----±----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 2 | 8 | SDA.1 | ALT0 | 1 | 3 || 4 | | | 5v | | | | 3 | 9 | SCL.1 | ALT0 | 1 | 5 || 6 | | | 0v | | | | 4 | 7 | GPIO. 7 | IN | 1 | 7 || 8 | 1 | ALT5 | TxD | 15 | 14 | | | | 0v | | | 9 || 10 | 1 | ALT5 | RxD | 16 | 15 | | 17 | 0 | GPIO. 0 | IN | 1 | 11 || 12 | 0 | IN | GPIO. 1 | 1 | 18 | | 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | | | 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | 0 | IN | GPIO. 4 | 4 | 23 | | | | 3.3v | | | 17 || 18 | 1 | OUT | GPIO. 5 | 5 | 24 | | 10 | 12 | MOSI | ALT0 | 0 | 19 || 20 | | | 0v | | | | 9 | 13 | MISO | ALT0 | 0 | 21 || 22 | 1 | OUT | GPIO. 6 | 6 | 25 | | 11 | 14 | SCLK | ALT0 | 0 | 23 || 24 | 1 | OUT | CE0 | 10 | 8 | | | | 0v | | | 25 || 26 | 1 | OUT | CE1 | 11 | 7 | | 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 | | 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | | | 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 | | 13 | 23 | GPIO.23 | IN | 0 | 33 || 34 | | | 0v | | | | 19 | 24 | GPIO.24 | IN | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 | | 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | IN | GPIO.28 | 28 | 20 | | | | 0v | | | 39 || 40 | 0 | IN | GPIO.29 | 29 | 21 | ±----±----±--------±-----±–±—+±—±–±-----±--------±----±----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM

that looks crappy…but at least i can recognize the flags from your code!!!

Moving forward… if this is the fbtft to make the driver work under raspbian:

  • PiScreen - 3.5" TFT touchscreen (480x320)

*/ &spi0 { piscreen@0{ compatible = “ilitek,ili9486”; reg = <0>; status = “disabled”;

	spi-max-frequency = <20000000>;
	rotate = <270>;
	bgr;
	fps = <30>;
	buswidth = <8>;
	reset-gpios = <&gpio 25 0>;
	dc-gpios = <&gpio 24 0>;
	led-gpios = <&gpio 22 1>;

	init = <0x10000b0 0x00
	        0x1000011
		0x20000FF
		0x100003A 0x55
		0x1000036 0x28
		0x10000C2 0x44
		0x10000C5 0x00 0x00 0x00 0x00
		0x10000E0 0x0F 0x1F 0x1C 0x0C 0x0F 0x08 0x48 0x98 0x37 0x0A 0x13 0x04 0x11 0x0D 0x00
		0x10000E1 0x0F 0x32 0x2E 0x0B 0x0D 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00
		0x10000E2 0x0F 0x32 0x2E 0x0B 0x0D 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00
		0x1000011 
		0X1000029>;
	debug = <0>;
};

Combined with the pinouts from wiringPi readall, I should be able to modify the C code to make this work…

Hope I didn’t p1ss anyone off XD no further progress so far…just managed to shut off HDMI :stuck_out_tongue:

Hello, Everyone! Looking for some help. I’ve switched information from kivutar’s code to “match” info from the datasheet of the screen I’m using: see here > https://drive.google.com/open?id=0ByxAPpji41kcM0pyLTVVdnNiTjg but all it managed to do was to turn off hdmi output, and (possibly) crash the Pi lol The program didn’t fry anything, as i can swap SD cards, and it everything boots up normally.

I noticed that when compiling the program with wiringPi, it was throwing errors for “ILI9486_PWCTRL 1” and " ILI9486_PWCTRL 2"; i presumed because of the spaces between ctrl and 1&2…so i removed the spaces in all instances, and replaced them with underscores; however, would that be incorrect, as the command PWCTRL_1 _2 are invalid for the ili9486 controller?

Oh, and here is the data sheet i’m using, if anyone wants to take a look > https://drive.google.com/open?id=0ByxAPpji41kcLW5PSmxqX1ROQlU Any help would be highly appreciated!

Hey, Guys! Foe now, i was able to use a 5" hdmi screen successfully on the Pi with Lakka ! Haven’t given up on the 3.5", as I think that would make the unit much “cooler” looking, but i do want to play some time this decade lol. So for now, thanks to everyone for your input. @Kivutar I learned a ton just from your input on this single thread!

1 Like

Hi…i am a new user here. As per my knowledge there is another part, which is completely different depending on the screen. Most screens will use a kernel module .In the case of gamegirl, there is a part in config.txt to set the video mode, rotate de screen, but we don’t use a kernel driver. We made a small C program that configure the screen in SPI mode using the GPIO. Which allowed us to have a very fast display (120Hz) while some other ways to do can limit you to 25Hz.

pcb assembly china

Hey, LulaNord! Correct, in my scenario I would be using a “regular” kernel module (fbtft or similar) which would give me max 30fps. I’ve tried to rewrite the program Kivutar showed me using info from the spec sheet for my LCD, but to no avail, yet… Haven’t abandoned the project completely, but the 5" hdmi works very well out of the box :wink:

Great work.

We have recently successfully reached overfunding on our project as well

Current support if for RetroPie (no comments please), but we would love to get Lakka as the main distro.

Now the challenge is to get OpenElec (Lakka) to work with FBTFT module.

You can check our wiki here to compile Lakka yourself http://www.lakka.tv/doc/Compiling-Lakka/

And learn how to package FBTFT.

Or you can send us a sample, and we will adapt Lakka for your hardware.

Thanks for the link. That will be my first go

And you can join #lakkatv on freenode to get help about packaging. Ask Ntemis, gouchi or me.

Thanks @Kivutar

You can check my GitHub Install This is an outline if you are using RetroPie (Raspbian)

I would love to know how to do this on Lakka/OpenELEC

Any advice would be great!

Thanks in advance

For an easy to maintain setup, I would start like this:

  • copy projects/RPi project to projects/GameBoyZero, so you can build with PROJECT=GameBoyZero
  • do the same for packages/lakka/RPi
  • to enable SPI, override the pi bootloader package like I did in projects/Gamegirl
  • autoloading modules can be done in projects/GameBoyZero/filesystem, once again, check how it is done on other projects
  • fbcp needs to be packaged too (but you’re going to get poor performance with this method, you’d better do like we did for Gamegirl to get 200FPS. If you persist in using fbcp, create a systemd unit to launch it on startup.