X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=TODO;h=0d6331eb86eab6cedffa29ae7a9da19bd97cda5e;hb=7a1ac49ac921964f48e0bbd9e1bf0d151d99b17e;hp=0922c663ca002416b26119a6ce39f1e893b7141c;hpb=587aa648509c90ef4fdae5b2dea7ed9664ba50eb;p=openocd.git

diff --git a/TODO b/TODO
index 0922c663ca..0d6331eb86 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,4 @@
+// This file is part of the Doyxgen Developer Manual
 /** @page tasks Pending and Open Tasks
 
 This page lists pending and open tasks being considered or worked upon
@@ -11,36 +12,6 @@ may have evolved an idea since it was added here.
 
 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.
@@ -68,11 +39,16 @@ This section list issues that need to be resolved in the JTAG layer.
 
 @subsection thelistjtagcore JTAG Core
 
-The following tasks have been suggeted for cleaning up the JTAG layer:
+The following tasks have been suggested for cleaning up the JTAG layer:
 
 - use tap_set_state everywhere to allow logging TAP state transitions
 - rename other tap_states to use standard JTAG names (suggested by ML)
 - Encapsulate cmd_queue_cur_state and related varaible handling.
+- add slick 32 bit versions of jtag_add_xxx_scan() that avoids
+buf_set_u32() calls and other evidence of poor impedance match between
+API and calling code. New API should cut down # of lines in calling
+code by 100's and make things clearer. Also potentially be supported
+directly in minidriver API for better embedded host performance.
 
 The following tasks have been suggested for adding new core JTAG support:
 
@@ -129,8 +105,19 @@ Once the above are completed:
 
 - general layer cleanup: @par
   https://lists.berlios.de/pipermail/openocd-development/2009-May/006590.html
+- regression: xscale does not place debug_handler.bin into the right spot. workaround:
+  use -s option on command line to place xscale/debug_handler.bin in search path @par
+  https://lists.berlios.de/pipermail/openocd-development/2009-July/009338.html
+- bug: either USBprog is broken with new tms sequence or there is a general
+  problem with XScale and the new tms sequence. Workaround: use "tms_sequence long"
+  @par
+  https://lists.berlios.de/pipermail/openocd-development/2009-July/009426.html
+- regression: "reset halt" between 729(works) and 788(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.
 - ARM11 improvements (MB?)
-  - fix single stepping  (reported by �H)
+  - fix single stepping  (reported by ØH)
   - implement missing functionality (grep FNC_INFO_NOTIMPLEMENTED ...)
 - Cortex A8 support (ML)
   - add target implementation (ML)
@@ -174,7 +161,7 @@ Once the above are completed:
 - finish implementing bus width/chip width handling (suggested by NC)
 - factor vendor-specific code into separate source files
   - add new callback interface for vendor-specific code
-- investigate/implement "thin wrapper" to use eCos CFI drivers (�H)
+- investigate/implement "thin wrapper" to use eCos CFI drivers (ØH)
 
 @section thelistdebug Debugger Support