You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

151 lines
5.7 KiB

  1. /** @page thelist Pending and Open Tasks
  2. This page lists pending and open tasks being considered or worked upon
  3. by the OpenOCD community.
  4. Items with a current patch available should include a link to its
  5. posting on the openocd-developer mailing list archives.
  6. Some items may be in progress, usually indicated by the individual whose
  7. initials in parentheses following it. A key for decoding these initials
  8. appears after The List.
  9. Most items are open for the taking, but please post to the mailing list
  10. before spending much time working on anything lists here. The community
  11. may have evolved an idea since it was added here.
  12. Feel free to send patches to add or clarify items on this list, too.
  13. @verbatim
  14. ==================================================================
  15. The List
  16. ------------------------------------------------------------------
  17. @endverbatim
  18. - JTAG/TAP changes:
  19. - update all drivers to use tap_get_tms_path_len API.
  20. - use tap_set_state everywhere to allow logging TAP state transitions
  21. - rename other tap_states to use standard JTAG names (suggested by ML)
  22. - retire jtag_add_end_state() and replace w/global variable. This also
  23. removes TAP_INVALID as an argument to jtag_add_xxxx(). The global variable
  24. as argument to jtag_add_xxxx() should eventually be phased out, but
  25. the global variable is useful in an interim phase where one needs to
  26. be bug by bug compatible before each change can be tested. Suggested
  27. by ØH. Michael Bruck also interested in this.
  28. - JTAG Interfaces:
  29. - autodetect devices present on the scan chain
  30. - implement 'discover_taps' command
  31. - FT2232 driver: (DH)
  32. - integrate FTD2XX High-Speed Device support
  33. - PATCH: https://lists.berlios.de/pipermail/openocd-development/2009-April/005479.html
  34. - massive set of changes (DH):
  35. - fixes non-recoverability of cable connect/reconnect
  36. - https://lists.berlios.de/pipermail/openocd-development/2009-May/006011.html
  37. - further cleanup (DH):
  38. - PATCH: https://lists.berlios.de/pipermail/openocd-development/2009-May/006112.html
  39. - fix outstanding bugs
  40. - J-Link driver: (ZW)
  41. - fix outstanding bugs
  42. - test with known targets (i.e. working with other interfaces)
  43. - test compatibility between v6.0 (yellow) and older units (e.g. v5.2)
  44. - TCP driver:
  45. - add TCP/IP client and server for remote JTAG interface control
  46. - Do others need some help? Probably....
  47. - Other Interfaces
  48. - SVF/XSVF:
  49. - pending tasks??
  50. - SPI/UART emulation:
  51. - (ab)use bit-banging JTAG interfaces to emulate SPI/UART
  52. - allow SPI to program flash, MCUs, etc.
  53. - SWD
  54. - Target Support:
  55. - general layer cleanup:
  56. - https://lists.berlios.de/pipermail/openocd-development/2009-May/006590.html
  57. - ARM11 improvements (MB?)
  58. - fix single stepping (reported by ØH)
  59. - implement missing functionality (grep FNC_INFO_NOTIMPLEMENTED ...)
  60. - Cortex A8 support (ML)
  61. - add target implementation (ML)
  62. - what else remains to be done?
  63. - MC1322x support (JW/DE?)
  64. - integrate and test support from JW (and DE?)
  65. - get working with a known good interface (i.e. not today's jlink)
  66. - AT91SAM92xx:
  67. - improvements for unknown-board-atmel-at91sam9260.cfg (RD)
  68. - STR9x: (ZW)
  69. - improvements to str912.cfg to be more general purpose
  70. - AVR: (SQ)
  71. - independently verify implementation
  72. - incrementally improve working prototype in trunk. (SQ)
  73. - work out how to debug this target
  74. - AVR debugging protocol.
  75. - FPGA:
  76. - improve things (??)
  77. - Coldfire (suggested by NC)
  78. - can we draw from the BDM project? @par
  79. http://bdm.sourceforge.net/
  80. - other targets? (suggestions always welcome)
  81. - CFI:
  82. - finish implementing bus width/chip width handling (suggested by NC)
  83. - factor vendor-specific code into separate source files
  84. - add new callback interface for vendor-specific code
  85. - investigate/implement "thin wrapper" to use eCos CFI drivers (ØH)
  86. - TCL
  87. - Isolate all TCL command support:
  88. - Allow pure C CLI implementations using --disable-builtin-tcl.
  89. Ref? How could this be made to work given targets extensive need
  90. for events, etc.? What about the target library?
  91. - Allow full TCL support? add --with-tcl=/path/to/installed/tcl
  92. - Move TCL support in foo.* to foo_tcl.* (other ideas?)
  93. - Debugger Support
  94. - Keil AGDI interface to OpenOCD (submitted by Dario Vecchio)
  95. - Architectural Upgrades
  96. - Allow N:M:P mapping of servers, targets, and interfaces
  97. - loadable module support for interface/target/flash drivers
  98. - libopenocd support: @par
  99. https://lists.berlios.de/pipermail/openocd-development/2009-May/006405.html
  100. - Test Suite:
  101. - implement server unit tests
  102. - implement JTAG core unit tests
  103. - implement JTAG interface unit tests
  104. - implement flash unit tests
  105. - implement target unit tests
  106. - Test Feedback Tools: @par
  107. https://lists.berlios.de/pipermail/openocd-development/2009-May/006358.html
  108. - extend target test script to produce helpful pass/fail output
  109. - provide results submission script
  110. - Generic Hardware Tester:
  111. - implement VHDL to use for FPGA-based JTAG TAP testing device
  112. - develop test suite that utilizes this testing device
  113. - Build Systems (Autotools, CMake, etc.)
  114. - investigate fixes to permit the use of -Wshadow
  115. - change bootstrap to call 'configure --enable-maintainer-mode <opts>'?
  116. - Miscellaneous:
  117. - make JTAG and USB debug output a run-time configuration option
  118. - review and clean up interface/target/flash APIs
  119. - factor code to eliminate duplicated functionality
  120. - overhaul use of types to improve 32/64-bit portability
  121. - Berlios Admin:
  122. - use patch tracker? @par
  123. https://developer.berlios.de/patch/?group_id=4148
  124. - use bug tracking? we need something!
  125. */