Colibri imx6 won't boot after flashing WEC7

My Colibri iMX6 came with Linux and I need to flash WEC7.
Found the instructions at:
[http://developer1.toradex.com/knowledge-base/apalis-imx6-wince-bring-up][1]

  • Downloaded and extracted imx6_wince_image_1.1.zip
  • Followed instructions to the letter.
  • The only issue I had was there were no instructions there on how to put the Coliibri into recovery mode, but I found that in the data sheet.
  • Everything went perfectly. The instructions are pretty clear. All responses from the system came back as expected.

However, after all that, the thing will not boot into WEC7. This is the serial output:

Toradex Bootloader 1.1 for Colibri Built Jan  9 2017
Splash screen is enabled.
Using 5MB of IPU memory and 32MB of GPU memory.
Board: Colibri iMX6 Solo 256MB
CPU is running at 984MHz.
Using eMMC boot partition (size: 4096 sectors).
Initializing L2 Cache.

Press [SPACE] to enter Bootloader Menu

Initiating image launch in 0 seconds.
System ready!
Preparing for download...
Loading compressed image...
Reading image from sector 40962.
Extracting 43432500 bytes from compressed image of 23844342 bytes
.........................................

Done.
Launching image at 10200000.

I get nothing on the monitor, and even though I’m new to the Toradex line, I kind of expected something else after “Launching image”.

I did the whole process a few times, also trying the WEC2013 edition that came with the download, but I alsways get the same result.

Does anyone have any suggestions on where to go from here?

Can you please try to enable additional debug messages from the OS by:

  • entering the bootloader console by pressing space and then X immediately after boot

  • typing:

    set dbg.serial 1
    save dbg
    
  • rebooting your device

This should give us a bit more information about what’s happening.
If you had previous beta releases you may also try to clear your registry (C option in the boot menu) before starting the OS.

P.S. we have instructions about the pads you have to shorten to enter recovery mode in the bring-up article, what do you feel it’s missing there? There are some steps that are not clear?

Thanks for the suggestions.

Clearing the registry had no visible effect: still no WEC7 boot.

Enabling debug shows the following:

Toradex Bootloader 1.1 for Colibri Built Jan  9 2017
Splash screen is enabled.
Using 5MB of IPU memory and 32MB of GPU memory.
Board: Colibri iMX6 Solo 256MB
CPU is running at 984MHz.
Using eMMC boot partition (size: 4096 sectors).
Initializing L2 Cache.

Press [SPACE] to enter Bootloader Menu

Initiating image launch in 0 seconds.
System ready!
Preparing for download...
Loading compressed image...
Reading image from sector 40962.
Extracting 43432500 bytes from compressed image of 23844342 bytes
.........................................

Done.
Launching image at 10200000.

IMAGE(CE7): 1.1
Colibri iMX6 Solo 256MB
SMP support disabled
PID:00400002 TID:00520002 Registry is empty.
PID:00400002 TID:01AF001A Multiplexing must be specified for non standard SPI po
rt.
PID:00400002 TID:01AF001A Port is used for OS debug!
PID:00400002 TID:01AF001A Waiting for flash disk \FlashDisk for 60 seconds
PID:00400002 TID:01AF001A Folder mounted
PID:00400002 TID:03250006 Ethernet: Auto-negotiation is on
PID:00400002 TID:01AF001A GALCORE 4.6.9(9754) (Oct  1 2013 11:00:31)
PID:00400002 TID:01AF001A Major GPU: SysIntr=32 MemBases=0x130000 MMU Version=0
PID:00400002 TID:01AF001A 2D GPU: SysIntr=33 MemBases=0x134000 MMU Version=0
PID:00400002 TID:01AF001A VG GPU: SysIntr=34 MemBases=0x2204000
PID:00400002 TID:01AF001A Video memory: BaseAddress=0x0 PhysBase=0x1ccc2000 size
=0x2000000 physSize=0x0
PID:00400002 TID:04920006 Maximum Allowed Error 5:
PID:05850012 TID:05870012 RTC reported oscillator failure
PID:05850012 TID:05870012 Invalid time on External RTC, please set a valid time
PID:05850012 TID:05870012 RTCSync: Completed.
PID:015C0036 TID:05AE0082 Loading NETUI...
PID:015C0036 TID:05AE0082 Done NETUI

And everything stops right there.

I noticed a couple of things regarding the RTC, but I’m not sure if those are show-stoppers.
Does this help?

This looks like a regular boot. It may be that the device is booting, but you can’t see anything on the screen.
What kind of display are you using?
Did you do a fresh install, switching from Linux or you already had a beta image running?
What kind of carrier board are you using?

"What kind of display are you using? "

It’s a 20" Dell flat-screen, can’t remember the model #, goes up to 1600x1200. I have a DVI-to-VGA adapter plugged in to the board and the VGA cable from here to the monitor.

"Did you do a fresh install, switching from Linux or you already had a beta image running?

The board came with some version of Linux on it. Booted up fine with that monitor but I had the DVI enabled for that (ribbon between Colibri and carrier).

“What kind of carrier board are you using?”

It’s an Iris v1.1A

BTW, do you know what the default VGA resolution is for the stock WEC7 installation? I wonder if it is something that the monitor cannot display. The Linux OS that came on my Colibri came up at 640x480, I think. At any rate it displayed fine on my Dell monitor.

Well I feel like a real putz. The monitor input was explicitly set to DVI (not autoscan or VGA) so of course it worked with the shipped Linux system over DVI.

I switched over to VGA for the WEC7 work, because I read that in the WinCE bring-up page: “Reboot your device and Windows CE will start configured for VGA output

However the monitor still has to be configured either to autoscan or VGA for this to work.

Thank you very much for your patience and help. Hopefully this answer might help some other noob in the future.

P.S. we have instructions about the pads you have to shorten to enter recovery mode in the bring-up article,

Yes you are correct. The pads are indeed shown for the Colibri board as well as the Apalis board. Sorry for the oversight.

Thank you for the update, we plan to support DVI in the new releases, so we will have the same behaviour on both versions.