文件列表:

Nandflsh\Build.log (3380, 2007-11-16)
Nandflsh\BuildExe\FLASHDRV.DEF (217, 2003-05-20)
Nandflsh\BuildExe\makefile (313, 2003-05-20)
Nandflsh\BuildExe\sources (366, 2003-05-20)
Nandflsh\dirs (51, 2003-05-20)
Nandflsh\FMD\cfnand.h (2674, 2003-10-02)
Nandflsh\FMD\ecc.c (3420, 2003-05-20)
Nandflsh\FMD\fmd.cpp (38485, 2003-11-17)
Nandflsh\FMD\makefile (250, 2003-05-20)
Nandflsh\FMD\nand.s (3342, 2003-07-28)
Nandflsh\FMD\sources (409, 2003-11-17)
Nandflsh\BuildExe (0, 2008-05-12)
Nandflsh\FMD (0, 2008-05-12)
Nandflsh (0, 2008-05-12)

//--------------------------------------------------------------------- // Copyright (c) Microsoft Corporation // // Module Name: NandFlash.dll // //--------------------------------------------------------------------- Purpose: --------- Provide a Flash Media Driver for Microsoft Flash block driver to work with resident NAND flash on SMDK2440 PCB. Design: -------- FMD is the lowest layer that deals with NAND flash chip directly. Microsoft Flash block driver access FMD via FMD_xxx interface which is documented in fmd.h file (smdk2440\inc). Environment varialbe: --------------------- You need to set BSP_HASNAND to 1 in order to build this component. Registry Settings: ------------------ [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NandFlash] "FSD"="fatfs.dll" "Prefix"="FAL" "Dll"="FLASHDRV.DLL" "Order"=dword:1 "Index"=dword:0 "Ioctl"=dword:4 "Folder"="NandFlash" "FriendlyName"="NAND FLASH Device Driver" Dependencies: ------------- The final DLL depends on some libraries in SMDK2440\Drivers\Nandflsh\buildexe\lib directory. To make the driver work, you also need to include FATFS in the final image. Issues and Recommendations: --------------------------- 1) The current implementation is for Windows CE 3.0 environment only. Starting from CE 4.0, the storage architecture has changed. You need to modify the drivers as well as registry setting to compliane to CE 4.x requirements. Luckily, Microsoft Flash Block Driver will be shipped in CE 4.2, which will provide an official way to construct the driver. 2) Bad block management. The current implementation write bad block mark to the spare area to mark a block is bad. This may not be the best way to track bad block. It might make sense to maintain a bad block list somewhere else. For examples, you can dedicate a block just for the place holder for bad block. 3) Performance improvement. The current NAND device driver doesn't support DMA or other means to speed up the read/write throughput. Even though we provide an assembly function ReadPage512 and WritePage512, it may still not be the most efficient way.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：