From: Oleksandr Shamray <oleksandrs@mellanox.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"jiri@resnulli.us" <jiri@resnulli.us>,
system-sw-low-level <system-sw-low-level@mellanox.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mec@shout.net" <mec@shout.net>,
"joel@jms.id.au" <joel@jms.id.au>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"vadimp@maellanox.com" <vadimp@maellanox.com>,
"tklauser@distanz.ch" <tklauser@distanz.ch>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [patch v1 0/2] JTAG driver introduction
Date: Thu, 3 Aug 2017 15:26:08 +0000 [thread overview]
Message-ID: <AM4PR0501MB2194E6B8D14EC15356C1C0BFB1B10@AM4PR0501MB2194.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20170802141209.GB25781@lunn.ch>
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: Wednesday, August 2, 2017 5:12 PM
> To: Oleksandr Shamray <oleksandrs@mellanox.com>
> Cc: gregkh@linuxfoundation.org; arnd@arndb.de; devicetree@vger.kernel.org;
> jiri@resnulli.us; system-sw-low-level <system-sw-low-level@mellanox.com>;
> openbmc@lists.ozlabs.org; linux-kernel@vger.kernel.org; mec@shout.net;
> joel@jms.id.au; linux-serial@vger.kernel.org; vadimp@maellanox.com;
> tklauser@distanz.ch; linux-arm-kernel@lists.infradead.org
> 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
> Andrew
Hi Andrew
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.
https://github.com/mellanoxbmc/mellanox-bmc-tools
Thanks
Oleksandr
next prev parent reply other threads:[~2017-08-03 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 13:18 [patch v1 0/2] JTAG driver introduction Oleksandr Shamray
2017-08-02 13:18 ` [patch v1 1/2] drivers: jtag: Add JTAG core driver Oleksandr Shamray
2017-08-02 13:44 ` Greg KH
2017-08-02 13:44 ` Greg KH
2017-08-02 14:16 ` Andrew Lunn
2017-08-02 14:24 ` Neil Armstrong
2017-08-02 15:37 ` Arnd Bergmann
2017-08-03 9:28 ` Tobias Klauser
2017-08-02 13:18 ` [patch v1 2/2] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver Oleksandr Shamray
2017-08-02 14:30 ` Neil Armstrong
2017-08-02 14:56 ` Arnd Bergmann
2017-08-02 14:54 ` Arnd Bergmann
2017-08-02 15:31 ` Randy Dunlap
2017-08-03 12:12 ` kbuild test robot
2017-08-03 14:35 ` [PATCH] drivers: jtag: fix resource_size.cocci warnings kbuild test robot
2017-08-03 14:48 ` Oleksandr Shamray
2017-08-03 14:35 ` [patch v1 2/2] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver kbuild test robot
2017-08-02 14:12 ` [patch v1 0/2] JTAG driver introduction Andrew Lunn
2017-08-03 15:26 ` Oleksandr Shamray [this message]
2017-08-03 17:48 ` Andrew Lunn
2017-08-28 20:03 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM4PR0501MB2194E6B8D14EC15356C1C0BFB1B10@AM4PR0501MB2194.eurprd05.prod.outlook.com \
--to=oleksandrs@mellanox.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mec@shout.net \
--cc=openbmc@lists.ozlabs.org \
--cc=system-sw-low-level@mellanox.com \
--cc=tklauser@distanz.ch \
--cc=vadimp@maellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).