Virtual COM Communications Issue
-
Sunday, March 03, 2013 1:37 AMI'm working on a Communications Device Class (CDC) driver for an embedded device. The COM port settings are 115200, 8-bit, no parity, 1 stop bit, no flow control. Our PC application (32-bit, Windows 7, .NET 2.0) communicates with the target device through a virtual COM port, which on the target device can connect to either a FTDI (USB-to-SCI bridge) chip or the integrated USB peripheral in the microcontroller, depending on which port is selected by the application.
Both virtual COM ports work without any problems using Realterm. However, while our desktop application works using the virtual COM port connected via the FTDI chip, it hangs when attempting to use the virtual COM connected via the microcontroller's integrated USB peripheral.
When connected via the virtual COM port using the integrated USB, the application consistently hangs on the second call to `SerialPort.Write(...)`. Using Serial Monitor from HHD Software I can see that the data is transmitted on the first call to `SerialPort.Write(...)`. However, that data is never received by the target device.
It's odd because the only time I have seen similar problems on previous projects was when the flow control settings on each side of the bus were mismatched. Any ideas or suggestions would be appreciated. Thanks.
All Replies
-
Sunday, March 03, 2013 1:10 PM
Since this is a peer-to-peer users discussion forum I doubt you will encounter very many who are well versed about application development.
Suggest you go to one of the Microsoft Developer Network (MSDN) forums and post there: http://msdn.microsoft.com/en-US
or http://social.msdn.microsoft.com/Forums/en-US/categories
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked As Answer by Tracy CaiMicrosoft Contingent Staff, Moderator Monday, March 04, 2013 2:25 AM
-
Sunday, March 03, 2013 7:16 PMThanks, Rick. I've reposted this question to the MSDN forum. Is there a way to delete or close this post?

