All Activity

There are probably 20 different CPUs that have cortex a53 (cpus from Allwinner, Rockchip and Amlogic). TV box manufacturers all the time will use different CPUs in TV boxes that have the same external markings. Which ever component is the cheapest at the time of manufacture is what gets used. The only way to really be sure what you have is to look at the chip on the board (but even then there are cases where chip markings have been altered to make you think you have something else). Welcome to the world of TV boxes (and why Armbian doesn't support them officially because they are a mess).

@Ducdanh Nguyen Yes does it tell you in android Google Ai: To find your Android device's GPU, download a hardware info app like Dev Check from the Google Play Store, go to Settings > About Phone > Hardware Information (though this is less reliable on some Android versions), or use developer tools like Android GPU Inspector (AGI) for detailed profiling.

Thank you SteelMan for the pointer. Downloaded the rolling build and wrote it to my USB using balenaEtcher in Windows, the resulting USB was MBR and I could read the boot partitions contents. That's a massive improvement from using the images from https://www.armbian.com/uefi-arm64/ which were GPT and regardless of writing the USB under Windows/Linux the boot partition was unreadable. My box is probably an A95X Max (S905x2 SOC, 4G Ram, gbit ethernet & 5g wifi) so the uboot should be u-boot-s905x2-s922 All that's left is to find the best dtb Thanks for all the help

Hi, many thanks for your hints @brentr and @laibsch! 😀 Using COMPRESS_OUTPUTIMAGE=xz did the trick and the image size is now more in an expected range. However, using the paramters and commandline above gives me an image with a size of 342MB whereas the current rolling Trixie image is 273MB. I don't think it is a big deal, but I still would like to understand the difference 😊 Cheers

@dale it seems like vfd-convert has not worked well. Perhaps because of some mix between script version and the template files version. Whatsoever, I've looked closer at the patch link you previously posted, this is the older pre-review dt-bindings syntax. You should be go to start with something like: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&gpio 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&gpio 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&gpio 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; titanmec,digits = [00 01 02 03]; titanmec,segment-mapping = [03 01 02 06 04 05 00]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_ALARM; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_USB; }; led@4,2 { reg = <4 2>; function = "play"; }; led@4,3 { reg = <4 3>; function = "pause"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = LED_FUNCTION_LAN; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_WLAN; }; }; }; }; Note that I haven't tested it, just made it from some copy-paste. If it doesn't work, even partially, you would most likely need to replace &gpio with the right reference to the gpio controller wired to the display.

Hello, I am new to arm board, I had this android tv stick called S moon mx10 5G, it have rk322x cpu, 2GB Ram, and ap6330 wifi chip. I tried armbian on this device but wifi chip was not detected, I tried using "rockchip-rk3318-box-wlan-ap6330.dtbo" as user_overlays, but still not working, could anyone tell me how to make this wifi chip working on rk322x armbian?. I attached some files for information: dmesg.txt s_moon_mx10_5g.dts

Do you mean gpu model? Like mail-g31?

Disabling automount (drive letter assignment) in windows before flashing might help - probably it is mount time when windows is checking and changing partition table.

First off, I would recommend using the "psuedo official" instructions from this site: https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus And there you will find the following warning: Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds.

Hey Guys, I know this post is old but I have some questions. I was following @Jaybyrd's instructions and I have a question pertaining to the Plugin USB-C to the power on the device "I am assuming that is on The OPi5 device." Am I supposed to plug in something else? Because it says to open a terminal "what terminal? On what device?" Thank you for your time, Michael

I wouldn't be so categorical - I have rock pi 4b, which never saw android or any os other than armbian, which has same thing- two boot devices on emmc. Since it doesn't bother me, I didn't investigate further.

@Ducdanh Nguyen Can you find the gpu version?

No that is not true. These are not from Armbian. As I said earlier if your eMMC previously had Android (which defines and uses these special partitions) even after a normal Linux repartitioning these will still appear.

It seems that eMMC has built-in boot partitions. eMMC devices are not just "raw storage" (like SD-Cards) they have special reserved hardware partitions defined by the JEDEC eMMC standard. These include: boot0 – a small partition (usually a few MB) reserved for bootloader code. boot1 – a second small boot partition, often used as a backup. RPMB (Replay Protected Memory Block) – a secure partition for keys and counters. The SoC’s boot ROM (first-stage loader) can be configured to read directly from boot0 or boot1 when powering on. Also, these partitions are read-only to decrease the risk of having corrupted boot code. Beware that they’re not used by the Linux filesystem unless explicitly written to (usually via dd when flashing U-Boot).

If the card still mounts, try running fsck first. If it’s clean but won’t boot, you can copy fresh /boot files from the same Armbian release. Otherwise, reinstalling to a new SD and restoring your data may be the safer route.

I faced a similar Ethernet throughput issue on Armbian under high latency. One thing that helped was using a USB Ethernet dongle instead of the onboard NIC. To simulate latency, you can use the tc command: sudo tc qdisc add dev eth0 root netem delay 200ms sudo tc qdisc del dev eth0 root For more solutions, check out this.

Hi, I am using Nanopi Neo board and I need RS485 driver to control DE pin automatically. I have prepared DTS Overlay file: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&uart1>; __overlay__ { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&uart1_pins &uart1_de_pin>; rs485-rts-gpios = <&gpio6 8 0>; /* PG8 active-low */ linux,rs485-enabled-at-boot-time; rs485-rts-delay = <0 300>; }; }; fragment@1 { target = <&uart2>; __overlay__ { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&uart2_pins &uart2_de_pin>; rs485-rts-gpios = <&gpio0 2 0>; /* PA2 active-low */ linux,rs485-enabled-at-boot-time; rs485-rts-delay = <0 300>; }; }; }; I produced dtbo file from dts one with the command: dtc -@ -I dts -O dtb -o rs485.dtbo rs485.dts I copied this rs485.dtbo file to /boot/dtb/overlay. Also I added rs485 string to ArmbianEnv.txt and rebooted. But only TX works, RX doesn't. What should I do else to make it work?

