Vontar KK MAX / HK1 RBOX R2 / R3 - RK3566 4GB/32GB(or 64GB)

[Deoptim]

Armbian 24.5.0 Bookworm images (linux-6.1/linux-6.6) for TVBoxes: Vontar KK MAX / HK1 RBOX R2 / HK1 RBOX R3

(the same dts/dtb should work for these TVBoxes)

 

Here is a dts and dtb files, working reworked for mainline:

hk1-rbox-r3-profile-kernel-6.1-6.6.zip

 

(original dts and dtb from TVBox rk-kernel-orig.zip)

 

Checked the following:

• HDMI - works (need to check hot plugging)
• HDMI sound - works
• USB 2.0 - works
• USB 3.0 - works
• SPDIF - should work (I cannot to check)
• SD-Card booting and detection - works
• eMMC install on it (/sbin/nand-sata-install) and detection - works
• RKDevTool installing and loading images on/from eMMC - works
• GPU (bugs/frizzes on mainline are not canceled) - works
• Hardware video acceleration(except for browsers) - works
• Dualboot if you flash new bootloader (SD-Card boot high priority) - works

 

Here are the compiled Armbian images (Bookworm only) with integrated dtb:

https://www.mediafire.com/file/4dwf7ce922x7obq/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.1.87_cinnamon_desktop.img.xz/file

https://www.mediafire.com/file/fjwtxb5gjzip341/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.1.87_minimal.img.xz/file

https://www.mediafire.com/file/iuz4uijgjh5ry1r/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_cinnamon_desktop.img.xz/file

https://www.mediafire.com/file/kofyqabr5k6qxm8/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_minimal.img.xz/file

 

The one of this box itself is HK1 RBOX R3, the photo shows the pins for short to go to the Maskrom bootloader and UART pins:

Скрытый текст

 

 

A working bootloader(supports dualboot) on this hardware for RKDevTool tool just in case:

Loader.zip

 

Скрытый текст

 

Please note that RKDevTool flashing utility only needs to flash the .img file with the bootloader, i.e. you need to unpack the .xz archive somewhere first (for ex. you can use 7-zip).

 

--

 

Recommendations for installation on eMMC

Скрытый текст

It is NOT recommended to install these images using RKDevTool utility on eMMC memory card because ext4 file system is not optimized for eMMC memory lifetime.
It is recommended to install the image on SD-card and boot from it, then configure the system according to your wishes and install it on eMMC using the script "sudo /sbin/nand-sata-install" built into Armbian using the F2FS file system for eMMC - this will extend the life of this memory many times.

 

1. Booting from SD-card and after configuring Armbian you need to install the f2fs-tools dependency:

sudo apt update && sudo apt install f2fs-tools

 

2. Run the script:

sudo /sbin/nand-sata-install

 

 

Alternatively, you can pre-compile an F2FS image for SD-Card and eMMC and immediately burn such an image with RKDevTool.

Just add these parameters during compilation:

./compile.sh ROOTFS_TYPE=f2fs FIXED_IMAGE_SIZE=31744 PACKAGE_LIST_BOARD="f2fs-tools"

(Where you should use a fixed image size for F2FS - here I have chosen 31GB (+ boot partition about 250MB by default) for eMMC 32GB. Keep in mind that the image must fit on the your disk where Armbian is compiled and after installing such image on eMMC you will not be able to change its size on booted TVBox only via external SD-Card OS or etc....
See how big your eMMC is and set your value to -1GB.)

 

----------------------------------------------------

For those who want to build Armbian themselves, here are the instructions:

Скрытый текст

1. Basic instruction https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

2. Before execute "./compile.sh" - copy the contents of the archive "hk1-rbox-r3-profile-kernel-6.1-6.6.zip" into next folders:

build\config\boards\hk1-rbox-r3.tvb
build\packages\blobs\hk1-rbox-r3\rk3566-hk1-rbox-r3.dtb

(where the build folder is our cloned Armbian repository and accordingly a new hk1-rbox-r3 folder should be created on the second path).

 

3. Before compilation, in the file hk1-rbox-r3.tvb we can edit the following:

If we use the BOARDFAMILY variable "media":

BOARDFAMILY="media"

Then when we execute "./compile.sh" and selecting our profile in the expert menu - the kernel 6.1 will build like a building block - and not compiled, it will take about tens of minutes, it will be built from precompiled distributions with the insertion of our dtb profile and only.

 

