9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] JTAG
Date: Wed, 27 Oct 2010 00:05:46 +0200	[thread overview]
Message-ID: <AANLkTinfw-GTmSBgbuucLaXB3LVaUTDa6TKOw3p=sc3Y@mail.gmail.com> (raw)
In-Reply-To: <cc658e0272de0d6ef80d77ca34708861@swcp.com>

On Tue, Oct 26, 2010 at 9:28 PM, EBo <ebo@sandien.com> wrote:
>
> I just ran into the following FAQ and info that might be of help:
>
> a JTAG FAQ: http://hri.sourceforge.net/tools/jtag_faq_org.html
>
> interesting detail:
>
> TAG specification is in Std IEEE 1149.1 (costs about $100). I don't
> have it. Please search at internet for some JTAG related documents.
> This is good: http://www-s.ti.com/sc/psheets/ssya002c/ssya002c.pdf
>
> also:
>
> You just have to write software to go through the states of JTAG FSM (here
> is the state diagram of this FSM:
> http://www.inaccessnetworks.com/projects/ianjtag/jtag-intro/jtag-state-machine-large.png).
> TCK and TMS are used to go through the states of FSM. And TDI is used to
> serially send through this interface your commands and data to JTAG
> controller on the IC (in your case, to the ARM uC) and read back reply
> through the TDO pin. The only problem is that some companies do not open all
> details about available custom JTAG commands (JTAG standard defines only 2
> necessary commands: EXTEST and SAMPLE and some optional commmands like
> INTEST, BIST and others). For example, Texas Instruments do not give an
> access to the description of commands that are used for In-Circuit Debugging
> of their TMS DSPs. Instead of, they sell this JTAG ICD with simple software
> for about 1000$!!! Nice business - such a price for 4 wires and some I/O
> ICs! ;-)
>
> Hope this helps.
>
>  EBo --
>
>

The way I think this works:

USB-MPSSE-JTAG-uP

The USB part is a simple protocol which I already have figured out and is
in the driver's .h.
http://yosemitefoothills.com/Electronics/FTDI_Chip_Commands.html

I am now looking into the MPSSE details which is a
kind of programmable controller for the JTAG which has high level commands
so that operations do not take a round trip through USB.

For this the best docs I found are the openocd code and some documents
referred in it:
http://www.ftdichip.com/Documents/AppNotes/AN2232C-01_MPSSE_Cmnd.pdf
http://openocd.berlios.de/web/

The openocd code is my main reference because it does work on linux.
If I have to I'll resort to sniffing the USB connection in linux, though I hope
it does not come to that.

After the MPSSE (or at the same time)
I have to figure the JTAG part for which probably EBo's references are good,
I haven't figured that part at all. Then there is an standard for
arm called ICE something or other (apparently there are different names and
interfaces for different versions of arm) which lets you look at the different
registers of arm and do interesting things to it. Then there is how the JTAG is
cabled inside the SoCer itself:

http://www.marvell.com/products/processors/embedded/kirkwood/HW_88F6281_OpenSource.pdf

I am working my way slowly through this sorry if this a tad
incoherent, but I haven't
figured most of it yet.

G.



  reply	other threads:[~2010-10-26 22:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2010-10-26 22:17         ` EBo
2010-11-02  6:32 Bhanu Nagendra Pisupati
2010-11-02  9:30 ` Gorka Guardiola
2010-11-02 10:28   ` Steve Simon
2010-11-02 16:01     ` Gorka Guardiola
2010-11-02 19:00     ` Eric Van Hensbergen
2010-11-02 16:45 Bakul Shah
2010-11-02 17:23 ` Nick LaForge
2010-11-02 20:00 ` Gorka Guardiola
     [not found] <mailman.17024.1288718605.1513.9fans@9fans.net>
2010-11-03  5:57 ` Bhanu Nagendra Pisupati

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='AANLkTinfw-GTmSBgbuucLaXB3LVaUTDa6TKOw3p=sc3Y@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).