Can't debug serial comm's on COM1:

[Andy]

I have a program running on an iPAQ 2210. It communicates successfully
via
COM1 on the iPAQ and COM1 on the PC to Hyperterminal, provided I start
it from VS with ctrl-F5 (Start without debugging).

If I run the debugger (F5), the debug connection drops out and the
program
terminates whenever I send data from the iPAQ to the PC.

Data goes from the PC to the iPAQ without problems.

ActiveSync is running over USB. In the "Connection Settings" dialog,
the COM
port option is not enabled.

It's as though the debugger or ActiveSync are trying to use COM1 even
when they are configured to use USB.

Can anyone shed light on this problem.

 

[Ginny Caughey [MVP]]

Andy,

I think it's likely that there is contention over the com port, although I
don't really know. I have debugged serial communications using a device
connected via wireless, but it's still hit or miss since a lot what goes on
in serial communications is time sensitive. I found using a log file to be
more useful for serial communications (and also for multithreaded apps) than
stepping through the debugger, so perhaps this would work for you too.

 

[Dick Grier]

Hi,

Is your device cradled? You cannot use the USB and serial ports
simultaneously in this case, I think. If your PPC has a "serial/USB 'Y'
cable" then, you might be able to do it. Otherwise, I'd suggest that you
connect to the PPC using either a wired or wireless connection for
debugging. Personally, I use a wireless (802.11b) card.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.