If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The 57 an error number used by BurnInTest, in this case there was an error trying to send data to the COM port, the number of bytes transferred didn't match the number of bytes requested to be sent).
The 0 is supposed to be an error number from a Windows API call, ClearCommError, and normally this would be resolved to a more specific error (buffer overrun, parity error etc) however in this case it hasn't returned a useful value so the raw values were logged.
The 57 an error number used by BurnInTest, in this case there was an error trying to send data to the COM port, the number of bytes transferred didn't match the number of bytes requested to be sent).
The 0 is supposed to be an error number from a Windows API call, ClearCommError, and normally this would be resolved to a more specific error (buffer overrun, parity error etc) however in this case it hasn't returned a useful value so the raw values were logged.
It errored out while sending data to the serial port.
Maybe the port is locked, broken, missing a device driver or flow control pins set incorrectly (blocking sending).
Comment