Green Hills Probe [BDM], MPC565 Single Stepping Problem



All,

I have some code running on a phyCORE MPC565 development board that I
created with the Green Hills MULTI toolset. I can load and run the
code forever error free. I can run from reset to a breakpoint, and even
do _some_ single stepping. Then, for reasons unknown, the debugger
simply decides to stop single stepping at a given instruction, It tell
me it's stopped at an unknown breakpoint. But, there is no breakpoint
explicitely set, and the offending instruction can be be executed w/o
an erros if I set a breakp[pint later in the code and run from reset.

I could be imagining it, but it seems to be somehow related to "branch"
instructions.

Has anyone seen this before? If so, what is the work-around or fix? It
has to be a configuraiton issue since this is basic functionality.

Any help would be appreciated. I have an entire team that could use the
tool if if would work, and our schedule is very tight.

Thanks in advance,

-Eric

.



Relevant Pages

  • Re: Setting breakpoint on the end of the method in Eclipse
    ... You whine that the IDE does not add a "nop" (is there even such an instruction in the JVM?). ... Right before the first instruction of a loop is the same spot as right after the last. ... which can be eliminated with a conditional breakpoint if it bothers you that much. ... It no longer sucks, does it? ...
    (comp.lang.java.programmer)
  • Re: How to implement the breakpoint in debugger?
    ... Breakpoint Handling ... the CPU raises an exception and reports it to GDB. ... theory is that GDB will replace a program instruction with a trap, ... set not to have any instructions usable for a software breakpoint, ...
    (comp.os.linux.misc)
  • Re: Slightly crazy idea to speed up EX instructions (XDC issue?)
    ... immediately following instruction, z/XDC's tracing process can get stuck. ... he immediately started using such code sequences as "gatekeepers" to try to keep an XDC user out of code that he wanted to keep "secret". ... XDC is perfectly fine with setting a breakpoint either on the EX or on its target or on both! ...
    (bit.listserv.ibm-main)
  • Re: [PATCH] Linux Kernel Markers
    ... "overwrite first 5 bytes of old function with `jmp new_function'". ... Insert breakpoint only on those routines at runtime. ... When the breakpoint gets hit, change the instruction pointer to ... the instrumented routine. ...
    (Linux-Kernel)