1. 09 Nov, 2009 1 commit
    • David Brownell's avatar
      finish removing deprecated/obsolete commands · d70d9634
      David Brownell authored
      It's been about a year since these were deprecated and, in most
      cases, removed.  There's no point in carrying that documentation,
      or backwards compatibility for "jtag_device" and "jtag_speed",
      around forever.  (Or a few remnants of obsolete code...)
      Removed a few obsolete uses of "jtag_speed":
       - The Calao stuff hasn't worked since July 2008.  (Those Atmel
         targets need to work with a 32KHz core clock after reset until
         board-specific init-reset code sets up the PLL and enables a
         faster JTAg clock.)
       - Parport speed controls don't actually work (tops out at about
         1 MHz on typical HW).
       - In general, speed controls need to live in board.cfg files (or
         sometimes target.cfg files), not interface.cfg ...
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
  2. 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>
  3. 05 Nov, 2009 2 commits
    • Krzysztof Kajstura's avatar
    • David Brownell's avatar
      PXA255: support Intel "Lubbock" platform · fd108f57
      David Brownell authored
      Config for Intel's "Lubbock" PXA255 development board.  Even more
      so than the PXA255 itself, this is obsolete.  AFAIK this was the
      first generally available development platform for PXA255.  Intel
      stopped providing these after other devel boards became available.
      One interesting thing about this board from the OpenOCD perspective
      is probably its flash configuration.  Each bank is 32 bits wide,
      built from two 16-bit StrataFlash chips wired in parallel.  This
      doubles throughput ... it reads/writes 32 bits in the time a single
      chip takes to write just 16 bits.
      This conf mostly works, given XScale bugfixes, but has some issues
      (notably: no access to the on-board SDRAM) flagged by FIXMEs.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
  4. 01 Nov, 2009 1 commit
  5. 31 Oct, 2009 1 commit
  6. 29 Oct, 2009 1 commit
  7. 27 Oct, 2009 4 commits
  8. 26 Oct, 2009 2 commits
  9. 25 Oct, 2009 1 commit
  10. 21 Oct, 2009 1 commit
  11. 20 Oct, 2009 2 commits
  12. 18 Oct, 2009 1 commit
  13. 14 Oct, 2009 3 commits
  14. 13 Oct, 2009 1 commit
  15. 12 Oct, 2009 3 commits
  16. 10 Oct, 2009 1 commit
  17. 09 Oct, 2009 3 commits
  18. 08 Oct, 2009 3 commits
  19. 07 Oct, 2009 2 commits
  20. 06 Oct, 2009 3 commits
  21. 05 Oct, 2009 2 commits
  22. 02 Oct, 2009 1 commit