| commit | 3172be80a3e14f4c8c3628a37db348c04fd60fc4 | |
| author | David Brownell <dbrownell@users.sourceforge.net> | |
| Wed, 27 Jan 2010 21:47:48 +0000 (27 13:47 -0800) | ||
| committer | David Brownell <dbrownell@users.sourceforge.net> | |
| Wed, 27 Jan 2010 21:47:48 +0000 (27 13:47 -0800) | ||
| tree | 17920235e9f192ca945e3a024d7ef78f09a6564d | treesnapshot (tar.gz zip) |
| parent | d44f1aaeff45d26348826bdff07caf3d097eca15 | commitdiff |
Cortex-M3: report lockup, and recover
ARMv7-M defines a "lockup" state that's entered in certain double
fault sequences which can't be recovered from without external help.
OpenOCD has previously ignored this.
Issue a diagnostic saying the chip has locked up, and force exit
from this state by halting the core. It's not clear this is the
best way to handle lockup; but there should now be less confusion.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
ARMv7-M defines a "lockup" state that's entered in certain double
fault sequences which can't be recovered from without external help.
OpenOCD has previously ignored this.
Issue a diagnostic saying the chip has locked up, and force exit
from this state by halting the core. It's not clear this is the
best way to handle lockup; but there should now be less confusion.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
| src/target/cortex_m3.c | diffblobblamehistory |