Forums

xds510 jtag emulator

Started by Yasser Attarizzi October 23, 2005
hi
i design a board with c6201 and want to load the program with xds510 jtag
emulator
what is the minimum requirement for jtag emulator to detect the IC? I mean
which pins have to be pulled up and what is nesessary for example oscilator
or reset pullup?
thanks

yasser

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/



hi
thanks Dileepan. i saw that documents and as I underestand there is no need
for example to pullup the RSV pins or reset pin for the emulator to detect
the DSP.
furthermore in the datasheet of 6201 it is said that RSV pins are reserved
but said that they have to be pullup or pulldown as described there. Is that
nesessary? I mean what happened if somebody leave them unconnected?
thanks
yasser

>From: Dileepan C <dileepan_c@dile...>
>To: Yasser Attarizzi <y_attar@y_at...>
>Subject: Re: [c6x] xds510 jtag emulator
>Date: Sun, 23 Oct 2005 23:02:51 -0700 (PDT) >hi,
>
>try these links:
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra584c
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra523c
>
>also refer the datasheet for device specific details..
>
>regards,
>Dileepan.
>
>--- Yasser Attarizzi <y_attar@y_at...> wrote:
>
> > hi
> > i design a board with c6201 and want to load the
> > program with xds510 jtag
> > emulator
> > what is the minimum requirement for jtag emulator to
> > detect the IC? I mean
> > which pins have to be pulled up and what is
> > nesessary for example oscilator
> > or reset pullup?
> > thanks
> >
> > yasser
> >


Hello yasser,

For the 6201 DSP specifically - it is very important
to get the pullup/pulldown configurations correct. I
have seen incorrect 'reserved pin' configugurations
cause operational problems.

This was TI's first member of the c6x family and I
suspect that the 'reserved pins' are used for some
special factory test or analysis modes.

The following needs to be correct to 'get started'
debugging:
1. Reserved pins
2. power/ground
3. CPU clock
4. reset
5. JTAG connections - use pullups on EMU0/1

mikedunn

--- Yasser Attarizzi <y_attar@y_at...> wrote:

> hi
> thanks Dileepan. i saw that documents and as I
> underestand there is no need
> for example to pullup the RSV pins or reset pin for
> the emulator to detect
> the DSP.
> furthermore in the datasheet of 6201 it is said that
> RSV pins are reserved
> but said that they have to be pullup or pulldown as
> described there. Is that
> nesessary? I mean what happened if somebody leave
> them unconnected?
> thanks
> yasser
>
> >From: Dileepan C <dileepan_c@dile...>
> >To: Yasser Attarizzi <y_attar@y_at...>
> >Subject: Re: [c6x] xds510 jtag emulator
> >Date: Sun, 23 Oct 2005 23:02:51 -0700 (PDT)
> >
> >
> >hi,
> >
> >try these links:
> >
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra584c
> >
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra523c
> >
> >also refer the datasheet for device specific
> details..
> >
> >regards,
> >Dileepan.
> >
> >--- Yasser Attarizzi <y_attar@y_at...> wrote:
> >
> > > hi
> > > i design a board with c6201 and want to load the
> > > program with xds510 jtag
> > > emulator
> > > what is the minimum requirement for jtag
> emulator to
> > > detect the IC? I mean
> > > which pins have to be pulled up and what is
> > > nesessary for example oscilator
> > > or reset pullup?
> > > thanks
> > >
> > > yasser
> > >
>
> c6x-unsubscribe@c6x-...





HI
thanks mike
unfotunately i design the board and the PCB produced and the chips are
implemented on the board and now the jtag emulator doesn't detect the board
i want to know is it possible that the RSV pins prevent the board to be
detected by the jtag emulator
i want to know the reason of that
thanks

yasser

>From: Mike Dunn <mike-dunn@mike...>
>To: Yasser Attarizzi <y_attar@y_at...>, dileepan_c@dile...
>CC: c6x@c6x@...
>Subject: Re: [c6x] xds510 jtag emulator
>Date: Mon, 24 Oct 2005 07:39:34 -0700 (PDT)
>
>Hello yasser,
>
>For the 6201 DSP specifically - it is very important
>to get the pullup/pulldown configurations correct. I
>have seen incorrect 'reserved pin' configugurations
>cause operational problems.
>
>This was TI's first member of the c6x family and I
>suspect that the 'reserved pins' are used for some
>special factory test or analysis modes.
>
>The following needs to be correct to 'get started'
>debugging:
>1. Reserved pins
>2. power/ground
>3. CPU clock
>4. reset
>5. JTAG connections - use pullups on EMU0/1
>
>mikedunn
>
>--- Yasser Attarizzi <y_attar@y_at...> wrote:
>
> > hi
> > thanks Dileepan. i saw that documents and as I
> > underestand there is no need
> > for example to pullup the RSV pins or reset pin for
> > the emulator to detect
> > the DSP.
> > furthermore in the datasheet of 6201 it is said that
> > RSV pins are reserved
> > but said that they have to be pullup or pulldown as
> > described there. Is that
> > nesessary? I mean what happened if somebody leave
> > them unconnected?
> > thanks
> > yasser
> >
> > >From: Dileepan C <dileepan_c@dile...>
> > >To: Yasser Attarizzi <y_attar@y_at...>
> > >Subject: Re: [c6x] xds510 jtag emulator
> > >Date: Sun, 23 Oct 2005 23:02:51 -0700 (PDT)
> > >
> > >
> > >hi,
> > >
> > >try these links:
> > >
> >
> >http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra584c
> > >
> >
> >http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra523c
> > >
> > >also refer the datasheet for device specific
> > details..
> > >
> > >regards,
> > >Dileepan.
> > >
> > >--- Yasser Attarizzi <y_attar@y_at...> wrote:
> > >
> > > > hi
> > > > i design a board with c6201 and want to load the
> > > > program with xds510 jtag
> > > > emulator
> > > > what is the minimum requirement for jtag
> > emulator to
> > > > detect the IC? I mean
> > > > which pins have to be pulled up and what is
> > > > nesessary for example oscilator
> > > > or reset pullup?
> > > > thanks
> > > >
> > > > yasser
> > > >
> >
> >
> >
> >
> >
> >
> >
> > c6x-unsubscribe@c6x-...
> >
> >
> >
> >
> >
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/



Yasser,

