• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 239 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.

CCS/TMDXIDDK379D: CCS Debug issue

Neil Patel
Prodigy 200 points
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

product: www.ti.com/.../TMDXIDDK379D

  • 0
    TI__Guru**** 168377 points

    Hi,

    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. 

    Regards,

    Rafael

  • 0 in reply to Neil Patel
    TI__Guru**** 168377 points

    Hi,

    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 7.4.7.4 of the CCS User's Guide (menu Help --> Contents) or at the link below. 

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

    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. 

    https://e2e.ti.com/support/tools/ccs/f/81/t/493016 

    Hope this helps, 

    Rafael