robertoj

drivers/net/wireless/rtl8192eu/hal/phydm/phydm.c seems like a linux source file... maybe this warning was shown AFTER uboot finished compiling?

Can you compare the device tree between your working system, and from the freshly installed 25.2.3/6.12.22 (write the img in a new microSD) View your device tree with: #(root) dtc -I fs -O dts /sys/firmware/devicetree/base (you need to find out which driver handles the audio, and search for that driver name in the working device tree) Also, check differences in armbianEnv.txt Also, check differences in ".config" in the /boot/ folder (specially anything related to audio) Also check the contents of "dmesg", searching for the audio driver name

The orange pi zero LTS has analog video under Armbian, because: * the LibreElec project had kernel patches that added the driver code for the same SBC * I carefully modified those patches so they would fit the Armbian version of Linux, correct all compilation errors, and all errors I saw. It was a month long effort If you see that Radxa has video output in the official distribution, do you see any source changes to enable it?

Is anyone using the orange pi zero LTS or 3, with any ilitek LCD, with spi-gpio driver? I had my LTS working with ili9341 and spi-gpio last year... but the touch is not working now... I think I changed the wiring or the DTS in the running system but I can't tell.

Does anyone know if the spi-cpol and spi-cpha parameters are applicable in the ads7846 part of the DTS? I have seen cpol in an LCD discussion here: https://forum.armbian.com/topic/38896-orange-pi-lite-problem-with-latest-firmware/#findComment-191293 I am running out of ideas to try to make touch work... I can also try using gpio-spi.ko I need to check that the IRQ pin is changing from 3.3 to 0V... if I connect a LED to it, will it be a 0.0V pulse or held low while I press my finger? I learnt that /proc/interrupts can tell me if the IRQ input is seeing something... and I can see the number increase each time I press my finger on the screen: (see the line that ends with ads7846) https://forums.raspberrypi.com/viewtopic.php?t=187023&start=25 Is there any way to debug the ads7846 kernel module? I have seen this J1jumper mentioned here: https://forum.arduino.cc/t/solved-3-5-tft-not-stable-at-power-up/684536/19 "if you jumper J1, you feed it with 3.3V" I power it with 3.3V and the J1 contacts are disconnected... so maybe the 7846 is undervolted... does anyone have experience with this?

I received my new LCD today. It is a 9486 but luckily it worked with my 9488 dts HOWEVER: The touch xpt2046/ads7846 is not sending any events…checking with evtest… same dts works with the ili9488 4.0” I already tried changing the GPIO polarity (level and clock transition) has anyone worked with any of the red 3.5 lcd ili9488 or 9486

I don't think increasing the SPI clock can help Try adding "BGR=<1>;" under the rotation line... this works for the ili9341, but i dont know about the driver that you use.

Great find.... this will be useful for me very soon

Try again with Linux 6.10 or older if you have an armbian img. Two things I found needed for linux 6.12+: 1. Define the pinctrl-names and pinctrl-0 parameters 2. MAYBE: rebuild Armbian in your computer, with one less Armbian patch As seen in: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-216779 In this thread, you can see how I detected miscofigurations of the SPI GPIO: https://forum.armbian.com/topic/50418-dont-use-kernel-61216-on-sunxi64/page/2/#findComment-216924 WDR_s: did you try upgrading to Linux 6.12? (you could get H264 acceleration if you upgrade)

pithecanthrope, That DTS is specific for the raspberry pi lcd... not for the red pcb ili9486. Do you have that? You can name the DTS any filename, for example ~/ili9486/ili9486-35.dts cd ~/ili9486-35 sudo armbian-add-overlay ili9486-35.dts The command will also add it to armbianEnv.txt Make sure to not add any other overlays related to SPI It is very nice that the raspberry pi lcd doesn't need us to fabricate a custom cable, just plug it in the correct orientation. Are you using Linux 6.12?

Start with a minimal image: no X11, no desktop sudo systemctl list-units --type=service --all Find those services you don't need, and "sudo systemctl disable <service>" Is buildroot a nice experience like armbian?