Who is the manufacturer of your emulator??

mikedunn

--- Yasser Attarizzi <y_attar@y_at...> wrote:

>
> HI
> thanks mike
> unfotunately i design the board and the PCB produced
> and the chips are
> implemented on the board and now the jtag emulator
> doesn't detect the board
> i want to know is it possible that the RSV pins
> prevent the board to be
> detected by the jtag emulator
> i want to know the reason of that
> thanks
>
> yasser
>
> >From: Mike Dunn <mike-dunn@mike...>
> >To: Yasser Attarizzi <y_attar@y_at...>,
> dileepan_c@dile...
> >CC: c6x@c6x@...
> >Subject: Re: [c6x] xds510 jtag emulator
> >Date: Mon, 24 Oct 2005 07:39:34 -0700 (PDT)
> >
> >Hello yasser,
> >
> >For the 6201 DSP specifically - it is very
> important
> >to get the pullup/pulldown configurations correct.
> I
> >have seen incorrect 'reserved pin' configugurations
> >cause operational problems.
> >
> >This was TI's first member of the c6x family and I
> >suspect that the 'reserved pins' are used for some
> >special factory test or analysis modes.
> >
> >The following needs to be correct to 'get started'
> >debugging:
> >1. Reserved pins
> >2. power/ground
> >3. CPU clock
> >4. reset
> >5. JTAG connections - use pullups on EMU0/1
> >
> >mikedunn
> >
> >--- Yasser Attarizzi <y_attar@y_at...> wrote:
> >
> > > hi
> > > thanks Dileepan. i saw that documents and as I
> > > underestand there is no need
> > > for example to pullup the RSV pins or reset pin
> for
> > > the emulator to detect
> > > the DSP.
> > > furthermore in the datasheet of 6201 it is said
> that
> > > RSV pins are reserved
> > > but said that they have to be pullup or pulldown
> as
> > > described there. Is that
> > > nesessary? I mean what happened if somebody
> leave
> > > them unconnected?
> > > thanks
> > > yasser
> > >
> > > >From: Dileepan C <dileepan_c@dile...>
> > > >To: Yasser Attarizzi <y_attar@y_at...>
> > > >Subject: Re: [c6x] xds510 jtag emulator
> > > >Date: Sun, 23 Oct 2005 23:02:51 -0700 (PDT)
> > > >
> > > >
> > > >hi,
> > > >
> > > >try these links:
> > > >
> > >
> >
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra584c
> > > >
> > >
> >
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra523c
> > > >
> > > >also refer the datasheet for device specific
> > > details..
> > > >
> > > >regards,
> > > >Dileepan.
> > > >
> > > >--- Yasser Attarizzi <y_attar@y_at...>
> wrote:
> > > >
> > > > > hi
> > > > > i design a board with c6201 and want to load
> the
> > > > > program with xds510 jtag
> > > > > emulator
> > > > > what is the minimum requirement for jtag
> > > emulator to
> > > > > detect the IC? I mean
> > > > > which pins have to be pulled up and what is
> > > > > nesessary for example oscilator
> > > > > or reset pullup?
> > > > > thanks
> > > > >
> > > > > yasser
> > > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > c6x-unsubscribe@c6x-...
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
_________________________________________________________________
> Express yourself instantly with MSN Messenger!
> Download today it's FREE!
>
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
> NEW! You can now post a message or access and
> search the archives of this group on DSPRelated.com:
> http://www.dsprelated.com/groups/c6x/1.php
>
> _____________________________________
> Note: If you do a simple "reply" with your email
> client, only the author of this message will receive
> your answer. You need to do a "reply all" if you
> want your answer to be distributed to the entire
> group.
>
> _____________________________________
> About this discussion group:
>
=== message truncated ===


Hello Yasser,

I have good news and bad news [hopefully not too bad].
The good news is that your JTAG scan path is working
properly - the bad news is that your 6201 is not
coming up in "emulation mode".

