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

Use reference to mailing list for known arm926ejs bugs rather fill The List with lots of details 

git-svn-id: svn://svn.berlios.de/openocd/trunk@2490 b42882b7-edfa-0310-969c-e2dbd0fdcd60
This commit is contained in:
oharboe 2009-07-07 11:32:58 +00:00
parent f56c2db5a7
commit 8ba6f13067
1 changed files with 2 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
TODO
View File

@ -22,24 +22,9 @@ https://lists.berlios.de/pipermail/openocd-development/2009-July/009206.html
- reset run/halt/step for arm926ejs is not robust. Needs lots of testing to
map out problems.
- i.MX27 reset run problems. Notice below that even if the target is running,
a EICE_DBG_STATUS_DBGACK(I think...) is detected and OpenOCD wrongly believes that the
target is halted. Polling the target afterwards reveals that the
target is running. Notice the MOE=0xe value.
> reset run
JTAG tap: imx27.bs tap/device found: 0x1b900f0f (mfg: 0x787, part: 0xb900, ver: 0x1)
JTAG Tap/device matched
JTAG tap: imx27.cpu tap/device found: 0x07926121 (mfg: 0x090, part: 0x7926, ver: 0x0)
JTAG Tap/device matched
WARNING: unknown debug reason: 0xe
target state: halted
target halted in ARM state due to debug-request, current mode: User
cpsr: 0x00000000 pc: 0xffffffe8
MMU: disabled, D-Cache: disabled, I-Cache: disabled
- i.MX27 reset run problems.
https://lists.berlios.de/pipermail/openocd-development/2009-July/009240.html
@section thelisttcl TCL