Re: NAND Flash drive in CE 6.0

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Jun 2, 2:52 pm, B-Dawg <BD...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Bradlry,

Thanks for your reply.  But I want to say that Harsh's reply didn't really
have anything to answer my question and there is no reply by anyone called
Andrew to my thread.  Where is these posts?  In my list Harsh only replied
once in a very general way asking for more info....  Is there a reason these
other replies you say are there are hidden from me?  Perhaps you can copy
them into your next reply to me.

So this hasn't left me anything yet to go by.  When you say reserved blocks
are you meaning in Config.bib?

I use groups.google.ca to access the newsgroups and andrews post shows
up there so you can always take a look at that interface. A Link is
here:
http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/130f36aa03c6ecc8/f67c9593185a0e39#f67c9593185a0e39

To summarize there are basically two ways to do a FAL/FMD driver (that
I am aware of, there could be more)

One method shows the FAL all blocks (including those occupied by non-
FS data such as Kernel and Bootloader (should they be on the same
flash device as your FS)) but marks blocks that the FAL should not
access (and is not allowed to touch) as RESERVED. This is what Harsh
is telling you to check and it has nothing to do with the config.bib
or any other .bib file.

The second method is to re-map the blocks in your FMD driver so that
there are no reserved blocks. In this case Block 0 as reported to the
FAL may not be Block 0 but be say Block XYZ.

To solve this problem you will have to read up and understand how the
FMD/FAL drivers work, andrew gave lots of hints (and a long post) so
please read that, you may have to try an online newsreader or even
check the microsoft interface.

If you look at your FMD_GetInfo function, then look into the functions
it calls you should eventually understand how it is all laid out.

Regards,
Brad.
.

Relevant Pages