1. 02 Mar, 2010 2 commits
    • David Brownell's avatar
      LPC1768 updates, IAR board support · 53b3d4dd
      David Brownell authored
      
      
      Fix some issues with the generic LPC1768 config file:
      
       - Handle the post-reset clock config:  4 MHz internal RC, no PLL.
         This affects flash and JTAG clocking.
      
       - Remove JTAG adapter config; they don't all support trst_and_srst
      
       - Remove the rest of the bogus "reset-init" event handler.
      
       - Allow explicit CCLK configuration, instead of assuming 12 MHz;
         some boards will use 100 Mhz (or the post-reset 4 MHz).
      
       - Simplify: rely on defaults for endianness and IR-Capture value
      
       - Update some comments too
      
      Build on those fixes to make a trivial config for the IAR LPC1768
      kickstart board (by Olimex) start working.
      
      Also, add doxygen to the lpc2000 flash driver, primarily to note a
      configuration problem with driver: it wrongly assumes the core clock
      rate never changes.  Configs that are safe for updating flash after
      "reset halt" will thus often be unsafe later ... e.g. for LPC1768,
      after switching to use PLL0 at 100 MHz.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      53b3d4dd
    • David Brownell's avatar
      ADIv5: use right ID for Cortex-M3 ETM · 5b311865
      David Brownell authored
      
      
      Correct a mistake made copying the ID of the Cortex-M3 ETM module
      from the TRM, so that "dap info" on a CM3 with an ETM will now
      correctly describe ROM table entries for such modules.  (They are
      included on LPC17xx and some other cores.)
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      5b311865
  2. 01 Mar, 2010 5 commits
  3. 28 Feb, 2010 13 commits
  4. 27 Feb, 2010 4 commits
    • David Brownell's avatar
      new "stellaris recover" command · e70d42a7
      David Brownell authored
      
      
      Stellaris chips have a procedure for restoring the chip to
      what's effectively the "as-manufactured" state, with all the
      non-volatile memory erased.  That includes all flash memory,
      plus things like the flash protection bits and various control
      words which can for example disable debugger access.  clearly,
      this can be useful during development.
      
      Luminary/TI provides an MS-Windows utility to perform this
      procedure along with its Stellaris developer kits.  Now OpenOCD
      users will no longer need to use that MS-Windows utility.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      e70d42a7
    • David Brownell's avatar
      ADIv5 DAP ops switching to JTAG or SWD modes · 3ef9beb5
      David Brownell authored
      
      
      Define two new DAP operations which use the new jtag_add_tms_seq()
      calls to put the DAP's transport into either SWD or JTAG mode, when
      the hardware allows.
      
      Tested with the Stellaris 'Recovering a "Locked" Device' procedure,
      which loops five times over both of these.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      3ef9beb5
    • David Brownell's avatar
      ft2232: implement TMS sequence command · 8c9b52e8
      David Brownell authored
      
      
      Implement the new TMS_SEQ command on FT2232 hardware.
      Also, swap a bogus exit() call with a clean failure return.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      8c9b52e8
    • David Brownell's avatar
      interface: define TMS sequence command · a3245bd7
      David Brownell authored
      
      
      For support of SWD we need to be able to clock out special bit
      sequences over TMS or SWDIO.  Create this as a generic operation,
      not yet called by anything, which is split as usual into:
      
       - upper level abstraction ... here, jtag_add_tms_seq();
       - midlayer implementation logic hooking that to the lowlevel code;
       - lowlevel minidriver operation ... here, interface_add_tms_seq();
       - message type for request queue, here JTAG_TMS.
      
      This is done slightly differently than other operations: there's a flag
      saying whether the interface driver supports this request.  (In fact a
      flag *word* so upper layers can learn about other capabilities too ...
      for example, supporting SWD operations.)
      
      That approach (flag) lets this method *eventually* be used to eliminate
      pathmove() and statemove() support from most adapter drivers, by moving
      all that logic into the mid-layer and increasing uniformity between the
      various drivers.  (Which will in turn reduce subtle bugginess.)
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      a3245bd7
  5. 25 Feb, 2010 3 commits
    • Mariano Alvira's avatar
      ft2232: add a mechanism to specify channel in layout structs · 4a64820f
      Mariano Alvira authored
      
      
      FT2232-family chips have two or more MPSSE modules.   FTDI documentation
      calls these channels.  JTAG adapter drivers thus need to be able to choose
      which channel to use.  (For example, one channel may connect to a board's
      microcontroller, while another connects to a CPLD.)
      
      Since each channel has its own USB interface, libftdi (somewhat confusingly)
      identifies channels using INTERFACE_* symbols.  Most boards use INTERFACE_A
      for JTAG, which is the default in OpenOCD.  But some wire up a different one.
      
      Note that there are two facets of what makes a wiring "layout":
      
       - The mapping between debug signals map and channel signals ... embedded
         in C functions.
      
       - Label used in Tcl configuration scripts ... part of the "layout" structure.
      
      By letting the channel be part of the layout struct, we permit sharing the C
      functions between Tcl-visible layouts, when those signal mappings are reused.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      4a64820f
    • David Brownell's avatar
      ARM ADIv5 doxygen and cleanup · 79010bf3
      David Brownell authored
      
      
      Add doxygen for mem_ap_read_buf_u{8,16,32}() calls,
      and shrink a few overlong lines.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      79010bf3
    • Hans Peter Mortensn's avatar
      AVR flash: handle AT90CAN128 chips · 7abe9f38
      Hans Peter Mortensn authored
      
      
      I have successfully programmed the AT90CAN128, based on the mega128  
      with some small modifications.
      
      [ dbrownell@users.sourceforge.net: patch cleanup ]
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      7abe9f38
  6. 24 Feb, 2010 1 commit
  7. 22 Feb, 2010 5 commits
  8. 21 Feb, 2010 7 commits
    • David Brownell's avatar
      ADIv5: relocate memacess_tck cycles · c8ea748d
      David Brownell authored
      
      
      When using an AP to access a memory (or a memory-mapped register),
      some extra TCK (assuming JTAG) cycles should be added to ensure
      the AP has enugh time to complete that access before trying to
      collect the response.
      
      The previous code was adding these cycles *before* trying to
      access (read or write) data to that address, not *after*.  Fix
      by putting the delays in the right location.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      c8ea748d
    • David Brownell's avatar
      ADIv5: remove ATOMIC/COMPOSITE interface mode · 3b68a708
      David Brownell authored
      
      
      This removes context-sensitivity from the programming interface and makes
      it possible to know what a block of code does without needing to know the
      previous history (specifically, the DAP's "trans_mode" setting).
      
      The mode was only set to ATOMIC briefly after DAP initialization, making
      this patch be primarily cleanup; almost everything depends on COMPOSITE.
      The transactions which shouldn't have been queued were already properly
      flushing the queue.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      3b68a708
    • David Brownell's avatar
      ARM: ADIv5, deadcode cleanup · ecff7304
      David Brownell authored
      
      
      I have no idea what the scan_inout_check() was *expecting* to achieve by
      issuing a read of the DP_RDBUFF register.  But in any case, that code was
      clearly never being called ("invalue" always NULL) ... so remove it, and
      the associated comment.
      
      Also rename it as ap_write_check(), facilitating a cleanup of its single
      call site by removing constant parameters.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      ecff7304
    • David Brownell's avatar
      ARM: ADIv5 code shrinkage, cleanup · 39cfe627
      David Brownell authored
      
      
      adi_jtag_dp_scan_u32() now wraps adi_jtag_dp_scan(), removing
      code duplication.  Include doxygen for the former.  Comment
      some particularly relevant points.  Minor fault handling fixes
      for both routines:  don't register a callback that can't run,
      or return ERROR_OK after an error.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      39cfe627
    • David Brownell's avatar
      ADIv5 clean up AP fault handling · a97bb675
      David Brownell authored
      
      
      Pass up fault codes from various routines, so their callers
      can clean up after failures, and remove the FIXME comments
      highlighting those previously goofy code paths.
      
       dap_ap_{read,write}_reg_u32()
       dap_ap_write_reg()
       mem_ap_{read,write}_u32()
       mem_ap_{read,write}_atomic_u32()
       dap_setup_accessport()
      
      Make dap_ap_write_reg_u32() just wrap dap_ap_write_reg(),
      instead of cloning its core code (and broken fault handling).
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      a97bb675
    • David Brownell's avatar
      ADIv5 clean up AP selection and register caching · 249263d2
      David Brownell authored
      
      
      Handling of AP (and AP register bank) selection, and cached AP
      registers, is pretty loose ... start tightening it:
      
       - It's "AP bank" select support ... there are no DP banks.  Rename.
         + dap_dp_bankselect() becomes dap_ap_bankselect()
         + "dp_select_value" struct field becomes "ap_bank_value"
      
       - Remove duplicate AP cache init paths ... only use dap_ap_select(),
       and don't make Cortex (A8 or M3) cores roll their own code.
      
       - For dap_ap_bankselect(), pass up any fault code from writing
       the SELECT register.  (Nothing yet checks those codes.)
      
       - Add various bits of Doxygen
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      249263d2
    • David Brownell's avatar
      ARM: keep a handle to the PC · 1aac72d2
      David Brownell authored
      
      
      Keep a handle to the PC in "struct arm", and use it.
      This register is used a fair amount, so this is a net
      minor code shrink (other than some line length fixes),
      but mostly it's to make things more readable.
      
      For XScale, fix a dodgy sequence while stepping.  It
      was initializing a variable to a non-NULL value, then
      updating it to handle the step-over-active-breakpoint
      case, and then later testing for non-NULL to see if
      it should reverse that step-over-active logic.  It
      should have done like ARM7/ARM9 does: init to NULL.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      1aac72d2