robertoj

Thank you I just got a banana pi m2 zero and I am trying to get the ili9341 working with the drm driver. What is the latest Linux it is known to work? please share DST and pin connections I got my ili9341 LCD working in Linux 5.13.12, with this DTS... and I still can't use the drm-enabled driver Notice that I needed to swap height=320 and width=240, or else I get garbled display. It is working fine with 40 MHz.. The connections are the same as show in the post from June 2, 2023

I use USB-serial adapters. In my experience they have worked better than the Arm CPU UARTS. The debug UART is the most trusty serial port for maintenance.

Looks like UDC is a part of the g_serial that fails to load. Not an easy problem for me. Just revert to working OS, and reinstall your applications Similar problems: https://support.xilinx.com/s/question/0D52E00006iHmGwSAK/usb-udccore-couldnt-find-an-available-udc-added-gmassstorage-to-list-of-pendi?language=en_US https://stackoverflow.com/questions/65012555/how-to-enable-usb-gadget-mode-from-menuconfig https://github.com/gokrazy/kernel/issues/418 I hope i didnt lose this functionality in my orange pi zero

I can see my SBC's DTS with armbian-config > System > DTC ... is this what you meant? Then ctrl-O to save it in my home folder. It is almost identical to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/allwinner/sunxi-h3-h5.dtsi?h=v6.6.47

