Jump to content

Orange Pi Zero 3 ili9486 TFT LCD

WDR_s

By WDR_s
in Allwinner sunxi

 Share
Go to solution Solved by WDR_s,

Recommended Posts

WDR_s

WDR_s

Posted
Posted

I have this screen here ili9486 : https://pt.aliexpress.com/item/32805704334.html?src=google&pdp_npi=4%40dis!BRL!43.31!38.51!!!!!%40!12000019014148570!ppc!!!&src=google&albch=shopping&acnt=768-202-3196&isdl=y&slnk=&plac=&mtctp=&albbt=Google_7_shopping&aff_platform=google&aff_short_key=UneMJZVf&gclsrc=aw.ds&&albagn=888888&&ds_e_adid=&ds_e_matchtype=&ds_e_device=c&ds_e_network=x&ds_e_product_group_id=&ds_e_product_id=pt32805704334&ds_e_product_merchant_id=107713925&ds_e_product_country=BR&ds_e_product_language=pt&ds_e_product_channel=online&ds_e_product_store_id=&ds_url_v=2&albcp=21106536414&albag=&isSmbAutoCall=false&needSmbHouyi=false&gad_source=1&gclid=EAIaIQobChMI14GV5um3iQMVK2BIAB0KwQPmEAYYASABEgJc4fD_BwE

 

I would like to know if i can connect to my orange pi zero 3

I have already tried to connect but without success, as I am new to this I would like you to help me if possible. 

Thanks!

Sorry for my English I'm on google.

 

0
robertoj

robertoj

Posted
Posted

Starting with the DTS that worked for me in the orange pi zero 3, with ili9341:

 

 

https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/?do=findComment&comment=204672

 

My DTS is for a customized set of pins that works for me, and it is different than/from the waveshare set of pins.

 

You need to change:

* file name change to: ili9486-ads7846-spi1.dts

* gpio pin selections everywhere in the DTS

* "adafruit,yx240qv29" should be "ilitek,ili9486"

* change "rotation" to "rotate"

* change "reset-gpios = <&pio N N 0>;" to "reset-gpios = <&pio N N 1>;

 

Then sudo armbian-add-overlay ili9486-ads7846-spi1.dts

Reboot

 

(does anyone know the correct DRM driver for ili9486?)

0
WDR_s

WDR_s

Posted
  • Author
Posted (edited)

I used your DTS and modified the driver and some other things and it looked like this:

 

