Search the Community

Support for rotation is better in modern 6.18.y Linux. Fastest is to download image and try https://www.armbian.com/boards/roc-rk3399-pc But VPU acceleration in rotated screen might be a problem ... and you will need to generate Gnome desktop image to facilitate Wayland or no fun.

Hi everybody, I running Helios64 with kernel 6.12.58 since a long time and the prahal dtb file rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and my helios64 work well. Today, Armbian upgrade to 6.18.10 kernel. Is this update use the same change or patch like in rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp ? Is rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp work with 6..18.10 kernel ? Is I must to downgrade to 6.12.58 kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and freeze at this kernel version ? Thanks for answer.

Hi all, I would like to ask support for the board EMB-3531. I'm having problem with booting this board from SD card. Here are some informations about this board. I hope that someone can help me with it. Thank you so much! I try to erase the emmc and flash the MiniLoaderAll.bin but it doesn't help. Or i don't have a correct image with armbian for this board. https://my.kos.org.cn:5154/rockchip/EMB3531/emb3531.pdf

Hello, this quick tutorial is to introduce an experimental Debian and Ubuntu APT repository to install ffmpeg compiled with v4l2request and v4l2drmprime patches developed by Linux kernel, LIbreELEC and Kodi folks to allow hardware video decoding on stateless decoders like those implemented in Rockchip and Allwinner SoCs for h.264, h.265, vp8 and vp9 codecs. The repository introduces a new ffmpeg package that integrates and substitues the base ffmpeg package and its related packages. Preconditions: Mainline kernel 6.1 or more recent armhf or arm64 architecture Supported distributions: Debian 12 - Bookworm Debian 13 - Trixie Ubuntu 22.04 - Jammy Ubuntu 24.04 - Noble Rockchip and Allwinner have already been tested, but this should work on other platforms with stateless decoders supported in kernel APT REPOSITORY SETUP To install the repository, just copy and paste the lines in a terminal: $ sudo wget http://apt.undo.it:7242/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc $ . /etc/os-release && echo "deb http://apt.undo.it:7242 $VERSION_CODENAME main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list $ echo -e "Package: *\nPin: release o=apt.undo.it\nPin-Priority: 600" | sudo tee /etc/apt/preferences.d/apt-undo-it INSTALL FFMPEG AND MPV PACKAGES $ sudo apt update $ sudo apt install ffmpeg mpv SETUP MPV CONFIG FILE $ sudo mkdir -p /etc/mpv $ echo -e "hwdec=drm\ndrm-drmprime-video-plane=primary\ndrm-draw-plane=overlay" | sudo tee /etc/mpv/mpv.conf You can now play your videos using mpv and they should run with hardware decoding if supported, either in virtual terminals or in X11/Wayland windows! Enjoy! Notes: your mileage may vary a lot: the more recent is the kernel version, the better is support (you may need edge kernel) bug: when rendered in X11/Wayland window, video may show scattered tiles during frames bug: Lima driver (Mali 400/450) shows a red/pink tint when video is played in X11/Wayland (see https://github.com/mpv-player/mpv/issues/12968) (workaround below: https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/?do=findComment&comment=177968) you may want to add --gpu-hwdec-interop=drmprime-overlay to the mpv command line if used in pure virtual terminal (no X, no Wayland) to use direct-to-overlay output Panfrost driver should work flawlessy 10 bit HEVC are generally supported on all Rockchip devices (rk322x, rk3288, rk33x8, rk3399), but Allwinner H3 have no hardware support for that

