2 ms·
Its missing a ton of information and it seems poorly presented. I found that surprising given that the author teaches the topic. In general I agree that the mo
by ChuckMcM 10y ago
Its missing a ton of information and it seems poorly presented. I found that surprising given that the author teaches the topic.
In general I agree that the most confusing part with these chips are that the ARM interrupts are all very well defined and they have clear semantics, but the vendor specific interrupts are kind of all over the place as the vendors use licensed IP from a variety of vendors and attach them to the interrupt structure in different ways.
That said, interrupts have the inherent complexity of "you were doing something and POW! now you're doing something else." which starts out weird to new programmers and then when nested interrupts are brought up their head explodes. I can imagine it is a tough topic to teach.
- rkangel 10y agoIt is missing some detail about how the interrupts operate, but: a) It's a blog post not a reference manual. It's aim appears to be clear up some confusion about terminology (and having been using a Cortex M4 for a year I've spent a fair amount of time trying to reconcile conflicting documentation). b) It's only the first blog post in an intended series. Who knows what's going to get covered next. Even though I've got most of this sorted out in my head by now, it's still helpful to me to have it put clearly in one place (even if it's just so that I have a link to give to newer members of my team).