Colibri iMX8X V1.0B - TEZI

Technical Support
, , , ,
1

Hello, I am trying to update TEZI on my module.
I’ve tried prerelease (2.0b6 | 2020-11-02) and few nightly releases (246, 247, 248, 252).

In all of these recovery-windows.bat contains 2 uuu.exe commands:

recovery\uuu.exe -t 1 recovery\uuu.auto-v10b &
recovery\uuu.exe recovery

Is it correct? Should I pick just one?

I haven’t found any kind of description for these commands and it’s pretty ok for me for run tezi from USB boot and try to flash something at least. So this is just report that something may be wrong there.

After flashing TEZI, module is no responding. I am connected to LPUART3 on Iris V1.1B board and usually there is at least U-Boot output. After flashing version 2.0b6 or 2.0b7, there is nothing. I must boot via recovery mode again and install something different (at the moment using torzizon core for 1.0B WH).

2

Hi Martin,
I ran into similar problems - in short, I had to downgrade to Tezi 2.0b5:

Simon

3

Hi @slezak.martin,

Please use one of the latest Beta Releases of the Easy Installer for Colibri iM8X:
https://developer.toradex.com/software/toradex-easy-installer#beta-release

Then, after uncompressing the Easy Installer, use the script recovery-linux.sh for Linux or recovery-windows.bat for Windows, for loading it after putting the module in Recovery Mode based on your carrier board (Iris). Please leave the script to make all the work for you, you don’t have to deal with uuu by yourself.

Remembering to not have a USB Stick nor SD Card inserted in the module at the time of putting it in Recovery Mode, ok?

Then, in the Easy Installer loaded, install one of the available images on it (like TorizonCore 5.1.0).

Please, try this and let me know if it worked for you.

Best regards,
André Curvello

4

Hi @andrecurvello.tx,

that’s exactly what I did.

I just mentioned two uuu.exe commands in recover-windows.bat (recovery-linux.sh).
Only one of them will succeed - mostly the first one. I found that second one succeeds when I type reboot -F into CLI.

Installing TorizonCore 5.1.0 works well, installing Tezi leads to bricked module.

5

Hi @slezak.martin,

Were you able to install and use TorizonCore 5.1.0?

If so, with what version of Tezi?

Please confirm that, after loading Tezi, you receive a message like this:

Successfully downloaded Toradex Easy Installer.

But, let me help to understand your use-case:

  • Do you plan to “flash Tezi” on the module, or just use it under Recovery Mode to install another image?

Please, be aware that, for all of our iMX8 modules, only Tezi 2.0b6 is recommended.

Best regards,
André Curvello

6

When I use Tezi 2.0b6 in recovery mode on Iris 1.1B I got this:

2415-tezi-20b6-01.png
2415-tezi-20b6-01.png931×336 9.18 KB

In UART from Iris board:

U-Boot 2018.03-toradex_imx_v2018.03_4.14.98_2.3.0_bringup+g9393e0c9bd (May 19 2020 - 21:36:48 +0000)

CPU:   Freescale i.MX8QXP revB A35 at 1200 MHz at 29C
DRAM:  2 GiB
PMIC:  device id: 0x40, revision id: 0x20, emrev 0, prog id fff
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX8 QuadXPlus 2GB Wi-Fi / BT IT V1.0B, Serial# 06494192

 BuildInfo: 
  - SCFW b929edfe, SECO-FW f449a0d2, IMX-MKIMAGE d7f9440d, ATF bb209a0
  - U-Boot 2018.03-toradex_imx_v2018.03_4.14.98_2.3.0_bringup+g9393e0c9bd 

Detect USB boot. Will enter fastboot mode!
flash target is MMC:0
Net:   eth0: ethernet@5b040000 [PRIME]
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for 				 mfgtools
Run bootcmd_mfg: fastboot 0
Hit any key to stop autoboot:  0 
Detect USB boot. Will enter fastboot mode!
Starting download of 2246 bytes

downloading of 2246 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 37580496 bytes
..........................................................................
..........................................................................
..........................................................................
................................................................
downloading of 37580496 bytes finished
## Executing script at 82e00000
## Loading kernel from FIT Image at 83000000 ...
   Using 'config@freescale_fsl-imx8qxp-colibri-eval-v3.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x8300010c
     Data Size:    6689273 Bytes = 6.4 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80280000
     Entry Point:  0x80280000
     Hash algo:    sha1
     Hash value:   166f527127b4e212cc5a5d63376ae48c22628051
   Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 83000000 ...
   Using 'config@freescale_fsl-imx8qxp-colibri-eval-v3.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  tezi-initramfs
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x836c8534
     Data Size:    30466048 Bytes = 29.1 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0xa0000000
     Entry Point:  unavailable
     Hash algo:    sha1
     Hash value:   7170742b7e38e68cc7331eb019e5de4c28ce538d
   Verifying Hash Integrity ... sha1+ OK
   Loading ramdisk from 0x836c8534 to 0xa0000000
