raufasertapete

I have a similar issue with my Orange Pi zero LTS and a waveshare clone. I have worked already several days on the problem but it looks like that I am not able to communicate with the ili9486 over SPI. I think the problem is, that I am somehow still using SPI Bus 0, but I have to use SPI Bus 1. My Device tree overlay looks as follows: /dts-v1/; /plugin/; / { compatible = "xunlong,orangepi-zero\0allwinner,sun8i-h2-plus"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <&pio>; __overlay__{ pins: tft35a_pins { pins = "PA1\0PA7\0PA19"; function = "gpio_in"; }; }; }; fragment@2 { target = <&spi1>; __overlay__ { #address-cells = <0x01>; #size-cells = <0x00>; disp: tft35a@0 { compatible = "ilitek,ili9486"; reg = <0x00>; pinctrl-names = "default"; pinctrl-0 = <&pins>; spi-max-frequency = <16000000>; txbuflen = <32768>; rotate = <90>; bgr = <0>; fps = <30>; buswidth = <8>; regwidth = <16>; reset-gpios = <&pio 0x00 0x07 0x01>; dc-gpios = <&pio 0x00 0x13 0x00>; debug = <0>; init = <0x10000f1 0x36 0x04 0x00 0x3c 0x0f 0x8f 0x10000f2 0x18 0xa3 0x12 0x02 0xb2 0x12 0xff 0x10 0x00 0x10000f8 0x21 0x04 0x10000f9 0x00 0x08 0x1000036 0x08 0x10000b4 0x00 0x10000c1 0x41 0x10000c5 0x00 0x91 0x80 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 0x100003a 0x55 0x1000011 0x1000036 0x28 0x20000ff 0x1000029>; }; }; }; __overrides__ { speed = <&disp>,"spi-max-frequency:0"; txbuflen = <&disp>,"txbuflen:0"; rotate = <&disp>,"rotate:0"; fps = <&disp>,"fps:0"; bgr = <&disp>,"bgr:0"; debug = <&disp>,"debug:0"; }; }; I deleted everything regarding the Touch controller for now to avoid dealing with CS1. I just want to get the display to work. My ArmbianEnv.txt looks like this: verbosity=1 bootlogo=false console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 i2c0 uart1 tft35a param_spidev_spi_bus=1 param_spidev_spi_cs=0 param_tft35a_rotate=90 param_tft35a_debug=1 rootdev=UUID=d522be3f-9ac0-489b-9d79-500c38e89c86 rootfstype=ext4 fbcon=map:1 hdmi_force_hotplug=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u dmesg | grep spi gives me: [ 13.191545] [drm] Initialized ili9486 1.0.0 20200118 for spi0.0 on minor 0 [ 15.079945] ili9486 spi0.0: [drm] fb0: ili9486drmfb frame buffer device This output looks like that the IC is connected to SPI0, but I have to use SPI1 on the OPzero. I am referring to &SPI1 in my dts, so I am wondering where else I do have to select the Bus. When I use the spi-dev overlay with the Option spidev_spi_bus=1 the Output for dmesg | grep spi says that I am using SPI-Bus 1, but then I have some error that the CS 0 is already in use. according to: dmesg | grep fb [ 0.000000] Kernel command line: root=UUID=d522be3f-9ac0-489b-9d79-500c38e89c86 rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=22563e30-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 3.919660] sunxi_fb_mem_reserve=16 [ 15.079945] ili9486 spi0.0: [drm] fb0: ili9486drmfb frame buffer device [ 15.143228] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 15.154104] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. A new /dev/fb0 device is registered, but the display stays white when I try to connect a console with con2fbmap 0 /dev/fb0 and activate the binding of the vtconsole. I get the same driver error as @olehs when I type sudo startx. I am also wondering why I can't change the verbose level of fbtft when I change the debug level from 0..7 in the dts. Thank you for your advice!