If we use instead of "media" the BOARDFAMILY variable "rockchip64":

BOARDFAMILY="rockchip64"

Its will already compile kernel 6.6 (on this date of publication) - it will take hours.

 

If you uncomment the variable:

SRC_CMDLINE="earlycon=uart8250,mmio32,0xfe660000"

The UART will display the kernel booting - useful for debugging.

 

 

UPD:
Added to images "f2fs-tools" package, added loader to support dualboot without touching the original Android(or other OS) image on eMMC - priority is given to SD-Card.
Boot will be from SD-Card if there is on boot partition exist folder and file \boot.scr or extlinux\extlinux.conf - uboot(both: original Android and compiled for Armbian) searches for this path and file if it found this file, it will load from device which contains this file. mmc1(SD-Card) - first, mmc0(eMMC) - second.
For correct priority loading it is necessary to replace the main bootloader which is in the archive Loader.zip - if you have an Android it is enough to flash only this bootloader as Loader at 0x0 offset using RKDevTool utility, the rest of the eMMC part should not be touched if the OS and settings we need are there. U-boot on eMMC must be original or Armbian and preinstalled at offset 0x4000.
Instructions:

Скрытый текст

1. Unplug power of TVBox and any SD-card

2. Press the reset(upgrade) button on the box with a paper clip and same time plug USB-A-USB-A(Male-to-Male) to USB 2.0 of TVBox

Then sequentially:

(remember, uboot must be on eMMC (even the original Android or Armbian, i.e. if you erase the eMMC - the boot will not work) and this is relevant if you have installed the original MiniLoaderAll.bin, which does not support booting from SD-Card, but only from eMMC. Some TVBoxes may already have a bootloader that supports SD-card booting.).

 

Feel free to test...

Edited April 23, 2024 by Deoptim
added dualboot images and info about it

[Hqnicolas]

can you post here to?

[Energokom]

On 4/22/2024 at 3:42 PM, Deoptim said:

For correct priority loading it is necessary to replace the main bootloader which is in the archive Loader.zip

Hi.

Can you buid a loader c with rk3566_ddr_1056MHz_v1.21.bin 

https://github.com/rockchip-linux/rkbin/blob/master/bin/rk35/rk3566_ddr_1056MHz_v1.21.bin

or tell me how to do it.

Thanks!

[Hqnicolas]

On 5/4/2024 at 3:17 AM, Energokom said:

Can you buid a loader c with rk3566_ddr_1056MHz_v1.21.bin 

@Energokom to build your DDR_1056mhz 

ADD This lines to the botom of the file Armbian: build/config/board/yourboardname.conf

# Newer blobs. Tested to work with 1056MHz
DDR_BLOB="rk35/rk3566_ddr_1056MHz_v1.18.bin"
BL31_BLOB="rk35/rk3568_bl31_v1.43.elf"         # NOT a typo, bl31 is shared across 68 and 66
ROCKUSB_BLOB="rk35/rk3566_spl_loader_1.14.bin" # For `EXT=rkdevflash` flashing

 

Edited May 16, 2024 by Hqnicolas

[Energokom]

On 5/16/2024 at 5:19 PM, Hqnicolas said:

# Newer blobs. Tested to work with 1056MHz
DDR_BLOB="rk35/rk3566_ddr_1056MHz_v1.18.bin"
BL31_BLOB="rk35/rk3568_bl31_v1.43.elf"         # NOT a typo, bl31 is shared across 68 and 66
ROCKUSB_BLOB="rk35/rk3566_spl_loader_1.14.bin" # For `EXT=rkdevflash` flashing

Unfortunately, it didn't work.

 

I want to build u-boot 2024 (since the old u-boot 2019 is being used now).

 

But it doesn't work out for me. I can't change defconf, since ./compile.sh CREATE_PATCHES="yes", doesn't work now.

I try CREATE_PATCHES (uboot-patch) but I don't get a pause to make changes. I used to use CREATE_PATCHES=yes and everything worked, now I can't build u-boot with my settings. You need more detailed instructions in the description of build options

Edited May 19, 2024 by Energokom

[Hqnicolas]

3 hours ago, Energokom said:

I want to build u-boot 2024 (since the old u-boot 2019 is being used now).

find a board with u-boot 2024 and rebase your board config file

I use OrangePi3B as a base config
 

Quote

# Rockchip RK3566 quad core 4/8GB RAM SoC WIFI/BT eMMC USB2 USB3 NVMe PCIe GbE HDMI SPI
BOARD_NAME="orangepi3b"
BOARDFAMILY="rk35xx"
BOARD_MAINTAINER=""
BOOTCONFIG="orangepi-3b-rk3566_defconfig"
BOOT_SOC="rk3566"
KERNEL_TARGET="legacy,vendor,edge"
FULL_DESKTOP="yes"
BOOT_LOGO="desktop"
BOOT_FDT_FILE="rockchip/rk3566-orangepi-3b.dtb"
IMAGE_PARTITION_TABLE="gpt"
BOOT_SCENARIO="spl-blobs"
BOOT_SUPPORT_SPI="yes"
BOOT_SPI_RKSPI_LOADER="yes"
MODULES="sprdbt_tty sprdwl_ng"
MODULES_BLACKLIST_LEGACY="bcmdhd"

 

# Newer blobs. Tested to work with opi3b
DDR_BLOB="rk35/rk3566_ddr_1056MHz_v1.18.bin"
BL31_BLOB="rk35/rk3568_bl31_v1.43.elf"         # NOT a typo, bl31 is shared across 68 and 66
ROCKUSB_BLOB="rk35/rk3566_spl_loader_1.14.bin" # For `EXT=rkdevflash` flashing

 

# Override family config for this board; let's avoid conditionals in family config.
function post_family_config__orangepi3b_use_mainline_uboot() {
    display_alert "$BOARD" "mainline (Kwiboo's tree) u-boot overrides" "info"

    BOOTSOURCE="https://github.com/Kwiboo/u-boot-rockchip.git"
    BOOTBRANCH="branch:rk3xxx-2024.04" # specific commit tested is commit:ccef7dfc453bc03c5b5c61fa67d2745b96fa7da6
    BOOTPATCHDIR="v2024.04-orangepi3b" # empty, patches are already in Kwiboo's branch:rk3xxx-2024.04

    BOOTDIR="u-boot-${BOARD}" # do not share u-boot directory

    BOOTDELAY=1 # Wait for UART interrupt to enter UMS/RockUSB mode etc
    UBOOT_TARGET_MAP="BL31=${RKBIN_DIR}/${BL31_BLOB} ROCKCHIP_TPL=${RKBIN_DIR}/${DDR_BLOB};;u-boot-rockchip.bin u-boot-rockchip-spi.bin u-boot.itb idbloader.img idbloader-spi.img"
    unset uboot_custom_postprocess write_uboot_platform write_uboot_platform_mtd # disable stuff from rockchip64_common; we're using binman here which does all the work already

    # Just use the binman-provided u-boot-rockchip.bin, which is ready-to-go
    function write_uboot_platform() {
        dd if=${1}/u-boot-rockchip.bin of=${2} bs=32k seek=1 conv=fsync
    }

    # Smarter/faster/better to-spi writer using flashcp (hopefully with --partition), using the binman-provided 'u-boot-rockchip-spi.bin'
    function write_uboot_platform_mtd() {
        declare -a extra_opts_flashcp=("--verbose")
        if flashcp -h | grep -q -e '--partition'; then
            echo "Confirmed flashcp supports --partition -- read and write only changed blocks." >&2
            extra_opts_flashcp+=("--partition")
        else
            echo "flashcp does not support --partition, will write full SPI flash blocks." >&2
        fi
        flashcp "${extra_opts_flashcp[@]}" "${1}/u-boot-rockchip-spi.bin" /dev/mtd0
    }

}

function post_family_tweaks_bsp__orangepi3b() {
    display_alert "$BOARD" "Installing sprd-bluetooth.service" "info"

    # Bluetooth on orangepi3b board is handled by a Spreadtrum (sprd) chip and requires
    # a custom hciattach_opi binary, plus a systemd service to run it at boot time
    install -m 755 $SRC/packages/bsp/rk3399/hciattach_opi $destination/usr/bin
    cp $SRC/packages/bsp/rk3399/sprd-bluetooth.service $destination/lib/systemd/system/

    return 0
}

function post_family_tweaks__orangepi3b_enable_services() {
    display_alert "$BOARD" "Enabling sprd-bluetooth.service" "info"
    chroot_sdcard systemctl enable sprd-bluetooth.service
    return 0
}
 

 

[Home Preka]

Hello,

All your link are dead 😔 

[Home Preka]

Hello,

I want to try to install it on vontar kkmax, please someone Can share Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_minimal.img.xz file ? Link seems to be dead on mediafire.

Many thanks

[Energokom]

Hello

Vontar kkmax has RAM memory SK Hynix h5anag8najr-wmc - 4 pcs. DDR4-2933.

 

Which DDR_BLOB= and BL31_BLOB= should I choose for this memory?

 

Help me determine the correct size of 8GB

Edited July 26, 2025 by Energokom

[Energokom]

On 4/22/2024 at 3:42 PM, Deoptim said:

(remember, uboot must be on eMMC (even the original Android or Armbian, i.e. if you erase the eMMC - the boot will not work) and this is relevant if you have installed the original MiniLoaderAll.bin, which does not support booting from SD-Card, but only from eMMC. Some TVBoxes may already have a bootloader that supports SD-card booting.).

@Deoptimhow to build the current u-boot ? and how build MiniLoaderAll.bin?
On the board, the 4 chips SK Hynix h5anag8najr-wmc  is only detected as 4GB, but it should be 8GB

DDR Version V1.08 20210520
ln
ddrconfig:3
DDR4, 324MHz
BW=32 Col=10 Bk=4 BG=4 CS0 Row=16 CS=1 Die BW=8 Size=4096MB
wrlvl:clk skew:0x80,0x80

 

Edited November 4, 2025 by Energokom

[Energokom]

On 4/22/2024 at 3:42 PM, Deoptim said:

(remember, uboot must be on eMMC (even the original Android or Armbian, i.e. if you erase the eMMC - the boot will not work) and this is relevant if you have installed the original MiniLoaderAll.bin, which does not support booting from SD-Card, but only from eMMC. Some TVBoxes may already have a bootloader that supports SD-card booting.).

@Deoptimhow to build the current u-boot ? and how build MiniLoaderAll.bin?

Edited November 4, 2025 by Energokom
delete

[Hqnicolas]

On 11/4/2025 at 8:09 PM, Energokom said:

the 4 chips SK Hynix h5anag8najr-wmc  is only detected as 4GB, but it should be 8GB

Welcome to TV-Box section, that's the real size of your RAM: 4gb

 

On 11/4/2025 at 8:09 PM, Energokom said:

how to build the current u-boot ? and how build MiniLoaderAll.bin?

https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/rkbin
 

[Energokom]

7 hours ago, Hqnicolas said:

the real size of your RAM: 4gb

 

How did you determine this without holding the board in your hands? Without connecting the uart?

 

The chips are located on both sides of the board. Assuming that h5anag8najr-wmc is a fake label and that the chip is 1Gbx8, the u-boot output on the uart should be Row=17 CS=2, not ROW=16 CS=1. Or am I wrong?

If the board allows you to work with two ranks and the CS-1, A14, and A16 are present (on the board), then u-boot should display ROW=17, CS=2 Size=4096MB.  BUT, the bootloader does not recognize the 2nd memory rank.

 

https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/rkbin - It is not possible to build rk356x_spl_loader_v1.xxx.bin, also known as the miniloader, using this link. There is no tools directory in this section.

 

 

I managed to figure out how to assemble rk356x_spl_loader_v1.xxx.bin using different (rk3566_ddr_528MHz_ultra_v1.10, rk3566_ddr_780MHz_ultra_v1.10, rk3566_ddr_920MHz_ultra_v1.10, rk3566_ddr_1056MHz_ultra_v1.20, as well as rk3566_ddr_920MHz_v1.23, rk3566_ddr_1056MHz_v1.23.)

I also managed to build u-boot - I'll have time to test it all.

It's a pity that few people share information.

 

P.S. If you look at https://github.com/hqnicolas/Rockchip-Library/blob/main/RK356x/u-boot/socfpga/rk3568_common.h, you'll see #define SDRAM_MAX_SIZE 0xf0000000, which limits the size to 4GB. Therefore, it is possible that u-boot is built with a 4GB SDRAM limit. However, I also assume that the memory could have been tampered with. I would benefit from obtaining U-boot's UART output from those with NT5AD1024M8A3 memory. Currently, I am considering three options.
1. U-boot is built with SDRAM_MAX_SIZE 0xf0000000 limitation

2. rk3566_ddr_xxxMHz_v1.xxx.bin - does not recognize the 2nd rank (2R) of Hynix h5anag8najr-wmc memory

