We have seen this behavior in very very fews instances, and unfortunately we have not been able to figure out the root cause of the problem. We believe it to be some sort of an internal Windows driver issue with some specific USB Controller chips maybe.
Note that we don’t really supply a driver, and the “INF” windows file simply identifies the hardware as a generic USB CDC device (aka Virtual COM port). Your results are very interesting to us because you are running it within a VM on the host machine and you indicate it works inside the VM but not on the host, which make us believe even more it’s some sort of an internal driver issue. We are trying to figure out if there is a “work around” we can implement within the firmware of the board itself to compensate for what happens, but unfortunately as we don’t know what actually causes it, we have had a hard time coming up with any kind of patch on our side to compensate for it.
Users browsing this forum: Google [Bot] and 3 guests