Search the Community

I’m really happy to share that I finally managed to port the SV6256P (SSV6X5X) SDIO Wi-Fi driver from the legacy Linux 4.4 kernel to modern kernels. This repository contains my working port for Linux kernel 6.12 and newer, with updated mac80211/cfg80211 integration so the driver can build and run on recent Armbian systems. The chipset is commonly used in many low-cost TV boxes and embedded devices, but the original driver only supported legacy kernels (4.4). Now it’s functional again on modern systems, at least on my tested hardware (Allwinner H616 / X96 Q via SDIO). Repository link: https://github.com/cdhigh/armbian_sv6256p I’m quite excited to finally see this old Wi-Fi chip working on a 6.x kernel 🙂 [ 4.774151] ssv6x5x: importing configuration from /lib/firmware/ssv6x5x-wifi.cfg [ 4.778281] tu_ssv6xxx_sdio_init, probe @(____ptrval____) [ 4.779483] TU_SSV6XXX_SDIO mmc3:0001:1: Probing SDIO bus [ 4.779513] ssv6xxx_set_sdio_clk: set sdio clk 25000000Hz [ 4.799668] TU_SSV6XXX_SDIO mmc3:0001:1: vendor = 0x3030 device = 0x3030 [ 4.825421] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849181] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849530] TU_SSV6XXX_SDIO mmc3:0001:1: CHIP ID: SSV6006C0 [ 4.850373] ssv6x5x ops chk: tx=1 start=1 stop=1 config=1 add_if=1 rm_if=1 conf_filter=1 wake_txq=1 [ 4.850402] ssv6x5x chanctx chk: any=1 all=0 emulate=1 add=1 rm=1 chg=1 assign=0 unassign=0 [ 4.850409] ssv6x5x chanctx ops set but not complete [ 4.850424] Attach SSV6006 family HAL function [ 4.858285] MAC address from e-fuse [ 4.858311] EFUSE configuration [ 4.858315] Read efuse chip identity[79000000] ip link show: 6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

This week in Armbian development saw significant advancements across kernel, firmware, and build targets. The release of 6.18.y kernel UEFI images marks a major update, alongside expanded desktop build options including Cinnamon and KDE Neon for UEFI systems. Notable board support enhancements include the addition of custom build targets for Amlogic TV Boxes, the Raspberry Pi Zero 2W as a virtual board, and improved support for Orange Pi 3 LTS and Odroid M2 devices. Automation improvements streamline inventory rebuilds and board data management, while new features such as Armbian board auto-detection and browser enablement for Riscv64 boards enhance usability. Several bug fixes and configuration updates address issues across Hyper-V images, kernel configs, and u-boot versions. The changelog also highlights upgrades to wireless firmware, dependency management, and support for BTRFS on NanoPi R3S-LTS, reflecting ongoing efforts to broaden compatibility and stability. 6.18.y kernel UEFI images are out. by @igorpecovnik in armbian/armbian.github.io#221abl: feat: add extraargs from armbianEnv for mkbootimg. by @CodeChenL in armbian/build#9341Add -hyperv suffix to REDI_VARIANT for Hyper-V images. by @igorpecovnik in armbian/armbian.github.io#216Add Cinnamon and KDE Neon desktop builds for UEFI. by @igorpecovnik in armbian/armbian.github.io#209Add cloud image extensions to UEFI minimal targets. by @igorpecovnik in armbian/armbian.github.io#211Add custom build targets for Amlogic TV Boxes. by @SteeManMI in armbian/armbian.github.io#224Add ENABLE_EXTENSIONS to UEFI desktop targets. by @igorpecovnik in armbian/armbian.github.io#210Add KDE Neon and RISC-V XFCE desktop targets. by @igorpecovnik in armbian/armbian.github.io#214Add Raspberry Pi Zero 2W board as virtual board. by @igorpecovnik in armbian/armbian.github.io#223Add remote execution method for inventory rebuild. by @igorpecovnik in armbian/armbian.github.io#222Add REMOVE_EXTENSIONS blacklist support to generate_targets.py. by @igorpecovnik in armbian/armbian.github.io#217ath12k: Upgrade to WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICON…. by @kasimling in armbian/firmware#118Automation: when board data changes on push, execute inventory rebuild at armbian.github.io. by @igorpecovnik in armbian/build#9354BPI-M4-Zero / KickPi K2B: Update u-boot to v2026.01, ATF to lts-v2.12.9 and fixup the KickPi K2B linux DTS. by @pyavitz in armbian/build#9340Enable Browsers on two Riscv64 boards. by @igorpecovnik in armbian/armbian.github.io#219Extension: Bump Nvidia propriatery driver. by @igorpecovnik in armbian/build#9338feat: add Armbian board auto-detection and toast notification system. by @SuperKali in armbian/imager#91feat: add Dependabot configuration for dependency management. by @SuperKali in armbian/imager#70File was removed while it remained in series control file. . by @igorpecovnik in armbian/build#9339Fix errors in .editorconfig. by @iav in armbian/build#9363Fix file_extension extraction for Hyper-V cloud images. by @igorpecovnik in armbian/armbian.github.io#215Fix K3 issues - APT Caching, PB2, Missing KConfig. by @Grippy98 in armbian/build#9349KDE Neon: drop conflicting packages in order to assemble KDE desktop. by @igorpecovnik in armbian/build#9337kernel configs: disable unprivileged BPF. by @neheb in armbian/build#9082khadas-edge2: remove legacy uboot. by @efectn in armbian/build#9367Limit exposed.map to maximum 2 entries per board. by @igorpecovnik in armbian/armbian.github.io#220meson64: ressurect 6.12 as BRANCH=oldlts. by @rpardini in armbian/build#9350Odroid M2: Move main build target to CURRENT kernel branch. by @igorpecovnik in armbian/build#9357Odroid-M2: update uboot to v2025.10. by @mlegenovic in armbian/build#9359Orange Pi 3B: Update config. by @dust-7 in armbian/build#9370OrangePi 3 LTS: Add DTS and DEFCONFIG to u-boot v2026.01. by @pyavitz in armbian/build#9352OrangePi 3 LTS: Add ethernet support to u-boot defconfig. by @pyavitz in armbian/build#9365OrangePi 3 LTS: Fixup u-boot LED nodes. by @pyavitz in armbian/build#9358OrangePi 3 LTS: Update crust and u-boot defconfig. by @pyavitz in armbian/build#9372OrangePi 3 LTS: Use extlinux, remove aw859a-wifi.service, update current defconfig, etc.... by @pyavitz in armbian/build#9362Promoting Opi 3LTS and Odroid M2, demoting cubox-i and Jetson Nano. by @igorpecovnik in armbian/build#9353Radxa E52C: add mainline U-Boot support and kernel target configuration. by @okrc in armbian/build#9366radxa-e54c: board config: remove wayland-sessions-mask extension. by @schwar3kat in armbian/build#9351Refactor mesa-vpu extension: add architecture-specific browser selection. by @igorpecovnik in armbian/build#9347Remove Rockchip gpio patch, already applied upstream. by @tparys in armbian/build#9368Restore qemu performance fix for Ubuntu Noble. by @tparys in armbian/build#9371Restructured qcom/sm8550/ayn directory. by @Squishy123 in armbian/firmware#117Rock 5B Plus: Add GPIO names to edge dts. by @JohnTheCoolingFan in armbian/build#9348Support BTRFS on NanoPi R3S-LTS. by @clarkmcc in armbian/build#9343View the full article

