NAND Flash MDD/PDD Model
Sandeep
I have implememted the NAND Flash MDD/PDD model. The driver is able to
initialize itself and able to read/write file through file system.
But I have some problem with this implementation, like:
1. During the initialization driver is not able to recognize the OS
partition and it is treating it as an extended partition. So I am not able to
retain the OS image stored in the NAND Flash across the boot.
2. Write fails if I try to write data into the NAND using DeviceIOControl().
The write error number is 31 and it means "A device attached to the system is
not functioning".
In my MDD/PDD registry settings, I am using "flashpart.dll" as my partition
driver.
Waiting for help.
--
Sandeep K
mike
----------------------------------------------------------------------
Hi Sandeep:
> 1. During the initialization driver is not able to recognize the OS
> partition and it is treating it as an extended partition. So I am not able to
> retain the OS image stored in the NAND Flash across the boot.
Answer: You need to configure your partition registry correctly such
as [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NANDFMD] etc.
Retain NAND Flash across the boot, you need to setup HIVE
in registry, and it is not easy.
> 2. Write fails if I try to write data into the NAND using DeviceIOControl().
> The write error number is 31 and it means "A device attached to the system is
> not functioning".
Answer: I never try to use DeviceIOControl() before, so I don't know.
Rik Attrill
> 2. Write fails if I try to write data into the NAND using DeviceIOControl().
> The write error number is 31 and it means "A device attached to the system is
> not functioning".
I'm assuming that none of your PDD functions get called into when this
happens?
IIRC, the source code for the MDD part of the new driver model isn't
made publicly available - so I think this will be pretty difficult to
debug.
Is there a particular reason you wish to use the MDD/PDD model? (e.g
you want MLC NAND support)
Have you considered using the older FMD model instead (at least to
start with)?
You could then wrap it up using the FMDWRAPPER library if you want/
need to conform to the MDD/PDD model. The source code for the wrapper
is at C:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\BLOCK\MSFLASH
\FMDWRAPPERPDD.
best regards,
Rik A
Gary Swalling
Are you using BinFS to store the OS image?
Is the driver configured to autoformat?
What filesystem manages the data partition?
Regards,
Gary
"Sandeep" <sandee...@gmail.com> wrote in message
news:A8CA113D-23E7-47EA...@microsoft.com...