• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 465 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Data damaged when loading from SD-card / FatFS

qxc
Genius 5820 points

Hi,

I found a problem when loading larger amounts of data from SD-card: In some cases some of the bytes are damaged (mainly first byte and some data in between). Now I found this happens only when data blocks with a size larger than 511 bytes are loaded. Changing my code in a way so that this limit is not exceeded (loading larger data by using repeted calls to f_read()) solves the problem.

The funny thing: in MLO code that comes with Starterware this 511 bytes limitation is already taken into account, the APP-file is loaded using repeated read-calls with sizes of max. 511 bytes.

So my question: what causes this limitation? It is the same value like the FatFS blocksize...so is the MLO-solution some workaround for buggy code or how can one explain this?

Thanks!