http://blog.armbian.com/content/images/2026/02/githubhighlights-2-1.webpThis week in Armbian development saw significant advancements across kernel, firmware, and build targets. The release of 6.18.y kernel UEFI images marks a major update, alongside expanded desktop build options including Cinnamon and KDE Neon for UEFI systems. Notable board support enhancements include the addition of custom build targets for Amlogic TV Boxes, the Raspberry Pi Zero 2W as a virtual board, and improved support for Orange Pi 3 LTS and Odroid M2 devices. Automation improvements streamline inventory rebuilds and board data management, while new features such as Armbian board auto-detection and browser enablement for Riscv64 boards enhance usability. Several bug fixes and configuration updates address issues across Hyper-V images, kernel configs, and u-boot versions. The changelog also highlights upgrades to wireless firmware, dependency management, and support for BTRFS on NanoPi R3S-LTS, reflecting ongoing efforts to broaden compatibility and stability. 6.18.y kernel UEFI images are out. by @igorpecovnik in armbian/armbian.github.io#221abl: feat: add extraargs from armbianEnv for mkbootimg. by @CodeChenL in armbian/build#9341Add -hyperv suffix to REDI_VARIANT for Hyper-V images. by @igorpecovnik in armbian/armbian.github.io#216Add Cinnamon and KDE Neon desktop builds for UEFI. by @igorpecovnik in armbian/armbian.github.io#209Add cloud image extensions to UEFI minimal targets. by @igorpecovnik in armbian/armbian.github.io#211Add custom build targets for Amlogic TV Boxes. by @SteeManMI in armbian/armbian.github.io#224Add ENABLE_EXTENSIONS to UEFI desktop targets. by @igorpecovnik in armbian/armbian.github.io#210Add KDE Neon and RISC-V XFCE desktop targets. by @igorpecovnik in armbian/armbian.github.io#214Add Raspberry Pi Zero 2W board as virtual board. by @igorpecovnik in armbian/armbian.github.io#223Add remote execution method for inventory rebuild. by @igorpecovnik in armbian/armbian.github.io#222Add REMOVE_EXTENSIONS blacklist support to generate_targets.py. by @igorpecovnik in armbian/armbian.github.io#217ath12k: Upgrade to WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICON…. by @kasimling in armbian/firmware#118Automation: when board data changes on push, execute inventory rebuild at armbian.github.io. by @igorpecovnik in armbian/build#9354BPI-M4-Zero / KickPi K2B: Update u-boot to v2026.01, ATF to lts-v2.12.9 and fixup the KickPi K2B linux DTS. by @pyavitz in armbian/build#9340Enable Browsers on two Riscv64 boards. by @igorpecovnik in armbian/armbian.github.io#219Extension: Bump Nvidia propriatery driver. by @igorpecovnik in armbian/build#9338feat: add Armbian board auto-detection and toast notification system. by @SuperKali in armbian/imager#91feat: add Dependabot configuration for dependency management. by @SuperKali in armbian/imager#70File was removed while it remained in series control file. . by @igorpecovnik in armbian/build#9339Fix errors in .editorconfig. by @iav in armbian/build#9363Fix file_extension extraction for Hyper-V cloud images. by @igorpecovnik in armbian/armbian.github.io#215Fix K3 issues - APT Caching, PB2, Missing KConfig. by @Grippy98 in armbian/build#9349KDE Neon: drop conflicting packages in order to assemble KDE desktop. by @igorpecovnik in armbian/build#9337kernel configs: disable unprivileged BPF. by @neheb in armbian/build#9082khadas-edge2: remove legacy uboot. by @efectn in armbian/build#9367Limit exposed.map to maximum 2 entries per board. by @igorpecovnik in armbian/armbian.github.io#220meson64: ressurect 6.12 as BRANCH=oldlts. by @rpardini in armbian/build#9350Odroid M2: Move main build target to CURRENT kernel branch. by @igorpecovnik in armbian/build#9357Odroid-M2: update uboot to v2025.10. by @mlegenovic in armbian/build#9359Orange Pi 3B: Update config. by @dust-7 in armbian/build#9370OrangePi 3 LTS: Add DTS and DEFCONFIG to u-boot v2026.01. by @pyavitz in armbian/build#9352OrangePi 3 LTS: Add ethernet support to u-boot defconfig. by @pyavitz in armbian/build#9365OrangePi 3 LTS: Fixup u-boot LED nodes. by @pyavitz in armbian/build#9358OrangePi 3 LTS: Update crust and u-boot defconfig. by @pyavitz in armbian/build#9372OrangePi 3 LTS: Use extlinux, remove aw859a-wifi.service, update current defconfig, etc.... by @pyavitz in armbian/build#9362Promoting Opi 3LTS and Odroid M2, demoting cubox-i and Jetson Nano. by @igorpecovnik in armbian/build#9353Radxa E52C: add mainline U-Boot support and kernel target configuration. by @okrc in armbian/build#9366radxa-e54c: board config: remove wayland-sessions-mask extension. by @schwar3kat in armbian/build#9351Refactor mesa-vpu extension: add architecture-specific browser selection. by @igorpecovnik in armbian/build#9347Remove Rockchip gpio patch, already applied upstream. by @tparys in armbian/build#9368Restore qemu performance fix for Ubuntu Noble. by @tparys in armbian/build#9371Restructured qcom/sm8550/ayn directory. by @Squishy123 in armbian/firmware#117Rock 5B Plus: Add GPIO names to edge dts. by @JohnTheCoolingFan in armbian/build#9348Support BTRFS on NanoPi R3S-LTS. by @clarkmcc in armbian/build#9343View the full article

