Search by Tags

Txx Recovery Mode

 

Compare with Revision




Subscribe for this article updates

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).

Instructions are also available as video. Check our reprogramming guide.

To successfully flash a new image you need to do the following:

Enter recovery mode

In order to flash a new image into an Apalis/Colibri Txx module you first need to put the module into recovery mode.

Using Windows CE

Type the following commands in the Bootloader Menu to enter into recovery mode:

x
reboot rcm

Using Linux

If your module runs the Embedded Linux BSP LinuxImageV2.0Beta1_20121218 or later stop at the U-Boot prompt and use the U-Boot command enterrcm.

U-Boot 2011.06-00002-gcb354a4 (Dec 27 2012 - 19:09:27)
...
Hit any key to stop autoboot:  0
Tegra2 # enterrcm
Entering RCM...

Iris Carrier Board 1.1A:

  1. Connect USB micro B to the X12 connector on the Iris board and USB A to your PC.

  2. To enter recovery mode short the pad 1 and 2 of the JP1 on Iris using a wire.

    Refer to the picture below:


  3. Power up the Iris board.

  4. Remove the wire.

Colibri Evaluation Board 3.1A

  1. Connect USB Standard B or Micro B to the X29 or X30 respectively on the Eval board and USB A to your PC.

  2. Power on the Eval board.

  3. Press and keep pressed (or hold) the recovery mode button SW9 and immediately press and release the reset button SW8 on the Eval board.

  4. After 2-5 seconds, release the recovery mode button SW9.

Directly on Txx module

Colibri T20 module

Connect the 2 pads as shown in the picture (this works best with a pair of tweezers) and then power on the system or perform a hardware reset


Colibri T30 module

Please have a look at the datasheet of the Colibri T30 in the recovery mode section.

Apalis T30 module

Connect the 2 pads as shown in the picture (this works best with a pair of tweezers) and then power on the system or perform a hardware reset


For more information have a look at the datasheet of the Apalis T30 in the recovery mode section.

Apalis TK1 module

Please have a look at the datasheet of the Apalis TK1 in the recovery mode section.

Connect the Module to your Development PC

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).

Colibri Familiy

Colibri Evalboard, Orchid, Protea

Use a USB A to USB B cable. (e.g Evaluation Board V3.1A connector X29)


  • USB A to USB B cable

    USB A to USB B cable

Iris

Use a USB A to micro B cable.


  • USB A to micro B cable

    USB A to micro B cable

Important: The Recovery Mode only works with USB 2.0 High Speed (480Mbps).

The Iris Carrier Board and the Evaluation Board V3.1A are the only Toradex Colibri carrier boards which support USB 2.0 High Speed (480Mbps) by default.

If your carrier board is not USB 2.0 High Speed compatible you will need to use one of the following ways in order to enter recovery mode:

  • Patch the board like we describe it here
  • Use a full speed only USB Hub
  • Disable the High Speed mode (EHCI driver) on your development PC. If you are a Linux user have a look here

Apalis Family

Apalis Evaluation Board

Use a USB A to USB B cable (X50) or a USB A to Micro USB B cable (X49)

Ixora

Use a USB A to micro B cable (X9).

Note: JP2 must not be populated in order to configure X9 as the USB Client port.

Flashing OS image on Colibri Txx module

Flashing WinCE Image

Updating recovery driver

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.

This driver works on 32-bit and 64-bit Windows systems.

Before you start download all the required tools and files:

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

  1. 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:


  2. Double-click APX and click Driver tab then Click Update Driver. Refer to the picture below:


  3. Choose Browse my computer for driver software. Refer to the picture below:


  4. Locate and click usbpc_driver_32_64 folder inside NVFlash / Recovery mode package. Refer to the picture below:


Note: If you get a warning about a unsigned driver, make sure you download the latest signed NVFlash driver (At least nvflash 2.1 868 of the NVFlash / Recovery Toolset).

  1. Upon successful driver installation you will get the following message box. Click Close to close message box. Refer the picture below:


Verify recovery mode

  1. In order to verify if the recovery driver is properly loaded open Control Panel->Device Manager.

  2. In Device Manager, you can confirm the successful driver installation by verifying NVIDIA USB Boot-recovery driver for Mobile devices under Universal Serial Bus controllers. Refer to the picture below:


Updating WinCE images

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


  2. 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.

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


Flashing Embedded Linux Image

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.

Further details can be found in the Flashing Embedded Linux to Tegra Modules article.

Possible Issue: USB_DET Pin (SODIMM Pin 137)

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.

Possible Issue: specified device is not the boot device

In case you get the error:

specified device is not the boot device

Connect the 2 pins directly on the module to enter the recovery mode. Refer to section Directly on Txx module.

This problem is fixed in the Win CE bootloader V0.1 beta 7 and newer.

Video Tutorial