robertoj
-
Posts
546 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by robertoj
-
-
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/
-
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
-
On 12/2/2025 at 5:13 AM, Bhupiister singh said:
I am not using that distro at the moment as its not fulfilling my purpose at the moment so still evaluating. Milk v has a small core for running arduino application and then Linux and arduino can talk, this lets real time task run on small core, which is what i want. That distro is using small core for Image signal processing, which i do not want.
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
-
8 minutes ago, Bhupiister singh said:
Making it work with panel-mipi-dbi is completely new to me. I hope ill be able to make sense out of it.
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?
-
There's a 4 inch RED ili9488 in aliexpress. VERY RECOMMENDED.
It may be shown as ili9486, correctly or incorrectly, but it doesn't matter. I have seen both ili9486 and ili9486 work with the same panel-mipi-dbi driver, settings and init firmware.
At least in orange pi zero 3, some pins worked fine for GPIO and others didn't.
Also make sure to use the default chip selects in your MilkV Duo 5, and not try to change that.
Also share what Armbian and Linux version you are using.
-
Deactivate spi-dev in the armbian-config.
That DTS is only used if you want to run a userspace program to talk to the LCD.
In this case, we want the linux kernel to talk to the LCD, so we only need to use the LCD driver (ideally not a FBTFT. DRM is preferred)
-
6 minutes ago, Bhupiister singh said:
What about your experience with ST7796? I have one with red pcb. Even this one is not working for me. Tried different dtb and .c files.
Did this work for you ever?I only have RED ili9341, ili9486 and ili9488
I don't have time to look right now, but search the Raspberry Pi forum and there's a nice thread with just the RED LCDs, st77** and iliteks working with panel-mipi-dbi driver
Then, when you find a solution over there, post the link here.
Your objective is MilkV Duo S with Waveshare ili9488 LCD, right?
-
The waveshare clones may not work with panel-mipi-dbi, because these LCDs are not purely SPI.
They have a SPI-to-parallel chip which allows the LCD panel to work in parallel mode.
Maybe they will work, but I don't own any waveshare LCD.
There's a driver inside the kernel for waveshare SPI LCDs (ILI9486_DRM or something like that), but I still haven't seen any example of anyone using it.
-
On 11/30/2025 at 2:08 AM, Bhupiister singh said:
But trying to make ILi9486 work is next to impossible for me.
I don't own any waveshare LCD.
I am not sure what to suggest, except that I believe it will only work with a "ili9486_DRM" (can't remember the exact name) driver ko.
It is made explicitly for waveshare SPI LCDSs, and you must activate within the armbian build script process.
-
5 hours ago, Orima said:
Can I use your DTS to connect to my Orange Pi Zero 3 and 3.95" ILI9488 display? What issues might I encounter? Can I use the pins described in the DTS file?
I've read your comments on this forum thread.
No, it wont work.
I have made another thread just for the orange pi zero 3 and ili9488
Change the GPIOs to match your wiring and connections.
-
I am glad that you have the first 15% done: get your kernel module in the OS, and the uboot accepting the DTBO
Now you are stuck in correcting the DTS, so that it configures the SPI pins correctly.
My last advice for you (through this stage) is: make sure you don't have anything else using SPI pins. Deactivate "spi_dev" in armbian-config.
Since I only had experience with H3 and H618 CPUs, I can't help with confidence. Post your question in the appropriate Rockchip forum section for up-to-date reliable advice.
I can say that Radxa/Waveshare DTS is very out of date: it uses the fb_ili9486, which is "framebuffer" (poor fps), instead of the modern "DRM" display driver (high fps, will allow wayland).
You should stay with that DTS with fb_ili9486, because it is still the closest starting point for you, and when you have it working, claiming all the GPIO pins needed, I can help again to use the DRM driver panel-mipi-dbi.
Regarding MISO and MOSI, I only meant to change that nomenclature in the graphic that you show in the forum.
I did't mean to change it in the DTS, if that's how other people make it work.
Maybe you need to have the full linux source, so you can decompile the DTBO correctly, showing the gpio pin addresses or symbols. Is it possible that you get the Radxa/Waveshare original DTS?
-
The first post reads "your mileage may vary" and "the latest kernel will work best"
Start by recompiling armbian for your Rockchip SBC, with the edge kernel option, then follow the ffmpeg install instructions
If it doesn't work, try the older Ubuntu, and both Debian options
-
If you already checked "dmesg|grep panel-mipi" and "dmesg|grep spi", check this:
* share which LCD you are using. Half of those LCDs are waveshare clones, which need a different driver. My DTS works in the RED LCDs.
* Look at the uboot messages in the serial port output. Does it confirm it is finding your dtbo and using it?
* verify that panel-mipi-dbi.ko exists in the modules folder. I know it is not preselected by default within the linux configuration menu
* Search the word "pinctrl" in this thread https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204741
To confirm that the kernel driver is using the gpio and spi pins
* send link of the rock3c DTS you are referencing, to see an example of how GPIOs are configured
* correct the gpio pin map you shared. Instead of tx/rx, use MOSI, MISO. Highlight and label clearly the CS0, CS1, RESET, DC, IRQ
* explain how those gpio numbers gpioX,XX transform into the DTS gpioX XX 1/0
If you at least get noise in the LCD, you are 50% done
(and maybe you will get lucky in the last 50%)
-
Can you copy those dtbo's to /boot/user-overlays (maybe they will need renaming)
Then activate them in armbianEnv.txt?
Compiling an LCD driver for armbian on Allwinner A33.
in Advanced users - Development
Posted
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