The message in the status bar reflects the current state of the CPU, and probably why it has reached this state.
The CPU has stopped because the user issued the Break command.
- stopped by breakpoint
The CPU has stopped because of a breakpoint condition (software or on-chip), and the breakpoint condition was set up via the debugger (e.g. Break.Set command).
- stopped by XXXevt
The TriCore CPU has stopped due to an event not triggered by the debugger. It shows the reason reported in the Debug Status Register, where XXXevt can be
software event, the CPU has executed a debug or debug16 instruction
external event, e.g. event on nBRKIN line via the JTAG cable
access to a Core Special Function Register (SFR) (feature not used by debugger)
- tr0evt or tr1evt
Memory Protection event, normally used by on-chip breakpoints
- stopped by unknown
An unknown event has occurred, the CPU is probably in some undefined state.
When using Target Based Flash Programming, the debugger shows "stopped by swevt" after each flash programming or erase action.