Breakpoints problems with p&e multilink usb cable

[Pitrunner]

I have a problems to set breakpoints with the new version of p&e multilink USB cable rev C that I have received with Codewarrior v 4.5.
I build up a new board with the 9S12XA512 on it. If I load down a small test code, the code runs and I can make e.g. changes in the registers, but I'm not able to set any breakpoints.
The context menu does not show "Set breakpoint". See Figure B in attachment.

When I load down a similar code to freescale demoboard 'DEMO9S12XDT512" all worked well.
See Figure A.

I assume that the integrated p&e interface on the freescale demobaord is similar as the p&e multilink usb cable.

So somebody can help me? Thank you.

[J2MEJediMaster]

1) Have you tried single-stepping through the code to see if the debugger has control?

2) Have you set a breakpoint immediately past the starting point in your code to confirm that the breakpoint mechanism is working? (Yes, you've set breakpoints, but if they're elsewhere and the program doesn't happen to run through those sections of code, the breakpoints don't appear to fire.)

---Tom

[Pitrunner]

1.) Yes it is possible to make single step, so the debugger has control.

2.) I set breakpoints at the beginning of my code, but the mechanism does not lock at that point.

[Pitrunner]

Workaround for the problem.
In the moment it looks so, that the Code Warrior Ver.4.5 is responsible for the problem.
Because if I use the older Ver. 4.1 and start then the debugger, I can set a breakpoint and the hardware reacts to it.
Anybody with similar problems?

[J2MEJediMaster]

1) Make sure you have the latest build and updates for CW 4.5.

2) Go to www.pemicro.com and download their latest drivers.

---Tom

[Sten]

It looks to me like you already have a breakpoint at SetupXGATE(), and if you have rightclick on that, you can only delete or disable the breakpoint. If you rightclick on any other row, you should be able to add a new breakpoint.

[Pitrunner]

I agree that the enclosed attachment was not a good example.
Because I should explain it in this way.
The debugger programm allows me to set a breakpoint, but the hardware does not react to it.
So why can I load the code to the MCU and it runs well, also I got an response if I change a register value. But if I set a breakpoint I got no reaction to it.