robertoj

JEB05DFC esd0402-6
https://www.jjm.com/profhqj4/
TVS Diode Array
ESD protective components are TVS arrays specially used for small-signal ESD protection or surge protection and are mostly used for multi-channel protection. It has the advantages of a small package size and high integration.

@robertoj
I thought that is what github provides, a complete track record of commits, pushes and changes? It's all there, I also have had contributor's. It's being sanity checked. The Orange Pi 4 Pro is nearly identical to Radxa Cubie A7A, I will be making a branch for the A7A shortly.

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"

Thank you for the information mmgen,
 
One thing you missed is the ffmpeg compilation information. Run:
 
$ ffmpeg
 
It will print out the ffmpeg version and all the libraries that were enabled, and all the libav* libraries it has compiled along with ffmpeg (libav* are parts of the ffmpeg project).
 
The interesting information is whether it uses the "v4l2-request" library, which lets ffmpeg control a part of the kernel that controls the hardware decoder.
 
When you run mpv -v yourvideo.mp4 you could also see v4l2request, or some other message about the hardware acceleration (at this point I doubt that v4l2request is used, because it works better in newer kernels)

Yes. Please wait. I was busy with other personal projects, so I haven't been doing armbian stuff for a few weeks.

Thank you

I operate an Odroid HC4, that has 4 x A55@1.8 and the board discussed here has 8  x X60@1.?. A fast sysbench says: single thread on OpiRv2 is slower (792 vs 1034) , multithreaded is faster (6342 vs 4151). Compiling a current kernel on RV2 needs 3 hours, nothing one would do do regularly. If you really need speed buy a Radxa Rock 5 (see platinum support devices on this site).
 
Edit1: NPU -> Opi Wiki, USB and SPI yes, for MIPI DSI/CSI you need to test yourself.
Edit2: Just remembered that I have a H618 (Opiz3). Single=708, Multi=2828 with the same Trixie sysbench. 
 
HTH + LG // Sven-Ola

No, it wont work.
 
I have made another thread just for the orange pi zero 3 and ili9488
https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#comment-208446
Change the GPIOs to match your wiring and connections.
 

Starting with the DTS that worked for me in the orange pi zero 3, with ili9341:
 
 
https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/?do=findComment&comment=204672
 
My DTS is for a customized set of pins that works for me, and it is different than/from the waveshare set of pins.
 
You need to change:
* file name change to: ili9486-ads7846-spi1.dts
* gpio pin selections everywhere in the DTS
* "adafruit,yx240qv29" should be "ilitek,ili9486"
* change "rotation" to "rotate"
* change "reset-gpios = <&pio N N 0>;" to "reset-gpios = <&pio N N 1>;
 
Then sudo armbian-add-overlay ili9486-ads7846-spi1.dts
Reboot
 
(does anyone know the correct DRM driver for ili9486?)

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

There's a new version of the kwiboo ffmpeg+v4l2request function
 
https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3
 
And it was shown as a work in progress in the ffmpeg community
 
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847
 
Then, it was noticed in the mpv community
 
https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427
 
They previously said that v4l2request first needs to be integrated in ffmpeg officially, then mpv would start working on v4l2request
 
This is needed, to have mpv+v4l2request compiling successfully and working under Debian Trixie (my experience)

Getting video acceleration is realtively easy in bookworm, but making it work in Trixie would be newsworthy

AFAIK bookworm is fine with wayland (weston, kde, ...)

For debian problems, do what I do:
 
Get the cheapest raspberry
Recreate the problem
Ask the question in the raspberry forum
Apply solution to Armbian
 
XD

Self compiled Armbian Bookworm + XFCE with Linux Edge 6.15.x
 
Then follow all the instructions in https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/#findComment-176981
 
 
Then add extraargs=cma=256M to armbianEnv.txt

Thank you for your suggestions. I am trying to build Mesa in my Orange Pi Zero 3.
 
When I tried installing the build dependencies, apt could not find libxatracker-dev, libllvm-18-dev, libspirv-tools-dev
i added changed "deb-src" in the /etc/apt/debian.list, so I could download *-dev packages. How did you install all the dependencies? Are you in Bookworm, or Trixie?
 
