USB 2.0 Hub and Flash Media Card Controller Combo: General Description Features
USB 2.0 Hub and Flash Media Card Controller Combo: General Description Features
USB 2.0 Hub and Flash Media Card Controller Combo: General Description Features
Errata
An errata sheet, describing minor operational differences from the data sheet and recommended workarounds, may exist for cur-
rent devices. As device/documentation issues become known to us, we will publish an errata sheet. The errata will specify the
revision of silicon and revision of document to which it applies.
To determine if an errata sheet exists for a particular device, please check with one of the following:
• Microchip’s Worldwide Web site; http://www.microchip.com
• Your local Microchip sales office (see last page)
When contacting a sales office, please specify which device, revision of silicon and data sheet (include -literature number) you are
using.
1.1 Introduction
The USB2642 offers a USB 2.0 compliant, versatile, cost-effective and energy-efficient hi-speed hub controller with 2
downstream USB ports and an SD/MMC flash media card interface. The dedicated flash media reader is internally
attached to a 3rd downstream port of the hub as a USB compound device. This combo solution supports today’s popular
multi-format flash media card formats. The flash media interface can support sustained transfer rates exceeding 35 MB/
s if the media and host support those rates.
The USB2642 also provides I2C over USB. The I2C bridge allows for control of any I2C device operating at 50kHz clock.
The USB2642 will attach to an upstream port as either a full-speed or full-/hi-speed hub. The hub supports low-speed,
full-speed, and hi-speed (if operating as a full-/hi-speed hub) downstream devices on all of the enabled downstream
ports.
All required resistors on the USB ports are integrated into the hub. This includes all series termination resistors on D+
and D- pins and all required pull-down and pull-up resistors. The over-current sense inputs for the downstream facing
ports have internal pull-up resistors.
The USB2642 includes programmable features such as:
PortMap which provides flexible port mapping and disable sequences. The downstream ports of a USB2642 hub can
be reordered or disabled in any sequence to support multiple platform designs with minimum effort. For any port that is
disabled, the USB2642 automatically reorders the remaining ports to
match the USB host controller’s port numbering scheme.
PortSwap which adds per-port programmability to USB differential-pair
pin locations. PortSwap allows direct alignment of USB signals (D+/D-)
to connectors avoiding uneven trace length or crossing of the USB differ-
ential signals on the PCB.
PHYBoost which enables four programmable levels of USB signal drive
strength in downstream port transceivers. PHYBoost attempts to restore
USB signal integrity. The diagram on the right shows an example of Hi-
Speed USB eye diagrams before (PHYBoost at 0%) and after (PHYBoost
at 12%) signal integrity restoration in a compromised system environ-
ment.
FIGURE 2-1:
PLL Serial
Bus-Power Interface 8051
BLOCK DIAGRAM
Upstream SFR
Serial
Interface I2C I2C (2 pins)
Repeater Controller
Engine RAM
6K ADDR SPI SPI (4 pins)
ROM MAP
64K
PWR_FET0 (CRD_PWR)
Transaction
Port Controller Program GPIOs GPO1
Translator
Memory
USB2642 BLOCK DIAGRAM
I/O Bus
XDATA BRIDGE
+ BUS ARBITER
EP0 TX
EP0 RX
3K BUS
total RAM
INTFC
Routing & Port Re-Ordering Logic AUTO_CBW
EP2
EP2 RX
RX PROC
EP2 TX
BUS FMDU
INTFC CTL
Port #3 Port #2
OC OC
Sense Sense SIE BUS
PHY Switch
PHY Switch
BRIDGE INTFC
CTL FMI
Driver Driver
SD/
MMC
DS00001578C-page 6
USB2642
USB2642
3.0 USB2642 PIN CONFIGURATION
VDD33 (OTP)
CRD_PWR
VDD33
VDD33
TEST2
TEST1
SD_D2
SD_D3
SD_D4
SDA
SCL
NC
36
35
34
33
32
31
30
29
28
27
26
25
GPO1 37 24 SD_CMD
RESET_N 38 23 SD_D5
VBUS_DET 39 22 REG_EN
TEST0 40 21 SD_CLK
VDDA33 41
USB2642 20 SD_D6
USBUP_DP 42 19 SD_D7
USBUP_DM 43 18 SD_D0
XTAL2 44 17 SD_D1
45 16
XTAL1 (CLKIN)
e3 VDD33
VDD18PLL 46 15 VDD18
RBIAS 47 14 SD_nCD
VDDA33 48 13 SD_WP
10
11
12
1
2
3
4
5
6
7
8
9
Ground Pad
USBDN_DM2
USBDN_DM3
VDDA33
PRTCTL2
PRTCTL3
USBDN_DP2
USBDN_DP3
VDD33
SPI_CE_N
SPI_DI
SPI_CLK/SCL_EP
SPI_DO/SDA_EP/SPI_SPD_SEL
(must be connected
to VSS)
SCL SDA
MISC (7 pins)
POWER (6 pins)
Total 48
SPI Interface
SPI_CE_N 8 O12 SPI Chip Enable
This is the active low chip enable output. If the SPI interface is enabled,
drive this pin high in power down states.
SPI_CLK/ 9 I/O12 SPI Clock
This is the SPI clock out to the serial ROM. See Section 5.4, "ROM Boot
Sequence" for diagram and usage instructions.
During reset, this pin is driven low.
SCL_EP When configured, this is the I²C EEPROM clock pin.
Digital/Power/Ground
VDD18 15 - 1.8 V Digital Core Power Bypass
This pin requires an external bypass capacitor of 1.0 µF.
If REG_EN is low, this pin serves as a power supply (1.8 V) for the device.
VDD33 12 - 3.3 V Power and Regulator Input
16
25 • 48QFN - Pin 16 requires an external bypass capacitor of 4.7 µF mini-
34 mum.
VDD33 (OTP) 26 - 3.3 V Power
5V
PRTCTL3
OCS
USB Power
Switch
EN
USB
USB2642 Device
5V
PRTCTL2
OCS
USB Power
Switch
EN
USB
Device
FIGURE 5-2: PORT POWER CONTROL WITH SINGLE POLY FUSE AND MULTIPLE LOADS
5V
PRTCTL3
USB
Device
USB2642
5V
PRTCTL2
USB
Device
When using a single poly fuse to power all devices, note that for the ganged situation, all power control pins must be
tied together.
FIGURE 5-3: PORT POWER WITH GANGED CONTROL WITH POLY FUSE
5V
USB2642
PRTCTL2 USB USB
Device Device
SPI_CE_N CE#
SPI_CLK / SCL_EP CLK
Symbol Description
IP Input enabled
Z Hardware disables pad. Both output driver and input buffers are disabled.
Reset State
Pin Pin Name
Input/ PU/
Function
Output PD
1 USBDN_DM2 USBDN_DM2 IP PD
2 USBDN_DP2 USBDN_DP2 IP PD
3 USBDN_DM3 USBDN_DM3 IP PD
4 USBDN_DP3 USBDN_DP3 IP PD
6 PRTCTL2 PRTCTL 0 -
7 PRTCTL3 PRTCTL 0 -
8 SPI_CE_N SPI_CE_N 1 -
9 SPI_CLK/SCL_EP IO 0 -
10 SPI_DO/SDA_EP/SPI_SPD_SEL IO 0 -
11 SPI_DI SPI_DI IP PD
13 SD_WP IO 0 -
14 SD_nCD IO IP PU
17 SD_D1 none Z -
Reset State
Pin Pin Name
Input/ PU/
Function
Output PD
18 SD_D0 none Z -
19 SD_D7 none Z -
20 SD_D6 none Z -
21 SD_CLK none Z -
22 REG_EN none IP PU
23 SD_D5 none Z -
24 SD_CMD none Z -
27 TEST1 none Z -
28 TEST2 none Z -
29 SDA IO IP PU
30 SD_D4 none Z -
31 NC GPIO IP PU
32 SD_D3 none Z -
33 SD_D2 none Z -
35 CRD_PWR IO Z -
36 SCL IO 0 -
37 GPO1 GPO 0 -
38 RESET_N RESET_N IP -
39 VBUS_DET VBUS_DET IP -
40 TEST0 TEST IP PD
42 USBUP_DP USBUP_DP Z -
43 USBUP_DM USBUP_DM Z -
7.1 Hub
Microchip’s USB2642 hub is fully compliant with the Universal Serial Bus 2.0 Specification (References). See
Chapter 11 (Hub Specification) for general details regarding hub operation and functionality.
The hub provides a single Transaction Translator (TT) shared by both downstream ports. The TT contains 4 non-peri-
odic buffers.
A0h-A3h rsvd
A6h-BEh rsvd
D8h-DAh rsvd
123h-129h rsvd
12Ah-145h rsvd
Dynamic Number of
146h DYN_NUM_ EXT_LUN 00h
Extended LUNs
147h-14Bh LUN_DEV_MAP LUN to Device Mapping FFh, FFh, FFh, FFh, FFh
14Ch-17Bh rsvd
Note that the following applies to the system values and descriptions:
• rsvd = reserved for internal use; do not write to these registers
Note 1: Refer to the USB 2.0 Specification (References) for other language codes.
2: This register value must not be changed from the default value.
F5h rsvd
F7h-FBh rsvd
25:0 USB_SER_NUM Maximum string length is 12 hex digits. Must be unique to each device.
1:0 USB_VID This ID is unique for every vendor, where the vendor ID is assigned by the
USB Implementer’s Forum.
1:0 USB_PID This ID is unique for every product, where the product ID is assigned by the
vendor.
59:0 USB_PRD_STR This string is used during the USB enumeration process by Windows®. The
maximum string length is 29 characters.
7:0 USB_BM_ATT Self- or Bus-Power: Selects between self- and bus-powered operation.
The hub is either self-powered (draws less than 2 mA of upstream bus power)
or bus-powered (limited to a 100 mA maximum of upstream power prior to
being configured by the host controller).
When configured as a bus-powered device, the Microchip hub consumes less
than 100 mA of current prior to being configured. After configuration, the bus-
powered Microchip hub (along with all associated hub circuitry, any embed-
ded devices if part of a compound device, and 100 mA per externally avail-
able downstream port) must consume no more than 500 mA of upstream
VBUS current. The current consumption is system dependent, and the OEM
must ensure that the USB 2.0 specifications are not violated.
When configured as a self-powered device, <1 mA of upstream VBUS current
is consumed and all ports are available, with each port being capable of
sourcing 500 mA of current.
80 = Bus-powered operation
C0 = Self-powered operation
A0 = Bus-powered operation with remote wake-up
E0 = Self-powered operation with remote wake-up
7:0 USB_MAX_PWR USB Max Power per USB Specification (References). Do NOT set this value
greater than 100 mA.
Bit
Byte Name Description
Number
5 Always read as 0
7 Always read as 0
6 Always read as 0
1 Always read as 0
3:0 rsvd
25:0 rsvd
6:0 DEV3_ID_STR These bytes are used to specify the LUN descriptor returned by the device.
These bytes are used in combination with the LUN to device mapping bytes
in applications where the OEM wishes to reorder and rename the LUNs. If
this device is configured to be part of a COMBO LUN then this string is
ignored for the appropriate CLUNx_ID_STR.
7:0 INQ_VEN_STR If bit 4 of the 1st attribute byte is set, the device will use these strings in
response to a USB inquiry command, instead of the USB descriptor
manufacturer and product ID strings.
4:0 INQ_PRD_STR If bit 4 of the 1st attribute byte is set, the device will use these strings in
response to a USB inquiry command, instead of the USB descriptor
manufacturer and product ID strings.
7:0 DYN_NUM_LUN This byte is used to specify the number of LUNs the device exposes to the
host. These bytes are also used for icon sharing by assigning more than one
LUN to a single icon. This is used in applications where the device utilizes
a combo socket and the OEM wishes to have only a single icon displayed
for one or more interfaces.
If this field is set to FF, the program assumes that you are using the default
value and icons will be configured per the default configuration.
3:0 LUN_DEV_MAP These bytes are used to specify the number of LUNs the device exposes to
the host. These bytes are also used for icon sharing by assigning more than
one LUN to a single icon. This is used in applications where the device
utilizes a combo socket and the OEM wishes to have only a single icon
displayed for one or more interfaces.
If this field is set to FF, the program assumes that you are using the default
values and LUNs will be configured per the default configuration.
2:0 rsvd
2:0 SD_MMC_BUS_ The values for these bytes are set internally and must not be altered.
TIMING
7:0 VID_LSB Least Significant Byte of the Vendor ID. This is a 16-bit value that uniquely
identifies the vendor of the user device (assigned by USB Implementer’s
Forum).
7:0 VID_MSB Most Significant Byte of the Vendor ID. This is a 16-bit value that uniquely
identifies the vendor of the user device (assigned by USB Implementer’s
Forum).
7:0 PID_LSB Least Significant Byte of the Product ID. This is a 16-bit value that the vendor
can assign that uniquely identifies this particular product.
7:0 PID_MSB Most Significant Byte of the Product ID. This is a 16-bit value that the vendor
can assign that uniquely identifies this particular product.
7:0 DID_LSB Least Significant Byte of the Device ID. This is a 16-bit device release
number in BCD (binary coded decimal) format.
7:0 DID_MSB Most Significant Byte of the Device ID. This is a 16-bit device release
number in BCD format.
6 rsvd
4 rsvd
3 EOP_DISABLE EOP Disable: Disables EOP generation of EOF1 when in Full-Speed mode.
During FS operation only, this permits the hub to send EOP if no
downstream traffic is detected at EOF1. See Section 11.3.1 of the USB 2.0
Specification (References) for additional details.
0 : An EOP is generated at the EOF1 point if no traffic is detected.
1 : EOP generation at EOF1 is disabled (normal USB operation).
Generation of an EOP at the EOF1 point may prevent a host controller
(operating in FS mode) from placing the USB bus in suspend.
2:1 CURRENT_SNS Over-Current Sense: Selects current sensing on a port-by-port basis, all
ports ganged, or none (only for bus-powered hubs). The ability to support
current sensing on a per port or ganged basis is dependent upon the
hardware implementation.
00 : ganged sensing (all ports together)
01 : individual (port-by-port)
1x : over-current sensing is not supported (must only be used with bus-
powered configurations)
0 PORT_PWR Port Power Switching: Enables power switching on all ports simultaneously
(ganged), or port power is individually switched on and off on a port-by-port
basis (individual). The ability to support power enabling on a port or ganged
basis is dependent upon the hardware implementation.
0 : ganged switching (all ports together)
1 : individual port-by-port switching
7:6 rsvd
3 COMPOUND Compound Device: Allows OEM to indicate that the hub is part of a
compound device per the USB 2.0 Specification. The applicable port(s) must
also be defined as having a “non-removable device”.
When configured via strapping options, declaring a port as non-removable
automatically causes the hub controller to report that it is part of a compound
device.
0 : no
1 : yes, the hub is part of a compound device
2:0 rsvd
7:4 rsvd
3 PRTMAP_EN Port Mapping Enable: Selects the method used by the hub to assign port
numbers and disable ports.
0 : Standard Mode. Strap options or the following registers are used to define
which ports are enabled, and the ports are mapped as port ‘n’ on the hub is
reported as port ‘n’ to the host, unless one of the ports is disabled, then the
higher numbered ports are remapped in order to report contiguous port
numbers to the host.
Register 300Ah: Port disable for self-powered operation (reset = 0x00).
Register 300Bh: Port disable for bus-powered operation (reset = 0x00).
1 : PortMap mode. The mode enables remapping via the registers defined
below.
Register 30FBh: PortMap 12 (reset = 0x00)
Register 30FCh: PortMap 3 (reset = 0x00)
2:0 rsvd
7:0 MAX_PWR_SP Value in 2 mA increments that the hub consumes from an upstream port
(VBUS) when operating as a self-powered hub. This value includes the hub
silicon along with the combined power consumption (from VBUS) of all
associated circuitry on the board. This value also includes the power
consumption of a permanently attached peripheral if the hub is configured
as a compound device, and the embedded peripheral reports 0 mA in its
descriptors.
Note: The USB 2.0 Specification (References) does not permit this value
to exceed 100 mA.
7:0 MAX_PWR_BP Value in 2 mA increments that the hub consumes from an upstream port
(VBUS) when operating as a bus-powered hub. This value includes the hub
silicon along with the combined power consumption (from VBUS) of all
associated circuitry on the board. This value also includes the power
consumption of a permanently attached peripheral if the hub is configured
as a compound device, and the embedded peripheral reports 0 mA in its
descriptors.
Note: The USB 2.0 Specification does not permit this value to exceed
100 mA.
7:0 HC_MAX_C_SP Value in 2 mA increments that the hub consumes from an upstream port
(VBUS) when operating as a self-powered hub. This value includes the hub
silicon along with the combined power consumption (from VBUS) of all
associated circuitry on the board. This value does NOT include the power
consumption of a permanently attached peripheral if the hub is configured
as a compound device.
Note: The USB 2.0 Specification (References) does not permit this value
to exceed 100 mA.
A value of 50 (decimal) indicates 100 mA, which is the default value.
7:0 HC_MAX_C_BP Value in 2 mA increments that the hub consumes from an upstream port
(VBUS) when operating as a bus-powered hub. This value will include the
hub silicon along with the combined power consumption (from VBUS) of all
associated circuitry on the board. This value will NOT include the power
consumption of a permanently attached peripheral if the hub is configured
as a compound device.
A value of 50 (decimal) would indicate 100 mA, which is the default value.
7:0 POWER_ON_TIME The length of time that it takes (in 2 ms intervals) from the time the host
initiated power-on sequence begins on a port until power is adequate on that
port. If the host requests the power-on time, the system software uses this
value to determine how long to wait before accessing a powered-on port.
7:2 rsvd
1:0 BOOST_IOUT USB electrical signaling drive strength boost bit for the upstream port ‘A’.
00 : normal electrical drive strength = no boost
01 : elevated electrical drive strength = low (approximately 4% boost)
10 : elevated electrical drive strength = medium (approximately 8% boost)
11 : elevated electrical drive strength = high (approximately 12% boost)
Note: “Boost” could result in non-USB Compliant parameters. OEM
should use a 00 value unless specific implementation issues
require additional signal boosting to correct for degraded USB
signaling levels.
7:6 rsvd
5:4 BOOST_IOUT_3 Upstream USB electrical signaling drive strength boost bit for downstream
port 3.
00 : normal electrical drive strength = no boost
01 : elevated electrical drive strength = low (approximately 4% boost)
10 : elevated electrical drive strength = medium (approximately 8% boost)
11 : elevated electrical drive strength = high (approximately 12% boost)
3:2 BOOST_IOUT_2 Upstream USB electrical signaling drive strength boost bit for downstream
port 2.
00 : normal electrical drive strength = no boost
01 : elevated electrical drive strength = low (approximately 4% boost)
10 : elevated electrical drive strength = medium (approximately 8% boost)
11 : elevated electrical drive strength = high (approximately 12% boost)
“Boost” could result in non-USB Compliant parameters. OEM should use a
00 value unless specific implementation issues require additional signal
boosting to correct for degraded USB signaling levels.
1:0 rsvd
7:0 PRT_SWP Swaps the upstream and downstream USB DP and DM pins for ease of
board routing to devices and connectors.
0 : USB D+ functionality is associated with the DP pin and D- functionality
is associated with the DM pin.
1 : USB D+ functionality is associated with the DM pin and D- functionality
is associated with the DP pin.
Bit 7 = rsvd
Bit 6 = rsvd
Bit 5 = rsvd
Bit 4 = rsvd
Bit 3 = controls physical port 3
Bit 2 = controls physical port 2
Bit 1 = rsvd
Bit 0 = controls physical port 0
0001 rsvd
0010 rsvd
0011 rsvd
7:0 rsvd
7:0 rsvd
4:0 NVSTORE_SIG This signature is used to verify the validity of the data in the first 256 bytes of
the configuration area. The signature must be set to ATA2.
6:0 CLUN0_ID_STR If the LUN to device mapping bytes have configured this LUN to be a combo
LUNs, then these strings will be used to identify the LUN rather than the
device identifier strings.
6:0 CLUN1_ID_STR If the LUN to device mapping bytes have configured this LUN to be a combo
LUNs, then these strings will be used to identify the LUN rather than the
device identifier strings.
6:0 CLUN2_ID_STR If the LUN to device mapping bytes have configured this LUN to be a combo
LUNs, then these strings will be used to identify the LUN rather than the
device identifier strings.
6:0 CLUN3_ID_STR If the LUN to device mapping bytes have configured this LUN to be a combo
LUNs, then these strings will be used to identify the LUN rather than the
device identifier strings.
6:0 CLUN4_ID_STR If the LUN to device mapping bytes have configured this LUN to be a combo
LUNs, then these strings will be used to identify the LUN rather than the
device identifier strings.
27:0 rsvd
7:0 DYN_NUM_ These bytes are used to specify the number of LUNs the device exposes to
EXT_LUN the host. These bytes are also used for icon sharing by assigning more than
one LUN to a single icon. This is used in applications where the device
utilizes a combo socket and the OEM wishes to have only a single icon
displayed for one or more interfaces.
If this field is set to FF, the program assumes that you are using the default
value and icons will be configured per the default configuration.
4:0 LUN_DEV_MAP These bytes are used to specify the number of LUNs the device exposes to
the host. These bytes are also used for icon sharing by assigning more than
one LUN to a single icon. This is used in applications where the device
utilizes a combo socket and the OEM wishes to have only a single icon
displayed for one or more interfaces.
If this field is set to FF, the program assumes that you are using the default
value and icons will be configured per the default configuration.
45:0 rsvd
3:0 NVSTORE_SIG2 This signature is used to verify the validity of the data in the upper 256 bytes
if a 512-byte EEPROM is used, otherwise this bank is a read-only configuration
area. The signature must be set to ecf1.
Note: Extensions to the I2C Specification are not supported. The device acts as the master and generates the
serial clock SCL, controls the bus access (determines which device acts as the transmitter and which
device acts as the receiver), and generates the START and STOP conditions.
7.6 Reset
There are two different resets that the device experiences. One is a hardware reset (either from the internal POR
(power-on reset) circuit or via the RESET_N pin) and the second is a USB bus reset.
Start
Hardware Device 8051 Sets Attach
USB Reset completion
reset Recovery/ Configuration USB Idle
recovery request
asserted Stabilization Registers Upstream
response
t4
t1 t2 t3 t5 t6 t7
RESET_N
VSS
Note 7-1 All power supplies must have reached the operating levels mandated in Section 8.0, "DC
Parameters", prior to (or coincident with) the assertion of RESET_N.
Note: The hub does not propagate the upstream USB reset to downstream devices.
Stresses above the specified parameters may cause permanent damage to the device. This is a stress rating only. Func-
tional operation of the device at any condition above those indicated in the operation sections of this specification is not
implied. When powering this device from laboratory or system power supplies the absolute maximum ratings must not
be exceeded or device failure can result. Some power supplies exhibit voltage spikes on their outputs when the AC
power is switched on or off. In addition, voltage transients on the AC power line may appear on the DC output. When
this possibility exists, a clamp circuit should be used.
3.3 V supply voltage VDD33, 3.0 3.6 V A 3.3 V regulator with an output
VDDA33 tolerance of ±1% must be used if
the output of the internal power
FET’s must support a 5%
tolerance.
Voltage
Voltage
tRT tRT
VDD33 3.3 V VDD18 1.8 V 100%
100%
90% 90%
10% 10%
VSS VSS
Thermal Resistance ΘJA 28 °C/W Measured from the die to the ambient air
Pull Down PD 72 µA
Pull Up PU 58 µA
Input Leakage
(All I and IS buffers)
Pull Down PD 72 µA
Pull Up PU 58 µA
IO-U (Note 6)
I-R (Note 7)
8.5 Capacitance
TA = 25°C; fc = 1 MHz; VDD33 = 3.3 V, VDD18 = 1.8 V
Limits
Parameter Symbol Unit Test Conditions
Min Typ Max
XTAL Pin Input Capacitance CXTAL - - 4 pF All pins (except USB pins
and pins under test) are tied
Input Capacitance CIN - - 10 pF to AC ground.
9.1 Oscillator/Crystal
Parallel Resonant, Fundamental Mode, 24 MHz ± 350 ppm.
C 1 = 2 x (C L – C 0) – C S1
C 2 = 2 x (C L – C 0) – C S2
Note 9-1 C0 is usually included (subtracted by the crystal manufacturer) in the specification for CL and should
be set to ‘0’ for use in the calculation of the capacitance formulas in Figure 9-2. However, the OEM
PCB itself may present a parasitic capacitance between XTAL1 and XTAL2. For an accurate
calculation of C1 and C2, take the parasitic capacitance between traces XTAL1 and XTAL2 into
account.
Note 9-2 Each of these capacitance values is typically approximately 18 pF.
FIGURE 10-1:
DS00001578C-page 49
FIGURE 10-2:
DS00001578C-page 50
USB2642
Acronym Description
EOF End of (micro) Frame
EOP End of Packet
FMC Flash Media Controller
FS USB Full-Speed
HS USB Hi-Speed
I2C™ Inter-Integrated Circuit
LS USB Low-Speed
LUN Logical Unit Number
MMC MultiMediaCard
OCS Over-current Sense
PHY Physical Layer
PLL Phase-Locked Loop
SDC Secure Digital Controller
I2C is a trademark of Philips Corporation.
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 docu-
ment.
Technical support is available through the web site at: http://microchip.com/support
Special: SEU = Single Event Upset Note 1: Tape and Reel identifier only appears in the
(Low Alpha Emissions Package) catalog part number description. This
identifier is used for ordering purposes and is
not printed on the device package. Check
with your Microchip Sales Office for package
availability with the Tape and Reel option.
• 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.
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
Microchip 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, implic-
itly or otherwise, under any Microchip intellectual property rights.
Trademarks
The Microchip name and logo, the Microchip logo, dsPIC, FlashFlex, flexPWR, JukeBlox, KEELOQ, KEELOQ logo, Kleer, LANCheck,
MediaLB, MOST, MOST logo, MPLAB, OptoLyzer, PIC, PICSTART, PIC32 logo, RightTouch, SpyNIC, SST, SST Logo, SuperFlash and
UNI/O are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
The Embedded Control Solutions Company and mTouch are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Analog-for-the-Digital Age, BodyCom, chipKIT, chipKIT logo, CodeGuard, dsPICDEM, dsPICDEM.net, ECAN, In-Circuit Serial
Programming, ICSP, Inter-Chip Connectivity, KleerNet, KleerNet logo, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK,
MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, RightTouch logo, REAL ICE, SQI, Serial
Quad I/O, 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 trademarks 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.
© 2014-2015, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.
ISBN: 9781632771735
QUALITY MANAGEMENT SYSTEM Microchip received ISO/TS-16949:2009 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
CERTIFIED BY DNV Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
== ISO/TS 16949 ==
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.