Search results

Fair enough. I intend to test it myself too, probably later today. The entire struct is volatile, so any operation on any field in the struct that might normally get optimized (e.g. setting a bit and then clearing it again) won't (shouldn't) get optimized away because of the volatile keyword...

??? I'm not sure what you're referring to, but I used the same code as you did to calculate the address, based on the _portnum member variable. The only difference is that I cast the pointer to a volatile IMXRT_LPSPI_t pointer instead of a volatile uint32_t. Would you care to comment on my...

available() has a bug? Hey @tonton81, I'm working on adding slave mode to all the Teensy's, using your libraries (TSPISlave and SPISlave_T4) as inspiration. Thank you very much for writing them! I noticed that your "available()" function in the SPISlave_T4 library uses the following code...