## Loading fdt from FIT Image at 83000000 ...
   Using 'config@freescale_fsl-imx8qxp-colibri-eval-v3.dtb' configuration
   Trying 'fdt@freescale_fsl-imx8qxp-colibri-eval-v3.dtb' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x83661428
     Data Size:    84042 Bytes = 82.1 KiB
     Architecture: AArch64
     Hash algo:    sha1
     Hash value:   5075a816962b48701bdee4ded29c65b247579a06
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x83661428
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 00000000fd663000, end 00000000fd67a849 ... OK
/dma-controller@591F0000, 64852
/dma-controller@599F0000, 65816
/dma-controller@5a1f0000, 63900
/dma-controller@5a1f0000, 63900

Starting kernel ...

[    0.350188] dmi: Firmware registration failed.
[    0.773192] Can't support > 32 bit dma.
Running /etc/rc.local...
TDX_VER_ID="Colibri-iMX8X_ToradexEasyInstaller_2.0b6-20201102"
Starting udev
System time was Wed Nov 18 13:55:35 UTC 2020.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Wed Nov 18 13:55:35 UTC 2020.

Welcome to the Toradex Easy Installer

This is a Linux based installer for Toradex modules. Currently, the installer
does not have a serial console interface. You can use the Toradex Easy Installer
via any of the available display interfaces using USB mouse/keyboard or via a
network connection using VNC. Use:
  # ip addr show eth0
to display the Ethernet IP address or use USB RNDIS at IP 192.168.11.1.

Check our documentation at:
  https://developer.toradex.com/software/toradex-easy-installer
/ #

I can’t connect to VNC server but I figured out how to install Tezi (or other image) from CLI.

/usr/bin/tezictl image-list
Currently available images:

[0]	TorizonCore with evaluation containers for V1.0C HW
	Version: 5.1.0-devel-202011+build.4.container (2020-11-06)
	URI: http://tezi.toradex.com/artifactory/torizoncore-oe-prod-frankfurt/dunfell-5.x.y/monthly/4/colibri-imx8x/torizon/torizon-core-docker-evaluation/teziimage/
[1]	TorizonCore with evaluation containers for V1.0B HW
	Version: 5.1.0-devel-202011+build.4.container (2020-11-06)
	URI: http://tezi.toradex.com/artifactory/torizoncore-oe-prod-frankfurt/dunfell-5.x.y/monthly/4/colibri-imx8x-v10b/torizon/torizon-core-docker-evaluation/teziimage/
[2]	TorizonCore for V1.0B HW
	Version: 5.1.0-devel-202011+build.4 (2020-11-06)
	URI: http://tezi.toradex.com/artifactory/torizoncore-oe-prod-frankfurt/dunfell-5.x.y/monthly/4/colibri-imx8x-v10b/torizon/torizon-core-docker/teziimage/
[3]	TorizonCore for V1.0C HW
	Version: 5.1.0-devel-202011+build.4 (2020-11-06)
	URI: http://tezi.toradex.com/artifactory/torizoncore-oe-prod-frankfurt/dunfell-5.x.y/monthly/4/colibri-imx8x/torizon/torizon-core-docker/teziimage/
[4]	Toradex Easy Installer
	Version: 2.0b6 (20201102)
	URI: http://tezi.toradex.com/artifactory/tezi-oe-prod-frankfurt/thud/release/2/colibri-imx8x/tezi/tezi-run/teziimage/
[5]	Toradex Embedded Linux Reference Minimal Image for V1.0B HW
	Version: 5.0.0+build.3 (2020-10-06)
	URI: http://tezi.toradex.com/artifactory/tdxref-oe-prod-frankfurt/dunfell-5.x.y/release/3/colibri-imx8x-v10b/tdx-xwayland/tdx-reference-minimal-image/teziimage/Colibri-iMX8X-V10B_Reference-Minimal-Image-Tezi_5.0.0+build.3/
