On Tue, 2009-07-07 at 12:33 +0200, Øyvind Harboe wrote: > Committed to TODO: > > - 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. > > > 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
Please do not use the TODO file for detailed bug reports like this; your post to the list could have easily been referenced, eliminating the bulk of the content. Also, test your changes before you commit them; it was clear that you did not try to view the results of your additions. The attached patch tries to fix the problems by linking to the mailing list in lieu of the report, and I moved everything into the section where it belonged. The entire file is a list of regressions, bugs, or features that are grouped by their place in the stack. At some point, we can switch to a real bug system that will allow us to sort these items any way we want. Thanks, Zach
Index: TODO =================================================================== --- TODO (revision 2488) +++ TODO (working copy) @@ -11,36 +11,6 @@ Feel free to send patches to add or clarify items on this list, too. -...@section thelisttcl Regressions - -- Dominic has spotted a "reset halt" regression between 838(fails) and 729(works) - -https://lists.berlios.de/pipermail/openocd-development/2009-July/009206.html - -...@section thelisttcl Bugs - -- 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 - - - - @section thelisttcl TCL This section provides possible things to improve with OpenOCD's TCL support. @@ -129,6 +99,13 @@ - general layer cleanup: @par https://lists.berlios.de/pipermail/openocd-development/2009-May/006590.html +- regression: "reset halt" between 729(works) and 838(fails): @par +https://lists.berlios.de/pipermail/openocd-development/2009-July/009206.html +- ARM923EJS: + - reset run/halt/step is not robust; needs testing to map out problems. +- i.MX27 + -reset run problems: @par +https://lists.berlios.de/pipermail/openocd-development/2009-July/009240.html - ARM11 improvements (MB?) - fix single stepping (reported by �H) - implement missing functionality (grep FNC_INFO_NOTIMPLEMENTED ...)
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