The guidance I found is on Github, nexbox-a95x-arm https://github.com/berci9ke101/nexbox-a95x-armbianbian. I think its similar to some guidance I looked at when I first looked at Armbian and how I got Coreelec to run on my A95X box

Please elaborate what do you mean by "hardware defined". Both obviously were created by armbian-config script after full emmc format during system transfer to emmc. Questions remain the same: what for and where are they used?

Hi! With latest edge 6.15.4 the board boots fine, shutdown also clean and complete but on reboot it does not again start up. Need to powercycle😒 I gets stuck et end of shutdown. Same for latest bookworm image (I think it's 6.12x). Earlier ones did work. => Any other board also affected? => Is for reboot the watchdog involved? T.

Hi and thanks! Tested now but no luck. Compiled edge 6.15.4 Linux nanopiduo2 6.15.4-edge-sunxi #1 SMP Fri Jun 27 10:13:43 UTC 2025 armv7l GNU/Linux now i get Device creation failed: -14. [h264 @ 0x11f9b40] No device available for decoder: device type drm needed for codec h264. Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native)) Device setup failed for decoder on input stream #0:0 : Bad address [AVIOContext @ 0x11ac030] Statistics: 498846 bytes read, 0 seeks command as follows: ffmpeg -v trace -re -hwaccel drm -i Big_Buck_Bunny_720_10s_10MB.mp4 -f null - also tried fbdev output but same result. ffmpeg version is still ffmpeg -v ffmpeg version 5.1.7-0+deb12u1 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14+deb12u1) configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --arch=arm --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 Unfortunately there are countless forks of ffmpeg. I used the one from here https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ As of now I haven't found anything about a current kernel and ffmpeg working on any H3, only stuff back in 2019 and/or kernel 4.x 🙂 I also tried several extraargs=cma=### up to 256M but all same error. I really woud love to get some more tech background on "how stuff works" which may help me troubleshoot. => Can we enable debug output from the cedrus driver? How? => Can we enable debug output from thev4l2 layer? How? => Which libraries are involved, eg. v4l2request, other v4l2* which may need additional install/update? => Do in need v4l2-util / v4l2-ctl to configure some stuff? If yes, what exactly? (Remember, Its currently for file playback. I know about for cam capture) => Could the v4l2loopback help? => Can anybody confirm it really works on H3 maybe on an OrangePi board? If yes I can pull the Opi device tree and compare for possible differences. T.

@Jean-Francois Lessard sorry for making you confused. Device tree source for tm16xx driver that I convert from a working openvfd.conf is below /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = < 7 GPIO_ACTIVE_HIGH>; mosi-gpios = < 2 GPIO_ACTIVE_HIGH>; cs-gpios = < 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0>; spi-3wire; spi-lsb-first; spi-max-frequency = <500000>; digits { #address-cells = <1>; #size-cells = <0>; 01 02 03 04 }; leds { #address-cells = <2>; #size-cells = <0>; led@{GRID0},0 { reg = <{GRID0} 0>; function = "apps"; }; led@{GRID1},1 { reg = <{GRID1} 1>; function = "setup"; }; led@{GRID2},2 { reg = <{GRID2} 2>; function = LED_FUNCTION_USB; }; led@{GRID3},3 { reg = <{GRID3} 3>; function = LED_FUNCTION_SD; }; led@{GRID4},4 { reg = <{GRID4} 4>; function = "colon"; }; led@{GRID5},5 { reg = <{GRID5} 5>; function = "hdmi"; }; led@{GRID6},6 { reg = <{GRID6} 6>; function = "video"; }; }; }; }; }; The convert script I downloaded from this commit https://github.com/jefflessard/tm16xx-display/blob/a93b257ed4c73780fcdefbb1f1dd189599cf6ecc/vfdconf-convert Can you please help get it to work? Thanks!

@Nick A based on chatgpt with website research, it depends on with box meaning that mine still have a h313, its cortex a53. 64 bit, then what is it? (I can give you more proof that mine is allwinner h313)

Everything you wish for here is achievable with pure U-Boot technology. A long time ago, I tried to practice how to realize this here in the forum, but my lesson from it was: You can't teach old dogs new tricks, and Armbian users want to celebrate their cargo cult and hope that it will magically fulfill their wishes.