Current TorizonCore on Colibri iMX6ULL

Dear all,

We have just started development of a new application based on the iMX6ULL.
I’d like to inquire whether this SoM is still supported in TorizonCore since the latest nightly build image does not boot, probably due to the usage of NAND memory instead of eMMC.

This is the image I’ve flashed through TEZI:

And here’s the output on the UART console after rebooting:

NAND:  512 MiB
Loading Environment from NAND... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX6ULL 512MB Wi-Fi / Bluetooth V1.1A, Serial# 06487293
Net:   Could not get PHY for FEC1: addr 2
eth-1: ethernet@020b4000
Hit any key to stop autoboot:  0 
ubi0: default fastmap pool size: 200
ubi0: default fastmap WL pool size: 100
ubi0: attaching mtd5
ubi0: scanning is finished
ubi0: attached mtd5 (name "ubi", size 508 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 4057, bad PEBs: 7, corrupted PEBs: 0
ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 7/3, WL threshold: 4096, image sequence number: 704326309
ubi0: available PEBs: 0, total reserved PEBs: 4057, PEBs reserved for bad PEB handling: 73
Scanning ubi 0:...
Found U-Boot script /boot.scr
2417 bytes read in 3 ms (786.1 KiB/s)
## Executing script at 87000000
422 bytes read in 37 ms (10.7 KiB/s)
42124 bytes read in 60 ms (685.5 KiB/s)
7598592 bytes read in 6740 ms (1.1 MiB/s)
3257417 bytes read in 2926 ms (1.1 MiB/s)
Kernel image @ 0x81000000 [ 0x000000 - 0x73f200 ]
## Flattened Device Tree blob at 82100000
   Booting using the fdt blob at 0x82100000
   Using Device Tree in place at 82100000, end 8210d48b
   Updating MTD partitions...

Starting kernel ...

[    2.583618] UBI error: cannot open mtd UBI, error -2
[    2.591734] rtc-ds1307 0-0068: hctosys: unable to read the hardware clock
Starting version 243+
root '/dev/ubi0_1' doesn't exist or does not contain a /dev.

After this, the bootup would hang indefinitely.
The same applies for an image I built with the provided Docker container.

Interestingly enough, an older TorizonCore image boots just fine:

Any suggestions what I might be doing wrong are welcome!

Thanks in advance!

Greetings @George,

Currently the i.MX6ULL is experimentally supported on TorizonCore. This means that while we continue to perform nightly builds for this SoM, these builds are usually not tested and any issues with this SoM on TorizonCore are not a very high priority to be fixed.

The reasoning for this decision is that using containers (the main selling point behind Torizon) can lead to some bottle-necking situations on the i.MX6ULL due to the relatively low amount of RAM and flash. That being said the i.MX6ULL will continue to be fully supported by our non-Torizon linux BSP.

However we at Toradex are still curious to hear about customers who wish to use Torizon on non-officially supported SoMs. So if I may ask, what kind of project are you planning to do on the i.MX6ULL with Torizon, and what unique features of Torizon are you trying to leverage?

Best Regards,