which nightly image for cubox

by-gnome · December 28, 2020 at 10:50 PM

I can confirm this working for Wandoards.

Code

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 ...

Display More

Code

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 ...

Display More

eTrax · December 29, 2020 at 10:48 AM

Hi there,

Cubox i2eXw is also working this way. Thanks.

At the moment I was still using an legacy OpenELEC 7 image (which was providing HW accelerated video playback) and was trying to get a running Armbian system with MESA HW acceleration on this small box. Two weeks ago I found these newer LibreELEC images and tried one. The image contained only one .dtb file, which didn't boot. The Armbian system used a v15-dtb, so I tried this one from the Kernel image-TAR - and now system is up and running.

To have only one image you should put all the .dtbs in one sub-directory and let the FDTDIR-tag point to this folder.

btw: Is there already a topic to discuss IMX.6 specific experiences, bugs etc. ?

**chewitt** · December 29, 2020 at 2:14 PM Official Post

Quote from eTrax

btw: Is there already a topic to discuss IMX.6 specific experiences, bugs etc. ?

Not really. We should probably create a forum section and let people start threads though.

**lrusak** · January 4, 2021 at 11:11 PM Official Post

Quote from vpeter

Seems I'm still the most knowledgeable man with i.MX6Q U-Boot

Want a cookie?

Why haven't you PR'd your changes yet?

**vpeter** · January 5, 2021 at 8:21 AM

Quote from lrusak

Why haven't you PR'd your changes yet?

Because you refused the changes I proposed on Slack. And I don't bother doing same thing twice.

Quote from lrusak

Want a cookie?

Yes please. Can I send you an address?

by-gnome · January 7, 2021 at 10:57 AM

May I do this PR?

**chewitt** · January 7, 2021 at 3:22 PM Official Post

As much as I like the simplicity and conformity of the extlinux arrangement vs. older "bootscript" approaches I am slso super keen on things that drive simplicity in the installation user experience, it's something that has always been a hallmark of LE/OE etc. and shipping 3x images or even 1x image instead of the current 6-8 rather weirdly named images could be a solid improvement.

I don't have any iMX6 hardware so I won't be able to test anything, but (speaking for myself) I'd like to see the PR.

**jernej** · January 7, 2021 at 6:25 PM Official Post

I would rather not change extlinux.conf approach exactly for simplicity reasons. As it was said before, FDTDIR is the way to go for multi-board support in single image with extlinux.conf.

**chewitt** · January 8, 2021 at 5:49 AM Official Post

I'm sure much was added since, but for reference on FDTDIR [U-Boot] [PATCH] pxe: implement fdtdir extlinux.conf tag

eTrax · January 10, 2021 at 5:57 PM

Took some time to setup a build machine, but here we are. I prepared a small change and added it as a PR for review.

eTrax · January 11, 2021 at 7:20 AM

Maybe we could discuss some of the remarks still in this topic and merge them to a solution:

- What is the preferred position to do the changes? Inside the NXP project (as by-gnome is using) or outside in the global scripts?

- dtb files should be placed in / folder beside the kernel file

- As both are using FDTDIR in extlinux.conf, maybe they both will require an additional patch of extlinux.conf during update, moving from a dl-/q-based image to the independent one?

- direct adressing of files is preferred instead of using wildcards (*cubox*.dtb)

As I shot forward maybe too quickly, I have no problems in recalling my PR for a better approach, just let me know.

**chewitt** · January 11, 2021 at 11:25 AM Official Post

Current "box" images use a "dtb" subfolder when there are a large number of dtb files (Amlogic has 30+ now) but I think when there are smaller numbers of files (cubox/udoo/wandboard are under 10x each) it's okay to keep them in the root folder. This also preserves backwards compat with currnent single-device images as although the content in new extlinux.conf will be difference (using FDTDIR) the file layout didn't change so the same update script we use with Amlogic will work fine for updating dtb (not dtbs).

Overall I prefer to keep the changes within the iMX6 project in the mkimage and release scripts as by-gnome has done. If we want to limit support to specific boards we need to be explicit in picking them by name. Otherwise there is precedent for *cubox* etc. since I do the same with Amlogic to add the dtbs for the SoC families we support only.

eTrax · January 17, 2021 at 2:54 PM

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... ?

by-gnome · January 17, 2021 at 9:37 PM

Quote from eTrax

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.

grisu127 · March 16, 2021 at 6:32 PM

I tested on my CuBox Pro i4x4 and can confirm that it's running smoothly.

Many thanks to all contributors

**chewitt** · March 17, 2021 at 4:29 AM Official Post

Seeking doesn't work .. I've been told something is missing from the hardware decoder (and the UAPIs for stateful decoders are still not finalised) but playback seems to work. I also have support for the Texas Instruments WiFi/BT in the newer Cubox-i version working and will push changes for that.

Saile · May 1, 2021 at 9:27 PM

Hi, I am super happy to hear that LibreElec 10 will also land on the Cubox-i! I already installed the nightly from 1.5.2021 and my first impression was: wow this is almost even faster. At second glance, however, some things did not work. For example, videos that I had recorded with the last working LibeElec version for Cubox-i were played in a wrong format and not synchronized with sound and video. And partly the playback was quite jerky. I read here that testers for the iMX6 platform are wanted: Upcoming changes – LibreELEC

I'm happy to help if you tell me what tests you need and what debug info.