Dreambox/Dreambox2 S922X device-tree experiments

_emanuel_ · April 3, 2021 at 7:50 PM

@chewitt

LibreELEC-AMLGX.arm-9.95.1-box.img.gz and also *10.0-nigthly* do not boot, they only freezes Box.

I've tested nigthly with chainload: Image booting, only sound works, screen is black.

I've build uboot for chainload from 2021.04

I've got no idea how to patch u-boot.bin to enable screen.

Other u-boot.ext from balbes150 could not handle lzo compressed Imgs.

AMLGX.arm-9.95.1-box.log

nightly.txt

_emanuel_ · April 5, 2021 at 12:08 AM

I've built mainline-u-boot 2020.10 (config lzo). It boots chainloaded the Image with screen

I've also built kernel module dreambox rc-keymaps (patch), and a dtb (patch).

rc works, but system-RGB-LED (gpio-leds) is ignorimg DTB's configs.

Very nice running Image!!

**chewitt** · April 5, 2021 at 8:58 AM Official Post

I moved the posts. Please share a URL to a GitHub repo with the dtb or patches (or share the patches) and I will see what changes might be needed for the LEDs and buttons. It should be simple to add.

**chewitt** · April 5, 2021 at 5:02 PM Official Post

_emanuel_ Updated LibreELEC-AMLGX.arm-9.95.1-box.img.gz image has two device-tree files for dreambox one/two that I created earlier. Please test whether the LED/button bits work. There are no RC keymaps in the image - I can see the BSP kernel keymaps, but there are 4x maps. If you can explain which keymap is used in which box I will add them.

See last four commits here: Commits · chewitt/linux · GitHub

_emanuel_ · April 5, 2021 at 5:29 PM

I tried several settings from several dtbs, not even:

Code

leds {
compatible = "gpio-leds";


sys_led {
label = "sys_led";
// color = <LED_COLOR_ID_RED>;
// function = LED_FUNCTION_POWER;
// gpios = <& gpio_ao GPIOAO_11 GPIO_ACTIVE_HIGH>;
gpios = <& gpio_ao GPIOAO_11 GPIO_ACTIVE_LOW>;
// default-state = "on";
// linux, default-trigger = "cpu0";
// linux, default-trigger = "heartbeat";
};
};

Display More

turns the LED off.

The keymaps function so far with the original assignment (got only the two new one, i could add more later)

But now I'll test the Image: LibreELEC-AMLGX.arm-9.95.1-box.img.gz

and give feedback later.

By the way (my nigthly build), I've notice one issue: while updating via update tar, it extracts all the dtbs to the LIBREELEC's root (mmc 0), not in the dtb folder, where they are stored normaly?

_emanuel_ · April 5, 2021 at 6:04 PM

Code

##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################

LibreELEC (chewitt): 9.95.1 (AMLGX.arm)
LibreELEC:~ # cd /sys/devices/platform/leds/leds/blue:power
LibreELEC:/sys/devices/platform/leds/leds/blue:power # echo 0 > brightness
LibreELEC:/sys/devices/platform/leds/leds/blue:power # cat brightness
0
LibreELEC:/sys/devices/platform/leds/leds/blue:power # echo gpio > trigger
LibreELEC:/sys/devices/platform/leds/leds/blue:power # echo 0 > brightness
LibreELEC:/sys/devices/platform/leds/leds/blue:power # echo 0 > max_brightness
-sh: can't create max_brightness: Permission denied
LibreELEC:/sys/devices/platform/leds/leds/blue:power # ls
brightness      max_brightness  subsystem       uevent
device          power           trigger
LibreELEC:/sys/devices/platform/leds/leds/blue:power # cat trigger
[none] rc-feedback kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock heartbeat gpio cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 mmc2 mmc1 mmc0 activity default-on rfkill-any rfkill-none 0.0:00:link 0.0:00:1Gbps 0.0:00:100Mbps 0.0:00:10Mbps rfkill0
LibreELEC:/sys/devices/platform/leds/leds/blue:power # cat uevent
OF_NAME=blue
OF_FULLNAME=/leds/blue
OF_COMPATIBLE_N=0
LibreELEC:/sys/devices/platform/leds/leds/blue:power #

Display More

still on, no changes at all.

_emanuel_ · April 5, 2021 at 6:11 PM

linux,rc-map-name = "rc-dreambox-one";

I would only use:

linux,rc-map-name = "rc-dreambox";

they are using the same ones.

_emanuel_ · April 5, 2021 at 7:49 PM

Suddenly the Exit menu started without turning on, starting on and off going in a loop, see log attached.

I also had this in my build when I gave the DTB the

Code

    gpio-keys-polled {
        compatible = "gpio-keys-polled";
        #address-cells = <1>;
        #size-cells = <0>;
        poll-interval = <100>;

        power-button {
            label = "power";
            linux,code = <KEY_POWER>;
            gpios = <&gpio_ao GPIOAO_3 GPIO_ACTIVE_HIGH>;
        };
    };

