Documentos de Académico
Documentos de Profesional
Documentos de Cultura
We reserve the right to change the contents of this document without notice. The information contained
herein is believed to be accurate as of the date of publication; however, Bernecker + Rainer Industrie-
Elektronik Ges.m.b.H. makes no warranty, expressed or implied, with regard to the products or the
documentation contained within this document. In addition, Bernecker + Rainer Industrie-Elektronik
Ges.m.b.H. shall not be liable in the event of incidental or consequential damages in connection with or
resulting from the furnishing, performance, or use of these products. The software names, hardware names,
and trademarks used in this document are registered by the respective companies.
I Version information
Version Date Comment Author
1.0 17.01.2006 First edition ROG
II Table of contents
5 Table index................................................................................................................ 10
6 Index.......................................................................................................................... 11
2 Products affected
Previous Compact Flashes New replacement Compact Flashes
5CFCRD.0032-02 Compact Flash 32MB TrueIDE SanDisk/A 5CFCRD.0064-03 Compact Flash 64MB TrueIDE SSI
5CFCRD.0064-02 Compact Flash 64MB TrueIDE SanDisk/A 5CFCRD.0064-03 Compact Flash 64MB TrueIDE SSI
5CFCRD.0128-02 Compact Flash 128MB TrueIDE SanDisk/A 5CFCRD.0128-03 Compact Flash 128MB TrueIDE SSI
5CFCRD.0256-02 Compact Flash 256MB TrueIDE SanDisk/A 5CFCRD.0256-03 Compact Flash 256MB TrueIDE SSI
5CFCRD.0512-02 Compact Flash 512MB TrueIDE SanDisk/A 5CFCRD.0512-03 Compact Flash 512MB TrueIDE SSI
5CFCRD.1024-02 Compact Flash 1024MB TrueIDE SanDisk/A 5CFCRD.1024-03 Compact Flash 1024MB TrueIDE SSI
5CFCRD.2048-02 Compact Flash 2048MB TrueIDE SanDisk/A 5CFCRD.2048-03 Compact Flash 2048MB TrueIDE SSI
5CFCRD.4096-03 Compact Flash 4096MB TrueIDE SSI
Table 2: Changeover list for the affected Compact Flashes
As you can see already, there is no 32MB version among the new CF’s. A 64MB CF must be used
instead. Additionally, a 4GB CF is now also available with the new CF generation.
If partition sizes were indeed modified, than in some cases the restored image will no longer be able to
boot correctly. This problem occurs right away during the first boot procedure and is therefore simple to
test!
The error usually occurs in relation with boot loaders if they are located at the wrong position or are
fragmented because of the partition size modification.
We observed the following phenomenon using the disk image tool "Powerquest Drive Image 2002" and
"Powerquest DeployCenter ImageCenter 5.5" in relation with a VxWorks Image:
When making boot partition sizes, images that were created on a 64MB Sandisk CF and restored on a
64MB Siliconsystem no longer booted if the image was restored without size adjustment. (the boot loader
cannot be located)
The 64MB Siliconsystems CF will also boot with this image without error if the size is automatically
adjusted here.
However, exactly this size modification will cause a problem with a much greater portion of VxWorks
Images.
The 64MB Siliconssystems CF will also boot without having to adjust the partition size if a Disk to Disk
copy is made from Sandisk to Siliconssystems using the same tools.
If the same Sandisk image is cloned with Norton Ghost then the 64MB Siliconsystems CF will boot
without any problems, even if the image is restored without size adjustment.
Therefore, it can be assumed that Powerquest Image Tools does not function 100% free-of-error in all
cases if an image is restored on a data carrier with modified disk geometry.
Important:
B&R recommends not adjusted the size of the boot partition when restoring images because this
will cause problems in most cases.
Although problems can occur when changing the partition sizes, some problems can also be
solved this way as seen in the case described above.
Important:
In some cases, restoring images on a data carrier with a different type/manufacturer can also
cause problems with commercial disk image products.
Therefore, the boot procedure for a restored image should always be tested after switching over
from a Sandisk to Siliconsystems CF.
Select the data carrier in the B&R eMbedded OS Installer and click on the "Properties" icon in the toolbar.
Select the "Geometry" tab, activate the "Manual disk geometry" checkbox and enter the following
geometry for the 64MB Siliconsystems CF 5CFCRD.0064-03:
Only this setting will allow Windows CE to boot correctly from a 64MB CF 5CFCRD.0064-03 on a target
system.
The disk geometry of all other Siliconsystems CF sizes is compatible to Sandisk CF’s, so that Windows
CE will also boot correctly without manually changing the disk geometry.
Note:
64MB Siliconsystems CF’s will also be supported in the next version of the B&R eMbedded OS
Installer without having to manually adjusted the disk geometry.
Important:
The following limitations apply to 32MB and 64MB images from Sandisk CF’s:
Due to the changed disk geometry, only Automation Runtime images created with 32MB or 64MB
Sandisk CF's can be restored on a 64 MB SiliconSystem CF.
Important:
Other operating system images will no longer function if this message appears when restoring!
Problems of this nature did not occur with sizes from 128MB to 2GB because the disk geometry of both
CF manufacturers starting at this size is compatible enough that we were not able to determine any
problems.
Important:
If manual device changes were made, e.g. switching off the disk cache for the Sandisk CF, then
these settings are lost and must be set again manually for the Siliconsystems CF.
This behavior also occurs if the CF Firmware version string is changed.
Because this has already happened once before for Sandisk CF’s at the beginning of 2005
(Firmware HDX 2.15 to 2.25), it should generally be known whether or not manual changes must
be made.
This problem does not usually occur because changes are generally not made to the default
settings for the data carrier.
Similar behavior must be expected in the event that other Plug and Play operating systems also
detect a new data carrier.
If this is the case then you also have to check whether manual changes must be made or not!
4 Figure index
Figure 1: B&R eMbedded OS Installer - Manual Disk Geometry..................................................................6
Figure 2: Changed disk geometry with the PVI Transfer Tool ......................................................................7
5 Table index
Table 1: Version information .........................................................................................................................2
Table 2: Changeover list for the affected Compact Flashes .........................................................................4
6 Index
F T
Figure Index..........................................................9 Table index .........................................................10
Table of contents ..................................................3
I
Index ...................................................................11
V
Version information...............................................2