New ver 20200118 kernel 5.5 and 5.4
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.
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.
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=).
I can't boot generated images from balbes150 git repository and neither images generated from chewitt git sources in my A95X F2 S905x2.
Create a new thread with a description of your developments.
New image 20200109
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.
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.
New image 20191224
Fix start KODI to rk3328.
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.
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 ?
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)?
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)?
New version 20191219 for rk33xx based on kernel 5.5.
Added support for WiFi 6359\6398.
Update version 20191216 with kernel 5.5.
Added support for built-in WiFi. Please note, the site added a version of the file " u-boot.usb " to run the patch from USB media on the g12 platform. To use, you need to rename the file to " u-boot.ext".
So is there not a .img file lIBREeLEC for the M4 that is all complete and tested that is 9 yet? The one on Rockchip – LibreELEC PINE64 RockPro64
LibreELEC-RK3399.arm-9.2.0-rockpro64.img.gz won't load. I don't know why.
The legacy one PINE64 RockPro64 LibreELEC-RK3399.arm-8.90.015-rockpro64.img.gz works fine.
This image is for another model. Its launch before (without additional settings), you can consider a lucky coincidence. You can try changing the settings and check the startup to M4.
But I don't find any that are the LibreElec? Anyone know the right one to load?
There are several options for LE images that you may be able to run on try your M4. See this topic, earlier posts. There is information on how to configure and verify the launch of LE on the T4 (this principle is suitable for tuning and M4). There is no guarantee that this will work for you.
Can you check your build parameters? Maybe it is not possible to just build one image for all RK3399 boards and then handle the difference via the DTB. (but I am no expert).
The u-boot parameters in my build are correct (for the models I use). I am using a new u-boot with a set of new features that are not present in the old version of u-boot that you built. In theory, it is probably possible to build a new u-boot that will work on your model. But I don't have RockPro64 for such tests. RK startup principles cannot work with multiple u-boot variants at the same time. To work around this problem, you need to use the combined startup option (simultaneously using an SD card with the desired u-boot and necessarily without the system + the entire system on a USB drive). But for this option, you need to make changes to the u-boot sources that you used.