• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 846 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/TMS320F28388D: XDS110 emulator issue on Windows 10 CCSv9.2

Sudharsanan
Expert 5330 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

I am using two XDS110 emulators connected to CCSv9.2.0.00013 with latest emulation updates.I have two different workspaces and the target configuration differentiates the emulators based on Serial number of the Emulator. 

While using the emulators to debug the software on target boards(F28388D based internal development boards). I get this error:

IcePick_C_0: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 8.4.0.00006)

CS_DAP_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 8.4.0.00006)

C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006)

Cortex_M4_0: JTAG Communication Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 8.4.0.00006)

Cortex_M4_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

This error is displayed on both CCS instances. Only a PC reboot helps to recover from this state. 

If attempting to connect without a Reboot CCS displays an Error message:

Error connecting to the target:
(Error -261 @ 0x0)
Invalid response was received from the XDS110.
(Emulation package 8.4.0.00006)

Regards,

Sudharsanan

  • 0
    TI__Guru**** 171074 points

    Sudharsanan,

    When you say that you have two workspaces, do you mean you have two CCS instances opened at the same time? If so, are you able to connect to each Debug Probe using only one instance of CCS opened? I am trying to better understand if there is no clash between the two. Also, if you have one debug session opened, can you go to the other CCS instance and issue a Test Connect? This would also reveal any clashes between the two instances. 

    I strongly suspect this may be the case, given that in the past two days I have been using the same version of the TI Emulators component, various Debug Probes (including the XDS110) and several F28x development kits (including a similar F28379D controlCARD) without issues. 

    Also, when the issue happens and you close both CCS instances, can you open the Windows Task Manager and see if there are any lingering processes of ccstudio.exe and Node.js? These may indicate that something prevented CCS from fully closing and therefore releasing the XDS110 Debug Probe. 

    I will try to think about additional details and report back if I find anything relevant. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    TI__Expert 5330 points

    Rafael,

    desouza said:
    do you mean you have two CCS instances opened at the same time? If so, are you able to connect to each Debug Probe using only one instance of CCS opened?

    Yes, I have two instances of CCS open at the same time. Each using different workspace and different Target Configuration files, selecting the XDS110 using serial number. 

    desouza said:
    Also, if you have one debug session opened, can you go to the other CCS instance and issue a Test Connect? This would also reveal any clashes between the two instances. 

    I am using the two instances all the time. When the issue happens it shows up in both the instances at the same time. 

    One additional observation is with latest TI emulation updates( with fixes related to XDS110) the frequency of occurence of the issue has come down. But it is annoying when it happens.. 

    Regards,

    Sudharsanan

  • 0 in reply to Sudharsanan
    TI__Guru**** 171074 points

    Sudharsanan, 

    Please apologize for the delay, but unfortunately the holidays delayed any attempts to further explore this. 

    Would it be possible to try to run the two debug probes in a single CCS session and see if the stability improves? Check the short clip below for details:

    https://youtu.be/w-W4eWYBnN4 

    Hope this helps,

    Rafael