topic Re: Debugging problem CodeWarrior 5.7 in CodeWarrior for MCU

Debugging problem CodeWarrior 4.6

chhg — Mon, 26 Nov 2007 20:42:16 GMT

I am using CodeWarrior 4.6 with BDI1000 on HC12A4. The debugger can download an run my abs file without problem and all works fine. But when I set break points and/or step over functions, the current C-code-line can not be found mostly and I have to reset the device.

Does somebody know something about this stepping problem?

Re: Debugging problem CodeWarrior 4.6

J2MEJediMaster — Mon, 26 Nov 2007 23:38:54 GMT

It sounds like you're not getting debugging symbols for your program, especially if the code downloads fine. Sorry, I have to ask the obvious because I don't know your exact setup.

Does it single-step fine through the code? Or does the debugger lose it after a while even when you do that?

---Tom

Re: Debugging problem CodeWarrior 4.6

chhg — Tue, 27 Nov 2007 00:38:30 GMT

Hi,

The compiler setup are:

-Cc -Cf -CpDPAGE -CpPPAGE -D_DEBUG -F2 -Mb -One -TD4LD4LLD4 -W2 -WmsgSd3303

In "Smart Slider" is the "Debug Complexity" around the center (~45%).

Sometimes it does single-step fine, but there is no rule, when the debugger lose it. It loses not always at the same location, when I jump into a function or over it, but mostly by loosing the procedur.

Thanks Christian

Re: Debugging problem CodeWarrior 4.6

CompilerGuru — Tue, 27 Nov 2007 16:16:09 GMT

I would check if all the interrupt handlers you have do either not set PPAGE/DPAGE,
or they do properlty back it up before modifying.
The descriptions sounds like if PPAGE would get corrupted by an interrupt,
do you "loose" the target when you are stepping in the 0x8000..0xBFFF PPAGE area?
Maybe try to assembly single step and try to catch the case where it just jumps away.

Daniel

Re: Debugging problem CodeWarrior 5.7

chhg — Tue, 27 Nov 2007 22:17:13 GMT

You are right: Always when it "loses", the assembly steps are between 0x8000 - 0xBFFF! What can I do?