I have an IoT project that uses an SPI LCD (480x320), showing 1 full screen application on top of X11, which starts automatically, almost in kiosk mode. Is it worth a lot trying to switch to Wayland? I have 2 roadblocks, which I am trying to drill through: * tkinter app re-write in pyqt * starting from a minimal armbian image, and install the bare minimum to have wayland and start the app Solid advantage: * Future proofing the product I have these preconceived advantages: * less resources needed: my application is fine with an OrangePi Zero 3 with 1 GB RAM, I don't want to upgrade RAM * faster startup (now I need to wait 1 minute from power-on to app ready to use, reducing it to 30 seconds would be nice) I know that I can't expect these advantages, since I use SPI instead of HDMI or DSI: * 30 FPS * No frame tearing But really, my main objective is faster startup: will Wayland help me with that? (without having disadvantageous side effects)

Can you connect with a USB-serial adapter, then run dmesg and look for error messages? Maybe the power supplies are not isolated and by some bad luck, they are trying to push electrons to each other on the 0V wire. Try using the SSD without its own power supply.

I will get an ili9486 soon, but it is different to yours: it has a red PCB and does not have the serial-to-parallel chip like those made for raspberry.

Interesting effect of changing the ili9488 10cm (4.0 inch) for a 9cm (3.5 inch) LCD, same resolution https://a.aliexpress.com/_mMKRqan https://a.aliexpress.com/_mqk0Qbv (I bought a similar with touch) maybe I need a different spi frequency update: I changed 40 MHz to 60 MHz and my new LCD works perfectly:) update: with 60 Hz, full screen video has a lot of noise and distortion. With 70Hz, there’s only white dots on black background with 50hz, the console shows wrong colors and video is white noise with 30 hz, console text and video are ok… but video looks 10 fps the touch panel in the smaller 9cm LCD does not work. Do not buy it!

Nice find I don't know why those changes happen... but we as bleeding edge linux users, must be aware of those things (by searching in the armbian forum... or sometimes in the raspberry forum)

With these instructions, you may get UART5 in ttyS1 https://forum.armbian.com/topic/43718-orange-pi-zero-3-issues-with-gps-on-uart/ https://forum.armbian.com/topic/44034-using-gpio-ports-on-orangepi-zero3/#comment-201030

The touch part is actually I2C, so the many DTS examples here will get you close to displaying stuff on the LCD, but not touch. Pay attention to this thread in the raspberry forum... they have a LCD similar to yours 50% working (you will have to modify pin numbers to make it work with opiz2w) https://forums.raspberrypi.com/viewtopic.php?p=2310966#p2310966

Danubio, build Armbian with latest Linux kernel 6.13, and see this old instruction I made for the opiz-lts audio… maybe it will help you for the opiz3 https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md#10-activate-and-use-analog-audio i just confirmed that opiz3 can play audio (alsa) with Linux 6.13.11. mpv.conf must contain the line: audio-device=alsa/plughw:CARD=Codec,DEV=0

When I start from scratch with TheGoing repo, linux 6.13.7, I apply my DTS, copy my firmware, and I get this DT (snipped in the area that counts) And the LCD works. And when I start from scratch from the Armbian repo, linux 6.13.11, I apply my DTS, copy my firmware, and get this Device Tree: But the GPIO pins PC7 and PC14 appear unclaimed (as seen in previous post), and the LCD remains white. The linux build configs are practically the same (side in 6.13.11 has the error in SPI configuration) I found that the TheGoing repo has a two less patches applied... the zero 2w seems more relevant IMPORTANT: I just added "-" before "patches.armbian/arm64-dts-sun50i-h618-orangepi-zero2w-Add-missing-nodes.patch" in the: build/patch/kernel/archive/sunxi-6.13/series.conf file, and I finally have the ili9488 LCD working with my ili9488-ads7846 DTS My SBC is the OrangePiZero 3, and I select that specific SBC in the menuconfigs after starting "./compile.sh"

