數(shù)據(jù)記錄儀畢業(yè)設(shè)計(jì)開題報(bào)告和外文翻譯(編輯修改稿)

　

【文章內(nèi)容簡(jiǎn)介】 do so without need of host intervention. is returned by a function in response to an IN token or after the data phase 9 of an OUT or in response to a PING transaction. STALL indicates that a function is unable to transmit or receive data, or that a control pipe request is not supported. The state of a function after returning a STALL (for any endpoint except the default endpoint) is undefined. The host is not permitted to return a STALL under any condition. The STALL handshake is used by a device in one of two distinct occasions. The first case, known as “functional stall,” is when the Halt feature associated with the endpoint is set. A special case of the functional stall is the “manded stall.” Once a function?s endpoint is halted, the function must continue returning STALL until the condition causing the halt has been cleared through host intervention. Protocol stall is unique to control pipes. Protocol stall differs from functional stall in meaning and duration. A protocol STALL is returned during the Data or Status stage of a control transfer, and the STALL condition terminates at the beginning of the next control transfer (Setup). The remainder of this section refers to the general case of a functional stall. 2 Transaction Packet Sequences The packets that prise a transaction varies depending on the endpoint type. There are four endpoint types: bulk, control, interrupt, and isochronous. Batch transaction type were characterized by the error detection and retry way to ensure the host and function of data between the ponents of the ability to send errorfree. Flow control and hang in some conditions, the data phase handshake signals are replaced, resulting in two with no data transfer phase of the transaction. When the host is ready to receive a batch of data when it sends the input tag. Feature port through the return packet, or if unable to return data, NAK, or STALL handshake is returned as a response. NAK means the feature is temporarily unable to return data, and STALL be stopped permanently, said the port needs to USB system software intervention. If the host receives a legitimate data packets, then it uses ACK handshake to answer. If you receive data with the host detects an error, then it does not return handshake contracted out features. Control of transmission at least two transaction stages: the establishment and status. Transmission can be selectively controlled, including the establishment and status data between the stages of phase. In the establishment phase, the establishment of services for the features of the control port to transmit information. Establishment of issues in the format similar to the output, but the use of the building rather than the output of the PID. Building is always in the establishment of services relative to the use of data DATA0 PID. 10 Before the establishment of the functional ponents must accept the establishment of data and use ACK response, if the data is damaged, then discards the data and do not return to shake hands. Control the data transmission phase, if any, by more than one input or output transaction structure, pliance and batch send the same protocol rules. All the data phase of the transaction must have the same direction (that is, all input or all output). In the data phase, the amount of data to be sent, and its direction is specified in the establishment phase. If the amount of data exceeds the previously identified data packet size, the data in support of the largest packet size of the number of transactions to be sent (input or output). Any remaining data as a residual in the final transaction is sent. Control of the state of transmission phase is the last one operation sequence. State phase at a relatively earlier stage of the data to characterize the changes in flow direction, and always use the DATA1 PID. For example, if the data phase transaction constituted by the output, the state is a single input transaction. If the control sequence is no data transmission phase, then it is by the establishment phase and the subsequent transaction by the input stages, consisting of the state. Interrupt transactions may consist of IN or OUT transfers. Upon receipt of an IN token, a function may return data, NAK, or STALL. If the endpoint has no new interrupt information to return (., no interrupt is pending), the function returns a NAK handshake during the data phase. If the Halt feature is set for the interrupt endpoint, the function will return a STALL handshake. If an interrupt is pending, the function returns the interrupt information as a data packet. The host, in response to receipt of the data packet, issues either an ACK handshake if data was received errorfree or returns no handshake if the data packet was received corrupted. Such endpoints use multiple transactions in a microframe as defined in that section. Each transaction for a highbandwidth. When an endpoint is using the interrupt transfer mechanism for actual interrupt data, the data toggle protocol must be followed. This allows the function to know that the data has been received by the host and the event condition may be cleared. This “guaranteed” delivery of events allows the function to only send the interrupt information until it has been received by the host rather than having to send the interrupt data every time the function is polled and until the USB System Software clears the interrupt condition. 3 Data Toggle Synchronization and Retry The USB provides a mechanism to guarantee data sequence synchronization between data transmitter and receiver across multiple transactions. This mechanism provides a 11 means of guaranteeing that the handshake phase of a transaction was interpreted correctly by both the transmitter and receiver. Synchronization is achieved via use of the DATA0 and DATA1 PIDs and separate