Timeline for AVR diagram of functions calling, ISR and main loop share the same resource
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2019 at 11:25 | vote | accept | bielu000 | ||
| Sep 6, 2019 at 0:00 | history | tweeted | twitter.com/StackElectronix/status/1169762239366213633 | ||
| S Sep 5, 2019 at 9:09 | history | suggested | Mike | CC BY-SA 4.0 |
i edit the body
|
| Sep 5, 2019 at 8:49 | review | Suggested edits | |||
| S Sep 5, 2019 at 9:09 | |||||
| Sep 4, 2019 at 21:50 | answer | added | Dave Tweed | timeline score: 4 | |
| Sep 4, 2019 at 21:43 | comment | added | Chris Stratton | This is a little bit odd as an architecture; typically you don't have an ISR putting tasks on a queue, rather you have an ISR changing task to implement a scheduler, otherwise you have cooperative multi-tasking in the sense that you only switch when a task complete or yields. At any rate, you likely do need locking. But more importantly, you should spend some time studying how this is usually done... | |
| Sep 4, 2019 at 21:25 | history | asked | bielu000 | CC BY-SA 4.0 |