Zach Welch wrote: > Here is the current list of outstanding tasks for the OpenOCD project. >
Nice work Zach. Maybe this file can be put into the top dir of the repository so it can evolve more easily than it can by reworking deleted email messages. Is this a good idea? The problem then is that the only way to evolve it is to submit a patch? Dick > > ================================================================== > The List > ================================================================== > OpenOCD's Pending and Open Tasks (r1506) > ------------------------------------------------------------------ > > The '+' items have a current patch, 'o' are in progress by the > individual whose initials are indicated, and '-' items are open. > The key to initials associated with tasks appears after the list. > > * JTAG/TAP changes: > - use tap_set_state everywhere to allow logging TAP state transitions > o add new TAP state table (provided by JW) (ZW) > - update tap_get_tms_path API (suggested by DE) > - slow boat: add tap_get_tms_path2 and allow both for a while > - convert drivers that use old API over to the new one > - remove old tap_get_tms_path > - rename other tap_states to use standard JTAG names (suggested by ML) > - write script that automate production of the series of 16-17 patches > - produce and distribute current series against the current trunk > - distribute script so developers can use on WC through live commits > - make live commits after giving sufficient notice to others > - add TAP_UNKNOWN to augment TAP_INVALID? (suggested by ML/DH) > > * CFI: > + speed enhancements (posted Apr 22 by NC) (??) > - factor vendor-specific code into separate source files > - add new callback interface for vendor-specific code > - finish implementing bus width/chip width handling (suggested by NC) > - investigate/implement "thin wrapper" to use eCos CFI drivers (ØH) > > * JTAG Interfaces: > > o FT2232 driver: (DH) > + integrate FTD2XX High-Speed Device Patch (JK+ZW) > - fix segfault from long scan chains (observed by DH) > - fix non-recoverability of cable connect/reconnect (seen by DH) > - cure buggy madness > > o J-Link driver: (ZW) > + add state debugging (provided by JW) > - cure buggy madness > - test with known targets (i.e. working with other interfaces) > - test compatibility between v6.0 (yellow) and older units (e.g. v5.2) > > - Do others need some help? Probably.... > > * Target Support: > > + MC1322x support (JW/DE?) > - integrate and test support from JW (and DE?) > - get working with a known good interface (i.e. not today's jlink) > > o Cortex A8 support (ML) > o? verify the cortex-swjdp portion against CoreSight specifications > o? update cortex-swjdp to support A8 > o? add target implementation > - what else remains to be done? > > - ARM11 improvements > - implement missing functionality (grep FNC_INFO_NOTIMPLEMENTED ...) > > - Coldfire (suggested by NC) > - can we draw from the BDM project? http://bdm.sourceforge.net/ > > - other targets? (suggestions always welcome) > > * Architectural Upgrades > - Allow N:M:P mapping of servers, targets, and interfaces > - loadable module support for interface/target/flash drivers > > * Miscellaneous: > + continue to improve state and system debugging (from JW) (ZW) > - review and clean up interface/target/flash APIs > - factor code to eliminate duplicated functionality > - overhaul use of types to improve 32/64-bit portability > > ================================================================== > OpenOCD's Active Developers and Testers > ------------------------------------------------------------------ > > ** - Name - Status - Targets - Interfaces > NC - Nico Coesel - * - AU1100 - * > DE - Duane Ellis - M - * - * > DH - Dick Hollenbeck - * - * - * > ØH - Øyvind Harboe - * - * - ZY1000 > JK - Joern Keipf - * - * - FT2232H/FT4232HS? > JW - Jeff Williams - * - MC1322x - J-Link > ML - Magnus Lundin - * - * - * > RA - Rick Altherr - * - * - * > ZW - Zach Welch - * - STR912 - J-Link > > Status Key: > * - Active Developer/Tester > M - Missing In Action > V - On Vacation > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
