• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 350 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.

Original question:

CCS/EK-TM4C123GXL: CORTEX_M4_0: Trouble Halting target CPU problem

CCS/EK-TM4C123GXL: Code Composer Studio™ forum

Pedro Tavares
Prodigy 70 points

Part Number: EK-TM4C123GXL
Other Parts Discussed in Thread: TM4C123GH6PM,

Tool/software: Code Composer Studio

Dear Ki,

Thanks for your help so far. It is been a time since last try because the corona issue I couldn't not return to my lab from that time. However, I tried all options quoted and it didn't work. Indeed the incident of it decreased but it stills as a not feasible frequency of incidence.
-I connected the board as TM4C123GH6PM

-Changed the JTAG frequency to 500 kHz (half of original)

-I connected TIVA on USB 2.0


Do you reckon this can be because the open terminal to change parameters by UART?
Its baud rate is 115400, standard config set.

The  CORTEX_M4_0: Trouble Halting target CPU always occurrs after I power the system and drive the luminaire with the buck, in open or closed loop

Do you speculate other changes that i can apply to try to fix it? I will try desperately to change computer and TIVA also to see if it any hardware possibility of error.

Best Regards,
Pedro L.

  • 0
    TI__Guru**** 171639 points

    Pedro,

    If I understood your setup, you are using the EK-TM4C123GXL to debug your custom board.

    Pedro Tavares said:
    The  CORTEX_M4_0: Trouble Halting target CPU always occurrs after I power the system and drive the luminaire with the buck, in open or closed loop

    Since this is a non-isolated Debug Probe, the scenario you describe above is very common in applications that drive high power systems. Several possible reasons are described in the section Hardware checklist of the Debugging JTAG page below (look for the tips 6, 7 and 8)

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

    Pedro Tavares said:
    Do you reckon this can be because the open terminal to change parameters by UART?

    UART and JTAG debugging use different USB endpoints and interference between the two are uncommon. 

    Hope this helps,

    Rafael