This week in Armbian development saw a significant expansion of hardware support, including new board images and compatibility for devices such as the Ariaboard Photonicat 2, SpacemiT MUSE Book, NanoPC T6 Plus, and Mekotronics R58S2. Kernel patches were updated across multiple platforms, notably for Rockchip and Sunxi families, enhancing stability and performance. Several new modules were introduced in the configuration framework, including browser-based code-server, memory management, Docker log viewing, and subscription tracking. Improvements to documentation, security hardening, and code formatting were also implemented. Notable fixes addressed USB, Ethernet, and device-specific issues, while ZFS functionality and tuning interfaces received updates. The release continues Armbian’s commitment to broad hardware support and robust system features. Changesaction: fix typos, update defaults, and harden GPG signing. by @igorpecovnik in armbian/build#9613Add Ariaboard Photonicat 2 support for rockchip64-6.18. by @HackingGate in armbian/build#9535Add container_type field to Uptime Kuma config. by @igorpecovnik in armbian/configng#776Add image and reusable slug for Qidi X-4. by @Shadowrom2020 in armbian/armbian.github.io#262Add Laptop SpacemiT MUSE Book. by @pyavitz in armbian/build#9591Add line breaks to improve .md rendering. by @igorpecovnik in armbian/configng#784Add NanoPC T6 plus image. by @igorpecovnik in armbian/armbian.github.io#266Add radxa-dragon-q6a to nightly release blacklist. by @igorpecovnik in armbian/armbian.github.io#260add recomputer rk3588-devkit support. by @ackPeng in armbian/linux-rockchip#460add rockchip patch for fusb302 to support aw3561. by @ackPeng in armbian/linux-rockchip#456add rockchip zbit mtd spi flash support. by @ackPeng in armbian/linux-rockchip#464Add rtl8710bufw_SMIC.bin for RTL8188GU WiFi USB. by @Shadowrom2020 in armbian/firmware#121add support for imx708 raspberry pi v3 camera. by @ackPeng in armbian/linux-rockchip#457Add trixie and noble to nightly manual targets. by @igorpecovnik in armbian/armbian.github.io#263Add xfce desktop for riscv64 legacy branch in stable builds. by @igorpecovnik in armbian/armbian.github.io#264aic8800-dkms extension. by @Shadowrom2020 in armbian/build#9578arm64: dts: rockchip: add Mekotronics R58S2. by @HeyMeco in armbian/linux-rockchip#461armbian-kernel: improve code documentation and formatting. by @igorpecovnik in armbian/build#9559Board image: Add Mekotronics R58S2. by @igorpecovnik in armbian/armbian.github.io#265Board: Add Mekotronics R58S2. by @HeyMeco in armbian/build#9610Bump geekyeggo/delete-artifact from 5 to 6. by @igorpecovnik in armbian/os#443docs: expand GitHub Actions section with examples and inputs reference. by @igorpecovnik in armbian/documentation#900docs: reorganize ZFS documentation with proper tab formatting. by @igorpecovnik in armbian/configng#779docs: simplify code-server documentation footer. by @igorpecovnik in armbian/configng#792Dozzle: Proper image. by @igorpecovnik in armbian/configng#775families: sm8550: Limit kernel version to 6.18.18. by @kasimling in armbian/build#9604feat: add code-server module for browser-based VS Code. by @igorpecovnik in armbian/configng#790feat: add comprehensive memory management module. by @igorpecovnik in armbian/configng#781feat: add Dozzle Docker log viewer module. by @igorpecovnik in armbian/configng#773feat: add Wallos subscription tracker module. by @igorpecovnik in armbian/configng#785feat: ZFS pool import and scan functionality. by @igorpecovnik in armbian/configng#782Fix Docker image configuration for GitHub Actions. by @igorpecovnik in armbian/docker-armbian-build#12fix: force destroy VMs when graceful shutdown fails. by @igorpecovnik in armbian/configng#793fix: improve kvmtest module security, UI, and add channel selection. by @igorpecovnik in armbian/configng#789fix: resolve mixed indentation in prometheus heredoc. by @igorpecovnik in armbian/configng#794framework artifact-rootfs - remove the last vestige of LEGACY_DEBOOTSTRAP. by @tabrisnet in armbian/build#9599HACK: Enable PCIe switch on RK3399. by @retro98boy in armbian/build#9574KDE Neon: add more packages for touchscreen devices. by @kasimling in armbian/build#9551mkspi: fix devicetree opp voltage settings. by @redrathnure in armbian/build#9603nanopi-zero2: add USB support for RK3528 (current + edge). by @rubycomm in armbian/build#9500OrangePi5Pro: Comprehensive HW Support: YT6801 PCIe-Eth, Codec ES8388 Audio, eFUSE & U-Boot v2025.10. by @c127dev in armbian/build#9600qcom/sc8280xp: sync microsoft blackrock (windows dev kit 2023) latest firmware for mainline kernel. by @rbqvq in armbian/firmware#122Qidi X-6: fix devicetree opp voltage settings. by @Shadowrom2020 in armbian/build#9577refactor: update KVM test images to latest releases. by @igorpecovnik in armbian/configng#783rock-3a: bump uboot to v2026.04-rc4. by @EvilOlaf in armbian/build#9576rockchip-rv1106: Enable (=m) Realtek 8188EU wifi. by @vidplace7 in armbian/build#9607rockchip64-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9587rockchip64: rk3528: fix USB OTG and ethernet for NanoPi Zero2. by @rubycomm in armbian/build#9597sm8550-6.18: Fix TF card IO performance regression. by @kasimling in armbian/build#9546SpacemiT MUSE Book: Fixup SRC_CMDLINE var. by @pyavitz in armbian/build#9612stmmac: Refactor Phytium ethernet patches into modular components. by @igorpecovnik in armbian/build#9585style: simplify markdown formatting in Wallos footer. by @igorpecovnik in armbian/configng#787sunxi-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9611sunxi: drm/gem-dma: Support dedicated DMA device for allocation. by @EvilOlaf in armbian/build#9605sunxi: edge: bump to 7.0. by @EvilOlaf in armbian/build#9549sunxi: Enable device mapper snapshot support. by @frank-f in armbian/build#9590sunxi: fix iommu driver patch to allow compilation. by @EvilOlaf in armbian/build#9592sunxi: fix Unhandled Exception in EL3. and/causing secondary cpus not coming online. by @EvilOlaf in armbian/build#9586sunxi: remove BSP GMAC/EPHY patch that breaks H6 internal EMAC. by @igorpecovnik in armbian/build#9609uefi edge: bump to 7.0. by @EvilOlaf in armbian/build#9547uefi-arm64-6.12: fix stmmac compilation errors. by @igorpecovnik in armbian/build#9596uefi-x86-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9588update seeed studio rk3576 devkit camera and dp overlay. by @ackPeng in armbian/linux-rockchip#463Update some board csc file. by @retro98boy in armbian/build#9573Update ZFS tuning recommendations and remove settings view. by @igorpecovnik in armbian/configng#780ZFS Performance Tuning Interface. by @igorpecovnik in armbian/configng#777[2026.5] - framework rootfs-create: remove LEGACY_DEBOOTSTRAP, use only the upstream mmdebstrap. by @tabrisnet in armbian/build#9512View the full article

