The new palmOne Treo 650 device ships with a newer version of HotSync Manager, and this is tripping up CodeWarrior for Palm OS V9 users. I just had a conversation with a developer that produced some useful notes.
CodeWarrior's debugger uses the USBPort.dll file included with HotSync Manager to handle its debugging connection. To load this DLL, CW's debugger uses instaide.dll to find out the location of the Palm Desktop data folders, and then tries to load this DLL from there. Previous versions of Palm Desktop put this in the "C:\Program Files\Palm" folder, with all of the data folders being in this directory. However, the Treo 650 Desktop installer puts USBPort.dll file into the System32 folder.
The developer tried a few things, but eventually was successful in getting both debugging and HotSync working. To quote:
So I installed the 4.1 desktop software (after removing the 6.0 version) and lo and behold, the USBPort.dll file is in the PalmOne folder and Metrowerks can debug via USB. I then installed the Treo 650 desktop on top of 4.1 and it moved the USBPort.dll file to the System32 folder! Now Metrowerks no longer worked. I tried copying the USBPort.dll file back into the PalmOne folder (as well as many other locations), but nothing worked.
Finally, I installed the 6.0 software from scratch, stopped HotSync, then moved (not copied) the USBPort.dll file into the PalmOne program folder. Success! Now HotSync works AND Metrowerks can debug via USB.
I'm glad its working for you now. In the future, one way to determine from where CW's debugger is trying to load USBPort.dll is to use the free program Dependency Walker to run the CW IDE and see a log of all of the DLL loads; try to start a debug session, and you'll see an error entry showing the path used to load USBPort.dll.