From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] JTAG
Date: Tue, 2 Nov 2010 10:30:26 +0100 [thread overview]
Message-ID: <AANLkTinzKhJ33Xotyt4-Gkv+36iiM+u_PEe0h_MmNMaV@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1011020216460.12637@tank.cs.indiana.edu>
On Tue, Nov 2, 2010 at 7:32 AM, Bhanu Nagendra Pisupati
<bpisupat@cs.indiana.edu> wrote:
> I am trying to understand the end objective of the JTAG work discussed in
> one of the threads last week (sorry, I'm behind on my mails!).
> There was one response that said: "The hope is that it would help debug
> usb/bt device issues on kw."; but beyond this I could not make out the use
> case for this work from the thread.
>
> Is the idea to use JTAG as a communication pipe on which to export virtual
> filesystems from within the device? Can somebody please elaborate?
>
The idea is to use JTAG to peek/set at the registers and pins and
maybe stop/start
the sheevaplug/guruplug. The JTAG on this machines can be accessed through
an endpoint in the usb/serial console.
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2010-11-02 9:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 6:32 Bhanu Nagendra Pisupati
2010-11-02 9:30 ` Gorka Guardiola [this message]
2010-11-02 10:28 ` Steve Simon
2010-11-02 16:01 ` Gorka Guardiola
2010-11-02 19:00 ` Eric Van Hensbergen
[not found] <mailman.17024.1288718605.1513.9fans@9fans.net>
2010-11-03 5:57 ` Bhanu Nagendra Pisupati
-- strict thread matches above, loose matches on Subject: below --
2010-11-02 16:45 Bakul Shah
2010-11-02 17:23 ` Nick LaForge
2010-11-02 20:00 ` Gorka Guardiola
2010-10-26 17:49 Jeff Sickel
2010-10-26 18:20 ` Skip Tavakkolian
2010-10-26 18:31 ` Bruce Ellis
2010-10-26 18:49 ` Steve Simon
2010-10-26 19:10 ` EBo
2010-10-26 19:28 ` EBo
2010-10-26 22:05 ` Gorka Guardiola
2010-10-26 22:17 ` EBo
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=AANLkTinzKhJ33Xotyt4-Gkv+36iiM+u_PEe0h_MmNMaV@mail.gmail.com \
--to=paurea@gmail.com \
--cc=9fans@9fans.net \
/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).