3. Memory labeling is still fake

Edited November 7, 2025 by Energokom

[Hqnicolas]

2 hours ago, Energokom said:

How did you determine this without holding the board in your hands? Without connecting the uart?

 

I came from 4pda to armbian and I came from there already being a prejudiced person.

this is just another normal day in the TV box section. Many other users have already encountered similar problems with Chinese boxes.
 

2 hours ago, Energokom said:

Memory labeling is still fake

 

you can solder a better module like @Deoptim
 

 

[Deoptim]

 

13 часов назад, Hqnicolas сказал:

you can solder a better module like @Deoptim

Continuing the story.
Or 4pda (Russian).

[kang_001]

Hello, the link you shared has expired. Could you please re-analyze it

[Deoptim]

Here are the modified latest official Armbian-supported images for Radxa Zero 3W/3E. Everything works for me, including hardware-accelerated YouTube playback in Chromium (however, with a caveat):
Armbian_26.2.1_hk1-rbox-r3_trixie_vendor_6.1.115_minimal.img.xz

Armbian_26.2.1_hk1-rbox-r3_noble_vendor_6.1.115_gnome_desktop.img.xz

MD5:

28654e87a39ac3e0b2bec4ce4211f5ca *Armbian_26.2.1_hk1-rbox-r3_noble_vendor_6.1.115_gnome_desktop.img.xz
ce74829c43c6d27b02bdf314580c4dc4 *Armbian_26.2.1_hk1-rbox-r3_trixie_vendor_6.1.115_minimal.img.xz

 

What you MUST do after installing Armbian:
Freeze auto-updates for the bootloader and DTB (kernel updates are OK, except for these two packages since we use a different bootloader, not for Radxa Zero 3):

sudo apt-mark hold linux-u-boot-radxa-zero3-vendor linux-dtb-vendor-rk35xx

 

Install dependencies for hardware-accelerated playback Youtube in Chromium:

sudo apt update
sudo apt install chromium-codecs-ffmpeg-extra ffmpeg

 

In Chromium, install the enhanced-h264ify extension. Then, in the extension's options, leave only AV1 disabled (i.e., enable VP8 and VP9).

 

Screenshots:

Скрытый текст

 

 

 

 

 

Instructions on how to modify any Armbian image yourself:

Скрытый текст

Inserting the DTB file

1. You need a Linux machine or WSL (in Windows) - I used WSL.

2 Download the archive hk1-rbox-r3-bootloaders.zip

3. Install the util-linux package in Linux/WSL.

4. Download the image you want to modify (e.g., with .img.xz extension).

5. Decompress the img.xz (Linux: unxz name.img.xz, Windows: use 7zip).

6. Mount the decompressed image using losetup:

sudo losetup -f -P /mnt/c/Users/Dima/Downloads/Armbian_26.2.1_Radxa-zero3_noble_vendor_6.1.115_gnome_desktop.img

Mount /dev/loop0p1 to the /mnt/ext folder:

sudo mkdir /mnt/ext
sudo mount /dev/loop0p1 /mnt/ext/

Edit the file /mnt/ext/boot/armbianEnv.txt:

Цитата

           fdtfile=rockchip/rk3566-hk1-rbox-r3.dtb

Copy our rk3566-hk1-rbox-r3.dtb to /mnt/ext/boot/dtb-6.1.115-vendor-rk35xx/rockchip/.

Additionally, I changed the hostname display by editing:

/mnt/ext/etc/hostname

/mnt/ext/etc/hosts (find all instances of radxa-zero-3 and replace with hk1-rbox-r3).

7. Unmount /mnt/ext/:

sudo umount /mnt/ext/

8. Detach the image:

sudo losetup -D

Replacing the bootloader

In the same .img, replace the bootloader by executing these commands sequentially:

sudo dd bs=1k seek=32 conv=notrunc if=./idbloader-ff.img of=/mnt/c/Users/Dima/Downloads/Armbian_26.2.1_Radxa-zero3_noble_vendor_6.1.115_gnome_desktop.img
sudo dd bs=1k seek=32 conv=notrunc if=./idbloader.img of=/mnt/c/Users/Dima/Downloads/Armbian_26.2.1_Radxa-zero3_noble_vendor_6.1.115_gnome_desktop.img
sudo dd bs=1k seek=8192 conv=notrunc if=./uboot-zero.bin of=/mnt/c/Users/Dima/Downloads/Armbian_26.2.1_Radxa-zero3_noble_vendor_6.1.115_gnome_desktop.img
sudo dd bs=1k seek=8192 conv=notrunc if=./u-boot.itb of=/mnt/c/Users/Dima/Downloads/Armbian_26.2.1_Radxa-zero3_noble_vendor_6.1.115_gnome_desktop.img

