I'm having a hard time making the DMASPI library to work on the Teensy 3.5.
First of all, I don't have the hardware, but I thought it should be possible to get at least one or the other feature of the library to work as intended. All tests in the library example fail on the Teensy 3.5, so I'm looking for differences in the DMA and the SPI peripherals between the Teensy 3.5 and Teensy 3.6 (because things do work on the 3.6). I can't tell if I'm not using the SPI correctly, or if it's the DMA system.
Can anyone try to point my in the right direction? Am I even using the correct defines in the library? Currently I'm using
for DMASPI0 and
for DMASPI1, assuming that I can use identical code for Teensy 3.2, 3.5 and 3.6.
First of all, I don't have the hardware, but I thought it should be possible to get at least one or the other feature of the library to work as intended. All tests in the library example fail on the Teensy 3.5, so I'm looking for differences in the DMA and the SPI peripherals between the Teensy 3.5 and Teensy 3.6 (because things do work on the 3.6). I can't tell if I'm not using the SPI correctly, or if it's the DMA system.
Can anyone try to point my in the right direction? Am I even using the correct defines in the library? Currently I'm using
Code:
#if defined(KINETISK)
for DMASPI0 and
Code:
#if defined(__MK64FX512__) || defined(__MK66FX1M0__)
for DMASPI1, assuming that I can use identical code for Teensy 3.2, 3.5 and 3.6.