The key indicator
"The JTAG IR instruction scan-path length is 4 bits."
should show 8 bits instead of 4. There are two
possible causes that I am aware of [I hope that it is
#1]:
1. EMU0/1 [JTAG connector pins 13 & 14] are not pulled
up to 3.3v with a 10-20k ohm resistor. Ideally you
should check these with a scope - or, if you have some
'old fashion' wire lead resistors and some jumper
wires, you could connect connect resistors pin 5 -->
13 and pin 5 --> 14.
2. The reserved pins are not configured properly.

Let us know what happens.

mikedunn

----reply from Yasser----
hi
thanks mike
i did what you told me and found out lot of things
about the jtag
here the output of that commanns:

This utility is named `XDSPROBE'.
It is used to probe scan-controllers and scan-paths.
It uses Release-3 of the Unified-SCIF stack.

It is version `3.01.07'.
It is dated `Apr 10 2001'.
It is Copyright (c) 1990-2001 by Texas Instruments
Incorporated.

This utility has determined the operating system is
Win98.

---[Open the
controller]----

The IO port address 0x240 will be used.
Requesting Unified-SCIF to detect and open the
controller.
The controller has been detected and opened
successfully.

---[Perform the scan-path length test on the JTAG IR
and DR]----

Allocated 0x800 words of scan-controller memory, base
0x0
Changed the JTAG state to Test-Logic-Reset.

The test for the JTAG IR instruction scan-path length
succeeded.
The JTAG IR instruction scan-path length is 4 bits.
The many-ones plus many-zeros tested length was 4
bits.
The many-zeros plus many-ones tested length was 4
bits.

The test for the JTAG DR bypass scan-path length
succeeded.
The JTAG DR bypass scan-path length is 1 bits.
The many-ones plus many-zeros tested length was 1
bits.
The many-zeros plus many-ones tested length was 1
bits.
Freed all scan-controller memory.

The scan-path appears to consist of just one device.

The JTAG IR register for a single ARM7 or ARM9 device
has 4 bits.
The JTAG IR register for a single classic TI DSP
device has 8 bits.
The JTAG IR register for a single IceMaker TI DSP
device has 38 bits.
The JTAG IR register for a single C621x or C671x
device has 46 bits.

The older TI DSP devices with classic emulation
include the:
C4x, C5x, C8x, C20x, C24x products.
The newer TI DSP devices with classic emulation
include the:
VC33, C54x, C620x and C670x products.
The TI DSP devices with IceMaker emulation include
the:
C27x, C28x, C55x and C64x products.

If the scan-path consists of only TI DSP chips, TI ARM
cores
and TI micro-controllers, or 8-bit long bypassed
devices,
then the measured lengths indicate that both the
link-delay and scan-path are configured correctly.

---[Perform the scan-path integrity test on the JTAG
IR]--------
<<<<<<<<<----- snip ---------------->>>>>>>>>>>>>>
---[Close the
controller]---

Requesting Unified-SCIF to close the controller.
The controller has been closed successfully.
////////////////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////

--- Mike Dunn <mike-dunn@mike...> wrote:

> Yasser,
>
> Have you ever used a TI utility called
> 'xdsprobe.exe'??
>
> It is available from a DOS prompt in .../cc/bin/
>
> 1. from a DOS prompt enter 'xdsprobe -hv
> >xdsprobe.txt'. This will give you more info than
> you
> ever wanted to know about the utility - you may need
> it for reference.
> 2. enter the command
> 'xdsprobe -fbrddat/ccbrd0.dat -v'
> This requires that you have already run ccs setup
> correctly for your emulator. This is just a
> practice
> command to see that everything is okay. You should
> get a bunch of text ending with something like 'JTAG
> reset successfully completed'.
> 3. Next check out the integrity [and size] of your
> JTAG scan chain by executing the following command
> [the results will be saved in test1.txt].
> 'xdsprobe -fbrddat/ccbrd0.dat -v -i >test1.txt'
> There are three pieces of important info that are
> important at this stage -
> a. does the last line say something about completed
> successfully or succeded??
> b. a few lines down from the top, a line should say
> something like:
> The JTAG IR instruction scan-path length is ?? bits.
> c. just below that line is a line like:
> The JTAG DR bypass scan-path length is ?? bits.
>
> Please post the entire contents of test.txt
>
> mikedunn
> --- Yasser Attarizzi <y_attar@y_at...> wrote:
>
> >
> > it is IcePack that is an ISA jtag emulator
> > compatible with xds510 from
> > softronix
> >
> >
> > >From: Mike Dunn <mike-dunn@mike...>
> > >To: Yasser Attarizzi <y_attar@y_at...>,
> > dileepan_c@dile...
> > >CC: c6x@c6x@...
> > >Subject: Re: [c6x] xds510 jtag emulator
> > >Date: Tue, 25 Oct 2005 07:17:21 -0700 (PDT)
> > >
> > >Yasser,
> > >
> > >Who is the manufacturer of your emulator??
> > >
> > >mikedunn
> > >
> > >--- Yasser Attarizzi <y_attar@y_at...> wrote:
> > >
> > > >
> > > > HI
> > > > thanks mike
> > > > unfotunately i design the board and the PCB
> > produced
> > > > and the chips are
> > > > implemented on the board and now the jtag
> > emulator
> > > > doesn't detect the board
> > > > i want to know is it possible that the RSV
> pins
> > > > prevent the board to be
> > > > detected by the jtag emulator
> > > > i want to know the reason of that
> > > > thanks
> > > >
> > > > yasser
> > > >
> > > > >From: Mike Dunn <mike-dunn@mike...>
> > > > >To: Yasser Attarizzi <y_attar@y_at...>,
> > > > dileepan_c@dile...
> > > > >CC: c6x@c6x@...
> > > > >Subject: Re: [c6x] xds510 jtag emulator
> > > > >Date: Mon, 24 Oct 2005 07:39:34 -0700 (PDT)
> > > > >
> > > > >Hello yasser,
> > > > >
> > > > >For the 6201 DSP specifically - it is very
> > > > important
> > > > >to get the pullup/pulldown configurations
> > correct.
> > > > I
> > > > >have seen incorrect 'reserved pin'
> > configugurations
> > > > >cause operational problems.
> > > > >
> > > > >This was TI's first member of the c6x family
> > and I
> > > > >suspect that the 'reserved pins' are used for
> > some
> > > > >special factory test or analysis modes.
> > > > >
> > > > >The following needs to be correct to 'get
> > started'
> > > > >debugging:
> > > > >1. Reserved pins
> > > > >2. power/ground
> > > > >3. CPU clock
> > > > >4. reset
> > > > >5. JTAG connections - use pullups on EMU0/1
> > > > >
> > > > >mikedunn
> > > > >
> > > > >--- Yasser Attarizzi <y_attar@y_at...>
> > wrote:
> > > > >
> > > > > > hi
> > > > > > thanks Dileepan. i saw that documents and
> as
> > I
> > > > > > underestand there is no need
> > > > > > for example to pullup the RSV pins or
> reset
> > pin
> > > > for
> > > > > > the emulator to detect
> > > > > > the DSP.
> > > > > > furthermore in the datasheet of 6201 it is
> > said
> > > > that
> > > > > > RSV pins are reserved
> > > > > > but said that they have to be pullup or
> > pulldown
> > > > as
> > > > > > described there. Is that
> > > > > > nesessary? I mean what happened if
> somebody
> > > > leave
> > > > > > them unconnected?
> > > > > > thanks
> > > > > > yasser
> > > > > >
> > > > > > >From: Dileepan C <dileepan_c@dile...>
> > > > > > >To: Yasser Attarizzi
> <y_attar@y_at...>
> > > > > > >Subject: Re: [c6x] xds510 jtag emulator
> > > > > > >Date: Sun, 23 Oct 2005 23:02:51 -0700
> (PDT)
> > > > > > >
> > > > > > >
> > > > > > >hi,
> > > > > > >
> > > > > > >try these links:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra584c
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra523c
> > > > > > >
> > > > > > >also refer the datasheet for device
> > specific
> > > > > > details..
> > > > > > >
> > > > > > >regards,
> > > > > > >Dileepan.
> > > > > > >
> > > > > > >--- Yasser Attarizzi
> <y_attar@y_at...>
> > > > wrote:
> > > > > > >
> > > > > > > > hi
> > > > > > > > i design a board with c6201 and want
> to
> > load
> > > > the
> > > > > > > > program with xds510 jtag
> > > > > > > > emulator
> > > > > > > > what is the minimum requirement for
> jtag
> > > > > > emulator to
> > > > > > > > detect the IC? I mean
> > > > > > > > which pins have to be pulled up and
> what
> > is
> > > > > > > > nesessary for example oscilator
> > > > > > > > or reset pullup?
> > > > > > > > thanks
> > > > > > > >
> > > > > > > > yasser
> > > > > > > >
> > > > > >
> > > > > >
>
=== message truncated ===



hi mike

thanks for very helpfull advices

i have pulled up EMU0/1 with 4.7k resistors now i changed the resistor to
20k and furthermore I see that there is ripple in the 3.3v i add capasitor
to the vcc and ripple decreased
nor that commands said that IR length is 8bit and DR length is 1 bit, what
is ur idea?
furtheremore after Isaw that the IR length is changed I start code composer
studio hopping that it detect the IC but it didn't and the current increases
about 100mA.

thanks

yasser

>From: Mike Dunn <mike-dunn@mike...>
>To: Yasser Attarizzi <y_attar@y_at...>, c6x@c6x@...
>Subject: Re: [c6x] xds510 jtag emulator
>Date: Wed, 26 Oct 2005 06:23:03 -0700 (PDT)
>
>Hello Yasser,
>
>I have good news and bad news [hopefully not too bad].
>The good news is that your JTAG scan path is working
>properly - the bad news is that your 6201 is not
>coming up in "emulation mode".
>
>The key indicator
>"The JTAG IR instruction scan-path length is 4 bits."
>should show 8 bits instead of 4. There are two
>possible causes that I am aware of [I hope that it is
>#1]:
>1. EMU0/1 [JTAG connector pins 13 & 14] are not pulled
>up to 3.3v with a 10-20k ohm resistor. Ideally you
>should check these with a scope - or, if you have some
>'old fashion' wire lead resistors and some jumper
>wires, you could connect connect resistors pin 5 -->
>13 and pin 5 --> 14.
>2. The reserved pins are not configured properly.
>
>Let us know what happens.
>
>mikedunn
>
>----reply from Yasser----
>hi
>thanks mike
>i did what you told me and found out lot of things
>about the jtag
>here the output of that commanns:
>
>This utility is named `XDSPROBE'.
>It is used to probe scan-controllers and scan-paths.
>It uses Release-3 of the Unified-SCIF stack.
>
>It is version `3.01.07'.
>It is dated `Apr 10 2001'.
>It is Copyright (c) 1990-2001 by Texas Instruments
>Incorporated.
>
>This utility has determined the operating system is
>Win98.
>
>---[Open the
>controller]----
>
>The IO port address 0x240 will be used.
>Requesting Unified-SCIF to detect and open the
>controller.
>The controller has been detected and opened
>successfully.
>
>---[Perform the scan-path length test on the JTAG IR
>and DR]----
>
>Allocated 0x800 words of scan-controller memory, base
>0x0
>Changed the JTAG state to Test-Logic-Reset.
>
>The test for the JTAG IR instruction scan-path length
>succeeded.
>The JTAG IR instruction scan-path length is 4 bits.
>The many-ones plus many-zeros tested length was 4
>bits.
>The many-zeros plus many-ones tested length was 4
>bits.
>
>The test for the JTAG DR bypass scan-path length
>succeeded.
>The JTAG DR bypass scan-path length is 1 bits.
>The many-ones plus many-zeros tested length was 1
>bits.
>The many-zeros plus many-ones tested length was 1
>bits.
>Freed all scan-controller memory.
>
>The scan-path appears to consist of just one device.
>
>The JTAG IR register for a single ARM7 or ARM9 device
>has 4 bits.
>The JTAG IR register for a single classic TI DSP
>device has 8 bits.
>The JTAG IR register for a single IceMaker TI DSP
>device has 38 bits.
>The JTAG IR register for a single C621x or C671x
>device has 46 bits.
>
>The older TI DSP devices with classic emulation
>include the:
> C4x, C5x, C8x, C20x, C24x products.
>The newer TI DSP devices with classic emulation
>include the:
> VC33, C54x, C620x and C670x products.
>The TI DSP devices with IceMaker emulation include
>the:
> C27x, C28x, C55x and C64x products.
>
>If the scan-path consists of only TI DSP chips, TI ARM
>cores
>and TI micro-controllers, or 8-bit long bypassed
>devices,
>then the measured lengths indicate that both the
>link-delay and scan-path are configured correctly.
>
>---[Perform the scan-path integrity test on the JTAG
>IR]--------
><<<<<<<<<----- snip ---------------->>>>>>>>>>>>>>
>---[Close the
>controller]---
>
>Requesting Unified-SCIF to close the controller.
>The controller has been closed successfully.
>////////////////////////////////////////////////////////////////////////////////////////
>//////////////////////////////////////////////////
>
>--- Mike Dunn <mike-dunn@mike...> wrote:
>
> > Yasser,
> >
> > Have you ever used a TI utility called
> > 'xdsprobe.exe'??
> >
> > It is available from a DOS prompt in .../cc/bin/
> >
> > 1. from a DOS prompt enter 'xdsprobe -hv
> > >xdsprobe.txt'. This will give you more info than
> > you
> > ever wanted to know about the utility - you may need
> > it for reference.
> > 2. enter the command
> > 'xdsprobe -fbrddat/ccbrd0.dat -v'
> > This requires that you have already run ccs setup
> > correctly for your emulator. This is just a
> > practice
> > command to see that everything is okay. You should
> > get a bunch of text ending with something like 'JTAG
> > reset successfully completed'.
> > 3. Next check out the integrity [and size] of your
> > JTAG scan chain by executing the following command
> > [the results will be saved in test1.txt].
> > 'xdsprobe -fbrddat/ccbrd0.dat -v -i >test1.txt'
> > There are three pieces of important info that are
> > important at this stage -
> > a. does the last line say something about completed
> > successfully or succeded??
> > b. a few lines down from the top, a line should say
> > something like:
> > The JTAG IR instruction scan-path length is ?? bits.
> > c. just below that line is a line like:
> > The JTAG DR bypass scan-path length is ?? bits.
> >
> > Please post the entire contents of test.txt
> >
> > mikedunn
> > --- Yasser Attarizzi <y_attar@y_at...> wrote:
> >
> > >
> > > it is IcePack that is an ISA jtag emulator
> > > compatible with xds510 from
> > > softronix
> > >
> > >
> > > >From: Mike Dunn <mike-dunn@mike...>
> > > >To: Yasser Attarizzi <y_attar@y_at...>,
> > > dileepan_c@dile...
> > > >CC: c6x@c6x@...
> > > >Subject: Re: [c6x] xds510 jtag emulator
> > > >Date: Tue, 25 Oct 2005 07:17:21 -0700 (PDT)
> > > >
> > > >Yasser,
> > > >
> > > >Who is the manufacturer of your emulator??
> > > >
> > > >mikedunn
> > > >
> > > >--- Yasser Attarizzi <y_attar@y_at...> wrote:
> > > >
> > > > >
> > > > > HI
> > > > > thanks mike
> > > > > unfotunately i design the board and the PCB
> > > produced
> > > > > and the chips are
> > > > > implemented on the board and now the jtag
> > > emulator
> > > > > doesn't detect the board
> > > > > i want to know is it possible that the RSV
> > pins
> > > > > prevent the board to be
> > > > > detected by the jtag emulator
> > > > > i want to know the reason of that
> > > > > thanks
> > > > >
> > > > > yasser
> > > > >
> > > > > >From: Mike Dunn <mike-dunn@mike...>
> > > > > >To: Yasser Attarizzi <y_attar@y_at...>,
> > > > > dileepan_c@dile...
> > > > > >CC: c6x@c6x@...
> > > > > >Subject: Re: [c6x] xds510 jtag emulator
> > > > > >Date: Mon, 24 Oct 2005 07:39:34 -0700 (PDT)
> > > > > >
> > > > > >Hello yasser,
> > > > > >
> > > > > >For the 6201 DSP specifically - it is very
> > > > > important
> > > > > >to get the pullup/pulldown configurations
> > > correct.
> > > > > I
> > > > > >have seen incorrect 'reserved pin'
> > > configugurations
> > > > > >cause operational problems.
> > > > > >
> > > > > >This was TI's first member of the c6x family
> > > and I
> > > > > >suspect that the 'reserved pins' are used for
> > > some
> > > > > >special factory test or analysis modes.
> > > > > >
> > > > > >The following needs to be correct to 'get
> > > started'
> > > > > >debugging:
> > > > > >1. Reserved pins
> > > > > >2. power/ground
> > > > > >3. CPU clock
> > > > > >4. reset
> > > > > >5. JTAG connections - use pullups on EMU0/1
> > > > > >
> > > > > >mikedunn
> > > > > >
> > > > > >--- Yasser Attarizzi <y_attar@y_at...>
> > > wrote:
> > > > > >
> > > > > > > hi
> > > > > > > thanks Dileepan. i saw that documents and
> > as
> > > I
> > > > > > > underestand there is no need
> > > > > > > for example to pullup the RSV pins or
> > reset
> > > pin
> > > > > for
> > > > > > > the emulator to detect
> > > > > > > the DSP.
> > > > > > > furthermore in the datasheet of 6201 it is
> > > said
> > > > > that
> > > > > > > RSV pins are reserved
> > > > > > > but said that they have to be pullup or
> > > pulldown
> > > > > as
> > > > > > > described there. Is that
> > > > > > > nesessary? I mean what happened if
> > somebody
> > > > > leave
> > > > > > > them unconnected?
> > > > > > > thanks
> > > > > > > yasser
> > > > > > >
> > > > > > > >From: Dileepan C <dileepan_c@dile...>
> > > > > > > >To: Yasser Attarizzi
> > <y_attar@y_at...>
> > > > > > > >Subject: Re: [c6x] xds510 jtag emulator
> > > > > > > >Date: Sun, 23 Oct 2005 23:02:51 -0700
> > (PDT)
> > > > > > > >
> > > > > > > >
> > > > > > > >hi,
> > > > > > > >
> > > > > > > >try these links:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra584c
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra523c
> > > > > > > >
> > > > > > > >also refer the datasheet for device
> > > specific
> > > > > > > details..
> > > > > > > >
> > > > > > > >regards,
> > > > > > > >Dileepan.
> > > > > > > >
> > > > > > > >--- Yasser Attarizzi
> > <y_attar@y_at...>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > hi
> > > > > > > > > i design a board with c6201 and want
> > to
> > > load
> > > > > the
> > > > > > > > > program with xds510 jtag
> > > > > > > > > emulator
> > > > > > > > > what is the minimum requirement for
> > jtag
> > > > > > > emulator to
> > > > > > > > > detect the IC? I mean
> > > > > > > > > which pins have to be pulled up and
> > what
> > > is
> > > > > > > > > nesessary for example oscilator
> > > > > > > > > or reset pullup?
> > > > > > > > > thanks
> > > > > > > > >
> > > > > > > > > yasser
> > > > > > > > >
> > > > > > >
> > > > > > >
> >
>=== message truncated === >
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/



Yasser,

Some current increase while bring up CCS is normal - I
am not sure what the typical amount of current
increase might be.

I assume that you have configured CCS for a 620x
target device.

What error message do you get from CCS - I suspect
that it is "can't initialize target".

What is the configuration of yout 'boot mode pins'??

,mikedunn
--- Yasser Attarizzi <y_attar@y_at...> wrote:

>
> hi mike
>
> thanks for very helpfull advices
>
> i have pulled up EMU0/1 with 4.7k resistors now i
> changed the resistor to
> 20k and furthermore I see that there is ripple in
> the 3.3v i add capasitor
> to the vcc and ripple decreased
> nor that commands said that IR length is 8bit and DR
> length is 1 bit, what
> is ur idea?
> furtheremore after Isaw that the IR length is
> changed I start code composer
> studio hopping that it detect the IC but it didn't
> and the current increases
> about 100mA.
>
> thanks
>
> yasser
>
> >From: Mike Dunn <mike-dunn@mike...>
> >To: Yasser Attarizzi <y_attar@y_at...>,
> c6x@c6x@...
> >Subject: Re: [c6x] xds510 jtag emulator
> >Date: Wed, 26 Oct 2005 06:23:03 -0700 (PDT)
> >
> >Hello Yasser,
> >
> >I have good news and bad news [hopefully not too
> bad].
> >The good news is that your JTAG scan path is
> working
> >properly - the bad news is that your 6201 is not
> >coming up in "emulation mode".
> >
> >The key indicator
> >"The JTAG IR instruction scan-path length is 4
> bits."
> >should show 8 bits instead of 4. There are two
> >possible causes that I am aware of [I hope that it
> is
> >#1]:
> >1. EMU0/1 [JTAG connector pins 13 & 14] are not
> pulled
> >up to 3.3v with a 10-20k ohm resistor. Ideally you
> >should check these with a scope - or, if you have
> some
> >'old fashion' wire lead resistors and some jumper
> >wires, you could connect connect resistors pin 5
> -->
> >13 and pin 5 --> 14.
> >2. The reserved pins are not configured properly.
> >
> >Let us know what happens.
> >
> >mikedunn
> >
> >----reply from Yasser----
> >hi
> >thanks mike
> >i did what you told me and found out lot of things
> >about the jtag
> >here the output of that commanns:
> >
> >This utility is named `XDSPROBE'.
> >It is used to probe scan-controllers and
> scan-paths.
> >It uses Release-3 of the Unified-SCIF stack.
> >
> >It is version `3.01.07'.
> >It is dated `Apr 10 2001'.
> >It is Copyright (c) 1990-2001 by Texas Instruments
> >Incorporated.
> >
> >This utility has determined the operating system is
> >Win98.
> >
> >---[Open the
> >controller]----
> >
> >The IO port address 0x240 will be used.
> >Requesting Unified-SCIF to detect and open the
> >controller.
> >The controller has been detected and opened
> >successfully.
> >
> >---[Perform the scan-path length test on the JTAG
> IR
> >and DR]----
> >
> >Allocated 0x800 words of scan-controller memory,
> base
> >0x0
> >Changed the JTAG state to Test-Logic-Reset.
> >
> >The test for the JTAG IR instruction scan-path
> length
> >succeeded.
> >The JTAG IR instruction scan-path length is 4 bits.
> >The many-ones plus many-zeros tested length was 4
> >bits.
> >The many-zeros plus many-ones tested length was 4
> >bits.
> >
> >The test for the JTAG DR bypass scan-path length
> >succeeded.
> >The JTAG DR bypass scan-path length is 1 bits.
> >The many-ones plus many-zeros tested length was 1
> >bits.
> >The many-zeros plus many-ones tested length was 1
> >bits.
> >Freed all scan-controller memory.
> >
> >The scan-path appears to consist of just one
> device.
> >
> >The JTAG IR register for a single ARM7 or ARM9
> device
> >has 4 bits.
> >The JTAG IR register for a single classic TI DSP
> >device has 8 bits.
> >The JTAG IR register for a single IceMaker TI DSP
> >device has 38 bits.
> >The JTAG IR register for a single C621x or C671x
> >device has 46 bits.
> >
> >The older TI DSP devices with classic emulation
> >include the:
> > C4x, C5x, C8x, C20x, C24x products.
> >The newer TI DSP devices with classic emulation
> >include the:
> > VC33, C54x, C620x and C670x products.
> >The TI DSP devices with IceMaker emulation include
> >the:
> > C27x, C28x, C55x and C64x products.
> >
> >If the scan-path consists of only TI DSP chips, TI
> ARM
> >cores
> >and TI micro-controllers, or 8-bit long bypassed
> >devices,
> >then the measured lengths indicate that both the
> >link-delay and scan-path are configured correctly.
> >
> >---[Perform the scan-path integrity test on the
> JTAG
> >IR]--------
> ><<<<<<<<<----- snip ---------------->>>>>>>>>>>>>>
> >---[Close the
> >controller]---
> >
> >Requesting Unified-SCIF to close the controller.
> >The controller has been closed successfully.
>
>////////////////////////////////////////////////////////////////////////////////////////
> >//////////////////////////////////////////////////
> >
> >--- Mike Dunn <mike-dunn@mike...> wrote:
> >
> > > Yasser,
> > >
> > > Have you ever used a TI utility called
> > > 'xdsprobe.exe'??
> > >
> > > It is available from a DOS prompt in .../cc/bin/
> > >
> > > 1. from a DOS prompt enter 'xdsprobe -hv
> > > >xdsprobe.txt'. This will give you more info
> than
> > > you
> > > ever wanted to know about the utility - you may
> need
> > > it for reference.
> > > 2. enter the command
> > > 'xdsprobe -fbrddat/ccbrd0.dat -v'
> > > This requires that you have already run ccs
> setup
> > > correctly for your emulator. This is just a
> > > practice
> > > command to see that everything is okay. You
> should
> > > get a bunch of text ending with something like
> 'JTAG
> > > reset successfully completed'.
> > > 3. Next check out the integrity [and size] of
> your
> > > JTAG scan chain by executing the following
> command
> > > [the results will be saved in test1.txt].
> > > 'xdsprobe -fbrddat/ccbrd0.dat -v -i >test1.txt'
> > > There are three pieces of important info that
> are
> > > important at this stage -
> > > a. does the last line say something about
> completed
> > > successfully or succeded??
> > > b. a few lines down from the top, a line should
> say
> > > something like:
>
=== message truncated ===



hi mike
yes the error message is what you said
Is the state of bootmode pins important for jtag emulation to start?
all of them are 0. I know that's not allowed but I didn't know that the
state of bootmode pins are important but I can change their state . what
state they have to be?

thannks alot
yasser >From: Mike Dunn <mike-dunn@mike...>
>To: Yasser Attarizzi <y_attar@y_at...>
>CC: c6x@c6x@...
>Subject: Re: [c6x] xds510 jtag emulator
>Date: Wed, 26 Oct 2005 12:51:42 -0700 (PDT)
>
>Yasser,
>
>Some current increase while bring up CCS is normal - I
>am not sure what the typical amount of current
>increase might be.
>
>I assume that you have configured CCS for a 620x
>target device.
>
>What error message do you get from CCS - I suspect
>that it is "can't initialize target".
>
>What is the configuration of yout 'boot mode pins'??
>
>,mikedunn
>--- Yasser Attarizzi <y_attar@y_at...> wrote:
>
> >
> > hi mike
> >
> > thanks for very helpfull advices
> >
> > i have pulled up EMU0/1 with 4.7k resistors now i
> > changed the resistor to
> > 20k and furthermore I see that there is ripple in
> > the 3.3v i add capasitor
> > to the vcc and ripple decreased
> > nor that commands said that IR length is 8bit and DR
> > length is 1 bit, what
> > is ur idea?
> > furtheremore after Isaw that the IR length is
> > changed I start code composer
> > studio hopping that it detect the IC but it didn't
> > and the current increases
> > about 100mA.
> >
> > thanks
> >
> > yasser
> >
> > >From: Mike Dunn <mike-dunn@mike...>
> > >To: Yasser Attarizzi <y_attar@y_at...>,
> > c6x@c6x@...
> > >Subject: Re: [c6x] xds510 jtag emulator
> > >Date: Wed, 26 Oct 2005 06:23:03 -0700 (PDT)
> > >
> > >Hello Yasser,
> > >
> > >I have good news and bad news [hopefully not too
> > bad].
> > >The good news is that your JTAG scan path is
> > working
> > >properly - the bad news is that your 6201 is not
> > >coming up in "emulation mode".
> > >
> > >The key indicator
> > >"The JTAG IR instruction scan-path length is 4
> > bits."
> > >should show 8 bits instead of 4. There are two
> > >possible causes that I am aware of [I hope that it
> > is
> > >#1]:
> > >1. EMU0/1 [JTAG connector pins 13 & 14] are not
> > pulled
> > >up to 3.3v with a 10-20k ohm resistor. Ideally you
> > >should check these with a scope - or, if you have
> > some
> > >'old fashion' wire lead resistors and some jumper
> > >wires, you could connect connect resistors pin 5
> > -->
> > >13 and pin 5 --> 14.
> > >2. The reserved pins are not configured properly.
> > >
> > >Let us know what happens.
> > >
> > >mikedunn
> > >
> > >----reply from Yasser----
> > >hi
> > >thanks mike
> > >i did what you told me and found out lot of things
> > >about the jtag
> > >here the output of that commanns:
> > >
> > >This utility is named `XDSPROBE'.
> > >It is used to probe scan-controllers and
> > scan-paths.
> > >It uses Release-3 of the Unified-SCIF stack.
> > >
> > >It is version `3.01.07'.
> > >It is dated `Apr 10 2001'.
> > >It is Copyright (c) 1990-2001 by Texas Instruments
> > >Incorporated.
> > >
> > >This utility has determined the operating system is
> > >Win98.
> > >
> > >---[Open the
> > >controller]----
> > >
> > >The IO port address 0x240 will be used.
> > >Requesting Unified-SCIF to detect and open the
> > >controller.
> > >The controller has been detected and opened
> > >successfully.
> > >
> > >---[Perform the scan-path length test on the JTAG
> > IR
> > >and DR]----
> > >
> > >Allocated 0x800 words of scan-controller memory,
> > base
> > >0x0
> > >Changed the JTAG state to Test-Logic-Reset.
> > >
> > >The test for the JTAG IR instruction scan-path
> > length
> > >succeeded.
> > >The JTAG IR instruction scan-path length is 4 bits.
> > >The many-ones plus many-zeros tested length was 4
> > >bits.
> > >The many-zeros plus many-ones tested length was 4
> > >bits.
> > >
> > >The test for the JTAG DR bypass scan-path length
> > >succeeded.
> > >The JTAG DR bypass scan-path length is 1 bits.
> > >The many-ones plus many-zeros tested length was 1
> > >bits.
> > >The many-zeros plus many-ones tested length was 1
> > >bits.
> > >Freed all scan-controller memory.
> > >
> > >The scan-path appears to consist of just one
> > device.
> > >
> > >The JTAG IR register for a single ARM7 or ARM9
> > device
> > >has 4 bits.
> > >The JTAG IR register for a single classic TI DSP
> > >device has 8 bits.
> > >The JTAG IR register for a single IceMaker TI DSP
> > >device has 38 bits.
> > >The JTAG IR register for a single C621x or C671x
> > >device has 46 bits.
> > >
> > >The older TI DSP devices with classic emulation
> > >include the:
> > > C4x, C5x, C8x, C20x, C24x products.
> > >The newer TI DSP devices with classic emulation
> > >include the:
> > > VC33, C54x, C620x and C670x products.
> > >The TI DSP devices with IceMaker emulation include
> > >the:
> > > C27x, C28x, C55x and C64x products.
> > >
> > >If the scan-path consists of only TI DSP chips, TI
> > ARM
> > >cores
> > >and TI micro-controllers, or 8-bit long bypassed
> > >devices,
> > >then the measured lengths indicate that both the
> > >link-delay and scan-path are configured correctly.
> > >
> > >---[Perform the scan-path integrity test on the
> > JTAG
> > >IR]--------
> > ><<<<<<<<<----- snip ---------------->>>>>>>>>>>>>>
> > >---[Close the
> > >controller]---
> > >
> > >Requesting Unified-SCIF to close the controller.
> > >The controller has been closed successfully.
> >
> >////////////////////////////////////////////////////////////////////////////////////////
> > >//////////////////////////////////////////////////
> > >
> > >--- Mike Dunn <mike-dunn@mike...> wrote:
> > >
> > > > Yasser,
> > > >
> > > > Have you ever used a TI utility called
> > > > 'xdsprobe.exe'??
> > > >
> > > > It is available from a DOS prompt in .../cc/bin/
> > > >
> > > > 1. from a DOS prompt enter 'xdsprobe -hv
> > > > >xdsprobe.txt'. This will give you more info
> > than
> > > > you
> > > > ever wanted to know about the utility - you may
> > need
> > > > it for reference.
> > > > 2. enter the command
> > > > 'xdsprobe -fbrddat/ccbrd0.dat -v'
> > > > This requires that you have already run ccs
> > setup
> > > > correctly for your emulator. This is just a
> > > > practice
> > > > command to see that everything is okay. You
> > should
> > > > get a bunch of text ending with something like
> > 'JTAG
> > > > reset successfully completed'.
> > > > 3. Next check out the integrity [and size] of
> > your
> > > > JTAG scan chain by executing the following
> > command
> > > > [the results will be saved in test1.txt].
> > > > 'xdsprobe -fbrddat/ccbrd0.dat -v -i >test1.txt'
> > > > There are three pieces of important info that
> > are
> > > > important at this stage -
> > > > a. does the last line say something about
> > completed
> > > > successfully or succeded??
> > > > b. a few lines down from the top, a line should
> > say
> > > > something like:
> >
>=== message truncated === >
>

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/



Yasser,

Please see my answers below.

mikedunn

--- Yasser Attarizzi <y_attar@y_at...> wrote:

>
> hi mike
> yes the error message is what you said
> Is the state of bootmode pins important for jtag
> emulation to start?
<mike>I have had trouble in the past with c6201
devices when the pins were configured for 'host boot'.
I would suggest that you start with 00101 [no boot,
map1]. If you are still having trouble with CCS
coming up, apply a hardware reset [I hope that you
have a reset button] and keep it applied. Open CCS
and when you see the 'splash screen', let it go. Try
it a few times to see if it helps.

> all of them are 0.
<mike>does that mean that nothing is connected to the
pins or are they all grounded??

>I know that's not allowed but I
> didn't know that the
> state of bootmode pins are important but I can
> change their state .
<mike> Anytime that you are making connections to a
device, ALWAYS select a 'legal' configuration. If the
documentation says that something is reserved or
illegal then "do not do it". BTW, 00000 is a legal
configuration.
>what state they have to be?
>
> thannks alot
> yasser > >From: Mike Dunn <mike-dunn@mike...>
> >To: Yasser Attarizzi <y_attar@y_at...>
> >CC: c6x@c6x@...
> >Subject: Re: [c6x] xds510 jtag emulator
> >Date: Wed, 26 Oct 2005 12:51:42 -0700 (PDT)
> >
> >Yasser,
> >
> >Some current increase while bring up CCS is normal
> - I
> >am not sure what the typical amount of current
> >increase might be.
> >
> >I assume that you have configured CCS for a 620x
> >target device.
> >
> >What error message do you get from CCS - I suspect
> >that it is "can't initialize target".
> >
> >What is the configuration of yout 'boot mode
> pins'??
> >
> >,mikedunn
> >--- Yasser Attarizzi <y_attar@y_at...> wrote:
> >
> > >
> > > hi mike
> > >
> > > thanks for very helpfull advices
> > >
> > > i have pulled up EMU0/1 with 4.7k resistors now
> i
> > > changed the resistor to
> > > 20k and furthermore I see that there is ripple
> in
> > > the 3.3v i add capasitor
> > > to the vcc and ripple decreased
> > > nor that commands said that IR length is 8bit
> and DR
> > > length is 1 bit, what
> > > is ur idea?
> > > furtheremore after Isaw that the IR length is
> > > changed I start code composer
> > > studio hopping that it detect the IC but it
> didn't
> > > and the current increases
> > > about 100mA.
> > >
> > > thanks
> > >
> > > yasser
> > >
> > > >From: Mike Dunn <mike-dunn@mike...>
> > > >To: Yasser Attarizzi <y_attar@y_at...>,
> > > c6x@c6x@...
> > > >Subject: Re: [c6x] xds510 jtag emulator
> > > >Date: Wed, 26 Oct 2005 06:23:03 -0700 (PDT)
> > > >
> > > >Hello Yasser,
> > > >
> > > >I have good news and bad news [hopefully not
> too
> > > bad].
> > > >The good news is that your JTAG scan path is
> > > working
> > > >properly - the bad news is that your 6201 is
> not
> > > >coming up in "emulation mode".
> > > >
> > > >The key indicator
> > > >"The JTAG IR instruction scan-path length is 4
> > > bits."
> > > >should show 8 bits instead of 4. There are two
> > > >possible causes that I am aware of [I hope that
> it
> > > is
> > > >#1]:
> > > >1. EMU0/1 [JTAG connector pins 13 & 14] are not
> > > pulled
> > > >up to 3.3v with a 10-20k ohm resistor. Ideally
> you
> > > >should check these with a scope - or, if you
> have
> > > some
> > > >'old fashion' wire lead resistors and some
> jumper
> > > >wires, you could connect connect resistors pin
> 5
> > > -->
> > > >13 and pin 5 --> 14.
> > > >2. The reserved pins are not configured
> properly.
> > > >
> > > >Let us know what happens.
> > > >
> > > >mikedunn
> > > >
> > > >----reply from Yasser----
> > > >hi
> > > >thanks mike
> > > >i did what you told me and found out lot of
> things
> > > >about the jtag
> > > >here the output of that commanns:
> > > >
> > > >This utility is named `XDSPROBE'.
> > > >It is used to probe scan-controllers and
> > > scan-paths.
> > > >It uses Release-3 of the Unified-SCIF stack.
> > > >
> > > >It is version `3.01.07'.
> > > >It is dated `Apr 10 2001'.
> > > >It is Copyright (c) 1990-2001 by Texas
> Instruments
> > > >Incorporated.
> > > >
> > > >This utility has determined the operating
> system is
> > > >Win98.
> > > >
> > > >---[Open the
> > >
> >controller]----
> > > >
> > > >The IO port address 0x240 will be used.
> > > >Requesting Unified-SCIF to detect and open the
> > > >controller.
> > > >The controller has been detected and opened
> > > >successfully.
> > > >
> > > >---[Perform the scan-path length test on the
> JTAG
> > > IR
> > > >and DR]----
> > > >
> > > >Allocated 0x800 words of scan-controller
> memory,
> > > base
> > > >0x0
> > > >Changed the JTAG state to Test-Logic-Reset.
> > > >
> > > >The test for the JTAG IR instruction scan-path
> > > length
> > > >succeeded.
> > > >The JTAG IR instruction scan-path length is 4
> bits.
> > > >The many-ones plus many-zeros tested length was
> 4
> > > >bits.
> > > >The many-zeros plus many-ones tested length was
> 4
> > > >bits.
> > > >
> > > >The test for the JTAG DR bypass scan-path
> length
> > > >succeeded.
> > > >The JTAG DR bypass scan-path length is 1 bits.
> > > >The many-ones plus many-zeros tested length was
> 1
> > > >bits.
> > > >The many-zeros plus many-ones tested length was
> 1
> > > >bits.
> > > >Freed all scan-controller memory.
> > > >
> > > >The scan-path appears to consist of just one
> > > device.
> > > >
> > > >The JTAG IR register for a single ARM7 or ARM9
> > > device
> > > >has 4 bits.
> > > >The JTAG IR register for a single classic TI
> DSP
> > > >device has 8 bits.
> > > >The JTAG IR register for a single IceMaker TI
> DSP
> > > >device has 38 bits.
> > > >The JTAG IR register for a single C621x or
> C671x
> > > >device has 46 bits.
> > > >
> > > >The older TI DSP devices with classic emulation
> > > >include the:
> > > > C4x, C5x, C8x, C20x, C24x products.
> > > >The newer TI DSP devices with classic emulation
> > > >include the:
>
=== message truncated ===