Toradex Colibrì iMX6 full eeprom cloning

Hello we have a master iMX6 that we managed to configure completely, now we want to be able to dump the full eeprom to binary files so that we can just clone another new iMX6 with the saved data.

In the past with T20 coming directly with WindowsCE preinstalled we could use the UpdateTool to achieve this.

Now it seems that UpdateTool no more dumps everything, and also in the Toradex Easy Installer it seems that it is not possible to load a full dump from anywhere.

Can someone help me about how to manage cloning on new Toradex boards?

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


For cloning a complete setup from one Colibri iMX6 module to another, including the EEPROM (which in the context of Toradex modules typically refers to the module’s configuration stored in a dedicated flash memory area rather than a traditional EEPROM), you can follow a process that involves creating a full image backup of the source module and then restoring this backup to your target modules.

Given that you’re working with the Colibri iMX6, which does not support direct EEPROM cloning in the same way that might have been possible with older modules or different tools, you’ll need to use a different approach. Here’s a method to achieve a similar result:

  1. Create a Backup Using the Toradex Easy Installer: While the Toradex Easy Installer (TEZI) primarily serves to flash new images onto Toradex modules, it doesn’t directly offer a feature to create a full backup of the module’s storage, including the configuration block and all partitions. However, you can use external tools to create a backup.

  2. Using External Tools for Backup:

    • Linux-based Systems: You can use the dd command to create a complete backup of the module’s internal storage. This requires booting the module into a state where you can access its internal storage over a connection (e.g., USB or network) from a Linux host.
    • Access via U-Boot: For modules with U-Boot accessible, you can use U-Boot’s UMS (USB Mass Storage) feature to expose the module’s storage to a connected computer as a USB mass storage device. From there, you can use disk imaging tools like dd on Linux or Win32 Disk Imager on Windows to create a complete image of the module’s storage.
  3. Restoring the Backup:

    • Once you have a complete backup image, you can write this image to new modules using the same tool you used to create the backup. This process effectively clones the entire setup, including the operating system, applications, and configuration data, from the source module to the target modules.
  4. Considerations:

    • Configuration Block: Pay special attention to the configuration block, which contains module-specific information like the serial number and MAC addresses. Cloning this information to multiple modules can lead to conflicts, especially in networked environments. You may need to manually adjust the configuration block on cloned modules to ensure unique identifiers.
    • Legal and Licensing: Ensure that any software or configurations being cloned comply with

Please, also check if these links can help you solve your problem:

Using DIP Switches to change the boot process | Toradex Developer Center.

The Colibri iMX6 module does not feature EEPROM, so I assume you are referring to eMMC.If you are using WinCE, I recommend using the UpdateTool to back up your Master image. First, on a new module, flash a ‘clean’ WinCE image using the Toradex Easy Installer. After that, boot to WinCE and use the UpdateTool to apply your Master backup.

Please, ensure that you use the same WinCE release for the ‘clean’ OS image as you did for your Master image.

Yes, the UpdateTool for iMX6 is slightly different, and you can’t do a full backup or restore with one click, but you can still back up all sections separately (bootloader, splash screen, registry, OS, configblock, SPL, and filesystem) and then restore them one by one. To automate this process, you can create a batch file using the UpdateTool CLI.

Hello, actually the UpdateTool in the WinCE7 image permits me only to backup Config Block, Registry and Filesystem, all the other sections are not available on the GUI.

Is there a way to provide locally a selected image so that EasyInstaller can download from an in premise server?

If you use the same version of a ‘clean’ WinCE image as your master one, the bootloader, OS image, and SPL will be the same. So, you only need to restore the Config block (if you made changes there), registry, and filesystem.

The Easy Installer can install images from local media (SD card/USB flash drive), and if you set the autoinstall property to ‘true,’ the installation will start automatically after booting the Easy Installer.

You can place the ‘clean’ OS image, backed-up files, and a batch file with the Update tool commands on the same media. Then, configure the batch file to autorun when WinCE boots.

This way, the new device flashing process will be as follows:

  1. You have a carrier board with the prepared media (as listed above) inserted.
  2. Insert a new Colibri iMX7 module.
  3. Power up the carrier board.
  • The module boots to the pre-flashed Easy Installer.
  • The Easy Installer automatically flashes the ‘clean’ WinCE image.
  1. Reboot the module.
  • WinCE boots and starts the batch files to update the registry, filesystem, and Config block (if needed)