• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1303 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

does compiler need internet connection ??

eric bouxirot
Intellectual 375 points
Other Parts Discussed in Thread: CCSTUDIO

hi, 

i just see that MSP430 compiler and/or CCS try to connect to external internet IP during compilation....

what's this ???

because i'm behind a hardest rules proxy, connection fail and build take VERRRYYY long time !!! 

each Warning or Error try to connect to this external IP and each try take about 2 or 3 seconds...

IP is : 23.223.210.223 and it's the ccstudio.exe process who try the connection.on random ports >64000 (incremented each try)

Can someone help me to remove this ??

  • Intellectual 375 points
    this is what i think try this connection..... (how can i disable this ???)

    !ENTRY com.ti.ccstudio.errorparser 4 0 2016-11-02 18:19:07.412
    !MESSAGE An internal error was logged by 'com.ti.ccstudio.errorparser'.
    !STACK 0
    java.net.SocketTimeoutException: connect timed out
    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:579)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
    at sun.net.www.http.HttpClient.New(HttpClient.java:308)
    at sun.net.www.http.HttpClient.New(HttpClient.java:326)
    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:997)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:933)
    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:851)
    at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:563)
    at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:540)
    at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:227)
    at org.jsoup.helper.HttpConnection.get(HttpConnection.java:216)
    at com.ti.ccstudio.errorparser.parsers.PatternProvider$PatternData.fillup(PatternProvider.java:217)
    at com.ti.ccstudio.errorparser.parsers.PatternProvider$PatternData.findMatch(PatternProvider.java:133)
    at com.ti.ccstudio.errorparser.parsers.PatternProvider.getEmdUrl(PatternProvider.java:413)
    at com.ti.ccstudio.errorparser.parsers.ErrorPattern.recordError(ErrorPattern.java:95)
    at com.ti.ccstudio.errorparser.parsers.CoffErrorParser.processPendingMesg(CoffErrorParser.java:334)
    at com.ti.ccstudio.errorparser.parsers.CoffErrorParser.processLine(CoffErrorParser.java:258)
    at org.eclipse.cdt.core.errorparsers.ErrorParserNamedWrapper.processLine(ErrorParserNamedWrapper.java:48)
    at com.ti.ccstudio.project.core.internal.build.ProjectAdviceManager$AdviceContentHandler.endElement(ProjectAdviceManager.java:119)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2973)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:648)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:332)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:328)
    at com.ti.ccstudio.project.core.internal.build.ProjectAdviceManager.processAdvice(ProjectAdviceManager.java:460)
    at com.ti.ccstudio.project.core.internal.build.ProjectAdviceManager.handleAdviceChangingEvent(ProjectAdviceManager.java:421)
    at com.ti.ccstudio.project.core.internal.build.ProjectAdviceManager.handleAdviceChangingEvent(ProjectAdviceManager.java:409)
    at com.ti.ccstudio.project.core.internal.build.ProjectAdviceManager.onProjectBuild_Post(ProjectAdviceManager.java:394)
    at com.ti.common.project.core.internal.events.ProjectStateMonitor$ResourceChangeListener$7.visit(ProjectStateMonitor.java:373)
    at com.ti.common.project.core.internal.events.ProjectStateMonitor.notifyListeners(ProjectStateMonitor.java:644)
    at com.ti.common.project.core.internal.events.ProjectStateMonitor.access$2(ProjectStateMonitor.java:633)
    at com.ti.common.project.core.internal.events.ProjectStateMonitor$ResourceChangeListener.resourceChanged(ProjectStateMonitor.java:371)
    at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
    at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
    at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:359)
    at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:495)
    at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:405)
    at com.ti.ccstudio.project.ui.internal.actions.RebuildProjectAction$CCSRebuildAction$1.runInWorkspace(RebuildProjectAction.java:64)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
  • TI__Guru* 84285 points
    The compiler does not attempt to connect to the internet. You need to ask this question in the CCS forum.
    It is possible that CCS is connecting to the internet to find hyperlinks for compiler errors in the "problems" console. This feature is called "DMED" and is not under the control of the compiler.
  • in reply to eric bouxirot
    TI__Guru**** 173310 points

    eric bouxirot said:
    this is what i think try this connection..... (how can i disable this ???)

    You could try disabling the TI error parsers but note that that will also prevent the errors/warnings from appearing in the Problems view. They will still appear in the CCS Build console though.

    To disable TI error parsers, go to Project Properties, click on Show Advanced Settings at the bottom, go to C/C++ Build->Settings->Error Parsers tab, and uncheck all the TI error parsers.

  • in reply to AartiG
    Expert 2290 points

    Hi all,
    I faced the same problem a few days ago when the TI servers were very slow to respond and compilation stalled waiting for the network. I found that disabling the network connection "solved" the problem because the connection attempt failed immediately. Now the TI servers seem to be working normally again and I cannot observe the problem, though I am using 8 jobs (-j8) on a 4-core CPU to maximise CPU usage even when some jobs are blocked by other factors (like the problem discussed here). I created a new thread before being directed to this one.

    I tried disabling the error parsers but did not see any measurable speed difference now that the TI servers are up. This caused the Problems view to not show the compilation errors and warning, which is not very practical.

    It seems that this "feature" of Eclipse/CCS is not very well though of, since the overall speed of compilation relies on the response speed of a remote server.