Request for Guidance on Migrating Data from Colibri VF50 V1.2 to a New Module

Technical Support
1

Hello Toradex Community
Im so new to Toradex Colibri and am currently using a Colibri VF50 V1.2 module in my system. I need to replace the existing module with a new Colibri VF50, but I would like to retain the same data, software, and configurations that are currently on the old module.

Could you please advise on the recommended procedure for:

Creating a complete backup of the flash/storage contents of the existing module.

Restoring this backup onto a new Colibri VF50 module.

If there are any specific tools, utilities, or documentation available (for example, related to the Toradex Easy Installer or USB recovery process), I would greatly appreciate if you could point me to them.

Thank you for your assistance.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

I need to clarify that the Colibri VF50 module you’re using is a Windows Embedded Compact (WinCE) product, not a Torizon-based system. While I can provide some guidance based on the available documentation, please note that WinCE is considered legacy technology and is not recommended for new projects.

Complete Backup and Restore Procedure

Creating Master Backup Files

For creating a complete backup of your existing Colibri VF50 module, you should follow these steps (1)(2):

  1. Set up the source module with all your software and settings (1)(2)

    • Ensure the Configblock and Registry are correct
    • Verify your software is properly installed (e.g., in \FlashDisk\)

  2. Use the Update Tool for backup (1)(2)

    • Use the Update Tool to backup all regions you want to restore including Configblock, Registry, and filesystem
    • Important: Use the latest available Update Tool - older versions may not work properly for downgrades or version changes

Restoring to New Modules

There are several options for restoring the master backup files to new modules (1)(2):

Option 1: Using Latest Update Tool

  • Execute Update.exe with Command Line parameters to restore regions one by one (1)(2)

Option 2: Production Programming Script

For production programming, you’ll need a USB, SD, or other mass storage device (1)(2):

Preparation (one-time setup):

  1. Download the production programming template (1)(2)
  2. Copy the master backup files into the folder Production programming template\Backup\ (1)(2)
  3. Copy the latest Update tool into the folder Production programming template\UpdateTool\ (1)(2)
  4. Modify the ProductionProgramming.Bat file to your needs (1)(2)
  5. Copy all files to your production programming storage device (1)(2)

Programming Process:

  1. Boot the target module and insert the production programming storage device (1)(2)
  2. The update process will start automatically - wait for completion (1)(2)
  3. Reboot the device (1)(2)

Important Considerations

Power Loss Warning: If power loss occurs while programming data, the flash could get corrupted (1)(2). As long as the Bootloader is not damaged, you can use it to restore the module. If the bootloader is damaged, you’ll need Recovery mode to restore the module (1)(2).

Version Compatibility:

  • If updating to a newer image version of the same OS, you need to clear the registry as it may be incompatible (1)(2)
  • If updating from a different version of Windows CE, you need to first update the bootloader and image, reboot, then update the remaining sections (1)(2)

Recovery Mode (if needed)

If your module doesn’t boot properly, you can use recovery mode following the procedures outlined in the VFxx Recovery Mode documentation (3). The recovery process involves specific hardware mechanisms or bootloader commands to enter recovery mode.

Additional Resources

For the most current Update Tool and detailed procedures, refer to the VF50/VF61 WEC Software documentation mentioned in the sources (3).

Note: The Colibri VF50 is supported only up to BSP 2, and there are no plans to support it in newer BSP versions like BSP7 (4). For new projects, consider upgrading to newer, better-supported modules in the Colibri family or the more future-proof Verdin family.

Best regards, Toradex AI Assistant.

3

Hi @Zahra8766!

Which OS and version are you using?

Were you able to test the procedure recommended by the Toradex AI?

Best regards.

4

i havent had any success yet, but im working on it. I have a monitoring MCU module which has colibri VF50 V1.2 on it, and i want to replace the module. i dont have an evaluation board, but my main module has USB-B port and Ethernet(which im not sure is connected to colibri module). i need to duplicate all the data to new module to replace it

5

@ToradexAI

the point is that I dont have any evaluation board, my colibri VF50 is installed on my main board, and i have access to a USB type B and Ethernet connector on it. i have copied the whole flash data but i have lost my CAN network connections. What should I do now?(besides its a windows operating product)

6

Thanks for your response.

Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.

Did you like my answer? :+1: :-1:

CAN Network Connection Recovery

Since you’ve successfully copied the flash data but lost CAN network connections, this suggests an issue with the module configuration block or registry settings. Here’s how to address this:

Restoring Factory Configuration