I cant see the problem XD In this latest-working setup, run "armbianmonitor -u" to get a snapshot of the boot execution, and copy the resulting link here. Also, show the result of "dmesg | grep g_serial" (the ko driver that enables the USB-serial-device function in the CPU. Try again with the Armbian_community_24.11.0-trunk.66_Nanopiduo2_noble_current_6.6.44.img.xz. Verify that the USB-serial-device function is working. Don't update, and run the 2 tests as above: armbianmonitor and dmesg|grep g_serial

I have a feeling that there's some difference between ili9341.ko (adafruit) and fb_ili9341.ko, in the way they handle GPIOs and SPI pins. fb_ili9341.ko handles the TFT perfectly in Linux 6.6.x (but it is desirable to use the DRM enabled ili9341.ko)

What is the latest linux that is known to work with ili9341.ko? Does it get you h264 acceleration? Is it possible to get touch events with a second chip select?

If still not working, install the newest OS image in a different microSD card, verify that you have the USB-serial function. Then check the differences in armbianEnv.txt, and the result of "lsmod", against your old microSD. If you succeed or not, post your results here, because that's how we build up the knowledge base.

Make sure that /boot/armbianEnv.txt is the same from the time it was working, to what it is today (the line “overlays=“)

I tried this DTS, to try to declare, reserve, or pin mux the chip select (I don't know what the added block does) The TFT screen did not work (100% white), but at least I see more pins used in pinctrl (PA2, PA18)

Check that the environment lines, plus the execstart from the service file, do what you want from “root”, since the service does not specify a user or specify your user, and try it with your user see what shows up with “journalctl -u x11vnc” (log) Here's another x11vnc server istructions: https://wiki.archlinux.org/title/X11vnc https://jasonschaefer.com/setup-x11vnc-server-with-systemd-auto-start-up/comment-page-1/

you need to configure WIFI with netplan setting files. See https://docs.armbian.com/User-Guide_Networking/ and apt install wpasupplicant if you don’t have it

I noticed the second serial port in the 26 pin connector it is in the same pins as SPI1

Investigating why fb_ili9341 works but ili9341 does not. With this ili9341-spi1.dts, fb_ili9341 gets loaded and TFT shows images perfectly here's the armbian-monitor -u result https://paste.armbian.com/vimetexiqe Other results in this successful DTS: When I change the DTS to (notice the differences in compatible and rotate/rotation lines) The TFT remains 100% white. Here's the armbianmonitor -u: https://paste.armbian.com/segulokeso Other tests in this failed attempt: In both cases, I used sudo armbian-add-overlay ili9341-spi1.dts, and my armbianEnv remained the same:

In “minimal” images, there’s no armbian-config to set up networking easily you need to configure it with netplan setting files. See https://docs.armbian.com/User-Guide_Networking/ and apt install wpasupplicant if you don’t have it

I tried kernel 6.6 and I only have luck with fb_ili9341, not ili9341 (adafruit’s drm driver) Is it drm_mipi_dbi.ko the part that actually handles the SPI port? Is there a manual to see the parameters, or a log file? i will include armbian-monitor -u soon my findings are in my thread https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/ To those who are enjoying a drm screen in their ili9341, are you also getting h264 acceleration? Are you also getting the touch events with a second chip select? Why do some DTS have this (in bold) part in their fragment0 (Ryzer May 30, 2023), and later versions of the DTS don't have that part? Well, I tried this DTS and I have the same result: white TFT

Thank you! The first serial port is the debug serial port (probably UART2), the second is UART5 in the 26 pin terminal. Are you able to use UART2? I think it would only be owned for boot up messages and a bash session.

Just to keep track of my progress: OrangePi Zero can drive a ILI9341, with this ili9341-spi1.dts, with the fb_ili9341.ko driver (not the drm driver). Works on Linux 6.1.104 and Linux 6.6.44 Pin connections inside the DTS code: and this armbianEnv.txt

As a sanity check, I tried this positive experience, and my TFT is working for the first time https://4pda.to/forum/index.php?showtopic=782242&st=5060#entry112401076 (using google translate) I copied the 3 DTS in that forum post, used them, and the TFT showed a black screen, with login prompt With linux 5.15.93, from Armbian_23.02.2_Orangepizero_jammy_current_5.15.93 I need to check what is being done here, and transfer it to my best experience with linux 6.1 or 6.6 quick check: sudo fbi -noverbose -a -t 10 -T 2 -d /dev/fb0 mafalda.jpg That spi_ili9341.dts in the 4pda forum works for orangepi zero, linux 6.1.104, although it only uses fb_ili9341, not the drm driver. ALSO: when I remove "tve" (NTSC) from the overlays, there's only /dev/fb0 (not fb1), which is the TFT LCD, and the boot messages appear in the LCD When I edit my DTS to look more like the "viroid" DTS, when in Linux 6.1.104, the TFT stays 100% white. Then, when I remove the "adafruit,yx240qv29", it works again Someone with a similar problem: https://forums.raspberrypi.com/viewtopic.php?t=358240#p2165609 https://github.com/notro/tinydrm/issues/14 i will try with a newer kernel, maybe the driver improved

Thank you for the suggestions... I rebuilt my armbian image for orangepi zero to linux 6.1.104, just to make it more similar to everyone else's setup I had better success with your latest dts, with my spi1, and GPIO pin modifications, without doing the simplified version On reboot, I tested that devices were configured well again: dmesg|grep ili, lsmod|grep ili, cat ...spi@1c69000/status, cat ...1c20800.pinctrl/pinmux-pins Then, I executed: apt install xinit xterm xauth x11-apps xserver-xorg lightdm sudo su - FRAMEBUFFER=/dev/fb1 startx But my TFT stayed 100% white. Here is my xorg log I was also doing tests with the DTS from https://ryjelsum.me/homelab/xpt2046-ili9341-opi-zero/ with a little better result: the TFT turns gray. The x11 server started with no errors, but the TFT stayed gray With either DTS, I see that there is no references to /dev/fb1, in xorg.log I also tried "sudo con2fbmap 2 1", it didn't work I am going to look for very old OS image ,where it is known to work with my SBC

Thank you!

Ok, I finally have a newly built Ubuntu Noble, with ili9341.ko in the /lib/modules/... folder I added the DTS again: I rebooted and there was no action in the TFT display. Also, nothing in dmesg indicated it that ili9341 was attempted to use... neither "spi" was found in dmesg I saw that the pins I want to use for SPI are not in use: Also, checking the proc, shows that both SPIs are disabled: Finally, I am able to load the kernel module, but it does nothing: Now I am trying replacing "spi0_pi_pins" with "spi1_pins"... New progress: spi1 is now enabled When I tried this simplification of my DTS: Then, finally the ili9341.ko gets loaded at boot: But the dmesg is referring to spi0.0... and I need to use spi1.0. The TFT screen shows nothing. Is there another thing I can test? Update: It seems that panel-ilitek-ili9341.ko is the part that wants to access spi0... is there any way to exhort it and use spi1? driver c code in: https://codebrowser.dev/linux/linux/drivers/gpu/drm/panel/panel-ilitek-ili9341.c.html

Thank you Ryzer... I left my home, with the PC building an armbian image ili9341 is available in the linux menuconfig, activated by default. However, I didn't find the ili9341.ko in the armbian-provided image (Noble)

Are you using the latest Debian Bookworm Minimal, or the more complete Ubuntu Jammy Server? In either case, post the result of "lsmod". Run "ip a" and see if there's any "wlan" interface. Run (root) nmtui to try to activate wifi. If nmtui is not available, run "apt install network-manager". Or try it "armbian-config" (apt install armbian-config) If you are using Debian Bookworm, try with Ubuntu Jammy instead... it worked for me yesterday, with Orange Pi Zero and wifi.

I might need to use the serial port pins, instead of USB-serial adapters. What did you activate in system>hardware? (or post your armbianEnv.txt) Can the 2 serial ports work with 230400 baud? (lidar snesors) Can they work with pyserial?