• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 3338 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.

Original question:

CCS/TMS320DM8148: JTAG : IcePick_D_0: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110

CCS/LAUNCHXL-CC26X2R1: IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110 (Emulation package 8.0.27.9)

Torbjorn Sorby
Expert 6315 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software: Code Composer Studio

Hi,

I get this message infrequently during debug session.

CCS Version: 8.1.0.00011 

macOS - High Sierra Version 10.13.2

  • 0
    TI__Guru**** 171309 points
    Tornbjorn,

    Historically this is quite an elusive error. It seems to stem from various scenarios without a clear root cause and affects various target devices.

    e2e.ti.com/.../639662
    e2e.ti.com/.../632959
    e2e.ti.com/.../2438605

    Our investigation and the various reports tend to indicate some sort of timeout or sudden loss of communcations, but unfortunately we couldn't thoroughly reproduce this here. Perhaps one of the above threads may help you overcome this?

    Regards,
    Rafael
  • 0 in reply to desouza
    TI__Expert 6315 points

    Hi Rafael,

    It doesn't actually seem to cause an issue. Over a period of about 5 minutes it happened about 5 times, in a irregular pattern.

  • 0 in reply to Torbjorn Sorby
    TI__Guru**** 171309 points
    Tornbjorn,

    Yes, that is what I observed here as well: it seems a recoverable glitch (a timeout of some sort) instead of a catastrophic failure for the JTAG connection.

    We had something similar when using EnergyTrace with higher data rates, but the message was slightly different.

    Taking the EnergyTrace case in point, perhaps you could try to reduce the TCLK speed in the JTAG configurations and see if the instability disappears? Also, check if there are other activities on the system that may contribute to a delay in communications such as high USB activity, overcrowded USB Hub, antivirus or other disk intensive operation. In the past these factors used to cause trouble with other soft-emulators such as XDS510.

    Regards,
    Rafael
  • 0 in reply to desouza
    TI__Expert 6315 points
    I believe I was running EnergyTrace at the time. Not a big deal as I said :)