• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 1771 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSv3.3 startup error

TIDR
Genius 9345 points

My customer has been using CCSv3.3 with SR12 for a while now. However, today she is having a problem with bringing up CCS. The runtime error shown does not clear even by restarting the machine so she appears to be stuck.

Uninstalling and reinstalling the whole package will probably fix the problem but I suspect that will take time. Is there any clue from the error message?

I figured I'd check with the team before suggesting a reinstall.

 

Rgds

-Dipa-

 

  • 0
    TI__Guru**** 463481 points

    Hi Dipa,

    That's a fairly generic error. Could you provide more details? What target setup is being used? Does the error happen when using other target setups?

    Thanks

    ki

  • 0 in reply to Ki
    TI__Genius 9345 points

    Sorry, Ki I should've been clearer.

     

    They are using emulator (BHUSB560) to talk to a C6748 target. At the time they get the error they are not that far along though. I've asked them to instead change the config to simulator to see if anything changes.

    FYI, they don't get a log dump file when the problem happens.

     

    Rgds

    -Dipa-

  • 0 in reply to TIDR
    TI__Genius 16490 points

    Dipa,

    One possible source of this problem can occur when plugins from multiple versions of CCS get intermixed (i.e. the component manager gets confused). If a .dmp file is generated when the problem happens, I could tell from the file whether this is the case here.

    Andy

  • 0 in reply to AndyW
    TI__Genius 9345 points

    Andy,

    No .dmp is generated.

    Shoudl I ask her to save the cccomp_db.ini file to a .bak and reopen CCS. Do you think that will help?

     

    Rgds

    -Dipa-

  • 0 in reply to TIDR
    TI__Genius 16490 points

    Renaming the ccs_Compdb.ini file probably won't help. Could you ask her to send us the ccs_Compdb.ini file so we can have a look?

    Also, could you ask her to start the compoment manager standalone (comp_mgr.exe), expand the Texas Instruments node, and check that all the selected plugins are from the appropriate release?

    Andy

  • 0 in reply to AndyW
    TI__Genius 9345 points

    Hi Andy,

    Here are the files. Hope you can help find something in these.

     

    Rgds

    -Dipa-

  • 0 in reply to TIDR
    TI__Genius 16490 points

    The is no problem indicated in the file. Were they able to start component manager from the command line without problems?

  • 0 in reply to AndyW
    TI__Genius 9345 points

    Yes, it came up without any issues. Any other ideas?

  • 0 in reply to TIDR
    TI__Genius 16490 points

    We're scraping the bottom of the barrel now. :)

    Here are a few other things to look at. If these don’t work, I’m out of ideas other than reinstalling.

     

    (1)     Start the other version of CCS they have installed (looks like 3.1). Exit, and then try to start CCS 3.3. This will force all the 3.3 plugins to be re-registered. If there is a plugin registration problem, this may clean it up.

     

    (2)     Temporarily rename ctools.dll to something else and try to start CCS 3.3. If that doesn’t help, rename it back.

     

    (3)     We had a couple of other reports of virus scanner software interacting with CCS. Most virus scanners will cause a DLL to be loaded into the same process space as CCS and this DLL somehow causes CCS to crash. How to prevent this virus scan DLL from being loaded is product dependent, but usually just disabling the virus scanner is not enough. It would be worth finding out what virus scan software they are using to see if it corresponds to any of the ones we’ve had problems with in the past, and also asking them to disable it to see if there is any effect.

  • 0 in reply to AndyW
    TI__Genius 16490 points

    To conclude this story:  the customer uninstalled and reinstalled CCS, but the problem persisted. After working with the customer a bit more, we eventually found there was a dodgy spyware-like application called “RelevantKnowledge” installed on the PC. This application loads DLLs into the CCS process space and it was an interaction with between CCS and these DLLs that was causing the crash. The DLLs were noticed when a debugger was attached to the cc_app.exe process after it had crashed.

    We ran the uninstall for RelevantKnowledge and rebooted. After the reboot, CCS was operational again. The customer had no awareness of when this application would have been installed.

    Another odd thing about this problem was that the customer also had CCS 3.1 installed and did not experience any problem with the older CCS version.