Hello,

I was normally connected to my 5509A processor board, suddedly 
connection got broken and never got up again. I read that EMU0 and 
EMU1 lines should 1, but EMU1 line is somewhere betweetn 0 and 1. Is 
my emulator broken? 

I've got two diffenrent boards with 5509A and both of them are not 
working with emulator. I've also got Spectrum Digital's TMS320VC5510 
DSK board and that works.

First error is:
Sequence ID: 0
Error Code: -1155
Error Class: 0x80001240

After that always comes:
A bad parameter value was detected within
an internal data-structure of Unified-SCIF.
The controller or Unified-SCIF may be in an invalid state.
Sequence ID: 0
Error Code: -116
Error Class: 0x80003240

Aimo Parru-

> I was normally connected to my 5509A processor board, suddedly
> connection got broken and never got up again. I read that EMU0 and
> EMU1 lines should 1, but EMU1 line is somewhere betweetn 0 and 1. Is
> my emulator broken?

Don't you think it'd be a good idea to say which emulator model?  Is it
parallel port or USB or PCI plug-in?

And when you say "connection", what is that?  SDConfig?  CCS?

-Jeff

> I've got two diffenrent boards with 5509A and both of them are not
> working with emulator. I've also got Spectrum Digital's TMS320VC5510
> DSK board and that works.
>
> First error is:
> Sequence ID: 0
> Error Code: -1155
> Error Class: 0x80001240
>
> After that always comes:
> A bad parameter value was detected within
> an internal data-structure of Unified-SCIF.
> The controller or Unified-SCIF may be in an invalid state.
> Sequence ID: 0
> Error Code: -116
> Error Class: 0x80003240

Aimo Parru-
>
>>  I was normally connected to my 5509A processor board, suddedly
>>  connection got broken and never got up again. I read that EMU0 and
>>  EMU1 lines should 1, but EMU1 line is somewhere betweetn 0 and 1. Is
>>  my emulator broken?
>
>Don't you think it'd be a good idea to say which emulator model? 
 
Yes it is. Sorry for my inaccuracy.

>Is it
>parallel port or USB or PCI plug-in?

It is in USB port. Blackhawk XDS560 USB Emulator with European Power Cords, TMDSEMU560U-0E.

>And when you say "connection", what is that?  SDConfig?  CCS?

With "connection" I mean connection between IDE and processor, that I can see memory,
registers and debug programs. CCS 3.1 is IDE what I'm using.

>-Jeff
>
>>  I've got two diffenrent boards with 5509A and both of them are not
>>  working with emulator. I've also got Spectrum Digital's TMS320VC5510
>>  DSK board and that works.
>> 
>>  First error is:
>>  Sequence ID: 0
>>  Error Code: -1155
>>  Error Class: 0x80001240
>> 
>>  After that always comes:
>>  A bad parameter value was detected within
>>  an internal data-structure of Unified-SCIF.
>>  The controller or Unified-SCIF may be in an invalid state.
>>  Sequence ID: 0
>>  Error Code: -116
>>  Error Class: 0x80003240

Aimo Parru-

> It is in USB port. Blackhawk XDS560 USB Emulator with European Power
> Cords, TMDSEMU560U-0E.
> 
> >And when you say "connection", what is that?  SDConfig?  CCS?
> 
> With "connection" I mean connection between IDE and processor, that
> I can see memory, registers and debug programs. CCS 3.1 is IDE what
> I'm using.

What happens if you run SDConfig utility?  That is more basic test than CCS, it can
help isolate problem between your system (CCS setup, software, etc), board, and
emulator.

-Jeff

> >>  I've got two diffenrent boards with 5509A and both of them are not
> >>  working with emulator. I've also got Spectrum Digital's TMS320VC5510
> >>  DSK board and that works.
> >>
> >>  First error is:
> >>  Sequence ID: 0
> >>  Error Code: -1155
> >>  Error Class: 0x80001240
> >>
> >>  After that always comes:
> >>  A bad parameter value was detected within
> >>  an internal data-structure of Unified-SCIF.
> >>  The controller or Unified-SCIF may be in an invalid state.
> >>  Sequence ID: 0
> >>  Error Code: -116
> >>  Error Class: 0x80003240

