Early mainline images for RK3288, RK3328 and RK3399

  • After some time of private testing mainline linux v5.1 on my rockchip devices here are some images for wider testing.


    Please note that this is very early mainline images and are not meant as a replacement for you daily driver.

    At this stage information if an image do not boot or stack traces is very good feedback.


    RK3288 (Tinker Board S) and RK3328 (Rock64, roc-cc, rockbox) have got most of my attention,

    so I expect there is more issues with RK3399 or any of the other boards/boxes not listed.


    For RK3399 owners there are some more device tree files in .tar-file at 3rdparty/bootloader/.

    Copy correct .dtb-file to sd-card and change DTB line in extlinux/extlinux.conf,

    please report if dtb-file works for any device not having a dedicated .img.gz-file


    What should work?
    - MPEG-2 hw decoding (everything else is sw decoded)
    - 8ch Linear PCM HDMI audio

    - SPDIF
    - CEC
    - IR (keymap is not pre configured)

    - Ethernet

    - SD/eMMC


    Known issues:
    - Only up to 1080p resolution and not all refresh rates
    - 10-bit videos will show as green picture
    - SW decoding of VP8 on RK3399 produce garbage
    - Hotplug of USB3 on RK3328 only work one time, a reboot is required to discover a new/replug usb device
    - No AC3/DTS/HD audio

    - No WiFi/BT (wifi should work on tinkerboard)

    - No deinterlacer


    Code:
    - Commits · Kwiboo/LibreELEC.tv · GitHub


    Images:
    - Index of /test/


    Please report any issues related to HDMI, Audio, CEC, IR, Ethernet not already listed in known issues.
    Issues related to other IO ports on your board will be ignored for now (too early to care about non-media player related issues).


    Thanks!

  • I tested trn9 build

    HDMI, spdif-Audio, CEC were OK

    Ethernet/WiFi/BT were not OK so I couldn't test more.

  • May I ask you to point me the correct build and/or dtb file for RK3399 H96 Max 2g RAM version?

    Sorry, I have only included dtb-files that have been submitted to mainline, with the exeption of some rk3328 dtb-files.

    Is there a good dts-file that can be ported to mainline and eventually be submitted upstream somewhere?


    Ethernet/WiFi/BT were not OK so I couldn't test more.

    Thanks for reporting, I will test ethernet on my MVR9 box, never did more then a quick boot test on MVR9 before posting 8)

  • May I ask you to point me the correct build and/or dtb file for RK3399 H96 Max 2g RAM version?

    There is no support for that device.

    Please ask the manufacturer to send sample devices to the LibreELEC developers plus the kernel source code.

    Try all the other RK3399 dts files and check which one works the best then the things not working can perhaps be fixed.

  • Is there any way for a beginner to modify same device's 4gig version dtb (seen in a neighbour thread)?

    Tried all the dtb's - the box doesn't boot

    Edited once, last by Patkino ().

  • Hi Kwiboo,


    I was running into an issue while I was updating from the latest tinkerboard nightly to your version.


    The error message during boot is LibreELEC-RK3288.arm-9.1-devel-20190512171730-bdfaff1-tinkerboard.img.gz does not work with tinkerboard hardware.

  • Hi Kwiboo,


    I was running into an issue while I was updating from the latest tinkerboard nightly to your version.


    The error message during boot is LibreELEC-RK3288.arm-9.1-devel-20190512171730-bdfaff1-tinkerboard.img.gz does not work with tinkerboard hardware.

    I think you may need to do a clean install. Please keep in mind that this is very early test images, so I would recommend you to test on a separate sd-card.

  • Hi,

    thanks a lot. Yeah was afraid of that. I installed libreelec on the internal emmc and the board is in a aluminium case for cooling. It is always a bit of a struggle to get the sd-card in and find the right jumper position. ;)

    Maybe during one of the next weekends.

    Thanks again, especially for all the great work on the rockchip adaptation. :thumbup:

  • tested the rockpro64 image, got a 'mode not supported' error on my 1080p60 monitor using HDMI. I can't tell if its the image or the old monitor causing the issue. For the record, the official 9.0.2 LE image works fine on the same hardware. I do not think ssh is enabled by default so I cannot remote in for logs unfortunately. Any suggestions are appreciated.

  • Hi.

    Checked the image for Khadas EDGE. As part of no DTB. I tried starting with DTB from RockPI4 ,the system normally starts carries out the STORAGE partition extension, reboots and LE starts (there is a Le screensaver and in the UART console there is a prompt for management), but Kodi itself does not start. This may be the result of an incorrect DTB (from another model).

  • Yeah was afraid of that. I installed libreelec on the internal emmc and the board is in a aluminium case for cooling. It is always a bit of a struggle to get the sd-card in and find the right jumper position.

    You should not need to change the emmc jumper to boot from sd-card, at least I do not have too, it will probably use ddr+u-boot from emmc, if u-boot is new enough it should still try to boot from sd-card before trying to boot from emmc.


    tested the rockpro64 image, got a 'mode not supported' error on my 1080p60 monitor using HDMI. I can't tell if its the image or the old monitor causing the issue.

    Mainline 5.1 linux do not have support for all video resolutions and refresh rate at the moment, connecting the device to a TV usually work, the old vendor 4.4 kernel have much better support for different resolutions and refresh rates and is why your monitor works using the latest non-mainline images. This should improve in the future.


    Checked the image for Khadas EDGE. As part of no DTB.

    I totaly forgott to remove that image Before uploading, mainline do not have a DTS for Khadas Edge and I have not created one yet, I will run tests and create a Khadas Edge dts suitable for mainline before next update.

  • I totaly forgott to remove that image Before uploading, mainline do not have a DTS for Khadas Edge and I have not created one yet, I will run tests and create a Khadas Edge dts suitable for mainline before next update.

    The initial patches for adding support for EDGE in the main kernel a long time (I build and test with them the images of Armbian for EDGE kernel NEXT). :)


    Build-Armbian/patch/kernel/rk3399-tv-next at master · 150balbes/Build-Armbian · GitHub



    Khadas representatives have no experience in sending requests to the core. Perhaps you will be able to advise Khadas specialists how to form the correct sending of requests for inclusion in the main kernel ?


    Linux mainline support - Khadas Edge - Khadas Community

  • If I can figure out how to send stuff to the kernel the knowledge barrier is set really low. Khadas just need to read HOWTO(s) and have a go :)

  • H96 MAX (4 GB version) with unmodified rk3399-rockpro64.dtb:

    Linux kernel boots: OK

    Kodi starts: OK

    Ethernet: OK

    HDMI CEC: OK

    HDMI audio: OK

    OpenGL ES 3.2 HW acceleration: OK

    MPEG-2 HW decoding: Not tested as there are no PVR addons


    So far so good :thumbup:

  • Maybe someone ran into this issue: my box doesn't boot at all with (probably) correct dtb files.


    Device: Libre Computer/ Firefly ROC-RK3399-PC

    dtb I tried: rk3399-roc-pc.dtb + rk3399-firefly.dtb


    I think that it might be a problem of the sdcard/partition format, because all images provided by firefly are in a not recognized partition format for linux. The flashed µSD with their images look to be empty/not formatted at all, but they boot.

    Any idea what I can try out?

  • [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.



    Edited 3 times, last by npcomplete ().