This week in Armbian development saw a significant expansion of hardware support, including new board images and compatibility for devices such as the Ariaboard Photonicat 2, SpacemiT MUSE Book, NanoPC T6 Plus, and Mekotronics R58S2. Kernel patches were updated across multiple platforms, notably for Rockchip and Sunxi families, enhancing stability and performance. Several new modules were introduced in the configuration framework, including browser-based code-server, memory management, Docker log viewing, and subscription tracking. Improvements to documentation, security hardening, and code formatting were also implemented. Notable fixes addressed USB, Ethernet, and device-specific issues, while ZFS functionality and tuning interfaces received updates. The release continues Armbian’s commitment to broad hardware support and robust system features. Changesaction: fix typos, update defaults, and harden GPG signing. by @igorpecovnik in armbian/build#9613Add Ariaboard Photonicat 2 support for rockchip64-6.18. by @HackingGate in armbian/build#9535Add container_type field to Uptime Kuma config. by @igorpecovnik in armbian/configng#776Add image and reusable slug for Qidi X-4. by @Shadowrom2020 in armbian/armbian.github.io#262Add Laptop SpacemiT MUSE Book. by @pyavitz in armbian/build#9591Add line breaks to improve .md rendering. by @igorpecovnik in armbian/configng#784Add NanoPC T6 plus image. by @igorpecovnik in armbian/armbian.github.io#266Add radxa-dragon-q6a to nightly release blacklist. by @igorpecovnik in armbian/armbian.github.io#260add recomputer rk3588-devkit support. by @ackPeng in armbian/linux-rockchip#460add rockchip patch for fusb302 to support aw3561. by @ackPeng in armbian/linux-rockchip#456add rockchip zbit mtd spi flash support. by @ackPeng in armbian/linux-rockchip#464Add rtl8710bufw_SMIC.bin for RTL8188GU WiFi USB. by @Shadowrom2020 in armbian/firmware#121add support for imx708 raspberry pi v3 camera. by @ackPeng in armbian/linux-rockchip#457Add trixie and noble to nightly manual targets. by @igorpecovnik in armbian/armbian.github.io#263Add xfce desktop for riscv64 legacy branch in stable builds. by @igorpecovnik in armbian/armbian.github.io#264aic8800-dkms extension. by @Shadowrom2020 in armbian/build#9578arm64: dts: rockchip: add Mekotronics R58S2. by @HeyMeco in armbian/linux-rockchip#461armbian-kernel: improve code documentation and formatting. by @igorpecovnik in armbian/build#9559Board image: Add Mekotronics R58S2. by @igorpecovnik in armbian/armbian.github.io#265Board: Add Mekotronics R58S2. by @HeyMeco in armbian/build#9610Bump geekyeggo/delete-artifact from 5 to 6. by @igorpecovnik in armbian/os#443docs: expand GitHub Actions section with examples and inputs reference. by @igorpecovnik in armbian/documentation#900docs: reorganize ZFS documentation with proper tab formatting. by @igorpecovnik in armbian/configng#779docs: simplify code-server documentation footer. by @igorpecovnik in armbian/configng#792Dozzle: Proper image. by @igorpecovnik in armbian/configng#775families: sm8550: Limit kernel version to 6.18.18. by @kasimling in armbian/build#9604feat: add code-server module for browser-based VS Code. by @igorpecovnik in armbian/configng#790feat: add comprehensive memory management module. by @igorpecovnik in armbian/configng#781feat: add Dozzle Docker log viewer module. by @igorpecovnik in armbian/configng#773feat: add Wallos subscription tracker module. by @igorpecovnik in armbian/configng#785feat: ZFS pool import and scan functionality. by @igorpecovnik in armbian/configng#782Fix Docker image configuration for GitHub Actions. by @igorpecovnik in armbian/docker-armbian-build#12fix: force destroy VMs when graceful shutdown fails. by @igorpecovnik in armbian/configng#793fix: improve kvmtest module security, UI, and add channel selection. by @igorpecovnik in armbian/configng#789fix: resolve mixed indentation in prometheus heredoc. by @igorpecovnik in armbian/configng#794framework artifact-rootfs - remove the last vestige of LEGACY_DEBOOTSTRAP. by @tabrisnet in armbian/build#9599HACK: Enable PCIe switch on RK3399. by @retro98boy in armbian/build#9574KDE Neon: add more packages for touchscreen devices. by @kasimling in armbian/build#9551mkspi: fix devicetree opp voltage settings. by @redrathnure in armbian/build#9603nanopi-zero2: add USB support for RK3528 (current + edge). by @rubycomm in armbian/build#9500OrangePi5Pro: Comprehensive HW Support: YT6801 PCIe-Eth, Codec ES8388 Audio, eFUSE & U-Boot v2025.10. by @c127dev in armbian/build#9600qcom/sc8280xp: sync microsoft blackrock (windows dev kit 2023) latest firmware for mainline kernel. by @rbqvq in armbian/firmware#122Qidi X-6: fix devicetree opp voltage settings. by @Shadowrom2020 in armbian/build#9577refactor: update KVM test images to latest releases. by @igorpecovnik in armbian/configng#783rock-3a: bump uboot to v2026.04-rc4. by @EvilOlaf in armbian/build#9576rockchip-rv1106: Enable (=m) Realtek 8188EU wifi. by @vidplace7 in armbian/build#9607rockchip64-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9587rockchip64: rk3528: fix USB OTG and ethernet for NanoPi Zero2. by @rubycomm in armbian/build#9597sm8550-6.18: Fix TF card IO performance regression. by @kasimling in armbian/build#9546SpacemiT MUSE Book: Fixup SRC_CMDLINE var. by @pyavitz in armbian/build#9612stmmac: Refactor Phytium ethernet patches into modular components. by @igorpecovnik in armbian/build#9585style: simplify markdown formatting in Wallos footer. by @igorpecovnik in armbian/configng#787sunxi-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9611sunxi: drm/gem-dma: Support dedicated DMA device for allocation. by @EvilOlaf in armbian/build#9605sunxi: edge: bump to 7.0. by @EvilOlaf in armbian/build#9549sunxi: Enable device mapper snapshot support. by @frank-f in armbian/build#9590sunxi: fix iommu driver patch to allow compilation. by @EvilOlaf in armbian/build#9592sunxi: fix Unhandled Exception in EL3. and/causing secondary cpus not coming online. by @EvilOlaf in armbian/build#9586sunxi: remove BSP GMAC/EPHY patch that breaks H6 internal EMAC. by @igorpecovnik in armbian/build#9609uefi edge: bump to 7.0. by @EvilOlaf in armbian/build#9547uefi-arm64-6.12: fix stmmac compilation errors. by @igorpecovnik in armbian/build#9596uefi-x86-6.18: rewrite kernel patches against 6.18.20. by @EvilOlaf in armbian/build#9588update seeed studio rk3576 devkit camera and dp overlay. by @ackPeng in armbian/linux-rockchip#463Update some board csc file. by @retro98boy in armbian/build#9573Update ZFS tuning recommendations and remove settings view. by @igorpecovnik in armbian/configng#780ZFS Performance Tuning Interface. by @igorpecovnik in armbian/configng#777[2026.5] - framework rootfs-create: remove LEGACY_DEBOOTSTRAP, use only the upstream mmdebstrap. by @tabrisnet in armbian/build#9512View the full article

Sorry I'm not able to find the sub category for M4V2 so I chose R4S instead. But please keep in mind that this is a bug report for NanoPi M4V2. So my box has been running well for 5 years without any issue, through multiple system upgrade from armbian buster to trixie. However after I upgrade the kernel from 6.12.58 to 6.18.10 just a couple of days ago, the system started to have some weird behavior. The main symptom is that I'll lose the network connection from the box once it starts up, and it could happen after just a few minutes, or a couple of hours. I have to power cycle the box to get it back online as I don't have any peripherals, and soon I will lose the connection again. Other symptoms I've observed so far: - Once I lost the connection and powered cycle the box, the timestamp in the log looks confusing. Somehow the system clock paused at the moment when system froze. When it boots up, there could be a large gap between the NTP server and it will have to sync up, and I don't even seem to be able to find any logs before this reboot - The line `fdtfile=rockchip/rk3399-nanopi-m4v2.dtb` in `/boot/armbianEnv.txt` looks to be missing, so I added it back but it didn't fix the issue Eventually I downgraded to 6.12.58 with armbian-config, by timing the time window between the bootup and system freeze. After that the issue seems to be gone. Please find the results for `armbianmonitor -u` at https://paste.armbian.com/werujijedo For those who has the same model as mine, please think twice before upgrading. Do backup your data if you'd like to take the risk.

