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/TMS320F28035: The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

Part Number: TMS320F28035
Other Parts Discussed in Thread: TMDSCNCD28035ISO

Tool/software: Code Composer Studio

Hello,

I am trying to run an example code from a control suite library for the TMS320F28035PN.

When I hit the debug button, the following Errors shows.

(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 6.0.222.0)


I have checked the device manager for usb connections. It does show.

I have also uninstalled ccs and reinstalled it with the spectrum digital drivers as previous threads have suggested. Still have same error. Any other ideas that could solve my problem? Please let me know. Thank you.

-Luis Riveros

  • Luis,

    Please check section 5.16 of the following page:
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    Hope this helps,
    Rafael
  • Hi Rafael,

    I have read the posts linked from then the wiki page. However, they did not help me fixing the problem. any other suggestions??

    Thank you.

    Luis R.

  • For others following this thread, this error was fixed.

    The error involved a DRV8412-C2-KIT and the error message was being caused by the switch SW3 of the F28035 ISO controlCARD (TMDSCNCD28035ISO) being set to the OFF (up) position.

    One of the controlCARDs was completely operational after the above procedure. However, another controlCARD was still showing the error below:

    This error is generated by TI's USCIF driver or utilities.

    The value is '-150' (0xffffff6a).
    The title is 'SC_ERR_FTDI_FAIL'.

    The explanation is:
    One of the FTDI driver functions used during
    configuration returned a invalid status or an error.

    This new error turned out to be caused by pre-existing code on the flash memory of the F28035. Changing the boot mode of the device on SW2 allowed the JTAG to properly connect to the F28035 device of this second controlCARD.

    Regards,

    Rafael