xxxajk
Well-known member
What was the ambient temp?max CPU surface temp I see is 101.4°F and I see 97°F max on the ethernet shield.
What was the ambient temp?max CPU surface temp I see is 101.4°F and I see 97°F max on the ethernet shield.
What was the ambient temp?
@PaulStoffregen I take pin32 will be connected to a USB power switch, such as MIC2004? VBUS power on the board I have does not change, but I can add this on mine.
Paul: Again not sure if you are interested in having the user be use the 6 pins for the SDCARD, but in case you might, I did do a Pull request for CORES and SPI projects
Understood, it is your baby!My main intention is for those 6 pins to be dedicated to SDIO mode.
At this moment I'm swamped in bed-of-nails test fixture details. But very soon I want to integrate simple SDIO code into the SD library. Still debating how the API should work, but will likely go with some name to use with SD.begin() instead of the normal CS pin number.
... See #93 for all pinout info.
Glad post #8 was useful. Is that 4 bus code posted as a sample? With Ethernet it looks like pins are clear for I2C[0,1,3] but I2C2 and ALT's all conflict.
Nice!Yes, there is a loopback example, which when compiled for T3.6 will use all 4 buses. It assumes they are all tied together with external pullup.
I totally missed this one! So the DMASPI library needs some work again... Paul, I'll get back to you when I can work on it. Which is not now, unfortunately.
The example included with the library is just a collection of multiple loopback tests, so connecting DIN to DOUT is enough. Adding other hardware would just make the demonstration harder to replicate by others, so I never expanded it.Yes - I started to look at it, but have not used it so not sure if there are good examples that make use of it to try out, like a version of one of the TFT displays that use it? Or other hardware? Or test between two Teensy processors?
Adding an additional SPI for the Teensy LC wasn't too hard, so I don't think it will be much of a problem with the 3.6.That is the New boards have 3 SPI ports, so would need another abstracted object for SPI2. Also not sure how your CS object works and if you always use one or not. If not, there are hard coded calls to SPI.beginTransaction and SPI.endTransaction which need to instead call SPI1. or SPI2. versions.
#if defined(__MK64FX512__) || defined(__MK66FX1M0__)
If you look at SPI.h in the release it has a lot of the stuff. Example to test for either of the new boards:
Code:#if defined(__MK64FX512__) || defined(__MK66FX1M0__)
Where __MK64FX512__ will be for the 3.5 and the __MK66FX1M0__ is for the 3.6 boards we are currently testing.
So if you are not using CS objects, then my guess is that the code may not work properly on SPI1 as I believe it will call SPI.beginTransaction() and SPI.endTransaction() instead of SPI1.beginTransaction, so it may not be setting up the correct CTAR register.
I updated the DMASPI library and the post above. If anyone wants to give it a try, go ahead! The example should work with SPI0 DIN connected to SPI0.DOUT, giving serial output about the progress. I don't have the board so I couldn't run *any* test. If you try it, please post any results here. Even if it's just "the board hangs and seems to be silent".
Hi!
Buffers are prepared
Time for non-DMA transfer: 226us
src and dest match
Press a key to continue
Testing src -> dest, single transfer
--------------------------------------------------
Finished DMA transfer
src and dest match
==================================================
Testing src -> discard, single transfer
--------------------------------------------------
Finished DMA transfer
last discarded value is 0x63
That appears to be correct
==================================================
Testing 0xFF dummy data -> dest, single transfer
--------------------------------------------------
Finished DMA transfer
src and dest match
==================================================
Testing multiple queued transfers
--------------------------------------------------
Finished DMA transfer
Finished DMA transfer1
src and dest match
src and dest match
==================================================
Testing pause and restart
--------------------------------------------------
Time until stopped: 220 us
Finished DMA transfer
DMA SPI appears to have stopped (this is good)
restarting
Finished DMA transfer1
src and dest match
src and dest match
==================================================
Testing src -> dest, with chip select object
--------------------------------------------------
Finished DMA transfer
src and dest match
==================================================
DMA SPI is still running
DMA SPI stopped.