Timeline for SPI Arduino Due conflict with pinMode(), bug?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 29, 2015 at 21:38 | history | suggested | dda | CC BY-SA 3.0 |
Spelling, grammar
|
| Nov 28, 2015 at 11:03 | review | Suggested edits | |||
| S Nov 29, 2015 at 21:38 | |||||
| Jun 1, 2015 at 5:24 | answer | added | CharlieHanson | timeline score: 1 | |
| Nov 10, 2014 at 7:30 | history | edited | newandlost | CC BY-SA 3.0 |
deleted 31 characters in body
|
| Nov 7, 2014 at 9:23 | comment | added | newandlost | @Gerben I modified my post | |
| Nov 7, 2014 at 9:22 | history | edited | newandlost | CC BY-SA 3.0 |
added 219 characters in body
|
| Nov 6, 2014 at 21:34 | comment | added | newandlost | Ja you are right, by accident I am calling setDataMode() twice. Tomorrow I will test the effect of SPI.setDataMode(10, SPI_MODE1); But why calling pinMode() has this effect is still not clear or? @Gerben | |
| Nov 6, 2014 at 19:05 | history | tweeted | twitter.com/#!/StackArduino/status/530435839726485504 | ||
| Nov 6, 2014 at 17:06 | comment | added | Gerben |
Shouldn't it be SPI.setDataMode(10, SPI_MODE1);? Also only the second one is useful, as begin() calls setDataMode. Looking at the source code it looks like the SPI library doesn't alter the pin you specified (though I don't know ARM).
|
|
| Nov 6, 2014 at 16:01 | history | asked | newandlost | CC BY-SA 3.0 |