• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 3631 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.

CCS/CC3220SF-LAUNCHXL: ROV _connect failed to start agent: socket error

Paavo Hynynen
Prodigy 60 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Tool/software: Code Composer Studio

Hi

I'm running the basic HELLO_CC3220SF_LAUNCHXL_tirtos_ccs example on LAUNCH-XL board.  My CCS is version 7.2.0.00013.  When starting ROV and clicking CONNECT button in the Connect to target -view of ROV, I get following error:  ROV _connect failed to start agent: socket error. 

I'm looking for a reason why ROV connect fails.

ROV Classic works as expected, also building, breakpoints work as expected.

regards Paavo

  • 0
    TI__Guru**** 162485 points

    Paavo,

    I haven't had any luck reproducing this.  What is selected for the target communication link?

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 60 points
    John,

    The Connect Target dialog looks exactly, what you posted above, i.e. the Target communication link is "Debugger". That is also the only alternative in the Drop down list of communcation links.

    Properties dialog for HELLO_CC3220SF_LAUNCHXL_tirtos_ccs say that the Target Connection is TI XDS110 USB Debug Probe, which I guess is right for this dev board. I tried also out RTOS Analyser -> Execution Analysis and that seems to work, i.e. it can collect the data from the dev. board. when I halt the program.

    I'm running this just now in a very basic ASUS laptop, with Windows 10 Home, version 1703.... so nothing very special there.

    Regards
    Paavo
  • 0 in reply to Paavo Hynynen
    Prodigy 60 points
    John
    In the end this seemed to be just some glitch. I did not quit CCS when I last time did put my lap-top to sleep and afterwards - when waking up the lap-top again - started to work with that alredy running CCS instance. The problem went away, when I just quit CCS and restarted it.
    Sorry for bothering with a trivial issue.
    regards Paavo
  • 0 in reply to Paavo Hynynen
    TI__Guru**** 162485 points
    No problem Paavo. I will give that sequence a try. If I can reproduce it I will file a bug as we should be able to handle that more gracefully, especially since the rest of debugging worked fine.

    Regards,
    John