RE: Multilink - Causing Hardfaults

RK — Thu, 26 May 2016 23:59:52 GMT

Why don't you stick to the original thread about this problem instead of creating a second one, especially as the previous one actually has lots of good details and analysis in it and was possibly heading towards a result. Hardfaults are hard, especially the occasional ones.

And the answer to this question is an emphatic no, as I was going to say in a reply to the previous one. In fact all the speculation about interrupts there is going in the wrong direction and is just guesswork. If the MCU is servicing an interrupt then even if that same interrupt, or any of the same or lower priority, is raised, it won't be taken until after the handler returns from the first one. And you also ask there if a higher priority interrupt occurred and how would you stop that, and the answer to that is it doesn't matter if it did and you can't stop it nor would you want to. That's the point of interrupt priorities and the ARM is perfectly capable of stacking the state of the lower priority ones to take the higher ones and return back to where it came from.

Now we've sorted out where the PC actually is on the exception stack I'll go look at the other thread again later and see if it makes any more sense now.