Blocks are tagged incorrectly by the IOCTL_FLASH_PDD_SET_BLOCK_STATUS I/O control on the NAND flash memory of a Windows Embedded CE 6.0 R3-based device


Symptoms


Consider the following scenario:
  • You have a Windows Embedded CE 6.0 R3-based device that uses NAND flash memory.
  • The flash memory uses the model device driver (MDD) and the platform-dependent driver (PDD) flash driver models.
  • You perform some read operations in the NAND flash memory.
  • A read operation is performed to a block, and then an error is returned to the IOCTL_FLASH_PDD_READ_PHYSICAL_SECTORS I/O control.
In this scenario, an IOCTL_FLASH_PDD_SET_BLOCK_STATUS I/O control tags another block as bad. If a write operation is performed to the first block, data corruption occurs.

Cause


This problem occurs because the error handling code considers the error as a failure to write a sector to the destination block. However, the error is actually a failure to read the sector from the source block. Therefore, the destination block is marked as a bad block.

Resolution


Software update information


A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (July 2010). You can confirm this by scrolling to the "File information" section. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is as follows:

Product version-yymmdd-kbnnnnnn-processor type

For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about how to obtain Windows CE Platform Builder and core operating system software updates:
837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder products

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

Restart requirement

After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
  • On the Build menu, click Clean, and then click Build Platform.
  • On the Build menu, click Rebuild Platform.
You do not have to restart the computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Installer files
File nameFile sizeDateTime
Wincepb60-100722-kb2263918-armv4i.msi986,11222-Jul-201019:55
Wincepb60-100722-kb2263918-mipsii.msi963,58422-Jul-201019:55
Wincepb60-100722-kb2263918-mipsii_fp.msi964,09622-Jul-201019:55
Wincepb60-100722-kb2263918-mipsiv.msi968,70422-Jul-201019:55
Wincepb60-100722-kb2263918-mipsiv_fp.msi968,70422-Jul-201019:55
Wincepb60-100722-kb2263918-sh4.msi955,39222-Jul-201019:55
Wincepb60-100722-kb2263918-x86.msi905,21622-Jul-201019:55
Files that are included in this hotfix package
File nameFile sizeDateTimePath
Windows embedded ce 6.0_update_kb2263918.htm7,65722-Jul-201019:30100722_kb2263918
Flashcommon.lib169,32428-Jun-201016:04Public\Common\Oak\Lib\Armv4i\Debug
Flashmddcore.lib746,15628-Jun-201016:04Public\Common\Oak\Lib\Armv4i\Debug
Flashcommon.lib135,12828-Jun-201016:04Public\Common\Oak\Lib\Armv4i\Retail
Flashmddcore.lib586,60228-Jun-201016:04Public\Common\Oak\Lib\Armv4i\Retail
Flashcommon.lib165,23028-Jun-201016:04Public\Common\Oak\Lib\Mipsii\Debug
Flashmddcore.lib721,10028-Jun-201016:04Public\Common\Oak\Lib\Mipsii\Debug
Flashcommon.lib135,52428-Jun-201016:04Public\Common\Oak\Lib\Mipsii\Retail
Flashmddcore.lib558,89228-Jun-201016:04Public\Common\Oak\Lib\Mipsii\Retail
Flashcommon.lib165,28628-Jun-201016:05Public\Common\Oak\Lib\Mipsii_fp\Debug
Flashmddcore.lib721,21828-Jun-201016:05Public\Common\Oak\Lib\Mipsii_fp\Debug
Flashcommon.lib135,57028-Jun-201016:05Public\Common\Oak\Lib\Mipsii_fp\Retail
Flashmddcore.lib558,99228-Jun-201016:04Public\Common\Oak\Lib\Mipsii_fp\Retail
Flashcommon.lib166,06828-Jun-201016:05Public\Common\Oak\Lib\Mipsiv\Debug
Flashmddcore.lib731,55028-Jun-201016:05Public\Common\Oak\Lib\Mipsiv\Debug
Flashcommon.lib137,38628-Jun-201016:05Public\Common\Oak\Lib\Mipsiv\Retail
Flashmddcore.lib567,41628-Jun-201016:05Public\Common\Oak\Lib\Mipsiv\Retail
Flashcommon.lib166,12428-Jun-201016:05Public\Common\Oak\Lib\Mipsiv_fp\Debug
Flashmddcore.lib731,66828-Jun-201016:05Public\Common\Oak\Lib\Mipsiv_fp\Debug
Flashcommon.lib137,43228-Jun-201016:05Public\Common\Oak\Lib\Mipsiv_fp\Retail
Flashmddcore.lib567,51628-Jun-201016:05Public\Common\Oak\Lib\Mipsiv_fp\Retail
Flashcommon.lib151,06428-Jun-201016:06Public\Common\Oak\Lib\Sh4\Debug
Flashmddcore.lib655,06628-Jun-201016:06Public\Common\Oak\Lib\Sh4\Debug
Flashcommon.lib129,73228-Jun-201016:06Public\Common\Oak\Lib\Sh4\Retail
Flashmddcore.lib529,28428-Jun-201016:05Public\Common\Oak\Lib\Sh4\Retail
Flashcommon.lib150,87628-Jun-201016:04Public\Common\Oak\Lib\X86\Debug
Flashmddcore.lib603,12628-Jun-201016:04Public\Common\Oak\Lib\X86\Debug
Flashcommon.lib128,55628-Jun-201016:04Public\Common\Oak\Lib\X86\Retail
Flashmddcore.lib517,21428-Jun-201016:04Public\Common\Oak\Lib\X86\Retail

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates