If the Appalis T30 is preflashed with Linux it is rather complex to change to Windows CE7.
Also “Production Programming” doesn’t work.
when the Apalis T30 is shipped it has Linux. So the “Volume Programming” doesn’t work?
Start the module to be programmed with
the storage medium inserted, or insert
the medium after Windows CE has
started
So the usual working steps are: Txx Recovery Mode | Toradex Developer Center, Production programming (includes copying of files), setup the Display, setup the .net Framework, calibrate touchscreen.
Hi Stefan.P
Toradex doesn’t offer custom image programming currently. The reason is, we deliver directly from stock and don’t manufacture on request. This has many advantages such as short lead times, etc.
You say production programming doesn’t work. Do you have more details on that? What’s the problem? Do you get any error messages? Because this would currently be the way to do your production programming. We can help you get it running if you share more details.
thank you. I thought that the production programming would only work with WinCe.
With the Image i would have some main needs:
Install the latest WinCE7 Image
Install the EDT700xx TFT Touchscreen (should work if the registry settings are set?)
Install the Compact Framework 3.5
Update the Splashscreen (will be bought soon)
Copy some files
In the next image release the UpdateTool schould get 100% backup/restore functionality. This mean that you can setup the image as needed, like registry, .NET CF install etc.
Then do a complete backup of the bootloader, config block, registry, filesystem and image in a single BIN file.
This BIN file can then be deployed like above with only one command in the BAT file:
when the Apalis T30 is shipped it has Linux. So the “Volume Programming” doesn’t work.
Start the module to be programmed with the storage medium inserted, or insert the medium after Windows CE has started
So the usual working steps are: Txx Recovery Mode | Toradex Developer Center, Production programming (includes copying of files), setup the Display, setup the .net Framework, calibrate touchscreen.
You are right, the production programming is much different from a module, that has Linux preflashed. There are currently two options for production programming with these kind of modules:
As you mentioned, you flash WinCE using the recovery mode and then flash the Drivers, Registry, Splashscreen and the .NET framework as mentioned in the production programming process. The drivers as well as the .NET framework should work fine with the registry import/export and the data copied to the right location.
You wait for an other 2 weeks to use the new UpdateTool to create backup files from a “golden module” which then can be also flashed over NVFlash/Recovery mode. The tool will be available with 2.0beta 1 release.
In both cases you need NVFlash, there is currently no other way around that. This means, you always need a PC that flashes the devices.
thank you. That sounds promising!
The problem that a PC is needed is not that big Problem.
But it would be still great if it would be possible to use a USB Stick to reset a Module to “Specific Defaults”.
Toradex doesn’t offer custom image programming currently. The reason is, we deliver directly from stock and don’t manufacture on request. This has many advantages such as short lead times, etc.
The production programming process was made much easier with the release of UpdateTool 6.0.1. You find the updated Production Programming Process as well as the link to the new Update Tool here.
Update Tool 6.0.1 can also be used with older images and now is a standalone tool (not linked with the image).
