Trouble connecting XDS100v2 to Custom OMAP-L138 board

...oh, and one additional point. My XDS100v2 connects properly to another of my custom boards and can communicate with both the ARM and DSP. So the emulator appears to be working properly (in fact I have 2 of them), but my second board doesn't. How can I debug this?

You've probably seen these pages already but I thought I'd point them out anyway as reference:
http://processors.wiki.ti.com/index.php/How_to_connect_to_the_OMAP-L138/C6748/AM1808_EVM_board_using_CCS%3F#XDS100v2.2C_XDS510_or_XDS560_external_emulator_-_DSP_.2B_ARM_.28OMAP-L138_SOM.29

You may also want to try the adaptive clocking setting in the XDS100v2 emulator connection properties:
http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_turn_on_adaptive_clocking.3F

To debug the issue at the JTAG level, please check this page: http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems
It describes how to use dbgjtag to do some basic JTAG integrity tests.

As a last step, please try deleting target cache files and debug launches as described here: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Debugger

Aarti,

Aarti said:

You've probably seen these pages already

You are correct. I have done a substantial amount of homework before posting my question.

Aarti said:

You may also want to try the adaptive clocking setting in the XDS100v2 emulator connection properties:

In case you missed my post above, I up until recently my XDS100v2 has been working well with two custom boards. I have been able to successfully connect to both the ARM and DSP. I am currently using adaptive clocking per the Wiki page's suggestion.

Aarti said:

To debug the issue at the JTAG level, please check this page: http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems
It describes how to use dbgjtag to do some basic JTAG integrity tests.

In case missed it in my post above, I am using the XDS100v2. All of the JTAG debug Wikis give information ONLY for the 5xx series of emulators. I cannot find a JTAG debug utility for the XDS100v2. I purchased two of the XDS100v2's from TI, both of which have been working well until recently. These units (purchased from TI) were manufactured by Spectrum Digital. I have attempted to find a JTAG debu utility from SD, but all I can find is SDConfiEX.exe, which, again, only supports the 5xx series of emulators.

Aarti said:

As a last step, please try deleting target cache files and debug launches as described here:

I have tried all of the suggestions here, to no avail.

**Could I get an answer to my original question?  **Can someone point me to the list of error codes and their interpretations??** Surely someone wrote these error codes for a reason.....to debug the device. Surely someone has a listing of what they mean.

Thx,

MikeH

MikeH said:

I cannot find a JTAG debug utility for the XDS100v2.

The dbgjtag utility works with the xds100v2, so you could try running some of the low level JTAG tests as mentioned in that wiki page.

Aarti,

Aarti said:

The dbgjtag utility works with the xds100v2,

Hmmmm...OK, then could you explain the statement below from your wiki page?

We will use Dbgjtag to do this test. IMPORTANT! Spectrum Digital users must use the utility called "SDconfig", which can perform very similar functions. Please refer to the section Using SDConfig to test JTAG connections below

Thx,

MikeH

I agree that statement is not very clear. Dbgjtag can be used with all xds100 emulators. All other Spectrum Digital emulators should use the SD utilities. I updated the wiki page to add a note on that. We will also look at making that wiki page a bit more clear overall.

Aarti,

Aarti said:

We will also look at making that wiki page a bit more clear overall.

I have also *still* not found a complete list of error codes. There are some error codes in xdserror.cfg in ccsv4\common\uscif, but it does not include my specific error (2131). I am dead in the water until I figure out what is wrong with the JTAG connection. Extremely frustrating.

MikeH