Posts by JerryPenguin

  • Status of NanoPC-T4 (RK3399)

    Quote from balbes150

    Try running this image Armbian on T4. It includes DTB for nanopc-t4. :)

    https://yadi.sk/d/sogru62pp1y_2q

    Wait a Moment ... I will test it.

    So, I tested it with the DTB directly from the image.

    Boot, EMMC, Bluetooth -> ok

    WiFi -> same problem with non-loadable firmware

    Video -> ok

    Sound:

    At first it wasn't possible via HDMI. I tried it via USB (changed via Default Sink), it worked. Changing to HDMI afterwards was ok.

    After every reboot the same problem, switch manually once and then sound came over HDMI.

    Under Debian there was no problem, only here under Ubuntu Bionic.

    The second DTB file in your download link, is it the same (right size) as in the image or should I do a test with it?

    I would still have time for a test today, then again at the weekend.

    Greetings

  • Status of NanoPC-T4 (RK3399)

    Quote from balbes150

    No, it's a new file. Maybe in the next images I will add this new DTB for T4.

    This would be advantageous for many in this thread, many are waiting for it. Thank you in advance. :)

    Quote from balbes150

    But you can check yourself, will work DTB rockpro64 from the image LE or not. :)

    No, or let's say once until about May I tried again and again to use the DTBs from your images.

    But there was always no WiFi device detected.

    Via dmesg I could see that.

    A modprobe on bmdhd failed because no device was found.

    Quote from balbes150

    PS Alas, I have no T4 for tests, significantly reduces the speed of debugging. :(

    No, or let's say once until about May I tried again and again to use the DTBs from your images.

    But there was always no WiFi device detected.

    Via dmesg I could see that.

    A modprobe on bmdhd failed because no device was found.

    But you deliver first class work for Rockchip Devices. And unfortunately almost every SBC manufacturer has its peculiarities and uses slightly different chips that are not already integrated.

    It would be easier for everyone if at least the standard components were the same.

    At the beginning of the year I had also been thinking about buying a Khadas EDGE, I can't remember why I got away from it.

    Too bad that FriendlyElec or FriendlyARM doesn't provide you developers with boards.

    I have searched for a long time for a suitable DTB file. Also the one from Armbian didn't work with LE.

    At some point I found what I was looking for at Recalbox. :)

    But your current DTB is really good and fast. Thanks a lot. :)

    I use Armbian on a BananaPI-M3, but only for Pi-Hole, Wireguard, OpenVPN and Munin.

    Greetings

  • Status of NanoPC-T4 (RK3399)

    Hi balbes150,

    it runs like a charm with your DTB file :)

    With WiFi the same problem, but the boot process runs 4-5 times faster.

    I have connected the NanoPC-T4 to my 4k monitor, but can only set the resolution to 1920x1024x60Hz.

    Your test video runs fine with sound.

    I will test your DTB file with my LE installation.

    Let's see if it works :)

    Addendum:

    Your DTB also works fine with your LE image, which I use.

    Thanks a lot

    Many greetings

    PS:

    Is the DTB file rk3399-rockpro64.dtb the one from your last LE images at

    https://yadi.sk/d/qgyvmkow5oqcha/2019090 ???

  • Status of NanoPC-T4 (RK3399)

    Yes, I can also watch the video in FullScreen Mode.

    And yes, in the log I see that he has problems with the firmware of the WiFi adapter:

    --snip

    [ 216.054284] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000

    [ 216.054394] dhd_bus_set_default_min_res_mask: Unhandled chip id

    [ 216.054723] dhd_os_open_image: /lib/firmware/brcm/config.txt (70 bytes) open success

    [ 216.054756] dhd_conf_read_pm_params: PM = 0

    [ 216.054764] dhd_conf_read_nv_by_chip: nv_by_chip_count=1

    [ 216.054771] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt

    [ 216.054776] CONFIG-ERROR) dhd_conf_read_config: not a right parameter 43430 0 nvram_ap6212.txt

    [ 216.054797] Final fw_path=/lib/firmware/brcm/fw_bcm4356a2_ag.bin

    [ 216.054801] Final nv_path=/lib/firmware/brcm/nvram_ap6356.txt

    [ 216.054805] Final clm_path=/lib/firmware/brcm/clm.blob

    [ 216.054809] Final conf_path=/lib/firmware/brcm/config.txt

    [ 216.055416] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/brcm/fw_bcm4356a2_ag.bin

    [ 216.055422] _dhdsdio_download_firmware: dongle image file download failed

    [ 216.055462] dhd_bus_devreset Failed to download binary to the dongle

    [ 216.055471] dhd_net_bus_devreset: dhd_bus_devreset: -35

    [ 216.055478] dhd_wl_ioctl: returning as busstate=0

    [ 216.055485] dhd_dbg_detach_pkt_monitor, 2204

    [ 216.055490] dhd_net_bus_devreset: dhd_bus_devreset: -35

    [ 216.055560] wifi_platform_set_power = 0

    [ 216.055566] ======== PULL WL_REG_ON(-1) LOW! ========

    [ 216.055571] [WLAN_RFKILL]: rockchip_wifi_power: 0

    [ 216.055589] [WLAN_RFKILL]: wifi shut off power.

    [ 216.055593] wl_android_wifi_on: Failed

    [ 216.055599] dhd_open : wl_android_wifi_on failed (-35)

    [ 216.055605] dhd_stop: Enter ffffffc0ebc06000

    [ 216.055609] wl_android_wifi_off in 1

    [ 216.055614] wl_android_wifi_off in 2: g_wifi_on=0, on_failure=1

    [ 216.055619] dhd_wl_ioctl: returning as busstate=0

    [ 216.055623] dhd_dbg_detach_pkt_monitor, 2204

    [ 216.055628] dhd_net_bus_devreset: dhd_bus_devreset: -35

    [ 216.055663] sdioh_disable_func_intr: error for read SDIO_CCCR_IENx : 0xffffff92

    [ 216.055668] wifi_platform_set_power = 0

    [ 216.055672] ======== PULL WL_REG_ON(-1) LOW! ========

    [ 216.055676] [WLAN_RFKILL]: rockchip_wifi_power: 0

    [ 216.055682] [WLAN_RFKILL]: wifi shut off power.

    [ 216.055686] wl_android_wifi_off out

    [ 216.055691] wl_ext_iapsta_dettach_netdev: Enter

    [ 216.055715] dhd_stop: Exit

    [ 216.055720] dhd_open : the lock is released.

    [ 216.055724] dhd_open: Exit ret=-1

    --snap

    greetings

  • Status of NanoPC-T4 (RK3399)

    Quote from balbes150

    Hi

    What is exactly the file you are using (copying) from the image Recalbox ? I need the full name of the DTB file used. If running Armbian happens, you can try to perform the initial configuration. If you took a desktop image, you need to log in to the console as "root" with the password 1234, change the password, create a new user, set the password and see if the graphical desktop shell will start.

    Hi balbes150,

    this answer comes from chromium on the NanoPC-T4.

    The desktop works up to 1920x1024x60Hz.

    I can have a look at your Test.mp4 and also have sound.

    I just can't get WiFi to work right away. I have to look at the logs again and get back to you.

    BTW: I also have access to the EMMC memory on which LE is installed.

    Greetings

  • Status of NanoPC-T4 (RK3399)

    Quote from balbes150

    Hi

    What is exactly the file you are using (copying) from the image Recalbox ? I need the full name of the DTB file used. If running Armbian happens, you can try to perform the initial configuration. If you took a desktop image, you need to log in to the console as "root" with the password 1234, change the password, create a new user, set the password and see if the graphical desktop shell will start.

    Hello balbes150,

    a moment, I used your image Armbian_5.96_Rk3399-tv_Debian_buster_default_4.4.154_20190913.img.xz, there is no X included.

    Just download Armbian_5.96_Rk3399-tv_Debian_buster_default_4.4.154_desktop_20190913.img.xz and continue testing.

    The Recalbox DTB is in the appendix.

    Many greetings

  • Status of NanoPC-T4 (RK3399)

    Quote from balbes150

    1. You can specify the name of the DTB file are you using from the image Recalbox ?

    2. You can perform a simple test of image is running Armbian

    https://yadi.sk/d/tpeis4lvlmgtvq

    (I'm interested in two things, will it work booting u-boot on a T4 and what DTB from the image Armbian will have better hardware support T4) ?

    Hello balbes150,

    I just tested your Buster image from https://yadi.sk/d/qgyvmkow5oqcha/2019090 with the DTB file for the NanoPC-T4 from Releases · recalbox/recalbox-os · GitHub Version 4.1.0.

    My NanoPC-T4 boots into a text console.

    Without a valid login I can't get any further here.

    Greetings

  • Status of NanoPC-T4 (RK3399)

    Quote from Aciel

    Yes, WiFi & Bluetooth both work flawlessly, using the above dtb.

    About eMMC, there is no support for it in Official images by LE. Internal Storage is not recognisable at all.

    Images by bybalbes150 do have eMMC support and you can install to it through LE Settings Menu.

    Thanks for the info...

    Because of the missing EMMC support I stay balbes150 Imgages ... even if no suitable AArch64 images are created at the moment.

    In combination with the DTB of RecalBox everything works fine, even if with an older image.

    Greetings

  • Status of NanoPC-T4 (RK3399)

    Hi Aciel,

    yes, you're right, the image files *.gz also contain DTBs and are exchanged.

    After that I always had the problem that I didn't have the EEMC entries (from balbes150) in the LE settings anymore and neither Bluethooth nor WLan works.

    Since balbes150 no longer created AARCH64 images, I also decided not to update. So I'm waiting for the change to the 5 kernel, where our NanoPC-T4 is directly supported.

    Since my configuration (except for the not always occurring problem with the aborts when watching TV in SD and HD) my LE installation runs stable.

    I only use LE to watch TV and movies over the EMBY plugin, because I have my own EMBY server with TVHeadend running on a QNAP for years.

    That runs sufficiently stable in this combination for me.

    I was already thinking about getting an ODROID N2, but I want to wait until I connect a new 4K TV to the LE (old TV causes its problems there) and hope that there will be stable images for the ODROIS N2 until then.

    Greetings

  • Status of NanoPC-T4 (RK3399)

    Hi Aciel,

    I can't recreate your problem.

    I use the following configuration:

    Code
    ##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################

LibreELEC (community): devel-20190606140016-a41fdf1 (RK3399.aarch64)

    I have this LE Image from @balbes150:

    Link to Balbes Images.

    With the extracted DTB from this Recalbox Version.

    All interfaces (also eth0) will be displayed:

    I'm sorry I can't help you with that.

    Greetings and good luck.

  • Status of NanoPC-T4 (RK3399)

    Quote from Aciel

    @JerryPenguin

    When you use Recalbox dtb on NanoPC-T4, is your ethernet working with the latest dtb from 3 June?

    I'm having caching issue on WiFi, so I thought I'll switch to ethernet. I plugged in my cable and disabled WiFi, but I got no Internet access and Kodi had no ethernet settings under LibreELEC Settings.

    I dropped in ssh and ran "ifconfig". There were only two interfaces wlan0 & lo, no eth0.

    Aciel,

    I can't reproduce the problem because I don't have a LAN on my NanoPC-T4 at the moment,

    but I will reproduce it in the next days and let you know.

  • Status of NanoPC-T4 (RK3399)

    Aciel:

    I used the following image of Kwiboo:

    libreelec-rk3399.arm-9.1-devel-20190512180245-bdfaff1-khadas-edge.img.gz

    with the nanopc-t4.dtb file from:

    http://http//kwiboo.libree…245-bdfaff1.tar

    As Kwiboo wrote under his posting, Wifi and BT so far only work on the tinkerboard.


    --snip

    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

    --snap

    So we still have to practice patience.