Aimo Parru-
>
>>  It is in USB port. Blackhawk XDS560 USB Emulator with European Power
>>  Cords, TMDSEMU560U-0E.
>>  
>>  > And when you say "connection", what is that?  SDConfig?  CCS?
>>  
>>  With "connection" I mean connection between IDE and processor, that
>>  I can see memory, registers and debug programs. CCS 3.1 is IDE what
>>  I'm using.
>
>What happens if you run SDConfig utility?  That is more basic test than CCS, it can
>help isolate problem between your system (CCS setup, software, etc), board, and
>emulator.
>
>-Jeff

Nothing happened. I'm using XDS560 emulator and SDConfig utility only works with XDS510
emulator. I tried to use SDConfig but it didn't find XDS560 USB emulator.

>
>>  > >   I've got two diffenrent boards with 5509A and both of them are not
>>  > >   working with emulator. I've also got Spectrum Digital's TMS320VC5510
>>  > >   DSK board and that works.
>>  > > 
>>  > >   First error is:
>>  > >   Sequence ID: 0
>>  > >   Error Code: -1155
>>  > >   Error Class: 0x80001240
>>  > > 
>>  > >   After that always comes:
>>  > >   A bad parameter value was detected within
>>  > >   an internal data-structure of Unified-SCIF.
>>  > >   The controller or Unified-SCIF may be in an invalid state.
>>  > >   Sequence ID: 0
>>  > >   Error Code: -116
>>  > >   Error Class: 0x80003240

Aimo Parru-

> >>  It is in USB port. Blackhawk XDS560 USB Emulator with European Power
> >>  Cords, TMDSEMU560U-0E.
> >>
> >>  > And when you say "connection", what is that?  SDConfig?  CCS?
> >>
> >>  With "connection" I mean connection between IDE and processor, that
> >>  I can see memory, registers and debug programs. CCS 3.1 is IDE what
> >>  I'm using.
> >
> >What happens if you run SDConfig utility?  That is more basic test than CCS, it can
> >help isolate problem between your system (CCS setup, software, etc), board, and
> >emulator.
> >
> >-Jeff
> 
> Nothing happened. I'm using XDS560 emulator and SDConfig utility only works
> with XDS510 emulator. I tried to use SDConfig but it didn't find XDS560 USB
> emulator.

"Didn't find" means what?  What error message to do you get?  Did you load the
correct driver?

-Jeff

> >>  > >   I've got two diffenrent boards with 5509A and both of them are not
> >>  > >   working with emulator. I've also got Spectrum Digital's
TMS320VC5510
> >>  > >   DSK board and that works.
> >>  > >
> >>  > >   First error is:
> >>  > >   Sequence ID: 0
> >>  > >   Error Code: -1155
> >>  > >   Error Class: 0x80001240
> >>  > >
> >>  > >   After that always comes:
> >>  > >   A bad parameter value was detected within
> >>  > >   an internal data-structure of Unified-SCIF.
> >>  > >   The controller or Unified-SCIF may be in an invalid state.
> >>  > >   Sequence ID: 0
> >>  > >   Error Code: -116
> >>  > >   Error Class: 0x80003240

