• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 39 subscribers
  • Views 448 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/CC3220S-LAUNCHXL: Filesystem behaviour when a sector is damaged.

Zac
Genius 3100 points
Part Number: CC3220S-LAUNCHXL

Tool/software: TI-RTOS

I understand that a typical serial flash ensures a data endurance of 100K write cycles per sector and beyond that the sector may becomes unusable. If such situation occurs and some sectors are damaged, how will the SL file system behaves while creating new files ?

Will it skip any bad sectors and allocated available good sectors for new files or would it fail creating files when a bad sector is encountered ?

Using SL operation, can we select the sectors to be used while creating file ?

  • 0
    TI__Guru 64455 points

    Hello,

    In a nuttshell, there is no bad sector detection in the file system.

    The only way is to follow the "good practice" instructions as appears on the NWP guide, paragraph 8.15.2 Software Design Consideration and 8.15.3/8.15.4.

    You also have a way to retrieve the write counter of a file when getting the file info. You should monitor this counter to not reach the limit.

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Genius 3100 points
    Thanks Shlomi,
    I may be sounding ignorant here, but if I reach the limit of a sector can I create another file on a different sector ?
    I mean how is the sector allocated while creating files ?

    Thanks for your support.
    Regards
    Zac
  • 0 in reply to Zac
    TI__Guru 64455 points

    Hello,

    This is all internal implementation.

    Basically, upon file creation, the file system manager is looking for the smaller memory hole that can fit to the size you are asking to alloacte.

    This is in order to reduce as much as possible the probability for unused memory locations (as there is no fragmentation feature).

    Regards,

    Shlomi