[FATFS] FA_OPEN_APPEND destroy first file content

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Håkon Alseth — Tue, 08 Sep 2020 07:59:00 GMT

This case is almost 2 years old, and is based on an older SDK. Could you create a new thread with your issue? Remember to describe which device you're using (and revision of it), as well as which SDK is in use.

Kind regards,

Håkon

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Constantin — Fri, 04 Sep 2020 11:40:22 GMT

We are facing the same issue. Writing into the SD card is just fine and when we plug the SD card directly in to the PC it is fine. But when we read via the msc it is corrupted there are some lines destroyed.

Did you had a solution for this problem?

RE: [FATFS] FA_OPEN_APPEND destroy first file content

JeffW — Fri, 12 Oct 2018 12:42:35 GMT

I am running into a very similar issue.

I have implemented the two known issue fixes, but was getting corruption on FATFS in the header of a file just by f_printf's.

I have since switched to exFat, the corruption no longer occurs in the top line of the text file, but deletes about 10 lines of log in the middle of the file, inserting many symbols and characters. This is very reproducible in my experimentation.

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Håkon Alseth — Thu, 23 Aug 2018 07:49:03 GMT

I have tried to recreate this issue at my end, but I am not able to see any corruption in the files.

Do you see the same problem if you do this on other computers as well?

Could you also tell me which version of the PCA10056 you have?

Kind regards,

Håkon

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Bartek — Wed, 22 Aug 2018 08:44:58 GMT

Logs from device:

[00:00:00.000,000] <info> app: Initializing disk 0 (QSPI)...
[00:00:00.000,000] <info> app: Mounting volume...
[00:00:00.000,000] <error> app: Mount failed. Filesystem not found. Please format device.
[00:00:00.000,000] <info> app: USBD MSC example started.
[00:00:00.000,000] <info> app: 
Creating filesystem...
[00:00:00.000,000] <info> app: Mounting volume...
[00:00:00.000,000] <info> app: Done
[00:00:00.000,000] <info> app: 
Listing directory: /
Entries count: 1
Creating file: f1.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f1.txt
done
Creating file: f1.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f1.txt
done
Creating file: f1.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f1.txt
done
Creating file: f2.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f2.txt
done
Creating file: f2.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f2.txt
done
Creating file: f2.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f2.txt
done
Creating file: f3.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f3.txt
done
Creating file: f3.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f3.txt
done
Creating file: f3.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f3.txt
done
[00:00:00.000,000] <info> app: USB power detected
[00:00:00.000,000] <info> app: Un-initializing disk 0 (QSPI)...
[00:00:00.000,000] <info> app: USB ready

File content:

[bartek:/run/media/bartek/4821-0000] $ xxd F1.TXT 
00000000: 4428 2864 1000 6440 2000 0002 4021 6a44  D((d..d@ ...@!jD
00000010: 030a                                     ..
[bartek:/run/media/bartek/4821-0000] $ xxd F2.TXT 
00000000: 6c69 6e65 310a 6c69 6e65 320a 6c69 6e65  line1.line2.line
00000010: 330a                                     3.
[bartek:/run/media/bartek/4821-0000] $ xxd F3.TXT 
00000000: 6c69 6e65 310a 6c69 6e65 320a 6c69 6e65  line1.line2.line
00000010: 330a                                     3.

When I create only one file, it works fine:

Logs form device

[00:00:00.000,000] <info> app: Initializing disk 0 (QSPI)...
[00:00:00.000,000] <info> app: Mounting volume...
[00:00:00.000,000] <info> app: 
Listing directory: /
Entries count: 1
[00:00:00.000,000] <info> app: USBD MSC example started.
[00:00:00.000,000] <info> app: 
Creating filesystem...
[00:00:00.000,000] <info> app: Mounting volume...
[00:00:00.000,000] <info> app: Done
Creating file: f1.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f1.txt
done
Creating file: f1.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f1.txt
done
Creating file: f1.txt ...[00:00:00.000,000] <info> app: 6/6 bytes written to: f1.txt
done
[00:00:00.000,000] <info> app: USB power detected
[00:00:00.000,000] <info> app: Un-initializing disk 0 (QSPI)...
[00:00:00.000,000] <info> app: USB ready

File content:

[bartek:/run/media/bartek/4821-0000] 127 $ xxd F1.TXT 
00000000: 6c69 6e65 310a 6c69 6e65 320a 6c69 6e65  line1.line2.line
00000010: 330a                                     3.

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Håkon Alseth — Wed, 22 Aug 2018 08:35:00 GMT

Hi,

I have tried your example on a PCA10056 v1.0.0, with FAT file system (+ both fixes initially mentioned), and I am not able to reproduce this issue. Could you post logs, F1.TXT content, and other failure descriptions?

Best regards,

Håkon

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Bartek — Wed, 22 Aug 2018 08:13:46 GMT

Hello,

Thanks for reply.

Of course I implemented both of fixes. They helped in described cases, but didn't help with OP issue.

I would not look for issue in USBD or QSPI libraries, since EXFAT is working fine...

RE: [FATFS] FA_OPEN_APPEND destroy first file content

Håkon Alseth — Wed, 22 Aug 2018 08:11:34 GMT

Hi,

There are two currently known issues in SDK 15 that might affect the operation of this specific example:

1. USBD: Erratas not properly applied

2. QSPI: usbd_msc example might fail if you alter files, then unplug/plug the USB

Could you ensure that these are applied, and then see if this fixes your issue?

Kind regards,

Håkon