Aimo Parru-
>
>>  > >   It is in USB port. Blackhawk XDS560 USB Emulator with European Power
>>  > >   Cords, TMDSEMU560U-0E.
>>  > > 
>>  > >   >  And when you say "connection", what is that?  SDConfig? 
CCS?
>>  > > 
>>  > >   With "connection" I mean connection between IDE and processor,
that
>>  > >   I can see memory, registers and debug programs. CCS 3.1 is IDE what
>>  > >   I'm using.
>>  > 
>>  > What happens if you run SDConfig utility?  That is more basic test than CCS, it
can
>>  > help isolate problem between your system (CCS setup, software, etc), board, and
>>  > emulator.
>>  > 
>>  > -Jeff
>>  
>>  Nothing happened. I'm using XDS560 emulator and SDConfig utility only works
>>  with XDS510 emulator. I tried to use SDConfig but it didn't find XDS560 USB
>>  emulator.
>
>"Didn't find" means what?  What error message to do you get?  Did you load the
>correct driver?
>
>-Jeff
>
It means that SDConfig utility couldn't see emulator, couldn't get connection to emulator.
Error was something: couldn't find emulator.

According to Spectrum Digital's documents SDConfig utility doesn't support XDS560 emulator.

http://emulators.spectrumdigital.com/utilities/sdconfig/SDConfig.htm
http://emulators.spectrumdigital.com/files/XDS560R_QSG.pdf
>>  > >   >  >    I've got two diffenrent boards with 5509A and both of them
are not
>>  > >   >  >    working with emulator. I've also got Spectrum Digital's
TMS320VC5510
>>  > >   >  >    DSK board and that works.
>>  > >   >  > 
>>  > >   >  >    First error is:
>>  > >   >  >    Sequence ID: 0
>>  > >   >  >    Error Code: -1155
>>  > >   >  >    Error Class: 0x80001240
>>  > >   >  > 
>>  > >   >  >    After that always comes:
>>  > >   >  >    A bad parameter value was detected within
>>  > >   >  >    an internal data-structure of Unified-SCIF.
>>  > >   >  >    The controller or Unified-SCIF may be in an invalid state.
>>  > >   >  >    Sequence ID: 0
>>  > >   >  >    Error Code: -116
>>  > >   >  >    Error Class: 0x80003240

Aimo Parru-

> >>  Nothing happened. I'm using XDS560 emulator and SDConfig utility only works
> >>  with XDS510 emulator. I tried to use SDConfig but it didn't find XDS560 USB
> >>  emulator.
> >
> >"Didn't find" means what?  What error message to do you get?  Did you load
the
> >correct driver?
> >
> >-Jeff
> >
> It means that SDConfig utility couldn't see emulator, couldn't get connection
> to emulator. Error was something: couldn't find emulator.
> 
> According to Spectrum Digital's documents SDConfig utility doesn't support XDS560
emulator.
> 
> http://emulators.spectrumdigital.com/utilities/sdconfig/SDConfig.htm
> http://emulators.spectrumdigital.com/files/XDS560R_QSG.pdf

Hmmm, lack of debug and test coverage -- maybe a reason to not use XDS560 in some
cases.  What about XDSprobe.exe?  That's a more powerful emulator test utility, but
still independent of CCS software.

Some notes on XDSprobe are in this document, "Using xdsprobe with the XDS560 and
XDS510":

  http://focus.ti.com/lit/an/spra758a/spra758a.pdf

-Jeff
 
> >>  > >   >  >    I've got two diffenrent boards with 5509A and both of
them are not
> >>  > >   >  >    working with emulator. I've also got Spectrum
Digital's TMS320VC5510
> >>  > >   >  >    DSK board and that works.
> >>  > >   >  >
> >>  > >   >  >    First error is:
> >>  > >   >  >    Sequence ID: 0
> >>  > >   >  >    Error Code: -1155
> >>  > >   >  >    Error Class: 0x80001240
> >>  > >   >  >
> >>  > >   >  >    After that always comes:
> >>  > >   >  >    A bad parameter value was detected within
> >>  > >   >  >    an internal data-structure of Unified-SCIF.
> >>  > >   >  >    The controller or Unified-SCIF may be in an invalid
state.
> >>  > >   >  >    Sequence ID: 0
> >>  > >   >  >    Error Code: -116
> >>  > >   >  >    Error Class: 0x80003240