Actually I am looking for a double benefit with a new Mesa (bookworm provides mesa 22.3.6, trixie provides 25.0.7):
*H264 hardware acceleration
*I know that Raspberry has a newer Mesa (don't have it at hand), and X11 can handle the same LCD, with the same kernel module panel-mipi-dbi.ko

You are right.
I just downloaded something from youtube and assumed it was H264.
When I checked it in VLC in my PC, the codec is: AOMedia's AV1 video (av01)
 
 
I picked another mp4, which I verified in VLC as H264-MPEG4, 720p, and it played with 10% CPU
This test below is with Bookworm XFCE, compositor ON, Linux 6.15.4 with default configuration
 
 
Then I repeat the test with a 1080p H264 mp4. mpv tries to use hardware acceleration, but the mpv is black and there's continuous DRM_IOCTL errors:
 
Then I tried this inside /etc/mpv/mpv.conf
hwdec=drm-prime
drm-drmprime-video-plane=primary
drm-draw-plane=overlay
 
and the 1080p H264 starts playing fluidly with just 40% CPU (compositor off)
 
With compositor on, I get same 40% CPU
 
Same video glitches, with or without compositor, but I am getting hardware acceleration (although there's the hwdec unsupported message)
 
Update: Thank you to all who helped me. I have hardware acceleration again with my opiz3
hwdec=drm is more efficient
extraargs=cma=256 is needed to avoid memory allocation problems and video glitches.
 
https://forum.armbian.com/topic/29202-orange-pi-zero-3/page/26/#findComment-222596
 
 

Currently trying to follow the manual
https://manpages.ubuntu.com/manpages/bionic/man8/initramfs-tools.8.html#configuration hook scripts
 
I want to include this file:
 
Creating this file:
 
chmod +x include-lcd-bin.sh
 
Then I updated the initrd:
 
Then I checked, and the desired file was included
I will repeat this with the actual armbian OS with plymouth, tomorrow.

Things you should try:
 
Capture the dmesg since before the sound file is playing
Try again with the sound file in the main EXT4 partition

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.
* another member of this community transformed it into a pull request to the armbian project, and the admins approved it
 
My part 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?

That fixed it, it's now detected on i2c3 (i2cdetect -y 3)
Python also can interact with it
 
 
root@orangepizero2w:~# i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Thank you SteeMan❤️

THANKS TO USER KungFuPancake, who showed me his github repo, where he indicates to use the latest Armbian-edge, and provides the a command byte sequence for the ili9488
 
https://github.com/KungfuPancake/v0_ips_touch_display?tab=readme-ov-file
 
If you see inverted colors, edit the panel-mipi-dbi-spi.txt and comment the line #command 0x21 before using the mipi-dbi-cmd
 
If you have the cheap chinese clone LCD (see first post), use this DTS (change the gpio codes as needed):
 
 
 
 
 
 

This is from panel-mipi-dbi-spi.txt
 
command 0xE0 0x00 0x03 0x09 0x08 0x16 0x0A 0x3F 0x78 0x4C 0x09 0x0A 0x08 0x16 0x1A 0x0F command 0xE1 0x00 0x16 0x19 0x03 0x0F 0x05 0x32 0x45 0x46 0x04 0x0E 0x0D 0x35 0x37 0x0F  
This is from LCDWIKI_SPI.cpp for ili9488:
0xE0, 15, 0x00, 0x07, 0x10, 0x09, 0x17, 0x0B, 0x41, 0x89, 0x4B, 0x0A, 0x0C, 0x0E, 0x18, 0x1B, 0x0F, 0xE1, 15, 0x00, 0x17, 0x1A, 0x04, 0x0E, 0x06, 0x2F, 0x45, 0x43, 0x02, 0x0A, 0x09, 0x32, 0x36, 0x0F,  
They are other commands that differs slightly. 
 
I've found other sources for the init sequence which seems all to be close to panel-mipi-dbi-spi.txt :
 
* Juj fbcp lib: https://github.com/juj/fbcp-ili9341/blob/master/ili9488.cpp#L28
* Bodmer eTFT_SPI lib for microcontrollers : https://github.com/Bodmer/TFT_eSPI/blob/master/TFT_Drivers/ILI9488_Init.h#L11
* Jarret Bucket Adafruit GLX lib : https://github.com/jaretburkett/ILI9488/blob/master/ILI9488.cpp#L378
* this one is for STM32 : https://github.com/RobertoBenjami/stm32_graphics_display_drivers/blob/master/Drivers/lcd/ili9488/ili9488.c#L219

In the same manner, we can found init sequences for other chips in these libraries, eg ili9486.
 
There's already a driver in the kernel source : https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/tiny/ili9486.c?h=linux-6.12.y but it is specific to Waveshare 35a or PiScreen displays (these with 4 kind of shift register ICs onboard).
 
So for now, while waiting for a new ili9488 display arrives home, I'm digging further around the right init sequence for ili9486.

For reference and as a bookmark reminder
 
* https://github.com/bkosciow/gfxlcd/blob/master/gfxlcd/driver/ili9486/ili9486.py
* https://github.com/ZinggJM/ILI9486_SPI/blob/master/src/ILI9486_SPI.cpp
* https://github.com/RobertoBenjami/stm32_graphics_display_drivers/blob/master/Drivers/lcd/ili9486/ili9486.c
* https://github.com/Bodmer/TFT_eSPI/blob/master/TFT_Drivers/ILI9486_Init.h
* https://github.com/ZinggJM/ILI9486_SPI/blob/master/src/ILI9486_SPI.cpp
* https://github.com/DeadReDeamed/Raspberry-Pi-LCD-ILI9486-Driver/blob/main/LCD_Driver/LCD_Driver.c