This article describes the process for production programming of the Toradex Tegra modules:
Production programming requires three steps: 1. Configure a master module. 2. Create a backup of your master module and setup a production programming storage device. 3. Deploy the master module backup to your target devices.
Create a module with all the required settings. The following regions will be considered by the Update Tool when creating a backup of your master module: OS Image, Bootloader, Splash Screen, Config Block, Registry and File System.
In order to keep your backup small and the production programming fast format the File System before you start coping files to it.
After you setup the master module you are ready to create a backup:
After the backup is done you should have the following files on your external drive:
|FlashBackup.cfg||Configuration file that links to the according files. Do not touch this file if you don't know what you are doing.|
|FlashBackup_config_block.nb0||Bootloader Configuration. Serial number and MAC address of the module will not be overwritten.|
|FlashBackup_os_image.nb0||WinCE OS image|
|FlashBackup_registry.nb0||Registry (only since v2.0 beta 1), before registry was stored in File System and is automatically stored in FlashBackup_filesystem.nb0|
The config section of the file AutoRun\ProductionProgramming.bat. No changes are required if you use the same locations as proposed in the template as well as if you use the default name prefix for your backup.
Important Note for Colibri T20 flashing image V1.3 and older
If you program a Colibri T20 with an image V1.3 and older you need to set the IS_T20_BEFORE_1_4 flag to 1. The reason therefore is that with image V 1.4 an improved NAND flash error correction (ECC) was introduced on Colibri T20 modules. The Update Tool sets the ECC handling always to the best possible mode for the flash on the module. Image 1.3 and before only supported RS4 error correction, so it can not handle newer ECC handling. We recommend you to use images 1.4 and later with using the new ECC handling.
See all the configuration options bellow:
|IS_T20_BEFORE_1_4||Set to 1 for Colibri T20 with target image V1.3 and older, set to 0 otherwise (see note above).|
|BACKUPFOLDER||Path to backup location (relative to Update Tool)|
|CONFIGFILE||Name of the backup cfg file (FlashBackup.cfg by default)|
|PATH_UPDATETOOL||Path to UpdateTool.exe (relative to this batch file)|
You should now have a production programming storage device that contains the a backup of your master module, the latest Update Tool and a proper config in AutoRun\ProductionProgramming.bat.
The programming process looks as the following:
Make sure you started coping files to your master module having a clean file system. Format the File System before you start coping files to it. This ensures your file system backup is kept as small as possible, which saves time during the restore process.
The Update Tool has to unmount the file system in order to make sure no operations are done on it during the backup / restore. Reboot your device after using the Update Tool. So also make sure no application tries to access the file system during the backup or production programming process.
This could be related to the fact that you try to flash an image 1.3 or older on a Colibri T20 and missed to set flag IS_T20_BEFORE_1_4 to 1 in the batch script.