The issue you’re experiencing is likely related to the module’s factory configuration being corrupted or not properly restored (1). You’ll need to restore the factory information using the bootloader commands.

First, access the bootloader console by pressing SPACE during boot (1):

Press [SPACE] to enter Bootloader Menu

Then press X to access the command prompt (1).

Module Configuration Recovery

Each module has specific factory information that needs to be restored. Check the sticker on your module for the following format (1):

  • Col type
  • V version
  • serial

Use the restorefactoryinfo command with your module’s information (1):

>restorefactoryinfo *modulecode* *serial* *ver*

For VF50 modules, the modulecode parameter should be either VF50128 or VF50128IT depending on your specific variant (1).

Example command format (1):

>restorefactoryinfo VF50128 04790168 1.0B

Registry Cleanup

If the CAN network is still not working after restoring factory info, you may need to clear the registry (1). This is important because registry settings from the old module might be incompatible:

  1. Boot the module and press SPACE to enter the bootloader menu (1)
  2. Press C to clear the registry (1)

Warning: After registry cleanup, you’ll need to reconfigure your display resolution, network settings, and other configurations (1).

Alternative Recovery Method

If the above doesn’t resolve the CAN issues, you might need to use the bootloader’s flash erasing capabilities (1):

  1. Access the bootloader command prompt
  2. Use the eraseflash command to clear specific flash regions if needed (1)
  3. Restore the backup files using the Update Tool

USB-B and Ethernet Connectivity

Since you have USB-B and Ethernet ports available on your main board, you can use these for:

  • USB-B: For connecting to a PC to run the Update Tool or access the bootloader console
  • Ethernet: For network-based updates if properly connected to the Colibri module (2)

The Ethernet connectivity can be used for data transfer as documented in the Ethernet communication procedures (2), but you’ll need to verify that it’s properly connected to the Colibri module on your custom board.

Important Notes

  • Make sure you’re using the latest Update Tool version, as older versions may not work properly for version changes (1)
  • The VF50 module supports advanced power management and GPIO configuration through registry settings (3)
  • If power loss occurs during programming, the flash could get corrupted, but as long as the bootloader isn’t damaged, recovery is possible (1)

Try the factory information restoration first, as this is the most likely cause of your CAN network connection issues after a module replacement.

Best regards, Toradex AI Assistant.

7

its windows but how should i get the version?

no i didnt have success with it, mainly cause i dont have evaluation board.

9

@ToradexAI

how am i supposed to access bootloader and etc while i just have a usb connection?

i can just connect to the module using usb and see the files using windows mobile

10

Thanks for your response.

Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.

Did you like my answer? :+1: :-1:

Accessing Bootloader via USB Connection

You can access the bootloader through your USB connection, but you’ll need to establish a serial terminal connection rather than just viewing files through Windows Mobile Device Center.

Setting Up Serial Connection via USB

To connect to the bootloader, you need (1):

  • A terminal application (e.g. HyperTerminal or TeraTerm) (1)
  • Your USB connection should provide a serial interface

Connection Settings (1):

  • For Colibri PXA, Colibri Tegra (BSP V1.1beta2 and older): 9600 Baud/ 8 Data Bits/No parity/1 Stop Bit (1)
  • For Colibri Tegra (BSP V1.1beta2 and newer), Apalis Tegra: 115200 Baud/ 8 Data Bits/No parity/1 Stop Bit (1)

Accessing the Bootloader Menu

  1. Open your terminal application on the PC (1)
  2. Configure the serial connection with the appropriate baud rate settings (1)
  3. To enter the Bootloader menu, press and hold the space bar on the Terminal PC, while rebooting the Colibri Module (1)
  4. Keep space bar pressed until you reached the Bootloader menu (1)

Expected Bootloader Menu

When you successfully enter the bootloader, your terminal should display something similar to this (1):

Toradex Windows CE Bootloader 3.1 for Colibri Built Apr  7 2008  
  
Press [SPACE] to enter Bootloader Menu  
  
BootLoader Configuration:  
  
C) Clear Flash Registry  
X) Enter CommandPrompt Mode  
D) Download image to RAM now  
F) Download image to FLASH now  
L) Launch existing flash resident image now  
  
Enter your selection:

(1)

Getting Module Version Information

Once you access the bootloader command prompt (press X from the main menu (1)), you can get version information. However, the easiest way to get your Windows CE version is:

  1. From Windows CE desktop: Check the system properties or version information in the Control Panel
  2. From the module sticker: Look for the physical sticker on your Colibri VF50 module which shows the hardware version
  3. Through bootloader commands: Access the command prompt and use system information commands

Troubleshooting USB Serial Connection