Help! My DTS, which used to work with 6.13 and 6.12 from the unofficial repo's from NickA and Going... are not working in the official armbian linux 6.13 This is an issue of not owning the DC and RESET pins, as seen in PC7 and PC14 need to show this: pin 71 (PC7): GPIO 300b000.pinctrl:71 pin 78 (PC14): GPIO 300b000.pinctrl:78 dmesg shows this error: $ dmesg|grep spi [ 1.911366] sun6i-spi 5010000.spi: Error applying setting, reverse things back [ 1.911650] sun6i-spi 5011000.spi: Error applying setting, reverse things back [ 1.917726] sun6i-spi 5010000.spi: Error applying setting, reverse things back [ 1.918005] sun6i-spi 5011000.spi: Error applying setting, reverse things back ... The DTS I used is: I think anyone with Linux 6.13 (armbian official) can try this DTS without an LCD connected to the orange pi zero 3... at this time, I only need that the PC7 and PC14 are owned by the SPI driver.

I confirm I got my Orange Pi Zero 3 playing hardware decoded videos: * armbian official, built with the EDGE kernel 6.13.11, xfce environment * followed all the instructions in the first post of this thread * connected to a 1080p LCD monitor with HDMI * MPV plays a 1080p video with frame "tearing" with a window 800 pixels height. CPU usage 25% in all 4 cores * 720p video can be resized to almost full screen, but then it suffers tearing when resized larger. 10% to 15% CPU usage. * with all videos, when I try to play full screen, MPV plays the video every other frame, and shows a static frame (the frame that was showing when I double-clicked for full screen) UPDATE: without X11, to play videos on tty1, with an ili9488 LCD * check what drm connections are available: * find your connected DRM device, and run mpv from SSH $mpv --vo=drm --gpu-context=drm --drm-connector=SPI-1 myvideo.mp4 (+) Video --vid=1 (*) (h264 1920x1080 60.000fps) [vo/drm] VT_GETMODE failed: Inappropriate ioctl for device [vo/drm] Failed to set up VT switcher. Terminal switching will be unavailable. VO: [drm] 1920x1080 yuv420p {plays video in tty1 } A 360p video uses 15% in all cpus. 720p video->25% in all cpus. 1080p video->100% in all cpus It might be related to the fact that the SPI port is not hardware accelerated for video, like HDMI... but I will keep trying to get results similar to 720p... like scaling and changing framerate from the mpv command Press ctrl-c and mpv will exit

I tested NickA's armbian build, so I could get the cedrus+v4l2 improvements that would allow me to get h264 acceleration... but in my ili9488 I got these playback errors and 100% CPU usage with a 720p video in a 480x320 screen I will try with an HDMI LCD now: (typed command from an SSH session) The HDMI LCD just turns black. But I think this may be because I am using openbox... I think everyone else is using xfce UPDATE: I installed the xfce environment, selected it, and I still get a black LCD screen... I will try with the armbian official... does it now offer linux 6.13 with the edge kernel option?

The DTS I posted before works for up to Linux 6.11 If anybody wants to use ili9488 in Linux 6.13, this is the modified DTS to use: Notice the new lines commented with "new for linux 6.13" Remenber that the firmware file must be named panel-mipi-dbi-spi.bin and copied to /lib/firmware I will test this with Linux 6.12 shortly... update: it works with linux 6.12.20 (The Going's repo) and 6.12.11 (NickA's repo, self built, not downloaded image) For reference, I discuss the process of finding this solution here: https://forum.armbian.com/topic/50418-dont-use-kernel-61216-on-sunxi64/page/2/#findComment-215554 Update: this DTS works for Linux 6.12 and 6.13... but make sure to add "-" before "patches.armbian/arm64-dts-sun50i-h618-orangepi-zero2w-Add-missing-nodes.patch" in the build/patch/kernel/archive/sunxi-6.13/series.conf file then build your OS with ./compile.sh

Thank you for the suggestion At first it didn't work... then I tried: fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; pinctrl-names = "default"; pinctrl-0 = <&spi1_pins>; cs-gpios = <&pio 7 9 0>,<&pio 2 15 0>; // PH9=CS0 for lcd, PC15=CS1 for touch ... Because I use non default CS pins The ili9488 LCD is now working in linux 6.13 ... the touch screen is also working with the evtest command I will post the whole DTS in my ili9488 thread