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.
 
 
 
 
 
 

276 lines
9.9 KiB

  1. /** @page tasks Pending and Open Tasks
  2. This page lists pending and open tasks being considered or worked upon
  3. by the OpenOCD community.
  4. @section thelist The List
  5. Most items are open for the taking, but please post to the mailing list
  6. before spending much time working on anything lists here. The community
  7. may have evolved an idea since it was added here.
  8. Feel free to send patches to add or clarify items on this list, too.
  9. @section thelisttcl Regressions
  10. - Dominic has spotted a "reset halt" regression between 838(fails) and 729(works)
  11. https://lists.berlios.de/pipermail/openocd-development/2009-July/009206.html
  12. @section thelisttcl Bugs
  13. - reset run/halt/step for arm926ejs is not robust. Needs lots of testing to
  14. map out problems.
  15. @section thelisttcl TCL
  16. This section provides possible things to improve with OpenOCD's TCL support.
  17. - Fix problem with incorrect line numbers reported for a syntax
  18. error in a reset init event.
  19. - organize the TCL configurations:
  20. - provide more directory structure for boards/targets?
  21. - factor configurations into layers (encapsulation and re-use)
  22. - Isolate all TCL command support:
  23. - Pure C CLI implementations using --disable-builtin-tcl.
  24. - Allow developers to build new dongles using OpenOCD's JTAG core.
  25. - At first, provide only low-level JTAG support; target layer and
  26. above rely heavily on scripting event mechanisms.
  27. - Allow full TCL support? add --with-tcl=/path/to/installed/tcl
  28. - Move TCL support out of foo.[ch] and into foo_tcl.[ch] (other ideas?)
  29. - See src/jtag/core.c and src/jtag/tcl.c for an example.
  30. - allow some of these TCL command modules to be dynamically loadable?
  31. @section thelistjtag JTAG
  32. This section list issues that need to be resolved in the JTAG layer.
  33. @subsection thelistjtagcore JTAG Core
  34. The following tasks have been suggeted for cleaning up the JTAG layer:
  35. - use tap_set_state everywhere to allow logging TAP state transitions
  36. - rename other tap_states to use standard JTAG names (suggested by ML)
  37. - Encapsulate cmd_queue_cur_state and related varaible handling.
  38. The following tasks have been suggested for adding new core JTAG support:
  39. - autodetect devices present on the scan chain
  40. - implement 'discover_taps' command
  41. - SPI/UART emulation:
  42. - (ab)use bit-banging JTAG interfaces to emulate SPI/UART
  43. - allow SPI to program flash, MCUs, etc.
  44. @subsection thelistjtaginterfaces JTAG Interfaces
  45. The following tasks have been suggeted for improving OpenOCD's JTAG
  46. interface support:
  47. - rework USB communication to be more robust. Two possible options are:
  48. -# use libusb-1.0.1 with libusb-compat-0.1.1 (non-blocking I/O wrapper)
  49. -# rewrite implementation to use non-blocking I/O
  50. - J-Link driver:
  51. - fix to work with long scan chains, such as R.Doss's svf test.
  52. - FT2232 (libftdi):
  53. - make performance comparable to alternatives
  54. - make usability comparable to alternatives
  55. The following tasks have been suggested for adding new JTAG interfaces:
  56. - TCP driver: allow client/server for remote JTAG interface control.
  57. @section thelistswd Serial Wire Debug
  58. - implement Serial Wire Debug interface
  59. @section thelistbs Boundary Scan Support
  60. - add STAPL support?
  61. - add BSDL support?
  62. A few possible options for the above:
  63. -# Fake a TCL equivalent?
  64. -# Integrate an existing library?
  65. -# Write a new C implementation a la Jim?
  66. Once the above are completed:
  67. - add support for programming flash using boundary scan techniques
  68. - add integration with a modified gerber view program:
  69. - provide means to view the PCB and select pins and traces
  70. - allow use-cases such as the following:
  71. - @b Stimulus
  72. -# Double-click on a pin (or trace) with the mouse.
  73. - @b Effects
  74. -# The trace starts blinking, and
  75. -# OpenOCD toggles the pin(s) 0/1.
  76. @section thelisttargets Target Support
  77. - general layer cleanup: @par
  78. https://lists.berlios.de/pipermail/openocd-development/2009-May/006590.html
  79. - ARM11 improvements (MB?)
  80. - fix single stepping (reported by �H)
  81. - implement missing functionality (grep FNC_INFO_NOTIMPLEMENTED ...)
  82. - Cortex A8 support (ML)
  83. - add target implementation (ML)
  84. - MC1322x support (JW/DE?)
  85. - integrate and test support from JW (and DE?)
  86. - get working with a known good interface (i.e. not today's jlink)
  87. - AT91SAM92xx:
  88. - improvements for unknown-board-atmel-at91sam9260.cfg (RD)
  89. - STR9x: (ZW)
  90. - improvements to str912.cfg to be more general purpose
  91. - AVR: (SQ)
  92. - independently verify implementation
  93. - incrementally improve working prototype in trunk. (SQ)
  94. - work out how to debug this target
  95. - AVR debugging protocol.
  96. - FPGA:
  97. - Altera Nios Soft-CPU support
  98. - Coldfire (suggested by NC)
  99. - can we draw from the BDM project? @par
  100. http://bdm.sourceforge.net/
  101. or the OSBDM package @par
  102. http://forums.freescale.com/freescale/board/message?board.id=OSBDM08&thread.id=422
  103. @section thelistsvf SVF/XSVF
  104. - develop SVF unit tests
  105. - develop XSVF unit tests
  106. @section thelistflash Flash Support
  107. - finish documentation for the following flash drivers:
  108. - avr
  109. - ecosflash
  110. - pic32mx
  111. - ocl
  112. - str9xpec
  113. @subsection thelistflashcfi CFI
  114. - finish implementing bus width/chip width handling (suggested by NC)
  115. - factor vendor-specific code into separate source files
  116. - add new callback interface for vendor-specific code
  117. - investigate/implement "thin wrapper" to use eCos CFI drivers (�H)
  118. @section thelistdebug Debugger Support
  119. - breakpoints can get lost in some circumstances: @par
  120. https://lists.berlios.de/pipermail/openocd-development/2009-June/008853.html
  121. - integrate Keil AGDI interface to OpenOCD? (submitted by Dario Vecchio)
  122. @section thelisttesting Testing Suite
  123. This section includes several related groups of ideas:
  124. - @ref thelistunittests
  125. - @ref thelistsmoketests
  126. - @ref thelisttestreports
  127. - @ref thelisttestgenerichw
  128. @subsection thelistunittests Unit Tests
  129. - add testing skeleton to provide frameworks for adding tests
  130. - implement server unit tests
  131. - implement JTAG core unit tests
  132. - implement JTAG interface unit tests
  133. - implement flash unit tests
  134. - implement target unit tests
  135. @subsection thelistsmoketests Smoke Test Tools
  136. -# extend 'make check' with a smoketest app
  137. - checks for OOCD_TEST_CONFIG, etc. in environment (or config file)
  138. - if properly set, runs the smoke test with specified parameters
  139. - openocd -f ${OOCD_TEST_CONFIG}
  140. - implies a modular test suite (see below)
  141. - should be able to run some minimal tests with dummy interface:
  142. - compare results of baseline sanity checks with expected results
  143. -# builds a more complete test suite:
  144. - existing testing/examples/ look like a great start
  145. - all targets should be tested fully and for all capabilities
  146. - we do NOT want a "lowest common denominator" test suite
  147. - ... but can we start with one to get going?
  148. - probably requires one test configuration file per board/target
  149. - modularization can occur here, just like with targets/boards/chips
  150. - coverage can increase over time, building up bundles of tests
  151. -# add new 'smoketest' Makefile target:
  152. - calls 'make check' (and the smoketest app)
  153. - gather inputs and output into a report file
  154. @subsection thelisttestreports Test Feedback Tools
  155. These ideas were first introduced here: @par
  156. https://lists.berlios.de/pipermail/openocd-development/2009-May/006358.html
  157. - provide report submission scripts for e-mail and web forms
  158. - add new Makefile targets to post the report:
  159. - 'checkreportsend' -- send to list via e-mail (via sendmail)
  160. - 'checkreportpost' -- send web form (via curl or other script)
  161. @subsection thelisttestgenerichw Generic Hardware Tester
  162. - implement VHDL to use for FPGA-based JTAG TAP testing device
  163. - develop test suite that utilizes this testing device
  164. @section thelistautotools Autotools Build System
  165. - make entire configure process require less user consideration:
  166. - automatically detect the features that are available, unless
  167. options were specifically provided to configure
  168. - provide a report of the drivers that will be build at the end of
  169. running configure, so the users can verify which driverswill be
  170. built during 'make' (and their options) .
  171. - eliminate sources of confusion in @c bootstrap script:
  172. -# Make @c bootstrap call 'configure --enable-maintainer-mode \<opts\>'?
  173. -# Add @c buildstrap script to assist with boostrap and configure steps.
  174. - automatically build tool-chains required for cross-compiling
  175. - produce mingw32, arm-elf, others using in-tree scripts
  176. - build all required target code from sources
  177. - make JTAG and USB debug output a run-time configuration option
  178. @section thelistarchitecture Architectural Tasks
  179. The following architectural tasks need to be accomplished and should be
  180. fairly easy to complete:
  181. - clean-up code to match style guides
  182. - factor code to eliminate duplicated functionality
  183. - rewrite code that uses casts to access 16-bit and larger types
  184. from unaligned memory addresses
  185. - libopenocd support: @par
  186. https://lists.berlios.de/pipermail/openocd-development/2009-May/006405.html
  187. - review and clean up interface/target/flash APIs
  188. The following strategic tasks will require ambition, knowledge, and time
  189. to complete:
  190. - overhaul use of types to improve 32/64-bit portability
  191. - types for both host and target word sizes?
  192. - can we use GDB's CORE_TYPE support?
  193. - Allow N:M:P mapping of servers, targets, and interfaces
  194. - loadable module support for interface/target/flash drivers and commands
  195. - support both static and dynamic modules.
  196. - should probably use libltdl for dynamic library handing.
  197. @section thelistadmin Documentation Tasks
  198. - Develop milestone and release guidelines, processes, and scripts.
  199. - Develop "style" guidelines (and scripts) for maintainers:
  200. - reviewing patches
  201. - committing to Subversion
  202. - Review The Guide for OpenOCD Users for documentation errors or omissions
  203. - Update The Manual for OpenOCD Developerrs:
  204. - Add documentation describing the architecture of each module
  205. - Provide more Technical Primers to bootstrap contributor knowledge
  206. */
  207. /** @file
  208. This file contains the @ref thelist page.
  209. */