root@orangepizero3:~/testopiz3# cat ili9486-ads7846-spi1.dts
/dts-v1/;
/plugin/;
/ {
    compatible = "allwinner,sun50i-h616";
    fragment@0 {
        target = <&spi1>;
        __overlay__ {
            status = "okay";
            cs-gpios = <&pio 7 9 0>,<&pio 2 15 0>; /*PH9=CS0 for lcd, PC15=CS1 for touch*/
            ili9486: ili9486@0 {
                compatible = "ilitek,ili9486";
                reg = <0>;
                pinctrl-names = "default";
                spi-max-frequency = <24000000>;
                rotate = <270>;
                bgr = <0>;
                fps = <30>;
                buswidth = <8>;
                reset-gpios = <&pio 2 14 1>; /* PC14 */
                dc-gpios = <&pio 2 7 0>; /* PHC7 */
                debug = <3>;
            };

            ads7846: ads7846@1 {
                compatible = "ti,ads7846";
                reg = <1>;
                pinctrl-names = "default";
                spi-max-frequency = <1000000>;
                interrupt-parent = <&pio>;
                interrupts = <2 10 2>; /* PC10 - IRQ */
                pendown-gpio = <&pio 2 10 1>; /* PC10 */

                /* OPTIONS */
                ti,x-min = /bits/ 16 <0>;
                ti,y-min = /bits/ 16 <0>;
                ti,x-max = /bits/ 16 <0xFFF>;
                ti,y-max = /bits/ 16 <0xFFF>;
                ti,pressure-min = /bits/ 16 <0>;
                ti,pressure-max = /bits/ 16 <0xFFF>;
                ti,x-plate-ohms = /bits/ 16 <400>;
                ti,swap-xy = <1>;
            };
        };
    };

 

the screen didn't turn on and I get this:

 

root@orangepizero3:~/testopiz3# dmesg|grep spi
[    1.336361] sun50i-h616-pinctrl 300b000.pinctrl: pin-64 (5010000.spi) status -517
[    1.336380] sun6i-spi 5010000.spi: Error applying setting, reverse things back
[    1.336625] sun50i-h616-pinctrl 300b000.pinctrl: pin-230 (5011000.spi) status -517
[    1.336642] sun6i-spi 5011000.spi: Error applying setting, reverse things back
[    1.344519] sun50i-h616-pinctrl 300b000.pinctrl: pin-64 (5010000.spi) status -517
[    1.344537] sun6i-spi 5010000.spi: Error applying setting, reverse things back
[    1.344790] sun50i-h616-pinctrl 300b000.pinctrl: pin-230 (5011000.spi) status -517
[    1.344807] sun6i-spi 5011000.spi: Error applying setting, reverse things back
[    1.353376] spi-nor spi0.0: supply vdd not found, using dummy regulator
[    1.368687] spi-nor spi0.0: spi-nor-generic (16384 Kbytes)
[    5.756110] ads7846 spi1.1: supply vcc not found, using dummy regulator
[    5.774274] ads7846 spi1.1: touchscreen, irq 72
[    5.778306] [drm] Initialized ili9486 1.0.0 20200118 for spi1.0 on minor 2
[    5.791888] spi_master spi1: noqueue transfer failed
[    5.791896] ili9486 spi1.0: [drm] *ERROR* Failed to update display -5
[    5.806250] input: ADS7846 Touchscreen as /devices/platform/soc/5011000.spi/spi_master/spi1/spi1.1/input/input4
[    6.332084] spi_master spi1: noqueue transfer failed
[    6.341922] spi_master spi1: noqueue transfer failed
[    6.343037] ili9486 spi1.0: [drm] fb0: ili9486drmfb frame buffer device
[    6.376583] SPI driver fb_ili9486 has no spi_device_id for ilitek,ili9486
[    6.392717] spi_master spi1: noqueue transfer failed
[    6.484766] spi_master spi1: noqueue transfer failed
[    6.496428] spi_master spi1: noqueue transfer failed
[    6.507222] spi_master spi1: noqueue transfer failed
[    6.524186] spi_master spi1: noqueue transfer failed
[    6.583772] spi_master spi1: noqueue transfer failed
[    6.665947] spi_master spi1: noqueue transfer failed
[    6.683600] spi_master spi1: noqueue transfer failed
[    8.071086] spi_master spi1: noqueue transfer failed
[    8.225788] spi_master spi1: noqueue transfer failed
[    8.260765] spi_master spi1: noqueue transfer failed
[    8.423577] spi_master spi1: noqueue transfer failed
[    8.455263] spi_master spi1: noqueue transfer failed
[    8.522713] spi_master spi1: noqueue transfer failed
[    8.564872] spi_master spi1: noqueue transfer failed
[    8.575518] spi_master spi1: noqueue transfer failed
[    9.074598] spi_master spi1: noqueue transfer failed
[    9.084348] spi_master spi1: noqueue transfer failed
[    9.116925] spi_master spi1: noqueue transfer failed
[    9.131941] spi_master spi1: noqueue transfer failed
[    9.144523] spi_master spi1: noqueue transfer failed
[    9.155518] spi_master spi1: noqueue transfer failed
[    9.363656] spi_master spi1: noqueue transfer failed
[    9.378223] spi_master spi1: noqueue transfer failed
[    9.391305] spi_master spi1: noqueue transfer failed
[    9.402360] spi_master spi1: noqueue transfer failed
[    9.536236] spi_master spi1: noqueue transfer failed
[    9.644439] spi_master spi1: noqueue transfer failed
[   10.144929] spi_master spi1: noqueue transfer failed
[   10.268524] spi_master spi1: noqueue transfer failed
[   10.285998] spi_master spi1: noqueue transfer failed
[   10.295763] spi_master spi1: noqueue transfer failed
[   10.610540] spi_master spi1: noqueue transfer failed
[   10.778565] spi_master spi1: noqueue transfer failed
[   11.373986] spi_master spi1: noqueue transfer failed
[   11.536724] spi_master spi1: noqueue transfer failed
[   11.615775] spi_master spi1: noqueue transfer failed
[   11.630380] spi_master spi1: noqueue transfer failed
[   11.641227] spi_master spi1: noqueue transfer failed
[   11.691254] spi_master spi1: noqueue transfer failed
[   11.727754] spi_master spi1: noqueue transfer failed
[   11.738178] spi_master spi1: noqueue transfer failed
[   12.109599] spi_master spi1: noqueue transfer failed
[   12.305293] spi_master spi1: noqueue transfer failed
[   12.664486] spi_master spi1: noqueue transfer failed
[   12.674529] spi_master spi1: noqueue transfer failed
[   13.020004] spi_master spi1: noqueue transfer failed
[   13.032088] spi_master spi1: noqueue transfer failed
[   13.042854] spi_master spi1: noqueue transfer failed
[   13.074828] spi_master spi1: noqueue transfer failed
[   13.203632] spi_master spi1: noqueue transfer failed
[   13.315447] spi_master spi1: noqueue transfer failed
[   57.093748] spi_master spi1: noqueue transfer failed

Edited by WDR_s
0
robertoj

robertoj

Posted
Posted

I see that you didnt change any gpios. You must change them... what are the pins in the orange pi zero 3 that will control the lcd? (you must have the LCD schematic)

 

If you try my original DTS, without having a screen like mine, do you get these 2 files?

/dev/fb0

/dev/input/event0

 

According to this https://mjmwired.net/kernel/Documentation/devicetree/bindings/display/ilitek,ili9486.yaml

You must use the line:

compatible = "waveshare,rpi-lcd-35", "ilitek,ili9486";

0
WDR_s

WDR_s

Posted
  • Author
Posted

I changed a few pins and the dts looked like this:

  Reveal hidden contents

 

the screen still doesn't give an image, but I get this:

  Reveal hidden contents

 

do i have to add anything to /boot/armbianEnv.txt ? i'm in doubt!

0
robertoj

robertoj

Posted
Posted

Regarding these lines:

cs-gpios = <&pio 2 5 0>,<&pio 7 9 0>; /*PH5=CS0 for lcd, PH9=CS1 for touch*/

reset-gpios = <&pio 0 8 1>; /* PC15 */
dc-gpios = <&pio 0 5 0>; /* PC5*/

interrupts = <2 7 2>; /* high-to-low edge triggered */
pendown-gpio = <&pio 2 7 0>;

 

Make sure that you make the comments match with the actual DTS code, for example PH5=<&pio 7 5 0>, because H=7

Also according to the gpio formula, C=2.

Also insert some initial comment lines at the top, summarizing the pinout you discovered for the orange pi zero 3, to show your intermediate work

 

You are very close. All those spi1.0, spi1.1 dmesg messages indicate that there's no conflict internally in the CPU, but probably the one or a few IOs are connected to the incorrect pin(s). 

 

Another thing to try is change "reset-gpios = <&pio 0 8 1>" to "reset-gpios = <&pio 0 8 0>" because sometimes different kernel modules handle the polarity in the opposite way than it is expected.

Also try changing "compatible = "ilitek,ili9486";" to "compatible = "waveshare,rpi-lcd-35";" and look at the example in https://mjmwired.net/kernel/Documentation/devicetree/bindings/display/ilitek,ili9486.yaml to find the little differences in parameters.

 

Keep googling this forum for ili9486, maybe someone did it already :)

