1. 01 Feb, 2010 1 commit
  2. 21 Jan, 2010 2 commits
  3. 13 Jan, 2010 1 commit
  4. 09 Jan, 2010 1 commit
  5. 07 Jan, 2010 1 commit
  6. 02 Jan, 2010 1 commit
    • David Brownell's avatar
      streamline and document helptext mode displays · b3bf1d12
      David Brownell authored
      
      
      Most commands are usable only at runtime; so don't bother saying
      that, it's noise.  Moreover, tokens like EXEC are cryptic.  Be
      more clear: highlight only the commands which may (also) be used
      during the config stage, thus matching the docs more closely.
      There are
      
       - Configuration commands (per documentation)
       - And also some commands that valid at *any* time.
      
      Update the docs to note that "help" now shows this mode info.
      
      This also highlighted a few mistakes in command configuration,
      mostly commands listed as "valid at any time" which shouldn't
      have been.  This just fixes ones I noted when sanity testing.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      b3bf1d12
  7. 31 Dec, 2009 1 commit
  8. 28 Dec, 2009 1 commit
  9. 15 Dec, 2009 1 commit
  10. 13 Dec, 2009 1 commit
    • David Brownell's avatar
      target: further shrink Jim-awareness · 38e376d2
      David Brownell authored
      
      
      Don't include <helper/jim.h> from target.h ... not everything
      which touches targets needs to be able to talk to Jim.  Plus,
      most files include this header by another path.
      
      Also, switch the affected files to use the classic sequence
      for #included files:  all <framework/headers.h> first, then
      the "local_headers.h".  This helps prevent growth of problematic
      layering, by minimizing entanglement.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      38e376d2
  11. 08 Dec, 2009 2 commits
  12. 07 Dec, 2009 1 commit
  13. 03 Dec, 2009 3 commits
  14. 02 Dec, 2009 2 commits
  15. 01 Dec, 2009 3 commits
  16. 28 Nov, 2009 4 commits
    • Zachary T Welch's avatar
      explode tcl_target_func into many handlers · 070259ca
      Zachary T Welch authored
      Eliminate the monolithic tcl_target_func by registering each of its
      commands using the new chained command registration mechanism.
      
      Also chains the target's commands under the CPU command, though these
      may not work properly without some further modification.
      070259ca
    • Zachary T Welch's avatar
      split jim_target into multiple handlers · cb8d567b
      Zachary T Welch authored
      The 'target' command group was implemented using its own command
      dispatching, which can be eliminated by using the new chained command
      registration mechanism.  This patch splits the jim_target() function
      into individual handlers, which makes them to be visible to the help and
      usage commands.  These one-trick handlers are much easier to understand.
      cb8d567b
    • David Brownell's avatar
      target: uplevel add_{break,watch}point() error checks · acbe054a
      David Brownell authored
      
      
      In target_type.h it's documented that the target must be
      halted for add_breakpoint() ... and with slight ambiguity,
      also for its add_watchpoint() sibling.  So rather than
      verifying that constraint in the CPU drivers, do it in the
      target_add_{break,watch}point() routines.
      
      Add minor paranoia on the remove_*point() paths too:  save
      the return value, and print it out in in the LOG_DEBUG message
      in case it's nonzero.
      
      Note that with some current cores, like all ARMv7 ones I've
      looked at, there's no technical issue preventing watchpoint or
      breakpoint add/remove operations on active cores.  This model
      seems deeply wired into OpenOCD though.
      
      ALSO:  the ARM targets were fairly "good" about enforcing that
      constraint themselves.  The MIPS ones were relied on other code
      to catch such stuff, but it's not clear such code existed ...
      keep an eye out for new issues on MIPS.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      acbe054a
    • David Brownell's avatar
      target: groundwork for "reset-assert" event · 4e56a230
      David Brownell authored
      
      
      This defines a "reset-assert" event and a supporting utility
      routine, and documents both how targets should implement it
      and how config scripts should use it.  Core-specific updates
      are needed to make this work.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      4e56a230
  17. 26 Nov, 2009 2 commits
    • David Brownell's avatar
      target: create and use target_name() · 2653b803
      David Brownell authored
      
      
      Several of the sites now using target_type_name() really
      ought to be using an instance-specific name.  Create a
      function called target_name(), accessing the instance's
      own (command) name.
      
      Use it in several places that really should be displaying
      instance-specific names.  Also in several places which
      were already doing so, but which had no wrapper to call.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      2653b803
    • David Brownell's avatar
      target: target_get_name() --> target_type_name() · b715a81f
      David Brownell authored
      
      
      There are two names that may matter on a per-target basis.
      One is a per-instance name (for example, "at91sam7s.cpu").
      The other is the name of its type (for example, "arm7tdmi"),
      which is shared among multiple targets.
      
      Currently target_get_name() returns the type name, which is
      misleading and is rarely appropriate for target diagnostics.
      Rename that as target_type_name().
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      b715a81f
  18. 25 Nov, 2009 5 commits
    • Zachary T Welch's avatar
      add 'testee' target type · 9d4c89f3
      Zachary T Welch authored
      Alliteration aside, this should provide the final piece of the puzzle
      for developers that want to get started writing a new target type.
      In this way, it also seeks to complement the 'dummy' interface driver
      and 'faux' NOR flash driver.
      9d4c89f3
    • Zachary T Welch's avatar
      add jim_handler to command_registration · 17a9dea5
      Zachary T Welch authored
      Adding jim_handler field to command_registration allows removing the
      register_jim helper.  All command registrations now go through the
      register_command{,s}() functions.
      17a9dea5
    • Zachary T Welch's avatar
      remove target_type register_command callback · 66ee3034
      Zachary T Welch authored
      Uses chaining of command_registration structures to eliminate all
      target_type register_callback routines.  Exports the command_handler
      registration arrays for those target types that are used by others.
      66ee3034
    • Zachary T Welch's avatar
      target: use register_commands() · 4e67912f
      Zachary T Welch authored
      4e67912f
    • Zachary T Welch's avatar
      use COMMAND_REGISTER macro · 833e7f52
      Zachary T Welch authored
      Replaces direct calls to register_command() with a macro, to allow
      its parameters to be changed and callers updated in phases.
      833e7f52
  19. 22 Nov, 2009 1 commit
  20. 20 Nov, 2009 1 commit
  21. 18 Nov, 2009 2 commits
  22. 17 Nov, 2009 3 commits