CCS/LAUNCHCC3220MODASF: Runtime Object Viewer - Connection Timeout when attempt to connect to debugger

Joss,

That is odd. I can see from the screen capture that you have a valid debug session. I will loop in an ROV expert when they get in but I had one thought. I see in your debug view that you have a terminated debug session. I wonder if ROV is trying to connect to it. In the debug view you should be able to click on the double grey X on the right hand side to remove terminated debug sessions. Could you give that a try, close ROV, open it again and see if it can connect.

Regards,
John

John,

I tried closing the terminated debug sessions with the double x's, but ROV still times out while trying to connect to the debugger.  I tried closing and reopening CCS as well, with the same results.

Thanks,

Joss

Hi Joss,

Does ROV Classic work?

Todd

Joss,
you can get more debugging info with the following steps.
1. Go to your CCS installation and navigate to ccsv8/eclipse directory.
2. Open ccstudio.ini and add the line
-Djxbrowser-remote-debugging-port=9222
There is already a line that starts with -Djxbrowser in that file, so add your new line just below that line.
3. Restart CCS and the debugger, and start an ROV session.
4. Go to http://127.0.0.1:9222 in Chrome, and click on "Runtime Object View".
5. Click on the tab Console, and copy and post here the complete output.

I used Chrome, but other browsers might work too. Also, you can use a port other than 9222, if that one is already used.

Todd,

I'm having trouble finding a link to ROV Classic, do you have a link to the install files?

Sasha,

Here is the output I'm seeing:

[Deprecation] /deep/ combinator is no longer supported in CSS dynamic profile. It is now effectively no-op, acting as if it were a descendant combinator. You should consider to remove it. See www.chromestatus.com/.../4964279606312960 for more details.
rovapi.js:557 _connect: connecting ...
rovapi.js:588 activeDebugContext: {
   "data": [
      {
         "core": "Texas Instruments XDS110 USB Debug Probe_0/Cortex_M4_0",
         "project": "relay"
      }
   ]
}
agent.js:896 WebSocket connection to 'ws://127.0.0.1:54908/' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
createClientModule @ agent.js:896
rovapi.js:633 ROV _connect failed to acquire DS: socket error
rovapi.js:273 Error: setExecutable() failed: ROV _connect failed to acquire DS: socket error
rovapi.js:557 _connect: connecting ...
rovapi.js:588 activeDebugContext: {
   "data": [
      {
         "core": "Texas Instruments XDS110 USB Debug Probe_0/Cortex_M4_0",
         "project": "relay"
      }
   ]
}
agent.js:896 WebSocket connection to 'ws://127.0.0.1:54908/' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
createClientModule @ agent.js:896
(anonymous) @ agent.js:829
_fulfilled @ q.js:794
self.promiseDispatch.done @ q.js:823
Promise.promise.promiseDispatch @ q.js:756
(anonymous) @ q.js:564
flush @ q.js:110
rovapi.js:633 ROV _connect failed to acquire DS: socket error
rovapi.js:273 Error: setExecutable() failed: ROV _connect failed to acquire DS: socket error

Todd,

Took me a little while to find ROV Classic, but yes - ROV Classic works.

So the question is, why does the new ROV not work?

Thanks,

Joss Steward