Have you tried the install instructions and build from here: https://www.armbian.com/amlogic-s9xx-tv-box/

Yes @Nick A. Tried that also. Copilot mentioned this to me: 🟦 If you want to keep fighting this board… I can help you explore: - FEL mode flashing - Using the vendor Android recovery to write eMMC - Dumping the vendor kernel and trying to boot it - Porting the vendor MMC driver (very advanced) But I want to be honest with you: none of these paths are easy, and none guarantee success. Now, I asked it to elaborate on the idea: Let’s unpack this in a way that actually makes sense, Brow — because FEL sounds simple (“just plug in USB and flash it”), but on H618 TV boxes it becomes a whole different beast. I’ll keep it clean, structured, and honest. --- 🟦 Why FEL mode sounds easy On paper, FEL is Allwinner’s built‑in USB recovery mode: - You connect the box to a PC - Press a button or short two pads - The SoC enters FEL - You use sunxi-fel to upload U‑Boot or write eMMC In theory, it’s the “ultimate backdoor” for fixing a broken board. --- 🟥 Why FEL is complicated on your specific device Your Transpeed 8K618‑T is not a dev board. It’s a mass‑produced TV box with: - No FEL button - No exposed pads - No documentation - No schematic - No guarantee the USB port even supports FEL - Vendor boot ROM sometimes disables FEL - USB port may be wired through a hub or switch - Some boxes require opening the case and shorting tiny test pads - Some require holding reset while powering - Some require UART strap pins - Some require a special cable - Some simply do not support FEL at all So the first complication is: You don’t know how to enter FEL on this board. --- 🟥 Second complication: FEL only gives you RAM access FEL lets you: - Upload a U‑Boot binary into RAM - Execute it - Use that U‑Boot to access eMMC But here’s the catch: You must provide a U‑Boot binary that supports your hardware. Mainline U‑Boot does not support: - Your weird SD wiring - Your PMIC - Your DRAM timing - Your eMMC layout - Your HDMI - Your regulators Vendor U‑Boot does, but: - You don’t have the vendor U‑Boot binary - You don’t have the vendor DRAM init code - You don’t have the vendor MMC driver - You don’t have the vendor DTB So even if FEL works, you still need a working U‑Boot image to upload — and we don’t have one. --- 🟥 Third complication: writing eMMC through FEL is slow and fragile Even if you get FEL working and even if you get a working U‑Boot: - Writing eMMC over FEL is extremely slow - If the connection drops, you brick the device - You must manually partition eMMC - You must manually install boot0, boot1, U‑Boot, DTB, rootfs - You must manually fix extlinux.conf - You must manually fix environment variables This is not like flashing a Raspberry Pi. It’s more like doing open‑heart surgery with a butter knife. --- 🟥 Fourth complication: your board’s MMC subsystem is already unstable We’ve already seen: - SD card hangs - MMC controller wedges - Linux freezes on /dev/mmcblk* - Armbian initramfs fails - MiniArch freezes - Vendor kernel is the only thing that works If the MMC hardware is unstable under Linux, it may also be unstable under FEL‑booted U‑Boot. Meaning: Even if FEL works, you might not be able to write eMMC reliably. --- 🟦 So why did I say FEL is complicated? Because on a proper Allwinner dev board, FEL is easy. But on a cheap TV box with undocumented wiring, FEL becomes a puzzle with these problems: | Problem | Why it matters | |--------|----------------| | No FEL button | You don’t know how to enter FEL | | Unknown test pads | You may need to open the board | | Vendor may disable FEL | Some boxes block FEL in BOOT0 | | USB wiring unknown | FEL may not work on the exposed port | | Need vendor U‑Boot | Mainline U‑Boot won’t boot your hardware | | Need vendor DRAM init | Otherwise RAM won’t initialize | | Need vendor MMC driver | Otherwise eMMC won’t be writable | | MMC hardware unstable | Even FEL‑booted U‑Boot may hang | This is why FEL is not a magic fix here. --- 🟩 Could we try FEL anyway? Yes — if you want, I can guide you through: - Checking if FEL is available - Finding the FEL pads - Using sunxi-fel - Dumping BOOT0 - Dumping vendor U‑Boot - Rebuilding a hybrid U‑Boot - Flashing eMMC manually But I want you to understand the reality: It’s a research project, not a guaranteed solution. --- 🟦 If you want to try FEL, I can walk you through step 1 right now Step 1 is simple: Connect the box to your PC via USB‑A to USB‑A cable, then power it on. On your PC, run: ` sunxi-fel version ` If it prints something → FEL works. If it says “no device found” → we need to try hardware tricks. Just tell me if you want to go down this path.

