topic Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor in CodeWarrior for MCU

Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

HK168 — Sat, 02 Dec 2006 01:21:13 GMT

Hi,

I was able to connect Hi-Wave debugger to a HC11 target. The single step works. But it does not work properly using a break point. From the trace (serial protocol trace with the debugger and target), it does not decrement the return address by 1 in the stack as was done in the single step. I was using version 3 of the debug monitor which came with Metrowerks CodeWarrior software package. Is this a known issue? How can I fix this problem since I don't have source code of Hi-Wave debugger.

Thanks in advance.

Jolland

Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

joerg — Sat, 02 Dec 2006 04:25:39 GMT

Dear HK168
I have had some experience with HC11 and CW (as teacher). It was often the case that after a breakpoint the execution did not react on the RUN command. Sometimes a single step command followed by RUN worked. I noted often that the debugger did not work in interrupt routines.
That's why i am not very satisfied with monitor debugging programs in general (speaking with about 25 years of experience, starting with 8085 and Z80 stuff). If possible change to HC(S)08 or HC12, since the HC11 is neither a fish nor a bird (German saying!) (i mean the HC11 is not really a 16bit MPU).

Sorry but i have no more access to the HC11 system.

Saluti Joerg

Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

CrasyCat — Mon, 04 Dec 2006 20:03:31 GMT

Hello

I did not use HC11 ROM monitor since a while, but as far as I remember, when debugging through ROM monitor, you HAD TO make sure you enable the interrupt somewhere in the main function.

Did you enable the interrupts?

CrasyCat

Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

joerg — Tue, 05 Dec 2006 03:10:42 GMT

Crasy Cat is right

It is a good idea to set first the stack pointer to the top of the RAM and the to enable
the interrupts be clearing the I bit with a CLI command.

Saluti joerg

Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

HK168 — Tue, 05 Dec 2006 11:03:58 GMT

It was a bug in my debug monitor. Now I can set breakpoints or using single steps in the Hi-Wave debugger connected to a target. The debug monitor which comes with Metrowerk works with minor modification.

I will be testing interrrupts other than "swi" next. Thanks for all the good suggestions and helps.

Jolland

Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

HK168 — Wed, 06 Dec 2006 02:37:47 GMT

Thanks for the information. Do you know where I can find more information regarding to writing and understanding cmd files?

Thanks again.

Jolland

Re: Break Point Problem with Hi-Wave Debugger Connected to HC11 Target Debug Monitor

CrasyCat — Wed, 06 Dec 2006 22:24:19 GMT

Hello

You should be able to find a description of debugger command line syntax in {Install}\\docu\HC11\manual\Manual Engine HC11.pdf.

Chapter HI-WAVE Commands is all about available commands.

I hope this helps.

CrasyCat