TI E2E Community
Code Composer Studio
Code Composer Forum
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:
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.
Have you put them here? Do you still get the same error? Have you done a reboot afterwards?
Please keep us informed.
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.
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:
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.
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.
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.
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.
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.
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.
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.
I uninstalled v5.1 and v5.2. Also uninstalled all versions of XDC, IPC, SYS/BIOS, deleted the TI directory. Tried to go back to a clean slate. Re-installed v5.2, without SYS/BIOS. Then installed the latest SYS/BIOS, XDC, and IPC.
Performed the with both dll's in the three directories, system32, DebugServer, and DebugServer/drivers.
Created a new SYS/BIOS project, the eval kit is connected, built the project and went into debug. No errors at all!!!. The code executed and all debugging worked perfectly.
Success, for now. Just wanted you to know, If someone has some ghosts of CCS past or a previous install, it can cause problems.
thanks for the feedback and patience here. That is good to know a previous install may interfere.
All the best with development.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.