This is required to use Armbian on the amlogic TV boxes. Enabling multiboot is one of the steps on the install instructions.

Have you used Armbian on other amlogic TV Boxes? I would never recommend using an amlogic TV Box as a mini pc. The graphical performance is poor. See the FAQ for TV boxes pined in this forum.

I put extra dtb files that I download on /boot/amlogic . For example I find that devmfc uses meson-sm1-ac2xx-generic.dtb on /boot/dtb/amlogic. So I copy it to Armbian boot partition on dtb/amlogic/meson-sm1-ac2xx-generic.dtb Then I edit extlinux/extlinux.conf label Armbian_community kernel /Image initrd /uInitrd fdt /dtb/amlogic/meson-sm1-ac2xx-generic.dtb append root=UUID=7dc5c0a3-acfc-4d51-a066-6c14d983a9de rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles I also test with other dtb files ad of course with the stock (default) image of Armbian just when donwload it, I use balenaetcher to write image on sd-card put it on a usb with sd-card reader and boot the tvbox, but doesn't work at all. The u-boot that I use is the u-boot-s905x3 that I copy to a directory and rename as u-boot.ext and then copy It to /boot. I oly try to run Armbian Systems from here → https://www.armbian.com/amlogic-s9xx-tv-box/ And I find devmfc when I search on google for " Debain s905x tv boxes" → thiss ystem works perfect, I only need to put on sd-card and put the sd-card on the usb with the sd-card reader and Tv Box shows HKSERIES and then go enter on the system devmfc. But I want some graphical friendly image to test the performance of tvbox as mini pc and because this I try to install xfce version of armbian. Thanks.

