CCS V4.2.4 - Issue Connecting a Spectrum Digital C2000 XDS510LC Emulator to a TMS320F28035 in Debug Mode

Jonathan Fortunati

Other Parts Discussed in Thread: TMS320F28035

Hi,

I'm having trouble getting into debug mode using the XDS510LC emulator to the TMS320F28035 on a windows 7 machine. The error I am receive is:

Error connecting to the target:
Error 0x80000200/-1041
Fatal Error during: OCS, 
Device driver: Problem with the Emulation Controller.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.

I've have found other posts detailing similar problems, but have found none with a complete resolution.

I have tried following the steps which the error message presents, to only receive the same error again. I'm assuming the drivers are installed correctly,

the device shows up in my devices manager. I also went through the steps to generate the .ccxml target configuration file, and have set it up for my emulator and

my processor. I verified that its not the processor or the emulator by going through the same set up procedure in CCSv4.2.4 on a co workers machine, and CCS connected

in debug mode just fine. So basically I'm at a loss as to why I cant connect to the processor via the debugger, so any help, or a link to a previously answered post

that I may have missed would be appreciated.

Thanks!

-Jon

over 13 years ago

AartiG over 13 years ago

TI__Guru**** 173310 points

Jon,

I would first suggest checking the low level JTAG connection using the SDConfig tool from Spectrum Digital. If this reports errors, then the problem is at a lower JTAG level than the CCS IDE. This troubleshooting page has some additional details on troubleshooting such issues.

If the JTAG connection checks out ok, then try deleting the debug launch and target cache files, and cleaning out the workspace as described in the page below before trying the connection again.
http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Debugger

Jonathan Fortunati over 13 years ago in reply to AartiG

Prodigy 70 points

The emulator test checks back alright, according to the tutorial.

I tried clearing out the .metadata folder to clean the work space. Now CCS crashes after I hit the debug button. Here's the error that I receive:

This happens during the connect phase, if I'm going about this manually.

AartiG over 13 years ago in reply to Jonathan Fortunati

TI__Guru**** 173310 points

Jonathan Fortunati said:

This happens during the connect phase, if I'm going about this manually.

This could be related to some known emulation issues in CCS 4.2.x. Could you try renaming the file ctools.dll to something else (the file will be in \ccsv4\emulation\analysis\bin within your installation folder)? Then close and restart CCS and see if that helps establish connection.

If feasible for you, it might be worth giving CCS 5.1 a shot as well, as there are several bug fixes and updates in this release (some emulation crash/hang issues were addressed as well).It can be download from http://processors.wiki.ti.com/index.php/Download_CCS

Jonathan Fortunati over 13 years ago in reply to AartiG

Prodigy 70 points

I went in and changed the ctools.dll file to some gibberish .dll, and when I restarted code composer there was an error log present that I haven't noticed before, full of errors. I tried to debug, and CCS crashed with the same error. Unfortunately I cant up grade to version 5.1 yet, the computer I'm using is being used on another project which requires version 4.2. I found this thread:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/33330.aspx

and tried some of the suggestions in there (bypassing the CLA, connecting to exact CPU, and not installing to program files) with no success.

AartiG over 13 years ago in reply to Jonathan Fortunati

TI__Guru**** 173310 points

Jonathan Fortunati said:
I went in and changed the ctools.dll file to some gibberish .dll, and when I restarted code composer there was an error log present that I haven't noticed before, full of errors. I tried to debug, and CCS crashed with the same error.

The error log is expected when ctools.dll is renamed and can be ignored, however it is unfortunate that it did not help with the connection issue. Can you confirm that even with ctools.dll renamed, that the crash happens during connect? To check this, instead of hitting the green bug button for debug active project, launch the debug session by right-clicking on the target configuration file (.ccxml), launch target configuration, and then connect to target when in the debug perspective.

Jonathan Fortunati said:
Unfortunately I cant up grade to version 5.1 yet, the computer I'm using is being used on another project which requires version 4.2.

It is ok to have a CCS4 and CCS5 version on the same machine. You can install CCS5 in a different folder than CCSv4 and if you wish, after performing some tests could even uninstall it at later time, if necessary. It would definitely be interesting to see if the connection works well with CCS 5.1.

Are you able to test the same emulator/board on a different PC, or another board or emulator on this same PC, to see if the issue may be tied to the CCS installation on this particular machine? I suspect so since you said the low level JTAG tests check out fine, but would be an interesting data point.

Let us know if you're able to move ahead with the CCSv5 installation and test it out.

If not, please rename ctools.dll back to its original name and capture and send us error logs, crash dump files and debug server logs as described here:
http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

Jonathan Fortunati over 13 years ago in reply to AartiG

Prodigy 70 points

Alrighty, I tried connecting the manual way, and its still crashing on the connect phase of the process.

I'll have to try out installing CCS5 next week, when I have some time. But in terms of trying it out on different machines, I've gotten the board to work on a windows XP machine with CCS v 3.3 and a windows 7 machine with CCS v 4.2, both with the same debugger / cable. Also, heres the diagnostic information from CCS which hopefully contains something useful on the crash:

Jonathan Fortunati over 13 years ago in reply to Jonathan Fortunati

Prodigy 70 points

On a side note, I haven't solved the crashing problem, but I have found a solution to my overall problem which is getting a way to talk to my processor via a debug session: Use another old XP machine I found lying around, that no one else was using (the machines I mentioned in my last post belonged to co workers). It had CCS v3.3 on it, and with a few updates, was able to talk to my board.

Code Composer Studio™︎

Code Composer Studio forum

CCS V4.2.4 - Issue Connecting a Spectrum Digital C2000 XDS510LC Emulator to a TMS320F28035 in Debug Mode