0
robertoj

robertoj

Posted
Posted

How is it going with the ili9486 LCD? :)


the armbianEnv.txt only needs the user-overlay line with the dts you are using (without the dts extension)… but seeing your progress, I am sure the armbianEnv.txt is perfect as it is now

 

your problem might be the gpio numbers (1st and 2nd parameter in <&pio xxx xxx xxx>) and the polarity setting (3rd parameter)

 

DO NOT ADD ANYTHING ELSE SPI RELATED

0
WDR_s

WDR_s

Posted
  • Author
Posted

Thanks for asking!

I'm using this dts:

  Reveal hidden contents

 

Come on, even if I change the pins I still get the same thing. 
 

  Reveal hidden contents

 

And when I change the driver compatibility from “compatible = ‘ilitek,ili9486’;” to “compatible = ‘waveshare,rpi-lcd-35’;”, it shows this:

  Reveal hidden contents

 

0
WDR_s

WDR_s

Posted
  • Author
Posted

Every time I change the pins, the driver doesn't load correctly, it always shows me the same driver message.

  Reveal hidden contents

 

this error is the wrong pins, but I haven't found a way to solve it yet.
Do you have any suggestions? 
 

0
WDR_s

WDR_s

Posted
  • Author
Posted (edited)

I used your dts, I just changed the drivers:

  Reveal hidden contents

 

i knew it wouldn't work, but it starts the driver on your dts.
 

  Reveal hidden contents

 

 

Edited by WDR_s
0
WDR_s

WDR_s

Posted
  • Author
Posted

Hello.
On this screen you need CS, when connected directly to the board, using dupont I'm not sure because I don't have it. 

 

The driver will only load if reset and dc are set to 2.

At the moment that's all I've found, but it still gives an error when it loads the driver, so I'm trying to solve it.

  Reveal hidden contents

 

0
robertoj

robertoj

Posted
Posted

Those 2 lines contradict each other: both reset and dc (data/command) cant be the same.

 

