• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 264 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.

EK-TM4C123GXL: losing target during debugging

Mohammed Fawzy
Expert 1935 points

Part Number: EK-TM4C123GXL

Hello,

My Environment:

- CCS Version: 9.3.0.00012 

- tirtos_tivac_2_16_01_14

-xdctools_3_32_01_22_core

at the start of my program, once I made step execution and once i reach line SysCtlPeripheralEnable(SYSCTL_PERIPH_ADC0);, then I lose the target and getting the bellow error messages

CORTEX_M4_0: Can't Run Target CPU: Debug Port error occurred.
CORTEX_M4_0: Error: Debug Port error occurred.

and no more steeping can be made.

Please advise!

Thanks,

Mohammed

  • +1
    TI__Guru**** 191886 points

    Hi,

      -  Do you have the same problem with any other TI-RTOS programs? I want to make sure it is not something related to the debug probe or a  hardware issue. 

      - Can you repeat the same issue on another LaunchPad if you have a spare one?

      - Prior to the SysCtlPeripheralEnable(SYSCTL_PERIPH_ADC0), were you able to single step?

      - Can you reconnect to the target again after the issue occur? 

      If this is only specific to your current program then please show your code or perhaps create a small CCS project that you can replicate the issue and attach the project. 

  • 0
    Expert 1935 points

    Actually, after changing the launchpad, The problem is resolved.

    but the most vague thing that I'm able to do single step but when reaching the line where I'm trying to enable the ADC0 or ADC1, then I lose the target.

    Any Idea?

  • 0 in reply to Mohammed Fawzy
    TI__Guru**** 191886 points
    Mohammed Fawzy said:
    Actually, after changing the launchpad, The problem is resolved.

    So a second LaunchPad running the same program does not have the problem, correct?

    Mohammed Fawzy said:
    but the most vague thing that I'm able to do single step but when reaching the line where I'm trying to enable the ADC0 or ADC1, then I lose the target.

    Are you still referring to the first LaunchPad?

    I really don't know why enabling ADC0 will cause the connection to lose. Do you have other programs to run that will always run normally but only lose connection when you insert the enable for ADC0.