interesting
/
riscv-openocd
mirror of https://github.com/riscv/riscv-openocd.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix certain arm926ejs targets(e.g. i.MX27) which report an unknown MOE(method of entry) - interpret this as dbgrq. "reset run" + "halt" + "step" now works. 

git-svn-id: svn://svn.berlios.de/openocd/trunk@2479 b42882b7-edfa-0310-969c-e2dbd0fdcd60
This commit is contained in:
oharboe 2009-07-06 14:25:25 +00:00
parent 56944ac1c8
commit d5e183c31f
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/target/arm926ejs.c
View File

@ -360,20 +360,21 @@ int arm926ejs_examine_debug_reason(target_t *target)
* openocd development mailing list if you have hardware * openocd development mailing list if you have hardware
* to donate to look into this problem.... * to donate to look into this problem....
*/ */
LOG_ERROR("mystery debug reason MOE = 0xc. Try issuing a resume + halt."); LOG_WARNING("WARNING: mystery debug reason MOE = 0xc. Try issuing a resume + halt.");
target->debug_reason = DBG_REASON_DBGRQ; target->debug_reason = DBG_REASON_DBGRQ;
retval = ERROR_TARGET_FAILURE;
break; break;
default: default:
LOG_ERROR("BUG: unknown debug reason: 0x%x", debug_reason); LOG_WARNING("WARNING: unknown debug reason: 0x%x", debug_reason);
/* Oh agony! should we interpret this as a halt request or
* that the target stopped on it's own accord?
*/
target->debug_reason = DBG_REASON_DBGRQ; target->debug_reason = DBG_REASON_DBGRQ;
/* if we fail here, we won't talk to the target and it will /* if we fail here, we won't talk to the target and it will
* be reported to be in the halted state */ * be reported to be in the halted state */
retval = ERROR_TARGET_FAILURE;
break; break;
} }
return retval; return ERROR_OK;
} }
uint32_t arm926ejs_get_ttb(target_t *target) uint32_t arm926ejs_get_ttb(target_t *target)