quiver

Just busy talking to myself over here but realised two things.. firstly that bit-banging would be even more difficult as I'd have to do it on the clock line also. Secondly as SPI data has no start and stop bits like serial, I could just have a...

OK. Sorted roadblock A. I was inadvertently overflowing the buffer, which caused a string of other issues. So now I'm just trying to do 9-bit DMA SPI writes (from an 8-bit array). Bit-banging a single high bit between writes seems to be the most...

Further investigation.. this is the line in SPI.cpp where it faults the 2nd time:_dmaRX->TCD->ATTR_SRC = 0;

I've tried creating a local buffer in my main program code so I control the setup of it, and using memcpy to shift the buffer into it before directing SPI.transfer to it (proving that the buffer is copying correctly but using my SPI.transfer9 fn...

Sure, here's the report: CrashReport: A problem occurred at (system time) 7:12:34 Code was executing from address 0xB28A CFSR: 82 (DACCVIOL) Data Access Violation (MMARVALID) Accessed Address: 0x27 Temperature inside the...

I've been using a 256x64 display in one of my designs for some years now and it's been great, but I'm limited to 20MHz SPI and that makes a full screen write a touch over 4ms for 9-bit. It's 9-bit because I don't use a D/C pin, I run the display...