Can you send a drawing of the wiring between the orange pi zero and the LCD display? (in terms of SPI-MISO, MOSI, DC, RESET, LED, etc, and the DTS you have just tried?

0
WDR_s

WDR_s

Posted
  • Author
Posted

I know that, I was just giving an example. 

it should be like this: <&pio 2 N N>:

I'm currently using this one:

  Reveal hidden contents

 

0
Ryzer

Ryzer

Posted
Posted

Hi WDR_s, did you manage to make any progress. if you are still getting the pinctrl errors as shown above the problems relate to PC0 (Pin 64) and PH6 (Pin 230). Are you running any addtional overlays? Can you check sudo cat /sys/kernel/debug/gpio to ensure the pins are not being used elsewhere?

 

Best of luck

Ryzer

0
robertoj

robertoj

Posted
Posted

WDR_s, can you check if the manufacturer actually says ili9486? I have an LCD from aliexpress, which claims it is ili9486, but deeper in the webpage it reads st7796s... and someone complained it is actually ili9488.

 

Maybe you havent identified correctly the LCD controller ilitek chip.

 

Here are other things we can try for the ili9486, ili9488 or st7796, using the panel-mipi-dbi-spi driver (changing the raspberry pi methods into armbian methods)

https://forums.raspberrypi.com/viewtopic.php?t=376047

https://forums.raspberrypi.com/viewtopic.php?t=358240&hilit=Ili9341#p2165638

https://github.com/notro/panel-mipi-dbi/wiki

https://gitlab.freedesktop.org/drm/misc/kernel/-/blob/drm-misc-next/Documentation/devicetree/bindings/display/panel/panel-mipi-dbi-spi.yaml?ref_type=heads

0
robertoj

robertoj

Posted
Posted

Thank you for answering...

 

What did you do, when you thought you had an ili9488 LCD?

 

in the raspberry forum, someone told me that st7796s is not the same as ili9488… but I found that the ili9341 driver with a slight modification could be made into a ili9488 driver

 

0
WDR_s

WDR_s

Posted
  • Author
Posted (edited)

Hi, I'm back, now I'm trying once again to connect the screen to the orange pi zero 3.
I was looking at this link, panel-mipi-dbi-spi, it doesn't work on the ili9486, but it works on the ili9341, so I would have to modify the ili9486 to the ili9341.
I'll try that now .

 

I now have the dupont wires.

Edited by WDR_s
0
WDR_s

WDR_s

Posted
  • Author
Posted (edited)

I'm making progress with the dts I've modified:

  Reveal hidden contents

 

I got this image, but I have to modify it a bit more.

e65fc002-357b-4fce-821a-f3dce4f058ed.jpg

Edited by WDR_s
0
robertoj

robertoj

Posted
Posted

Nice progress.

 

I think that your SPI, DC, CS, RESET configurations are correct. DONT CHANGE THOSE :)

 

Regarding the ili9341 vs ili9486 driver... hopefully you will find an example using the ilitek,ili9486 driver, with a correct init parameter.

(check that the init is the same as the people having success in https://forum.armbian.com/topic/11701-35-lcd-ili9486-with-orange-pi-zero/#comment-86679 )

 

 

With the correct init parameter, you configure the LCD to receive the data in the correct pixel format and ordering, to match the format sent by the CPU. Also, it configures VCOM, a key parameter that I think is electrical and not data related... read the LCD manual, I can't remember what it is for.

 

Search for ili9486 in the raspberry pi forum. Maybne someone figured it out already.

 

Here's how I used the mipi driver for the ili9488, based on someone's success with Raspberry Pi https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-207964

 

0
WDR_s

WDR_s

Posted
  • Author
Posted (edited)

LCD working, modifying it to work on the ili9341 drriver, with this DTS. Now it's time to get the touch working too.

  Reveal hidden contents

 

 

3f605d22-1d8e-4bda-bcac-ebc6e76ba370.jpg

Edited by WDR_s
0
robertoj

robertoj

Posted
Posted

Great :)

 

Does the opiz3 fit well under this LCD?

 

Are you still going to modify the DTS to plug the LCD directly on the OPIZ3?

 

There are 2 ways that the touch IC is connected: same SPI bus, and separate SPI bus... which one is it for this LCD?

If it is the same SPI bus, refer my ili9488 thread as a base

If it needs a separate SPI bus, see my ili9341 thread, and search for gpio-spi... I can't make this work in opiz3 yet, only opiz

0
WDR_s

WDR_s

Posted
  • Author
Posted

Before trying the touch, I wanted to test something else and it worked.
Now connected directly to the orange pi zero 3.
The ones above were with dupont wires, but I'm not sure if the touch will work.

 

  Reveal hidden contents

 

I had to change the CS, RESET and DC.

 

Before 

  Reveal hidden contents

 

After

  Reveal hidden contents

 

1db02f3c-2235-4229-95f1-df5ca86bed46.jpg

128c0fb8-b48d-465a-8f02-1760d9358478.jpg

0
robertoj

robertoj

Posted
Posted

Orangepi had the good idea to make the SPI pins match the Raspberry Pi pins :)

 

I read somewhere that the mipi-dbi driver doesn't have the rotate/rotation parameter... I guess I need a different initialization byte sequence for the LCD to do the rotation. Or does anyone know that there's a rotation parameter?

0

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept