I merged all suggestions in the @by-gnome proposed project files in a new branch.
I also prepared a solution for the NXP/imx6 update.sh script.
How to proceed? Would you like to review the other files in advance, should I close this PR and start a new one based on the other branch or... ?
You can force push your changes in the same branch and PR will be automaticaly updated.
May I do this PR?
I can confirm this working for Wandoards.
U-Boot SPL 2020.10 (Dec 24 2020 - 16:39:31 +0300)
Trying to boot from MMC1
U-Boot 2020.10 (Dec 24 2020 - 16:39:31 +0300)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
DRAM: 2 GiB
MMC: FSL_SDHC: 2, FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
auto-detected panel HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Board: Wandboard rev C1
Net: eth0: ethernet@2188000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
155 bytes read in 22 ms (6.8 KiB/s)
1: LibreELEC
Retrieving file: /KERNEL
11952312 bytes read in 577 ms (19.8 MiB/s)
append: boot=UUID=2412-2405 disk=UUID=ec6a72f4-0c79-4e48-b2b1-ac2c0b29b80d console=ttymxc0,115200 console=tty0
Retrieving file: /imx6q-wandboard.dtb
37561 bytes read in 19 ms (1.9 MiB/s)
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800c2b8
Starting kernel ...U-Boot SPL 2020.10 (Dec 24 2020 - 16:39:31 +0300)
Trying to boot from MMC1
U-Boot 2020.10 (Dec 24 2020 - 16:39:31 +0300)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
DRAM: 2 GiB
MMC: FSL_SDHC: 2, FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
auto-detected panel HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Board: Wandboard rev B1
Net: eth0: ethernet@2188000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
155 bytes read in 21 ms (6.8 KiB/s)
1: LibreELEC
Retrieving file: /KERNEL
11952312 bytes read in 577 ms (19.8 MiB/s)
append: boot=UUID=2412-2405 disk=UUID=ec6a72f4-0c79-4e48-b2b1-ac2c0b29b80d console=ttymxc0,115200 console=tty0
Retrieving file: /imx6q-wandboard-revb1.dtb
37559 bytes read in 19 ms (1.9 MiB/s)
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800c2b6
Starting kernel ...But the script files are used by the Amlogic project and it looks like it works.
LibreELEC.tv/boot.scr.src at master · LibreELEC/LibreELEC.tv · GitHub
Now i am testing the same for iMX6 in Lakka-LibreELEC... and to be honest, I see only one obstacle to doing this in LibreELEC - your unshakable opinion.
I guess we can boot all iMX6 targets with one image using boot.scr
I tried this with Wandboard B1 and C1 and it works.
The script I used:
setenv image "/KERNEL"
setenv bootargs "boot=UUID=2511-1511 disk=UUID=3a00fe1a-8c24-42fd-83ae-69c4a2043aa0 quiet console=ttymxc0,115200"
load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} ${image}
load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${fdtfile}
bootz ${kernel_addr_r} - ${fdt_addr_r}