Posts by npcomplete

  • Unofficial LE for RK356x RK3328\RK3399 RK3588(s)

    hi balbes150 I'm seeing errors while playing 4K content as well as some 1080p content.

    I'm running the build on RK3399 based X99 TV box

    [ 199.702783] ------------[ cut here ]------------

    [ 199.702813] WARNING: CPU: 2 PID: 1001 at drivers/gpu/drm/drm_gem.c:1096 drm_gem_mmap_obj+0x1a8/0x208

    [ 199.703499] Modules linked in: 8021q garp mrp stp llc rockchip_rga rockchip_vdec(C) hantro_vpu(C) videobuf2_vmalloc videobuf2_dma_sg videobuf2_dma_contig videobuf2_memops v4l2_h264 v4l2_mem2mem bnep brcmfmac videobuf2_v4l2 videobuf2_common fusb302 tcpm brcmutil typec videodev snd_usb_audio cfg80211 snd_usbmidi_lib panfrost snd_soc_simple_card joydev hci_uart btqca btrtl btbcm gpu_sched btintel crct10dif_ce btsdio snd_soc_simple_card_utils bluetooth snd_hwdep ecdh_generic ecc gpio_ir_recv mc rfkill ipv6

    [ 199.703688] CPU: 2 PID: 1001 Comm: kodi.bin Tainted: G WC 5.10.0-rc5 #1

    [ 199.703692] Hardware name: Hugsun X99 TV BOX (DT)

    [ 199.703700] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)

    [ 199.704397] pc : drm_gem_mmap_obj+0x1a8/0x208

    [ 199.704404] lr : drm_gem_mmap_obj+0x7c/0x208

    [ 199.704408] sp : ffff8000145f3c00

    [ 199.704415] x29: ffff8000145f3c00 x28: 0000000000000008

    [ 199.704426] x27: ffff000040348d80 x26: ffff000047368000

    [ 199.705705] x25: 0000000000000258 x24: ffff0000466fa400

    [ 199.705714] x23: ffff00004731e800 x22: ffff000049a58000

    [ 199.705721] x21: ffff000040348d80 x20: 0000000000000000

    [ 199.705729] x19: ffff00006572e000 x18: 0000000000000000

    [ 199.705736] x17: 0000000000000000 x16: 0000000000000000

    [ 199.705743] x15: 0000000000000000 x14: 0000000000000000

    [ 199.705751] x13: 0000000000000000 x12: 0000000000000000

    [ 199.705758] x11: 0000000000100000 x10: ffff000047368028

    [ 199.705766] x9 : 0000000000000001 x8 : 00000000000000c8

    [ 199.706316] x7 : 0000000000000020 x6 : 0000000000008bf4

    [ 199.706323] x5 : ffff00006572e020 x4 : 0000000000000000

    [ 199.706330] x3 : ffff0000473c6d38 x2 : 0000000000000064

    [ 199.706337] x1 : 0000000000000000 x0 : 00000000000000fb

    [ 199.706345] Call trace:

    [ 199.706356] drm_gem_mmap_obj+0x1a8/0x208

    [ 199.706361] drm_gem_mmap+0x164/0x2a0

    [ 199.707492] mmap_region+0x3d8/0x6a0

    [ 199.707498] do_mmap+0x34c/0x588

    [ 199.707504] vm_mmap_pgoff+0x90/0xf0

    [ 199.707986] ksys_mmap_pgoff+0x1b8/0x1e8

    [ 199.707994] __arm64_compat_sys_aarch32_mmap2+0x20/0x30

    [ 199.708000] el0_svc_common.constprop.0+0x80/0x220

    [ 199.708916] do_el0_svc_compat+0x1c/0x48

    [ 199.708922] el0_sync_compat_handler+0x140/0x28c

    [ 199.708927] el0_sync_compat+0x178/0x180

    [ 199.708933] ---[ end trace 328f70cbfe9d8601 ]---

  • Early mainline images for RK3288, RK3328 and RK3399

    Quote from lumpi

    Hi everyone

    Is this the correct thread for the actual nightly builds for rk3399 devices here: Index of /

    I'm actually thinking about buying an rk3399 based board and am wondering if it is possible to turn the SBC on via IR remote or on board button, or if it has to be powercycled once shut down.

    Thanks

    P.S. turns out npcomplete has similar question :) I guess it all depends if there is an embedded controller and if that's supported by mainline LE.

    I was reading else where and I think this needs to be configured in u-boot, i.e u-boot controls "power-on" and LibreElec (OS) controls the "power-on"

    I'm interested in power-on either from hdmi-cec or RC

  • LED (VFD) Displays in LibreELEC

    hi The Coolest

    [Edit: just realized I opened an old thread]

    I see following error on RK3399 TV Box:

    Code
         Loaded: loaded (/usr/lib/systemd/system/openvfd.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
  Condition: start condition failed at Sat 2020-01-11 01:34:31 UTC; 15min ago
             └─ ConditionPathExists=/proc/device-tree/openvfd was not met

Jan 11 01:34:31 LibreELEC systemd[1]: Condition check resulted in OpenVFD Service being skipped.

    This is in manufacturer's DTS:

    Code
        skykirin_led {
        compatible = "skykirin-ht1628";
        spi_clk = <&gpio1 RK_PB1 GPIO_ACTIVE_HIGH>;
        spi_cs = <&gpio1 RK_PB2 GPIO_ACTIVE_HIGH>;
        spi_data = <&gpio1 RK_PB0 GPIO_ACTIVE_HIGH>;
        status = "okay";
    };

    Let me know how to fix this

  • Early mainline images for RK3288, RK3328 and RK3399

    [EDIT] Ignore my post. I fixed the incorrect voltage used for pmu_io_domains (1.8 correct vs 3.0 wrong) now I do get 1080p display. I'll post my dts soon.

    Kwiboo I have a RK3399 box (X99) for which I had a working 4.4 dts. I tried booting the rockpro64 img, but it gave an error wrt i2c on the serial console.

    I ended up modifying the original 4.4 dts which got rid of the i2c error bringing it closer to rockpro64, but the screen is blank. There is an error regarding EDID is blank.

    Let me know so I can provide any debug logs or dump of any parameters from serial console.

  • Videostrong(Mecool) VS-RK3399

    Quote from fosf0r

    1) Is this build hardcoded to speak to Videostrong hardware, or does it contain the full DTB tree for the tons of rk3399 variants, such that if I threw it on my pine rockpro64, it would figure itself out?

    2) What kernel version is it? ( if it's not exactly 4.4.138 I will be unable to use it, because my designware/synposis "i2s"/bridge driver goes bad past 4.4.138 which is what my rockpro64 uses for HDMI-carried audio I think?; anyway >4.4.138 floods dmesg with 'fail to clear' errors and audio goes -1,000x speed, sounds like a demon when you play a file if using >4.4.138). How would I even begin getting help with that?

    This build was never intended to drive anything but vs-rk3399. Even if SoCs are same, vendors pick and choose what features to implement and how to implement them. So you might get lucky if this build works on your board, but no guarantee.

    Also this build uses kernel v4.4.154.

  • Videostrong(Mecool) VS-RK3399

    Here you go: