iMX7 WinCE8 Bring-up

I am just a newbe and so I followed strictly the article link text.

But, nothing happens. I connected the console interface via USB to my PC and I also set the Jumpers, but no reaction.
As there were two USB cables needed, I only see one additional Serial port, is this ok?
This Serial port is dead, no character written and no reaction on typed in characters. I use TeraTerm and I made a Connection to this USB port (here the only one, so no mistake possible)

I often use Serial links like that, so I have some skill with that Kind of Connections.

One of the steps is:
‘5.Your PC should now detect iMX7 module’ … what did this told me? I found a new USB Input module in my device Manager list, but how to Access?

Mybe I didn’t understand everything correct.

I use the Colibri Evaluation Board V3.2 and an iMX7 dual Colibri, the supplied cables (cable kit for this board), so nothing added from third Party.

Thanks for helping

With best regards


… ok, I pressed the reset button now and get this Output:

U-Boot 2016.11-1.6.0+gaca804c (Jun 19 2018 - 23:04:18 +0000)

CPU:   Freescale i.MX7D rev1.3 996 MHz (running at 792 MHz)
CPU:   Extended Commercial temperature grade (-20C to 105C) at 33C
Reset cause: POR
DRAM:  512 MiB
PMIC:  RN5T567 LSIVER=0x01 OTPVER=0x0d
NAND:  512 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX7 Dual 512MB V1.1D, Serial# 03139133
Net:   FEC0
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Booting Toradex Easy Installer...
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: 4057, bad PEBs: 7, 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: 1181184088
ubi0: available PEBs: 0, total reserved PEBs: 4057, PEBs reserved for bad PEB handling: 73
No size specified -> Using max size (21370672)
Read 21370672 bytes from volume rootfs to 82100000
## Loading kernel from FIT Image at 82100000 ...
   Using 'config@imx7d' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Linux Kernel 4.1
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x821000dc
     Data Size:    5308496 Bytes = 5.1 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x81000000
     Entry Point:  0x81000000
     Hash algo:    md5
     Hash value:   84b3a0850892b754269c3b6d0f1f391f
   Verifying Hash Integrity ... md5+ OK
## Loading ramdisk from FIT Image at 82100000 ...
   Using 'config@imx7d' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  SquashFS RAMdisk
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x82610214
     Data Size:    15925248 Bytes = 15.2 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    md5
     Hash value:   5feb1be46d6fd9f85c4560a4cd633494
   Verifying Hash Integrity ... md5+ OK
## Loading fdt from FIT Image at 82100000 ...
   Using 'config@imx7d' configuration
   Trying 'fdt@imx7d' fdt subimage
     Description:  Colibri iMX7 Dual Device Tree
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x8354afa4
     Data Size:    45356 Bytes = 44.3 KiB
     Architecture: ARM
     Hash algo:    md5
     Hash value:   76f76a539fc485372532ae7cbf683d5b
   Verifying Hash Integrity ... md5+ OK
   Booting using the fdt blob at 0x8354afa4
   Loading Kernel Image ... OK
   Loading Device Tree to 8fff1000, end 8ffff12b ... OK
   Updating MTD partitions...

Starting kernel ...

[    0.348375] gpmi-nand 33002000.gpmi-nand: mode:5 ,failed in set feature.
[    0.371522] imx_usb 30b10000.usb: Can't register ci_hdrc platform device, err=-517
[    0.702527] rtc-ds1307 3-0068: hctosys: unable to read the hardware clock
Running /etc/rc.local...

Welcome to 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 through any of the available display interfaces
using USB mouse/keyboard or via network using VNC. Use:
  # ip addr show eth0
to display the Ethernet IP address or use USB RNDIS at IP

/ #

Is this also ok, somesthing new or reading an old Version of the documentation …

Thanks for helping.

With best regards


Dear @Gerhard

Recovery Mode

Your first attempt “iMX7 WinCE8 Bring-up” can always be used, even if the software on the Colibri module is completely erased.

The last step you described was

5.Your PC should now detect iMX7 module

The new input device you saw in the device manager is exactly the expected behavior, so everything you did so far was correct.
You don’t need to access this device manually, but the next step

6.Start Recovery.bat inside the package, you downloaded from our website.

would use the new device to download and start the recovery software in the Colibri’s RAM.

But don’t do this now, because there is a simpler way to install WinCE8 on your system:

Toradex Easy Installer

The log output you sent in your comment prrofs, that the Toradex Easy Installer is running on your system. This is how we ship our latest modules by default.

Simply connect a few standard devices to the Colibri Evaluation Board:

  • a display (VGA / LCD)
  • a mouse
  • a network cable for Internet access

After a few seconds, you will see a selection of OS images to install, one of the options is the WEC2013 image.
Simply click on it and wait a few seconds until the installation has finished.

The Easy Installer provides more options to do the OS installation, I just described the simplest one. Refer to the Toradex Easy Installer documentation for more details.

Regards, Andy

Hi Andy,

Works great.

Some questions left …

After this procedure, I can move the iMX7 module from the eval board to my IRIS board and start developing?
I prefere headless Operation, cause my target System didnt offer any kbd/mouse/Display, so how can I use the GUI? I have heard the RNDIS is an Option, but I cant get any Connection using the Default address, even when I temporarely disabled the fire wall of my PC.

I also prefere fixed IP adresses to easily find my modul, is there any Chance to set the IP address?

With best regards


Hi @Gerhard
Thank you for the feedback.

You can move the Colibri module forth and back between the Iris and Evaluation board. During development it is often helpful to have a display and mouse connected, even though you don’t need it for your final device.
If you can connect your SPI device to the Evalboard (I assume you have an SPI device, according to your previous question), it might be easier to do the whole development on the Evaluation board, and possibly do some tests on the Iris after each major development step.

I created a new ticket for the IP question:

Regards, Andy

… ok.
With the command prompt on my device and ipconfig I get the address. I try to ping, works.
Than I started VS2015 und tried to use some remote Tools (remote file Viewer) just to see the Connection working, but … no Response.
I used the remote Tools on this PC with other products, no Problem.

Where to look into?

With best regards


Hi @Gerhard
I also created a new ticket for this question

Regards, Andy