amlg12
Error in this. This is for s905x2\s922 chips. You need amlgx (s905x\s912) or amlgxbb (recommended for s905).
For s905\s905x\s912, you only need to configure the DTB, and you don't need to add or change anything.
amlg12
Error in this. This is for s905x2\s922 chips. You need amlgx (s905x\s912) or amlgxbb (recommended for s905).
For s905\s905x\s912, you only need to configure the DTB, and you don't need to add or change anything.
But first I want backup these two boxes before I start playing around before I brick any of the box.
Creating a full eMMC backup is easy. Deploy the latest LE system from this theme (or Armbian) on any good media (SD card or USB media). The size of the media (SD card or USB flash drive) is selected depending on the EMMC data filling. For example, to create a full compressed copy of eMMC standard Android, media size of 8 GB is sufficient. Start the system on the TV box and in the LE settings menu, select work with eMMC and create a copy. The copy creation procedure starts, and the system shuts down automatically when it is complete. Depending on the parameters of the data size and speed of the media where the backup is being copied, the time may take approximately 5 to 40 minutes. After creating a copy, it is recommended to save the copy file in a safe place (PC, NAS, additional USB flash drive, etc.). The created copy file is located in the directory (/storage/backup/ddbr). When using Armbian with DE, the DDBR utility is used to create a copy (select the compressed copy option). Ease of using Armbian to create a copy, you can clearly see the entire process of creating a copy with progress indicators, and after creating a copy, you can immediately launch the browser from Armbian and place a copy on a shared resource. The copy in Armbian is located in the directory (/ddbr).
Update image 20200611 (all)
and 20200613-rk3288
The first test images for the RK3288 platform are available.
I checked the launch on Ugoos UM3, the main hardware is working (including WiFi). Plays 4K.
but are your images only for those who have modified u-boot files?
The images contain a u-boot, but it is intended for certain models. To run on other models, you need to add the correct u-boot after writing the image.
If i don't have them.. no chance to use your builds?
The working u-boot for other models can be obtained from any working image (LE or Armbian). The topic contains details on how to do this.
1. RK3328 Z28
This model needs its own u-boot.
Beelink gs1 (allwinner H6)
Images from this theme are intended for Rockchip. For Allwinner, there is its own version of images.
The Armbian image I used is Armbian_20.02.1_Rock64_buster_current_5.4.20.
This boots fine. Using the commands, you provided, I copied u-boot image and then wrote it to the sdcard that contains your libreelec. DTB has been configured to load the rock64.dtb.
If everything is done correctly, the system must necessarily show the start LE (primary screen with the LE logo). Which DTB do you use ? Show the content (uEnv.txt). Show all the commands that you use to copy and write u-boot.
Oh, just to be clear, you mean I can etch your LE to a thumbdrive and etch armbian to an sdcard. Insert both sdcard and the thumbdrive and I can boot LE? Thanks. Also I just saw that you added support to 4K TV. I will try that too. I've been connecting Rock64 to a 4K tv.
Edit1: So I tried the armbian in sdcard and your LE in a thumbdrive method. Rokc64 boots to armbian as before and asks for login information. It did not prompt boot options or anything. Is there a specific command or edits I should do?
Edit2: I also tried editing u-boot based on your helpful guide. All commands seemed to have worked fine. 17MB/16MiB sized img was created. But as before, no signal to the TV. Also, no LED activity as before.
What exact version of the Armbian image are you trying ? The official Armbian does not have the function of launching from USB media. The size of the u-boot image must not exceed 16Mb. After writing the LE image and add u-boot to SD card, you must configure the DTB used in the file (uEnv.txt).
Version 20200529.
Added support for video output to 4K TV (Tested on RockPi 4B).
and Armbian all work fine.
If you have ArmbianTV running, you can easily start LE from a USB drive. Write LE to USB, configure DTB, and connect an SD card with USB in place. Automatically start LE from USB.
can build his image with the changes mentioned by CvH here on this link
Sorry, I don't understand what you want to get ?
To All update 20200527 (fix amlgx)
Tried the rock64 build and made sure to change the uEnv to point to rock64 dtb but I get no signal from HDMI at all - just black screen. Is there anything else I need to do?
What image do you use ? You may also need to add u-boot to your SD card for your model.
These files are for the old 4.4 kernel. I don't work with it anymore.
Test images 20200524.
Good news. It seems that lrusak solved the problem of returning to KODI after playing a video for the AML platform.
Updated version 20200512.
Used by the kernel 5.7-rc5 + latest patches from Kwiboo
On models rk3399 running 4K decoding.
Added version 3328-old with simplified u-boot for older models.
GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI
This topic is about a different version. You need to refer to the leading maintainer of the RK platform in its theme.
Moderators, can you move these messages to the correct topic ?
Unfortunately, the freshly built image does not want to boot on my NanoPi M4 from SD card.
You can add a working u-boot separately. Write your image to the SD card and then write the u-boot image to the same SD card (you can download it from this link).