The most current download images for Helios64 are now all provided with linux 6.18.xx. I downloaded a minimal image and checked the dtb: it would not appear to contain the opp-microvolt patch that made Helios64 finally stable. So for the ones who have stability issues again on Helios64, I attached the patched dtb compiled for linux 6.18.xx using the exact same opp-microvolt values as in the previous dtb versions I compiled for linux 6.6 and 6.12. The current linux deb files can be downloaded from beta.armbian.com, the linux 6.18.18 deb files I used can be downloaded from here (to be installed with 'dpkg -i linux*'). In order to install the dtb, simply unzip it, copy it into the proper location, update initramfs and reboot: # install the dtb with the opp-microvolt patch: unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb update-initramfs -u reboot rk3399-kobol-helios64.dtb-6.18.18-opp.zip

[ 1.234958] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 1.235032] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110 PCI support on this SoC has never been fully stable. Patch that tries to mitigate the issue, exists: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.18/rk3399-fix-pci-phy.patch Not really much we can do more - use a kernel that it works, try current one with few reboots, ... I know its not perfect but we have nobody that can afford investing few weeks trying to fix this. Imagine the frustration if nothing will be improved - which I highly suspect for this case.

Hello, I hope you don't have any problem. Maybe me and my brother have defective or more unstable helios64 than you. Only thing I can say that Prahal share here the specifics files rk3399-kobol-helios64.dtb-6.XX.xx-L2-hs400-opp in this forum since two years ago my helios64 and my brother's helios64 work stable only with it. I back to 6.12.58 Kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp file and freeze firmware/kernel with armbian-config.

