Martin and I are on it :) My J-Link is on its way to Segger for repair
right now, and I'd like to use my LPC-Link2 CMSIS-DAP adapter for JTAG in
the meantime. It looks like CMSIS-DAP has some higher level JTAG options
for ADIv5 targets, but the raw side is the most useful part to implement as
ADIv5 targets can already do SWD.
Cheers,
Phil
On Thu, Feb 25, 2016 at 3:57 AM, Spencer Oliver <s...@spen-soft.co.uk>
wrote:
> On 25 February 2016 at 09:38, Paul Fertser <fercer...@gmail.com> wrote:
> > Hey Spencer,
> >
> > On Thu, Feb 25, 2016 at 08:49:13AM +0000, Spencer Oliver wrote:
> >> If I recall the details CMSIS-DAP operates at the ADIv5 layer so from
> >> OpenOCD's point of view we still use the swd driver mode but change
> >> the actual adapter to JTAG mode.
> >>
> >> We should not need to implement the full jtag_interface. Try setting
> >> cmsis_dap_usg::swd_mode to false as a start.
> >
> > I'd disagree. If raw JTAG mode is implemented, CMSIS-DAP adapters
> > would become useful for all kind of OpenOCD work, including
> > heterogeneous JTAG chains, boundary scan, FPGA/CPLD configuration
> > etc. Adding just the ADIv5 JTAG mode won't buy us much, IMHO. Why
> > agree for less when we can get more? ;)
> >
>
> I agree that is a better overall solution, if someone has time to
> implement it then great.
>
> Spen
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
