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.

XDC110: HW break point with integrated debugger

Other Parts Discussed in Thread: TDA4VM

Hello, 

picking up from a previous conversation on XDC110 Debugger, 

"The debugger will try to preserve any existing hardware breakpoints when possible. It will do so for a CPU reset. If you manually disconnect the debugger from the target and then reboot (power cycle), it will reapply the breakpoint when you connect the debugger again.

 

The only issue is if the device is rebooted while the debugger is still connected (which is NOT recommended). This will force the debugger to disconnect but it may put the debugger in a bad state where it may not be able to properly reapply breakpoints. Hence it may appear that a breakpoint is set when it actually isn’t. Manually toggling the breakpoint would resolve this. In any case, forcing the debugger to lose connection that way is not recommended." 

for an EVM with an integrated debugger like the TDA4VM is there a way to disconnect the debugger? (I am assuming that removing the usb is not disconnecting the debugger) 

  • Hello Daviel,

    picking up from a previous conversation on XDC110 Debugger,

    There's no link to a previous discussion in your post.

    is there a way to disconnect the debugger

    If somebody has advised  to "disconnect the debugger" I don't think they don't mean physically, they mean disconnect (and connect) through CCS. i.e. 'Run' -> 'Disconnect Target' or 'Run' -> 'Connect Target'.

  • If somebody has advised  to "disconnect the debugger" I don't think they don't mean physically, they mean disconnect (and connect) through CCS. i.e. 'Run' -> 'Disconnect Target' or 'Run' -> 'Connect Target'.

    Kier is correct. 

    Thanks

    ki