Aimo Parru-
>
>>  > >   Nothing happened. I'm using XDS560 emulator and SDConfig utility only
works
>>  > >   with XDS510 emulator. I tried to use SDConfig but it didn't find XDS560
USB
>>  > >   emulator.
>>  > 
>>  > "Didn't find" means what?  What error message to do you get?  Did you
load the
>>  > correct driver?
>>  > 
>>  > -Jeff
>>  > 
>>  It means that SDConfig utility couldn't see emulator, couldn't get connection
>>  to emulator. Error was something: couldn't find emulator.
>>  
>>  According to Spectrum Digital's documents SDConfig utility doesn't support XDS560
emulator.
>>  
>>  http://emulators.spectrumdigital.com/utilities/sdconfig/SDConfig.htm
>>  http://emulators.spectrumdigital.com/files/XDS560R_QSG.pdf
>
>Hmmm, lack of debug and test coverage -- maybe a reason to not use XDS560 in some
>cases.  What about XDSprobe.exe?  That's a more powerful emulator test utility, but
>still independent of CCS software.
>
>Some notes on XDSprobe are in this document, "Using xdsprobe with the XDS560 and
>XDS510":
>
>  http://focus.ti.com/lit/an/spra758a/spra758a.pdf
>
>-Jeff
> 
Something strange happened. Suddenly my other board started to work. Another one is still not
working. Is my emulator broken?

I ran XDSprobe utility. There were errors on JTAG IR scan-path length and integrity tests. This
is output:

ma 23.10.2006 13:25:01,31			 	 
--------------------------		
Performing integrity test on scan-path	