While waiting for new info, first poke in the dark. rk3399-fix-pci-phy.patch disabled https://testing.armbian.de/r4s/ feel free to test

For information: First reboot and crash same that before use rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp. 😞 Back to 6.12.58, rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and freeze to this setting Me and my brother have helios64 with 6.18.10 Kernel : RAID 10 / LVM / LUKS and crash always when "cryptsetup open..." start Crash when many I/O Crash when use Full CPUs With rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and Kernel 6.12.58 or 6.12.(XX below): Me, never crash but I reboot often and power off often for personal choice. My brother have uptime upper than 100 or 200 days with problem, freeze or crash Bye

I see there's an overlay for the R4S called rk3399-dwc3-0-host, but it already seems to be in host mode by default. I can't figure out how to set it to peripheral mode so I can have some usb-gadget love. Anyone figured out a fix?

Updating via `apt update && apt upgrade` causes Armbian to fail to boot on the single-board computer. I'm attaching the UART logs in the file `failed_log.txt`. Start-Date: 2025-11-13 04:45:12 Commandline: apt -y upgrade Upgrade: armbian-bsp-cli-nanopct4-current:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-dtb-current-rockchip64:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-image-current-rockchip64:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-u-boot-nanopct4-current:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), armbian-firmware:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469) End-Date: 2025-11-13 04:47:04 out: Starting kernel ... efi_free_pool: illegal free 0x00000000f0f09040 "Synchronous Abort" handler, esr 0x96000004 elr: 00000000002856e4 lr : 00000000002702f0000000f3f9b2f0 x0 : dfb6333a7ba2b4b7 x1 : 00000000f3fba060 x2000000 x5 : dfb6333a7ba2b4b7 x6 : 00000000f0d07000 x7 : 00000000000ef98 x11: 00000000f1f0b5bc x12: 000000000000ef98 x13: 000003f558a4 x17: 00000000d8136251 x18: 00000000f1f22d90 x19: 000000000000001 x23: 00000000f1f303c0 x24: 00000000f3fdcff0 x25: 00000000000000001 x29: 00000000f1f0b470 Code: eb04005f 54000061 5resetting ... To reproduce the issue (~13.11.2025-16.11.2025), simply download and flash the current `Minimal/IOT for Armbian Linux v6.12 [Debian] Debian 12 (Bookworm)` images (`https://www.armbian.com/nanopc-t4/`) and run `apt update & upgrade` on a running system, then reboot. After this, the system, regardless of whether the `SD card` or `EMMC` is used, will enter an infinite boot loop (`out` and file `failed_out.txt`). Thank you. failed_log.txt armbian_release.txt normal_log.txt

It seems that the HDMI output does not have any option beyond 1080P. Tried multiple monitors. The font size at uboot stage seems right but the resolution maxed out at 1080P after kernel starts. Tried Armbian 24.2.1 with 6.6.16. Could be related with this: https://forum.manjaro.org/t/rk3399-hdmi-output-for-resolutions-different-than-1080p/90644. but patches should be applied at Kernel 6.4: https://www.phoronix.com/news/Linux-6.4-imx25-Rockchip-4K Attached is the screenshot when connected with DELL 25inch monitor. Should have 2K option. diagnoses: https://paste.armbian.com/gaketoluye Thank you

