On the Apalis Txx / Colibri Txx, the shared USB Client/Host port can be used to download a new OS image. This is only required if the Bootloader doesn't boot anymore. If your module still boots, you can use the Update Tool (Only for Windows CE at the moment).

When the Apalis/Colibri Txx module enters the recovery mode, it will be available as an USB device in the device manager.
Please connect the client port of the carrier board with your development PC. Depending on the carrier board you need a different cable. Toradex' standard base boards utilize different USB Client Port connectors (Type B, Mini B, Micro B).

If you have successfully entered the recovery mode the Module will show up as APX device on your development PC. You can now install the APX drivers. The driver is part of NVFlash / Recovery mode package.

Note: Earlier NVFlash and batch script were already in the image download package. Do not use them any longer.

If you are using the recovery mode for the first time open 'Control Panel' -> Select drop-down box adjacent to 'View by:' and select 'Small icons' -> Click 'Device Manager' in your PC and you should be able to see APX. Refer to the picture below:

Open the NVFlash / Recovery Toolset folder. Refer to the picture below:

Double-click update.bat. You are asked to select the *.cfg file according to the Windows CE version you want to flash. Locate the *.cfg in the Image you downloaded before.

This will delete all data on the module, including registry, flash file system and config block.
The module's hardware revision and serial number (mac address) are automatically backed up and finally restored as part of the process.

Once the image gets successfully flashed you will get the following messages (shown for WinCE7 on Colibri T20).

Execute the update.sh shell script as contained in the Embedded Linux demo image packages with the -d (debug parameter) to download U-Boot directly into RAM. On the Colibri T20, additional parameters are required to specify the module type/version: '-r 512' for 512 MB RAM modules and '-v V1_1' for V1.1B or V1.1C modules.
Then, after inserting a prepared SD/microSD card (as populated with './update.sh -o <path to card>'), the actual flashing can be initiated on the serial debug console using the 'run setupdate; run update' commands.

USB_DET needs to be very close to 3.3V when entering the Recovery Mode. Typically a voltage divider is implemented on these pins. We saw on some customer boards with high impedance voltage dividers that the recovery mode was not working. In these cases, the update utility will display this message and the system will stall:

Do you like to program Windows CE 6 or CE 7?
"Choose 6 or 7"
7
Nvflash version unknown started
rcm version 0X20001

To fix this problem you need to connect the pin to 3.3V while in Recovery Mode.

If USB client detection remains an issue even after updating Windows CE, the voltage divider has to be patched with lower resistance resistors.