---[The scan-path lengths of TI DSP's and microcontrollers]-----

The JTAG IR register for a ARM7 or ARM9 device has 4 bits.
The JTAG IR register for a `classic' TI DSP device has 8 bits.
The JTAG IR register for a `IceMaker' TI DSP device has 38 bits.
The JTAG IR register for a 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.

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

The test for the JTAG IR instruction scan-path length succeeded.
The JTAG IR instruction scan-path length is 40 bits.

The test for the JTAG DR bypass scan-path length succeeded.
The JTAG DR bypass scan-path length is 1 bits.

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

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 either the
link-delay or scan-path has a configuration error.

---[Perform the scan-path integrity test on the JTAG IR]--------

This scan-path test uses blocks of 512 32-bit words.
Starting an Integrity Test using 0xFFFFFFFF.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x00000000.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0xFE03E0E2.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x01FC1F1D.
Word 0: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 1: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 2: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 3: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 4: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 5: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 6: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
Word 7: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 100.0 percent.
Finished that Integrity Test.
Starting an Integrity Test using 0x5533CCAA.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0xAACC3355.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
The JTAG IR integrity test has failed.

---[Perform the scan-path integrity test on the JTAG DR]--------

This scan-path test uses blocks of 512 32-bit words.
Starting an Integrity Test using 0xFFFFFFFF.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x00000000.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0xFE03E0E2.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x01FC1F1D.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x5533CCAA.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0xAACC3355.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
The JTAG DR integrity test has succeeded.
						
Integrity test successful!		
--------------------------		
Performing data test on scan-path	

---[The scan-path lengths of TI DSP's and microcontrollers]-----

The JTAG IR register for a ARM7 or ARM9 device has 4 bits.
The JTAG IR register for a `classic' TI DSP device has 8 bits.
The JTAG IR register for a `IceMaker' TI DSP device has 38 bits.
The JTAG IR register for a 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.

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

The test for the JTAG IR instruction scan-path length succeeded.
The JTAG IR instruction scan-path length is 40 bits.

The test for the JTAG DR bypass scan-path length succeeded.
The JTAG DR bypass scan-path length is 1 bits.

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

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 either the
link-delay or scan-path has a configuration error.

---[Perform the scan-path given data test on the JTAG IR]-------

This scan-path test uses blocks of 512 32-bit words
that repeat the data pattern 0x5533CCAA.
Starting the Given Data Test.
All of the 32-bit data values were scanned correctly.
Finished the Given Data Test.
The JTAG IR given data test has succeeded.

---[Perform the scan-path given data test on the JTAG DR]-------

This scan-path test uses blocks of 512 32-bit words
that repeat the data pattern 0x5533CCAA.
Starting the Given Data Test.
All of the 32-bit data values were scanned correctly.
Finished the Given Data Test.
The JTAG DR given data test has succeeded.
						
Data test successful!

Janne-

>>Some notes on XDSprobe are in this document, "Using xdsprobe with the
>> XDS560 and XDS510":
>>
>>  http://focus.ti.com/lit/an/spra758a/spra758a.pdf
>
> Something strange happened. Suddenly my other board started to work.
> Another one is still not working. Is my emulator broken?
>
> I ran XDSprobe utility. There were errors on JTAG IR scan-path length and
> integrity tests. This is output:

Looks pretty good to me, just the one error, plus I question the IR scan
length of 40 bits -- I think all 55xx devices should be 38 bits.

The 5509A boards are your own design, right?  Maybe you didn't handle
TCK_return signal correctly, didn't buffer and terminate TCK, missed some
pull-up Rs, your JTAG cable is a little too long or slightly flaky, etc. 
Possibly you have just enough TCK clock noise to miss a bit or double a
bit (clock glitch) every now and then.

Definitely you need to do a lot more debug -- run more experiments, try to
see what makes XDSprobe results worse or better.  My guess is you have a
basic design, board layout, or cabling issue that's going to take you some
work and time to get a grip on.  But in any case, I doubt your emulator is
broken, so that answers your original question.

-Jeff

> ma 23.10.2006 13:25:01,31
> --------------------------
> Performing integrity test on scan-path
>
> ---[The scan-path lengths of TI DSP's and microcontrollers]-----
>
> The JTAG IR register for a ARM7 or ARM9 device has 4 bits.
> The JTAG IR register for a `classic' TI DSP device has 8 bits.
> The JTAG IR register for a `IceMaker' TI DSP device has 38 bits.
> The JTAG IR register for a 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.
>
> ---[Perform the scan-path length test on the JTAG IR and DR]----
>
> The test for the JTAG IR instruction scan-path length succeeded.
> The JTAG IR instruction scan-path length is 40 bits.
>
> The test for the JTAG DR bypass scan-path length succeeded.
> The JTAG DR bypass scan-path length is 1 bits.
>
> The scan-path appears to consist of just one device.
>
> 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 either the
> link-delay or scan-path has a configuration error.
>
> ---[Perform the scan-path integrity test on the JTAG IR]--------
>
> This scan-path test uses blocks of 512 32-bit words.
> Starting an Integrity Test using 0xFFFFFFFF.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0x00000000.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0xFE03E0E2.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0x01FC1F1D.
> Word 0: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 1: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 2: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 3: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 4: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 5: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 6: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> Word 7: scanned out 0x01FC1F1D and scanned in 0x7407F07C.
> The details of the first eight errors have been provided.
> The utility will not report further errors found by this test.
> Some of the 32-bit data values were corrupted - 100.0 percent.
> Finished that Integrity Test.
> Starting an Integrity Test using 0x5533CCAA.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0xAACC3355.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> The JTAG IR integrity test has failed.
>
> ---[Perform the scan-path integrity test on the JTAG DR]--------
>
> This scan-path test uses blocks of 512 32-bit words.
> Starting an Integrity Test using 0xFFFFFFFF.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0x00000000.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0xFE03E0E2.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0x01FC1F1D.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0x5533CCAA.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> Starting an Integrity Test using 0xAACC3355.
> All of the 32-bit data values were scanned correctly.
> Finished that Integrity Test.
> The JTAG DR integrity test has succeeded.
>
> Integrity test successful!
> --------------------------
> Performing data test on scan-path
>
> ---[The scan-path lengths of TI DSP's and microcontrollers]-----
>
> The JTAG IR register for a ARM7 or ARM9 device has 4 bits.
> The JTAG IR register for a `classic' TI DSP device has 8 bits.
> The JTAG IR register for a `IceMaker' TI DSP device has 38 bits.
> The JTAG IR register for a 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.
>
> ---[Perform the scan-path length test on the JTAG IR and DR]----
>
> The test for the JTAG IR instruction scan-path length succeeded.
> The JTAG IR instruction scan-path length is 40 bits.
>
> The test for the JTAG DR bypass scan-path length succeeded.
> The JTAG DR bypass scan-path length is 1 bits.
>
> The scan-path appears to consist of just one device.
>
> 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 either the
> link-delay or scan-path has a configuration error.
>
> ---[Perform the scan-path given data test on the JTAG IR]-------
>
> This scan-path test uses blocks of 512 32-bit words
> that repeat the data pattern 0x5533CCAA.
> Starting the Given Data Test.
> All of the 32-bit data values were scanned correctly.
> Finished the Given Data Test.
> The JTAG IR given data test has succeeded.
>
> ---[Perform the scan-path given data test on the JTAG DR]-------
>
> This scan-path test uses blocks of 512 32-bit words
> that repeat the data pattern 0x5533CCAA.
> Starting the Given Data Test.
> All of the 32-bit data values were scanned correctly.
> Finished the Given Data Test.
> The JTAG DR given data test has succeeded.
>
> Data test successful!

Janne-
>
>> > Some notes on XDSprobe are in this document, "Using xdsprobe with the
>> >  XDS560 and XDS510":
>> > 
>> >   http://focus.ti.com/lit/an/spra758a/spra758a.pdf
>> 
>>  Something strange happened. Suddenly my other board started to work.
>>  Another one is still not working. Is my emulator broken?
>> 
>>  I ran XDSprobe utility. There were errors on JTAG IR scan-path length and
>>  integrity tests. This is output:
>
>Looks pretty good to me, just the one error, plus I question the IR scan
>length of 40 bits -- I think all 55xx devices should be 38 bits.
>
>The 5509A boards are your own design, right?  Maybe you didn't handle
>TCK_return signal correctly, didn't buffer and terminate TCK, missed some
>pull-up Rs, your JTAG cable is a little too long or slightly flaky, etc. 
>Possibly you have just enough TCK clock noise to miss a bit or double a
>bit (clock glitch) every now and then.
>
>Definitely you need to do a lot more debug -- run more experiments, try to
>see what makes XDSprobe results worse or better.  My guess is you have a
>basic design, board layout, or cabling issue that's going to take you some
>work and time to get a grip on.  But in any case, I doubt your emulator is
>broken, so that answers your original question.
>
>-Jeff
>

Yes, both of the boards are our own design. But why I thought that debugger was faulty is that
we have three independent processor-JTAG lines in two different boards. They all started to
give same errors without any warning. All lines are terminated just like the data sheets tell.
And EMU1 line was somewhere between 0 and 1 (it was connected trough pull-up), some discussion
said that it means faulty debugger.

But I finally got my both boards working. Another one board started to work after I changed
processor.

Thank you for your help!

Janne-

> Yes, both of the boards are our own design. But why I thought that debugger
> was faulty is that we have three independent processor-JTAG lines in two
> different boards. They all started to give same errors without any warning.
> All lines are terminated just like the data sheets tell. And EMU1 line was
> somewhere between 0 and 1 (it was connected trough pull-up), some
> discussion said that it means faulty debugger.

I understand.  But in my 22 yrs of DSP experience, I rarely find the debugger is the
problem.  The circuitry inside debugger is super simple and normally well-protected
against ESD and other bad things that engineers can inflict.  After all, the emulator
manufacturers must deal with 1000s of customers, so their products must be made
tough.  Your board is just dealing with you.

> But I finally got my both boards working. Another one board started to
> work after I changed processor.

Great, glad to hear that.  But one small worry:  my guess is the problem will come
back at some point.  It may be intermittent and related to things that are still
undiscovered :-)

-Jeff