• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 194 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.

TM4C123GH6PZ: Real-time actions are not occurring when the program is running in debug mode.

Mathankumar Raja
Prodigy 60 points
Part Number: TM4C123GH6PZ
Other Parts Discussed in Thread: SEGGER,

Hi, 

I am utilizing a TM4C123GH6PZ custom board along with a Segger J-Link for debugging purposes.

Although I can enter debug mode, I am unable to observe any real-time actions such as live values, displaying digits on the 7-segment display, or initiating UART communication, RTC, or watchdog functionalities. Even after making modifications to the code, uploading them to the MCU, and power cycling the board, the changes take effect as expected.

However, it's noteworthy that during debug mode, I encounter a limitation wherein live execution cannot be observed.

Thanks

  • 0
    TI__Guru**** 191886 points

    Hi,

    Mathankumar Raja said:
    Although I can enter debug mode, I am unable to observe any real-time actions such as live values, displaying digits on the 7-segment display, or initiating UART communication, RTC, or watchdog functionalities.

    I'm not clear with your problem description. I have some questions.

    - Are you using CCS with J-link?

    - You mentioned about not working in debug mode. What about in free-run mode without the debugger connected. Does it produce the same behavior?

    - Are you saying the MCU is not running code despite code is loaded? Or the code is running but the debugger is not able to show something that you are looking for?

    - Do you see the same issue running the same code on a LaunchPad? This will tell if the issue is related to the firmware or the hardware.

    - To isolate it is not an issue related to your J-Link debug probe, do you have another debug probe that you can try? Do you see the same issue?

    - If you load a simple TivaWare hello example on you custom board, do you see the 'hello' message sent to the terminal window through UART?