From 00815f2db444a65e7e5cfc9c3168d355623aa342 Mon Sep 17 00:00:00 2001
From: Richard Allen <rsaxvc@gmail.com>
Date: Sat, 3 Jun 2017 00:48:51 -0500
Subject: [PATCH] Manually manage FIFO volatility

Replace volatile with properly placed __sync_synchronize

SPI1W0 is volatile, but when writing multiple words
to the FIFO (which is really just a piece of SRAM),
we don't need to worry about write ordering. We only
need worry about write ordering such that all FIFO
words are written completely before HSPI is told to
use FIFO by setting SPI1CMD |= SPIBUSY;
---
 libraries/SPI/SPI.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libraries/SPI/SPI.cpp b/libraries/SPI/SPI.cpp
index a5638d9c6..08e08f9cc 100644
--- a/libraries/SPI/SPI.cpp
+++ b/libraries/SPI/SPI.cpp
@@ -398,7 +398,7 @@ void SPIClass::writeBytes_(uint8_t * data, uint8_t size) {
     // Set Bits to transfer
     setDataBits(size * 8);
 
-    volatile uint32_t * fifoPtr = &SPI1W0;
+    uint32_t * fifoPtr = (uint32_t*)&SPI1W0;
     uint32_t * dataPtr = (uint32_t*) data;
     uint8_t dataSize = ((size + 3) / 4);
 
@@ -408,6 +408,7 @@ void SPIClass::writeBytes_(uint8_t * data, uint8_t size) {
         fifoPtr++;
     }
 
+    __sync_synchronize();
     SPI1CMD |= SPIBUSY;
     while(SPI1CMD & SPIBUSY) {}
 }