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: TMDXIDDK379D
Tool/software: Code Composer Studio
I am trying to use TMDXIDDK379D kit to run a motor. I am following the IDDK user's guide's example CCS project and it fails on whenever I try to debug the project. The project complied and worked the first time and didn't work after that. I am stuck on 4.4 in user guide step 11. so now I get the following errors after I debug.
user guide: http://www.ti.com/lit/ug/sprui44/sprui44.pdf
What kind of error are you getting? Is this error happening when you are launching the debugger or after you start running your code?
In any case, please copy the error messages or describe the expected runtime response versus the unexpected runtime error you are getting.
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:
In reply to Neil Patel:
Please apologize for the delay; I missed your reply. Are you still having this issue?
The description and error indicate to me there is a lingering status of a previous run. The second screenshot indicates the CPU seems to be stable, but perhaps a breakpoint set in a prior run (on the LS0 RAM) is not valid anymore due to a reset event (breakpoints are cleared during reset transitions). You can open the Breakpoints view and clear all breakpoints - check section 22.214.171.124 of the CCS User's Guide (menu Help --> Contents) or at the link below.
If you keep getting issues loading the code, I wonder if the first run may be influencing the ability to properly run a second time. This could be solved with a power cycle of the board, but obviously that, if the failing software is still programmed in Flash, the outcome would be the same. A workaround would be to enable the "wait on reset" and performing a step-by-step by checking the following thread.
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.