Crasy,
Yes, I have installed that update after installing 3.1. It allows me to usually see the BDM Multilink on the connect window. However, when attempting to run the debugger, it will almost invariably hang at 80% when programming the chip. It will not do this under 4.7 while using the same board and BDM. For these steps I'm attempting a plain old vanilla project created with the project wizard and no changes made to program. All the program does is go into an infinite loop and performs no action.
When it hangs, the only message that shows up in the debugger window is 'Mcu invalidated'. No other comments at all. If I google search on that message, I get a few other forums for people having trouble, however none of the suggestions seem to point towards a solution for me. I've wondered if it's some sort of timing issue, since the autoset clock is different from what I get when I manually compute the timing calculation (15, vs 14). However, I cannot communicate at all when I manually set the timing to 14.
I qualified the above statements with a 'usually' and an 'almost always' because sometimes when I start the debugger, the BDM doesn't appear at all, even when the blue and yellow lights are on. If it doesn't appear at all, I can usually get it to appear by opening the 'Connect' dialog box and manually selecting it or repeatedly trying to open the debugger and going to the 'Connect' dialog box.
Finally, just last morning, I got a setup that appeared to work. But that install process has been unrepeatable.
If it helps any, I've been trying to install some permutation of:
CW 3.1
Patch C128
Patch E256
USB 2.0 Patch
P&E BDM Multilink Drivers.
Additionally, CW3.1 offers to install a different BDM driver (Noral ?). I've tried installing with and without this. I have no idea whether it works in conjunction with the P&E driver, just gets in the way, or is irrelevent.
-slaybalj