• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 250 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F280039C: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

Aaron Ogorzaly
Prodigy 10 points
Part Number: TMS320F280039C
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello,

I am currently running into this error when trying to flash my TMS320F280039C using Simulink integrated with Code Composer Studio 12.8.1:

Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 20.0.0.3298)

I successfully flashed my TMS320F280039C twice before using the same code, and this error occurred the third time with the same code. I have tried running a simple code in CCS, but debug came back with the same error. The "Test Connection" comes out successful. I have tried updating my CCS and using the UNIFLASH tool, which still runs into the same error when trying to connect. LEDs 1:A, 3:A, and D3 all light up RED, BLUE, and GREEN respectively, and LED 2:A weakly flashes BLUE once when trying to connect. I have also checked if the java based jar files are present in the class path, and they are. 

I am not sure how to proceed, or even how to determine if the on-board XDS110 debugger is broken. I would appreciate the help.

  • 0
    TI__Mastermind 32296 points

    Hi,

    Could you please check out this app note? https://www.ti.com/lit/pdf/spracf0

    Thanks,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 10 points

    I have looked over this app note and tried the recommended troubleshooting, but still no luck. When I perform Test Connection(s) in CCS, I see this message in the test results:

    -----[Print the reset-command hardware log-file]-----------------------------
    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    Is this possibly a hardware issue?

  • +1 in reply to Aaron Ogorzaly
    Prodigy 10 points

    Found the error. There was 1.6V going to the processor core. May have been the result of ESD, but uncertain.

  • 0 in reply to Aaron Ogorzaly
    TI__Mastermind 32296 points

    Ok, I am glad you found the problem. I am closing this thread.