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.

DebugServer.DLL runtime dependencies



Hello,

I'm trying to get hardware debugging running. I'm using CCS v4.2.4.00033 on Win 7 64. I have a Spectrum Digital XDS510 USB emulator connecting to third party C6000 hardware. 

The current roadblock is this: when I launch the TI debugger I get the error "Exception occurred during launch. Reason: An internal errror occurred during 'Creating Debug Server'". The error details list CreateInstanceByID failing with error code 80040154. Based on other posts, I've tracked this down to missing runtime dependencies for DebugServer.DLL. Using depends.exe to diagnose, I added the following directories to my system path:

C:\Program File (x86)\Texas Instruments\ccsv4\common\bin
...\ccsv4\common\uscif
...\ccsv4\DebugServer\win32
...\ccsv4\DebugServer\bin\win32

This helps but DebugServer.DLL depends on JTAGDATA.DLL which in turn depends on VC80.CRT version 8.0.50727.5592. My system winsxs directory has VC80 CRT versions up to .4940. I installed the VC2005 redist, the SP1 redist, and a subsequent ATL security update but no luck, I just can't find 8.0.50727.5592. Note: to see this dependency I extracted the manifest from JTAGDATA.DLL using mt.exe (you can also load JTAGDATA.DLL in VS and look at the manifest there). 

Has anyone else run into this? Does anyone know where to get the .5592 runtime or how best to patch around it?

Thanks,

Bill

  • It turns out that you need the vcredist.exe installer shipped with VC++ 2005 Pro. I was able to get this from a colleague and install it, and this installed 8.0.50727.6195. The TI debugger now launches without the above error.

    Cheers,

    Bill

  • Bill,

    Good to hear you got it going.  We do ship the visual C redistributable package with CCS but I believe we did update it recently in v5.1 to include a slightly different package as the one we had was sometimes not getting installed.

    I noticed you have CCS installed in Program Files (x86).  This can cause some problems depending on what your UAC settings are.  I used to be able to run fine in this directory but they our IT policies changed and then I had to reinstall outside of Program Files.  The issue is that Windows can lock down this folder so that writes cannot occur at runtime.  For the most part this is ok but there are a couple things like updating that write to the folder.  Just something to be aware of.  In the newer installs we put up a warning about installing there.

    Regards,

    John

  • Hi John,

    Note I'm using CCS v4 due to third party requirements. I can see in the install log that CCS v4 installed several VC runtimes but these are older than needed by JTAGDATA.DLL. I think this will only affect CCS v4 users who don't happen to have VC++ 2005 Pro installed, and one need only track down the proper runtime.

    Thanks for the heads up regarding install dir. I'm pretty sure I followed the installer defaults and I haven't noticed any problems - perhaps this is a CCS v5 issue?

    Cheers,

    Bill