@balbes150 LE images with Kodi-19 for S9xxx

  • Quote from balbes150
    Try the latest version image 20191008. Preferably with UART output.

    Hello balbes150,

    Nanopi-K2 booting again.

    GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;

    no sdio debug board detected

    TE: 317760

    BL2 Built : 12:06:06, Jun 13 2016.

    gxb g176ecdb - laiyin.mo@droid12-sz

    set vcck to 1100 mv

    set vddee to 1000 mv

    Board ID = 8

    CPU clk: 1536MHz

    DDR chl: Rank0+1 same @ 792MHz

    DDR0: 2048MB(auto)-2T-11

    DataBus test pass!

    AddrBus test pass!

    Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000

    New fip structure!

    Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x0000d460

    Sending bl30......................................................OK.

    Run bl30...

    Load bl31 from SD, src: 0x00020200, des: 0x101000[00, size: 0x00013140

    Image: gxb_v1.1.3134-b387442 2016-06-16 14:48:44 yun.cai@droid06]

    OPS=0x13

    f0 8c d5 21 23 9f ab d1 5e e4 dd 45 [0.413206 Inits done]

    secure task start!

    high task start!

    low task start!

    Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x0007c300

    NOTICE: BL3-1: v1.0(debug):c813a61

    NOTICE: BL3-1: Built : 14:47:05, Jun 16 2016

    INFO: BL3-1: Initializing runtime services

    WARNING: No OPTEE provided by BL2 boot loader

    ERROR: Error initializing runtime service opteed_fast

    INFO: BL3-1: Preparing for EL3 exit to normal world

    INFO: BL3-1: Next image address = 0x1000000

    INFO: BL3-1: Next image spsr = 0x3c9


    U-Boot 2019.07 (Oct 08 2019 - 15:37:28 +0300) nanopi-k2

    Model: Unknown

    Soc: Amlogic Meson GXBB (S905) Revision 1f:c (13:1)

    DRAM: 2 GiB

    MMC: mmc@70000: 0, mmc@72000: 1

    In: serial@4c0

    Out: serial@4c0

    Err: serial@4c0

    Net:

    Warning: ethernet@c9410000 (eth0) using random MAC address - 42:a2:51:d6:ad:8a

    eth0: ethernet@c9410000

    Hit any key to stop autoboot: 0

    switch to partitions #0, OK

    mmc1 is current device

    Scanning mmc 1:1...

    Found /extlinux/extlinux.conf

    Retrieving file: /extlinux/extlinux.conf

    161 bytes read in 5 ms (31.3 KiB/s)

    1: LibreELEC

    Retrieving file: /KERNEL

    17723400 bytes read in 856 ms (19.7 MiB/s)

    append: boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=ttyAML0,115200n8 console=tty0

    Retrieving file: /dtb/meson-gxbb-nanopi-k2.dtb

    27379 bytes read in 6 ms (4.4 MiB/s)

    ## Flattened Device Tree blob at 08008000

    Booting using the fdt blob at 0x8008000

    Loading Device Tree to 000000007df58000, end 000000007df61af2 ... OK

    Starting kernel ...

    [ 0.146241] debugfs: Directory 'c1105400.audio' with parent 'regmap' already present!

  • Can someone tell me whats the current situation with libreelec on n2? Does everything, except netflix, work?

    This topic is for images in development!

    If you want to test and tell yourself the current situation this is the right place.

    Here we help developers by reporting issues.

    Look for nothing stable here, just developing images as quoted in the topic.:thumbup:

  • balbes150 I realized did a unification of the amlogic images, I correct if I'm wrong.

    S905, X, D processors. Now use the same image. (Great job)

    CEC is broken in the images:

    AML.arm-9.80-devel-20191013180457-6e9040d-amlgx

    CvH I do not know if you have done some work on the crazycat driver until the moment did not recognize the tuner TBS.

    Edited once, last by erbas (October 13, 2019 at 8:32 PM).

  • I just tried the 0922 and 0944 for the s912. Unfortunately, the LibreElec Repository does not work, its pointing to an non-existing folder. Are there alternatives to get a PVR client except from the repository?

  • 1. The G12 platform (s905x2 s922x a311d) now uses a single image (it also works on N2).

    2. For the Odroid N2 model, I only check the option to run on USB media using SPIboot.

    3. Addons are transferred to the new Kodi-19 platform, there may be failures and not correct operation. Therefore, it is recommended to test a clean install\run (without using the update via TAR).

    Image update 20191019.