Flashing iMX6ULL module

I am using a BSP 2.8b7, and I have flashed the iMX6S and VF50 modules using the IRIS carrier board with no troubles, and recently I got an iMX6ULL module to use as main CPU of a new product.

I created an image to it by uncomented the “colibri-imx6ull” machine in the “local.conf” file and commented all the others.

I generated a simple image using “bitbake console-tdx-image” command, and everything compiled ok.

Then, I extract the generated file “Colibri-iMX6ULL_Console-Image_2.8b7-20210512.tar.bz2” in the deploy folder.

And I used the command “./update.sh -o” to update the folder where my tftp server is serving the files, as I do with iMX6 and VF50 generated images. Below is the tftp folder structure:

    /tftp/imx6ull
    total 17K
    drwxrwx--- 1 root vboxsf 4,0K mai 13 00:49 ./
    drwxrwx--- 1 root vboxsf 4,0K mai 12 14:16 ../
    drwxrwx--- 1 root vboxsf 4,0K mai 13 00:49 colibri-imx6ull/
    -rwxrwx--- 1 root vboxsf  710 mai 13 00:49 flash_blk.img*
    -rwxrwx--- 1 root vboxsf  444 mai 13 00:49 flash_eth.img*
    
    /tftp/imx6ull/colibri-imx6ull/
    total 98M
    drwxrwx--- 1 root vboxsf 4,0K mai 13 00:49 ./
    drwxrwx--- 1 root vboxsf 4,0K mai 13 00:49 ../
    -rwxrwx--- 1 root vboxsf 1,4K mai 13 00:49 flash_blk.img*
    -rwxrwx--- 1 root vboxsf 1,3K mai 13 00:49 flash_eth.img*
    -rwxrwx--- 1 root vboxsf  38K mai 13 00:49 imx6ull-colibri-aster.dtb*
    -rwxrwx--- 1 root vboxsf  39K mai 13 00:49 imx6ull-colibri-eval-v3.dtb*
    -rwxrwx--- 1 root vboxsf  38K mai 13 00:49 imx6ull-colibri-wifi-aster.dtb*
    -rwxrwx--- 1 root vboxsf  39K mai 13 00:49 imx6ull-colibri-wifi-eval-v3.dtb*
    -rwxrwx--- 1 root vboxsf  92M mai 13 00:49 ubifs.img*
    -rwxrwx--- 1 root vboxsf 540K mai 13 00:49 u-boot-nand.imx*
    -rwxrwx--- 1 root vboxsf   72 mai 13 00:49 versions.txt*
    -rwxrwx--- 1 root vboxsf 5,3M mai 13 00:49 zImage*

Then I reset my iris board and stopped autoboot, then “run setupdate” and “run update” as I do with the others modules, but I got a message “Volume kernel not found!” at the end, as showing in the message below.

U-Boot 2016.11-2.8.7+g5c2d46b325 (May 12 2021 - 21:59:33 +0000)

CPU:   Freescale i.MX6ULL rev1.1 792 MHz (running at 396 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 53C
Reset cause: WDOG
DRAM:  512 MiB
NAND:  512 MiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

Video: 640x480x18
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX6ULL 512MB Wi-Fi / Bluetooth IT V1.1A, Serial# 06823048
Net:   FEC0
Hit any key to stop autoboot:  0
Colibri iMX6ULL # run setupdate
Card did not respond to voltage select!
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1:   USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
Using FEC0 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
Filename 'colibri-imx6ull/flash_eth.img'.
Load address: 0x82000000
Loading: ##################################################  1.3 KiB
         214.8 KiB/s
done
Bytes transferred = 1323 (52b hex)
## Executing script at 82000000
enter "run update" to update the entire module
Colibri iMX6ULL # run update
Using FEC0 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
Filename 'colibri-imx6ull/u-boot-nand.imx'.
Load address: 0x82100000
Loading: ##################################################  540 KiB
         8.9 MiB/s
done
Bytes transferred = 552960 (87000 hex)

NAND erase.part: device 0 offset 0x80000, size 0x180000
Erasing at 0x1e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x80000, size 0x87000
 552960 bytes written: OK

NAND erase.part: device 0 offset 0x200000, size 0x180000
Erasing at 0x360000 -- 100% complete.
OK

NAND write: device 0 offset 0x200000, size 0x87000
 552960 bytes written: OK
ubi0: default fastmap pool size: 200
ubi0: default fastmap WL pool size: 100
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=4", 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: 4056, bad PEBs: 8, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1018639178
ubi0: available PEBs: 0, total reserved PEBs: 4056, PEBs reserved for bad PEB handling: 72
Using FEC0 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
Filename 'colibri-imx6ull/zImage'.
Load address: 0x82100000
Loading: ##################################################  5.2 MiB
         9.1 MiB/s
done
Bytes transferred = 5463816 (535f08 hex)
Volume kernel not found!
Colibri iMX6ULL #

Why I’ve got this message when updating iMX6ULL?

I found out here that the iMX6ULL has no support to legacy update procedure using update.sh.

If that is true, so I need to update using Easy Installer by using a remote desktop as explained here.

I tryed it bu I can’t connect to Iris carrier board using TightVNC Viewer to ip 192.168.11.1.

Now I figure out that I had to connect my PC to the Iris board USB/OTG without OTG cable, e everything works fine, now I can install my custom images.
Thanks for all.

I could now flash the iMX6ULL using Toradex Easy Installer.

But I have been asked why we can’t use the way to flash as we do with iMX6S and VF50.

Can you tell me how can I use the old update.sh to flash the iMX6ULL ?

As the Colibri iMX6ULL was directly brought up with the Toradex Easy Installer installation method only there is no officially supported legacy update procedure available, sorry.