• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 735 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/RM48L952: Breakpoints lost on target power cycle

Allen Hayward
Prodigy 150 points
Part Number: RM48L952


Tool/software: Code Composer Studio

I am debugging code on a RM48 processor communicating with a TPS65381A power supply. I need to be able to power cycle the board to place the TPS back into RESET mode which means the power is also cycled to the RM48. I am connected to the system using an XDS200 interface and am using Code Composer 7.1.0.00016. I have placed several breakpoints into the system prior to power cycling that work as expected. Once the power is cycled the system comes back up but no longer stops at the breakpoints. The communications to the target can be restored after power outage using the RUN -> CONNECT TARGET after which the breakpoints resume there normal operations after a target reset. I read in other posts that power loss can interfere with breakpoints.

Is there a way to create a breakpoint that "sticks" during a target power loss? I suspect the issue is that after a power up the debugger is not "engaged" with the CPU so the breakpoints are ignored until I manually restore communications.

  • 0
    TI__Guru**** 472441 points

    Hi Allen,

    Allen Hayward said:
    I have placed several breakpoints into the system prior to power cycling that work as expected.

    What kind of breakpoints are being set - hardware or software?

    Allen Hayward said:
    Once the power is cycled the system comes back up but no longer stops at the breakpoints.

    Are you disconnecting CCS from the target and then shutting down the debug session before you power cycle? Or just disconnecting the target without debugger shutdown? Please describe exactly the procedure that is being done here.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 150 points
    Hi Ki,

    I am using hardware breakpoints as indicated by [H/W BP] in the breakpoint list.

    I am leaving the Debugger connected at the time the power is cycled. The debugger correctly indicates a power fail occurred and I must reconnect the target manually after power up. At power up the target starts running automatically. After debugger reconnect the target halts at wherever it was in the code at the time and the debugger works normally. The breakpoint in CCS remains blue (active) and works if I RESET the target and start the program again without a power down.

    If there is an active breakpoint prior to power down I also get an error message of "Failed to remove the debug state from the target before disconnecting." when powered back up.

    Allen
  • 0 in reply to Allen Hayward
    TI__Guru**** 472441 points
    For HW breakpoints, the debugger needs to be connected to the target for the breakpoints to be active. If you know when you will power cycle the target (it sounds like you may), it is recommended to properly disconnect the debugger from the target (Run -> Disconnect Target) first. This will allow the debugger to properly remove and save the debug state before disconnect. This will allow the debugger to correctly restore the debug state on target connect (including set breakpoints). Otherwise it can put the debugger in a poor state and won't properly recover when reconnecting.

    Hope this helps
    ki