Transfer Errors Sample Clauses

Transfer Errors. There are several types of transfer errors that must be handled by the HC. They fall into the following categories: • transmission • sequence • system Transmission errors are errors that occur in communicating information over the USB wires and manifest themselves as CRC errors, BITSTUFFING errors, DEVICENOTRESPONDING errors. Sequence errors occur when the number of data bytes received does not match the number of bytes expected from an endpoint. System errors occur when the Host Controller has a problem resulting from the HC’s system environment that cannot otherwise be attributed to USB. 4.3.1.3.6.1 Transmission Errors For errors in this category, USB defines a policy that allows the transaction to be retried for up to three times before the transfer is failed and returned to the client. The Host Controller supports this policy with the ErrorCount field. This field is initialized to 0 by the Host Controller Driver when the General TD is queued. This field is updated after each transaction attempt. If there is no transmission error, the field is written to 0. If, however, there is a transmission error, the field is incremented. If the ErrorCount field reaches 2 (10b) and another transmission error occurs (the third error in a row), the TD is retired to the Done Queue and the endpoint is halted. Data toggle mismatches on input data are counted as transmission errors. The cause of a data toggle mismatch is either failure of the endpoint to receive an ACK or a broken device. Data received when the data toggle mismatches is discarded and never written to host memory. An error in the PID check field is counted as a transmission error and is reported with a ConditionCode of PIDCHECKFAILURE. 4.3.1.3.6.2 Sequence Errors Sequence errors occur only on reads from an endpoint to the Host Controller (IN). Sequence errors are not checked unless the data packet is received without a transmission error. There are two types of sequence errors: data overrun and data underrun. When either of these error conditions is encountered, the ConditionCode field is set accordingly, the General TD is retired, and the endpoint is halted. A data overrun error occurs when the number of bytes received from an endpoint exceeds either Maximum Packet Size or the number of bytes remaining in a General TD’s buffer. In the case of an overrun condition, the Host Controller writes to memory all of the data received up to the point where the data overrun condition was created. When the General TD...

Transfer Errors. If we do not properly complete a Transfer or Payment on time or we made a Transfer or Payment in an amount less than you requested, our liability is limited to any related late fees or finance charges that you reasonably incur as a result, provided that, your account with the payee was otherwise current and in good standing. • Cancellation Errors. If we fail to cancel a Transfer according to your cancellation instructions or if we make a Transfer in an amount in excess of that you requested, our liability is limited to a refund of the amount erroneously paid, plus interest thereon lost as a result for the period beginning with the date on which the funds associated with such Transfer are withdrawn from your account to the date of such refund. However, in no event will this interest period exceed 60 days. • Interest. If we become liable to you for interest under this Services Agreement or other applicable law, such interest shall be calculated based upon the average Federal Funds Rate at the Federal Reserve Bank in the Federal Reserved District in which we are headquartered for each day interest is due, computed on the basis of a 360-day year.