• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 480 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/LAUNCHXL-F28069M: Error debugging

Jinan
Intellectual 480 points
Part Number: LAUNCHXL-F28069M


Tool/software: Code Composer Studio

hello, 

Once debugging lab2a , an error came up saying this: 

Error connecting to the target:
(Error -1015 @ 0x0)
Device is not responding to the request.  Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 8.4.0.00006)

Note that I previously debugged the same lab without any debugging errors.

By repeating the debug new errors come up : 

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 8.4.0.00006)

I tried to change the cable, with a new one, same error remained. 

Could it be power supply error? I am using 9 V battery to spin a small motor. 

Can you screenshot how to Unlock the device as recommended above in the error details. 

Here is a screenshot of my screen


Thanks , 

Jinan

 

 

  • 0
    TI__Guru**** 171254 points

    Jinan,

    Error -1015 can be originated from multiple sources of error. Please check a description and a few related threads in the Debugging JTAG page below (just search for the error number).

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

    Usually the second error (-1135) reflects a secondary root cause that is influenced by the first one - thus with minimal relevance for the troubleshooting process. 

    That said, to unlock the device you may need to keep it in "Wait in Reset" by properly setting its bootstrap jumpers. This will prevent the code from running after power on/reset, which will have more stability during the connection process. 

    Hope this helps,

    Rafael