Re: NAND Flash drive in CE 6.0

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Does no one out there no anything about CE Flash partitions?
....................


"B-Dawg" wrote:

Hi,

I am using the FAL-FMD structure for my NAND driver. Do you want more info
about it / source code etc?

I am not using EBOOT or any part of the CE OS as my bootloader. I am using
a bootloader called Vivi. The nk.nb0 OS image itself is not being written
over the bootloader it is just the flash drive partition that I make using
Storage Manager in CE 6 Explorer, Control Panel on which I want to store my
files.

Bevan


"harry" wrote:

Hi,

I assume that you are using FAL-FMD (FTL) structure to use your NAND.

The Blocks for the Boot-loaders are needed to be reserved, so as no
other application can Write or Erase these blocks.
However it looks like that Blocks where Boot-loader resides are not
reserved hence OS image is getting written onto it.

You can verify the EBOOT, which is responsible for writing the OS
image onto the Flash.
EBOOT should check that it is not writing or erasing any reserved
block.

Kindly furnish the FTL details so as you can get the precise
answer. :)

Regards,
Harsh




On May 27, 1:15 pm, B-Dawg <BD...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a Samsung SMDK2440 based system with 64MB of RAM and 64MB of NAND
Flash. I have a smartmedia driver that formats the NAND space not used by
the OS into a flash partition. This works OK and I can put files onto it etc.

However, when creating the partition it overwrites the bootloader that is
also situated in the NAND flash so that the device will not boot the second
time. The bootloader is not part of the CE OS and so CE will not know about
it and therefore I presume does not protect those sectors. If I reflash the
bootloader back on the OS is then able to start up and is not corrupted but
the new partition that I had created is gone. This is what leaves me to
believe the NAND storage partition and the bootloader are occupying the same
sectors somewhere on the NAND.

Can someone point me in the right direction about how to resolve this? Do I
put a reserved entry into Config.bib, or do I need to code this into my
driver? Any help would be appreciated.


.

Relevant Pages

  • Re: Nand Flash Data Lost
    ... While you mentioned not only registry but also the files are lost after reboot and the bootloader did not repartition your flash, it is believe the OS wipes the Flash. ... Have you tried to build a Image only mount the NAND as an ordinal external storage but not for storing Hive nor mounting as root file-system and to see if files still lost after rebooting? ...
    (microsoft.public.windowsce.platbuilder)
  • 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)
  • Re: NOR flash choosing
    ... Are you going to be using the rest of your NAND flash for data storage? ... If you're going to store bootloader and OS ... So, our board will have 128M NAND-flash, and NOR-flash chip, with size ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Nand Flash Data Lost
    ... I check the code flow of bootloader again. ... BINFS partition will be created first and remainder space will be FAT ... And bootloader will not repartition the NAND flash, ...
    (microsoft.public.windowsce.platbuilder)
  • Problem with bootpart.lib
    ... Formatting flash. ... CreatePartition: Enter CreatePartition for 0x21. ... ERROR: OEMLaunch: failed to create/open BINFS partition. ... as it's done with bootloader config info. ...
    (microsoft.public.windowsce.platbuilder)