usb msc corruption on nrf52840

[Blance]

Hello:

I asked a question a few months ago

https://devzone.nordicsemi.com/f/nordic-q-a/54708/about-nrf52840-save-file-error

However, the follow-up did not get an answer, it may be that the way of asking is not good

I recently thought of this doubt again and found that this question was raised a long time ago

https://devzone.nordicsemi.com/f/nordic-q-a/39428/usb-msc-corruption

However, there seems to be no clear answer at the time of reading the content. Is there an answer now?

The formatting section has been adjusted according to the recommendations. The test looks normal in the root directory, but if you open a folder (such as "Data") and change the archive location of the test file to this folder, you have a chance to reproduce the problem.

[Sigurd]

Hi,

In the first case you are referring to, the last reply was a suggestion to try to "move the "ff_result = f_sync( & file);" outside the for-loop (for (uint16_t i = 0; i < 96; i++)".

A part from that, we are currently looking into some USB MSC issues described in this post: https://devzone.nordicsemi.com/f/nordic-q-a/61704/nrf52840-usb_msc-demo-fatfs-error

[Blance]

I have tried this method. It is true that a file is only opened and closed once. The content is usually ok. But my application will save about 4k bytes into the file every minute. And I hope that the file room is closed during the period, so coding like this

[Sigurd]

Blance said:

But my application will save about 4k bytes into the file every minute.

 So you are then calling f_sync() after 4k bytes is saved ? And that works?

If not, could you try the workaround from this link? https://devzone.nordicsemi.com/f/nordic-q-a/61704/nrf52840-usb_msc-demo-fatfs-error/253842#253842