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.
Huh? I didn't install! I have a working system, and I'm in the middle of a project development! Are you telling me I have to do a full reinstall of CCSv5, Stellarisware, etc.. And hope I get a working environment, because the updater screwed up the path? Can we just fix the path / config?
Just so we are clear... CCSv5 is in the DEFAULT directory, which is 'C:\Texas Instruments\' - I didn't 'pick' a directory name with spaces.. Been doing this too long to make that mistake. That said, I also use the default install directory on tools to keep things simple. I'm pointing out that the updater breaks a DEFAULT directory install of CCS! We need to fix this, right? Not just wave hands and say everyone's default install of CCS will be broken - go download a couple Gigabytes per user and reinstall all the dev tools, because a config file somewhere is incorrect.. right? What can we do here? Help?
Hi Todd,
the default directory for CCSv5 should be c:\ti actually and unfortunately yes, I would say reinstall into that or similar directory with no spaces or accented/special characters.
Please keep us informed.
Best Regards,
Lisa
Todd
Browse to "c:\Texas Instruments\ccsv5\eclipse\downloads" in windows explorer. Edit file "ccs_update_5.2.0.00069.bat" in notepad. Change the last line to:
start "CCS" /b "C:\Texas Instruments\ccsv5\eclipse\downloads\ccs_update_5.2.0.00069.exe" %params%
Restart CCS from the desktop shortcut or from "c:\texas instruments\ccsv5\eclipse\ccstudio.exe". The update should now proceed.
The default directory was 'C\Texas Instruments\' and I didn't pick it. Seriously. I don't pick install directories for tools with spaces or special characters. The whole system was working well and updating since November, and I ran a CCS update last night, which caused this problem, which trying to address the breakpoint issue I referenced. (any ideas there, btw?)
Doesn't TI actually support CCS? This is probably a simple config file fix for someone who knows it well. Please address this, instead of waving me off with a reinstall.