Announcement

**Ian (PassMark)** · Mar-23-2006, 05:59 AM

"Device transceiver errors" are triggered when the USB transceiver on the USB 2.0 loopback plug detects what it considers to be an error. These are events at a low level that may lead to the packet being retransmitted, or they may not. They do not represent data errors at the application level. These errors are normally not visible to the user, but are displayed to help identify potential problems, for example, poor quality cables, cables that are too long, or system internals with insufficient electrical shielding with high electrical interference on the bus. Errors that may cause a device transceiver error are:
o Bad PID
o CRC error
o Bit stuff error
o Extra bits in a packet
o Full Speed EOP ending on K
o Loss of high-speed valid before EOP (truncated packet)
o Overflow (host clock running too fast or device clock running too slow)
o Token larger than 3 bytes
It should be noted that device transceiver errors are not an indication that the USB port does not comply with the USB Specification.

In many cases they are not errors as such, however we report them as high levels like you are seeing may warrant further investigation. A typical reason for this is poor quality cables, internal as well as external. It is possible that another USB device on the bus (like a mouse) could trigger the USB chip we use to flag an error.

I would repeat the test without anything else on the bus, and add devices incrementally to determine the difference.

It should be noted that unless there are "Verification errors" as well, a "device transceiver error" should not be considered serious - but rather just that as an indication that you might like to consider further investigation - like changing cables or using one of the (really expensive) analyzers.

Best regards,
Ian

Announcement

USB 2.0 Loopback Plug transceiver errors

USB 2.0 Loopback Plug transceiver errors

Comment