Nick A

Can you look for the display controller chip on your board. This will at least give us a starting point. Then we can find other boards with a similar chip. Also, a picture of your front display would help. This README describes the values better. https://github.com/arthur-liberman/vfd-configurations/blob/master/README.md I forgot about the command armbian-add-overlay. When I was playing with openvfd I didn't use an overlay file. I added the openvfd node directly to my boards dts. I didn't need to make any changes because I used the original openvfd settings.

This already has AXP806. You just need to modify the deconfig with the settings that worked for you. u-boot: https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/151-add-x96-q-ddr3-defconfig.patch kernel: https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.12/files/0647-arm64-dts-allwinner-h313-add-x96q-TVbox.patch Also, edit /boot/armbianEnv.txt and set verbosity to 7 to get full boot logs. Your directory layout might be different. You can browse the folders. Find the correct path. sudo adb shell su cd /dev/block/

Hi Mark Modify your /boot/dtb/allwinner/overlay/openvfd.dts . You need to change the display-type. I can't really tell by the image you took which chip the display is using. If you can check again. It's the chip beside the LED display. https://github.com/arthur-liberman/vfd-configurations/?tab=readme-ov-file#display-type Try this see what happens... ( ID=01, A display like on the Sunvell T95m. It is similar to T95U, but the icons are positioned differently, and the digits are "upside down".) openvfd_display_type = <0x01000000>;

Good question. I'm not sure. First you need to enable Developer options. Then enable Wireless debugging on your device. https://www.androidpolice.com/use-wireless-adb-android-phone/ https://developer.android.com/tools/adb#Enabling If you are using linux you don't need Android SDK platform-tools to access adb software. sudo apt install adb sudo adb connect 192.168.X.X:5555 (x is your local network address for your android box) sudo adb shell ls -al /dev/block/

[ 14.228753] OpenVFD: Failed to verify VFD configuration file, attempt using device tree as fallback. Your openvfd is using the device tree as the configuration file since it cannot find the configuration file vfd.conf. You can edit your device tree overlay or you would need to create a /storage/.config/ directory and put your vfd.conf inside. You’ll need root permission to create the directories and file. Here you can find example vfd.conf files. https://github.com/arthur-liberman/vfd-configurations/ You can also try running this command for help. OpenVFDService --help Then there's also the openvfd.service. This runs OpenVFDService everytime your linux server boots. openvfd.service Other ways of controlling the LED's. You can put these commands in openvfd.service if needed. https://github.com/arthur-liberman/linux_openvfd/blob/9264588ba27a964a1e56346202901dd17f9e133d/led_control.txt Have you tried extracting your dts? you might find your android original openvfd device tree settings there.

openvfd,display-type usually is 00 (normal) or 01 if your display translate by 180 degrees (ie: characters are flipped down and specular) Maybe you can find more info here.. https://discourse.coreelec.org/t/how-to-configure-vfd/427/702?page=34

I just updated the repository. Wifi now works.

https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-207680 Using MMorales openvfd scripts I don't remember needing vdf.conf. In openvfd.service you can remove "#" infront of ExecStart=/bin/sh -c '[ `cat /proc/device-tree/openvfd/compatible` = "open,vfd" ] && /sbin/modprobe openvfd; python3 /linux_openvfd/scroll.py' then edit the scroll.py script with your custom settings. Remember to add '#' in the second ExecStart. [Unit] Description=OpenVFD Service ConditionPathExists=/proc/device-tree/openvfd/ [Service] #ExecStart=/bin/sh -c '[ `cat /proc/device-tree/openvfd/compatible` = "open,vfd" ] && /sbin/modprobe openvfd; python3 /linux_openvfd/scroll.py' ExecStart=/bin/sh -c '[ `cat /proc/device-tree/openvfd/compatible` = "open,vfd" ] && /sbin/modprobe openvfd; /usr/sbin/OpenVFDService' ExecStop=/bin/kill -TERM $MAINPID ExecStopPost=-/usr/sbin/rmmod openvfd RemainAfterExit=yes [Install] WantedBy=basic.target