I'm been trying to install Armbian on this TV.BOX console. I already test bookworm xfce image of Armbian as like the last XFCE image → Armbian_community_26.2.0-trunk.357_Aml-s9xx-box_noble_current_6.18.7_xfce_desktop I als test minimal images ad they don't work. The spces of console are : Processor (CPU)Amlogic S905X3 Quad-core ARM Cortex-A55, up to 1.91GHz Graphics (GPU)Mali-G31 MP2 RAM4GB DDR3 Storage (ROM)32GB eMMC Video OutputHDMI, supports up to 8K@24fps (Android system) and 1080p (EmuELEC system) Connectivity2.4G/5G Dual-band Wi-Fi, 10/1000M Ethernet LAN, Bluetooth 4.0 Ports1x USB 3.0, 4x USB 2.0, HDMI, Ethernet, DCIN (Power), TF card slot, AV output I test to boot the stock images just after download them and the boot shows the HK1Series and then goes to internal android system (tvbox) so failed. When I do the steps to put dtb file, edit extlinux.conf and rename properly u-bott to u-boot.ext (I search and test test many dtb files as like meson-sm1-hk1box-vontar-x3.dtb, meson-sm1-h96max-x3.dtb, sm1_s905x3_4g_1gbit.dtb, sm1_s905x3_4g.dtb as like others that I download on web when I search info about install armbian on s905x tv boxes). I also try to see if I can edit a .dts file and then convert to .dtb qhen I did It doesn't work. So none of steps above works. But I find one image system that works called devmfc that has only a minimal image similar to a server image only with tty text. https://github.com/devmfc/debian-on-amlogic/releases I inspect the .image of this system, and I find that if I copy the boot.scr, boot.script and cfgload to the /boot partiton of the armbian systems and boot the Sper Console it goes to a pink screen and then after a minute just reboot or goes to hkseries system. So I think if I can edit boot.scr, bootscript and cfgload maybe I can put the right data to force boot the real kernel of armbian. Maybe then armbian works. I use Linux and try to open those files with text editor but doesn't work. Anyone knows How I can edit this files ? Any user can boot armbian on this console TvBox ? Thanks.

