HCS12 CW3,1 debugger not able to continue after breakpoint-seems to reset. COP???

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

HCS12 CW3,1 debugger not able to continue after breakpoint-seems to reset. COP???

跳至解决方案
2,244 次查看
AndersJ
Contributor IV

Hi,

I use HCS12 CW 3.1 and Processor Expert 2.95.

I also use the WatchDog bean.
It is auto initialized at startup by PE code.

While debugging I have problems with the processor restarting after
having stopped it to inspect memory, registers etc.

I have tried to enable the cpu bean "BDM Debug Support",
and setting the "Stop COP and RTI in Active BDM mode" to YES,
which does not help.

I have also attempted to disable the WatchDog bean.
Since the beans "Enable in ini. code" option is always greyed
I have not managed to do this.
The entire bean can be disabled but then my code breaks since the
WD code is no longer generated.

Q1: Why does it not help to "Stop COP and RTI in Active BDM mode"?
Q2: How can I temporarily disable the WatchDog bean?
Q3: What is the corect way to make sure the debugger can be started
   and stopped without causing any disruptions in the cpu internals?
Q4: Is there anything else I might be doing wrong,
   since I cannot "continue"" after stopping at a breakpoint.

Thanks,
Anders

标签 (1)
标记 (1)
0 项奖励
回复
1 解答
1,046 次查看
Lundin
Senior Contributor IV
I don't know about beans, but in C or asm, simply write 0x00 to COPCTL to disable the wdog. This register is write-once, but since you will be running in special single chip mode when debugging, that shouldn't be a problem.

An alternative is to set the flag COPWAI in CLKSEL register = "COP stops in wait mode".

在原帖中查看解决方案

0 项奖励
回复
1 回复
1,047 次查看
Lundin
Senior Contributor IV
I don't know about beans, but in C or asm, simply write 0x00 to COPCTL to disable the wdog. This register is write-once, but since you will be running in special single chip mode when debugging, that shouldn't be a problem.

An alternative is to set the flag COPWAI in CLKSEL register = "COP stops in wait mode".
0 项奖励
回复