Doing so, these two tests led us to the conclusion that since both the cable operates properly on GNU/Linux and the board operates properly using the other cable, that the issue we had was the automatically installed Windows 10 drivers. The UC232A was brand new so we tested that it works on a GNU/Linux machine, which turned out to be OK. The data on the screen was consistent and the ghost was banished. We played around with the configuration parameters, hoping that it was an issue like having the need to add large transmit delay but it did not change anything, the communication with the board was unstable.Īfterwards, we switched to another cable, of a different company, and everything worked as expected. Some times keystrokes did not appear on screen, in other times results would not appear correctly (they could be truncated or mixed with other data) and in general, the system acted like it was possessed by a ghost. We noticed that something was wrong with the process as the terminal would not operate consistently.
USB VID_0557&PID_2008&REV_0300 SERIAL
Our serial port configuration was the following: The software we used was TeraTerm on a 64bit Windows 10 without installing custom drivers. Recently we started using the UC232A USB-to-Serial Converter to connect to a board.
23 November 2016 in Windows tagged ATEN / Converter / Drivers / serial / UC232A / usb / Windows 10 by Tux