Dandaman46

@Sma ads7846 is a touch screen driver module.

Hmmmmm interesting. You are using ads7846 right? I'ved Confirmed the Linux 5.15.93-sunxi works, and the latest doesn't. If we could work backwards to different version of the kernel we might be able to find the offending code change.

I haven't been able to get it working on the nanopi neo air yet.

The only notable difference I could see was this line from dmesg Not working 6.6.12 ads7846 spi0.1: touchscreen, irq 80 5.15.63 working ads7846 spi0.1: touchscreen, irq 113 Perhaps there is a mapping issue going on.

Thanks for sharing your journey. I've got to the exact same spot with the new kernel. SPI ADS7846 device connected and recognized with evtest, just no interrupt is trigger when pressing the screen. I am using a custom build of 6.6.12-current-sunxi. with all else being identical to my previous working build of 5.15.63. I compared the the output of gpioinfo and all the gpio connections seem to be configred correctly. root@nanopiair:~# evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: ADS7846 Touchscreen Select the device event number [0-0]: 0 Input driver version is 1.0.1 Input device ID: bus 0x1c vendor 0x0 product 0x1ea6 version 0x0 Input device name: "ADS7846 Touchscreen" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 100 Max 4095 Event code 1 (ABS_Y) Value 0 Min 100 Max 4095 Event code 24 (ABS_PRESSURE) Value 0 Min 0 Max 4095 Properties: Testing ... (interrupt to exit) ..... more crickets Perhaps an update in the kernel has broken something? Any tips would be great I've been stuck for a while on this one!

The build system is in a bit of flux at the moment. The documentation hasn't caught up all the way. Can you use the docker build process instead? Ensure you have docker installed, download the git repo and run the following. ./compile.sh build BOARD=nanopiair BRANCH=current BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=bookworm

Are you using nmcli to create your access point? If not, what is your process for setting up the access point?

Is this still the case with the debian build?

Thanks for the clarification!

The release blog for Suni mentioned Fast and Safe Updates Is this referring to the streamlining of the apt-get or apt packages, or is there a new update to be used? I looked through the release notes and other sources and couldn't find anything. https://www.armbian.com/newsflash/armbian-23-05-suni/ Fast and Safe Updates: Our streamlined system allows for fast and safe updates, ensuring that users can easily stay up to date with the latest improvements and security patches.

Just bumping this, delighted to see boot splash start working after an apt-get update, would like to change the image though, any advice anyone?

Yeah, that's the one. Hmm it has been a worthy adversary I see. I made a seperate thread with some more details but no replies yet. Any assistance would be appreciated! It's interesting we seem to be the only two people on the internet trying to get this working and we are both from the Melbourne area! I'll buy you a coffee next time I'm in town.

Hello, I have been trying for a few weeks to get this LCD dsiplay (Store Wiki) to work with the NanoPi Neo Air. The display driver required is apparently the ST7789V. I was able to get the pair to work using this image supplied by FriendlyArm. https://drive.google.com/open?id=1CAKS1BNGk6vbAsPy5HmeGdO4FPZkvksz However, the OS introduces other issues to my setup and I don't want to depart from our beloved Armbian. at last I know the hardware working and wired correctly. I think I need a custom kernel, but I'm not sure. This thread mentioned the display I am using and talked about building a custom kernel. I got the build env up ran a kernel build but I was not able to find any drivers relating to the ST7789V. Any advice on how I can get this working? I can get the fbtft and the fb_st7789v drivers running but they do not detect the lcd display. In case you are interested in the back story this is what I have tried so far: Add drivers to currently running kernel (was 4.1.x somthing at the time) according to instruction here. https://forum.armbian.com/topic/7119-guide-how-to-configure-tft-display-touchscreen-on-orange-pi-pc-mainline-kerneel/ Copy kernel files from FriendlyArm OS Copy Armbian rootfs to friendlyArm OS image (almost worked) Found out that fbtft_device name is no longer supported Tested two incompatible fbtft driver alternatives https://github.com/bitbank2/bb_spi_lcd/tree/master/examples/spi_lcd_demo Some rasberry pi only one. Found that I can build custom kernels fairly easily! https://docs.armbian.com/Developer-Guide_Build-Preparation/ EDIT: Had trouble adding the wiki link. Here it is: http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_2'8_SPI_Key_TFT

Hi @Exie trying to get the same friendly arm tft to work. What driver did you select? Did you have to install any additional software? Burnt about 2 weeks on this so far.. I have tried all sorts of kernel/os/driver combinations. Any tips? I did try to build a custom kernel but couldn't find any reference to a tft/spi/ST7789V driver.