FlashDisk error after Updating WinCE to Version 1.9

Technical Support
, ,
1

After updating to the actuel Version 1.9 of the WinCE 6 Image, we have issues with corrupt data on the flashdisc.

If we try to install compact framework 3.5, the installer stops with error, after that the flasdisc is write protected and we see badblock errors.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

I understand you’re experiencing flashdisk corruption issues with WinCE 6 Image Version 1.9, particularly when installing Compact Framework 3.5. Based on the available documentation, I can provide some guidance on Toradex WinCE features and troubleshooting approaches.

WinCE Compact Framework Support

According to the Toradex documentation, the .NET Compact Framework is supported as an installable feature that can be added to the WinCE image(1). The documentation mentions that you can add WinCE features like the .NET Compact Framework without building your own image(1).

Known Issues and Troubleshooting

The documentation indicates that there have been various issues addressed across different WinCE releases(2). For specific issues like flashdisk corruption and bad block errors, the documentation suggests checking the Release Details page for information about fixed and pending issues(2).

Registry Configuration Options

The Toradex WinCE system provides extensive registry-based configuration options(1). The documentation states that through the Windows registry, it’s possible to configure the behavior of the WinCE operating system in almost every area, including:

  • Display interfaces and settings(1)
  • Audio and touch screen controller settings(1)
  • Driver management (disable drivers that are not required)(1)
  • USB stack configuration(1)

Update Recommendations

When updating WinCE images, the documentation emphasizes several important points(2):

  • If updating both bootloader and image, both must be updated before rebooting(2)
  • Registry changes may be required between versions(2)
  • Some versions require clearing the registry to maintain default behavior(2)

Next Steps

For your specific flashdisk corruption issue with Version 1.9 and Compact Framework 3.5 installation, I recommend:

  1. Check Release Notes: Review the WinCE BSP Release Details for Version 1.9 specific known issues(2)
  2. Registry Reset: Consider clearing the registry if transitioning between versions(2)
  3. Alternative Installation: Try using the binary WinCE image approach rather than building custom images(1)

The documentation suggests that using the tested binary images is often more reliable than custom builds, as they are tested by Toradex and thousands of customers(1).

Best regards, Toradex AI Assistant.

3

Hello @broenner !

To better assist you with this issue, could you please provide more details about your setup? Specifically, we would need to know:

  • The SoC/module you are using

  • The version/revision of the module

  • The carrier board being used

This information will help us narrow down the possible causes of the flash corruption and provide you with more accurate guidance.

4

Hello,
we use a VF61 256MB IT Colibri Module Version 1.2A on a Viola Plus Carrier Board Version 1.2A, the same issue we see on a Iris Rev. 1.1 Board.

Best Regards
Marc

5

Hi Marc,

Sorry for the delay, Your ticket just got assigned to me…
You say you have some issues with flashdisk after upgrading to image 1.9. Did you also update the bootloader to 1.9?
Flash timings were updated in image 1.9, but this works only if the bootloader is also 1.9.

Germano Kern
Toradex