From today’s build 20260306 there is separate dtb for this device named s6_s905x5_ugoos_am9_pro.dtb. Please use this one which has at least fix for a LED for now which works the same way as on non Pro version.
I also tested the new dtb for the Ugoos AM9 Pro.
The dtb works correctly and allows proper control of the status LED color and brightness, thanks to the corrected mosi-gpios configuration. At this point, a big thank you to the developers.
For anyone who wants to experiment with it or adjust the behavior on their system, here are some details.
LED node in the dtb
The relevant section is the /led node:
/led {
compatible = “amlogic,sk9822_led”;
status = “okay”;
sck-gpios = <0x1d 0xa 0x0>;
mosi-gpios = <0x1d 0x5b 0x1>;
active-color = <0x01003000>;
suspend-color = <0x01000090>;
shutdown-color = <0x00000000>;
};
The status LED is controlled via an SK9822 controller.
Color value format
Colors are defined as 32-bit values in the format:
Example from the dtb: active-color = <0x01003000>
You can read the current values in CoreELEC with:
cat /sys/devices/platform/led/colors/*
Example output: active color is 1 00 30 00
Value meaning
Brightness (1–9)
Red
Green
Blue
Testing colors live (no reboot required)
The LED can be controlled directly via sysfs.
Example: red at lowest brightness
echo “1 ff 00 00” > /sys/devices/platform/led/colors/active
Persistent settings via CoreELEC (autostart.sh)
Changes via /sys are not persistent and will reset after reboot.
To apply settings automatically, create:
/storage/.config/autostart.sh
Setting colors directly in the dtb
Alternatively the colors and brightness can be defined directly inside the dtb. This requires a custom compiled dtboutside the official CoreELEC release.
Example:
active-color = <0x02000040>;
suspend-color = <0x02400000>;
shutdown-color = <0x00000000>;
Disabling the LED completely
Inside the dtb:
status = “disabled”;
or simply set all colors to 0:
active-color = <0x00000000>;
suspend-color = <0x00000000>;
shutdown-color = <0x00000000>;
Hello, I found an issue on the latest nightly with Ugoos AM9 Pro. If I play a Dolby Vision file that has an L5 active area set for top and bottom (so it’s not 0-0) then the player’s navigation bar (interface) gets invisible because the L5 value is cut off. The functions are working (I can stop, pause etc) but I don’t see the buttons.
A few nightlies ago this could be resolved by setting the “override L5 with 0” option in the Display menu, but now that’s not working anymore. I see the difference in the brightness of the black letterbox bars when I change this setting but the player’s navigation bar won’t reappear.
I’d like to share my impressions of the AM9 Pro running CoreELEC 22.0-Piers_alpha3, having previously used Khadas Vim 4: Overall, it’s very stable, boots up very quickly, and has the widest range of format support I’ve seen so far (only Profile 7 FEL is missing). Unfortunately, the graphics performance is far below that of Vim 4, making it impossible to display the interface in 4K (the frame rate is too low). Furthermore, the screen tearing (vertical desynchronization?) present even with the GUI upscaler makes for a very unpleasant user experience.
Therefore, I’ve decided to stick with VIM4 for a while longer, even though this issue is likely due to a graphics driver problem. In any case, I’d like to thank the developers for their work.