XDS100v2 and OMAP L138 doesn't work reliably

Hi,

I've got an OMAP L138 and try to debug it with the XDS100v2 and CCS v4.2.3.00004. Somehow the debugging is not very stable, sometimes it works and sometimes it does not. I always can connect with CCS to the debugger showing me the DSP/ARM cores disconnected, yet I can not connect to the cores.

1) I get Signals on TCK, TDI, TDO and RTCK on the oscilloscope - TCK is buffered, RTCK is directly routed from the OMAP pin to JTAG header

2) When using dbgjtag.exe, as well as in CCS I get different errors (with the same setup)

2.1)

 C:\Programme\Texas Instruments\ccsv4\common\uscif>dbgjtag.exe -f "C:\Programm
exas Instruments\ccBoard0.dat" -rv

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Feb 28 2011'.
The library build time was '22:16:13'.
The library package version is '5.0.333.0'.
The library component version is '35.34.29.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will now attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

2.2)

C:\Programme\Texas Instruments\ccsv4\common\uscif>dbgjtag.exe -f "C:\Programm
exas Instruments\ccBoard0.dat" -rv

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Feb 28 2011'.
The library build time was '22:16:13'.
The library package version is '5.0.333.0'.
The library component version is '35.34.29.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-154' (0xffffff66).
The title is 'SC_ERR_POD_TBC_WRITE'.

The explanation is:
This utility failed to use the adapter for a custom
emulator to perform a write to a controller register.
The adapter returned an error.

3) I tried to flash the new firmware on the XDS100v2(the JTAG Header is not connected for flashing)

Sometimes this flashing works sometimes i get the following error:

C:\Programme\Texas Instruments\ccsv4\common\uscif\ftdi\xds100v2_cpldprog>xds100v
2_cpldprog.exe -v1 xds100v2_cpld.xsvf
XSVF Player v5.01, Xilinx, Inc.
Found 2 USB 2.x devices
Opened Texas Instruments Inc.XDS100 Ver 2.0 B, at Location 1378
XSVF file = -v1
XSVF file = xds100v2_cpld.xsvf
ERR: FAILED GPIO PIN PLAY
ERR: FAILED GPIO PIN PLAY
ERROR:  TDO mismatch
ERROR at or near XSVF command #462.  See line #462 in the XSVF ASCII file.
Execution Time = 22.229 seconds

Can someone help me with this? It seems like a problem with the XDS100v2 and not the Board with the OMAP. Sadly I do not have any evaluation boards or second OMAP boards so I can't tell for sure if the problem is the board or the emulator, yet regarding the errors that occur I would really think it's a emulator problem.

Stefan