Posts by _emanuel_

New build from amlogic branch works nice as far as I can see, till now no shutdown (pm) problems.

I had tested it like this before:

gpio-keys-polled {
    compatible = "gpio-keys-polled";
    poll-interval = <100>;

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

leds {
    compatible = "gpio-leds";
    #status = "disabled";

    sys-led {
        label="sys_led";
        gpios=<&gpio_ao GPIOAO_11 GPIO_ACTIVE_HIGH>;
        default-state ="on";
        retain-state-suspended;
        linux,default-trigger="cpu0";
        };
};

but it only caused interference with the IR remote control. (gpio-keys-polled) After a few button presses, the exit menu suddenly starts to flicker on off on off... Kodi can then no longer be operated and must be terminated via terminal. I hadn't caught either the LED or the Power HW button at the time. With your patch I have the same flakes. The HW power button and the LED don't work either. Dreamtwo has an RGB LED. I think Dreamone is only blue. If I set the gpio-keys-polled to GPIO_ACTIVE_LOW, the menu stops flickering, but it still appears with almost every X keystroke, but you get out with exit.

What are the adc keys for? how can i test it?

I've got shutdown problems.

see log

@chewitt: now it works nice

one patch hung, but build boots.

APPLY PATCH (device)      projects/Amlogic/devices/AMLGX/patches/linux/amlogic-0028-FROMLIST-v6-arm64-dts-Fix-NPU-power-domain-reference.patch
patching file arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
Hunk #2 succeeded at 2493 (offset 1 line).
patching file arch/arm64/boot/dts/amlogic/meson-g12b.dtsi
patching file arch/arm64/boot/dts/amlogic/meson-sm1.dtsi

The log in the attachment

@chewitt: woks nice without:

amlogic-0022-FROMLIST-v6-dt-bindings-power-Add-G12A-NNA-power-dom.patch.aus

amlogic-0023-FROMLIST-v6-soc-amlogic-meson-pwrc-Add-NNA-power-dom.patch.aus

amlogic-0024-FROMLIST-v6-arm64-dts-Add-DT-node-for-the-VIPNano-QI.patch.aus

amlogic-0025-FROMLIST-v6-drm-etnaviv-Add-nn_core_count-to-chip-fe.patch.aus

amlogic-0026-FROMLIST-v6-drm-etnaviv-Warn-when-probing-on-NPUs.patch.aus

amlogic-0028-FROMLIST-v6-arm64-dts-Fix-NPU-power-domain-reference.patch.aus

amlogic-0052-WIP-arm64-dts-meson-add-support-for-the-NPU-on-Radxa.patch.aus

Wifi only works setting

LibreELEC.tv/amlogic-0088-WIP-arm64-dts-meson-add-initial-device-trees-for-Dre.patch at bb98dc6f00cc16e33796ac0dc4fc672281a7093f · chewitt/LibreELEC.tv

Just enough OS for KODI. Contribute to chewitt/LibreELEC.tv development by creating an account on GitHub.

github.com

to

<&gpio GPIOA_11 GPIO_ACTIVE_LOW>;

The log in the attachment

@chewitt: I just built a testimg from your github amlogic branch.

Unfortunately, kernel 6.1.0 does not boot like this.

The log in the attachment

I've made a build from your github LE src (Branche "amlogic") 6.1-rc8 still do not boot on dreambox.

@chewitt: You recently gave me a test image that unfortunately didn't boot. It had a linux 6.1 kernel.

Did you fix that with the nand on some boxes?

If so, could you build the box img for me?

Would be interesting if wifi works there.

It works with my dtb in le-nightly (6.0.9) but not in armbian-current (6.0.14) or in armbian-etch (6.1).

(brcmfmac debug log attached)

>>> found the patch armbian bug, now wifi works on 6.0/6.1.1

@ chewitt: Since I'm dependent on a chain uboot, I noticed the following: since this commit https://github.com/u-boot/u-boot/…4b8373dbb7b6dc5 the terminal display only works if I explicitly add "CONFIG_BAUDRATE=1000000" to the u-boot config. Maybe I'm not the only one there.

@chewitt my update for the dreambox patches.

@chewitt I've found working dreambox gpio reset :-))

sdio_pwrseq: sdio-pwrseq {
compatible = "mmc-pwrseq-simple";
reset-gpios = <&gpio GPIOA_11 GPIO_ACTIVE_LOW>;
clocks = <&wifi32k>;
clock-names = "ext_clock";
};

The image did not boot, see pic.

So I've copied the dtb in the nightly build. Booted, but no wifi.

I am trying to activate the Wifi (brcmfmac) on a Dreambox (s922x).

I have tested all g12b dtb, it does not work.

Also not by hand.

Blutooth works and that's the same brcm chip.

See log using a gtking like dtb:

hastebin

chewitt

The manager wrote to me that he would like to send you hardware.

If you want a Dreambox, you can send me your address.

I will handle your data carefully and only pass it on to the managing director.

Bad news...

>> or you switch to the vendor kernel and work with CE sources

I made that before, worked well incl. dvb. [Dreambox One UHD] - Amlogic s922X - #14 by buzzmarshall - Development & Testing - CoreELEC Forums

Other team is still working with that src, but never new builds have problem with decoding.

It is not all about kodi, other things like Linux Distr and the AndroidTV-11 (yukawa) all uses mainline.

>> I also learned some things about the M4 chip used for MCU functions.

Does that cause the reboot in other kernels such as the vendor. There for is the fp-dev.ko?

>> I don't have the skillset to debug much more about the boot issue without access to hardware.

So hardware could help? I'll tell this the manager.

I better had to been reading first: If you can get u-boot sources it's simple to extract the FIPs.

I wrote to the manager again (incl. link).

I haven't got developer emails only:

irc freenode Channel #enigma2

Developers are: __Ghost__, [3des], reichi

or the Forum - Dreamboard

so I'm still waiting

Unfortunately I don't have any feedback yet.

I only know that they are very busy with something new, as the managing director told me.

Can you really stretch the bin?

I'll attach both of them.

uboot_dreamone.bin.zip

uboot_dreamtwo.bin.zip

I asked the vendor about the original fip bins.

I hope something comes from them.

I want to see how it works in standalone.

Hopefully the mainline u-boot will work without my 2 ugly patches.

Are the fips very different for the s922x boxes?

I once flashed a vim3 bootloader that bricked the box.