FTCJTAG.dll error/issue .... FAQ/Work Around

On a Windows 7 box, CCS v5.2, I tired the suggested workaround. No help. I put the fies in three palces:

 C:\CCS5.2\ccsv5\ccs_base\DebugServer

C:\ccsv5\ccs_base\DebugServer

 C:\Windows\System32 

Any ideas, need to get this working.

This is in response to this post

There is a know issue with the copying of some FTDI drivers which affects Stellaris products on Win 7 64 bit in particular.

If you are seeing the following error:

Error initializing emulator: Error loading FTCJTAG.dll. Please make sure that the file exists (C:\CCS5.2\ccsv5\ccs_base\DebugServer\drivers\FTCJTAG.dll)

Fix: FTCJTAG.dll and ftd2xx.dll and need to be copied to: C:\CCS5.2\ccsv5\ccs_base\DebugServer

Note: Both files (FTCJTAG.dll and ftd2xx.dll) are required to fix this issue!

It may be required to copy both .dll-Files to the C:\Windows\System32 folder if they don’t exist there yet!

This should fix your error.

  • Hi Ed,

    Have you put them here?  Do you still get the same error?  Have you done a reboot afterwards?

    C:\ccsv5\ccs_base\DebugServer\drivers

    Please keep us informed.

    Best Regards,

    Lisa

  • In reply to Lisa TI:

    Lisa,

    My CCS install is in c:\ti\CCS5.2\ccsv5\ccs_base\DebugServer\drivers

    I have put both files in that directory as well.  Same results.

  • In reply to Ed Wahler:

    Hi Ed,

    what target are you using? Did you try a reboot?   Have you tried downloading the standard ftdi drivers from the web?

    Eg we post a version of Stellaris ones here:

    http://www.ti.com/tool/lm_ftdi_driver

    Best Regards,
    Lisa

  • In reply to Lisa TI:

    Hello Lisa,

    I am using a Stellaris EKS-LM4F232 Evaluation Kit. I have rebooted repeatedly. The specific error I am getting in CCS is :

    CORTEX_M4_0: Error initializing emulator: Error loading FTCJTAG.dll. Please make sure that the file exists (C:\ti\ccsv5\ccs_base\DebugServer\drivers\FTCJTAG.dll)

    Which of course it does exist. I did the FTclean. I did an update to the drivers you hyper-linked above. Windows reports the drivers are correct and the Stellaris In-Circuit Debug Interface is working correctly.

    I am sure this is something subtle if the working around is working for the rest of the CCS community. I can run CCSv5.0 on my laptop (Windows 7 also). I have been hesitant to update it to ccsv5.2 if that means I can't run CCS on either machine.  It comes up and gives me the ftd2xx.dll error, but clinking OK lets it go off and proceed.

    Do you want to link up on Skype and I can share the desktop so you can see what I see and we can probe the depths of windows together? I use this computer for all my engineering work. I mostly use another computer with a Linux distribution for almost everything else. So the machine is not overly cluttered. 

    I just confirmed that I can run the qs-logger application and get data off the eval kit through the USB port. I also can use LM Flash Programmer to program the flash on the eval kit through the Stellaris In Circuit Debug Interface which would seem to indicate that the USB drivers are working OK. 

    That is all I can think to providefor now.

    Ed

  • In reply to Ed Wahler:

    Hi Ed,

    a couple things.  Are the mentioned drivers also in your system32 directory?  Just to double check.  Have you tried a fresh workspace and project?

    If you are still stuck after that, then perhaps I can see about arranging a webex.


    Best Regards,
    Lisa

  • In reply to Lisa TI:

    Hi again Lisa,

    Yes the drivers are in system32 dir. I have tried projects that work perfectly on my laptop from the class I took with Scott Bland. I did a complete reinstall of CCS. The only I haven't done it install ccsv5.0 like I have on my laptop to see if that makes a difference. But I was hoping to use the latest (v5.2) and move on.

    Ed

  • In reply to Ed Wahler:

    Hello Lisa,

    I installed CCS v 5.1 and it gives me the ftd2xx.dll error, I click OK and on we go. So CCS 5.1 works and 5.2 doesn't. There seems to be a definite problem in 5.2. Just thought you should know.

    Ed

  • In reply to Ed Wahler:

    Hi Ed,

    this is a known issue, but I am surprised the work around did not do the trick for you.  Let me see if I can get some development colleagues to help dig into this for you.

    Best Regards,

    Lisa

  • In reply to Lisa TI:

    Hello Lisa:

    I am thinking about doing a complete uninstall of all verion and components of CCS, SYS/BIOS, XDC, etc. And do a clean install of ccs v 5.2. What are your thoughts.

    Ed

  • In reply to Ed Wahler:

    Hi Ed,

    it may be worth a try, but you would still need to implement the work around.   If you do try this please keep us informed.

    Best Regards,
    Lisa