1. 01 Apr, 2011 1 commit
  2. 31 Mar, 2011 1 commit
  3. 22 Mar, 2011 1 commit
  4. 17 Mar, 2011 2 commits
  5. 03 Feb, 2011 1 commit
    • Mathias K's avatar
      24bit buffer support · b0bdc4e2
      Mathias K authored
      Hello,
      
      this patch add 24bit support to the target buffer functions and little/big endian functions.
      
      Regards,
      
      Mathias
      b0bdc4e2
  6. 31 Jan, 2011 2 commits
  7. 04 Jan, 2011 1 commit
  8. 29 Dec, 2010 2 commits
    • Andrew MacIsaac's avatar
      Compilation Warnings on OS X 10.5 · 50e79d60
      Andrew MacIsaac authored
      I received a number of "-Wshadow" related warnings (treated as errors) while
      trying to build on OS X Leopard.  In addition, there were two miscellaneous
      other warnings in the flash drivers.  Attached are two patches which correct
      these issues and the commit messages to accompany them.
      
      My system has the following configuration (taken from uname -a):
      
      Darwin 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009;
      root:xnu-1228.15.4~1/RELEASE_I386 i386
      
      === Werror_patch.txt Commit Message ===
      compilation: fixes for -Wshadow warnings on OS X
      
      These changes fix -Wshadow compilation warnings on OS X 10.5.8
      
      Compiled with the following configure command:
      
      ../configure --prefix=/usr/local --enable-maintainer-mode --enable-jlink
      --enable-ft2232_libftdi
      
      === flash_patch.txt Commit Message ===
      compilation: fixes for flash driver warnings on OS X
      
      These changes fix two compilation warnings on OS X 10.5.8:
      
      ../../../../src/flash/nor/at91sam3.c:2767: warning: redundant redeclaration
      of 'at91sam3_flash'
      ../../../../src/flash/nor/at91sam3.c:101: warning: previous declaration of
      'at91sam3_flash' was here
      
      and
      
      ../../../../src/flash/nor/stmsmi.c:205: warning: format not a string literal
      and no format arguments
      
      Compiled with the following configure command:
      
      ../configure --prefix=/usr/local --enable-maintainer-mode --enable-jlink
      --enable-ft2232_libftdi
      ===
      
      Andrew
      50e79d60
    • Øyvind Harboe's avatar
      target: do not expose error numbers to users · 8f93c0a3
      Øyvind Harboe authored
      
      
      error numbers are only reported at DEBUG log levels and
      used internally, they are not part of the user interface.
      Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
      8f93c0a3
  9. 01 Dec, 2010 1 commit
  10. 22 Nov, 2010 1 commit
  11. 04 Nov, 2010 1 commit
    • ddraskovic's avatar
      arm964e: Add support for ARM946E target. · 9e3d43cf
      ddraskovic authored
      So far most of the people have been using existing ARM966E in the
      place of ARM946E, because they have practically the same scan chains.
      
      However, ARM946E has caches, which further complicates JATG handling
      via scan-chain. this was preventing single-stepping for ARM946E when
      SW breakpoints are used.
      
      This patch thus introduces :
      1) Correct cache handling on memory write
      2) Possibility to flush whole cache and turn it off during debug, or
      just to flush affected lines (faster and better)
      3) Correct SW breakpoint handling and correct single-stepping
      4) Corrects the bug on CP15 read and write, so CP15 values
      are now correctly R/W
      9e3d43cf
  12. 29 Oct, 2010 1 commit
  13. 12 Oct, 2010 2 commits
  14. 29 Sep, 2010 2 commits
  15. 15 Aug, 2010 1 commit
    • Oleksandr Tymoshenko's avatar
      avr32: work-in-progress · c3d51bf0
      Oleksandr Tymoshenko authored
      committed so as to ease cooperation and to let it be improved
      over time.
      
      So far it supports:
      - halt/resume
      - registers inspection
      - memory inspection/modification
      
      I'm still getting up to speed with OpenOCD internals and AVR32 so code is a little
      bit messy and I'd appreciate any feedback.
      c3d51bf0
  16. 11 Aug, 2010 1 commit
  17. 09 Aug, 2010 1 commit
  18. 02 Aug, 2010 1 commit
  19. 22 Jun, 2010 3 commits
  20. 15 Jun, 2010 1 commit
  21. 14 Jun, 2010 1 commit
  22. 08 Jun, 2010 1 commit
  23. 16 May, 2010 1 commit
  24. 05 May, 2010 2 commits
  25. 04 May, 2010 1 commit
  26. 09 Apr, 2010 2 commits
  27. 04 Apr, 2010 3 commits
    • David Brownell's avatar
      Restore deleted '!' character · 2a17fd9f
      David Brownell authored
      
      
      I'm not sure what caused this significant character to get deleted.
      it may be related to intermittent Editor or terminal flakes  I've
      been seeing lately (sigh).  This fix is trivial.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      2a17fd9f
    • David Brownell's avatar
      target: are we running algorithm code? · 876bf9bf
      David Brownell authored
      
      
      Fixing one bug can easily uncover another  .... in this case,
      making sure that we properly invalidate some cached NOR state when
      resuming arbitrary target code turned up an issue when the code
      wasn't quite arbitrary (and we couldn't know that, but some parts
      of OpenOCD assumed the cache would not be invalidated.
      
      Specifically:  some flash drivers (like CFI) update that state in loops
      with downloaded algorithms, thus invalidating the state as it's probed.
      
       + Add a new target state flag, to record whether the target is
        running downloaded algorithm code.
      
       + Use that flag to add a special case:  "trust" downloaded algorithms
         not to corrupt that cached state, bypassing cache invalidation.
      
      Also update some of the documentation to stipulate that this flavor of
      trustworthiness is now *required* ... not just a fortuitous acident.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      876bf9bf
    • David Brownell's avatar
      simplify and unconfuse target_run_algorithm() · 88fcb5a9
      David Brownell authored
      
      
      For some reason there are *two* schemes for interposing logic into
      the run_algorithm() code path...  One is a standard procedural wapper
      around the target method invocation.
      
      the other (superfluous) one hacked the method table by splicing
      a second procedural wrapper into the method table.  Remove it:
      
      	* Rename its  slightly-more-featureful wrapper so it becomes
      	  the standard procedural wrapper, leaving its added logic
      	  (where it should have been in the first place.
      
                Also add a paranoia check, to report targets that don't
      	  support algorithms without traversing a NULL pointer, and
      	  tweak its code structure a bit so it's easier to modify.
      
      	* Get rid of the superfluous/conusing method table hacks.
      
      This is a net simplification, making it simpler to analyse what's
      going on, and then interpose logic . ... by ensuring there's only one
      natural place for it to live.
      
      ------------
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      88fcb5a9
  28. 25 Mar, 2010 1 commit
    • Øyvind Harboe's avatar
      target: fix poll off · ed6756fb
      Øyvind Harboe authored
      
      
      I don't know when "poll off" broke, but "poll off" didn't
      stop background polling of target. The polling status flag
      simply wasn't checked in the handle_target timer callback.
      
      All target polling(including power/reset state) is now stopped
      upon "poll off".
      Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
      ed6756fb
  29. 17 Mar, 2010 1 commit