FDS CRC errors

[nrbrook]

We have a firmware using FDS with #define FDS_CRC_CHECK_ON_READ 1 and #define FDS_CRC_CHECK_ON_WRITE 1.

In my testing it works fine, but for another engineer in a different location they are seeing a lot of CRC errors (0x860C) with multiple devices, and eventually the flash seems to get full. What can cause CRC errors? I suspected low voltage supply, but we haven't confirmed or rejected that theory yet.

[Einar Thorsrud]

It is so that you never see this issue while your colleague see it repeatedly, right? Are there any differences in your setup? Both with regards to HW, but also importantly, the firmware? Are you able to reproduce the corruption issue if you use the exact firmware as him and test in the exact same way (so that you could potentially trigger the same bug)?

Also, do you see CRC errors on write or read (or both)? If you see them on write, that could indicate an issue with the source buffer, for instance that it is modified before the flash operation has completed. But if it is successfully written with data intact, and is subsequently corrupted, that would be something else.

Have you inspected the corrupt data to see if there is a pattern there?

Regarding the nrfjprog issues it could be that it is related, but it could also be independent issues. Is it so that it always work with JFlash, or is it a perceived difference in how often the issue occurs? Does it help to for instance connect the USB cable from the debugger directly to the computer and not via a USB hub, or use a different computer?