My build uses warpme-6.12 patches so people with other boards can make a board config to compile their own images. https://github.com/NickAlilovic/build/blob/warpme-6.12/config/boards/radxa-cubie-a5e.csc https://github.com/NickAlilovic/build/tree/warpme-6.12/patch/kernel/archive/warpme-6.12 1170-arm64-dts-allwinner-h728-add-x96q-pro-tvbox-plus.patch 1172-arm64-dts-allwinner-t527-add-orangepi-4a-dts.patch 1173-arm64-dts-allwinner-a527-add-Radxa-A5E-support.patch Orangepi 4a uses the same radxa-a5e_defconfig. https://github.com/warpme/minimyth2/blob/master/script/bootloaders/board-t527.orangepi_4a/Makefile x96q_pro_plus_defconfig https://github.com/warpme/minimyth2/blob/master/script/bootloaders/board-h728.x96q_pro_plus/Makefile

I just updated my repository. I changed one line to include boot.cmd https://github.com/NickAlilovic/build/commit/d578b352143d15abee25c805880f6ba6016a9490

Thanks Juan, I was able to boot the kernel with some changes. I used this extlinux.conf file. Changed the kernel to /Image and fdt to /dtb. I manually created a directory called extlinux in the boot directory. I then moved the extlinux.conf there. /extlinux/extlinux.conf label ARMBIAN kernel /Image fdt /dtb/allwinner/sun55i-a527-radxa-a5e.dtb append earlycon=uart8250,mmio32,0x02500000 clk_ignore_unused console=ttyS0,115200 loglevel=8 root=/dev/mmcblk0p2 rw rootwait radxa-cubie-a5e.csc I changed one line BOOTSCRIPT="extlinux.conf" # Allwinner Cortex-A55 octa core 2/4GB RAM SoC USB3 USB-C 2x GbE BOARD_NAME="radxa cubie a5e" BOARDFAMILY="sun55iw3" BOARD_MAINTAINER="Nick A" BOOTCONFIG="radxa-a5e_defconfig" OVERLAY_PREFIX="sun55i-a527" BOOT_LOGO="desktop" KERNEL_TARGET="edge" FORCE_BOOTSCRIPT_UPDATE="yes" BOOT_FDT_FILE="dtb/allwinner/sun55i-a527-radxa-a5e.dtb" BOOTFS_TYPE="fat" BOOTSCRIPT="extlinux.conf" IMAGE_PARTITION_TABLE="msdos" BOOTSTART="1" BOOTSIZE="512" ROOTSTART="513" UBOOT_EXTLINUX=yes" UBOOT_EXTLINUX_ROOT=root=UUID=%%ROOT_PARTUUID%%" UBOOT_EXTLINUX_FDT="sun55i-a527-radxa-a5e.dtb" Most Armbian boards use the boot.cmd for their bootscript. I found the line I missed in build/config/sources/families/sun55iw3.conf. I cloned a clean build and changed one line in sun55iw3.conf. declare -g BOOTSCRIPT='boot-sun50i-next.cmd:boot.cmd' declare -g ATF_TARGET_MAP="PLAT=sun55i_a523 DEBUG=1 bl31;;build/sun55i_a523/debug/bl31.bin" declare -g ATFBRANCH="branch:a523" declare -g BOOTSCRIPT='boot-sun50i-next.cmd:boot.cmd' declare -g BOOTDELAY=1 declare -g BOOTSOURCE='https://github.com/apritzel/u-boot' _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.02 rolling for radxa cubie a5e running Armbian Linux 6.12.12-edge-sun55iw3 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 6 packages available for upgrade Support: DIY (custom image) IP addresses: (LAN) IPv4: IPv6: Performance: Load: 5% Up time: 4 min Memory usage: 4% of 3.83G Usage of /: 3% of 58G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop nick@radxa-cubie-a5e:~$

