AMLGX
supports the following 64-bit SoCs:AMLMX
supports the following 32-bit SoCs:AMLGX
and AMLMX
provide a "box" image for use with devices that run Amlogic (aka Vendor or Legacy) boot firmware (U-Boot 2015.01 with Amlogic and manufacturer customisations) and "board" images using modern boot firmware (mainline U-Boot) specific to a single SBC board or STB device. The image type can be identified by the filename -suffix
:LibreELEC-AMLGX.arm-10.0.0-box.img.gz
is the AMLGX
"box" imageLibreELEC-AMLGX-arm-10.0.0-khadas-vim3.img.gz
is a "board" image for VIM3LibreELEC-AMLMX-arm-10.0.0-box.img.gz
is a "box" image for Meson 8 devicesbox
images can be used on many devices you must configure the device-tree file to use first. This is done by editing uEnv.ini
in the root folder of the SD card. Change @@[email protected]@
to the name of the .dtb file to use. Current supported device-tree files are in the dtb
folder.uEnv.ini
file:@@DTB_NAME
to meson-g12b-gtking.dtb
board
image to eMMC (overwriting Android or other factory-installed images).install2internal
script to reconfigure the factory boot process and run LibreELEC from the internal eMMC storage. In the past when most box devices had 1GB RAM and SD cards were slow the performance difference between an SD card and "internal" storage was substantial, so the script evolved a cult following and many users belive they must install to internal eMMC or their box will be unusuable. This is wrong advice. On modern boxes with faster CPUs, 2GB+ RAM and better SD card support, the performance difference is often marginal.install2internal
script and something messes up; your problem is not our problem!AMLGX
image there is an eMMC helper script called emmctool
that supports a range of useful functions for backup/write/erase (and more) for eMMC storage. See:emmctool
helper supports a limited range of SBC boards with eMMC modules. On a generic Android device it will output the (i) info only.