Skip to content
GitLab
  1. 10 Nov, 2009 1 commit
    • Thomas Kindler's avatar
      stm32.cfg: remove reset_config · 85944d41
      Thomas Kindler authored 
      

Here's a patch for the double-reset problem on STM32.  I've tested
downloading and debugging with GDB and Eclipse, and everything seems
to work fine.

This effectively sets reset_config to none. trst_only would also
be ok, but that's better left to a board configuration file since
not all boards wire it up.

The NVIC is used to trigger reset, which at least on this chip also
pulses nSRST so the whole system does get rest -- exactly once.

Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      85944d41
  3. 08 Nov, 2009 1 commit
    • David Brownell's avatar
      target.cfg: remove "-work-area-virt 0" · 3e6f9e8d
      David Brownell authored 
      

The semantics of "-work-area-virt 0" (or phys) changed with
the patch to require specifying physical or virtrual work
area addresses.  Specifying zero was previously a NOP.  Now
it means that address zero is valid.

This patch addresses three related issues:

 - MMU-less processors should never specify work-area-virt;
   remove those specifications.  Such processors include
   ARM7TDMI, Cortex-M3, and ARM966.

 - MMU-equipped processors *can* specify work-area-virt...
   but zero won't be appropriate, except in mischievous
   contexts (which hide null pointer exceptions).

   Remove those specs from those processors too.  If any of
   those mappings is valid, someone will need to submit a
   patch adding it ... along with a comment saying what OS
   provides the mapping, and in which context.  Example,
   say "works with Linux 2.6.30+, in kernel mode".  (Note
   that ARM Linux doesn't map kernel memory to zero ...)

 - Clarify docs on that "-virt" and other work area stuff.

Seems to me work-area-virt is quite problematic; not every
operating system provides such static mappings; if they do,
they're not in every MMU context...

Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      3e6f9e8d
  5. 01 Nov, 2009 1 commit
  7. 31 Oct, 2009 1 commit
  9. 21 Sep, 2009 1 commit
  11. 04 Sep, 2009 1 commit
  13. 01 Jul, 2009 1 commit
  15. 30 Jun, 2009 1 commit
  17. 29 Jun, 2009 1 commit
  19. 27 May, 2009 2 commits
    • zwelch's avatar
      Move TCL script files -- Step 2 of 2: · dbbc9c41
      zwelch authored 
      - Move src/tcl to tcl/.
- Update top Makefile.am to use new path name.


git-svn-id: svn://svn.berlios.de/openocd/trunk@1919 b42882b7-edfa-0310-969c-e2dbd0fdcd60
      dbbc9c41
    • zwelch's avatar
      Move TCL script files -- Step 1 of 2: · 140d6c8e
      zwelch authored 
      - Move src/target/{interface,target,board,test}/ into src/tcl/
- Remove existing rules in src/Makefile.am and src/target/Makefile.am.
- Add Makefile.am handling of *.cfg and *.tcl files in top Makefile.am:
  - Add dist-hook to include such files under src/tcl in the distribution.
  - Add install-data-hook to install contents of '$(top_srcdir)/src/tcl/'.
  - Add uninstall-hook to remove the installed script files.
- Change paths to (un)install script files in '$(pkgdatadir)/scripts'.


git-svn-id: svn://svn.berlios.de/openocd/trunk@1918 b42882b7-edfa-0310-969c-e2dbd0fdcd60
      140d6c8e
  21. 23 Apr, 2009 1 commit
  23. 02 Apr, 2009 1 commit
  25. 03 Dec, 2008 1 commit
  27. 30 Nov, 2008 1 commit
  29. 30 Oct, 2008 1 commit
  31. 18 Aug, 2008 1 commit
  33. 28 Jul, 2008 1 commit
  35. 18 Jul, 2008 1 commit
  37. 04 Jul, 2008 1 commit
  39. 16 Apr, 2008 1 commit
  41. 14 Apr, 2008 1 commit
  43. 03 Apr, 2008 1 commit
    • oharboe's avatar
      · d3f0549f
      oharboe authored 
      - Work on fixing erase check. Many implementations are plain broken.
Wrote a default flash erase check fn which uses CFI's target algorithm
w/fallback to memory reads. 
- "flash info" no longer prints erase status as it is stale. 
- "flash erase_check" now prints erase status. erase check can take a 
*long* time. Work in progress
- arm7/9 with seperate srst & trst now supports reset init/halt
after a power outage. arm7/9 no longer makes any assumptions
about state of target when reset is asserted.
- fixes for srst & trst capable arm7/9 with reset init/halt
- prepare_reset_halt retired. This code needs to be inside
assert_reset anyway
- haven't been able to get stm32 write algorithm to work. Fallback
flash write does work. Haven't found a version of openocd trunk
where this works.
- added target_free_all_working_areas_restore() which can
let be of restoring backups. This is needed when asserting
reset as the target must be assumed to be an unknown state.
Added some comments to working areas API
- str9 reset script fixes
- some guidelines
- fixed dangling callbacks upon reset timeout 


git-svn-id: svn://svn.berlios.de/openocd/trunk@536 b42882b7-edfa-0310-969c-e2dbd0fdcd60
      d3f0549f
  45. 09 Mar, 2008 1 commit
  47. 01 Mar, 2008 5 commits