@jock The schematic is maybe was a wrong example (I just search for rk3399 schematic, and take the first) in this case Leez P710, but I also look at the RK3399_Design_Guide and find a interesting point, UART2 based on the sd card pins!!! I already read a bit regarding the ddrbin_tool.py (which is part of the rkbin), which one could be used to manipulate the rockchip boot loader, but until now I not really understood how this work, then I find this in the Rockpi4 schematic I became enlightened. In the ddrbin_tool_user_guide is the following: * UART info uart id: uart number. 0 for uart0, 1 for uart1, 2 for uart2..., 0xf will disable uart. uart iomux: uart iomux info, 0 for uartn_m0, 1 for uartn_m1, 2 for uartn_m2...(like uart2_m0, uart2_m1,uart2_m2), or 1 for uartn_a, 2 for uartn_b, 3 for uartn_c.(like uar2a, uart2b, uart2c). uart baudrate: uart baudrate should be 115200 or 1500000. I still don't understanding what the iomux (io multiplexing) is, but in theory if I change the uart iomux parameter to 1 then this should means that UART2A is used, which is SD card D0,D1 pins. (Similar concept I see in Amlogic SoCs. ) So I read out the ddrbin parameters from rk3399_ddr_800MHz_v1.27.bin ./tools/ddrbin_tool.py RK3399 -g ddrbin_param.txt ./bin/rk33/rk3399_ddr_800MHz_v1.27.bin then I change the UART parameters in the file ddrbin_param.txt like this: uart id=2 uart iomux=1 uart baudrate=115200 then I write the parameters back ./tools/ddrbin_tool.py RK3399 ddrbin_param.txt ./bin/rk33/rk3399_ddr_800MHz_v1.27.bin Then I build a new loader based on the rk3399_ddr_800MHz_v1.27.bin ./tools/boot_merger ./RKBOOT/RK3399MINIALL_1.27.ini Content of the ./RKBOOT/RK3399MINIALL_1.27.ini [CHIP_NAME] NAME=RK330C [VERSION] MAJOR=1 MINOR=30 [CODE471_OPTION] NUM=1 Path1=bin/rk33/rk3399_ddr_800MHz_v1.27.bin Sleep=1 [CODE472_OPTION] NUM=1 Path1=bin/rk33/rk3399_usbplug_v1.26.bin [LOADER_OPTION] NUM=2 LOADER1=FlashData LOADER2=FlashBoot FlashData=bin/rk33/rk3399_ddr_800MHz_v1.27.bin FlashBoot=bin/rk33/rk3399_miniloader_v1.26.bin [OUTPUT] PATH=rk3399_loader_v1.27.126.bin The result was uploaded in the emmc rkdeveloptool db rk3399_loader_v1.27.126.bin rkdeveloptool ul rk3399_loader_v1.27.126.bin the I connected my microsd sniffer and after some praying I reset the device ... Then the magic is happened 🤩 DDR Version 1.27 20211018 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 MHz, current 856MHz OUT Boot1 Release Time: May 29 2020 17:36:36, version: 1.26 CPUId = 0x0 ChipType = 0x10, 645 SdmmcInit=2 0 BootCa Yes, is working, I have debug output 😁 this is maybe not the best solution but I could start working running Armbian on this device. The key point was: So thanks again the advise.

Hi Armbian community I have a Giada DN74 media player and would like to install Armbian on the box. First I try (through SD card) some community maintained images like the Orange Pi RK3399 or the Firefly RK3399, but none of them worked. Some google search teach me the Rockchip SoCs have fixed boot order (SPI->eMMC->SD card), and this cause my boot issue. Then search again how boot from SD card, the only solution which I find is to erase eMMC, so I erase the eMMC using: "rkdeveloptool ef". Unfortunately the box still not want to boot, so I open the box and try to identify the UART to see what is happening during the boot. I find a 4 pin connector (see images) which I assume this is the UART console, have a label "MCU_D" (Micro Controller Units Debug?) and have 3,3V on first pin and GND on the last pin. I try to use this connector whit some USB-to-UART (PL2303 and FT232RL) with multiple baud rate (115200, 1500000) without output. At this point was able still connect the box through USB and recover Android because MaskRom mode work fine. After some reading on https://opensource.rock-chips.com/wiki_Boot_option I deiced to build u-boot using evb-rk3399_defconfig and flash to the eMMC (which wan was a big mistake). I assume the box is try to boot from eMMC, but stuck there because is only u-boot on the eMMC nothing else. Unfortunately still no UART output (maybe is not UART connector) but also no Maskrom mode. If I understand right jock guide Unbrick Part, the only option to recover the box if I short EMMC CLK pin to GND. So my question is somebody could help me identify the eMMC CLK pin? Some extra info: According the rk3399 hardware design guide, I need to find a 22 ohm resistor near to the CLK pin. The eMMC is a Kingstone EMMC32G-TX29, and the manual write different CLK frequency's, I am don't know what I need to look. I have a Fnirsi dst-210 3in1 (sure not the best), which I could use measurements but I do not know how to set the oscilloscope parameters to find the CLK.

