SPIM3 tx data corruption, byte carried over from previous operation.

RE: SPIM3 tx data corruption, byte carried over from previous operation.

Anthony Ambuehl — Mon, 24 Feb 2025 22:09:29 GMT

I gave up and switch to the older/slower version of the SPIM peripheral. If I have time and client is willing to pay I'll spend time trying to figure it out.

RE: SPIM3 tx data corruption, byte carried over from previous operation.

Einar Thorsrud — Mon, 20 Jan 2025 13:45:27 GMT

Hi,

There are some unfortunate issues with SPIM3. In this case, I wonder if it would help to use double-buffering and ensure that the buffers are on separate RAM sections, as shown in this post?

RE: SPIM3 tx data corruption, byte carried over from previous operation.

Anthony Ambuehl — Fri, 17 Jan 2025 21:42:05 GMT

To confirm that this is a bug with SPIM3, I switched to SPIM2 and have not been able to repeat the failure after many 10's of minutes of testing. SPIM3 usually fails within 4-8 minutes..

I've read multiple posts where people just give up on SPIM3 and switch to an older style SPIM with the 8 MHz limit. Its frustrating to spend time on stuff that is clearly broken.