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.
 
 
 
 
 
 

290 lines
11 KiB

  1. // This file is part of the Doyxgen Developer Manual
  2. /** @page tasks Pending and Open Tasks
  3. This page lists pending and open tasks being considered or worked upon
  4. by the OpenOCD community.
  5. @section thelist The List
  6. Most items are open for the taking, but please post to the mailing list
  7. before spending much time working on anything lists here. The community
  8. may have evolved an idea since it was added here.
  9. Feel free to send patches to add or clarify items on this list, too.
  10. @section thelisttcl TCL
  11. This section provides possible things to improve with OpenOCD's TCL support.
  12. - Fix problem with incorrect line numbers reported for a syntax
  13. error in a reset init event.
  14. - organize the TCL configurations:
  15. - provide more directory structure for boards/targets?
  16. - factor configurations into layers (encapsulation and re-use)
  17. - Isolate all TCL command support:
  18. - Pure C CLI implementations using --disable-builtin-tcl.
  19. - Allow developers to build new dongles using OpenOCD's JTAG core.
  20. - At first, provide only low-level JTAG support; target layer and
  21. above rely heavily on scripting event mechanisms.
  22. - Allow full TCL support? add --with-tcl=/path/to/installed/tcl
  23. - Move TCL support out of foo.[ch] and into foo_tcl.[ch] (other ideas?)
  24. - See src/jtag/core.c and src/jtag/tcl.c for an example.
  25. - allow some of these TCL command modules to be dynamically loadable?
  26. @section thelistjtag JTAG
  27. This section list issues that need to be resolved in the JTAG layer.
  28. @subsection thelistjtagcore JTAG Core
  29. The following tasks have been suggested for cleaning up the JTAG layer:
  30. - use tap_set_state everywhere to allow logging TAP state transitions
  31. - rename other tap_states to use standard JTAG names (suggested by ML)
  32. - Encapsulate cmd_queue_cur_state and related varaible handling.
  33. - add slick 32 bit versions of jtag_add_xxx_scan() that avoids
  34. buf_set_u32() calls and other evidence of poor impedance match between
  35. API and calling code. New API should cut down # of lines in calling
  36. code by 100's and make things clearer. Also potentially be supported
  37. directly in minidriver API for better embedded host performance.
  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. - regression: xscale does not place debug_handler.bin into the right spot. workaround:
  80. use -s option on command line to place xscale/debug_handler.bin in search path @par
  81. https://lists.berlios.de/pipermail/openocd-development/2009-July/009338.html
  82. - bug: either USBprog is broken with new tms sequence or there is a general
  83. problem with XScale and the new tms sequence. Workaround: use "tms_sequence long"
  84. @par
  85. https://lists.berlios.de/pipermail/openocd-development/2009-July/009426.html
  86. - regression: "reset halt" between 729(works) and 788(fails): @par
  87. https://lists.berlios.de/pipermail/openocd-development/2009-July/009206.html
  88. - ARM923EJS:
  89. - reset run/halt/step is not robust; needs testing to map out problems.
  90. - ARM11 improvements (MB?)
  91. - fix single stepping (reported by �H)
  92. - implement missing functionality (grep FNC_INFO_NOTIMPLEMENTED ...)
  93. - Cortex A8 support (ML)
  94. - add target implementation (ML)
  95. - MC1322x support (JW/DE?)
  96. - integrate and test support from JW (and DE?)
  97. - get working with a known good interface (i.e. not today's jlink)
  98. - AT91SAM92xx:
  99. - improvements for unknown-board-atmel-at91sam9260.cfg (RD)
  100. - STR9x: (ZW)
  101. - improvements to str912.cfg to be more general purpose
  102. - AVR: (SQ)
  103. - independently verify implementation
  104. - incrementally improve working prototype in trunk. (SQ)
  105. - work out how to debug this target
  106. - AVR debugging protocol.
  107. - FPGA:
  108. - Altera Nios Soft-CPU support
  109. - Coldfire (suggested by NC)
  110. - can we draw from the BDM project? @par
  111. http://bdm.sourceforge.net/
  112. or the OSBDM package @par
  113. http://forums.freescale.com/freescale/board/message?board.id=OSBDM08&thread.id=422
  114. @section thelistsvf SVF/XSVF
  115. - develop SVF unit tests
  116. - develop XSVF unit tests
  117. @section thelistflash Flash Support
  118. - aduc702x segfault reported by Thomas A Moulton
  119. https://lists.berlios.de/pipermail/openocd-development/2009-July/009186.html
  120. - aduc7024 programming w/working area does not work:
  121. https://lists.berlios.de/pipermail/openocd-development/2009-July/009337.html
  122. - finish documentation for the following flash drivers:
  123. - avr
  124. - ecosflash
  125. - pic32mx
  126. - ocl
  127. - str9xpec
  128. @subsection thelistflashcfi CFI
  129. - finish implementing bus width/chip width handling (suggested by NC)
  130. - factor vendor-specific code into separate source files
  131. - add new callback interface for vendor-specific code
  132. - investigate/implement "thin wrapper" to use eCos CFI drivers (�H)
  133. @section thelistdebug Debugger Support
  134. - breakpoints can get lost in some circumstances: @par
  135. https://lists.berlios.de/pipermail/openocd-development/2009-June/008853.html
  136. - integrate Keil AGDI interface to OpenOCD? (submitted by Dario Vecchio)
  137. @section thelisttesting Testing Suite
  138. This section includes several related groups of ideas:
  139. - @ref thelistunittests
  140. - @ref thelistsmoketests
  141. - @ref thelisttestreports
  142. - @ref thelisttestgenerichw
  143. @subsection thelistunittests Unit Tests
  144. - add testing skeleton to provide frameworks for adding tests
  145. - implement server unit tests
  146. - implement JTAG core unit tests
  147. - implement JTAG interface unit tests
  148. - implement flash unit tests
  149. - implement target unit tests
  150. @subsection thelistsmoketests Smoke Test Tools
  151. -# extend 'make check' with a smoketest app
  152. - checks for OOCD_TEST_CONFIG, etc. in environment (or config file)
  153. - if properly set, runs the smoke test with specified parameters
  154. - openocd -f ${OOCD_TEST_CONFIG}
  155. - implies a modular test suite (see below)
  156. - should be able to run some minimal tests with dummy interface:
  157. - compare results of baseline sanity checks with expected results
  158. -# builds a more complete test suite:
  159. - existing testing/examples/ look like a great start
  160. - all targets should be tested fully and for all capabilities
  161. - we do NOT want a "lowest common denominator" test suite
  162. - ... but can we start with one to get going?
  163. - probably requires one test configuration file per board/target
  164. - modularization can occur here, just like with targets/boards/chips
  165. - coverage can increase over time, building up bundles of tests
  166. -# add new 'smoketest' Makefile target:
  167. - calls 'make check' (and the smoketest app)
  168. - gather inputs and output into a report file
  169. @subsection thelisttestreports Test Feedback Tools
  170. These ideas were first introduced here: @par
  171. https://lists.berlios.de/pipermail/openocd-development/2009-May/006358.html
  172. - provide report submission scripts for e-mail and web forms
  173. - add new Makefile targets to post the report:
  174. - 'checkreportsend' -- send to list via e-mail (via sendmail)
  175. - 'checkreportpost' -- send web form (via curl or other script)
  176. @subsection thelisttestgenerichw Generic Hardware Tester
  177. - implement VHDL to use for FPGA-based JTAG TAP testing device
  178. - develop test suite that utilizes this testing device
  179. @section thelistautotools Autotools Build System
  180. - make entire configure process require less user consideration:
  181. - automatically detect the features that are available, unless
  182. options were specifically provided to configure
  183. - provide a report of the drivers that will be build at the end of
  184. running configure, so the users can verify which driverswill be
  185. built during 'make' (and their options) .
  186. - eliminate sources of confusion in @c bootstrap script:
  187. -# Make @c bootstrap call 'configure --enable-maintainer-mode \<opts\>'?
  188. -# Add @c buildstrap script to assist with boostrap and configure steps.
  189. - automatically build tool-chains required for cross-compiling
  190. - produce mingw32, arm-elf, others using in-tree scripts
  191. - build all required target code from sources
  192. - make JTAG and USB debug output a run-time configuration option
  193. @section thelistarchitecture Architectural Tasks
  194. The following architectural tasks need to be accomplished and should be
  195. fairly easy to complete:
  196. - clean-up code to match style guides
  197. - factor code to eliminate duplicated functionality
  198. - rewrite code that uses casts to access 16-bit and larger types
  199. from unaligned memory addresses
  200. - libopenocd support: @par
  201. https://lists.berlios.de/pipermail/openocd-development/2009-May/006405.html
  202. - review and clean up interface/target/flash APIs
  203. The following strategic tasks will require ambition, knowledge, and time
  204. to complete:
  205. - overhaul use of types to improve 32/64-bit portability
  206. - types for both host and target word sizes?
  207. - can we use GDB's CORE_TYPE support?
  208. - Allow N:M:P mapping of servers, targets, and interfaces
  209. - loadable module support for interface/target/flash drivers and commands
  210. - support both static and dynamic modules.
  211. - should probably use libltdl for dynamic library handing.
  212. @section thelistadmin Documentation Tasks
  213. - Develop milestone and release guidelines, processes, and scripts.
  214. - Develop "style" guidelines (and scripts) for maintainers:
  215. - reviewing patches
  216. - committing to Subversion
  217. - Review The Guide for OpenOCD Users for documentation errors or omissions
  218. - Update The Manual for OpenOCD Developerrs:
  219. - Add documentation describing the architecture of each module
  220. - Provide more Technical Primers to bootstrap contributor knowledge
  221. */
  222. /** @file
  223. This file contains the @ref thelist page.
  224. */