Toradex Easy Installer Error on Apalis iMX6

I tried to install custom tezi image on Apalis iMX6Q IT 2GB module by ToradexEasyInstaller(v1.0-20170605). It printed error from console
U-Boot 2016.11-1.0.0+g0e9e31a (Jun 05 2017 - 16:38:56 -0700)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
Reset cause: WDOG
I2C:   ready
DRAM:  2 GiB
PMIC:  device id: 0x10, revision id: 0x21, programmed
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Using default environment

In:    serial_mxc
Out:   serial_mxc
Err:   serial_mxc
Model: Toradex Apalis iMX6 Quad 2GB IT V1.1B, Serial# 04958409
Serial Downloader recovery mode, using sdp command
Net:   using PHY at 7
FEC [PRIME]
Hit any key to stop autoboot:  0 
SDP: initialize...
SDP: handle requests...
Downloading file of size 20408300 to 0x12100000... EP0/out FAIL info=4018080 pg0=8df78500
ERROR: Unexpected report 4
at /build/ags/oe-core_tezi_morty/build/tmp-glibc/work/apalis_imx6-oe-linux-gnueabi/u-boot-toradex/2016.11-1.0.0-gitr0e9e31a/git/)
Downloading file of size 367 to 0x12000000... done
Jumping to header at 0x12000000
Header Tag is not a IMX image
## Loading kernel from FIT Image at 12100000 ...
Bad FIT kernel image format!
ERROR: can't get kernel image!

But on PC, it said it’s successful.

    ben@LinuxDev:~/Tezi/Apalis-iMX6_ToradexEasyInstaller_1.0-20170605$ ./recovery-linux.sh 
    Downloading Toradex Easy Installer...
    Successfully downloaded Toradex Easy Installer.

Do you what the problem is? Thanks very much!

okay. Finally as you suggested, it works on Windows. On Linux PC, it always fail with usb3.0/2.0 and usb hub. But for Apalis iMX6D 1GB IT V1.1B, the same Toradex Easy Installer is fine.
Thanks.

I tried to install custom tezi image on Apalis iMX6Q IT 2GB module by ToradexEasyInstaller(v1.0-20170605).

I guess at this stage there is nothing custom about any of this at all yet, right?


Downloading file of size 20408300 to 0x12100000… EP0/out FAIL info=4018080 pg0=8df78500
ERROR: Unexpected report 4

I believe we have seen this USB related issue before however do not have an immediate solution available. What may help is using a different USB host port of your Linux workstation or going through a USB hub vs. direct connection. Alternatively try a completely different machine maybe even a Windows one (;-p).