In the latest UpdateTool from image version 1.7, it is not possible to do a complete backup of bootloader, Config Block, OS image, Registry etc.
I can either make a backup of the registry, config block or filesystem
Why is this removed? I could this in the previous versions (I need to update from 1.4 to 1.7)
How do I now make the production image? It contain OS image, registry, Confgi block and filesystem changes.
It was much easiere when I just could make a complete backup. Now I need to run a bat file updating image, config block, rwgistry and filesystem seperate!!
Unfortunately for all new SOCs we decided to use the new UpdateLib concept of single sections Backup/Restore. Only PXA and Tegra still use the old concept.
I’m sorry for the inconvenience this might cause you.
You should be still able to fully automate the update procedure with a batch file.
Maybe in future i will re-add the feature by allowing to open a layout file (similar to the one in Tegra) that will automatically process all the sections. Also such a layout file could be generated during Backup of multiple sections.
Windows CE does not have the concept of “current directory” as in Desktop Windows, so paths are always absolute. You need to specify the whole path in the command line:
It depends on the CE version in the module before update.
If I flash the modules with CE6 version 1.4 and it is update to CE8 version 1.7, it must be restarted before I can load the file system backup to it. Else I get an unspecified error from update tool
OK, this is probably a special case as we did some major changes from 1.4 to 1.5 in the NAND FileSystem handling. I did not think you’ll downgrade to a very old version.
Please also check the release notes, as lots of things were changed and bugs were fixed since 1.4, maybe some will affect you. Especially the new Flash handling improved reliability of the flash device.
I did the downgrade, because we have some old units out there with 1.4 on them. And in the case we do an upgrade of those (for any reason) it would be nice to know that the automatic update procedure also would work on them. Thats why I did the test with the old version…
The new module we get in production is version 1.2B, so we need to upgrade the image for the future