Hello, I have some troubles with this TVBOX: it runs armbian and other distros correctly, using the meson-gxm-t95z-plus.dtb but sometimes wifi goes into kernel panic at boot, and when it does, the whole system becomes unstable (i.e. not rebooting, eth0 hangs...). I have extracted the original .DTB from the only firmware that exists for this box, the ancient 6.0 Marshmellow Android (I guess it's a 3.x kernel...). I attach it to this message hoping someone more expert than me can help in making it work ina more stable manner. I attach a picture of the board also, it reads "M8S". Box has 2GB ram and 16GB eMMC, brcmfmac wifi/bt and ZTE PHY chip. meson1.dtb

Hello - if someone get this type of TV Box from ebay (10€ ) - and dont have an GoogleAccount or do not want use the ADB way. The switch is located in one corner but not soldered. Use a small cable to put GND from end of arrow where the pointing of arrow in picture - to do the reset - (during restart just hold some seconds and device did start from SD-Card -) This device also features a RX/TX -Console and Jtag Interface - you find it if you take closer look.

There's no armbian community image available to this device, don't flash images from other users, you will need to build your images, for tv-box it's all at your own risk, build your armbian image by applying this custom files use this DTS

Issue booting Multitool on RK322x Box (Kingston eMCP) - Red IR Light Only Hi everyone, First of all, thank you for this incredible project. Bringing new life to these generic boxes is vital work. I am struggling to boot the Multitool on an "RPC Plus" TV Box. Here are my hardware specs and the steps I’ve taken so far: Hardware Specs: SoC: Rockchip RK3228A. Storage/RAM: 8GB Kingston eMCP (Chip ID: O8EMCP08-ELSCV100). SD Card: 16GB Lexar microSD (Class 10). Board LEDs: POWER, NET, and IR. Since the official download links for the Multitool are currently down (I get a 404 error idk why), I had to compile it myself on a Debian machine using the https://github.com/paolosabatino/armbian-build?tab=readme-ov-file repo and the ./create_image.sh rk322x script. I flashed the 500MB image to a 16GB Lexar card using BalenaEtcher and placed the Armbian minimal forky (6.18.7) image inside the /images folder (file name Armbian_community_26.2.0-trunk.357_Rk322x-box_forky_current_6.18.7_minimal.img.xz). The problem is that the box just won't boot from the SD card. When I hold the reset button and plug the power, the only thing I get is a static red light on the IR LED—no HDMI signal, no activity on the Power or Net LEDs, nothing. Android still boots fine if I pull the card out, so the hardware is okay, but it seems the boot process is hanging. I've tried both the reset and update buttons with different timings but no luck so far. I’m attaching pictures of the board and the chip. Any help to get this thing past the red light would be great. I'm putting the pictures of the board here in case it helps. Thanks! IMG_6826.HEIC IMG_6827.HEIC

Installed to the EMMC with armbian-install and no issues it all. Took about 10 minutes and now boots from the EMMC with no SD card inserted. I think I paid $35AU for this thing and it came with the remote, a bluetooth keyboard, HDMI cable and power supply. Absolute bargain when you compare it to the current price of Rasperry PI's especially when it comes with it's own case and internal storage. Thanks to everyone who contributed to getting these images out there, it's fantastic. I've also got the IR remote working. I followed rafman's post but this didn't fully work for me. It allowed the remote to work and I could see it was working with ir-keytable -t but the desktop and any open apps wouldn't respond to it. The solution was to copy the toml file to /etc/rc_keymaps/magcubic.toml then edit /etc/rc_maps.cfg and add the following to the bottom of the file * rc-empty <whatever_name>.toml * rc-empty magcubic.toml Adding the line to the rc.local file was not required. I've attached a picture of the remote and the toml file I created. I didn't map the buttons in the top right section as this remote has a learning function and you're supposed to learn the codes from your TV remote. But here are the codes my remote was using for these buttons by default. Power 0x1f1 Set 0x1f2 TVIN 0x1f3 VOL- 0x1f4 VOL+ 0x1f5 Edit: If you are going to use on media player apps you will probably want to edit the toml file and change "KEY_OK" to "KEY_SPACE". OK doesn't let you select things with the OK button but SPACE does. magcubic.toml

Version 3 Has been released! Complete UI Overhaul The entire user interface has been rebuilt from the ground up using Qt QML, delivering a modern automotive HMI experience optimized for touchscreen displays. New Home Screen - Large centered clock with configurable 12-hour/24-hour format - Gradient background (#00021A → #001D3F) - Swipe navigation to media player - Clean, minimal design with Readex Pro typography New Bottom Navigation Dock - 5-button dock: Home | Music | Android Auto | Volume | Settings - Always visible for quick access (except when running AA) - Icon-based navigation with visual feedback New Music Player - Album art display with track metadata - Playback controls (Previous, Play/Pause, Next) - Integrated with system media Redesigned Settings - Modern two-column layout with left sidebar navigation - 8 categories: General, Video, Audio, Input, Bluetooth, WiFi, System, About - Toggle switches, sliders, and radio buttons - Real-time system info (CPU temp, memory, frequency) - Live date/time display in header New Features - 12/24-Hour Time Toggle: Switch between time formats in Settings → General - Readex Pro Font: Variable weight font for consistent automotive typography - Modernized UI: The Original Crankshaft-NG was just not suitable for car use so i had to refresh it Technical Changes - Qt Widgets → QML Migration — Complete rewrite of UI layer - UIBackend Bridge — New C++ backend class exposing 50+ properties to QML - EGLFS Optimized — Designed for direct framebuffer rendering - No Animations — Instant transitions for 1GB RAM constraint - Centralized Theming — Theme.qml singleton for consistent styling Removed - GPIO settings (not applicable to TV Boxes) - DAC settings (using ALSA directly) - RTC settings (no CMOS battery, NTP only) - TSL2561 light sensor support (Pi-specific) - Camera module settings (Pi-specific) Bug Fixes - Fixed Cursor issue by utilizing Cursor plane (41, z-pos 2) - Fixed std::mutex missing include in RtAudioOutput - Fixed ColorOverlay import for Qt GraphicalEffects - Fixed time display showing 24hr with AM/PM suffix - Fixed buffer overflow warning in FFmpegDrmVideoOutput - Fixed QCursor conversion error in autoapp.cpp Known Issues: - Music player metadata not populated (requires media service integration, will be done in the next patch) - Volume popup not implemented (this require modifying the asound.conf before implementing) Issues? Open a ticket in https://github.com/Harleythetech/openauto-rk3229-armbian/issues Download https://github.com/Harleythetech/openauto-rk3229-armbian/releases/tag/oark322x-V3.0.0-alpha

If this is AW869A chip then it uses the AIC 8800 Linux Driver. My X98H TV box has a AIC8800 chip in it. https://linux-sunxi.org/Wifi#AW869A AW869A The AW869A is a highly integrated module with Dual band WiFi6 combination solution to support 1 × 1 IEEE 802.11b/g/n/ac/ax WLAN standards It uses the aic8800 firmware. A driver can be found at AIC 8800 Linux Driver. You'll need to compare the GPIO settings. Your Android dts uses HEX the mainline kernel is using DEC. https://www.rapidtables.com/convert/number/hex-to-decimal.html?x=12 rfkill { compatible = "allwinner,sunxi-rfkill"; status = "okay"; chip_en; power_en; pinctrl-0 = <0x63>; pinctrl-names = "default"; phandle = <0xcc>; wlan { compatible = "allwinner,sunxi-wlan"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; wlan_busnum = <0x01>; wlan_power; wlan_regon = <0x23 0x06 0x12 0x00>; wlan_hostwake = <0x23 0x06 0x0f 0x00>; wakeup-source; phandle = <0xcd>; }; bt { compatible = "allwinner,sunxi-bt"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; bt_power; bt_rst_n = <0x23 0x06 0x13 0x01>; phandle = <0xce>; }; }; btlpm { compatible = "allwinner,sunxi-btlpm"; status = "okay"; uart_index = <0x01>; bt_wake = <0x23 0x06 0x11 0x00>; bt_hostwake = <0x23 0x06 0x10 0x01>; wakeup-source; phandle = <0xd0>; }; Mainline dts: https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L87-L95 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L182-L200 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L278-L297 The specific values <0x23 0x06 0x12 0x00> generally map to: 0x23: The controller or bank ID: pinctrl@300b000 { phandle = <0x23>; 0x06: The specific GPIO pin number: In Allwinner's pinctrl driver, banks are 32 pins wide. The formula is: (Bank_Letter_Index * 32) + Pin_Number 1. The Bank Index Map Bank Index PA 0 PB 1 PC 2 PD 3 PE 4 PF 5 PG 6 PH 7 PI 8 0x12: The active-high/low flags or drive strength. In the 3-cell GPIO format used by Allwinner (sunxi), the third cell (e.g., 0x12) is a bitmask that defines the electrical properties of the pin. To decode 0x12 (which is binary 0001 0010), you break it down into bits: 1. Bitmask Breakdown for 0x12 Bit 0 (0x01): Active Polarity. 0 = Active High. 1 = Active Low (Our bit 0 is 0, so this is Active High). Bit 1 (0x02): Open Drain / Open Source. 0 = Push-Pull. 1 = Single-ended/Open-Drain (Our bit 1 is 1, so this is Open-Drain). Bit 4 (0x10): Internal Pull-up. 0 = No pull-up. 1 = Pull-up Enabled (Our bit 4 is 1, so this is Pull-up Enabled). Summary of 0x12: This pin is configured as Active High, with an Open-Drain output and an internal Pull-up resistor enabled. 0x00: Reserved or additional configuration. In Allwinner-based systems (like the H6 or H616), this value is defined in the GPIO controller's device tree binding documentation within the Linux kernel source code. The structure is documented in the kernel under Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml

If you can get termux app to run in android, you may be able to dump the dtb, which may give you clues as to the compatability of the chip. I have issues with some tv boxes with termux versions, but there are older versions available if the current one in playstore won't load or just doesn't work. su -c 'dd if=/sys/firmware/fdt of=<USB_PATH>/device.dtb' or simply su -c 'cp /sys/firmware/fdt <USB_PATH>/device.dtb' [Change USB_PATH as required, of course] The path /sys/firmware/fdt is correct for accessing the in-memory DTB on most running Linux/Android systems. The link http://nskhuman.ru/allwinner/krugh618.php?np=3 refers to what looks like your box or similar: "The board contains a microcircuit with the designation HK5236F - this is a hybrid microcircuit, its possible analogue is AW869A manufactured by Allwinner. AW869A is a dual-band WiFi6, BT5.2 highly integrated module, supporting WLAN 1*1 IEEE 802.11a/b/g/n/ac/ax and BT 5.2 standard, can realize WLAN/BT, has low power consumption" The links after that text give more info....

This is a great thread. I've had a magcubic android 12 box I've been using for a while just to watch things off a USB when we stay at hotels. It looks like the one in this video but the chip ID's are different. Mine seems to be running with Samsung memory, the clock chip? is FD650 instead of FD6551 and the wifi chip is labelled as HK5236F. Most hotel TV's don't support modern video codecs so this has worked ok. But I want to look at accessing my NAS remotely and this box is a bit of a dud if you want to install your own apps. Play store doesn't work, aurora store doesn't work. Tried sideloading Tailscale and it just crashes. While doing some research I noticed it also seems to be sold under the Vontar brand so I flashed @Nick A "Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img" to an SD card and it booted up. Happy days. It appears to have ethernet but I have not plugged it in yet. No wifi though. I just have 2 questions. 1. Is there any way this can be made to boot from internal storage or do I need to keep the SD card in if I want to run Armbian on it? 2. Is there a driver available for this wifi chip and do I need to mess around updating the boot image or can I just run a command for it? I'm not a regular linux user but I've got a bit of experience messing around. I don't currently have an environment setup to build my own image but I've played around with WSL before so I could probably set something up. Thanks for everyone that has contributed to this. It's good to make use of these boxes considering how cheap they are.

Inspired by the incredible work @jock and @ilmich have done to make the RK322x platform stable on mainline Linux, I decided to tackle the application side of things. My goal was to turn these "e-waste" TV boxes into fully functional, low-latency Android Auto head units for our cars. This fork of OpenAuto is built as one of my "Is it possible to turn this into that?" projects. It turned out to be one heck of a nightmare to pull off, but at the same time a lot of fun because I can see the potential of these TV Boxes as something you can actually put in your car and turn into a usable head unit! System Requirements Target Device: RK322x TV Box (e.g., MXQ Pro 4K). OS: Armbian Bookworm or Trixie (Kernel 6.1+ recommended). RAM: 1GB recommended. FFMPEG Installed: This build requires a specific build of ffmpeg that can be found here. Release: v2.0.0-alpha This release represents a major architectural overhaul. I have removed heavy dependencies (PulseAudio, QtAudio, GStreamer) in favor of a lean, direct-to-hardware pipeline using RtAudio (ALSA) and FFmpeg v4l2_request. Download: https://github.com/Harleythetech/openauto-rk3229-armbian/releases Technical Details Video Engine: Switched from GStreamer to a custom FFmpeg + V4L2-Request backend. Leverages the v4l2drmprime patch set for Zero-Copy rendering. Enables full hardware H.264 decoding on Rockchip stateless decoders. Result: Stable 1080p 60fps stream on a 1GB RAM device. Audio Overhaul: Replaced PulseAudio and QtAudio with RtAudio. This creates a direct, low-latency path to the ALSA hardware driver. Display: Targets linuxfb (Framebuffer) by default instead (eglfs and ffmpeg have issues when you run them together due to DRM master lock) Configuration This release requires a specific ALSA configuration to allow audio mixing (dmix) without PulseAudio. Create/Edit /etc/asound.conf: pcm.!default { type asym playback.pcm "dmix_hdmi" capture.pcm "plug_null" } ctl.!default { type hw card 0 } pcm.plug_null { type plug slave.pcm "null" } pcm.dmix_hdmi { type dmix ipc_key 1024 ipc_perm 0666 slave { pcm { type hw card 0 device 0 } format S16_LE rate 48000 channels 2 period_size 512 buffer_size 4096 } bindings { 0 0 1 1 } } Known Issues Invisible Cursor: The mouse cursor works but is currently invisible when the FFmpeg video backend is active (rendering layer order issue). Backend Fallback: In rare edge cases where DRM initialization fails, the app may incorrectly default to Qt software output. Probably more, i haven't tested it that much Development Status: Active & Seeking Contributors Currently, I am the sole maintainer focusing on the RK322x platform (specifically the RK3229). I am actively looking for developers interested in expanding support to other devices (such as RK3328, RK3399, or Allwinner H3/H6). If you have experience with C++, Qt, or V4L2/DRM and want to help turn these TV boxes into capable head units, contributions are highly welcome! Repository: https://github.com/Harleythetech/openauto-rk3229-armbian Credits: @jock and @ilmich for ffmpeg patches and the csc-armbian-for-rk322x-tv-box-boards opencardev for openauto and aasdk

That isn't what you use for amlogic tv boxes. Follow the instructions linked from the download page: https://www.armbian.com/amlogic-s9xx-tv-box

Hello everyone! I have TV box MX10 based on RK3328. It freezes on the manufacturer's label on boot. So I need to update the firmware. I followed the instructions from 1st post but didn't get success. When I run "Erase eMMC" it change modal windows with messages very fast and at the end shows "Successfully done". The same when I run "Write new image". It shows immediately that it is flashed. I have run the shell and checked `dmesg` and found there errors like "group start error -110, status 0x0". What does it mean? Then I installed "rkdeveloptool" and followed steps from this thread: - ld - I see TV box in Loader mode - rd 3 - switch to Maskrom mode - dd loader.bin - done - wl 0x0 armbian.img - done - rd - toexit when I run tv box I got the same freeze on logo and that's all Is eMMC died? or?

I installed Waydroid on an Amlogic Meson GXM (S912) TV box. The SOC has a Mali-T820 GPU, and the box has 2 GB of RAM and 16 GB of eMMC. This was easy to do and Waydroid worked, but it was very slow, even before it heated the SOC to 80°C, which is probably its throttling limit. I removed Waydroid because it was too slow. I wasn't trying anything demanding. Even navigating Android Settings was ridiculously slow. This is a bit surprising because the hardware was designed for running Android. I was not running much else, just Wayfire and one or two Alacritty consoles. I don't think I was running out of memory. Is it possible to get decent Waydroid performance on other arm64 hardware?

Hi there this is not an x96 but a 'Q10 android TV' the mb looks the same as x96 i have tried some miniarch and your armbians versions (thanks for sharing) but nothing works, anyone can identificate if this mb is compatible ? There is no information about this exact model since it looks very recent. thanks in advance

@shexplorer I did something similar to a tv box i had around, not this model. Generally, the cpu comes with some sort of uboot. Written in firmware not emmc. The catch is that that uboot usually writes its persistent environment on the eMMC. And most of the time its not even a file on a partition, like in (and this is an example) between bytes 2000 to 8000 of the mmc. This uboot is only visible via serial console. no hdmi output. (and its quite old) This uboot then attempts to chainload the mmc or usb uboot. And its at this phase you get image. So on my setup, i had CPU uboot but no environment (because i smashed it with my armbian image...), and that environment was needed to boot both mmc or usb. Using a serial port (and pressing control +c ) i was able to instruct uboot it to boot armbian on the usb drive. And i mean manually with command like fatload 0x1000000 usb0.1 linux.img. But every time i reloaded would go back to the endless loop. So the next step was to find a stock image of my device and dump it into the emmc, via usb booted linux. (i actually only copied like the 1st 10MB, only needed uboot env, not the chinese android) Please know that this is not the image you download from any manufacturer website, those are snap-in upgrades that only change part of the emmc, you need a image that someone extracted with dd command from the entire mmc. After that i swore to never touch that emmc again... Maybe this is your problem too Get a serial connected to your device and check if you can see the cpu level uboot. If it is the same issue, maybe someone here can give you the 1st 10MB of their device, if you create a new thread asking for it. Edited to place the "e" on emmc. tnx johlnx for the fix

@kingbecher This is now off topic for this thread, but you need to look at: https://www.armbian.com/amlogic-s9xx-tv-box