Use 64M Flash to make FAT32 FS, open Writeback mode(NRF_BLOCK_DEV_QSPI_FLAG_CACHE_WRITEBACK), write 1M file "1.txt", "2.txt" in order, use Windows PC to check the prompt "1.txt" damaged.
Environment:SDK15 usbd_msc project
Use 64M Flash to make FAT32 FS, open Writeback mode(NRF_BLOCK_DEV_QSPI_FLAG_CACHE_WRITEBACK), write 1M file "1.txt", "2.txt" in order, use Windows PC to check the prompt "1.txt" damaged.
Environment:SDK15 usbd_msc project
Hi,
Did you have USB connected when writing?
Here is the documentation for the example: USB MSC Example
It states this:
This example allows you to manipulate the file system (on QSPI memory) only while USB is not connected. If USB is connected, access to the file system from a user application is not possible because MSC is not designed to allow access to the file system from multiple sources.
Best regards,
Håkon
Hi,
Did you have USB connected when writing?
Here is the documentation for the example: USB MSC Example
It states this:
This example allows you to manipulate the file system (on QSPI memory) only while USB is not connected. If USB is connected, access to the file system from a user application is not possible because MSC is not designed to allow access to the file system from multiple sources.
Best regards,
Håkon
Hi,
USB is disconnected.
This issue is happened in the above operation.
Which version of the nRF52840-DK do you have? Note that In SDK v15, workarounds for engineering A were removed, so it will not work as intended.
Hi,
Thank you for your replay.
It has nothing to do with the nrf52840-dk version. I was connected to another 64M Flash chip and changed the IO port.
I have checked and checked the various situations. It is indeed a problem with the FAT file system.