The paste armbian URL displays nothing (anymore?) so without any (new) info from you, no-one can help you. AFAIR, 4K via HDMI connector is only recently available (on RK3588, not sure about RK3399), so make sure you can manage various combinations of U-Boot, kernel, rootfs. So sort of act like a developer, als make sure you have a serial console (debug) cable, else you cannot get any step further. Use a 26.2 based U-Boot and 6.19 rockchip64 kernel I would say, then see what happens.

@kisgezenguz you're welcome. You can check the UART RX/TX paths with the multimeter in diode/continuity mode and checking the continuity against RX (or TX) and the various SMD components. But anyway, if you read 3.3v on all the UART pins, I can guess there are three other hypothesis: * the UART RX/TX pins are correctly connected, but not to the usual debug UART. rk3399 has several uarts, so perhaps that exposed UART is not the same configured in software to be used to log the debug. * MCU_D makes me think that UART is used for the little MCU embedded into rk3399. rk3399 has two small Cortex-M0 cores for very low power tasks. So again that UART is not what you are looking for. * the RX/TX pins are just shorted to high voltage level/pulled ups on purpose (improbable) edit: I just paid attention to the schematic you posted, but it looks it does not match what you've discovered: the schematic says you should read 5.0v on the VCC pin, instead you read 3.3v. Perhaps that MCU_D connector it's definitely not the one you are looking for.

@jock Than you for the hints. If I measure on all (except GND) UART Pin 3.3V is not indicate that all resistor in place? Regarding the rk3399 schematic design, there should be some 100 ohm resistors there. To be honest for me was also very difficult to find the MaskRom pins, search something what is not there is a bit challenging. I measure all black SMD item (far as I know they are resistors), but non of them 100 ohm. (The board other side I do not see any missing resistor) Could you please advise me what I need to look? There is 3 point where possible to solder resistor, how to identify which one I need?

Which DTB did you use? I extracted the Android files and found a resource file named ENTRrk-kernel.dtb. The file began with "Rockchip RK3399 Excavator Board edp (Android)". Could it be possible that the device is compatible with this board?

The sysfs GPIO interface does not allow you to create clock outputs as-is. You'd do better seeing if that pin can be exposed through the sysfs PWM interface. I know the NanoPi M4V2's fan controller works this way (RK3399), and you can set the duty cycle. But you'd have to check if PWM is supported on that pin, and can be used in the way you're hoping. Failing that, it is possible to bit-bang the GPIO lines yourself if you're willing to write some C code. You can use Kernel Timers for fairly accurate timing, as long as you set High Scheduler Priority and Real Time Scheduler Class. Note that kernel timers only have a user specified resolution of 1ns, so you might not hit that frequency exactly.

Hello all. I have an Android-based Yundoo Y8 TV box, which I want to use for UPS management. I want it to be able to run Armbian to install the UPS management software, but I cannot figure out which Armbian I should download. The board is based on Rockchip RK3399. In cpu-z app I see the board identified as rk30sdk, and the hardware is rk30board. Can you please help me identify the board so I can understand which version of Armbian I need? I couldn't find anything in the forum about RK3399... I really appreciate any help you can provide.

Hello Armbian community, I am writing this topic because, despite the drivers for the processor's integrated GPU are installed within the operating system, they do not seem to work properly. Precisely the system seems to work but as soon as I try to play a video it is played by the CPU and not by the GPU with lag and the CPU is at 100%. I leave the link and the attachment of the result of the armbianmonitor -U command that I posted here: https://paste.debian.net/1337993/ it is a compressed tar.gz file since I included all the results of the command Analysis.txt

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