Re: File system is not working in Retail Version in WinCE 5.0



Hi Anthony,

Thanks, Now i am able to format, create the new partition also i am storing
the files to the NAND Flash File system.But when i reboot it in the retail
Version, i am not able to see the partitions. But in debug version the files
i created in the retail version is visible.

In Debug version boot process after the NAND.dll the MSPART.dll,FATFSD.dll
and diskCache.dll are called one by one. But The MSPART.dll and other dlls
are not called.

"prabu" wrote:

Hi Anthony,

Thanks for your reply......

As per your suggestion if there is problem in our FMD, for NAND file system
i have the own FMD, but for the NOR file system i am using the FMD given by
the Microsoft in the public Directory and i am using tthe Strata P30 flash.

Advanced Thanks ,
Prabu Kumar.K


"Anthony Pellerin" wrote:

TFAT and FAL work fine in DEBUG and RETAIL version, you should check your
FMD, and mainly the timing on your chip select of something like that.
I would suggest you modify your fmd_init so that at the end, it performs an
erase of the whole flash, writes different patterns in each sector (and
spares), reads them back and compares to what is expected.

HTH

--
--
--
----------------------------------------------------------------
Anthony Pellerin (eMVP)
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------
"prabu" <prabu@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de news:
3B511CD4-9EE2-43A8-B95E-583A64CF89F4@xxxxxxxxxxxxxxxx
Hi all,

I am trying to implement the tfat filesystem for NAND and NOR flash in my
device on WINDOWSCE 5.0.
Both Nor and Nand Flash filesystem is working in the Debug version. But it
is not working in the retail version.

During the format operation,

FMD_WriteSector() is called by the FAL,after that FMD_ReadSector() is
called
by the FAL,then again the FMD_WriteSector() and FMD_ReadSector() is called
for each Sector Starting from 0th Sector.

But the same operation is not taken place in retail version for both NAND
and NOR filesystem. Only FMD_ReadSector() is called for some time and it
says
the following error on the Message box.

"A System Cannot Write to the Specified Device".

Is there any Code Optimisation Issue During the Compilation process?
Because
both the NAND and NOR FMD drivers are working correctly in the Debug
Version.The Same issue is occured in both the file system.

Also I am suspecting the issue in FAL. Because the FMD_ReadSector() and
FMD_WriteSector() is called by that Layer.


Advanced Thanks,
Prabu Kumar.K





.



Relevant Pages

  • Re: File system is not working in Retail Version in WinCE 5.0
    ... As per your suggestion if there is problem in our FMD, for NAND file system ... the Microsoft in the public Directory and i am using tthe Strata P30 flash. ...
    (microsoft.public.windowsce.embedded)
  • Re: File system is not working in Retail Version in WinCE 5.0
    ... I'm using a NOR based flash, ... and when I'm in debug mode, ... As per your suggestion if there is problem in our FMD, for NAND file system ...
    (microsoft.public.windowsce.embedded)
  • Re: File system is not working in Retail Version in WinCE 5.0
    ... I'm using a NOR based flash, ... and when I'm in debug mode, ... As per your suggestion if there is problem in our FMD, for NAND file system ...
    (microsoft.public.windowsce.embedded)
  • Re: File system is not working in Retail Version in WinCE 5.0
    ... I am using the NAND Flash for FAT File System only and I am using the ram ... debug and retail versions after that the loading sequences differs for each. ... As per your suggestion if there is problem in our FMD, for NAND file system ...
    (microsoft.public.windowsce.embedded)
  • Re: NAND Flash drive in CE 6.0
    ... When the OS mounts the flash filing system, ... Blocks are marked as bad by the manufacturer of the NAND part. ... So, to protect your bootloader from being erased, you need to ensure ... the driver call for sector 0, your shim adds an offset (sufficient to ...
    (microsoft.public.windowsce.platbuilder)