Skip to content
Snippets Groups Projects
Select Git revision
  • 1392c27cf9ff1a7f5f5477d23880f2e5c59c898e
  • master default protected
  • v0.10.0
  • v0.10.0-rc2
  • v0.10.0-rc1
  • v0.9.0
  • v0.9.0-rc1
  • v0.8.0
  • v0.8.0-rc2
  • v0.8.0-rc1
  • v0.7.0
  • v0.7.0-rc2
  • v0.7.0-rc1
  • v0.6.1
  • v0.6.0
  • v0.6.0-rc2
  • v0.6.0-rc1
  • v0.5.0
  • v0.5.0-rc2
  • v0.5.0-rc1
  • v0.4.0
  • v0.4.0-rc2
22 results

TODO

Blame
  • TODO 15.37 KiB
    // This file is part of the Doxygen Developer Manual
    /** @page tasks Pending and Open Tasks
    
    This page lists pending and open tasks being considered or worked upon
    by the OpenOCD community.
    
    @section thelist The List
    
    Most items are open for the taking, but please post to the mailing list
    before spending much time working on anything lists here.  The community
    may have evolved an idea since it was added here.
    
    Feel free to send patches to add or clarify items on this list, too.
    
    @section thelisttcl TCL
    
    This section provides possible things to improve with OpenOCD's TCL support.
    
    - Fix problem with incorrect line numbers reported for a syntax
      error in a reset init event.
    
    - organize the TCL configurations:
      - provide more directory structure for boards/targets?
      - factor configurations into layers (encapsulation and re-use)
    
    - Fix handling of variables between multiple command line "-c" and "-f"
      parameters.  Currently variables assigned through one such parameter
      command/script are unset before the next one is invoked.
    
    - Isolate all TCL command support:
      - Pure C CLI implementations using --disable-builtin-tcl.
        - Allow developers to build new dongles using OpenOCD's JTAG core.
        - At first, provide only low-level JTAG support; target layer and
          above rely heavily on scripting event mechanisms.
      - Allow full TCL support? add --with-tcl=/path/to/installed/tcl
      - Move TCL support out of foo.[ch] and into foo_tcl.[ch] (other ideas?)
        - See src/jtag/core.c and src/jtag/tcl.c for an example.
        - allow some of these TCL command modules to be dynamically loadable?
    
    @section thelistjtag JTAG
    
    This section list issues that need to be resolved in the JTAG layer.
    
    @subsection thelistjtagcore JTAG Core
    
    The following tasks have been suggested for cleaning up the JTAG layer:
    
    - use tap_set_state everywhere to allow logging TAP state transitions
    - Encapsulate cmd_queue_cur_state and related variable handling.
    - add slick 32 bit versions of jtag_add_xxx_scan() that avoids
    buf_set_u32() calls and other evidence of poor impedance match between
    API and calling code. New API should cut down # of lines in calling
    code by 100's and make things clearer. Also potentially be supported
    directly in minidriver API for better embedded host performance.
    
    The following tasks have been suggested for adding new core JTAG support:
    
    - Improve autodetection of TAPs by supporting tcl escape procedures that
      can configure discovered TAPs based on IDCODE value ... they could:
        - Remove guessing for irlen
        - Allow non-default irmask/ircapture values
    - SPI/UART emulation:
      - (ab)use bit-banging JTAG interfaces to emulate SPI/UART
      - allow SPI to program flash, MCUs, etc.
    
    @subsection thelistjtaginterfaces JTAG Interfaces
    
    There are some known bugs to fix in JTAG adapter drivers:
    
    - For JTAG_STATEMOVE to TAP_RESET, all drivers must ignore the current