2015-2016 Microchip Technology Inc. DS00001997B-page 1 INTRODUCTION The USB to GPIO bridging feature of Microchip’s USB 2.0 hubs provides system designers expanded system control and potential BOM reduction. General Purpose Input/Outputs (GPIOs) may be used for any general 3.3V level digital control and input functions. This feature is available on the Microchip USB5734 and USB58xx/USB59xx USB3.1 Gen 1 Hubs. Commands may be sent from the USB Host to the internal Hub Feature Controller device in the Microchip hub to per- form the following functions: • Set the direction of the GPIO (input or output) • Enable a pull-up resistor • Enable a pull-down resistor • Read the state • Set the state SECTIONS Section 1.0, General Information Section 2.0, Part Number Specific Information Section 3.0, SDK Implementation Section 4.0, Manual Implementation Section 5.0, Examples REFERENCES Consult the following documents for details on the specific parts referred to in this document. • Microchip USB5734 Data Sheet • Microchip USB5806 Data Sheet • Microchip USB5816 Data Sheet • Microchip USB5826 Data Sheet • Microchip USB5906 Data Sheet • Microchip USB5916 Data Sheet • Microchip USB5926 Data Sheet • Microchip AN1903 Configuration Options for the USB5734 and USB5744 • Microchip AN2316 Configuration Options for the USB58xx and USB59xx AN1997 USB to GPIO Bridging with Microchip USB3.1 Gen1 Hubs Author: Andrew Rogers Microchip Technology, Inc.
32
Embed
AN1997 USB to GPIO Bridging with Microchip USB3.1 …ww1.microchip.com/downloads/cn/AppNotes/cn576827.pdfUSB to GPIO Bridging with Microchip USB3.1 Gen1 Hubs Author: Andrew Rogers
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
AN1997USB to GPIO Bridging with Microchip USB3.1 Gen1
Hubs
INTRODUCTION
The USB to GPIO bridging feature of Microchip’s USB 2.0 hubs provides system designers expanded system control and potential BOM reduction. General Purpose Input/Outputs (GPIOs) may be used for any general 3.3V level digital control and input functions. This feature is available on the Microchip USB5734 and USB58xx/USB59xx USB3.1 Gen 1 Hubs.
Commands may be sent from the USB Host to the internal Hub Feature Controller device in the Microchip hub to per-form the following functions:
• Set the direction of the GPIO (input or output)
• Enable a pull-up resistor
• Enable a pull-down resistor
• Read the state
• Set the state
SECTIONS
Section 1.0, General Information
Section 2.0, Part Number Specific Information
Section 3.0, SDK Implementation
Section 4.0, Manual Implementation
Section 5.0, Examples
REFERENCES
Consult the following documents for details on the specific parts referred to in this document.
• Microchip USB5734 Data Sheet
• Microchip USB5806 Data Sheet
• Microchip USB5816 Data Sheet
• Microchip USB5826 Data Sheet
• Microchip USB5906 Data Sheet
• Microchip USB5916 Data Sheet
• Microchip USB5926 Data Sheet
• Microchip AN1903 Configuration Options for the USB5734 and USB5744
• Microchip AN2316 Configuration Options for the USB58xx and USB59xx
Author: Andrew RogersMicrochip Technology, Inc.
2015-2016 Microchip Technology Inc. DS00001997B-page 1
AN1997
1.0 GENERAL INFORMATION
Microchip hub USB Bridging features in Microchip hubs work via host commands sent to a Hub Feature Controller embedded within the hub located on an additional internal USB port. In order for the bridging features to work correctly, this internal Hub Feature Controller must be enabled by default. Table 1 provides details on default Hub Feature Con-troller setters by device.
TABLE 1: DEFAULT SETTINGS FOR THE HUB FEATURE CONTROLLER ENABLE
Part Number Part SummaryHub Feature Controller Default
Setting
USB5734 4-Port USB3.1 Gen 1 Hub Enabled by default
USB5806 6-Port USB3.1 Gen1 Hub Enabled by default
USB5816 6-Port USB3.1 Gen1 Hub with Type-C™ Support on 1 Downstream Port
Enabled by default
USB5826 6-Port USB3.1 Gen1 Hub with Type-C Support on 2 Downstream Ports
Enabled by default
USB5906 6-Port USB3.1 Gen1 Hub with Type-C Support on the Upstream Port
Enabled by default
USB5916 6-Port USB3.1 Gen1 Hub with Type-C Support on the Upstream Port and 1 Downstream Port
Enabled by default
USB5926 6-Port USB3.1 Gen1 Hub with Type-C Support on the Upstream Port and 2 Downstream Ports
Enabled by default
The Hub Feature Controller is a USB2.0 WinUSB class device connected to an extra internal USB2.0 port in the hub. For example, in a four port hub, the Hub Feature Controller is connected to port 5 of the USB2.0 portion of the hub. The Product ID (PID) for the Hub Feature Controller is 0x2740 on USB5734, and 0x2840 on USB58xx/USB59xx. All bridging commands are addressed to the Hub Feature Controller, not the Hub.
FIGURE 1-1: MICROCHIP HUB CONTROLLER EXAMPLE
USB Host
MicrochipUSB5734 GPIO
I2CUARTSPI
prt4prt1 prt2 prt3
prt5
UpstreamPort
Hub FeatureController
DownstreamPort
DownstreamPort
DownstreamPort
DownstreamPort
U S B D e v i c e s
VID = 0x0424PID = 0x2740
DS00001997B-page 2 2015-2016 Microchip Technology Inc.
AN1997
FIGURE 1-2: MICROCHIP HUB CONTROLLER EXAMPLE
USB Host
MicrochipUSB5806 GPIO
I2C
SPI
prt5prt2 prt3 prt4
prt7
UpstreamPort
Hub FeatureController
DownstreamPort
DownstreamPort
DownstreamPort
DownstreamPort
U S B D e v i c e s
VID = 0x0424PID = 0x2840
prt1
DownstreamPort
prt6
DownstreamPort
The following GPIO Functions are supported:
• Set the GPIO Direction (Input or Output)
• Enable GPIO Internal Pull-up Resistor
• Enable GPIO Internal Pull-down Resistor
• GPIO Read State (Input Mode)
• GPIO Set State (Output Mode)
1.1 Set the GPIO Direction (Input or Output)
Each GPIO can be configured as either a Schmitt-triggered input or output with an 8 mA sink/source.
1.2 Enable GPIO Internal Pull-up Resistor
Each GPIO can be enabled with a 50 μA (typical) internal pull-up resistor. Internal pull-up resistors prevent unconnected inputs from floating. The pull-up is only 67k, so it may not be strong enough to drive a load of less than 100k. When connected to a load that must be pulled high, an external resistor must be added.
1.3 Enable GPIO Internal Pull-down Resistor
Each GPIO can be enabled with a 50 μA (typical) internal pull-down resistor. Internal pull-down resistors prevent uncon-nected inputs from floating. The pull-down is only 67k, so it may not be strong enough to drive a load of less than 100k. When connected to a load that must be pulled low, an external resistor must be added.
1.4 GPIO Read State (Input Mode)
Read a 0: GPIO is below 0.9V
Read a 1: GPIO is above 1.9V
Note: When configured as an input, the GPIOs are digital Schmitt-triggered inputs. The range 0.8V - 2.0V is an indeterminate input state, so 3.3V-2.5V signaling is supported.
2015-2016 Microchip Technology Inc. DS00001997B-page 3
AN1997
1.5 GPIO Set State (Output Mode)
Set to 0: GPIO Drives to 0.0V. When driven low, an 8 mA sink is enabled driving the pin to 0.4V or lower.
Set to 1: GPIO Drives to 3.3V. When driven high, an 8 mA source is enabled driving the pin to VDD33 - 0.4V or higher.
DS00001997B-page 4 2015-2016 Microchip Technology Inc.
AN1997
2.0 PART NUMBER SPECIFIC INFORMATION
2.1 Part Summary
Table 2 summarizes the total number of available GPIOs by part number. Many of the GPIOs on the hub are only avail-able after configuration. The following methods may be used to configure the hub:
• ProTouch: If configuring via internal One-Time Programmable (OTP) memory, or if configuring via SPI EEPROM with a base firmware file.
• SMBus/I2C Configuration: If using an embedded SoC/I2C EEPROM to configure the hub at each start-up/reset.
• Pin Strapping: Many of the GPIOs are made available by specific pin strapping or by simply not populating a SPI EEPROM device.
2015-2016 Microchip Technology Inc. DS00001997B-page 5
AN1997
2.2 USB5734 GPIO Pins
TABLE 3: USB5734 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
7 GPIO7 PROG_FUNC7/GPIO Set CFG_STRAP to Mode 4
34 GPIO20 Port 4 Port Power Control
Disable Port 4 and Disable Port Power 4 Output + OCS 4 InputorSet hub into Port Power Ganged Mode and Disable Port Power 4 Output + OCS 4 Input
36 GPIO19 Port 3 Port Power Control
Disable Port 3 and Disable Port Power 3 Output + OCS 3 InputorSet hub into Port Power Ganged Mode and Disable Port Power 3 Output + OCS 3 Input
37 GPIO18 Port 2 Port Power Control
Disable Port 2 and Disable Port Power 2 Output + OCS 2 InputorSet hub into Port Power Ganged Mode and Disable Port Power 2 Output + OCS 2 Input
38 GPIO17 Port 1 Port Power Control
Disable Port 1 and Disable Port Power 4 Output + OCS 1 InputorSet hub into Port Power Ganged Mode and Disable Port Power 1 Output + OCS 1 Input
39 GPIO2 PROG_FUNC2/GPIO Set CFG_STRAP to Mode 1 or 4
40 GPIO3 PROG_FUNC3/GPIO Set CFG_STRAP to Mode 1 or 4
41 GPIO16 VBUS_DET Disable VBUS_DET function
42 GPIO4 SPI_CLK Do not use SPI ROM, UART, or I2C interface
43 GPIO5 SPI_DO Do not use SPI ROM, UART, or I2C interface
44 GPIO9 SPI_DI Do not use SPI ROM
45 GPIO7 SPI_CE_N Do not use SPI ROM
46 GPIO6 PROG_FUNC4/GPIO Set CFG_STRAP to Mode 4
47 GPIO8 PROG_FUNC5/GPIO Set CFG_STRAP to Mode 4 or Mode 5
49 GPIO11 PROG_FUNC6/GPIO Set CFG_STRAP to Mode 4 or Mode 5
50 GPIO1 PROG_FUNC1/GPIO Set CFG_STRAP to Mode 1 or Mode 4
2.3 USB5806 GPIO Pins
TABLE 4: USB5806 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
50 GPIO65 SPEED_IND5 No config required.
53 GPIO23 HOST_TYPE0 No config required.
55 GPIO67 HOST_TYPE1 No config required.
56 GPIO2 SPEED_IND3 No config required.
60 GPIO3 SPEED_IND4 No config required.
61 GPIO71 SPEED_IND2 No config required.
63 GPIO70 SPEED_IND1 No config required.
65 GPIO4 C_ATTACH3 Do not implement Type-C control on Port 3 in hardware.
66 GPIO5 C_ATTACH2 Do not implement Type-C control on Port 2 in hardware.
69 GPIO69 PRT_CTL0 No config required.
DS00001997B-page 6 2015-2016 Microchip Technology Inc.
AN1997
2.4 USB5816 GPIO Pins
TABLE 5: USB5816 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
53 GPIO23 HOST_TYPE0 No config required.
55 GPIO67 HOST_TYPE1 No config required.
60 GPIO3 GPIO3 GPIO3 by default.
61 GPIO71 SPEED_IND2 No config required.
63 GPIO70 SPEED_IND1 No config required.
65 GPIO4 GPIO4 GPIO4 by default.
66 GPIO5 GPIO5 GPIO5 by default.
69 GPIO69 PRT_CTL0 No config required.
71 GPIO66 GPIO66 GPIO66 by default.
77 GPIO68 SUSP_IND No config required.
2.5 USB5826 GPIO Pins
TABLE 6: USB5826 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
53 GPIO23 HOST_TYPE0 No config required.
55 GPIO67 HOST_TYPE1 No config required.
60 GPIO3 GPIO3 GPIO3 by default.
61 GPIO71 SPEED_IND2 No config required.
63 GPIO70 SPEED_IND1 No config required.
65 GPIO4 GPIO4 GPIO4 by default.
66 GPIO5 GPIO5 GPIO5 by default.
69 GPIO69 PRT_CTL0 No config required.
77 GPIO68 SUSP_IND No config required.
71 GPIO66 SPEED_IND6 No config required.
73 GPIO1 C_ATTACH1 Do not implement Type-C control on Port 1 in hardware.
76 GPIO64 C_ATTACH0 Do not implement Type-C control on Port 0 in hardware.
77 GPIO68 SUSP_IND No config required.
TABLE 4: USB5806 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
2015-2016 Microchip Technology Inc. DS00001997B-page 7
AN1997
2.6 USB5906 GPIO Pins
TABLE 7: USB5906 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
50 GPIO65 GPIO65 GPIO65 by default.
55 GPIO67 HOST_TYPE1 No config required.
53 GPIO23 HOST_TYPE0 No config required.
61 GPIO71 SPEED_IND2 No config required.
63 GPIO70 SPEED_IND1 No config required.
65 GPIO4 GPIO4 GPIO4 by default.
66 GPIO5 GPIO5 GPIO5 by default.
69 GPIO69 PRT_CTL0 No config required.
71 GPIO66 GPIO66 GPIO66 by default.
77 GPIO68 SUSP_IND No config required.
2.7 USB5916 GPIO Pins
TABLE 8: USB5916 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
53 GPIO23 HOST_TYPE0 No config required.
55 GPIO67 HOST_TYPE1 No config required.
61 GPIO71 SPEED_IND2 No config required.
63 GPIO70 SPEED_IND1 No config required.
65 GPIO4 GPIO4 GPIO4 by default.
66 GPIO5 GPIO5 GPIO5 by default.
69 GPIO69 PRT_CTL0 No config required.
71 GPIO66 GPIO66 GPIO66 by default.
77 GPIO68 SUSP_IND No config required.
2.8 USB5926 GPIO Pins
TABLE 9: USB5926 GPIO AVAILABILITY AND CONFIGURATION REQUIREMENTS
Pin # Name Primary Function Configuration Required
53 GPIO23 HOST_TYPE0 No config required.
55 GPIO67 HOST_TYPE1 No config required.
61 GPIO71 SPEED_IND2 No config required.
63 GPIO70 SPEED_IND1 No config required.
69 GPIO69 PRT_CTL0 No config required.
65 GPIO4 GPIO4 GPIO4 by default.
66 GPIO5 GPIO5 GPIO5 by default.
77 GPIO68 SUSP_IND No config required.
DS00001997B-page 8 2015-2016 Microchip Technology Inc.
AN1997
3.0 SDK IMPLEMENTATION
The simplest method for implementing the USB to GPIO bridging functions is to use the publicly available DLL which is distributed with the ProTouch2 configuration tool. The DLL is compatible with Windows operating systems. Visit the USB5734 product page on microchip.com to download ProTouch2 with the DLL package. Using the libraries available in the DLL, the bridging features can be implemented in C-code.
The DLL package contains the following:
• User’s Manual (Protouch2 DLL User’s Guide) with detailed description of how to use the DLL and call each func-tion
• Release Notes
• Library Files:
- For Windows: A “.dll” and a “.lib” file
- For Linux: a “.cpp” file that can be built into a “.a” file
• Example code
3.1 Commands Included in the SDK
• MchpUsbGpioConfigureGPIO: Configures a pin to behave as a GPIO.
• MchpUsbGpioGet: Sets the queried GPIO to an input (if not already set as such) and then reads the input state.
• MchpUsbGpioSet: Sets the queried GPIO to an output (if not already set as such) and then sets the output state.
For additional details on how to use the SDK to implement USB to GPIO bridging, download the SDK package and refer to the User’s Manual.
2015-2016 Microchip Technology Inc. DS00001997B-page 9
AN1997
4.0 MANUAL IMPLEMENTATION
The USB to GPIO bridging features may be implemented at the lowest level if you have the ability to build USB packets. This approach is required if you are not using a Windows or Linux host system and cannot use the SDK.
All USB to GPIO bridging commands are accomplished with internal register writes and reads. Further details can be found in Microchip application note AN1903 Configuration Options for the USB5734 and USB5744 or AN2316 Config-uration Options for the USB58xx and USB59xx. All USB to GPIO bridging commands must be sent directly to Endpoint 0 of the Hub Feature Controller connected to the last downstream port of the Microchip hub (i.e.: located on port 5 of a 4-port hub).
For details on the register read and write USB SETUP packets, refer to Section 4.1, "Register Read" and Section 4.2, "Register Write", respectively. The configuration register addresses and contents are detailed in Section 4.3, "GPIO Configuration Register Map for USB5734" and Section 4.4, "Register Definitions for USB5734".
4.1 Register Read
To read the state of a GPIO, a register read with the following USB SETUP packet must be used:
TABLE 10: REGISTER READ USB SETUP COMMAND
Setup Parameter Value Description
bmRequestType 0xC1 Device-to-host, vendor class, targeted to interface
bRequest 0x04 Register read command: CMD_REG_READ
wValue Register Address Valid Address Range: <0x0000> to <0xFFFF> [64KB]
wIndex 0x0000 Reserved
wLength Data Length Length of the data bytes to be retrieved
4.1.1 REGISTER READ USB TRANSACTION SEQUENCE
Command Phase: Hub Feature Controller receives the setup packet with the parameters specified in Table 10.
Data Phase: Hub Feature Controller sends the data bytes of length wLength from the specified address.
Status Phase: Hub Feature Controller sends ACK on successful completion of register read.
4.2 Register Write
To configure the direction of a GPIO, pull-up/pull-down resistor settings, or set the output state of a GPIO, a register write command with the following USB SETUP packet must be used:
TABLE 11: REGISTER WRITE USB SETUP COMMAND
Setup Parameter Value Description
bmRequestType 0x41 Host-to-device, vendor class, targeted to interface
7 GPIO_71_PU R/W Set bit to enable GPIO71 Pull-up resistor.
6 GPIO_70_PU R/W Set bit to enable GPIO70 Pull-up resistor.
5 GPIO_69_PU R/W Set bit to enable GPIO69 Pull-up resistor.
4 GPIO_68_PU R/W Set bit to enable GPIO68 Pull-up resistor.
3 GPIO_67_PU R/W Set bit to enable GPIO67 Pull-up resistor.
2 GPIO_66_PU R/W Set bit to enable GPIO66 Pull-up resistor.
1 GPIO_65_PU R/W Set bit to enable GPIO65 Pull-up resistor.
0 GPIO_64_PU R/W Set bit to enable GPIO64 Pull-up resistor.
2015-2016 Microchip Technology Inc. DS00001997B-page 25
AN1997
5.0 EXAMPLES
5.1 Read the Direction State of all GPIOs on USB5734
1. Command Phase (SETUP Transaction): Send the following SETUP Register Read Command to Endpoint 0 of the USB5734 Hub Feature Controller to read the contents of registers 0x830, 0x831, 0x832, and 0x833 which contain the direction control settings for all GPIOs.
TABLE 57: REGISTER READ SETUP COMMAND EXAMPLE
Setup Parameter Value Note
bmRequestType 0xC1 —
bRequest 0x04 —
wValue 0x0830 First register in a series of consecutive registers to read from.
wIndex 0x0000 —
wLength 0x0004 4 consecutive registers are to be read.
FIGURE 5-1: REGISTER READ SETUP TRANSACTION EXAMPLE
2. Data Phase (IN Transaction): Hub Feature Controller sends the data bytes of length wLength starting from the specified address after receiving an IN packet.
FIGURE 1: REGISTER READ IN TRANSACTION EXAMPLE
3. Status Phase (OUT Transaction): Host sends an OUT packet to complete the USB Transfer. Hub Feature Con-troller responds with a zero length data packet.
FIGURE 2: REGISTER READ OUT TRANSACTION EXAMPLE
DS00001997B-page 26 2015-2016 Microchip Technology Inc.
AN1997
5.2 Write Registers to Set GPIO10 as an output on the USB5734
1. Command Phase (SETUP Transaction): Send the following SETUP Register Write Command to Endpoint 0 of the USB5734 Hub Feature Controller to write the contents of registers 0x830, 0x831, 0x832, and 0x833 which contain the direction control settings for all GPIOs. In this example, GPIO10 will be set as an output, all other GPIOS will remain at the default input state.
TABLE 58: REGISTER WRITE SETUP COMMAND EXAMPLE
Setup Parameter Value Note
bmRequestType 0x41 —
bRequest 0x03 —
wValue 0x0830 First register in a series of consecutive registers to write from.
wIndex 0x0000 —
wLength 0x0004 4 consecutive registers are to be read.
FIGURE 3: REGISTER WRITE SETUP TRANSACTION EXAMPLE
2. Data Phase (OUT Transaction): Host sends the four data bytes to set 0x830 = 0x00, 0x831 = 0x04, 0x832 = 0x00, and 0x833 = 0x00 from the specified address after sending the OUT packet.
FIGURE 4: REGISTER WRITE OUT TRANSACTION EXAMPLE
3. Status Phase (OUT Transaction): Host sends an IN packet to complete the USB Transfer. Hub Feature Con-troller responds with a zero length data packet.
FIGURE 5: REGISTER WRITE IN TRANSACTION EXAMPLE
2015-2016 Microchip Technology Inc. DS00001997B-page 27
AN1997
APPENDIX A: APPLICATION NOTE REVISION HISTORY
TABLE A-1: REVISION HISTORY
Revision Level & Date Section/Figure/Entry Correction
DS00001997B (12-07-16) All Fixed references to AN2316 Configuration Options for the USB58xx and USB59xx throughout.
Trademark and Sales Listing pages updated.
Updated minor formatting and grammar issues throughout.
DS00001997A (09-10-15) All Initial release.
DS00001997B-page 28 2015-2016 Microchip Technology Inc.
AN1997
NOTES:
2015-2016 Microchip Technology Inc. DS00001997B-page 29
AN1997
DS00001997B-page 30 2015-2016 Microchip Technology Inc.
THE MICROCHIP WEB SITE
Microchip provides online support via our WWW site at www.microchip.com. This web site is used as a means to make files and information easily available to customers. Accessible by using your favorite Internet browser, the web site contains the following information:
• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQ), technical support requests, online discussion groups, Microchip consultant program member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives
CUSTOMER CHANGE NOTIFICATION SERVICE
Microchip’s customer notification service helps keep customers current on Microchip products. Subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest.
To register, access the Microchip web site at www.microchip.com. Under “Support”, click on “Customer Change Notifi-cation” and follow the registration instructions.
CUSTOMER SUPPORT
Users of Microchip products can receive assistance through several channels:
• Distributor or Representative
• Local Sales Office
• Field Application Engineer (FAE)
• Technical Support
Customers should contact their distributor, representative or Field Application Engineer (FAE) for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in the back of this document.
Technical support is available through the web site at: http://microchip.com/support
2015-2016 Microchip Technology Inc. DS00001997B-page 31
AN1997
Information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Micro-chip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, AnyRate, AVR, AVR logo, AVR Freaks, BeaconThings, BitCloud, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KEELOQ, KEELOQ logo, Kleer, LANCheck, LINK MD, maXStylus, maXTouch, MediaLB, megaAVR, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, Prochip Designer, QTouch, RightTouch, SAM-BA, SpyNIC, SST, SST Logo, SuperFlash, tinyAVR, UNI/O, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLight Load, IntelliMOS, mTouch, Precision Edge, and Quiet-Wire are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BodyCom, chipKIT, chipKIT logo, CodeGuard, CryptoAuthentication, CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit Serial Programming, ICSP, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, Mindi, MiWi, motorBench, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PureSilicon, QMatrix, RightTouch logo, REAL ICE, Ripple Blocker, SAM-ICE, Serial Quad I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, Total Endurance, TSHARC, USBCheck, VariSense, ViewSpan, WiperLock, Wireless DNA, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.
Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries.
GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.
All other trademarks mentioned herein are property of their respective companies.
Note the following details of the code protection feature on Microchip devices:
• Microchip products meet the specification contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and wafer fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The Company’s quality system processes and procedures are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and analog products. In addition, Microchip’s quality system for the design and manufacture of development systems is ISO 9001:2000 certified.
QUALITYMANAGEMENTSYSTEMCERTIFIEDBYDNV
== ISO/TS16949==
DS00001997B-page 32 2015-2016 Microchip Technology Inc.
AMERICASCorporate Office2355 West Chandler Blvd.Chandler, AZ 85224-6199Tel: 480-792-7200 Fax: 480-792-7277Technical Support: http://www.microchip.com/supportWeb Address: www.microchip.com
AtlantaDuluth, GA Tel: 678-957-9614 Fax: 678-957-1455
Austin, TXTel: 512-257-3370
BostonWestborough, MA Tel: 774-760-0087 Fax: 774-760-0088
ChicagoItasca, IL Tel: 630-285-0071 Fax: 630-285-0075