Posts by _emanuel_

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

    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>;
        };
    };

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

I would only use:

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

they are using the same ones.

##############################################
#                 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 # 

still on, no changes at all.

I tried several settings from several dtbs, not even:

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";
};
};

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?

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

see log at RE: Official LE Test Images for Amlogic (Kodi-19)

@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

For Dreambox One/Two IRs

Sadly the april image crashes here while resize the storage:

@chewitt: Thank you for the info, that sounds very good (except for the slow development of the vdec driver).

First and foremost, I wanted to rule out the device-tree as an accident/non-boot source of errors for the image.

So it have been the vdec.

What is missing, I have to try it out first,

I haven't even thought of LEDs, keymaps, bluetooth, wifi, display, etc. until now.

@ balbes150 First of all, thank you for making these images.

That was the first image with a mainline kernel that ran longer than 5 minutes on the

Dreambox dreamone (s922x) / deamtwo (s922x).

The method of reloading the u-boot.ext is ingenious.

I used meson-g12b-ugoos-am6.dtb with a patched memory line.

Now that I've finally got a mainline kernel running on the box, I would like to adapt the device tree.

Unfortunately, I still have no idea what to adapt to the 5.X dt.

This is totally new to me. I have the current Dreambox kernel src here: see dreamone.dts/dreamtwo.dts

A better fitting dt would be very helpful, because the image freezes to death when I play a TS-stream via the enigma2-pvr-addon. I don't know if Panfrost works at all on running TS-streams, but otherwise the image was the best of all mainline tests, All other kernels have already died with a low I/O load or didn't even start.

And I would be grateful for any tip.