[6]	Toradex Embedded Linux Reference Multimedia Image for V1.0B HW
	Version: 5.0.0+build.3 (2020-10-06)
	URI: http://tezi.toradex.com/artifactory/tdxref-oe-prod-frankfurt/dunfell-5.x.y/release/3/colibri-imx8x-v10b/tdx-xwayland/tdx-reference-multimedia-image/teziimage/Colibri-iMX8X-V10B_Reference-Multimedia-Image-Tezi_5.0.0+build.3/
[7]	Toradex Embedded Linux Reference Minimal Image
	Version: 5.0.0+build.3 (2020-10-06)
	URI: http://tezi.toradex.com/artifactory/tdxref-oe-prod-frankfurt/dunfell-5.x.y/release/3/colibri-imx8x/tdx-xwayland/tdx-reference-minimal-image/teziimage/Colibri-iMX8X_Reference-Minimal-Image-Tezi_5.0.0+build.3/
[8]	Toradex Embedded Linux Reference Multimedia Image
	Version: 5.0.0+build.3 (2020-10-06)
	URI: http://tezi.toradex.com/artifactory/tdxref-oe-prod-frankfurt/dunfell-5.x.y/release/3/colibri-imx8x/tdx-xwayland/tdx-reference-multimedia-image/teziimage/Colibri-iMX8X_Reference-Multimedia-Image-Tezi_5.0.0+build.3/
[9]	Qt for Device Creation Demo Image
	Version: Qt 5.15.1 (2020-09-07)
	URI: http://tezi.toradex.com/artifactory/legacy-oe-3rdpartyprod-frankfurt/b2qt-embedded-qt5-image-colibri-imx8x-20200907064801-Tezi_3.0.3/
[10]	Kynetics Android Pie for Colibri iMX8QXP V1.0B
	Version: 1.0-SNAPSHOT-20190823 (20190829)
	URI: http://tezi.toradex.com/artifactory/legacy-oe-3rdpartyprod-frankfurt/Colibri-iMX8QXP_V1.0B_Kynetics-Android-Image_9.0.0_2.0.1-eval-1.0-SNAPSHOT-20190823/
/ # /usr/bin/tezictl image-install 4
Image installation started, please wait...
Success: Image installation finished!

/ # reboot -f
[ 687.873244] reboot: Restarting system

U-Boot 2018.03-toradex_imx_v2018.03_4.14.98_2.3.0_bringup+g9393e0c9bd (May 19 2020 - 21:36:48 +0000)

CPU: Freescale i.MX8QXP revB A35 at 1200 MHz at 56C
DRAM: 2 GiB
PMIC: device id: 0x40, revision id: 0x20, emrev 0, prog id fff
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC… *** Warning - bad CRC, using default environment

Failed (-5)
In: serial
Out: serial
Err: serial
Model: Toradex Colibri iMX8 QuadXPlus 2GB Wi-Fi / BT IT V1.0B, Serial# 06494192

BuildInfo:

  • SCFW b929edfe, SECO-FW f449a0d2, IMX-MKIMAGE d7f9440d, ATF bb209a0
  • U-Boot 2018.03-toradex_imx_v2018.03_4.14.98_2.3.0_bringup+g9393e0c9bd

Detect USB boot. Will enter fastboot mode!
Net: eth0: ethernet@5b040000 [PRIME]
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: fastboot 0
Hit any key to stop autoboot: 0

[Hangs]

Then I turn off/on power and nothing appears on UART.

To answer Your questiions, yes, I am able to isntall TorizonCore 5.1.0 from CLI (tezi v 2.0b6 as just desribed) or even via VNC with newer versions from night builds.

I do not need to install Tezi or Use TorizonCore (at least at the moment), just bumped on this behavior and wanted to make some feedback.

7

Hi @slezak.martin,

Well, the most important thing is that your module is fine and you are able to install and use TorizonCore 5.1.0.

But then, let us discuss your issue with Recovery Mode.

Are you using your USB OTG connection to the carrier board through a USB Hub?

If so, I recommend you to directly connect it to your computer. We have known a lot of cases similar to what you have shown in your picture, mostly because of the usage of a USB Hub.

And, is this happening even with the latest nightly builds of Easy Installer?

The recommended way of using Easy Installer is through its graphical interface, by either connecting it directly to a display or by using the VNC as you tried.

The VNC does not work even by the Ethernet port and the USB RNDIS connection through USB OTG?

If you are using Windows, please try accessing the VNC using TightVNC.

Best regards,

André Curvello