Posts by ArtUrlWWW

  • Can't build the latest master branch from git repo

    I have cleaned it with

    PROJECT=Amlogic DEVICE=S912 ARCH=arm scripts/clean openssl

    PROJECT=Amlogic DEVICE=S912 ARCH=arm make image


    but it failed again:

  • Can't build the latest master branch from git repo

    I've cleaned project with

    make clean

    PROJECT=Amlogic DEVICE=S912 ARCH=arm scripts/clean linux


    and started

    PROJECT=Amlogic DEVICE=S912 ARCH=arm make image -j 4

    again

    but it failed again, but at another moment:

    What I do wrong? :)

  • Can't build the latest master branch from git repo

    devusr@scw-97b47e:/home/le/LibreELEC.tv$ git branch

    * master

    devusr@scw-97b47e:/home/le/LibreELEC.tv$ git log

    commit 544f25dffdc1e267033a252d5239456d0cc208d4 (HEAD -> master, origin/master, origin/HEAD)

    Merge: 3049f4ffc 9f0d70b81

    Author: MilhouseVH <[email protected]>

    Date: Wed Mar 7 16:18:30 2018 +0000

    Merge pull request #2556 from HiassofT/le9-rpi-kodi-pr13594

    RPi: temporarily add kodi PR13594

    commit 3049f4ffc3d16d124e9ea6d2b734bce3739c360f

    Merge: 6f7037fcd 9c76dbc3a

    Author: Radostan Riedel <[email protected]>

    Date: Wed Mar 7 09:55:28 2018 +0100

    Merge pull request #2564 from ToKe79/aml-uboot-patch1

    Amlogic u-boot: fix order of PKG_URL and PKG_VERSION

  • Can't build the latest master branch from git repo

    Hello.

    I've tried to compile sources from master branch of GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI , but it failed to compile with

    Code
    PROJECT=Amlogic DEVICE=S912 ARCH=arm make image -j 2

    If I restart it again, I got this output log:

    Is master branch broken now?

  • [8.2.2.3] LibreELEC 8.2 for S912

    Hello.

    kszaq , I found, that my tv box with 3GB RAM has DTS with

    Code
    memory@00000000 {
        device_type = "memory";
        linux,usable-memory = <0x0 0x100000 0x0 0xbff00000>;
    };

    I am newbie in u-boot and DTB files, but I think, that 0xbff00000 means 3,220,176,896 bytes = 3220176896/(1024^2)=3,071 GB , right?

    But I see in Kodi System Info, that it found only 2,805MB of RAM.

    Why not all RAM showing in Kodi?

    It looks like you use aarch64 and it should use all available RAM

    uname -a

    Linux LibreELEC 3.14.29 #1 SMP Fri Oct 6 14:11:43 CEST 2017 aarch64 GNU/Linux

  • [S905] Device trees

    Nope :) . I am in correct thread, because I plan to provide kszaq a new version of gmx_q201_3g.dtb for my TV box.

    Good news, everyone! :)

    My decompiled dts is different from kszaq's gmx_q201_3g.dtb decompiled dts.

    So I have a little hope, that my TV box could start with gmx_q201_3g.dtb, splitted from my multi-DTB file and will work with libreelec and balbes150's Armbian.

    But it just a hope, I'll check it tonight at home :).

    Thank you again for info, kszaq !

  • [S905] Device trees

    Quote from Tim_Taylor

    What is the benefit ?

    To learn and to start Armbian on Beelink GT1 Ultimate.

    I also have done it to check, is kszaq's version of gmx_q201_3g.dtb similar to mine - I'll check for differences those decompiled dts data in text format.

    I couldn't start balbes150's Armbian with kszaq's version of gmx_q201_3g.dtb , so I have a suspicion, that my dtb file could be different from kszaq's version of gmx_q201_3g.dtb . So, I'll check it now.

  • [S905] Device trees

    OK, I figured out, what is the multi-dtb file :) .

    Here is my a very simple Python 3.3 code for my multi-dtb file parsing:

    It may be useful for somebody in the future, I hope :)

    I plan to test splitted dts files tonight.

  • [S905] Device trees

    kszaq , you are right, your gmx_q201_3g.dtb works fine with your libreelec distrib for s912, thank you very much for this distrib.

    Looks, like you have a very good memory - I wrote, that I have successfully started libreelec with gmx_q201_3g.dtb some time ago :) .

    But currently I am trying to start armbian ubuntu-based distrib from balbes150. I know, that it's not your distrib and, possible, not your area, but I trying to ask you only as an expert, not distrib owner.

    Display Spoiler

    The problem is that tv box starting well without any DTB files in BOOT and trying to start X, failed, console only:

    IMG_20171220_215905.jpg


    After that I've rebooted TV box with CTLR+ALT+DEL and got another view:

    Display Spoiler


    IMG_20171220_220728.jpg

    I've tried all files from dtb directory and, as result, TV box booted only with kvim****.dtb files, but the similar boot error.

    With other files from dtb directory TV box didn't booted at all - it hangs on Beelink boot logo.

    Here is my /var/log/ directory from TV box, booted with kvim multiboot dtb - log.zip - Google Drive .

    I also tried to start it with gmx_q201_3g.dtb from your libreelec distrib, but armbian distrib hangs on bootloader Beelink logo too.

    Can you advise me, how to fix such error?

  • [S905] Device trees

    kszaq , I found a very strange thing.

    In my extracted dts file there is info

    amlogic-dt-id = "gxm_q201_1g";

    and

    memory@00000000 {

    device_type = "memory";

    linux,usable-memory = <0x0 0x100000 0x0 0x3ff00000>;

    };

    Ie, in /etc/dtb there is file for 1GB RAM version of the TV box, but I have Ultimate version, that has 3GB RAM and Android used 3GB very well.

    How could it be?

    Looks like Android doesn't use that dtb file and developers of Beelink didn't updated DTB file for Ultimate version with 3GB RAM!!! :(

  • [S905] Device trees

    kszaq , there is some problem with downloaded file.

    I tried

    dd if=/dev/dtb > /sdcard/dtb.img

    and

    cat /dev/dtb > /sdcard/dtb.img

    but file, downloaded with

    adb pull /sdcard/dtb.img

    has not same file header, not like in your dtb files, if I view it in HEX...

    It also can't be processed with dtc, that was installed on ubuntu with command

    sudo apt-get install device-tree-compiler

    Result is

    dtc -I dtb -O dts -o dts dtb.img

    FATAL ERROR: Blob has incorrect magic number

    and

    boot.img-ramdisk.gz dtb.img env.img extract-dtb.py mmcblk0boot0.img mmcblk0boot1.img mmcblk0rpmb.img split_bootimg.pl

    root@scw-97b47e:/tmp/qqq# fdtdump dtb.img

    /dts-v1/;

    // magic: 0x414d4c5f

    // totalsize: 0x2000000 (33554432)

    // off_dt_struct: 0x3000000

    // off_dt_strings: 0x206d7867

    // off_mem_rsvmap: 0x20202020

    // version: 538976288

    // last_comp_version: 538976288

    // boot_cpuid_phys: 0x31303271

    // size_dt_strings: 0x20202020

    // size_dt_struct: 0x20202020

    Segmentation fault


    My downloaded file is here dtb.img - Google Drive .

    Can you take a loot at him?

    Thank you!