I have configured CodeWarrior to use USB and an actual device, not the Emulator. I put the device in the cradle, and enter "shortcut .. 2" to enable the debugger. When I do this, the Windows H/W manager alerts me that the Palm device is active. But when I go into Code Warrior and hit "connect", I receive the following error messages:
>> CmdReadRemoteMem: error in SlkSendPacket = Error code: FFFFFFFF >> CmdReadRemoteMem: error in SlkSendPacket = Error code: FFFFFFFF and when I use the Palm Hardware debugger from OS 4SDK and enter "att" I get this error: >> CmdGetRemoteState: error in SlkReceivePacket = Serial Link timeout. and when I use the Palm Hardware debugger from OS 5 SDK I get a scrolling list of the same error even before I enter the "att" command: >> error code: 040E >> error code: 040E >> error code: 040E >> error code: 040E >> error code: 040E >> error code: 040E >> error code: 040E Obvious things: 1. I have been able to Hot-Sync via USB without any issues 2. I do not have the Hot-Sync software running while debugging 3. I'm using Metrowerks (IDE v4.2.6.832, Compiler is v8.3). 4. Palm Debugger is 4.0 for the OS 4 release), 4.2 for the OS 5 release 5. My Palm Desktop is version 4.1, and HotSync Manager is version 4.1.0 Is there something completely wrong with what I am doing, or is there some other weird interaction going on that someone has seen before? Regards, mjh -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
