robertoj

Rebuilding all the image doesn't represent much more time than the time to recompile the kernel. I can't advise to download the linux source to the armbian SBC, because you would also need the armbian patches. One thing I use for debugging of DTS (and maybe linux kernel modules) taking control of GPIO is: sudo cat /sys/kernel/debug/gpio

Yes. Try the latest kernel. The latest is always the one with the most corrections (unless someone discovers an error). How do you select a H616 vs H618 kernel? I always select Unsupported Board > Orange Pi Zero 3

Urgently go back to the previous selection of dtbos in armbian-config. Just having 1 undesired dtbo may interfere with everything else. Then try adding: overlays=analog-codec in armbianEnv.txt And check the lsmod again

I am lost, confused by your explanation. Are you trying to use the Orange Pi zero 3 and RED LCD ili9488? The solution is: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208446 What did you mean by "booting to 16 bit"?

That photo tells me that you have the SPI and GPIO configuration right. Keep that. The completed solution for orange pi zero 3 and ili9341 is: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204672 Copy the parts within the ili9341:ili9341@0 {} section, while keeping your gpio

I know of a way to install a specific kernel version: sudo apt install linux-image-edge-sunxi64=25.5.1 --> installs linux 6.14.8 But how do you install specifically linux 6.15.4? Also, have you checked if the newest linux version requires a dtbo to be activated in armbian-config? If you still can: compare the output of lsmod under 6.15.4 and under 6.16.8

Can you share the DTS you used, to have success with the waveshare LCD? The only thing we need to extract from it are the gpio pins. And I am curious how you made a waveshare LCD work. The gpio formatting in your DTS looks very weird. Can you start with the DTS I shared? Share also which armbian and Linux version you are using. (I can only help with a Linux 6.11 or newer). If you only get a white LCD screen, it means that the LCD is not getting the right control signals in the correct pins. You don't need to try XFCE at this point. It won't work.

Can you try: * activate "analog-codec" within armbian-config * run: sudo apt install alsa-utils * run: alsamixer (text user interface to increase volume by individual output) * basic mp3 player: "sudo apt install mpg123" (instructions for orange pi zero LTS, but it may still work for opiz3) What do you mean by "image became distorted", and "kernel artifacts"? Can you build your own armbian OS with armbian build? (with Linux edge version)

Orima, Ubuntu 22.04 is recommended, but I have no problem installing armbian build in Linux Mint 22.0. I think Debian Trixie in your laptop is too new to have the right requirements and versions for armbian build. You can build Debian Trixie for your orange pi, with no problems. Don't try to fill all the parameters in a single command line. Just download the armbian zip, "git clone" it in a new directory. Then run "./compile.sh". You will be presented with all the text user interfaces to make your board selections, linux and debian versions, etc.

I would like to know too. The orange pi zero 3 has a GPU that's available for SIMD acceleration through the latest OpenGLES library, but I haven't had time for that: https://ai.google.dev/edge/mediapipe/framework/getting_started/gpu_support Try it in your opi5+, then run the mediapipe python examples. Then look for other neural network tasks that use the same NN engine: tensor flow light (tensor flow, pytorch will need a different method) Other examples: https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#comment-167001 https://opencv.org/blog/working-with-neural-processing-units-npus-using-opencv/

You dont need to cross-compile. You need to select the in-kernel-source option: https://www.kernelconfig.io/config_drm_panel_himax_hx8394 within the armbian build process. Then you need to create a DTS like: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/ And also dig through the experience in this thread: https://forum.armbian.com/topic/50963-dsi-display-does-not-work-on-raspberry-pi-5/#comment-216030 Send photo of the a33 and LCD

As a reminder: earlier this year, WDR_s had success with the waveshare 9486 LCD, with the ili9341 driver, but that was the fbtft old style driver. https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/#findComment-213110 I can't remember whether someone used the adafruit ili9341 driver (DRM) for the Waveshare ili9486/9488 LCD... anyone remembers? And a success case in the reddit community (warning Raspberry): https://www.reddit.com/r/raspberry_pi/comments/1lk18a7/comment/mzql8v4/

Yes, it is a custom Armbian image (no coding needed) Download the Armbian build system from github Select panel-mipi-dbi to be a kernel module (M) Choose Trixie, minimal (the greeter+desktops available in Armbian need to be pure wayland, but the greeter is not) Try the DTS and firmware file again I will try to explain better tonight Are you sure you meant Linux 6.1.31? My opiz3 is running 6.13.x or newer

I am glad that you made it work. However, it looks like you are using another Debian Distro for RiscV, not Armbian (not a bad thing) I am continuing the conversation over there

At this time, panel-mipi-dbi is the most universal way of using these SPI LCDs. Even the Raspberry community gets this recommendation (except for Waveshare LCDs). Bhupiister, does the MilkV Duo S really have 512MB RAM? How do you deal with that? I have used an orange pi zero LTS with 512MB of RAM with LXDE desktop in the past, but only with lightweight GUI applications. Does it really have a useful TPU?