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/TM4C1290NCPDT: Anomalous IDE loading/debugging behavior.

Part Number: TM4C1290NCPDT
Other Parts Discussed in Thread: SEGGER, TM4C1231H6PM

Tool/software: Code Composer Studio

When I click on the Debug button, the system loads the program but does not run and stop at main(), sometimes only the Stop button is enabled, other times the Start and End buttons are enabled and it shows the PC stopped at some random location in the code.  I click Stop then the Debug button again and the program loads and indeed the PC breaks at main().  When I click run the code runs but the SysTick timer does not run.  If I click Stop and then power-cycle the board everything runs fine but I can't use any of the debugging tools.

CCS v9.3.0.00012, Segger Flasher with their latest software.

I posted this earlier on my other account (different business) and the suggestion was that I contact Segger for their advice.  They stated that they have not experienced any problems like this with this CPU.

I have used this Segger Flasher successfully on a different design with a TM4C1231H6PM and CCS v8.3.1.00004

Thanks, Doug

  • Hi Doug,

    Doug Broadwell85 said:
    the system loads the program but does not run and stop at main(), sometimes only the Stop button is enabled

    If neither the resume or halt button (or any of the target execution buttons besides terminate) is available, then it sounds like the proper debug context is not selected.

    Doug Broadwell85 said:
    other times the Start and End buttons are enabled and it shows the PC stopped at some random location in the code. 

    This sounds like some exception was hit

    Doug Broadwell85 said:
    I click Stop then the Debug button again and the program loads and indeed the PC breaks at main().  When I click run the code runs but the SysTick timer does not run. 

    By this time, it looks like the target is not in a good state (hence why the power cycle seems to help)

    Doug Broadwell85 said:
    If I click Stop and then power-cycle the board everything runs fine but I can't use any of the debugging tools.

    Can you clarify what you mean by "I can't use any of the debugging tools."? Do you mean that you power cycle the board and the code boots from flash and runs fine as long as you don't connect CCS to it?

    Thanks

    ki

  • Thanks Ki,

    You got me thinking and I again tried something that I thought I had tried before, which was to set "Reset the target on a connect", and now it works correctly.

    Regards,

    Doug

  • Glad to hear you resolved the issue and thank you for the update!

    ki