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