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.
Part Number: DRV8301-HC-C2-KIT
Tool/software: Code Composer Studio
We are using the DRV8301-HC-C2 kit for turning BLDC motors. We recently purchased a new f28035 control card and tried to debug a new project. When we did this, we got the following error:
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).
This control card is brand new, so I don't see how it could be damaged. I've read on these forums that we need to use "wait in reset " mode or perhaps check the flash content of the card? How exactly do I do these things? I'm not sure where to access "wait in reset" mode or the flash content inside CCS.
Hi, Please check the Debugging JTAG reference below, which contains references to troubleshoot this error (search the page for the error code). http://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html Hope this helps, Rafael
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to desouza:
I have tried everything in this manual and still am not having any luck. I'm not sure where to find the boot mode settings to use "wait in reset" in ccs v7. Can you tell me where that is located?
Also, are there any issues related to a brand new control card that could be related to this issue?
In reply to Ben Wright:
Please apologize for the delay; I missed your reply.
Were you able to overcome this issue?
I was trying to find any additional details that may trigger this scenario, apart from the issues reported above, I couldn't find anything that could trigger this.
Obviously that a faulty controlCARD is a rare event but not necessarily impossible.
The "Wait in Reset" is usually useful to try to erase the device and bring it out of a locked state. That shouldn't be the case with a new board, though.
At any rate, the "Wait in Reset" is set by the Advanced tab of the Target Configuration File.
The options specific status of the EMU0 and EMU1 pins - the thread below mentions this.
Hope this helps,
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.