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

fformat on SD card

Hi,

I'm having some trouble with the fformat function from the FlashFS library...I think.

I have >50 Qty of a PCBA design, each running the same code. The PCBA has an M3 processor and it interfaces to an SD card using the parallel interface. The code running on each of the boards is the same.

On ~10% of the boards the fformat function will not work. On the other 90% the function works OK. On all of the systems the fwrite, fdelete, fopen, fclose, fputc and fgetc functions work ok.

Changing and moving SD cards from the working to failing PCBAs has no effect and the fault stays with the PCBA.

Where can I find more information on the fformat function other then the following? http://www.keil.com/support/man/docs/rlarm/rlarm_fformat.htm

Does anybody know whether the fformat function uses or does something that the other function's don't?

Does anybody feel it is more likely to be a hardware fault rather then software? I've checked all lines with an oscilloscope and they seem OK.

Any views to help move me forward would be appreciated.

Tom

Parents
  • I've noted that the functions that work on all of the boards (fwrite, fclose, fputc ect ect) are all File I/O routines but the fformat function is a File Maintenance routine.

    Although finit seems to work OK which is also a File Maintence routine.

Reply
  • I've noted that the functions that work on all of the boards (fwrite, fclose, fputc ect ect) are all File I/O routines but the fformat function is a File Maintenance routine.

    Although finit seems to work OK which is also a File Maintence routine.

Children
  • hi
    I had a quite similar experience with LPC1788, all file Maintenance routines like finit and fformat did work,but fopen or other did not,the problem was vanished when i change the library files that I was using,I tried fatfs and it did work,
    although variety of problems that you mentioned make me believe that there is a problem with hardware or sd cards at the very first moment,but I still wanna to say that maybe a small software matter is responsible for this mess.
    Regards,
    Hessam