USB Certification for Stellaris-based USB
Contents
1. 1 SPIRK 1CSDA_3 SPTX 5 SPIGLK 33V SPISEL O RSTn 2 33V E gt 2 ms 3 4 TeK ct 5 6750 7 8 9 10_RST HDROXS MH 4 STAG SWD 33v USB Device Ray 10K USB Host 11 4 PAooRx PBOUIRX HE gt 15 PALuorx PBI UITX H 0 PAXSSIOCLK PB22COSCL 57 St PAYSSIOFSS PBYI2COSDA 57 J PAWSSIORX b RTS s PASISSIOTX ppsiccro 27 RvBUS CTS Se 2 1 1 1 jH PB NML 1 52 n 61 IH PDO CANORX 0 0 PCI TMSISWDIO PDICANOTX 8 524 Pom PDYADCS Hi pcx tDorswo ppsvApct Hy TH PCS USBOEPEN vBus 14 PO6 USBOPFLT A EY 4 0 54 Peovapes uspopp 4188 6 HY PENADO USBODM 14 PEYADCI 3 USBORBIAS Re PE4 CCP3 2 Moscar n 0900 is it 33V 99 USB HOST gt e xosco 2 25 12 gt nour srt XOSCI 15 16 32 WARE RIOUT RIIN 27 4 pay 10 lt 9 R2IN 12 VERS Lae FBI 1200hm 100MHz 33V 33V kasei 1 2 __ o47uF GND2. x Header Header USB Power 7 Controller 3 3 gt 3 3V regulator 5V E USB Device uss Host Phoenix The microcontroller used is the Stellaris LM3S5732 which includes 128 Kbytes of Flash memory 64 Kbytes of SRAM and a USB 2 0 full speed host device controller in an LQFP64 package An 8 MHz crystal is used to drive an internal PLL to generate all the required clocks for the microcontroller The board uses 5 VDC power and a switch selects the power source which can be an external supply or the USB Device bus connector In addition to the USB port the Phoenix board includes an RS 232 transceiver and DBY female connector for a standard 115 kbps serial port The board also has a JTAG connector for programming and debug and a 2x5 header providing additional I O signals from the microcontroller USB Device Phoenix USB Device assemblies do not include specific components for USB Host The system application is a USB to RS 232 serial port bridge Most personal computers today do not have serial ports and so this bridge provides an easy way to add a serial port to a PC with an available USB port After installing the driver the bridge appears as USB serial port COMx with x as the COM port number assigned See
3. KAn KEAR AnKa NEE 30 Schema 36 39 Referentes olaaa a aa a ia 39 June 26 2009 3 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Introduction This application note describes the USB Implementers Forum USB IF certification process for a USB full speed device and a USB full speed embedded host system The Stellaris family of microcontrollers includes several parts with USB Device and USB Host capability This application note describes this process using the certification of the Stellaris LM3S5732 microcontroller as the example USB IF The Universal Serial Bus USB was initially created as a mechanism for connecting peripherals to personal computers but it has grown into other uses including applications in the embedded world For products to be USB compliant they must meet the USB Specification electrical and functionality requirements per the USB 2 0 standard published by USB IF The USB IF provides a USB Compliance Program to ensure a standard level of acceptability Products that pass the compliance program requirements are included in the USB Integrators List which is available only to member companies and includes products meeting the requirements for
4. 4 USB DEVICE arsi 5 USB Embedded 5 Product Submission Procedure for USB 6 Checklist COMPpPICIOMN 6 Online Registration A ea WO i i as 6 Testtab 5 2 ice bean aaea iae a aT ee tuna etd 6 Product Testing ig 6 USR Device Test 7 USB 2 0 Compliance Checklist Sample for Phoenix USB Test Board 14 Product Submission Procedure for USB Embedded 29 Checklist Completion ie ig ci eee eatin iced en a ne ee ee etd 29 Online REGISHALION 29 Test Lab Setup 6 itis Oh nels tal hn een A ea ae 29 Test niet ee ited doen eee ated a eee ee 29 USB Embedded Host Targeted Peripheral 115 30 USB Embedded Host Test
5. Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Conclusion The Stellaris family of ARM Cortex M3 microcontrollers includes a range of parts with USB 2 0 Full Speed Host and Device capabilities USB hardware features are complemented by comprehensive USB driver software available in StellarisWare Certifying a USB Device or USB Embedded Host board is straightforward when using USB certified Stellaris microcontrollers References Documents used in the generation of this application note include Stellaris LM3S5732 Microcontroller Data Sheet Publication Number DS LM3S5732 StellarisWare Driver Library User s Manual publication number SW DRL UG USB Compliance Checklist Peripherals Excluding Hubs Checklist Version 1 08 November 28 2001 USB Compliance Checklist Peripheral Silicon Excluding Hubs Checklist Version 1 08 December 18 2001 USB Compliance Checklist Systems Checklist Version 1 05 October 5 2001 Requirements and Recommendations for USB Products with Embedded Hosts and or Multiple Receptacles Revision 1 0 July 8 2004 USB IF Embedded Host Compliance Plan Revision 1 0 August 2006 June 26 2009 39 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Important Notice Texas Instruments Incorporated and its subsidiaries reserve the right to make correcti
6. 7 2 3 500mA less Does the device limit its inrush current either by using capacitors smaller than 10uF or by using soft start circuits such that no more than 10uF of capacitance is charged By currents higher than 100mA when the device is hot plugged By currents higher than the device s MaxPower at configuration or when the device transitions to its operating mode ves 7 1 2 If ferrite beads are used in the device s USB connection are they presenton yes no 0 7 1 6 only the Vgus and GND lines 9 2 6 1 If the device is self powered and does not operate any of its components yes no from bus power does it only signal an attach when both bus power and external power are available Oetaher 5 9001 5 26 2009 20 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 14 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripherals Excluding Hubs 6 Explanations This section should be used to explain any no answers or clarify answers on checklist items above Please key entries to the appropriate checklist question M7 no edge rate capacitors used 2 1 Low Speed devices not applicable device is full speed only 2 3 Tethered devices not applicable device is untethered 3 3 Remote wakeup remote wakeup not supported Octaher 5 9001 R June 26
7. A 100 VIN g u3 HDR 1X2 VBUS VIN 4 VIN VOUT 5 4 A VBUS GI 7 l VR a VIN VOUT 1 SPDT SLIDE RA GNI 023 i 47 2 T PQING33MASPQ GREEN_LED Li R14 4 mag D3 x j Texas Instruments TEXAS INSTRUMENTS oa wia asin pa son peters This document contains information proprietary to Luminary Micro Inc and shall not be used for engineering design procurement of manufacture in whole or in part without the express written permission of Luminary Micro Inc Copyright 2007 Luminary Micro Inc All rights reserved Amaldo Cruz Phoenix Serial2USB Module Host Amaldo Cruz DustDevil Voltage Regulator UART transceiver Sa
8. INFO Service Pack 3 0 INFO USBCommandVerifier dll ver 1 3 2 0 INFO TestServices dll ver 1 3 2 0 INFO StackSwitcher dll ver 1 3 2 0 DeviceDescriptorTest_DeviceConfigured Passed Number of Fails 0 Aborts 0 Warnings 0 INFO Now Starting Test Device Descriptor Test Configuration Index 0 INFO Device descriptor length 12 INFO Device descriptor type 1 INFO ajor version 2 INFO inor version 0 INFO Device supports different class spec on different interfaces 2 INFO Device class code indicates Communication Device INFO Device sub class 0 INFO Device protocol 0 INFO Device MaxPacketSize0 40 INFO Vendor information for VendorID 1 Luminary Micro Inc INFO Device ProductID 2 INFO Device BCD 100 INFO ENGLISH_US language string descriptor is Luminary Micro Inc INFO ENGLISH_US language string descriptor is Virtual COM Port INFO ENGLISH_US language string descriptor is 12345678 INFO umber of configurations device supports 1 INFO Stopping Test Device Descriptor Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 DeviceDescriptorTest_DeviceAddressed Passed INFO ow Starting Test Device Descriptor Test Configuration Index 0 INFO Device descriptor length 12 INFO Device descriptor type 1 INFO ajor version 2 INFO inor version 0 INFO Device supports different class spec on different interfaces 2 INFO Device class code indicates Com
9. 2009 21 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 15 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon LS12 Does the receiver accept an SEO between 670ns 1 76us long followed 7 1 13 2 by a J as an LS13 Does the receiver accept a packet whose first bit has been distorted by as yes _ 7 1 14 much as 25ns 7 1 14 7 1 9 LS14 Does the receiver accept a packet whose last bit has been lengthened by as yes much as 260ns dribble bit LS15 Is the receiver data jitter tolerance at least 141ns for consecutive yes _ 00 7 1 15 transitions LS16 Is the receiver jitter tolerance for paired transitions at least 184ns yes no 7 1 15 LS17 Is the device s turn around time between two and 6 5 low speed bit times or 7 1 18 7 5 bit times if the device has a fixed cable LS18 15 the time out period 16 18 low speed bit times 1 7 1 19 LS19 Is D between 2 7 and 3 6V and D between 0 0 and 0 3V when the bus is idle Note the low speed receiver jitter tolerances listed here do not apply to hosts and hubs Consult section 7 1 15 for host and hub jitter requirements 2 2 Full Speed Ports applicable to any USB port which can operate at 12Mb s FS1 With series termination resistors does the devi
10. A minimum of 1 0uF is recommended Low Speed Devices not applicable to full speed devices Does the device with its captive cable present a single ended capacitance pF on the D and D lines 2 2 Full Speed Devices not applicable to low speed devices Does the device pull up D Does the device s source impedance remain in the shaded areas of Figure 7 1 11 7 4 Is the device s signaling rate 12 000Mb s 25 even if the device uses 7 1 11 spread spectrum clocking 2 3 Tethered Devices not applicable to untethered devices Tethered devices are devices with a captive cable Does the captive cable have a series A plug 2 4 Untethered Devices not applicable to tethered devices Does the device pull up the appropriate data line with a 1 5kQ 5 resistor yes J no 0 7 1 5 attached to a voltage source between 3 0 and 3 6V or with a Thev nin source of at least 900Q Oetaher 5 9001 3 June 26 2009 16 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 10 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripherals Excluding Hubs Untethered devices are devices with a detachable cable MUTI Does the device have a series receptacle Does the device pull up D with a 1 5kQ 5 resistor attached to a voltage source between 3 0 and 3 6V MUT3_ Does the device s upstream port
11. The suffix of 0 or indicates the data PID used in the transaction TF1 Does the data stage always start with a datal PID yes 8 5 2 Are all the transactions of the data stage in the same direction Is there status stage s direction opposite that of the data stage Is the data packet used in the status stage zero bytes in length 4 Recommended Questions 4 1 Device Robustness 4 1 1 Bitstreams i n Does an agent ignore a truncated up to 90 first bit of the sync field yes without impacting the rest of the bitstream Is the state of the differential receiver ignored during single ended signaling Does the target reject bitstreams less than one bit time long without ing future transactions Does the target adjust to the difference in frequency and phase between _ incoming clock its internal clock yesi Is a bitstream which is not part of a packet with bit stuff error ignored by yes the target nored by the targ Is a packet with a corrupt PID PID check error ignored by the target yes Jno sd Is a token with a bad CRC ignored by the target yes noL lt RF4 Is a CRC error on a data packet recognized by the target Is the sync field recognized as valid even if the first two bits of it are 9 Only the last 3 bits actually need to be decoded Is a token whose address field doesn t match a
12. minimum 132 00 V us maximum 660 00 V us Falling Edge Rate 147 82 V us Equivalent risetime 17 86 ns minimum 132 00 V us maximum 660 00 V us Edge Rate Match 9 73 limit 10 June 26 2009 32 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 24 Phoenix USB Embedded Host Full Speed Signals Signal Data D 0 and common mode signak V Data Eye D 0 V 10 20 30 40 50 60 70 80 26 2009 33 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 25 Phoenix USB Test Board Embedded Host Low Speed Test Results Low Speed DS Hub Signal Quality Test Results for 745 LuminaryMicro_LM3S5732_rA_USBET_lsu For details on test setup methodology and performance criteria please consult the signal quality test description at the USB IF Compliance Program web page Required Tests Overall result pass Signal eye eye passes EOP width 1 33 us EOP width passes Measured signaling rate 1 4994 MHz signal rate passes Crossover voltage range 1 73 V to 1 81 V mean crossover 1 77 V first crossover at 1 75 V 21 other differential crossovers checked crossover voltages pass Consecutive jitter range 7 652 ns to 5 805 ns RMS jitter 3 928 ns Paired JK jitter range 0 883 ns to 1 945 ns RMS jitter 1 177 ns Paired KJ jitter range 2 259 ns to 2 254
13. r 2 2 1 12 a Endpoint descriptor raw MaxPacketSize 10 Endpoint descriptor interval a Endpoint descriptor length 7 Endpoint descriptor type 5 Endpoint Type Bulk Number 2 Direction Endpoint descriptor bmAttributes 2 Endpoint descriptor raw MaxPacketSize 40 Endpoint descriptor interval 0 Endpoint descriptor length 7 Endpoint descriptor type 5 Endpoint Type Bulk Number 3 Direction Endpoint descriptor bmAttributes 2 Endpoint descriptor raw MaxPacketSize 40 Endpoint descriptor interval 0 Stopping Test Endpoint Descriptor Test Number of Fails 0 Aborts 0 Warnings 0 IN OUT Configuration Index 0 EndpointDescriptorTest_DeviceAddressed Passed INFO Now Starting Test Endpoint Descriptor Test Configuration Index 0 INFO Testing Interface number 0 Alternate setting 0 INFO Endpoint descriptor length 7 INFO Endpoint descriptor type 5 INFO Endpoint Type Interrupt Number 1 Direction IN INFO Endpoint descriptor bmAttributes 3 INFO Endpoint descriptor raw MaxPacketSize 10 NFO Endpoint descriptor interval a NFO Endpoint descriptor length 7 NFO Endpoint descriptor type 5 INFO Endpoint Type Bulk Number 2 Direction IN INFO Endpoint descriptor bmAttributes 2 INFO Endpoint descriptor raw MaxPacketSize 40 INFO Endpoint descriptor interval 0 INFO Endpoint descriptor length 7 INFO End
14. Embedded Host Systems USB 2 0 Compliance Checklist Sample for Phoenix USB Test Board The following section contains the specific pages for the USB 2 0 Compliance Checklist as it was completed for the Phoenix USB test board see Figure 8 on page 15 through Figure 21 on page 28 June 26 2009 14 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 8 Phoenix USB Test Board Compliance Checklist Sample USB 2 0 Compliance Checklist Peripherals Excluding Hubs 1 Introduction This checklist helps designers of USB peripherals to assess their products compliance with the Universal Serial Bus Specification Revision 2 0 Unless explicitly stated otherwise all references to the USB Specification refer to Revision 2 0 This checklist is also used in part to qualify a USB peripheral for the USB IF Integrators List This document and other USB compliance tools including USB Check are available in the developers section of the USB IF s website http www usb org developers The compliance checklists are updated periodically so developers should check for updates when starting new projects Section 5 Recommended Questions contains questions covering areas not required by the USB Specification Answering these questions is not a requirement for compliance with the Specification or acceptance to the Integrators List However vendors are strongly encouraged to take these q
15. Enum amp Op General Goldtree Op Hot Detach amp Reattach Cold Boot Target Device Enumeration Target Device Operation Hot Attach amp Reattach Power Cycle OTG DUT Enumerate 5 Hubs Target Peripheral List Mice Logitech Kensinton Microsoft Tested June 26 2009 31 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 23 Phoenix USB Test Board Embedded Host Full Speed Test Results continued Full DS Hub Signal Quality Test Results for 745 LuminaryMicro_LM3S5732_rA_USBET_fsu For details on test setup methodology and performance criteria please consult the signal quality test description at the USB IF Compliance Program web page Required Tests Overall result pass Signal eye eye passes EOP width 166 85 ns EOP width passes Measured signaling rate 12 0009 MHz signal rate passes Crossover voltage range 1 57 V to 1 90 V mean crossover 1 74 V first crossover at 1 61 V 17 other differential crossovers checked crossover voltages pass Consecutive jitter range 376 136 ps to 465 019 ps RMS jitter 259 113 ps Paired JK jitter range 288 141 ps to 457 097 ps RMS jitter 254 084 ps Paired KJ jitter range 99 747 ps to 225 611 ps RMS jitter 127 087 ps jitter passes Additional Information Rising Edge Rate 133 45 V us Equivalent risetime 19 78 ns
16. P7 Is the data payload of a low speed packet limited to a maximum of 8 bytes yesf no J 8 6 5 LES E the PRE packet 16 bits long rr t 865 __ Does the PRE packet consist of only a SYNC followed by a PID yesi no _ 8 6 5 3 4 Transactions Transactions are sets of packets used for unidirectional data transfer Transactions are discussed in detail in section 8 5 of the USB Specification Does an isochronous endpoint synthesize frame markers to replace SOFs 5 10 6 which may be lost due to bus error Do handshakes conform to order of precedence described in section 8 4 5 yes 8 4 5 TA3 Does the generated packet comply with the flows show in Figure 8 9 8 11 yes 8 5 8 13 or 8 14 as appropriate 8 6 5 Is an unsuccessful NAKed or timed out in non token phase transaction retried Does the retried transaction use the same data PID as the original transaction 3 5 Transfers Transfers are data structures used by control endpoints Each transfer is made up of setup and status stages possibly with a data stage Transfers can be one of October 5 2001 June 26 2009 25 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 19 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon setup0 outl outO outl out0 inl
17. USB Embedded Host Table 1 Targeted Peripheral List for Phoenix USB Embedded Host Class Name Description Class Code Sub Class Code Protocol Specs Supported HID Supports USB mouse 03h Oth 02h FS LS Devices Tested Manufacturer Model Vendor lD Description Speed Logitech G5 laser mouse 46Dh C049h USB gaming mouse FS USB Embedded Host Test Results This section provides the Phoenix USB test board results for a USB Embedded Host starting with Figure 22 on page 31 through Figure 23 on page 32 Figure 24 on page 33 shows the Phoenix USB Embedded Host Full Speed Signals Figure 25 on page 34 shows the Phoenix USB Test Board Embedded Host Low Speed Test Results and Figure 26 on page 35 shows the Phoenix USB Embedded Host Low Speed Signals June 26 2009 30 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 22 Phoenix USB Test Board Embedded Host Full Speed Test Results MCCI USB IF Compliance Test Report Full Speed Host Compliance Test Checklist USB Silicon result notes Luminary Micro LM3S5732 Hardware result Downstream Connection A socket User Interface Hyperterminal Debug window Maximum Power result notes Power Source device powers on Signal Quality High notes n Host Downstream Port 1 el Interoperability Host Interoperability
18. applications and acknowledge and agree that they are solely responsible for all legal regulatory and safety related requirements concerning their products and any use of TI products in such safety critical applications notwithstanding any applications related information or support that may be provided by TI Further Buyers must fully indemnify and its representatives against any damages arising out of the use of products in such safety critical applications products are neither designed nor intended for use in military aerospace applications or environments unless the products are specifically designated by as military grade or enhanced plastic Only products designated by as military grade meet military specifications Buyers acknowledge and agree that any such use of TI products which has not designated as military grade is solely at the Buyer s risk and that they are solely responsible for compliance with all legal and regulatory requirements in connection with such use products are neither designed nor intended for use in automotive applications or environments unless the specific products are designated by as compliant with ISO TS 16949 requirements Buyers acknowledge and agree that if they use any non designated products in automotive applications will not be responsible for any failure to meet such requirements Following are URLs where you can obtain information on other Texas Instrume
19. device s pullup control between 1 0V and 4 0V If the device is bus powered or uses bus power to run any of its components yes Z 7 1 5 does it pull up the appropriate data line within 100ms of Vaus exceeding 4 01 7 1 7 3 EN ALTS LLTS 7 1 7 3 9 1 1 BLTS 7 1 7 4 7 1 7 4 7 1 7 5 TAT 7 1 7 3 9 1 1 1 7 9 Does the device complete its wakeup within 2015 Can the device function correctly with frame lengths between 995 and 1005us gt Does the device function correctly tier 6 when subjected to worst case hub bit skews and delay times 7 1 19 D19 Does the device drive no signals upstream on power up Does the combination of the device s pullup and the 15kQ 5 pulldown resistor at the upstream port yield a voltage between 2 7 and 3 6V when the bus is idle D2 Does the device complete SetAddress or a standard request with no data in yes no 7 3 2 less than 50ms 9 2 6 3 Oetaher 5 9001 June 26 2009 17 Application Note Figure 11 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripherals Excluding Hubs Does the device deliver the first and all subsequent data packets except for the last data packet for a standard request within 500ms 9 2 6 4 D23 Does the device deliver the last data packet for a standard request within 7 3 2 50ms 9 2 6 4 8 and 9 Does the device implement a default control endpoint 0 for all addresse
20. oe Ye GND FBZ Tm TOMA UCG 2R GND m O 47UF 10K ey y cs osn GND VBAT GND i GND 5 GND USB DEVICE WAD an Fat f 67068 8000 gt EN 9 4 3 0 1uF 0 01UF Enea a H VDDA I FA FORCEOFF A 18 bas cre C14 cis 2 HJH 1 I 113223 0 47UF 8 000 MHz 33V c17 18pF 18pF RIS o 1 0 n vBUS vout e 33v c28 c22 s u3 Bus 5 4 5 oos 3 VEN 1 330 B Gi k 1 3 USB Host Power_Jack 2 5mm bearer an lee GND m 4 7uF PQINSSMASPQ GREEN_LED es L___4 cu 3 3V i FB3 1200hm 100 MHz Texas Instruments Ki TEXAS INSTRUMENTS Two Wild Basin Suite 350 Austin TX 78748 This document contains information proprietary to Luminary Micro Inc and shall not be used for engineering design procurement of manufacture in whole or in part without the express written permission of Luminary Micro Inc Copyright 2007 Luminary Micro Inc All rights reserved Designer Drawing Tie Variar Amaldo Cruz Phoenix Serial2USB Module Device Drawn by Page Tile Amaldo Cruz DustDevil Voltage Regulator UART transceiver Approved Size Docu
21. setup0 inl inO inl inO l out setup0 inl Transactions in italics constitute the data stage The suffix of 0 or indicates the data PID used in the transaction TF1 Does the data stage always start with a datal PID yes 8 5 2 Are all the transactions of the data stage in the same direction Is there status stage s direction opposite that of the data stage Is the data packet used in the status stage zero bytes in length 4 Recommended Questions 4 1 Device Robustness 4 1 1 Bitstreams yesi n Does an agent ignore a truncated up to 90 first bit of the sync field 5 without impacting the rest of the bitstream Is the state of the differential receiver ignored during single ended yes no signaling Does the target reject bitstreams less than one bit time long without no i future transactions Does the target adjust to the difference in frequency and phase between yes incoming clock and its internal clock Is a bitstream which is not part of a packet with bit stuff error ignored by yes the target nored by the targ Is a packet with a corrupt PID PID check error ignored by the target yes Jno sd Is a token with a bad CRC ignored by the target yes noL lt RF4 Is a CRC error on a data packet recognized by the target Is the sync field recognized as valid even if the first two bits of it are 9 Only the last 3 bits actually need
22. to be decoded Is a token whose address field doesn t match any address in the device no ignored by the device Is a token whose endpoint field doesn t match any endpoint in the address yes ignored by the device nored nO October 5 2001 7 June 26 2009 26 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 20 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon by the device a ae Is a SETUP token to a unidirectional endpoint ignored by the device Is every endpoint capable of handling zero length data packets in its yes assigned directions Does an ISO endpoint use a zero length data packet if fresh frame data is not 307 available Is a packet whose length doesn t match the standard length for the packet ho a type rejected by target 4 1 4 Does the measurement of packet length take into account the possibility of yes jitter and hub repeater skews in the EOP Is a bitstream that does not constitute a valid packet rejected by the target 1 Are low speed packets received by full speed upstream ports ignored yes 11 8 6 5 Transactions Do all pipes in the device return to normal operation when the device no resumes from suspend Is a pa
23. 0 0 ns for consecutive 7 1 15 transitions FS18 Is the receiver jitter tolerance for paired transitions at least 12 0 ns 5 J 7 1 15 FS19 Is the device s turn around time between two and 6 5 full speed bit times or yesi 7 1 18 7 5 bit times if the device has a fixed cable FS20 Is the time out period 18 full speed bit times yes 7 1 19 October 5 2001 June 26 2009 22 Application Note Figure 16 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon Is D between 2 7 and 3 6V and D between 0 0 and 0 3V when the bus is idle 3 Signaling Protocol and Error Handling 3 1 Bitstreams Is the possibility of both D and D registering as NIB 1 during bus transitions accounted for 7 1 13 1 yes no Is the bitstream on the bus NRZI encoded E B5 Is bit stuffing performed on all data transmitted including CRCs prior to 7 1 9 NRZI encoding 8 3 5 Is bit stuffing performed even if the stuffed bit follows the last bit of a packet Is NRZI to NRZ decoding done before bit unstuffing yes J 7 1 9 Is bit unstuffing performed all received data including CRCs 8 3 5 Is bit unstuffing done before the bitstream is parsed yes nol 7 1 9 3 2 Fields A field is one of address 7 bit field 0 to 1023 byte field data CRC 16 bit field endpoint 4 b
24. Stopping Test SetConfiguration Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 SuspendResumeTest Passed NFO Now Starting Test Suspend Resume Test Configuration Index 0 NFO Suspended the parent port of the device INFO Stopping Test Suspend Resume Test Configuration Index 0 INFO NFO NFO Now Starting Test Remote Wakeup Test Configuration Index 0 The device does not support remote wakeup Stopping Test Remote Wakeup Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 June 26 2009 FO Now Starting Test Remote Wakeup Test Configuration Index 0 FO The device does not support remote wakeup FO Stopping Test Remote Wakeup Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 EnumerationTest Passed FO Now Starting Test Enumeration Test repeat 150 times FO Device speed is Full FO Stopping Test Enumeration Test repeat 150 times Number of Fails 0 Aborts 0 Warnings 0 Summary NFO Summary Log Counts Fails 0 Aborts 0 Warnings 0 USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems 11 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 6 Phoenix USB Test Board Full Speed Signal Quality Test Results Full Speed Signal Quality Test Results for 713 LuminaryM
25. USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Application Note Aa TEXAS INSTRUMENTS ANO1271 01 Copyright 2009 Texas Instruments Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Copyright Copyright 2009 Texas Instruments Inc All rights reserved Stellaris and StellarisWare are registered trademarks of Texas Instruments ARM and Thumb are registered trademarks and Cortex is a trademark of ARM Limited The USB IF Logos are trademarks of Universal Serial Bus Implementers Forum Inc Other names and brands may be claimed as the property of others Texas Instruments 108 Wild Basin Suite 350 Austin 78746 TEXAS 1 512 279 8800 Fax 1 512 279 8879 INSTRUMENTS http www luminarymicro com Cortex a a Intelligent Processors by ARM ARM ERY June 26 2009 2 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Table of Contents Introductio Mas Ba eae Ne Al alee ee Peta Real 4 eed dread e tas bated a tener 4 4 Block E A
26. USB certification Once a product is in the USB Integrators List a USB IF Trademark License Agreement must be submitted for licensing of the USB logo Information about the Compliance Program can be found at www usb org developers compliance Products can be tested for compliance by either submitting the product to a USB IF sponsored compliance workshop or by submitting the product to a USB IF approved independent test lab A list of approved labs is available at www usb org developers compliance labs For this application the product was submitted to MCCI Corporation www mcci com Phoenix USB Test Board The Phoenix USB test board was built as a platform for silicon certification and board level certification In order to certify silicon the board used to test the silicon must also be certified All USB IF requirements are the same for board and silicon certification with silicon certification requiring an additional checklist The Phoenix USB test board can be assembled as a USB Device peripheral or as a USB Embedded Host Block Diagram The block diagram for the Phoenix USB test board is shown in Figure 1 June 26 2009 4 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 1 Phoenix USB Test Board Block Diagram gt UARTO lt USB BUS UART1 SPI GPIO LM3S5732 2x5
27. ce s source impedance yes 7 1 1 1 remain in the shaded areas of Figure 7 3 Are data line rise times between 4 0 and 20ns when driving into a single ended 50pF load Are data line fall times between 4 0 and 20ns when driving into a single 7 1 2 ended 50 load Are the rise and fall times matched to within 10 for JK transitions 56 Is a SEO less than 14ns long ignored at all transitions in a bitstream J 7 14 Is a SEI less than 8ns long ignored at all transitions in a bitstream yes no_ If the device tracks the K gt low speed transition on its upstream yes 7 1 7 5 port at the end of resume does it correctly handle the low speed EOP FS10__ Is the transmission data rate between 11 97 and 12 03Mb s _ yes no J 7 1 11 Is the differential driver jitter for consecutive transitions less than 2 0ns Is the differential driver jitter for paired transitions less than 1 0ns FS13_ Is the EOP width between 160ns and 175 at the transmitter yes no 7 1 13 2 FS14 Does the device accept an SEO between 82ns and 250ns long followed by a yes 7 1 13 2 an EOP 7 1 14 FS15 Does the receiver accept a packet whose first bit has been distorted by as yes 7 1 14 much as 25ns FS16 Does the receiver accept a packet whose last bit has been lengthened by as yes no _ 7 1 14 much as 75ns 7 1 9 FS17 Is the receiver data jitter tolerance at least 2
28. cket which doesn t fit the current phase of a transaction rejected by the target Does the receipt of a token always start a new transaction and end a pending transaction Is a data packet with same PID as the previous data packet to an endpoint ae ignored other than ACKing the data packet RTAS Does a time out or error in any phase cause the transaction to be terminated yesY noL RTA6 Isa transaction alw ays started w itha token xesh noL e endpo int fal Pore arene subsequent transactions 9 4 1 5 Can consecutive packets in the same direction be handled provided there are two or more bit times of interpacket gap between each packet Transfers Does the receipt of a nonzero length data packet in the status stage cause the transfer to be terminated with an error indication October 5 2001 8 June 26 2009 27 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 21 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon 5 Explanations This section should be used to explain any no answers or clarify answers on checklist items above Please key entries to the appropriate checklist question Section 2 1 Low Speed Ports is non applicable USB Device only works in full s
29. cklist provides an assessment of product compliance Any problems at this stage must be resolved to ensure a successful compliance test Note that all USB connectors cables and USB silicon used in the design must be on the Integrators List otherwise a checklist must also be provided for any component not on the list Online Registration The product must be registered with the USB IF at www usb org kcompliance members Information about the product is submitted here including the checklist completed in the previous step At this stage an independent test lab is selected The USB IF evaluates the application and if accepted a product test ID TID is issued and the application is sent to the test lab In some cases the USB IF could request additional information before approval Test Lab Setup Once the product application is received by the test lab they contact the applicant to arrange for lab testing fees and product shipment Two units are usually shipped with required power supplies cables software installation CDs and documentation with installation instructions If the unit can be reprogrammed it is a good idea to ship the programming tools and instructions to avoid long delays if problems are found during testing that could be fixed by reprogramming Product Testing The actual test procedure is described the USB IF Full and Low Speed Electrical and Interoperability Compliance Test Procedure which can be found at www usb o
30. device s configuration descriptor 100mA or 7 2 1 3 less 9 6 2 Can the device operate in all states with a steady state Vsus of 4 35 5 25V Can the device operate in all states with a transient Veus as low as 4 02 or less at all times provided its Vaus is between 4 02 5 25V LP5 than 10uF or by using soft start circuits such that no more than 10uF of 1 7 8 capacitance is charged by currents higher than 100mA when the device is 9 4 1 2 High Power Devices not applicable to low power and self powered devices Does the device draw the amount of current specified in its MaxPower field yes 7 2 1 3 LP5 6 Does the device limit its inrush current either by using capacitors smaller yes no O 7 2 4 1 When the device is suspended is its average current draw less than 500 If the device s current draw spikes during suspend is the maximum spike yes no 7 2 3 height less than 100mA and is the spike s edge rate less than 100mA us for Veus between 4 02 and 5 25V L When the device wakes up from suspend does it limit any inrush currents to yes 7 2 3 100mA or less LP Does the device draw no inrush current at configuration or when it yes no 7 2 4 1 transitions to its operating mode Can the device operate in its unconfigured state with a steady state Vagus of yes Q no 7 2 2 4 35 5 25V Can the device operate in its unconfigured state with a transient Vaus a
31. ec Can the device s data lines withstand voltages between 1 0 and 4 6V Oetaher 5 9001 9 June 26 2009 15 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 9 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripherals Excluding Hubs 2 1 applied with a source impedance of 39Q 2 for up to 100ns an When tri stated can either data line be continuously shorted to Vsus GND the other data line or the connector s shield without damage occurring When driving 50 of the time can either data line be shorted to Veus GND yesi no 0 7 1 1 the other data line or the connector s shield without damage occurring Do the D and D traces present a characteristic impedance of 45Q 15 to yes no 7 1 6 GND and differential impedance of 9092 15 between the device s cable 7 1 6 connection and termination resistors If edge rate control capacitors are used Are they located between the transciever pins and the device s termination resistors Is their capacitance less than 75pF and balanced within 10 Are the device s receivers and transmitters within Ins of its cable 7 1 16 connection Does the device present sufficient capacitance between Vsus and GND to yes Z I 7 2 4 2 prevent adverse effects from flyback voltages when its cable is disconnected
32. icro_StellarisLM3S5732 rA_T USBET_UsFs sqc 01 For details on test setup methodology and performance criteria please consult the signal quality test description at the USB IF Compliance Program web page Required Tests Overall result pass Signal eye eye passes EOP width 165 35 ns EOP width passes Measured signaling rate 12 0031 MHz signal rate passes Crossover voltage range 1 46 V to 1 76 V mean crossover 1 60 V first crossover at 1 52 V 10 other differential crossovers checked crossover voltages pass Consecutive jitter range 699 634 ps to 656 259 ps RMS jitter 481 842 ps Paired JK jitter range 158 641 ps to 140 808 ps RMS jitter 149 990 ps Paired KJ jitter range 310 214 ps to 481 647 ps RMS jitter 299 756 ps jitter passes Additional Information e Rising Edge Rate 137 80 V us Equivalent risetime 19 16 ns minimum 132 00 V us maximum 660 00 V us e Falling Edge Rate 137 75 V us Equivalent risetime 19 16 ns minimum 132 00 V us maximum 660 00 V us e Edge Rate Match 0 04 limit 10 June 26 2009 12 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 7 Phoenix USB Device Full Speed Signals USB Signal Data D 0 and common mode signak USB Data Eye D and 0 V time ns June 26 2009 13 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and
33. it at least 5 0ms after its bus segment enters the idle state before sending a remote wakeup Does the device signal remote wakeup by driving K upstream for at least lms but not more than 15m After driving K does the device immediately tri state its buffers without driving the bus to any non K state Does the device send remote wakeups only when configured to do so Oetaher 5 9001 a June 26 2009 USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems 18 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 12 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripherals Excluding Hubs 4 Operating Voltages and Power Consumption P1 Does the device source no current to Veus under any circumstance yes nol 4 1 Bus Power Consumption applicable to all devices including self powered devices Note the current allotted for a device consuming bus power encompasses all current drawn from Vpus including the power required to drive the device s upstream USB port For details on testing USB device current consumption please consult the USB IF current test description which can be downloaded from the USB IF Compliance Program webpage 4 1 1 Low Power and Self Powered Devices not applicable to high power devices Is the MaxPower field in the
34. it field EOP 3 bit field with NIB value 00J frame 11 bit field number 8 bit field whose types are listed in section 8 3 1 SYNC 8 bit field with NZB value 00000001 token CRC 5 bit field Is the SYNC field as measured on the bus wires correct NIB 8 2 1 F2 Are all PIDs used among those listed in Table 8 1 yesW noO 8 3 1 F3 Are the PID check bits the ones complement of the packet type field F4 Are the CRC generator s contents inverted and sent to the checker MSb first F5 Is the token CRCs generated with the polynomial NZB 00101 onthe ADDR yes 8 3 5 1 and ENDP fields of IN SETUP and OUT tokens If all bits are received without error does the CRC computation on a token yes 8 3 5 1 or SOF leave a residual of NZB 01100 at the EOP 7 Is the data CRC generated with the polynomial NZB 1000000000000101 5 1 8 3 5 2 October 5 2001 June 26 2009 USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems 23 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 17 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon setup0 outl outO outl out0 inl setup0 inl inO inl inO l out setup0 inl Transactions in italics constitute the data stage
35. ment Number Rev 0001 Dae 782000 at 6 i ow 3 _ Power_Jack 2 5mm ae ae oer rs 33V ng 3 4 0 1uF Me 8 9 10 RSTn JTAG SWD iie aav uocTS USB Device m USB Host PAO UORX PBouIRX Hir 5 PAL UOTX PBI UITX PA2 SSIOCLK 2 2 1 57 TxD PA3 SSIOFSS PB3 I2COSDA EJ RXD PA4 SSIORX 7 RTS PAS SSIOTX PBS CCPO 56 RVBUS CTS PA6 I2CISCL PB6 CCP1 55 52 PCOTCK SWCLK PDOCANORX 5g PEVTMS SWDIO PDI CANOTX a mana is PC6 USBOPFLT Prwanes USBODP SH PEIADC2 USBODM T 2 USBORBIAS PEA CCP3 33V Ose USB HOST gt gt 7 16 a wo 2 san eee lt ast 12 Cl V 3 OANE GND VDD33 EJ cap vonss a TOON UES 37 265 o47uF SATE GND VBAT 8 GND 22 USB DEVICE NVA GND VDD25 i GND vpp2s 52 4 3 O1uF O 1uF 0 01uF en alama I I TOREO 2 10 10 10 0105 AUF I 3223 0 470 8 000 MHz 33V ak AE zE j F 51
36. munication Device INFO Device sub class 0 INFO Device protocol 0 INFO Device MaxPacketSize0O 40 INFO Vendor information for VendorID lcbe Luminary Micro Inc INFO Device ProductID 2 INFO Device BCD 100 INFO ENGLISH_US language string descriptor is Luminary Micro Inc INFO ENGLISH_US language string descriptor is Virtual COM Port INFO ENGLISH_US language string descriptor is 12345678 INFO Number of configurations device supports 1 INFO Stopping Test Device Descriptor Test Configuration Index 0 June 26 2009 ConfigDescriptorTest_DeviceConfigured Passed INFO Now Starting Test Configuration Descriptor Test Configuration Index 0 INFO Configuration descriptor contains descriptor of type 24 INFO Configuration descriptor contains descriptor of type 24 INFO Configuration descriptor contains descriptor of type 24 INFO Number of interface descriptors found 1 INFO Number of alternate interface descriptors found 0 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 3 Phoenix USB Test Board Device Framework Results continued INFO Number of endpoint descriptors found 3 INFO Configuration descriptor length 9 INFO Configuration descriptor type 2 INFO Configuration descriptor TotalLength 35 INFO Configuration descriptor NumInterfaces 1 INFO Configuration descriptor ConfigurationValue 1 INFO ENGLISH_US language stri
37. ndex 0 Number of Fails 0 Aborts 0 Warnings 0 INFO Now Starting Test Interface Descriptor Test Configuration Index 0 INFO Bandwidth check passed INFO Testing Interface number 0 Alternate setting 0 NFO Interface descriptor length 9 NFO Interface descriptor bDescriptorType 4 INFO Interface descriptor bAlternateSetting 0 INFO Interface descriptor bNumEndPoints 3 INFO Interface descriptor bInterfaceClass reserved for assignment by the USB IF 2 INFO Interface class code indicates CDC Control Interface INFO Interface descriptor bInterfaceSubClass 2 INFO Device does not use a class specific protocol on this interface INFO ENGLISH_US language string descriptor is ACM Control Interface INFO Stopping Test Interface Descriptor Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 EndpointDescriptorTest_DeviceConfigured Passed INFO Now Starting Test Endpoint Descriptor Test Configuration Index 0 INFO Testing Interface number 0 Alternate setting 0 INFO Endpoint descriptor length 7 INFO Endpoint descriptor type 5 INFO Endpoint Type Interrupt Number 1 Direction IN INFO Endpoint descriptor bmAttributes 3 June 26 2009 9 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 4 Phoenix USB Test Board Device Framework Results continued 2 2 2
38. ng descriptor is Self Powered Configuration NFO Configuration descriptor bmAttributes INFO Device does not support remote wake up INFO Maximum power device requires OmA INFO Device is SELF POWERED INFO Device is currently SELF POWERED INFO Currently remote wakeup is DISABLED INFO Stopping Test Configuration Descriptor Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 INFO Now Starting Test Configuration Descriptor Test Configuration Index 0 INFO Configuration descriptor contains descriptor of type 24 NFO Configuration descriptor contains descriptor of type 24 NFO Configuration descriptor contains descriptor of type 24 NFO Number of interface descriptors found 1 NFO Number of alternate interface descriptors found 0 NFO Number of endpoint descriptors found 3 NFO Configuration descriptor length 9 NFO Configuration descriptor type 2 NFO Configuration descriptor TotalLength 35 INFO Configuration descriptor NumInterfaces 1 INFO Configuration descriptor ConfigurationValue 1 NFO ENGLISH_US language string descriptor is Self Powered Configuration NFO Configuration descriptor bmAttributes NFO Device does not support remote wake up NFO Maximum power device requires OmA NFO Device is SELF POWERED NFO Device is currently SELF POWERED NFO Currently remote wakeup is DISABLED NFO Stopping Test Configuration Descriptor Test Configuration I
39. ns RMS jitter 1 705 ns jitter passes Additional Information e Rising Edge Rate 23 41 V us Equivalent risetime 112 76 ns minimum 8 80 V us maximum 35 20 V us e Falling Edge Rate 22 33 V us Equivalent risetime 118 21 ns minimum 8 80 V us maximum 35 20 V us e Edge Rate Match 4 83 limit 20 June 26 2009 34 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 26 Phoenix USB Embedded Host Low Speed Signals Signal Data D 0 and common mode signak Y Data Eye D and 0 V 0 100 200 300 400 500 600 time ns June 26 2009 35 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Schematics This section contains the schematic diagrams for the Stellaris USB Embedded Host and USB Device USB Device on page 37 USB Host on page 38 June 26 2009 36 15
40. nts products and application solutions Products Applications Amplifiers amplifier ti ccom Audio www ti com audio Data Converters dataconverter ti com Automotive www ti com automotive DLP Products www dlp com Broadband www ti com broadband DSP dsp ti com Digital Control www ti com digitalcontrol Clocks and Timers www ti com clocks Medical www ti com medical Interface interface ti com Military www ti com military Logic logic ti com Optical Networking www ti com opticalnetwork Power Mgmt power ti com Security www ti com security Microcontrollers microcontroller ti com Telephony www ti com telephony RFID www ti rfid com Video amp Imaging www ti com video RF IF and ZigBee Solutions www ti com lprf Wireless www ti com wireless Mailing Address Texas Instruments Post Office Box 655303 Dallas Texas 75265 Copyright 2009 Texas Instruments Incorporated June 26 2009 40
41. ny address in the device no ignored by the device Is a token whose endpoint field doesn t match any endpoint in the address yes ignored by the device nored nO October 5 2001 7 June 26 2009 24 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 18 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripheral Silicon Excluding Hub Silicon the data field of a data packet a ae If all bits are received without error does the CRC computation on the data yes 8 3 5 2 field leave a residual of NZB 1000000000001101 at the EOP 3 3 Packets A packet can be one of the following packet fields comprising packet SYNC PID data data CRC EOP handshake SYNC PID EOP PRE SYNC PID SOF SYNC PID frame number token CRC EOP SYNC PID endpoint token CRC EOP Pi Are all token packets 32 bits long and followed by an EOP 3 4 1 Are all token packets of the form SYNC PID address endpoint token CRC EOP Are all data packets an integral number of bytes long 4 to 1027 excluding the EOP Is the data packet constituted as sync followed by PID followed by 0 to 8 4 3 1023 bytes of data followed by data CRC followed by EOP P5 Are all handshake packets 16 bits EOP J 844 P6 Are all handshake packets of the form SYNC PID EOP 844
42. o the test lab In some cases the USB IF could request additional information before approval Test Lab Setup Once the product application is received by the test lab they contact the applicant to arrange for lab testing fees and product shipment Two units are usually shipped with required power supplies cables software installation CDs and documentation with installation instructions If the unit can be reprogrammed it is a good idea to ship the programming tools and instructions to avoid long delays if problems are found during testing that could be fixed by reprogramming Test Requirements The test requirements are described in two documents Requirements and Recommendations for USB Products with Embedded Hosts and or Receptacles USB IF Embedded Host Compliance Plan A USB Embedded Host must source at least 8 mA on each downstream port The Phoenix test board supports 100 mA on its downstream port June 26 2009 29 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems USB Embedded Host Targeted Peripheral List Embedded host systems only support a limited number of USB Devices as defined in the Targeted Peripheral List TPL The Phoenix USB Embedded Host has support for a USB low speed and a USB full speed mouse with mouse X Y delta movement and button press release data transmitted over the serial port Table 1 shows the targeted peripheral list for the Phoenix
43. ons modifications enhancements improvements and other changes to its products and services at any time and to discontinue any product or service without notice Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete All products are sold subject to Tl s terms and conditions of sale supplied at the time of order acknowledgment warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TI s standard warranty Testing and other quality control techniques are used to the extent deems necessary to support this warranty Except where mandated by government requirements testing of all parameters of each product is not necessarily performed assumes no liability for applications assistance or customer product design Customers are responsible for their products and applications using Tl components To minimize the risks associated with customer products and applications customers should provide adequate design and operating safeguards does not warrant or represent that any license either express or implied is granted under any patent right copyright mask work right or other intellectual property right relating to any combination machine or process in which products or services are used Information published by regarding third party products or services does not con
44. peed October 5 2001 9 June 26 2009 28 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Product Submission Procedure for USB Embedded Host This section describes the submission procedure for USB Embedded Host compliance certification There are four main steps in this process 1 Checklist completion 2 Online registration 3 Test lab setup 4 Test requirements Checklist Completion The USB Compliance Checklist for Systems available at www usb org developers compliance must be submitted The checklist provides an assessment of product compliance and any problems at this stage must be resolved to ensure a successful compliance test Note that USB connectors and cables used must be in the Integrator s List otherwise a checklist must also be provided for the corresponding component not on the list No additional checklist is required for silicon certification Online Registration The product must be registered with the USB IF at www usb org kcompliance members Information about the product is submitted here including the checklist completed in the previous step An additional requirement is the submission of a Targeted Peripheral List TPL which is a list of the specific devices that the USB Embedded Host supports see Table 1 on page 30 The USB IF will evaluate the application and if accepted a product test ID TID is issued and the application is sent t
45. point descriptor type 5 NFO Endpoint Type Bulk Number 3 Direction OUT INFO Endpoint descriptor bmAttributes 2 NFO Endpoint descriptor raw MaxPacketSize 40 INFO Endpoint descriptor interval 0 INFO Stopping Test Endpoint Descriptor Test Configuration Index 0 Number of Fails 0 Aborts 0 Warnings 0 Z FO 2 2 2 2 1 2 2 2 a g g g g Now Starting Test Halt Endpoint Test Testing Interface number Testing EndPoint type Interrupt Address Endpoint is currently not halted Endpoint is halted Cleared endpoint halt Testing EndPoint type Bulk Address 82 Endpoint is currently not halted Endpoint is halted Cleared endpoint halt Testing EndPoint type Bulk Address 3 Endpoint is currently not halted Endpoint is halted Cleared endpoint halt Stopping Test Halt Endpoint Test Number of Fails 0 Aborts 0 Warnings 0 Configuration Index 0 0 Alternate setting 0 81 Configuration Index 0 SetConfigurationTest Passed INFO INFO June 26 2009 Now Starting Test SetConfiguration Test SetConfiguration with configuration value Configuration Index 0 1 10 Application Note Figure 5 Phoenix USB Test Board Device Framework Results continued Number of Fails 0 Aborts 0 Warnings 0 NFO Unconfigured the device INFO SetConfiguration with configuration value 1 INFO
46. present 100pF or less on D and D 3 Device States and Signals Can the device pull up the appropriate data line to at least 2 0V within 2 5us Does the device respond to a reset no sooner than 2 5us and no later than yes no O 10ms after the SEO begins Is the device s reset recovery time less than 10ms At the end of reset is the device in the default state Can the device correctly handle more than one USB RESET with no intervening packets D D D4 D 9 Does the device meet all power on and connection timing requirements as yes illustrated in Figure 7 29 Does the device begin the transition to its suspend state after its bus segment has been idle for 3ms regardless of the device s state Has the device s power consumption dropped to its suspended value after the hub s upstream bus segment has been idle for 10ms When suspended does the device recognize any non idle state on the bus excluding a reset as a resume signal D13 When suspended does the device recognize a reset and act on the signal yes f7 so that it enters the default state Does the device recognize a K gt low speed EOP J transition on its 7 1 7 7 upstream port as the end of resume signaling 2 3 5 Is the device able to accept a SetAddress request 10ms after resume is signaled Is the device s pullup active only when is high Is the Veus switching threshold for the
47. rg developers docs USB IFTestProc1_3 pdf This document describes test procedures for systems hubs and peripherals The test requirements include Electrical tests Interoperability tests Functional tests June 26 2009 6 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Recommendation Read this document and pre test as much as possible before submitting the product for testing At a minimum run the USB command verifier tool USBCV which evaluates a USB Device s conformance to the USB Device Framework on the target device This tool runs on a Windows PC and requires that the target device connect to a USB 2 0 high speed hub connected to the host PC This tool can be found at www usb org developers tools USB Device Test Results This section provides the Phoenix USB test board results for a USB Device starting with Figure 2 on page 8 through Figure 5 on page 11 Figure 6 on page 12 shows the Phoenix USB Test Board Full Speed Signal Quality Test Results and Figure 7 on page 13 shows the Phoenix USB Device Full Speed Signals June 26 2009 7 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 2 Phoenix USB Test Board Device Framework Results USB Device Framework Chapter 9 Tests NUMBER OF TESTS 13 RESULT passed InitializeTestSuite INFO Microsoft Windows XP Build 2600
48. s 9 1 1 4 Are the device s differential and single ended USB signals within spec yes Z no 7 1 6 Note This test is especially important if ferrite beads or a common mode D24 Does the device pass a full Chapter 9 test as performed by USB Check Chapters choke is used on the USB data lines as these components often pose a significant signal integrity hazard Device vendors are strongly encouraged to complete all bus transactions as quickly as is practical See section 9 2 6 1 for details For details on testing USB signals consult the USB IF s signal quality test description which can be downloaded from the USB IF Compliance Program webpage 3 1 Low Speed Devices not applicable to full speed devices Does a low speed device implement the default control pipe and at most yes 5 3 1 1 two interrupt endpoints Does the device allow an interpacket delay of at least two low speed bit yes 7 1 18 times Is the device s transaction timeout 16 18 low speed bit times 7 1 19 Does the device recognize keep alive strobes and remain awake 11 8 4 1 3 2 Full Speed Devices not applicable to low speed devices Does the device allow an interpacket delay of at least two full speed bit 7 1 18 times Is the device s transaction timeout 16 18 full speed bit times 7 1 19 Does the device ignore low speed packets 3 3 Remote Wakeup not applicable to devices which do not support remote wakeup Does the device wa
49. s low as 4 02V While unconfigured does the device draw 100mA or less at all times 72 1 3 provided its Vaus is between 4 02 and 5 25V Can the device operate in its configured state with a steady state Vgus of yes no 7 2 2 4 50 5 25V Can the device operate in its configured state with a transient Vsus as low as 4 17V While configured does the device draw the amount of current specified in yes 7 2 1 3 its MaxPower field or less at all times provided its Veus is between 4 02 and 5 25V If the device does not support remote wakeup the device is not configured Oetaher 5 9001 June 26 2009 A 19 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Figure 13 Phoenix USB Test Board Compliance Checklist Sample continued USB 2 0 Compliance Checklist Peripherals Excluding Hubs or remote wakeup is disabled is the device s average suspend current draw less than 5001 Tf the device supports remote wakeup remote wakeup is enabled and the yes no 7 2 3 device is configured is the device s average suspend current draw less than 2 5mA If the device s current draw spikes during suspend is the maximum spike yes 7 2 3 height less than 500mA and the spike s leading edge rate less than 100mA us for Vsus between 4 02 and 5 25V When the device wakes up from suspend does it limit any inrush currents to
50. stitute a license from to use such products or services or a warranty or endorsement thereof Use of such information may require a license from a third party under the patents or other intellectual property of the third party or a license from TI under the patents or other intellectual property of TI Reproduction of TI information data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties conditions limitations and notices Reproduction of this information with alteration is an unfair and deceptive business practice is not responsible or liable for such altered documentation Information of third parties may be subject to additional restrictions Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all express and any implied warranties for the associated product or service and is an unfair and deceptive business practice is not responsible or liable for any such statements products are not authorized for use in safety critical applications such as life support where a failure of the product would reasonably be expected to cause severe personal injury or death unless officers of the parties have executed an agreement specifically governing such use Buyers represent that they have all necessary expertise in the safety and regulatory ramifications of their
51. the Product Submission Procedure for USB Device on page 6 for specific information on submitting a product to the USB IF The Phoenix USB Device schematic is shown on page 37 All specific components for USB Host are marked with a red X and are not fitted during board assembly Note that resistors R4 and R17 are required for USB Device operation due to a silicon errata USB Embedded Host Phoenix USB Host assemblies include a USB power controller but do not include specific components for USB Device See the Product Submission Procedure for USB Embedded Host on page 29 for specific information on submitting a product to the USB IF The Phoenix USB Host schematic is shown on page 29 All specific components for USB Device are marked with a red X and are not fitted during board assembly Note that resistors R3 and R17 are required for USB Host operation due to a silicon errata June 26 2009 5 Application Note USB Certification for Stellaris Microcontroller based USB Peripherals and Embedded Host Systems Product Submission Procedure for USB Device This section describes the submission procedure for USB Device compliance certification This process has four main steps 1 Checklist completion 2 Online registration 3 Test lab setup 4 Product testing Checklist Completion The first step should be to complete the USB Compliance Checklist Peripherals Excluding Hubs form available at www usb org developers compliance The che
52. uestions into consideration when designing their products Questions or comments regarding the Integrators List Compliance Workshop testing results or checklist submissions should be sent to admin usb org If you have questions regarding the checklist itself feel it fails to adequately cover an aspect of the USB specification have found an error or would like to propose a question please contact the USB IF at checklists usb org 1 1 General Notes All voltages are referenced to the device s USB ground 2 Mechanical Design and Layout question What is the manufacture and model identifier of the connectors or cables used with this peripheral Manufacturer Molex USB B connector Model 67068 8000 If the connectors or cables used in this peripheral are NOT listed on the USB Integrators List attach Connector and Cable Assembly checklists covering this peripheral s connectors and cable assemblies What is the manufacture and model identifier of the USB silicon used in this peripheral Manufacturer Luminary Micro Model LM3S5732 If the silicon used in this peripheral is NOT listed on the USB Integrators List attach a Peripheral Silicon checklist covering this peripheral s USB silicon Device vendors are strongly encouraged to review the Connector and Cable Assembly and Peripheral Silicon checklists regardless of whether or not their device s cabling connectors and silicon appear on the Integrators List e ooo ac in sp
Download Pdf Manuals
Related Search