![]() Source code has been added to the same git location. We could also simulate the issue with it (but we need to wait for a long time as it is slower). We have created a win32 command line tool with a similar functionality. Tested on Windows 10 Professional 64bit version: 1703-15063.540įollow-up in the Microsoft MSDN: BUG Report - COM-Port over CDC (usbser) Source code for testing can be found here: So I come to a conclusion that the issue seem to be very specific to Windows 10 + USB CDC while reading the data using SerialPort object.ĭid anybody already experience this behavior? I have monitored the packet in the USB PHY using USB protocol suite (Teledyne Lecroy Mercury T2) and I didn't find any transmission error that is observed by the application. The conditions for a full reception is either receiving 225792 bytes or a timeout of 1 second. If it isn't equal to the expected number (.which is 225792 / 256 = 882), then I create a log with the error data into data.txt in the same directory. To detect an error, I count the number of times I receive the 256 byte pattern (0x00, 0x01. Then the issue seem to be less frequent, but still I could see issue rarely though. Then with the reference from various blogs (especially from ), I switched to method SerialPort.BaseStream. With this I could easily simulate the issue with lots of errors while reading data. NET SerialPort object with the help of DataReceived event to receive the data from the COM port. Initially I developed the host application using. Each 256 bytes follow this pattern: 0x00, 0x01. When the μC receives char '0', it sends back the data size it will transmit (225792 for my example) as a UINT32 (4 bytes) - When the μC receives char '1', it sends back 225792 bytes by packet of 256 bytes each. ![]() Project based on LPCOpen example ' lpcopen_2_19_lpcxpresso_ngx_xplorer_4330'. To reproduce this issue, I created a sample project on LPCXpresso on the device side and a C# project on the host side. ![]() On the received pictures, I can see 3 different patterns: The issue is observed only on Windows 10 and not on Windows 7.įor reference the following are the pictures with the error in data read by the host application on a Windows 10 platform. This issue appears with our products while transmitting picture from a NXP's L PC4333JBD144 μC using a virtual COM port (i.e., USB CDC). Repeating the same if anyone has already experienced this and could help me to an extent. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |