GmP
-
Posts
20 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by GmP
-
-
@jock Hi, I have updated the build source for the leds overlay files (leds 6 and 7) for both the the rockchip64 H50 tvbox and the T9 tvbox, for kernels 6.12 (old non scrolling driver) and 6.18 (new scrolling driver) the version for 6.18 is also fine for 6.19.
Have a look at my fork in https://github.com/gpaesano/build.
Some modifications are just refinements other are functional.
I have built all the images and variants on a ubuntu linux and are running well.
I am not familiar with pull requests and do not want to be impolite, so If you think there is some added value please support it.
All the best
@GmP
-
this is the latest console build compatible with T9. You will need to configure a little bit the environment after booting to enable all the features via ssh and wired lan.
If the device is still on android the best is to follow the tutorial from @jock in
-
First of all, thank you to @Hqnicolas and all the members for this great effort.
Just bought an H96 rk3566, having this hardware configuration:
BOARD LABEL: HCY-RK3566-1X32-V20 2023-01-13
SOC RK3566
PMIC RK809-5
LAN RTL8211F
DISPLAY FD6551
WIFI AIC8800D40
eMMC H26M74002HMR - SK Hynix eMMC 5.1 NAND Flash 64Gb.It seems to be a mix of the other versions described in this topic, although very close to the one of @WINEDS (thanks for the hints).
Everything seems to work so far.
Installed using rockchip dev tools, as advised.
here its:
_ _ _ _ _
/_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _
/ _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || |
/_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, |
|___| |__/
v26.2 rolling for h96-tvbox-3566 running Armbian Linux 6.12.61-current-rockchip64Packages: Debian stable (trixie)
Support: for advanced users (rolling release)
IPv4: (LAN) 192.168.111.228, 192.168.111.91 (WAN) xxxxxxxxxxx
Containers: big-bear-photoprism-dbPerformance:
Load: 8% Uptime: 46 minutes
Memory usage: 6% of 7.50G
CPU temp: 38°C Usage of /: 31% of 57GTo enable Bluetooth I have used this small overlay in /boot/overlay-user/ (which enables SPDIF as well):
/dts-v1/; /plugin/; /* &{/serial@fe650000} */ &uart1 { status = "okay"; dma-names = "tx\0rx"; bluetooth { status = "disabled"; }; }; &spdif { clock-names = "mclk\0hclk"; status="okay"; };The followings are the drivers used for wifi-bluetooth
wget https://github.com/radxa-pkg/aic8800/releases/download/4.0%2Bgit20250410.b99ca8b6-3/aic8800-firmware_4.0+git20250410.b99ca8b6-3_all.deb wget https://github.com/radxa-pkg/aic8800/releases/download/4.0%2Bgit20250410.b99ca8b6-3/aic8800-sdio-dkms_4.0+git20250410.b99ca8b6-3_all.deb dpkg -i aic8800-firmware_4.0+git20250410.b99ca8b6-3_all.deb dpkg -i aic8800-sdio-dkms_4.0+git20250410.b99ca8b6-3_all.debService to enable bluetooth :
[Unit] Description=Bluetooth HCI Attach (AIC8800) After=systemd-modules-load.service Requires=systemd-modules-load.service After=dev-ttyS1.device Requires=dev-ttyS1.device [Service] Type=oneshot # Load AIC module ExecStartPre=/sbin/modprobe aic8800_btlpm_sdio # Just a small delay ExecStartPre=/bin/sleep 2 # Attach HCI ExecStart=/usr/bin/hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleepTo re-enable display in Linux 6.12 another small overlay is required: (the display itself it is not scrolling and available at: /sys/class/leds/display/value )
/dts-v1/; /plugin/; &{/i2c-aux-display} { compatible = "i2c-gpio"; #address-cells = <0x01>; #size-cells = <0x00>; display@24 { compatible = "fdhisi,fd6551"; reg = <0x24>; #address-cells = <0x01>; #size-cells = <0x00>; tm16xx,digits = [04 03 02 01]; tm16xx,segment-mapping = [00 01 02 03 04 05 06]; led@0,0 { reg = <0x00 0x00>; function = "alarm"; }; led@0,1 { reg = <0x00 0x01>; function = "usb"; linux,default-trigger = "usb-host"; }; led@0,2 { reg = <0x00 0x02>; function = "pause"; linux,default-trigger = "mmc2"; }; led@0,3 { reg = <0x00 0x03>; function = "play"; linux,default-trigger = "mmc0"; }; led@0,4 { reg = <0x00 0x04>; function = "colon"; }; led@0,5 { reg = <0x00 0x05>; function = "lan"; linux,default-trigger = "stmmac-0:00:link"; }; led@0,6 { reg = <0x00 0x06>; function = "wlan"; linux,default-trigger = "mmc1"; }; digits { status = "disabled"; }; leds { status = "disabled"; }; }; }; -
@jock this is the user-overlay patch I am using to enable both leds on the board. The "working" led is as usual a couple of alternating leds of red/blue. The led-ir is a standalone blue, I have triggered one to the "timer" and the other to "activity" , both running.
I can confirm bluetooth, IR remote receiver are also working. Bluetooth needs BCM.hd (I have used BCM43342.hcd).
For the wifi 2/5G the correct overlay is rk3318-box-wlan-ap6334.
HDMI, despite apparently is initialized correctly and answering to all commands still gives a black screen.
-
TV Box Status Information Template Version 1.0
TV Box Name (example: TX3 mini): T9
CPU (example: amlogic s905w): RK3328
Armbian build file name: Armbian_community_25.11.0-trunk.367_Rk3318-box_trixie_current_6.12.54_minimal.img
DTB file used: rockchip/rk3318-box.dtb
Kernel Version: 6.12.56-current-rockchip64
Distribution Installed (focal, buster, etc): trixie
Working Ethernet (Yes/No):Yes
Max Ethernet Speed that works (100/1000): 100 Max
Does wifi work (Yes/No): Yes 2/5
Does bluetooth work (Yes/No): Yes
Does HDMI audio work (Yes/No): Yes - after last update , (also analog and spdif ports are available - not tested).
Additional Comments (provide any additional information you feel is important): IR Receiver yes
5 Digit display working: yes
MASKROM PINS for recovery flashing available on the back side.
SOC RK3328
RAM 4Gx4 D9PQL
VFD DRIVER FD6551
WLAN CHIP SP6330
32 GB EMMc KLMBG2JENB
VT RT9045
-
Update I have opened the box. Indeed the driver is an FD6551 and the SOC is RK3328. I was using the FD655 just because that was the one used in a working vfd-openvfd conf file.
So I have just changed the dtso file directive compatible = "fdhisi,fd6551";
The advantage is that 8 levels of intensity are now available using 1..8 in "echo 1 > /sys/class/leds/display/brightness".
I did not chage the filename but as a matter of fact it should be as well the working rk3328-t9.dtso.
-
Quote
Posted yesterday at 06:32 PM
Hi @GmP, thanks for your detailed feedback.
I think your previous permission denied issue was because you were using an older version of the driver with the current version of the display-service. Since you have reviewed the DT, I understand that you are now using the current driver version and that display-service is now working properly.
Latest driver version now use line-display library (expected upstreaming requirements), therefore there is no more sysfs value attribute. This has been replaced with the line-display message attribute.
Both senteces are correct , I have reviewed the DT and now display-service is working properly and consequently there is no more sysfs "value" attribute. "Message" attribute is working as expected (scrolling, etc).
Notes: It seems to me that the automatically generated dtso file for rk3328-t9 in the git repository is not valid.
There are a lot of "T9" TVBOXES all around, mine is labelled T9-RK3328-8x4-V1.8 , (although I have always used it as an rk3318-t9 due to the main dtb file), so I will reopen it one of these day and be back.
Anyway the latest driver is working as well with another box, another chip (FD650), please see:
-
the two tv box are quite different.The rk3318-H50 of this post is quite cheap, so are the component inside. By the way for the rk3318-H50:
the PMIC is a DF1517, not an usual one.
The Board has three leds (one red is power on always on the other two are both blu but I have never seen them on) and a 4 digit display plus (colon) usb, lan and wlan icons.
Wifi works with the base configuration 2 and 5 ghz (although some warnings in the log).
Bluetooth is recognized as well.
I do not see any message related to the IR receiver.
By the way it seems to be quite stable.
This is the gpio list:
android_tv_box_32:/ $ cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-31, parent: platform/pinctrl, gpio0:
gpio-2 ( |vcc_otg_vbus ) out hi
gpio-30 ( |vcc_sd ) out higpiochip1: GPIOs 32-63, parent: platform/pinctrl, gpio1:
gpio-42 ( |bt_default_rts ) out lo
gpio-50 ( |reset ) out hi
gpio-53 ( |bt_default_poweron ) out hi
gpio-56 ( |fd650_scl ) out hi
gpio-57 ( |fd650_sda ) out hi
gpio-58 ( |bt_default_wake_host) in higpiochip2: GPIOs 64-95, parent: platform/pinctrl, gpio2:
gpio-81 ( |vcc_host_vbus ) out hi
gpio-82 ( |power-led-ir ) out lo
gpio-90 ( |power-led-normal ) out logpiochip3: GPIOs 96-127, parent: platform/pinctrl, gpio3:
The T9 is an old and quite different TVBOX (cames in two flavours rk3318 and rk3328 from Sunwell) and everything is working "out of the box" - wifi, bluetooh, lan, hdmi, ir receiver. It has no leds but a 5 digit display + 6 icons but if you think it would be useful I can open it and peraphs describe it in a different post to avoid confusion. It seems to me that is more widespread as there are configuration files all around. Let me know if it is of ant interest.
-
@jock, sorry for the confusion actually there are two boards (two different TV-BOX) one (here in this post) is an rk3318-H50 as you say T98... using FD650, the other one is rk3318-T9 (only T9) using FD655. All the dtso files posted are correct: for the H50 (T98) in this post you have the versions for the old kernel and the new one. Same in the other post "HELP WANTED" for the other TV BOX. At the end the two latest dtso are valid for the latest kernel. One of the difference between FD650 and FD655 is that the first one has 4 digits but 8 segments (0-7) on the contrary FD655 drives 5 digits and 7 segments (0..6). DTSO files are configured accordingly and fully working. Hope it clarifies.
-
-
Here you are the correct dtso for the latest version of the tm16xx / kernel. Note that this is not the same model of rk3328-t9.dtso found in https://github.com/jefflessard/tm16xx-display however I do think it will work with that model as well. The automatic generated dtso file for the rk3328 from vfd seems to be icorrect as it is addressing segment 7 of fd655.
-
Yes you are perfectly right. It took me some "minutes" to figure out. Just in case I do have the overlay dtso for the previous tm16xx version. No scrolling message however. Use ../value instead.
-
Attached the source overlay file for the tm16xx driver. All features working. See for details and thanks to https://github.com/jefflessard .
-
Hi - thank you for the nice driver. Here is my contrbute:
Device under test : T9_RK3318 (T9 Sunwell 3318 version 4+32 GB)
Running:
v25.11 rolling for RK3318 Box running Armbian Linux 6.12.55-current-rockchip64Packages: Debian stable (trixie)
Support: for advanced users (rolling release)Some info:
RK3318:~# lsmod | grep tm
tm16xx 28672 0
stmmac_platform 20480 1 dwmac_rk
stmmac 241664 3 stmmac_platform,dwmac_rk
pcs_xpcs 28672 1 stmmaclsmod | grep i2c
i2c_gpio 16384 0
i2c_algo_bit 12288 1 i2c_gpiols /sys/bus/i2c/devices/
5-0024 i2c-4 i2c-5ls /sys/class/leds/display
brightness device digits map_seg7 max_brightness num_digits num_segments power segments subsystem trigger uevent valuels -l /sys/class/leds/
total 0
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::alarm -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::alarm
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::colon -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::colon
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::lan -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::lan
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::pause -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::pause
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::play -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::play
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::usb -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::usb
lrwxrwxrwx 1 root root 0 Oct 26 11:53 display::wlan -> ../../devices/platform/i2c-display/i2c-5/5-0024/leds/display::wlan
lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::capslock -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::capslock
lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::compose -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::compose
lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::kana -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::kana
lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::numlock -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::numlock
lrwxrwxrwx 1 root root 0 Jan 1 1970 input3::scrolllock -> ../../devices/platform/ff600000.usb/xhci-hcd.0.auto/usb2/2-1/2-1:1.1/0003:248A:8208.0002/input/input3/input3::scrolllock
lrwxrwxrwx 1 root root 0 Jan 1 1970 working -> ../../devices/platform/gpio-leds/leds/working
Testing...
echo "1234" > /sys/class/leds/display/value
echo 1 > /sys/class/leds/display\:\:lan/brightness
echo 1 > /sys/class/leds/display\:\:usb/brightness
All the 7 functions and 4 digits are working and correctly associated.
Also trigges are working.
I still have this small bug which is stopping rolling messages:
display-service -c [INFO] all digits and leds on
/usr/sbin/display-service: 116: cannot create /sys/class/leds/display/message: Permission denied
All the function leds reacts well (all on) but the four clock digits do not switch, most likey because of the message permission denied. However they do work writing directly in the "value" as above and in the picture.
Edit: I have investigated a little and it seems that I am still using the tm16xx which came with the distribution, as depmod was failng. After a fresh recompile all your module load but nodes under "leds" are not there, it seems that the dtso/dtbo is not read - nothing appears in dmesg.
Attached the working dtso file.
-
I will try to upgrade to tm16xx driver and be back.
As for the HDMI, do you mean that Multitool shoud work anyway?
THKS
-
-
Hi, thanks a lot for pointing me in the right direction. Indeed so far I am booting from the SD card. I have erased eMMC with multitool via SSH, as multitool as well is not visible via HDMI. Used the newer images as suggested, same situation: everything works via SSH cmd line, no output on HDMI. Log contains mainly errors as the ones posted above.
-
Thank you for the answer.
Yes I will try the various dts, so far I have found that librelec - despiite not running at all, is crashing giving a visible prompt on the HDMI.
I will try to compare that dtb/dts to the default rk3318-box and be back.
-
Hi, welcome everyone. I’m using an H50 TV box that I was about to throw away because I thought I had completely bricked it.
I disassembled it and found the pins to activate maskrom mode.
I think this could be useful for everyone.
I then installed the current image, and everything seems to work except for the HDMI output (blank screen).
Do you have any suggestions? Thanks. Some data and photo below.
In case you want to install please note that also multitool fails to activate the HDMI, so you will need SSH to config.
SOC: RK3188 (Hopefully - I did not remove the heatsink)
eMMC: Samsung KLMBG4GEAC-B001 32GB (64x4)
eMCP: Samsung KMQN10006B 8 GB eMMC + 1 GB LPDDR3 RAM
Wi-Fi IC 339S0209 2.4G/5G
LAN working
WIFI Working
----------------------------
root@rk3318-box:~# lscpu
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: ARM
Model name: Cortex-A53
Model: 4
Thread(s) per core: 1
Core(s) per cluster: 4
Socket(s): -
Cluster(s): 1
Stepping: r0p4
CPU(s) scaling MHz: 60%
CPU max MHz: 1008.0000
CPU min MHz: 600.0000
BogoMIPS: 48.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 256 KiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Gather data sampling: Not affected
Indirect target selection: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Reg file data sampling: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Not affected
Spectre v1: Mitigation; __user pointer sanitization
Spectre v2: Not affected
Srbds: Not affected
Tsa: Not affected
Tsx async abort: Not affected
Vmscape: Not affected
root@rk3318-box:~# free -l
total used free shared buff/cache available
Mem: 1504636 291372 1037440 46940 297848 1213264
Low: 1504636 467196 1037440
High: 0 0 0
Swap: 752316 0 752316
SOME TESTS ON THE HDMI ISSUE:
hdmi_debug_20251008_230528.log
Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G
in Rockchip CPU Boxes
Posted · Edited by GmP
@GBEM yes the service file can be improved, also it might be worth it to blacklist some unuseful module like:
sudo nano /etc/modprobe.d/blacklist.conf
# Add:
blacklist btusb
blacklist btrtl
blacklist btbcm
blacklist btintel