• Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 860 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/TM4C129ENCPDT: LOAD PROGRAM ERROR

Barry Andrews
Genius 3460 points
Part Number: TM4C129ENCPDT


Tool/software: Code Composer Studio

I am using CCS V7 with XDS2xx probe, have observed the same issue with XDS100V2 probe.

Up until last Friday I did not have any issues, suddenly when I went to debug the program I got the following.

I have found that I can recover this by deleting the .launches folder from the debug folder and restarting the CCS application.

However, after working once or twice I once again get the failure.

I am also finding that the debug fails to connect first attempt and I have to click the retry button in order to get the debugger to connect.

 This is most frustrating and wasting heaps of time, would appreciate feedback on how to fix this.

  • TI__Guru**** 472411 points
    Hi Barry,
    Usually this error occurs when the debugger is unable to find the executable to load (due to some build error). I don't think that is the case for you. Do you see any other error messages in the console? When you clean the .launches folder to remedy the issue again and then after a bit the error returns, have you been rebuilding the project at all?

    Thanks
    ki
  • in reply to Ki
    Genius 3460 points

    Hello Ki-Soo

    I have given up on CCSV7.1 and gone back to CCSV6.2 and it is all working fine again.

    With CCSV7.1 I managed to get it working by deleting the ".launches" folder and restarting the CCS IDE each time, however this is very painful and not at all efficient.

    Altogether I find the debugging / JTAG on CCS flaky.

    Even when it is working I get the debug connection failed almost every time I try to connect, followed by a working connection as soon as I click retry.

    When I get an exception under TIRTOS the stack trace is destroyed and you get no information other than which task is the problem.

    Basically the whole thing is flaky which is annoying as I like the processor and I like the TIRTOS firmware.

    I guess its a case of you get what you pay for.

    I shouldn't need to be deleting folders all the time or fixing corrupted files, and debugging should aid the programmer, not further frustrate them.