Posts by ChriChri

    Just tried https://test.libreelec.tv/11.0/Rockchip/…8-rock64.img.gz and ScummVM didn't start.

    To be honest I'd prefer to fix it somehow manually in the actual stable I use. Is there somewhere documented how to "reproduce or not" the build-problem?

    If I could "not reproduce" the problem would I have to install the whole image or just replace the add-on?

    Edit: As I understood from what I read the build problem only exists on github and is not reproducible when building on other machines. A build I would do on my notebook (e.g. inside a docker image) should work and should not reproduce the problem, right?

    From what others wrote I guess that I'd have to replace the add-on only - like with one that vpeter build previously for people in this thread and that WebEye confirmed that it worked.

    Edit: Checked out libreelec-10.0 and build it successfully - what a ride ;-). Then build the addons game.libretro and game.libretro.scummvm. Updated my rock64 to the freshly build libreelec and installed the two addons. I could start scummvm - great!

    Added Monkey Island (first one, german version, files: 000.LFL 902.LFL 904.LFL DISK02.LEC DISK04.LEC 901.LFL 903.LFL DISK01.LEC DISK03.LEC) to scummvm and started it.

    Sound started, the midi tunes seemed to be mixed up, but I still could recognize them. Screen stayed black.

    On my notebook the same files work in scummvm.

    Updated my rock64 to the official version 10.0.3 again.

    Recognized that I may need to use 10.0.3 and checked out that tag to build the add-ons from that tree again and test them.

    Edit: Didn't make a difference. Or maybe a git checkout 10.0.3; git pulldidn't do what I expected. Anyway, opened an issue.

    Hey, thanks for the information! You made my day! I'll check and get back...

    ...later:

    With your information at hand I compared the armbian dtb with the libreelec dtb again and found how to do it:

    In 'spdif@ff870000 {' I changed 'status = "disabled";' to 'status = "okay";'.

    To disable some other output I changed in 'i2s@ff880000 {' 'status = "okay";' to 'status = "disabled";'.

    There's been sound on the optical output :). I still have to test whether it really works without errors or glitches, but it is definitely the right track I'm on.

    Wouldn't it be a nice idea to put an alternative dtb inside the RockPro64 image so that it is easier for users to change to spdif?

    boot ends with kernel panic:


    DDR Version 1.17 20190115
    In
    channel 0
    CS = 0
    MR0=0x98
    MR4=0x1
    MR5=0xFF
    MR8=0x10
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 1
    CS = 0
    MR0=0x98
    MR4=0x1
    MR5=0xFF
    MR8=0x10
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8


    MR25=0x0
    channel 0 tr@ining pass!
    channel 1 tr@ining pass!
    change freq to 400MHz 0,1
    channel 0
    CS = 0
    MR0=0x98
    MR4=0x1
    MR5=0xFF
    MR8=0x10
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 1
    CS = 0
    MR0=0x98
    MR4=0x1
    MR5=0xFF
    MR8=0x10
    MR12=0x72
    MR14=0x72
    MR18=0x0
    MR19=0x0
    MR24=0x8
    MR25=0x0
    channel 0 tr@ining pass!
    channel 1 tr@ining pass!
    change freq to 800MHz 1,0
    Channel 0: LPDDR4,800MHz
    Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
    Channel 1: LPDDR4,800MHz
    Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
    256B stride
    ch 0 ddrconfig = 0x101, ddrsize = 0x40
    ch 1 ddrconfig = 0x101, ddrsize = 0x40
    pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
    OUT
    Boot1 Release Time: Dec 24 2019 18:00:26, version: 1.24
    CPUId = 0x0
    ChipType = 0x10, 313
    mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
    mmc: ERROR: Card did not respond to voltage select!
    emmc reinit
    mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
    mmc: ERROR: Card did not respond to voltage select!
    emmc reinit
    mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
    mmc: ERROR: Card did not respond to voltage select!
    SdmmcInit=2 1
    mmc0:cmd5,20
    SdmmcInit=0 0
    BootCapSize=0
    UserCapSize=1920MB
    FwPartOffset=2000 , 0
    StorageInit ok = 48373
    SecureMode = 0
    SecureInit read PBA: 0x4
    SecureInit read PBA: 0x404
    SecureInit read PBA: 0x804
    SecureInit read PBA: 0xc04
    SecureInit read PBA: 0x1004
    SecureInit read PBA: 0x1404
    SecureInit read PBA: 0x1804
    SecureInit read PBA: 0x1c04
    SecureInit ret = 0, SecureMode = 0
    GPT 0x3380ea0 signature is wrong
    recovery gpt...
    GPT 0x3380ea0 signature is wrong
    recovery gpt fail!
    LoadTrust Addr:0x4000
    No find bl30.bin
    No find bl32.bin
    Load uboot, ReadLba = 2000
    Load OK, addr=0x200000, size=0xaa7b0
    RunBL31 0x40000 @ 158908 us
    NOTICE: BL31: v1.3(debug):734d84297
    NOTICE: BL31: Built : 15:30:40, Dec 12 2019
    NOTICE: BL31: Rockchip release version: v1.1
    INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
    INFO: Using opteed sec cpu_context!
    INFO: boot cpu mask: 0
    INFO: If lpddr4 need support multi frequency,
    INFO: please update loader!
    INFO: Current ctl index[0] freq=400MHz
    INFO: Current ctl index[1] freq=800MHz
    INFO: plat_rockchip_pmu_init(1190): pd status 3e
    INFO: BL31: Initializing runtime services
    WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEK
    ERROR: Error initializing runtime service opteed_fast
    INFO: BL31: Preparing for EL3 exit to normal world
    INFO: Entry point address = 0x200000
    INFO: SPSR = 0x3c9


    U-Boot 2017.09 (May 28 2020 - 04:15:26 -0400), Build: jenkins-RK3399-273

    Model: Rockchip RK3399 Evaluation Board
    DRAM: 3.9 GiB
    Relocation Offset is: f7d14000
    PMIC: RK808
    pwm-regulator(vdd-center): init 950000 uV
    vdd_center 950000 uV
    regulator(vdd-center) init 950000 uV
    MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0
    Using default environment

    In: serial@ff1a0000
    Out: serial@ff1a0000
    Err: serial@ff1a0000
    Model: Rockchip RK3399 Evaluation Board
    Net: eth0: ethernet@fe300000
    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
    reading /extlinux/extlinux.conf
    228 bytes read in 7 ms (31.3 KiB/s)
    1: LibreELEC
    Retrieving file: /KERNEL
    reading /KERNEL
    17774600 bytes read in 759 ms (22.3 MiB/s)
    append: boot=UUID=2805-0959 disk=UUID=0121dc5d-3c0a-4846-a32a-bec4742338d2 quiet console=uart8250,mmio32,0xff1a00000
    Retrieving file: /rk3399-rockpro64.dtb
    reading /rk3399-rockpro64.dtb
    56543 bytes read in 10 ms (5.4 MiB/s)
    ## Flattened Device Tree blob at 01f00000
    Booting using the fdt blob at 0x1f00000
    Loading Device Tree to 00000000f5eea000, end 00000000f5efacde ... OK
    Adding bank: start=0x00200000, size=0xf7e00000

    Starting kernel ...


    [ 8.644734] rockchip-drm display-subsystem: failed to bind ff940000.hdmi (ops dw_hdmi_rockchip_ops): -517
    [ 8.698999] panfrost ff9a0000.gpu: failed to get regulators: -517
    [ 8.701343] panfrost ff9a0000.gpu: regulator init failed -517
    [ 9.282244] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
    [ 9.394251] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port
    [ 10.994540] Unable to handle kernel paging request at virtual address ffff800014a02194
    [ 10.997087] Mem abort info:
    [ 10.997994] ESR = 0x86000006
    [ 10.998945] EC = 0x21: IABT (current EL), IL = 32 bits
    [ 11.000675] SET = 0, FnV = 0
    [ 11.001573] EA = 0, S1PTW = 0
    [ 11.002555] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000002d87000
    [ 11.004576] [ffff800014a02194] pgd=00000000f7fff003, pud=00000000f7ffe003, pmd=0000000000000000
    [ 11.007292] Internal error: Oops: 86000006 [#1] SMP
    [ 11.008417] Modules linked in:
    [ 11.009561] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 5.6.6 #1
    [ 11.010853] Hardware name: Pine64 RockPro64 v2.1 (DT)
    [ 11.012166] pstate: 40000005 (nZcv daif -PAN -UAO)
    [ 11.013416] pc : 0xffff800014a02194
    [ 11.014600] lr : of_device_get_modalias+0x60/0x168
    [ 11.015828] sp : ffff80001004b5d0
    [ 11.016798] x29: ffff80001004b5d0 x28: 0000000000000000
    [ 11.018278] x27: ffff800010c11f08 x26: ffff0000f175cb00
    [ 11.019707] x25: ffff800010a35da8 x24: ffff0000f650c000
    [ 11.021091] x23: 0000000000000000 x22: ffff0000f7807510
    [ 11.022472] x21: ffff0000f650c1e0 x20: 000000000000073b
    [ 11.023821] x19: ffff0000f1771c20 x18: 0000000000000001
    [ 11.025175] x17: ffff8000106e3bc8 x16: ffff8000106e0350
    [ 11.026525] x15: ffff0000f6e10410 x14: ffffffffffffffff
    [ 11.027871] x13: ffff0000f650c91c x12: ffff0000f650c1d5
    [ 11.029203] x11: 0000000000000004 x10: 0101010101010101
    [ 11.030556] x9 : fffffffffffffffd x8 : 7f7f7f7f7f7f7f7f
    [ 11.031903] x7 : fefefeff646c606d x6 : 0a041b0ce3e5dff4
    [ 11.033241] x5 : 0000000000000000 x4 : 0000000000000054
    [ 11.034592] x3 : ffff0000f7807510 x2 : ffff800010c97000
    [ 11.035928] x1 : 000000000000073b x0 : ffff0000f650c1e0
    [ 11.037264] Call trace:
    [ 11.038154] 0xffff800014a02194
    [ 11.039264] of_device_uevent_modalias+0x60/0xb0
    [ 11.040598] i2c_device_uevent+0x18/0x58
    [ 11.041778] dev_uevent+0xcc/0x2d0
    [ 11.042921] kobject_uevent_env+0x2e8/0x7b8
    [ 11.044097] kobject_uevent+0x10/0x18
    [ 11.045226] driver_bound+0x90/0x100
    [ 11.046327] really_probe+0x118/0x438
    [ 11.047441] driver_probe_device+0xdc/0x130
    [ 11.048651] __device_attach_driver+0x88/0x108
    [ 11.049868] bus_for_each_drv+0x74/0xc0
    [ 11.050999] __device_attach+0xdc/0x160
    [ 11.052146] device_initial_probe+0x10/0x18
    [ 11.053315] bus_probe_device+0x90/0x98
    [ 11.054536] device_add+0x5fc/0x788
    [ 11.055709] device_register+0x1c/0x28
    [ 11.056877] i2c_new_client_device+0x138/0x278
    [ 11.058154] of_i2c_register_device+0xb0/0xd8
    [ 11.059424] of_i2c_register_devices+0x9c/0x198
    [ 11.060690] i2c_register_adapter+0x150/0x408
    [ 11.061938] __i2c_add_numbered_adapter+0x58/0xa0
    [ 11.063222] i2c_add_adapter+0x9c/0xc8
    [ 11.064429] rk3x_i2c_probe+0x258/0x3f0
    [ 11.065635] platform_drv_probe+0x50/0xa0
    [ 11.066781] really_probe+0xd8/0x438
    [ 11.067869] driver_probe_device+0xdc/0x130
    [ 11.069070] device_driver_attach+0x6c/0x78
    [ 11.070253] __driver_attach+0x9c/0x168
    [ 11.071346] bus_for_each_dev+0x6c/0xc0
    [ 11.072462] driver_attach+0x20/0x28
    [ 11.073533] bus_add_driver+0x138/0x218
    [ 11.074670] driver_register+0x60/0x110
    [ 11.075862] __platform_driver_register+0x44/0x50
    [ 11.077231] rk3x_i2c_driver_init+0x18/0x20
    [ 11.078428] do_one_initcall+0x50/0x190
    [ 11.079694] kernel_init_freeable+0x208/0x2a0
    [ 11.080903] kernel_init+0x10/0xfc
    [ 11.081980] ret_from_fork+0x10/0x1c
    [ 11.083150] Code: bad PC value
    [ 11.084319] ---[ end trace 7af8388fcaf1564e ]---
    [ 11.087057] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
    [ 11.089038] SMP: stopping secondary CPUs
    [ 11.090247] Kernel Offset: disabled
    [ 11.091273] CPU features: 0x10002,2000600c
    [ 11.092293] Memory Limit: none
    [ 11.093553] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

    Quote

    Ihre Nachricht enthält folgende zensierte Wörter: tr@ining (4×)

    What good is it for to censor tr@ining?

    Sometime giving the thought about an approach some time helps. Not this time. I'm stuck.

    I'd bet that there is only something really small to change to get the spdif output for rockpro64 working since the difference to the dtb and kernel of armbian is so slight. But I don't see my approach to pin it.

    Nobody else out there running rockpro64 and thinking about using a digital output ;) ?

    Anybody who can point me in the right direction to look to find the difference?

    Thought some more about it. Build my own image - cool build process :) .

    Compared config.gz and dtb of Armbian to the ones of LibreElec and found differences.

    Made some changes to .config of the kernel package in LibreElec (funny, I had to change the package directory to get a rebuild of the package - changing the kernel configuration didn't do the trick) and changed some minor difference in the dtb.

    I'm still reading about these things as I'm new to them.

    Well, I'm stuck with this message on serial console when starting:

    Code
    [    2.128560] rockchip-spdif ff870000.spdif: Missing dma channel for stream: 0
    [    2.129312] rockchip-spdif ff870000.spdif: ASoC: pcm constructor failed: -22
    [    2.130055] asoc-simple-card spdif-sound: ASoC: can't create pcm ff870000.spdif-dit-hifi :-22
    [    2.130946] asoc-simple-card spdif-sound: ASoC: failed to instantiate card -22

    Don't know how to cure this. The system is otherwise working fine, but no spdif out.

    New image 20200406

    New to this. But anyway, I tried on RockPro64 v2.1:

    • downloaded the image and put it on a sdcard
    • edited uEnv.txt to contain FDT=/dtb/rockchip/rk3399-rockpro64.dtb
    • booted of the sdcard (my jumper for disabling eMMC is closed - the eMMC contains an armbian)

    The connected hdmi monitor doesn't get a signal (works in armbian).

    I connected the serial console and found the system working except the output to the hdmi connected monitor. I appended the output of the serial console.

    Just got my Rock64Pro and started it with LibreElec. Still need to connect it via toslink:

    - Looked around to find a vendor for DLT1150A or a similar toslink f.e.m.a.l.e connector, but just found offers for a whole box (2000 pieces) of them. Any idea where to get the connector (from Germany)?

    - Looked at "Audio output devices" in LibreElec and found 4x ALSA (Default: HDMI Analog, HDMI Analog, HDMI HDMI, ES8316 Analog) and a Pulse Bluetooth Audio. Which one would be the right output to get a signal on the SPDIF header?


    Thanks, Chris

    PS: My message contains the censored word "f.e.m.a.l.e" as part of the technical name of the thing one can plug a toslink cable into. I'm not an english native speaker and its been the only translation I found.

    After my cubox is not supported any more I ordered a Rock64Pro to use instead. I need TOSLINK to connect audio and looked around for a solution like for the audio board for the Rock64 that does not work on the Rock64Pro.

    I found the this forum message with a description how to connect SPDIF/TOSLINK to pins on the Rock64Pro.

    Did anybody try this, yet? Is there information whether audio routing with LibreELEC would work through such a connection?