(Replace paths to files from the archive and the image path as needed)

 

Source: 4PDA

Edited February 27 by Deoptim

[Deoptim]

Continuing to dig into this. Updated the Armbian images - available via the same links above (md5sum mismatch):

Цитата

1. Added a modified rewritten kernel module for ws2801 (fd6513 chip) to control the RGB LED on the box.

By default, the Red LED blinks using the "heartbeat" trigger (specified in the dts, or you can change the trigger via a dts-overlay or via /sys/class/leds (in Armbian it remembers the changes made in sys)).

The following colors are available there: Red, Green, Blue, White, Yellow - you can specify a color mix with your own mask.

2. Updated the bootloader to the latest 2025.10_armbian-2025.10-Se50b-P0727-He37c-V59e8-B2eb2-R448a.

3. Added "performance" optimization for the CPU and peripherals in rc.local, as well as disabled powersave for Wi-Fi (since there is a visible wake-up delay when working with this box via ssh, for example).

 

How to add the module to an already working system (so you don't have to reinstall from scratch):

1. Download the archive ws2801-1.0.tar.gz with the dkms source code for the ws2801 module.

2. Extract the source folder to /usr/src/ :

sudo tar -xzvf ~/ws2801-1.0.tar.gz -C /usr/src/

(here ~/ is the /home directory of my user)

3. Install the module step-by-step via dkms:

sudo dkms add ws2801/1.0
sudo dkms build ws2801/1.0
sudo dkms install ws2801/1.0

4. To avoid rebooting, you can load the module immediately:

sudo modprobe ws2801

 

By default, Red should start blinking as a "heartbeat" trigger.

 

Description of dts and demo:

Скрытый текст

The main control segment for the ws2801 module (modded for fd6513) in the dts consists of this node:

	led-stripe {
		compatible = "fd6513";
		clk-gpios = <&gpio0 RK_PC5 GPIO_ACTIVE_HIGH>;
		data-gpios = <&gpio0 RK_PC3 GPIO_ACTIVE_HIGH>;
		num-leds = <1>;
		auto-commit;
		status = "okay";

    	led-config-red {
    	    label = "red";
    	    led-num = <0>;
    	    color-on = <255 0 0>;
    	    trigger = "heartbeat";
    	};
    	
    	led-config-green {
    	    label = "green";
    	    led-num = <0>;
    	    color-on = <0 0 255>;
    	    trigger = "none";
    	};
    	
    	led-config-blue {
    	    label = "blue";
    	    led-num = <0>;
    	    color-on = <0 255 0>;
    	    trigger = "none";
    	};

    	led-config-white {
    	    label = "white";
    	    led-num = <0>;
    	    color-on = <255 255 255>;
    	    trigger = "none";
    	};

    	led-config-yellow {
    	    label = "yellow";
    	    led-num = <0>;
    	    color-on = <255 0 255>;
    	    trigger = "none";
    	};
	};

 

As you can understand, you can mix colors and so on, also this node can be replaced via a dts overlay so you don't have to replace the entire main dtb.

 

Just like in the original ws2801, demos are available for RGB (smooth color changing like an RGB LED) and CPU (blue - CPU is idle / mix with yellow (medium load) / mix with red (maximum load)).

These demos are available at the following path:

deoptim@hk1-rbox-r3:/$ ls /usr/src/ws2801-1.0/demos/
common.c  common.o  cpu-load.c  rgb-demo    ws2801-demo    ws2801.h
common.h  cpu-load  Makefile    rgb-demo.c  ws2801-demo.c
deoptim@hk1-rbox-r3:/$

For the demo to work properly, we need to turn off all indicators (by default, Red is blinking); to do this, run the following command in the console:

echo none | sudo tee /sys/class/leds/led-stripe\:red/trigger

Then run, for example:

sudo /usr/src/ws2801-1.0/demos/cpu-load -n 10 -k led-stripe

(where led-stripe is the name of the node in the dts)

 

The color will change according to the CPU load.