Fruchtzerg

Yep so I got the Xorg running and it show the armbian screen but I have a similar error message in the Xorg.0.log as you got (==) FBDEV(0): Backing store enabled [ 199.430] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument For my bananapi the HDMI is deactivated if there is no cable on startup so my lcd display becomes fb0 maybe you are trying to start on the wrong device? But from here on I can only make some guesses since i have never before worked with Xorg (==) FBDEV(0): Backing store enabled [ 199.430] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument This seems not to cause any problem however connecting a mouse or a keyboard always fails. This is then probably related to the xorg config file which I created following the previously mentioned guide. Then I just execute sudo startxfce4 an I get the desktop on my display.

Don't do that it can cause you troubles with your spi, I also just learned that recently from Ryzer in the following post. Then why is your Chip Select (CS) connected to ground? Connect it to the Spi_Cs0 PC3 Pin 24. and then change Fragment@1 in the overlay to following: fragment@1 { target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status="okay"; cs-gpios = <&pio 2 3 0>; num-chipselects = <1>; This should work with the OrangePi for the nano pi you need to check and change the pins. For example the spi_cs pin on the neo3 ist the B0 and on the orange pi it is the C3 so for the neo3 the line in the overlay should be: cs-gpios = <&pio 1 0 0>; The Pios for dc and reset need to be changed in a similar way as well since the neo3 doesn't have an A3 pin so maybe take A4 and A6. Maybe also the targeted spi needs to be changed since some boards don't use spi0 on the 40 header pins. Last but not least good luck with your display

Hi just had a similar problem with my bananapi and the ili9341 and might have some helpful tips. 1. thing I did was to check if there's a driver for your chip honestly I am not sure if this is the case for the ili9488 locate ili9488 2. Load your overlay and check dmesg dmesg | grep -E ili9488 There you should see if the panel gets loaded during spartup or if there are any problems with the spi bus for example. 3. Post your overlay and wiring, I had a lot of trouble too understand the syntax fot the <&pio x y z > and got them wrong all the time. the orange pi cs(chipselect) for the spi4 is the gpio1_c4 so it should look like this <&pio 2 4 0> With 2 = (letter C)-1 4(comes from the pin) and 0 is low. at least that's how it works with the bananapi. Hope this can help a little bit

Now I will work on the touchscreen but that's a whole different topic

Finally it works or at least I can see the console here's the overlay I used sudo vim /boot/dtb/overlay/bananapitft.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragmen@0 { target = <&pio>; __overlay__ { display_pins: display_pins { pins = "PC4", "PA2"; function = "gpio_out", "gpio_out"; }; }; }; fragment@1 { target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status="okay"; cs-gpios = <&pio 2 3 0>; num-chipselects = <1>; display: display@0 { compatible = "adafruit,yx240qv29", "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&display_pins>; spi-max-frequency = <8000000>; rotation= <270>; bgr = <0>; fps = <10>; buswidth = <8>; height = <240>; width = <320>; reset-gpios = <&pio 2 4 1>; /* GPIO 24 */ dc-gpios = <&pio 0 2 0>; /* GPIO 25 */ debug = <3>; }; }; }; __overrides__ { rotation = <&display>, "rotation:0"; fps = <&display>, "fps:0"; debug = <&display>, "debug:0"; }; }; I did a stupid copy paste mistake and targeted spi1 insead of spi0 also manually compiling the .dts gave me warnings that didn't show up while using the armbian-add-overlay maybe that makes a difference as well but right now I am too lasy to check that. Thank you all for your help wouldn't been able to do it without it :)))