RE: [patch v1 0/2] JTAG driver introduction
From: Oleksandr Shamray
Date: Thu Aug 03 2017 - 11:26:19 EST
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@xxxxxxx]
> Sent: Wednesday, August 2, 2017 5:12 PM
> To: Oleksandr Shamray <oleksandrs@xxxxxxxxxxxx>
> Cc: gregkh@xxxxxxxxxxxxxxxxxxx; arnd@xxxxxxxx; devicetree@xxxxxxxxxxxxxxx;
> jiri@xxxxxxxxxxx; system-sw-low-level <system-sw-low-level@xxxxxxxxxxxx>;
> openbmc@xxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; mec@xxxxxxxxx;
> joel@xxxxxxxxx; linux-serial@xxxxxxxxxxxxxxx; vadimp@xxxxxxxxxxxxx;
> tklauser@xxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [patch v1 0/2] JTAG driver introduction
> On Wed, Aug 02, 2017 at 04:18:36PM +0300, Oleksandr Shamray wrote:
> > When a need raise up to use JTAG interface for system's devices
> > programming or CPU debugging, it could be done from the external JTAG
> > master controller.
> > For such purpose, usually the user layer application implements jtag
> > protocol or using a proprietary connection to vendor hardware.
> > This method is slow and not generic.
> > We propose to implement general JTAG interface and infrastructure to
> > communicate with user layer application. In such way, we can have the
> > standard JTAG interface core part and separation from specific HW
> > implementation.
> > This allow new capability to debug the CPU or program system's device
> > via BMC without additional devices nor cost.
> Hi Oleksandr
> Do you have patches for OpenOCD? Or maybe i should ask it another way, what
> user space tools are you using?
Thanks a lot for review.
We used user space tool for that, which is an adaptation of some Lattice tools, which allows programming of SVF files. We are using it for Lattice CPLD burning, since we have for such devices on our system, but this tool could be used for programming other devices from other vendors as well.