guenter

I bought this board because it has 2 lanes. So I changed the number of lanes in the dtb from 1 to 2. I need confirmation of an expert but my quick speed test with 2 lanes looks promising : gt@yy3568:~$ sudo hdparm -tT --direct /dev/nvme0n1p1 /dev/nvme0n1p1: Timing O_DIRECT cached reads: 1062 MB in 2.00 seconds = 530.34 MB/sec Timing O_DIRECT disk reads: 928 MB in 3.00 seconds = 308.97 MB/sec gt@yy3568:~$ sudo dmesg | grep lane [ 4.183004] phy phy-fe8c0000.phy.6: lane number 0, val 1 [ 4.183679] phy phy-fe8c0000.phy.6: lane number 1, val 2 pcie@fe280000 { compatible = "rockchip,rk3568-pcie"; #address-cells = <0x03>; #size-cells = <0x02>; bus-range = <0x20 0x2f>; clocks = <0x0f 0x8f 0x0f 0x90 0x0f 0x91 0x0f 0x92 0x0f 0x93>; clock-names = "aclk_mst\0aclk_slv\0aclk_dbi\0pclk\0aux"; device_type = "pci"; interrupts = <0x00 0xa5 0x04 0x00 0xa4 0x04 0x00 0xa3 0x04 0x00 0xa2 0x04 0x00 0xa1 0x04>; interrupt-names = "sys\0pmc\0msg\0legacy\0err"; #interrupt-cells = <0x01>; interrupt-map-mask = <0x00 0x00 0x00 0x07>; interrupt-map = <0x00 0x00 0x00 0x01 0xcb 0x00 0x00 0x00 0x00 0x02 0xcb 0x01 0x00 0x00 0x00 0x03 0xcb 0x02 0x00 0x00 0x00 0x04 0xcb 0x03>; linux,pci-domain = <0x02>; num-ib-windows = <0x06>; num-ob-windows = <0x02>; max-link-speed = <0x03>; msi-map = <0x2000 0x66 0x2000 0x1000>; num-lanes = <0x02>; phys = <0xca>; phy-names = "pcie-phy"; power-domains = <0x11 0x0f>; reg = <0x03 0xc0800000 0x00 0x400000 0x00 0xfe280000 0x00 0x10000 0x00 0xf0000000 0x00 0x100000>; ranges = <0x1000000 0x00 0xf0100000 0x00 0xf0100000 0x00 0x100000 0x2000000 0x00 0xf0200000 0x00 0xf0200000 0x00 0x1e00000 0x3000000 0x03 0x80000000 0x03 0x80000000 0x00 0x40000000>; reg-names = "dbi\0apb\0config"; resets = <0x0f 0xc1>; reset-names = "pipe"; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <0xcc>; reset-gpios = <0x58 0x1e 0x00>; vpcie3v3-supply = <0xcd>; phandle = <0x271>; legacy-interrupt-controller { interrupt-controller; #address-cells = <0x00>; #interrupt-cells = <0x01>; interrupt-parent = <0x01>; interrupts = <0x00 0xa2 0x01>; phandle = <0xcb>; }; };

After much trouble with my old build environment I cloned Hqnicolas build repo. Now I can confirm that it seems to work. I made a quick speed comparison between the ssd and my external USB drive: gt@yy3568:~$ sudo hdparm -tT --direct /dev/sda /dev/sda: Timing O_DIRECT cached reads: 178 MB in 2.00 seconds = 88.89 MB/sec Timing O_DIRECT disk reads: 322 MB in 3.01 seconds = 106.88 MB/sec gt@yy3568:~$ sudo hdparm -tT --direct /dev/nvme0n1p1 /dev/nvme0n1p1: Timing O_DIRECT cached reads: 1160 MB in 2.00 seconds = 579.44 MB/sec Timing O_DIRECT disk reads: 690 MB in 3.00 seconds = 229.89 MB/sec Thank you very much to both @Arthur Gu and @Hqnicolas

@Arthur Gu Thank you for the effort and congratulations for your success. I will try it in the next days.

@Hqnicolas I'm a bit late because I have overlooked your request for testing. Now I can confirm that the AuxDisplay works correctly with my H96_tvbox_3566 (with AIC 8800 wlan chip). Thank you for your effort.

@Hqnicolas I tried https://github.com/armbian/build/tree/v25.11.0-trunk.258 but the display didn't work on my h96-max-v56 board with aic8800. This board may have same differences with the auxdisplay compared with older boards. When I add my 'old' tm16xx.dtbo the display works again. My source for this overlay is attached. It contains 2 lines which are necessary with my board: i2c-gpio,sda-output-only; /* despite kernel warnings, those two directives are necessary! */ i2c-gpio,scl-output-only; I didn't find the advertised kernel message, so the comment above my be deprecated. For my board it is required but not sufficient to add the 2 lines above. The mapping of the LED segments seems to be different from yours. The line i2c-gpio,delay-us = <3>; from the original code was not required with my board. And thank you very much for your work! rk3566-h96-max-v56-gt.dtso

@GBEM I'm running: _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.8.1 for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Support: DIY (community maintained) IPv4: SNIPP Performance: Load: 2% Uptime: 8 days 8:01 Memory usage: 3% of 7.50G CPU temp: 38°C Usage of /: 12% of 57G Commands: Configuration : armbian-config Monitoring : htop Last login: Mon Sep 15 15:59:34 2025 from 192.168.1.48 I can switch the blue leds with: root@tvbox:/home/gt# echo 0 >/sys/class/leds/led-power/brightness root@tvbox:/home/gt# echo 1 >/sys/class/leds/led-power/brightness as root. sudo didn't work. I used the project: gt@tvbox:~/tm16xx-display$ git config --get remote.origin.url https://github.com/jefflessard/tm16xx-display.git I created a dtbo which is loaded during boot: gt@tvbox:~/tm16xx-display$ cat /boot/armbianEnv.txt ...... user_overlays=tm16xx ..... The mentioned project provides a service which updates the front display with the time.

I never used RKDevTool because I'm on Linux. I understand the instructions as follows: Download RKDevTool, Wipe_part and Clear_EMMC_yy3568.zip from the links in the original post. The zip contains the config for RKDevTool from Nicolas. The included file path will not work on your system. You have to adjust these that uboot.img, miniloader.bin and parameter.txt from the Clear_EMMC_yy3568 are used and the separately downloaded wipe_part. I assume that at the next boot some partitions on EMMC are cleared and in consequence booting from SDcard is activated.

No problem. Good luck with the exams. And thank you for the interesting link. I remember there was a hype about fuzzy logic, when I was young and in college😀.

It was already mentioned that bluetooth is not working on boxes with AIC8800D40. Maybe is the bug describe here: https://github.com/radxa-pkg/aic8800/issues/14 responsible for that.

Hello Hqnicolas, thank you very much for the effort you made with the yy3568. I have a nvme SSD connected to .m2 and this works with the youyeetoo kernel "Linux yy3568 4.19.232 #8 SMP Wed Aug 7 10:48:37 CEST 2024 aarch64 GNU/Linux". I tried your Armbian plus the attached patch but the SSD doesn't work. See attached screenlog.0 [ 2.512779] pci 0000:00:00.0: ROM [mem 0xf4200000-0xf420ffff pref]: assigned [ 2.512806] pci 0000:00:00.0: PCI bridge to [bus 01-ff] [ 2.512830] pci_bus 0000:00: resource 4 [io 0x0000-0xfffff] [ 2.512844] pci_bus 0000:00: resource 5 [mem 0xf4200000-0xf5ffffff] [ 2.512857] pci_bus 0000:00: resource 6 [mem 0x300000000-0x33fffffff] [ 2.516131] pcieport 0000:00:00.0: PME: Signaling with IRQ 73 [ 2.516722] pcieport 0000:00:00.0: AER: enabled with IRQ 73 [ 2.518475] phy phy-fe8c0000.phy.2: lane number 0, val 1 [ 2.518506] phy phy-fe8c0000.phy.2: lane number 1, val 2 [ 2.518519] phy phy-fe8c0000.phy.2: bifurcation enabled [ 2.519039] phy phy-fe8c0000.phy.2: rockchip_p3phy_rk3568_init: lock failed 0x6890000, check input refclk and power supply [ 2.519059] phy phy-fe8c0000.phy.2: phy init failed --> -110 [ 2.519102] rockchip-dw-pcie 3c0800000.pcie: probe with driver rockchip-dw-pcie failed with error -110 [ 2.520137] mmc0: new HS200 MMC card at address 0001 [ 2.525326] mmcblk0: mmc0:0001 ISOCOM 57.6 GiB [ 2.529794] rockchip-usb2phy fe8a0000.usb2phy: Requested PHY is disabled [ 2.531377] rockchip-usb2phy fe8a0000.usb2phy: Requested PHY is disabled [ 2.531408] rockchip-usb2phy fe8a0000.usb2phy: Requested PHY is disabled At least is PCI bridge found: root@yy3568:~# lspci -v 00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 73 Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: [disabled] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Expansion ROM at f4200000 [virtual] [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Capabilities: [70] Express Root Port (Slot-), MSI 00 Capabilities: [b0] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [148] Secondary PCI Express Capabilities: [160] L1 PM Substates Capabilities: [170] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Kernel driver in use: pcieport It would be great if you find some time to find a solution. Kind Regards, Guenter kernel-rockchip64-edge.patch screenlog.0