• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 1435 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RL-FlashFS - fformat options LOW and LOW_EB

Tom P

Hi All,

I'm currently working on an old project with uVision4.60

I'm using the RL-FlashFS with an SD card. I have the majority of the file maintenance routines working including fformat where I can use the options FAT32 and WIPE.

I cannot however get the LOW or LOW_EB options to work (see link below). Does anybody know whether these are later additions to the fformat function?

http://www.keil.com/support/man/docs/rlarm/rlarm_fformat.htm

Thanks

Tom

  • 0 Arm Employee Badge

    From your linked web page:

    LOW and LOW_EB options are used to low-level format the NAND drive.

- LOW will erase all good blocks, but will preserve bad blocks.
- LOW_EB will also erase bad blocks - this is particularly useful at the NAND driver
  development time, when blocks may be accidentally marked as bad - this is often the
  cause of fformat failure on NAND devices.

    Therefore, these two options are only applicable on NAND drive.

  • 0 in reply to Vladimir Umek

    The SD card that I'm using is a SLC NAND Flash memory Card, is this not the same as the NAND drive referenced in the documentation? Apologies if this is a silly question.

    As a note I have had a reply from KEIL and only the LOW and not LOW_EB are supported in V4.60

  • 0 Arm Employee Badge in reply to Tom P

    No, this is not the same ;) Documentation is referring to the "drive" as FlashFS N: drive, which is used to manage raw NAND devices.

    You are using drive M: which is used to access SD cards. SD card contains NAND controller which is managing NAND device inside of the SD card. Therefore, you don't need to know anything about SD cards internal structure and you also don't have a direct access to the NAND device inside - only controller has.

  • 0 in reply to Vladimir Umek

    Ahh I see, thank you for the clarification.

    That rules the use of LOW out for me then! Thanks for the quick replys.