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.
Part Number: CCSTUDIO
Tool/software: Code Composer Studio
I have a fresh installation of CCSv7 on my MacBookPro running MacOS El Capitan. The Resource Explorer window reports that the server fails to start.
There were no other installations made, so the install is clean. The workspace is new and empty.
The advice I can find on these forums and from web searches includes the following:
As far as I can tell, the CCS platform is unusable without Resource Explorer. So, there is no easy work-around that would ignore the issue.
Is there a log file some place explaining what CCS is doing and why it is failing? What other advice is given for bringing CCS up on MacOS?
Here is the tirex log file.
In reply to Marc Singer98:
If my reply answers your question please click the "This resolved my issue" button
In reply to JohnS:
Please check if there's an old node process hanging around and kill it. Then restart CCS.
In reply to OliverP:
Were you able to try Oliver's suggestion.
He is referring to this process:
There is no node process running when CCS quits. When I start Resource Explorer, two node processes start. After I receive the failure message, there is only one node process active. Closing CCS terminates the remaining node process.
As explained in the original post, I tried rebooting the machine. Running CCS after a fresh boot makes no difference.
When Resource Explorer starts up it tries to discover existing installed packages in the ti folder. It could be that there's a package in your folder that causes some problems. We can check this by temporarily pointing Resource Explorer to another folder. Please create a new empty folder (e.g. ~/ti_test) and then change the "contentPath" setting in the app_localserver.json file to this new folder. The file is located in the CCS installation folder: ccsv7/tirex/ti-rex-core/config/app_localserver.json
As this was a fresh install, I would have been very surprised to see this make a difference. It did not.
I created a new directory ~/ti/tirex_content and pointed tirex's configuration to that directory. On startup, REX created a 'zips/' directory, but nothing is ever downloaded to it.
Are there any log files we can activate to see what TIREX is doing? It seems like getting some information about the state of the program would help narrow down our search for a solution. I posted a log file to this bug. Does it help? Are there any verbosity flags we can enable?
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.