Issue with XDS100V2?

Justin,

Justin McQuown78781 said:

I downloaded the latest version of CCS v4, Version: 4.2.3.00004,

Did you install only CCS 4.2.3 or any other updates or installers on top of it?

Justin McQuown78781 said:

I then tried uninstalling and reinstalling CCS v4 in the c:\Texas Instruments directory, but it hasn't seemed to help.

For Windows7, it is recommended to install CCS outside of the c:\Program Files(x86) directory as there could be problems if UAC is enabled. Please see this FAQ:
http://processors.wiki.ti.com/index.php/FAQ_-_CCSv4#Q:_Is_Windows_7_supported.3F

If installing it in a different location also causes the same behavior, could you please try the following:

1) Try the suggestions in the "General IDE" and "Debugger" sections of this troubleshooting page. If that does not help,
2) Try renaming the file ctools.dll found in <ccs_install_dir>\ccsv4\emulation\analysis\bin to some other name. If that does not help,
3) Generate diagnostic logs and attach them here to help us investigate this further. Please see this page for details on generating and accessing the logs: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

Hi,

AartiG said:

Did you install only CCS 4.2.3 or any other updates or installers on top of it?

AartiG said:

For Windows7, it is recommended to install CCS outside of the c:\Program Files(x86) directory as there could be problems if UAC is enabled.

UAC is disabled and I installed CCSv4 in the director c:\Texas Instruments\ccsv4

AartiG said:

1) Try the suggestions in the "General IDE" and "Debugger" sections of this troubleshooting page. If that does not help,

This did not help.

AartiG said:

2) Try renaming the file ctools.dll found in <ccs_install_dir>\ccsv4\emulation\analysis\bin to some other name. If that does not help,

This seemed to fix the speed and connectivity issue, though now I get a number of entries in the error log within ccs everytime I debug the project.  Is this expected?  I've attached the error log.7077.Error Log 7-20-2011.zip

One more thing, after opening code composer and selecting debug active project, I get the following error message.  'The program can't start because ctools.dll is missing from your computer.  Try reinstalling the program to fix this problem.'  I've attached a screen shot.3603.ctools missing from computer.tif

Thanks,

Jusitn

Justin McQuown78781 said:

This seemed to fix the speed and connectivity issue, though now I get a number of entries in the error log within ccs everytime I debug the project.  Is this expected? 

Yes the messages in the error log are expected when ctools.dll is disabled, and can be ignored for now. Also some advanced emulation features will not be available when it is disabled, so it is not an ideal solution, but it should allow you to get going.

Justin McQuown78781 said:

One more thing, after opening code composer and selecting debug active project, I get the following error message.  'The program can't start because ctools.dll is missing from your computer.  Try reinstalling the program to fix this problem.'

We'd still like to figure out CCS was hanging up during launch in the first place. So when you have a chance, if you could go back, rename the ctools file to its original name, and generate and provide the diagnostic logs, that would be very helpful.

Justin,

I wanted to follow up and see if you were still seeing the error message " 'The program can't start because ctools.dll is missing from your computer.  Try reinstalling the program to fix this problem", after renaming ctools.dll. If so, does adding the -clean option as mentioned in my previous post help?

We would really like to get to the bottom of these errors so if you could go back to using the original ctools.dll file and generate the diagnostic logs as described in my previous post and attach them here, that will be much appreciated.

Thanks for your patience.

AartiG,

I know longer get the error on startup when using the -clean option.  I still however have the extended launch times when using the original ctools.dll.  I've attached the log files.  Let me know if you need more information.8802.Delayed Launching Logs.zip

Justin,

Thanks for sending the logs. We'll take a look to see if they give any clues as to the cause of the issue.

Could you confirm a couple more things for us:

1) You mention having extended launch times when using the original ctools.dll. Does it actually finally launch and connect to target successfully? If so, in about how long?

2) Can you try the debugger launch in manual steps and let us know exactly where it hangs up? To do this, just follow the steps below and reply back to let us know in which step in hangs up:
  - right click on your .ccxml file and select Debug As->Debug Session
  - atfer you switch to Debug perspective, go to menu Target->Connect Target
  - Go to menu Target->Load Program, browse to your project folder and load the .out file from the \Debug folder

I suspect it locks up in the "Connect Target" step, but please confirm if this is the case.

AartiG,

Yes it does eventually launch but it can take 10-15 minutes and you are correct, "Connect Target" step is where it locks up.

Justin

Justin,

There is one more log that will be helpful to our developers in looking into this issue. If you don't mind, could you please follow the steps described in this page to generate a cTools/Trace log? http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#cTools.2FTrace_Logging

Make sure to keep the original ctools.dll when doing this so the issue with the very long launch time can be reproduced.

Also could you let us know if you had any script running when attempting the target connection.

M     08:54:22:637 | JTRACE: GetChannelServer(): Creating ChannelServer.
M     08:54:22:668 | JTRACE: GetChannelServer(): ChannelServer unavailable. Operating in stand-alone mode.
M     08:54:22:668 | JTRACE: GetConnectedCPUNames: channelServer = 00000000
M     09:04:05:396 | JTRACE: GetConnectedCPUNames: Entering
M     09:04:05:396 | JTRACE: GetChannelServer(): Creating ChannelServer.
M     09:04:47:501 | JTRACE: GetChannelServer(): ChannelServer unavailable. Operating in stand-alone mode.
M     09:04:47:501 | JTRACE: GetConnectedCPUNames: channelServer = 00000000
M     09:04:48:484 | JTRACE: CTraceEventHandler::Lock(): Thread 4156 attempting to lock...
M     09:04:48:484 | JTRACE: CTraceEventHandler::Lock(): Lock obtained by thread 4156.
M     09:04:48:484 | JTRACE: CTraceEventHandler::Unlock(): Thread 4156 is trying to remove lock owned by thread 4156 ... 
M     09:04:48:484 | JTRACE: CTraceEventHandler::Unlock(): Thread 4156 successfully removed lock.

Aartig,

Here is the log file you asked for.  I was not running a script when trying to connect to the target.

Procedure to recreate the problem

1) Open CCS

2) Choose workspace

3) Select Target -> Debug Active Project

Hi TI,

Any update on this issue?  We have been seeing the exact same thing which has halted our development with CCS4 & XDS100.

Thanks,

TipTop