If you’re having trouble establishing the serial connection:

  1. Check Device Manager on your Windows PC to see if the USB device appears as a COM port
  2. Install proper USB drivers if the device isn’t recognized as a serial port
  3. Try different terminal applications - some users reported problems with HyperTerminal, so try TeraTerm if you have issues (1)

Alternative: Using Network Services

If you can’t establish serial access, Windows CE provides network services that might help (2):

  • Telnet Server - if enabled and configured (2)
  • FTP Server - for file access (2)
  • Web Interface - for remote administration (2)

However, these services require no default password (2). If no initial password is set, most services cannot be used (2). An initial password can be set on the remote admin interface if you haven’t disabled this feature (2).

The key point is that you need to establish a serial terminal connection through your USB port, not just file access through Windows Mobile Device Center. This will give you access to the bootloader console where you can perform the necessary recovery operations.

Best regards, Toradex AI Assistant.

11

@ToradexAI

i cannot connect to the usb using sserial port, my device appears as a portable device, not usb connection

12

Thanks for your response.

Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.

Did you like my answer? :+1: :-1:

Let me address your specific issue with the USB connection appearing as a portable device instead of a serial port.

Serial Over USB for WinCE Modules

Your Colibri VF50 module can establish a serial connection over USB, but you need to configure it properly first (1).

Steps to Enable Serial Over USB

  1. Disable ActiveSync on the module (1)
  2. Stop ActiveSync/Mobile Device Center service (wcescomm.exe) on your PC to prevent it from occupying the virtual serial port (1)

Accessing the Serial Port

Once properly configured, the module will provide access to a virtual serial port (1):

On the Toradex Module (Windows CE side):
The COM port can be accessed on the virtual port \$device\COM0 (1):

HANDLE hPort;  
hPort= CreateFile( TEXT("\\$device\\com0"), GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, 0, NULL );  
	     
if (hPort == INVALID_HANDLE_VALUE)   
{  
    printf("Can not open port!\r\n");  
}

(1)

On the PC (Host side):
The virtual serial port on the module can be accessed using regular COM port APIs. The port is called \\.\wceusbsh001 (1):

HANDLE h;  
unsigned char buf[32] = "TestMsg";  
unsigned int written;  
  
h = CreateFile("\\\\.\\wceusbsh001", FILE_ALL_ACCESS, 0, NULL, OPEN_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL);   
// do some error handling here....  
  
WriteFile(h, buf, 5, &written, NULL);  
CloseHandle(h);

(1)

Important Requirements

  • Install ActiveSync on your PC - The drivers used on the PC are the same drivers used by ActiveSync/Mobile Device Center, so you need to install ActiveSync even though you won’t use it directly (1)
  • Note: This method may not work on Windows Vista and later versions. For newer Windows versions, WinUSB is recommended on the host side (1)

Alternative: WinUSB Method

For newer Windows versions, you can use WinUSB instead (1):

  1. Create a custom installer to match your idVendor and idProduct as described on MSDN (1)
  2. Use Zadig tool - a third-party tool that lets you create and install a customized WinUSB driver (1)
  3. Download the WinUSB Serial Sample Project - Toradex provides a basic sample project for communication (1)

Troubleshooting Your Current Issue

Since your device appears as a “portable device” instead of a serial port:

  1. Check if ActiveSync/Mobile Device Center is running - This service can interfere with serial communication (1)
  2. Ensure proper driver installation - You may need to manually install or update the USB serial drivers
  3. Verify the module’s USB configuration - The module might need to be configured to enable serial over USB functionality

The key is that your Colibri VF50 module needs to be configured to present itself as a serial device over USB rather than a storage/portable device. This typically requires proper driver installation and ensuring ActiveSync isn’t interfering with the connection.

Best regards, Toradex AI Assistant.

13

Hi @Zahra8766!

Just to confirm and address your issue correctly, do you need to migrate all the data from a Colibri VF50 to a new module? Do you already know which are the new family and model?

About your OS, you have been using WinCE so far, right? For the new module, will you use Torizon OS or your custom image built using Yocto?

Best regards.

14

I have Colibri VF50 on an old board, i want to change the module with a new Colibri VF50(dont need to change the version or firmware or OS)

How should i copy the data? Its OS is windows CE and i dont have a carrier board. Just the main board having USB and Ethernet

15

Hi @Zahra8766 ,

We could not find your e-mail in our customer records, can you provide us information on what company you’re working? Is your company a Toradex Customer?

If not, did you buy the device containing the Toradex Module from another company that might be a Toradex customer, then you should ask support through that other company.