Hi Juan, I'm having the same issue. I believe it's due to this scp.bin file that's needed by a523 u-boot. Trying to figure out how to modify the build scripts to add scp.bin before u-boot compiles. I tried to add a patch to include this binary but I would get an error about patching binary files not supported. https://github.com/warpme/minimyth2/tree/master/script/bootloaders/board-a527.cubie_a5e/files I also need to add extlinux.conf or boot.cmd/boot.scr.

if anyone has a Radxa cubie A5E and wants to test the lastest bringup work here you go. I don't own the other h728/a523/t527 boards so I can't test them. I willl not provide images because this is experimental. git clone https://github.com/NickAlilovic/build.git --branch warpme-6.12 --single-branch

if anyone has a Radxa cubie A5E and wants to test the lastest bringup work here you go. I don't own the other h728/a523/t527 boards so I can't test them. I willl not provide images because this is experimental. https://github.com/NickAlilovic/build/tree/warpme-6.12I

I just started working on a new project using the latest Armbian build and warpme's 6.12 kernel patches. I'm going to add warpme's u-boot patches next. The Edge builds will use warpme's 6.12 patches for now. This should make it easier to add boards already supported by warpme.

Are you using Orangepie's DRAM settings? Or did you extract your boxes DRAM settings? For USB2 ports you probably need this in your dts &ehci2 { status = "okay"; }; &ohci2 { status = "okay"; };

Afiftyp, I tested your patches. First boot the kernel detected my bluetooth module. [ 15.837115] Bluetooth: hci0: BCM: features 0x2f [ 15.860556] Bluetooth: hci0: BCM4335B0 JA-3G SemcoB62 AFH_LimitPwr_EDR2 2STOPBIT-0343 [ 15.860579] Bluetooth: hci0: BCM4335A0 (002.001.006) build 0347 But after multiple reboots I would get hci1. [ 9.987983] Bluetooth: hci1: command 0x0c03 tx timeout [ 9.988039] Bluetooth: hci1: BCM: Reset failed (-110) Also some new panfrost errors. [ 58.359410] panfrost 1800000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0xa1cdec0, tail=0xa1cdec0

Yup, I saw that. It still compiles not sure why. At the time I didn't correct the mistake because it would break other board patches that were added after mine. I don't know if anyone is working on adding their own board now. I'll fix it. If people are getting u-boot compile errors with their fork then this is the reason. Thanks for the reminder.

Hi Javad, if you are playing youtube videos. 720p works fine for me. 1080 freeezes. robertoj was able to get hardware video decocding working with ffmpeg-v4l2request. I haven't tested this method yet.

Hi Javad, Did you apply the GPU enable patch in your u-boot? https://github.com/NickAlilovic/build/blob/v20241125/patch/u-boot/u-boot-sunxi/allwinner-h616-GPU-enable-hack.patch

You can find patches for A523/A527 here. Just need to port them over to Armbian. https://github.com/warpme/minimyth2/tree/master/script/bootloaders/board-t527.orangepi_4a/files https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.12/files https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.12/files/1172-arm64-dts-allwinner-t527-add-orangepi-4a-dts.patch

The solution I found to enable stereo after googling for a few days is: editing a pulseaudio conf file sudo nano /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf In this file look for a section starting with: [Mapping analog-mono] and ending with: priority=7 It will be about 6 or 8 lines long Comment these lines out by preceding them with a " ; " (without the " " of course) This will disable the analog-mono section Save the file, sudo reboot and voila: your device profiles will contain stereo output (as well as multichanel, wich I did not try out) And, even better, your sound IS in stereo Regards, aert077 https://forums.raspberrypi.com/viewtopic.php?t=293459 I found this.. I haven't tried it.

You need the header files from my build.. https://github.com/NickAlilovic/build/releases/tag/20241125

You need to build u-boot with your DRAM settings. You can find the settings in Android DT file or you can extract it from a factory update using sunxi-tools.

This is the box I'm using.. Everything works. Bluetooth still has some bugs. (Works only after I enable it in android). https://linux-sunxi.org/Transpeed_8K618-T