Status of NanoPC-T4 (RK3399)

  • In the latest build Kodi 19 does not start (LibreELEC-RK3399.arm-9.80-devel-20191011115114-6e9040d-box.img) I think you forgot to link the libraries:

    You took the version with kernel 5, this is a very new direction and a lot of things may not work from version to version. It is intended for General tests.



    at the moment I don't know how to start the NanoPC-T4 from USB, so I haven't tested it yet.

    See the posts in the topic. Verification is very simple. To write the image Armbian to SD card (do not need to configure DTB). The image on the SD card is only needed to run u-boot, then it should start from USB. Write to USB flash drive LE with kernel 4 (you can use any working version of LE). Configure on USB correctly DTB. Connect SD card and USB flash drive to T4. Turn on the power and wait 3-4 minutes. If nothing happens, you need to try to connect a USB flash drive to another connector USB. Start your tests with USB 2.0 connectors. I have on EDGE and on Magicsee N6 now in eMMC already installed the latest version of LE (20191011 with kernel 4) and now I can quickly run different test systems from a USB flash drive.


    What is the difference between the images (desktop and normal) ?

    Versions of Armbian called Desktop have an XFCE GUI. Default images are server images.

  • The latest versions of Libreelec (and Armbian) added the to start the system from USB media. Can you test this new feature on your T4 ? Details can be found in this topic.


    https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87554

    Hallo balbes150 ,


    so, I tested your new image LibreELEC-RK3399.arm-9.80-devel-20191011084333-6e9040d-box.img.gz (Kernel 4.4) with the DTB for nanopc-t4 directly from the image.


    Step one:

    Burn image to SD

    Change DTP to your nanaopt-t4.dtb


    Step two:

    Burn image to USB

    Change DTP to your nanaopt-t4.dtb


    Step three:

    Insert the SD card into the NanoPC-T4 and connect the USB to a free USB3 port.


    Then the NanoPC-T4 will boot normally.



    boot -> ok

    WiFI -> ok

    WiredNet -> ok

    EMMC -> ok

    Bluetooth -> ok

    Video -> ok (max 1920x1024x60Hz)

    Sound (HDMI) -> ok

    Sound (USB) -> ok


    EMBY -> ok

    TVHeadend Client -> ok


    /storage ist mounted from my USB Stick:


    LibreELEC:~ # df

    Filesystem 1K-blocks Used Available Use% Mounted on

    devtmpfs 1951480 4 1951476 0% /dev

    /dev/sda1 524008 172656 351352 33% /flash

    /dev/loop0 144896 144896 0 100% /

    /dev/sda2 14222669 362834 13855739 3% /storage

    tmpfs 1985720 0 1985720 0% /dev/shm

    tmpfs 1985720 9992 1975728 1% /run

    tmpfs 1985720 0 1985720 0% /sys/fs/cgroup

    tmpfs 1985720 2224 1983496 0% /var

    tmpfs 1985720 0 1985720 0% /tmp

    /dev/mmcblk1p1 502820 164868 337952 33% /var/media/LE_EMMC

    /dev/mmcblk0p2 27633 779 26199 3% /var/media/STORAGE

    /dev/mmcblk1p2 14294663 570472 12982806 4% /var/media/DATA_EMMC

    /dev/mmcblk0p1 524008 172656 351352 33% /var/media/LIBREELEC



    It looks to me like everything's going to be just fine.


    But I have one more question:


    Is there a schedule when I can test a LE image with kernel 5 that works without USB?


    Many greetings and a nice weekend


    Jerry

  • Where did you find the LOG entry?

    Since the kernel is working and the problem is in Kodi I could connect via SAMBA. There you find a folder called "Log". In the log file 09_Journal-cur.log the kodi error is I posted here.

  • JerryPenguin About the schedule question - It takes as long as it takes and you are requesting too much ;) (new Kernel and new Kodi).


    What WiFI module are you using (chipset) and does it work in other images with the 5.3 kernel, e.g. armbian? USB works correctly, but I think in the kernel config for LibreElec 5 / RK3399 some required modules are disabled. I can upload a working build with the "old" Kodi and the new kernel (I just applied the pull request 3560 to the mainline).

  • JerryPenguin About the schedule question - It takes as long as it takes and you are requesting too much ;) (new Kernel and new Kodi).


    What WiFI module are you using (chipset) and does it work in other images with the 5.3 kernel, e.g. armbian? USB works correctly, but I think in the kernel config for LibreElec 5 / RK3399 some required modules are disabled. I can upload a working build with the "old" Kodi and the new kernel (I just applied the pull request 3560 to the mainline).

    Hi zeus24 ,


    I know that all too well and please don't take my question as impatience.


    Rather, I offer myself as a tester for the platform and may be able to contribute something.


    I myself am a sysadmin and Python/Skrip developer but not a kernel or LE developer.


    Therefore I am grateful to you and balbes150 that you also consider the not so common SOC NanoPC-T4.


    Many greetings

  • There is interesting information about co-running the same image on two platforms simultaneously rk3399 and rk3328. This will further allow to have a shared image for rk3399 and rk3328 when upgrading via TAR. The details there is in this topic.


    https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87869


    It would be useful to test this option on different rk3399 and rk3328. By the way, the latest Libreelec and Armbian images use a common u-boot-2019.10, the difference is only in the configuration for the two platforms when building.

  • There is interesting information about co-running the same image on two platforms simultaneously rk3399 and rk3328. This will further allow to have a shared image for rk3399 and rk3328 when upgrading via TAR. The details there is in this topic.


    https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87869


    It would be useful to test this option on different rk3399 and rk3328. By the way, the latest Libreelec and Armbian images use a common u-boot-2019.10, the difference is only in the configuration for the two platforms when building.

    Hi balbes150 ,


    I'll test your new images once next week.

    There I have vacation and time :-)


    Greetings

    Jerry

  • There is interesting information about co-running the same image on two platforms simultaneously rk3399 and rk3328. This will further allow to have a shared image for rk3399 and rk3328 when upgrading via TAR. The details there is in this topic.


    https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87869


    It would be useful to test this option on different rk3399 and rk3328. By the way, the latest Libreelec and Armbian images use a common u-boot-2019.10, the difference is only in the configuration for the two platforms when building.

    Hi balbes150 ,


    I tested your two new images:


    1. LE Kernel 4 20191018


    Then the NanoPC-T4 will boot normally.


    boot -> ok

    WiFi -> ok

    WiredNet -> ok

    EMMC -> ok

    Bluetooth -> ok

    Video -> ok (max 1920x1024x60Hz)

    Sound (HDMI) -> ok

    Sound (USB) -> ok

    CEC -> N/A


    EMBY -> ok

    TVHeadend Client -> ok


    2. LE Kernel 5 20191019 with Boot from SD and LE on USB


    boot -> ok

    WiFi -> ok

    WiredNet -> ok

    EMMC -> ok

    Bluetooth -> ok

    Video -> ok (max 1920x1024x60Hz)

    Sound (HDMI) -> ok

    Sound (USB) -> ok

    CEC -> ok


    EMBY -> not tested

    TVHeadend Client -> not tested


    I can't test the dualboot option, I only have a NanoPC-T4 and no other RK device.


    Greetings

    Jerry

  • Omg, today I did an update on my T4 with Rock960 LE 20191031 image and it broke my system badly.


    This new image is based on Kodi 19 Alpha 1 and a lot of adons are not supported on it.


    Does anyone have older image based on last version of Kodi 18?

  • There is interesting information about co-running the same image on two platforms simultaneously rk3399 and rk3328. This will further allow to have a shared image for rk3399 and rk3328 when upgrading via TAR. The details there is in this topic.


    https://forum.armbian.com/topic/8263-armbian-for-rk3399/?do=findcomment&comment=87869


    It would be useful to test this option on different rk3399 and rk3328. By the way, the latest Libreelec and Armbian images use a common u-boot-2019.10, the difference is only in the configuration for the two platforms when building.

    I've also tested your images, both kernels. Kernel v4 works just like JerryPenguin reported, apart from HDMI CEC. I'm using Philips 42PFS7189/12 TV and with my old SolidRun HummingBoard Pro i2ex HDMI CEC works on that TV with the same HDMI cable.


    I've managed to get HDMI CEC running with your image and DTB from Joern-p's image, but then the sound doesn't work.



    Kernel v5 refuses to boot at all with the following error message:


    *** Error in mount_flash: mount_common: Could not mountLABEL=LIBREELEC ***

    ### Start debugging shell for boot steps: mount_flash... type exit to quit ###

  • I've managed to get HDMI CEC running with your image and DTB from Joern-p's image, but then the sound doesn't work.

    Hi jtosic,


    the device tree depends on the kernel. The kernel in my build is that of friendlyarm 4.4.179 (original for nano-pc t4).

    The sound works with this kernel.


    Greetings

  • I have a nanopc-t4 and have been trying the various images referenced in this thread without success. The best for me has been Joern-p's image, but for me that image doesn't have working audio over the headphone jack. The same is true for me with the LibreElec nightly with the correct dtb. The friendlyarm image has audio through the headphone jack, so I know my hardware is working.


    Is anyone using the headphone jack, and if so, which image have you gotten to work?


    Thanks for any help!

  • Hi balbes150 ,

    If it's not a secret, what version of the LE image (full name) do you have installed in eMMC ?


    no, it's no secret :-)


    I use your image LibreELEC-RK.arm-9.80-devel-20191025134119-6e9040d-rk3399.img.gz.


    But I've just seen you have newer images available and I'll test the latest once a week and report here.


    Any news about the images with Kernel 5?


    Greetings

    Jerry