Display More

**chewitt** · April 5, 2021 at 7:53 PM Official Post

Bump v4.9.113-641429-g1883b89 · emanuel4you/linux-meson64@7f99a65 · GitHub

^ this is probably why the LED doesn't work - and you can see 11/4 are in use for other things. In the absence of schematics the best thing to do is boot an original dreambox kernel and see what is set there. It might be a PWM config rather than GPIO, or a different GPIO_AO?

**chewitt** · April 5, 2021 at 8:04 PM Official Post

Updated LibreELEC-AMLGX.arm-9.95.1-box.img.gz image has RC keymaps added and I removed button things as those are likely wrong too. I moved the LED to GPIOAO_3, but this is just a random guess.

_emanuel_ · April 5, 2021 at 8:31 PM

Code

root@dreambox:/proc/stb/fp# ls
fp_version  led_blink  led_brightness  led_color  led_fade  nec_ir  phy_powered  rtc  wakeup_time  was_timer_wakeup
root@dreambox:/proc/stb/fp# cat *
1.12
000710ff
000000ff
00ffffff
00000007
00000001
01617649904
0
0
root@dreambox:/proc/stb/fp#

Display More

This is all build in a chain of drivers hanging on the "fp-dev" driver,

the Led is not listed in /sys/devices/platform/leds/ like in mainline.

The main task of this fp-dev driver is the communication with the manufacturer boot loader: shutdown / reboot / standby / wakeup / ... The boot loader always gets the reboot result = boot loader (0x8), regardless of whether I have Android, LibreElec, ... Enter "shutdown -h now" always arrives reboot bootloader. Unless I'm using the original kernel with the fp-dev. That's why I built the Android and the CE with the original kernel in order to be able to use the drivers. I suspect that the original boot loader omitted the reboot result somewhere else.

Here I looked for the GPIOs with an on-off hack driver and multimeter.

Post

RE: [9.X-devel] LibreELEC builds for g02ref/g18ref_th2 (Prima PM-6001, VS-IP166, VS-IP015, ...)

Update + Addon VFD Display (Prima PM-6001, VS-IP166 ) locale: en/de

Have fun

emanuel4you

March 4, 2019 at 10:35 PM

Will flash the update

_emanuel_ · April 5, 2021 at 8:58 PM

The build in remotes work great.

LED - still fishing...

Code

LibreELEC:/sys/devices/platform/leds/leds/blue:power # echo gpio > trigger
LibreELEC:/sys/devices/platform/leds/leds/blue:power # echo 0 > brightness
LibreELEC:/sys/devices/platform/leds/leds/blue:power # cat *
0
cat: read error: Is a directory
1
cat: read error: Is a directory
cat: read error: Is a directory
[none] rc-feedback kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock heartbeat gpio cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on mmc2 mmc0 mmc1 rfkill-any rfkill-none 0.0:00:link 0.0:00:1Gbps 0.0:00:100Mbps 0.0:00:10Mbps rfkill0
OF_NAME=blue
OF_FULLNAME=/leds/blue
OF_COMPATIBLE_N=0
LibreELEC:/sys/devices/platform/leds/leds/blue:power #

Display More

**chewitt** · April 6, 2021 at 5:18 AM Official Post

The fp-dev component sounds like an MCU so it's probably attached via i2c, but is also probably a custom part so you would need infos or sources from the manufacturer (or proper reverse-engineering skills) to figure it out.

Do you have any high-resolution PCB photos? - is there an RTC chip and power cell attached? - I would expect yes (to support timed wake and record) but there is no mention of this in the vendor kernel device-tree or sources.

_emanuel_ · April 6, 2021 at 8:54 PM

So I took a couple of nude photos, thank God the girl is still playing with me

https://photos.app.goo.gl/7mGqKxuFeikQSaKBA

By the way: I've also tested the Img on "dreamtv" (s905x2, u212) same manufacture, other vendor, android streaming box.

it has a real problem with mmc 0, it can load kernel form it, but the later mount fails and the /dev/mmcblk0 does not exists only mmc 1 (emmc).

_emanuel_ · April 6, 2021 at 9:59 PM

made a log and a nice picture

the box uses the same remote as the dreambox, but I'm not so far at all...

_emanuel_ · April 8, 2021 at 8:26 PM

So, new build bootloader acts a little bit better (rigth color). But still isscues with mounts

**chewitt** · April 9, 2021 at 3:29 AM Official Post

[ 2.298762] Run /init as init process

^ the boot log stops here because of the console ordering you've defined in boot params (the order matters):

systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0 <= correct ordering

console=ttyAML0,115200n8 console=tty0 no_console_suspend systemd.debug_shell=ttyAML0 <= yours

I also use boot=LABEL=LIBREELEC, disk=LABEL=STORAGE instead of UUIDs, so see if that makes a difference?

_emanuel_ · April 9, 2021 at 11:09 AM

Now I've got only kernel panic