robertoj
-
Posts
561 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by robertoj
-
-
All this time, I thought you were using a custom H618 board hardware. Now it is clear to me, that you have an Orange Pi Zero 3,
In armbian build, make sure you don't add any configuration files. Just do "./compile.sh" and when you get the menu for board selection, press the button "Unsupported/CSC" (or something like that).
The text menu will turn red. Press OK and you will see a list of more Linux boards. Press "P" to quickly scroll down, then "UP" to find Orange Pi Zero 3.
Then choose the option for Linux edge, and choose that you want to configure linux.
-
Can you get an orange pi zero 3? As a hardware beginner, you need a very stable, well known linux board.
-
Alright
Did you ever make this LCD work with your H618 motherboard, with another kernel driver?
-
Try the X11 windowing manager or the Wayland compositor without lightdm (or another display manager).
-
On 12/11/2025 at 3:27 AM, vd3 said:
I am talking about hdmi audio. Analog audio works fine on both kernels. HDMI-Audio doesn't work in 6.16.8 kernel. I'll keep using v25.11.0-trunk.190 with kernel 6.15.4 for now since HDMI works there. I might experiment with those configs later, or perhaps it will get fixed in a future version. Thanks.
Posting this interesting event, in case someone can see why it worked:
Banana Pi M4 zero (H618) gained HDMI audio when upgrading to Linux 6.12.30
https://forum.armbian.com/topic/50773-bpi-m4-zero-hdmi-audio/
But in this thread, there's a report that upgrading to 6.16.8 (from 6.15.4) lost HDMI audio
-
Can you clarify that you made a custom H618 board
?? (not exactly Orange Pi Zero 3?).
If I remember correctly, you had previous success with an ili9341 and the same linux board?
You need to compare the DTS that worked for you (with ilitek, ili9341, right?) and the new DTS you are trying to modify (with panel-mpi-dbi, for ili9488).
Make sure you haven't changed the GPIO in the DTS, and the connections in the LCD and your Linux board.
If the ili9341 was working for you with the H616 armbian configuration, changing to H618 might need changes in the LCD DTS from that change.... to make those SPI pins to be addressed correctly.
That previous H616 armbian configuration... what Linux board was it meant for?
Change back to the configuration that made your board work with the ili9341.
-
Now that you can replicate the crash anytime. Right after it crashes:
$ dmesg
$ journalctl -u lighdtm
Also, try another application that will use the LCD continuously, without starting X11:
$ mplayer -vo fbdev2:/dev/fb0 videofile.mp4 (use a 320x240 approx video, so it will be smooth without hardware acceleration)
If it works, then maybe X11 is the problem, not the LCD driver.
I wish more people switched to 100% Wayland in their HDMI monitors and LCDs. I have a method.
If you want it too: https://forum.armbian.com/topic/55882-critique-or-improve-my-method-to-get-a-lightweight-labwc-desktop/#comment-227469
-
Check out the learning experience in this thread:
In an ssh session, do this: $ tail -f /var/log/Xorg.0.log
And see what happens when the X11 server crashes
-
I am glad you made the LCD work with a DRM driver
Three clarifications:
the driver panel-mipi-dbi is provided in the OS image you write in the microSD.
The DTS is something you get from this thread, and install it with armbian-add-overlay.
Kungfupancake provides a txt or a bin file that defines the configuration sent to the LCD, when the kernel driver starts, and instructions on how to install it.
The panel-mipi-dbi driver (the recent versions I tried) does not support X11, and you need 100% Wayland, and 0% X11
See my thread to install rpi-greeter (one of the 2 login managers that work with Wayland), and Labwc:
-
Yes, One/some/all of those kernel configs may be needed for analog audio.
Start with the activating configs that correlate with the missing kernel modules
* snd_soc_sunxi_machine
* snd_soc_sunxi_ahub
* snd_soc_sunxi_ahub_dam
If it still doesn't work, activate all the 2 other linux kernel configs: internalcodec and aaudio
-
That's good news
You are using lightdm with the default greeter GUI, right? That means that your LCD driver can support X11. Are you still using adafruit,yx240qv29?
Maybe the lightdm service is getting confused about which display to use.
What do you get with: $ ls /dev/fb* ?
Make sure that you don't connect an HDMI LCD at the same time.
Which desktop(s) do you use? XFCE and Gnome?
-
If you have X11 installed, then boot with only the LCD and try:
sudo systemctl stop lightdm (the greeter, which requires X11)
sudo startx
Show me what errors you see
If you have Trixie, boot with only the LCD and:
sudo apt install labwc
labwc (as a regular user)
Large language models are just google on steroids. They can only give good answers, if hundreds of people have typed and published solution similar to your problem.
-
Jeffrey,
Is your DTS using this in the "compatible" line: adafruit,yx240qv29 ?
Are you trying to use an X11 or Wayland greeter and desktop? (I can't remember what commands to use to check that right now).
I didn't know about X11 problems with adafruit,yx240qv29 (only with the other driver panel-mipi-dbi)
There's no available image to download with all the required parts.
-
Yes, that is the correct sequence of actions:
1. Build armbian minimal with panel-mipi-dbi kernel module
2. Use DTS so that the kernel links the GPIO, SPI to the panel-mipi-dbi kernel module
3. Use the bin file (originally provided by Kungfu pancake) <-mandatory, not optional
4. If you see console text successfully in the LCD during boot, you have successfully installed your LCD
5. Tell us here, for the next step in GUI installation
The "greeter" is the graphical login screen. Labwc is the wayland-based compositor and window manager (I think).
-
On 12/6/2025 at 3:03 AM, Patrick 42 said:
And I try to not be annoying here, but I am a bit lost. What is the common method for driver debugging/development in armbian?
I mean how to recompile the kernel without rebuilding all the image?
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:
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:
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://opencv.org/blog/working-with-neural-processing-units-npus-using-opencv/
Orange Pi Zero 3 ili9486 TFT LCD
in Allwinner sunxi
Posted · Edited by robertoj
If you use your own boardconfig file, or edit another boardconfig file, you may be missing some configs or device tree overlay, and make problems in configuring SPI and GPIO pins.
I always use boardconfig that's included in armbian-build, specifically for Orange Pi Zero 3, by following the text menu, and not editing any file.