Timeline for Triggering an SPI transfer with an interrupt in Arduino Due
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2019 at 0:03 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 21, 2018 at 0:01 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 20, 2018 at 23:18 | answer | added | Curt Nichols | timeline score: 1 | |
| Nov 20, 2018 at 13:23 | comment | added | shz |
@Majenko I thought that the SPI.usingInterrupt is specifically for that purpose// If SPI is used from within an interrupt, this function registers // that interrupt with the SPI library, so beginTransaction() can // prevent conflicts. The input interruptNumber is the number used // with attachInterrupt. If SPI is used from a different interrupt // (eg, a timer), interruptNumber should be 255. static void usingInterrupt(uint8_t interruptNumber);
|
|
| Nov 19, 2018 at 19:41 | comment | added | Majenko | I am not familiar with the internal workings of the Due SPI library to be sure though. Best to be safe and not do SPI in an interrupt regardless. | |
| Nov 19, 2018 at 19:40 | comment | added | Majenko | Probably SPI transfers use an interrupt, which can't trigger because you're already in an interrupt. You should have the SPI operations outside the interrupt and just update some variables and set a flag in your interrupt. | |
| Nov 19, 2018 at 19:40 | review | First posts | |||
| Nov 19, 2018 at 21:31 | |||||
| Nov 19, 2018 at 19:36 | history | asked | shz | CC BY-SA 4.0 |