1. 29 Dec, 2010 1 commit
  2. 01 Dec, 2010 1 commit
  3. 22 Nov, 2010 1 commit
  4. 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
  5. 29 Oct, 2010 1 commit
  6. 12 Oct, 2010 2 commits
  7. 29 Sep, 2010 2 commits
  8. 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
  9. 11 Aug, 2010 1 commit
  10. 09 Aug, 2010 1 commit
  11. 02 Aug, 2010 1 commit
  12. 22 Jun, 2010 3 commits
  13. 15 Jun, 2010 1 commit
  14. 14 Jun, 2010 1 commit
  15. 08 Jun, 2010 1 commit
  16. 16 May, 2010 1 commit
  17. 05 May, 2010 2 commits
  18. 04 May, 2010 1 commit
  19. 09 Apr, 2010 2 commits
  20. 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
  21. 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
  22. 17 Mar, 2010 3 commits
    • Øyvind Harboe's avatar
      gdb: long running "monitor mww" now works w/gdb · cc197c80
      Øyvind Harboe authored
      
      
      invoke keep_alive() to make sure that the default 2000ms
      timeout does not trigger.
      Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
      cc197c80
    • Øyvind Harboe's avatar
      target: faster mww operations · bf71e34c
      Øyvind Harboe authored
      
      Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
      bf71e34c
    • Øyvind Harboe's avatar
      target: mdX/mwX on target were badly broken · 099ffc75
      Øyvind Harboe authored
      
      
      - incorrect parsing of arguments
      - mdX didn't display arguments correctly
      
      I don't think anyone ever used that code path :-)
      
      Did you know that "target mdw" and mdw are very different?
      
      for {set i 0} {$i < 256} {set i [expr $i+1]} {mwb [expr 0x2000000+$i] $i}
      
       mdw 0x2000000 0x10
      0x02000000: 03020100 07060504 0b0a0908 0f0e0d0c 13121110 17161514 1b1a1918 1f1e1d1c
      0x02000020: 23222120 27262524 2b2a2928 2f2e2d2c 33323130 37363534 3b3a3938 3f3e3d3c
      
      > zy1000.cpu mdb 0x2000000 0x20
      0x02000000 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f ................
      0x02000010 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f ................
      > zy1000.cpu mdh 0x2000000 0x20
      0x02000000 0100 0302 0504 0706 0908 0b0a 0d0c 0f0e ................
      0x02000010 1110 1312 1514 1716 1918 1b1a 1d1c 1f1e ................
      0x02000020 2120 2322 2524 2726 2928 2b2a 2d2c 2f2e  !"#$%&'()*+,-./
      0x02000030 3130 3332 3534 3736 3938 3b3a 3d3c 3f3e 0123456789:;<=>?
      > zy1000.cpu mdw 0x2000000 0x20
      0x02000000 03020100 07060504 0b0a0908 0f0e0d0c ................
      0x02000010 13121110 17161514 1b1a1918 1f1e1d1c ................
      0x02000020 23222120 27262524 2b2a2928 2f2e2d2c  !"#$%&'()*+,-./
      0x02000030 33323130 37363534 3b3a3938 3f3e3d3c 0123456789:;<=>?
      0x02000040 43424140 47464544 4b4a4948 4f4e4d4c @ABCDEFGHIJKLMNO
      0x02000050 53525150 57565554 5b5a5958 5f5e5d5c PQRSTUVWXYZ[\]^_
      0x02000060 63626160 67666564 6b6a6968 6f6e6d6c `abcdefghijklmno
      0x02000070 73727170 77767574 7b7a7978 7f7e7d7c pqrstuvwxyz{|}~.
      Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
      099ffc75
  23. 04 Mar, 2010 1 commit
    • David Brownell's avatar
      NOR: invalidate cached state on target resume · 5fdf9535
      David Brownell authored
      
      
      The NOR infrastructure caches some per-sector state, but
      it's not used much ... because the cache is not trustworthy.
      
      This patch addresses one part of that problem, by ensuring
      that state cached by NOR drivers gets invalidated once we
      resume the target -- since targets may then modify sectors.
      
      Now if we see sector protection or erase status marked as
      anything other than "unknown", we should be able to rely
      on that as being accurate.  (That is ... if we assume the
      drivers initialize and update this state correctly.)
      
      Another part of that problem is that the cached state isn't
      much used (being unreliable, it would have been unsafe).
      Those issues can be addressed in later patches.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      5fdf9535
  24. 02 Mar, 2010 1 commit
    • David Brownell's avatar
      target_resume() doxygen · d72e90ae
      David Brownell authored
      
      
      Add doxygen for target_resume() ... referencing the still-unresolved
      confusion about what the "debug_execution" parameter means (not all
      CPU support code acts the same).
      
      The 'handle_breakpoints" param seems to have resolved the main issue
      with its semantics, but it wasn't part of the function spec before.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      d72e90ae
  25. 01 Feb, 2010 1 commit
  26. 21 Jan, 2010 2 commits
  27. 13 Jan, 2010 1 commit
  28. 09 Jan, 2010 1 commit
  29. 07 Jan, 2010 1 commit