Posts by balbes150

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

    Quote from rua1

    v20200211 on SDcard as is (only replace config to rk3399-rock-pi-4.dtb)

    Did I understand correctly that you didn't add a u-boot to the SD card and the system started with the current u-boot ?


    Quote from rua1

    p.s. with fdt others versions strings "pci" and "nvme" in dmesg are missing

    Use the latest versions, where NVMe is defined on RockPI4b.


    Quote from Patkino

    Which dtb do I have to use for h96 max rk3399 box?

    I don't have such equipment, I don't test it.


    Quote from Patkino

    Install2emmc script no longer works.

    The image contains incorrect scripts. This has been fixed in the new images.

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

    Quote from casper007

    Everytime when nanopi reboot, MAC adress is different, then IP is different (Manual settings does not work)

    Add to the settings file (uEnv.txt) in the string parameter APPEND "mac=your_address".


    Quote from casper007

    With 9.2.0 image

    This version uses the old core 4, in my images the new core 5. In the new kernel, functions have just started to be added, not everything will work.


    Quote from rua1

    Now, if I use fdt file from version 20200201, nvme is mounted after mounting STORAGE and run kodi. I can use mount -o bind to the some directories.

    If you create a partition on NVMe (ext4) and assign a label to It, you can immediately in the config file (uEnv.txt) specify (instead of the STORAGE label) this label to automatically use NVMe as the primary device for data in LE.

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

    Quote from rua1

    I'm test LibreELEC-RK.arm-9.80-devel-20200127120222-6e9040d-rk3399.img on rock pi. Not boot. On screen message after kernel boot "Could not mount flash/SYSTEM".

    I'm make extlinux.conf and boot with radxa uboot. On screen message: Not found boot=LABEL.... . Replace to boot=/dev/mmcblk0p9 ... not found ...ha ... it place on /dev/mmcblk1p9 , emmc on mmcblk2 , nvme not found. This kernel only for khadas?

    According to the description, you are not running the system correctly. What media is used ? What settings do you make for DTB ? What "internal" media is connected (eMMC NVMe)? What is in SPI ?

    If setting is correct , the LE can be run without problems on RockPI 4.

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

    The new version 20200116.

    Please note that the DTB configuration order has changed. now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB. The system installation script in eMMC has changed accordingly. If you have a kernel 5 system installed in eMMC, it is advisable to perform a clean installation in eMMC to upgrade to the new version.

  • @balbes150 LE images with Kodi-19 for S9xxx

    The new test version of the LE 20200115.

    Added installation in eMMC for the G12 platform along with color correction. For this function to work correctly, you need to update the universal multi-upload (a similar new version of multi-upload will now be used in Armbian >=19.11.5).

    Before installing to eMMC, be sure to make a full backup of the entire eMMC.


    Pay attention.

    The DTB configuration algorithm has changed. Now a single file (uEnv.txt) will be used for all versions of my images for Rockchip (rk33xx) Allwinner H6 Amlogic s9xxx platforms. The principle of setting is the same - you need to correctly specify the name of the dtb used in the string (FDT=).

  • @balbes150 LE images with Kodi-19 for S9xxx

    Quote from steved

    I just installed image 20200108 on my VIM2 Pro, installation and everything works fine, but video playback only shows a green screen. I guess its the video acceleration.

    Currently I test this with an RTSP stream over IPTV Simple Client. The log says the following Log

    Even though the 'InputStream Client for RTMP Streams' is installed, is says ' unsupported protocol(RTSP)'.

    The green screen problem and the log message might be unrelated, since local media files won't work neither.

    Is this already a known problem?

    I saw this behavior (no video works) right after the initial setup wizard. For me it helps to restart the system. I haven't figured out yet why the video doesn't work on the first run.

  • Tanix TX6

    Test version (20200108) with support for installing LE in eMMC. :)

    Tested on Tanix TX6. Before installing, be sure to make and save a full backup of eMMC (for this purpose, the system has a special item in the LE settings menu). The process of creating a full copy can take up to 20-30 minutes (depending on the SD card and filling eMMC data). After that, you can try running the installation in eMMC. Perhaps the first time you install the system will not be installed completely, you need to re-boot from the SD card and once again run the menu item install in eMMC. After completing the installation procedure, the system should automatically shut down. You need to turn off the power supplies and pull out the SD card. The first time you start the system, you will be asked to perform the initial system setup. Please note, this is the first test version of the installation in eMMC and possible side problems.

  • Tanix TX6

    Quote from jernej

    Not sure what you mean exactly. U-Boot has search procedure for extlinux.conf stored in environment variables. This is the same for all platforms, not only Allwinner. You can change them at runtime with setenv and store them with saveenv.

    Still, having system on USB dongle and having U-Boot on SD card is very inconvenient for the end user.

    USB startup support is needed primarily for those who use LE and Armbain from eMMC or on SD card and want to help quickly test new versions, but do not have free SD cards. USB flash drives are much easier to use (you do not need a card reader on your PC to write) and significantly cheaper than SD cards. Many have old USB flash drives that they can easily use to run and test any system (no need to change the SD card in the device, plug in the USB flash drive and test). :)


    I think I found where to make patches for u-boot. Now I will test at myself. :)

  • Tanix TX6

    Quote from jernej

    No, main issue is RAM initialization. For example, Tanix TX6 has DDR3 and most or all SBCs have LPDDR3. Due to tight size constraint in SPL there is place for only one RAM driver.

    Then I'll rephrase the question. :)

    What is the minimum number of u-boot options will be enough to run the system on different h6 models ?

    1 for DDR3, 2 for LPDDR3 ?

    Quote from jernej

    I'm not sure in what state U-Boot H6 USB driver is, I don't use it. U-Boot itself can't start from USB dongle (only SD card, eMMC, SPI and NAND), but it can start Linux from USB.

    For my purposes, the option to support starting from USB when it is in SD\eMMC\SPI is quite enough (change the order of polling devices by making USB first). Similar I already did for RK33xx, it allowed to have universal images of LE and Armbian which can be run on all devices, it is enough to configure DTB in (extlinux.conf). You can tell in which source files there are parameters that are responsible for the order of polling devices, where to look (extlinux.conf)?

  • Tanix TX6

    jernej great job.

    On the basis of your sources, I built a version of LE with the addition of support for USB WiFi, USB BT, USB sound (sometimes it is more convenient to use external sound devices with much better parameters than built-in sound). All these devices work well on TX6. :)

    The question. U-boot versions for different H6 models are very different from each other, is it possible to have a universal version that will be able to run on all models ? Is it possible in u-boot for H6 to work with USB (start the system from USB media)?