第三部分結(jié)構(gòu)知識(shí)usb20及usb11相關(guān)errata

1、張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Errata for “USB Revision 2.0 April 27, 2000” as of 12/7/2000Check thewebsite for the latest errata.Chapter 5Reversed Values in Transaction Overhead Tables:Background: The tables in chapter 5 showing high-speed transaction overheads have typographical errors wh

2、ere the interpacket gap and minimum bus turnaround time values were reversed. No functional impact.Change: p. 43, table 5-3 & p. 45, table 5-5 and p. 51, table 5-8: change “8 bit interpacket gap, 88 bit min bus” to “88 bit interpacket gap, 8 bit min bus”.Table 5-3. High-speed Control Transfer Li

3、mits1張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開Protocol Overhead(Based on 480 Mb/s and 88 bit interpacket gap, 88 bit min bus(173 bytes)turnaround, 32 bit sync, 8 bit EOP: (9x4 SYNC bytes,9 PID bytes, 6 EP/ADDR+CRC,6 CRC16, 8 Setup data, 9x(1+11) byte interpacket delay (EOP, etc.)Data PayloadMax Bandwidth (bytes/second)Microframe

4、 Bandwidth per TransferMax TransfersBytes RemainingBytes/ Microframe Useful Data13440002%432%4215084413440002%42662%41793281649920003%391296243292160003%36120115264158720003%311531984Max600000007500張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Table 5-8. High-speed Interrupt Transaction Limits2張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開

5、Protocol Overhead(Based on 480 Mb/s and 88 bit interpacket gap, 88 bit min bus turnaround, 32 bit sync, 8 bit EOP: (3x4 SYNC bytes, 3 PID bytes, 2 EP/ADDR+CRC bytes, 2 CRC16 and a 3x(1+11) byte interpacket delay(EOP, etc.)Data PayloadMax Bandwidth (bytes/second)Microframe Bandwidth per TransferMax T

6、ransfersBytes RemainingBytes/ Microframe Useful Data110640001%133521%13133262440640001%1277508876160001%1193952%10545168032220160001%8618275264322560002%6334032128409600002%401805120256491520004%24366144512532480008%13129665610244915200014%61026614420484915200028%31191614430724915200042%212466144Max

7、600000007500張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Table5-5. High-speed Isochronous Transaction Limits3張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開Protocol Overhead(Based on 480 Mb/s and 88 bit interpacket gap, 88 bit min bus turnaround, 32 bit sync, 8 bit EOP: (2x4 SYNC bytes, 2 PID bytes, 2 EP/ADDR+addr+CRC5, 2 CRC16, and a 2x(1

8、+11) byte interpacket delay (EOP, etc.)Data PayloadMax Bandwidth (bytes/second)Microframe Bandwidth per TransferMax TransfersBytes RemainingBytes/ MicroFrame Useful Data115360001%192121%18720374456960001%178247128104320001%16321304%273920001%10710342464373760001%73544672128460800002%4530576025651200

9、0004%251506400512532480007%13350665610245734400014%766716820484915200028%31242614430724915200041%212806144Max600000007500張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Chapter 7Issue with Test_SE0_NAK Behavior:Background: While in test mode Test_SE0_NAK, upstream facing ports “must respond to any IN token

10、packet with a NAK handshake (only if the packet CRC is determined to be correct) within the normal device response time.” The question has been raised as to the meaning of “any IN token” and whether a device must NAK even if the packet is not directed to the device or directed to any endpoint on tha

11、t device. If it must, a device placed in this test mode will NAK even when an IN token is directed to another devices, such as a mouse or keyboard, resulting in possible problems for other devices connected to the bus during compliance testing. At this point, there are probably implementations that

12、interpret the spec both ways, so this erratum expands the spec to allow either interpretation. This will have to be dealt with in compliance testing. There will be no impact on non-test-mode operation.Change: p. 169, section 7.1.20, 1st bullet, 3rd sentence: Change complete sentence to: “In addition

13、, while in this mode, upstream facing ports (and only upstream facing ports) must respond to any IN token packet directed to the device (with an endpoint number supported by the device), and optionally to any IN token packet which is not directed to the device or optionally with any endpoint number,

14、 with a NAK handshake (only if the packet CRC is determined to be correct) within the normal device response time. Note: This means that the host should send test packets to a device under test with the devices current address and endpoint number zero to ensure that the device will respond.”7.1.20Te

15、st Mode SupportTo facilitate compliance testing, host controllers, hubs, and high-speed capable functions must support the following test modes:·Test mode Test_SE0_NAK: Upon command, a ports transceiver must enter the high- speed receive mode and remain in that mode until the exit action is tak

16、en. This enables the testing of output impedance, low level output voltage, and loading characteristics. In addition, while in this mode, upstream facing ports (and only upstream facing ports) must respond to any IN token packet with a NAK handshake (only if the packet CRC is determined to be correc

17、t) within the normal allowed device response time. In addition, while in this mode, upstream facing ports (and only upstream facing ports) must respond to any IN token packet directed to the device (with an endpoint number supported by the device), and optionally to any IN token packet which is not

18、directed to the device or optionally with any endpoint number, with a NAK handshake (only if the packet CRC is determined to be correct) within the normal device response time. Note: This means that the host should send test packets to a device under test with the devices current address and endpoin

19、t number zero to ensure that the device will respond. This enables testing of the device squelch level circuitry and, additionally, provides a general purpose stimulus/response test for basic functional testing.4張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Issue with Test_Force_Enable Behavior

20、:Background: The question has been raised as to the meaning of the language that says “the disconnect bit can be polled while varying the loading on the port, allowing the disconnect detection threshold voltage to be measured.” Some implementations have allowed the port to exit the test mode and ret

21、urn to the disconnected port state when the disconnect threshold is exceeded. Others have let the port stay in the test mode and allowed the bit to be “l(fā)ive”. This erratum allows either behavior. There will be no impact on non-test-mode operation.Change: p. 170, section 7.1.20, bullet on Test_Force_

22、Enable: Add sentence at end of paragraph, “Disconnect detection is optionally allowed to exit test_mode and return the port to the disconnected port state.”·Test mode Test_Force_Enable: Upon command, downstream facing hub ports (and only downstream facing hub ports) must be enabled in high-spee

23、d mode, even if there is no device attached. Packets arriving at the hubs upstream facing port must be repeated on the port which is in this test mode. This enables testing of the hubs disconnect detection; the disconnect detect bit can be polled while varying the loading on the port, allowing the d

24、isconnect detection threshold voltage to be measured. Disconnect detection is optionally allowed to exit test_mode and return the port to the disconnected port state.Issue with Test_Packet behavior:Background: The question has been raised as to the minimum inter-packet gap allowed for an upstream fa

25、cing port in test mode Test_Packet. The spec states that “The inter-packet timing must be no less than the minimum allowable inter-packet gap as defined in Section 7.1.18 and no greater than 125us.” Unfortunately, an upstream facing port never sends back-to-back packets, so this parameter is actuall

26、y not defined. Since an upstream facing port may send a packet in response to an incoming packet after a minimum of 8 bit times, some designers have interpreted this to mean the minimum inter-packet gap in the test mode should be 8 bit times. This erratum allows this interpretation. It will meet the

27、 needs of compliance testing, and there will be no impact on non-test-mode operation.Change: p. 170, section 7.1.20, bullet on Test_Packet: Add sentence at end of paragraph, “For an upstream facing port, the inter-packet timing must be no less than 8 bit times.”·Test mode Test_Packet: Upon comm

28、and, a port must repetitively transmit the following test packet until the exit action is taken. This enables the testing of rise and fall times, eye patterns, jitter, and any other dynamic waveform specifications.The test packet is made up by concatenating the following strings. (Note: For J/K NRZI

29、 data, and for NRZ data, the bit on the left is the first one transmitted. “S” indicates that a bitstuff occurs, which inserts an “extra” NRZI data bit. “* N” is used to indicate N occurrences of a string of bits or symbols.)5張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的· A port in Test_P

30、acket mode must send this packet repetitively. The inter-packet timing must be no less than the minimum allowable inter-packet gap as defined in Section 7.1.18 and no greater than 125 µs. For an upstream facing port, the inter-packet timing must be no lessthan 8 bit times.Issue with TDR Loading

31、 Specification:Background: On page 144, Section 7.1.6.2, 4th paragraph, there is a sentence which reads “No single excursion, however, may exceed the Through limits for more than twice the TDR rise time (400 ps).” This is confusing, since the TDR risetime is required to be 400 ps, not 200 ps. This e

32、rratum clarifies the language. There is no negative impact caused by this clarification.Change: Change the sentence to read “No single excursion, however, may exceed the Through limits for more than twice the TDR rise time (twice the 400 ps risetime is 800 ps).”No single excursion, however, may exce

33、ed the Through limits for more than twice the TDR rise time (twice the 400 ps risetime is 800 ps).No single excursion, however, may exceed the Through limits for more than twice the TDR rise time (400 ps).6張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開NRZI Symbols (Fields)NRZ Bit StringsNumber of NRZ BitsKJ * 15, KK (SYNC)00000000 *

34、3, 0000000132KKJKJKKK (DATA0 PID)110000118JKJKJKJK * 900000000 * 972JJKKJJKK * 801010101 * 864JJJJKKKK * 801110111 * 864JJJJJJJKKKKKKK * 80, 111111S *15, 11111197JJJJJJJK * 8S, 111111S, 0111111S * 755JKKKKKKK * 10, JK00111111, S0111111 * 9, S072JJJKKKJJKKKKJKKK (CRC16)011011010111001116JJJJJJJJ (EOP

35、)011111118張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Chapter 8Issue with Some PING STALL Response Omissions:Background: The PING protocol state machines and “railroad diagrams” show (correctly) that STALL is an allowed response to PING. However, two sentences in the spec do not explicitly mention STALL

36、. This change should cause no functional impact since the more explicit and detailed figures show the full set of allowed responses. Any potential impact is limited to bulk OUT and control endpoints in high-speed devices.Change: p. 217, section 8.5.1, 4th paragraph, last sentence: change “ a NAK or

37、an ACK handshake.” to “. a NAK, STALL or an ACK handshake.”The host controller queries the high-speed device endpoint with a PING special token. The PING special token packet is a normal token packet as shown in Figure 8-5. The endpoint either responds to the PING with a NAK, STALL, or an ACK handsh

38、ake.Change: p. 219, section 8.5.1.1, 3rd paragraph, change “. the allowed ACK, NAK or an NYET handshakes for the PING mechanism.” to “. the allowed ACK, NAK, STALL or an NYET handshakes for the PING mechanism.”Figure 8-27 shows the host controller state machine for the interactions and transitions b

39、etween PING and OUT/DATA tokens and the allowed ACK, NAK, STALL, or an NYET handshakes for the PING mechanism.Clarifying PING Related OUT NAK Responses:Background: The PING protocol tries to limit NAK responses to OUT transactions. However, a description in the spec suggests that NAK responses to PI

40、NG transactions are unusual, (which it not true). This change should cause no functional impact since the other descriptions of PING more clearly identify that PING can be NAKd “forever”. Any potential impact is limited to bulk OUT and control endpoints in high-speed devices.Change: p. 218, section

41、8.5.1.1, 2nd paragraph, 1st sentence: change “A NAK response is expected to be an unusual occurrence.” to “A NAK response to an OUT is expected to be an unusual occurrence.”p. 218, section 8.5.1.1, 2nd paragraph, 3rd sentence: change “allowed to NAK” to “ allowed to NAK an OUT”A NAK response to an O

42、UT is expected to be an unusual occurrence. A high-speed bulk/controlendpoint must specify itsum NAK rate in its endpoint descriptor. The endpoint isallowed to NAK an OUT at most one time each bInterval period. A NAK suggests that the endpoint responded to a previous OUT or PING with an inappropriat

43、e handshake, or that the endpoint transitioned into a state where it (temporarily) could not accept data. An endpoint can use a bInterval of zero to indicate that it never NAKs. An endpoint must always be able to accept a PING from the host, even if it never NAKs.7張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%

44、拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Incorrect Figure 8-27 (Host High-speed Bulk OUT/Control Ping State Machine):Background: The Host High-speed Bulk OUT/Control Ping State Machine figure was incorrectly cut and pasted from the draft specification (where it was correct). The current (incorrect) figure is a total duplica

45、te of figure 8-32. Any potential impact is limited to bulk OUT and control endpoints in high-speed devices.Change:p. 218: Replace incorrect Figure 8-27 with below:Figure 8-27. Host High-speed Bulk OUT/Control Ping State Machine8張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開(HSU2.PID /= STALL and HSU2.PID /= NAK andHSU2.PID /= ACK and

46、BCI_error1Wait_resp1HSU2.PID /= NYET) orWait_for_packet(HSU2.timeoutIncError;ErrorCount >= 3HSU2, ITG);RespondHC(Do_halt);Packet_ready(HSU2)ErrorCount < 3RespondHC(Do_ping);Issue_packet(HSD1, datax);&HSU2.PID = NYETRespondHC(Do_next_ping);not HC_cmd.setup andDo_data1not HC_cmd.pingIssue_pa

47、cket(HSU2.PID = STALLHSD1, tokenOUT);RespondHC(Do_halt);HC_cmd.setupHSU2.PID = NAKIssue_packet(HSD1, tokensetup);RespondHC(Do_ping);HSU2.PID = ACKRespondHC(Do_next_cmd);Do_token1HSU2.PID = ACK RespondHC(Do_OUT);HC_cmd.ping andHSU2.PID = NAKnot HC_cmd.setupRespondHC(Do_same_cmd);Issue_packet(HSD1, pi

48、ng);Ping_respWait_for_packet(HSU2.PID = STALLHSU2, ITG);RespondHC(Do_halt);Packet_ready(HSU2)&ErrorCount >= 3 RespondHC(Do_halt);(HSU2.PID /= NAK and HSU2.PID /= ACK andHSU2.PID /= STALL) orP_errErrorCount < 3HSU2.timeoutIncError;RespondHC(Do_same_cmd);HC_HS_BCONot allowed for control setu

49、p transac ion張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的，有問必答）Clarifying Figure Title for Figure 8-31 & 8-32:Background: The titles on figures 8-31 and 8-32 are misleading. The current titles suggest that the figure is uniformly applicable for all speeds, bulk/control/interrupt OUT transactions, (which i

50、s not true). No functional impact.Change: p.222, figure 8-31: caption should be “FS Bulk, FS/LS Control, or HS/FS/LS Interrupt OUT Transaction Host State Machine”Wait_resp Wait_for_packet( HSU2, ITG);BCI_errorIncError;&Issue_packet(HSD1, datax);ErrorCount >= 3RespondHC(Do_halt);Do_datanot HC_

51、cmd.setupIssue_packet( HSD1, tokenOUT);HSU2.PID = NAKRespondHC(Do_same_cmd);Do_tokenFigure 8-31. FS Bulk, FS/LS/ Control, or HS/FS/LS Interrupt/ OUT Transaction Host State Machine9張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開HC_Do_BCINTONot allowed for control setup transactionHSU2.PID = ACKRespondHC(Do_next_cmd);HC_cmd.setup Issue_

52、packet(HSD1, tokensetup);HSU2.PID = STALLRespondHC(Do_halt);ErrorCount < 3 RespondHC(Do_same_cmd);Packet_ready(HSU2)(HSU2.PID /= STALL and HSU2.PID /= NAK and HSU2.PID /= ACK) orHSU2.timeout張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Change: p. 223, figure 8-32: caption should be “FS Bulk, FS/LS Cont

53、rol, or HS/FS/LS Interrupt OUT Transaction Device State Machine”.&HSD2.x = device.ep(token.endpt).toggle and HSD2.CRC16 = ok and device.ep(token.endpt).space_availDopktDev_accept_data;&Dchkpkt2Dev_wait_OdataWait_for_packet( HSD2, ITG);Figure 8-32. FS Bulk, /FS/LS Control, /or HS/FS/LS Interr

54、upt OUT Transaction Device State Machine10張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開Dev_Do_BCINTO(HSD2.PID = datax and HSD2.CRC16 = bad) orHSD2.PID /= datax or HSD2.timeoutPacket_ready(HSD2)device.ep(token.endpt).ep_trouble Issue_packet(HSU1, STALL);HSD2.x = device.ep(token.endpt).toggle and HSD2.CRC16 = ok andnot device.ep(token

55、.endpt).space_avail Issue_packet(HSU1, NAK);token.PID = tokenOUT and HSD2.PID = dataxIssue_packet(HSU1, ACK);token.PID = tokenSETUP and HSD2.PID = dataxHSD2.x /=device.ep(token.endpt).toggle and HSD2.CRC16 = ok(not HSD2.x) and HSD2.CRC16 = ok anddevice.ep(token.endpt).space_avail Dev_accept_data;HSD2.x ornot device.ep(token.endpt).space_avail張飛實(shí)戰(zhàn)電子：點(diǎn)擊打開，有問必答）（勿擾100%拒絕水貼，10名瘋狂工程師運(yùn)營(yíng)的Clarifying No Data PID Sequencing for Interrupt:Background: Typog