RE: Can't use Palm device after emulator?
The emulator can be configured to use one of your PC's serial ports as the serial port on the emulated Palm. If your cradle and real device are plugged into the same port while the emulator is still running you'll get that conflict. To solve this problem you can close the emulator before hotsyncing or debugging on the real device. Alternately, you can configure the emulator to not use a serial port at all by right-clicking the emulator, choosing Properties and changing Serial Port to None. If the emulator is configured to a different port than the cradle it's still possible that you're getting a conflict. On a typically configured PC, COM1 and COM3 share an interrupt, and COM2 and COM4 also share an interrupt. If your cradle is on COM1 and your emulator is using COM3, the two probably can't share that interrupt. If this is the problem, the solutions are the same, or you can reconfigure the emulator to use a port which doesn't conflict with the cradle. Good luck! -Bob Whiteman -Original Message- From: DIAMOND JEFF To: Palm Developer Forum Sent: 8/3/2000 10:46 PM Subject: Can't use Palm device after emulator? I'm currently using the most uptodate versions of CodeWarrior and the Debugger (Update 1, patch, etc.) What I've found is that if I'm doing a programming session using POSE, nomatter how cleanly I exit the session, when I try to THEN try out my program on a real Palm, I get a Serial port is busy when it starts the download. The only thing that seems to remedy this is to reboot my computer. In fact, after I've done the POSE debugging, I can't even do a hotsync without the same effect. What's tying up the serial port? Thanks folks! - Jeff -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
RE: Can't use Palm device after emulator?
The emulator can be configured to use one of your PC's serial ports as the serial port on the emulated Palm. If your cradle and real device are plugged into the same port while the emulator is still running you'll get that conflict. To solve this problem you can close the emulator before hotsyncing or debugging on the real device. Alternately, you can configure the emulator to not use a serial port at all by right-clicking the emulator, choosing "Properties" and changing "Serial Port" to "None". If the emulator is configured to a different port than the cradle it's still possible that you're getting a conflict. On a typically configured PC, COM1 and COM3 share an interrupt, and COM2 and COM4 also share an interrupt. If your cradle is on COM1 and your emulator is using COM3, the two probably can't share that interrupt. If this is the problem, the solutions are the same, or you can reconfigure the emulator to use a port which doesn't conflict with the cradle. Good luck! -Bob Whiteman -Original Message- From: DIAMOND JEFF To: Palm Developer Forum Sent: 8/3/2000 10:46 PM Subject: Can't use Palm device after emulator? I'm currently using the most uptodate versions of CodeWarrior and the Debugger (Update 1, patch, etc.) What I've found is that if I'm doing a programming session using POSE, nomatter how cleanly I exit the session, when I try to THEN try out my program on a real Palm, I get a "Serial port is busy" when it starts the download. The only thing that seems to remedy this is to reboot my computer. In fact, after I've done the POSE debugging, I can't even do a hotsync without the same effect. What's tying up the serial port? Thanks folks! - Jeff -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
