4.1 Pin Assignm e n ts ...................... .. ............. .. ........................... .. ............. ... ............. .. .. ..................9
4.2 I/O Registe r S u m ma ry ......... .............. .. ............. .. ............. ... ............. .. ............. ... .. ....................10
4.3 Instruction S e t S u mm a r y ........... .. .. ............. ... ............. .. .. ............. ... ............. .. ............. ... .. . ........11
5.0 PROGRAMM I N G M OD E L .................. .. .............. .. .. ............. .. .............. .. ............. .. ... ............. .. .......12
5.1 14-bit Program Counter ............................... ..................... ...................................... .................12
5.1.1 Program Memory Organization ......................................................................................................13
5.6.1 Data (Immediate) ...........................................................................................................................15
5.6.2 Direct ..............................................................................................................................................15
Figure 9-1. Blo ck Di a g ra m of a GPIO Pin ................. ............. .. .. ............. ... ............. .. .. .............. .. .........18
Figure 9-2. Por t 0 Dat a ..... .. ............. .. .............. .. .. ............. ... ............. .. .. .............. .. ............. ..................18
Figure 9-3. Por t1 Da ta ...... ............. .. .............. .. .. ............. .. .............. .. .. ............. ... ............. .. ..................18
Figure 9-4. Por t 2 Dat a ..... .. ............. .. .............. .. .. ............. ... ............. .. .. .............. .. ............. ..................18
Figure 9-6. GPIO C o n fig u r a tio n R e g is te r .... ... ............. .. .......................... ... ............. .. ............. ... .. .........19
Figure 9-5. Por t 3 Dat a ..... .. ............. .. .............. .. .. ............. ... ............. .. .. .............. .. ............. ..................19
Figure 9-7. Por t 0 Int e rr u p t E na b l e .... .............. .. ............. .. .............. .. .. ............. ... ............. .. ..................20
Figure 9-8. Por t 1 Int e rr u p t E na b l e .... .............. .. ............. .. .............. .. .. ............. ... ............. .. ..................20
Figure 10-1. Ti m e r L SB Re g is t e r .............. .. .............. .. .. ............. .. .............. .. .. ............. ... ......................21
Figure 10-2. Ti m e r MS B R egister .................... .. .. ............. ... ............. .. .. .............. .. ............. .. ................21
Figure 9-9. Por t 2 Int e rr u p t E na b l e .... .............. .. ............. .. .............. .. .. ............. ... ............. .. ..................21
Figure 9-10. Port 3 Interrupt Enable ....................................................................................................21
Figure 10-3. Ti m e r Bl o c k D ia g r a m .............. .............. .. .. ............. .. .............. .. .......................... ... ...........22
Figure 11-1. I
Figure 12-1. I
Figure 12-2. I
Figure 13-1. Processor Status and Control Register ...........................................................................24
Figure 14-1. Global Interrupt Enable Register .....................................................................................25
Figure 14-2. USB Endpoint Interrupt Enable Register .........................................................................26
Figure 14-3. Interrupt Controller Function Diagram .............................................................................27
Figure 14-4. GP IO In t er ru p t Structure ................. ............. ... ............. .. .. .............. .. ............. .. .. .............. 29
Figure 16-1. Hub Ports Connect Status ...............................................................................................31
Figure 16-4. Hub Downstrea m P o rts Control Re gi s te r .... . ... ............. .. ............. ... ............. .. ............. .. ... 33
Figure 16-5. Hub P o rt s F o rce Low Registe r .... .. ............. .. .............. .. .. ............. ... ............. .. .. ................33
Figure 16-6. Hub P o rt s F o rce Low Registe r .... .. ............. .. .............. .. .. ............. ... ............. .. .. ................33
Figure 16-7. Hub P o rts SE0 Status Re g i ster .................... ... ............. .. ............. ... ............. .. .. ................33
Figure 16-8. Hub P o rt s D a ta R e g is te r .......................... .. .. .............. .. ............. .. .............. .. .. ..................34
•I/O ports
—Three GPIO ports (Port 0 to 2) capable of sinking 7 mA per pin (typical)
—An additional GPIO port (Port 3) capable of sinking 12 mA per pin (typical) for high current requirements: LEDs
—Higher current drive achievable by connecting multiple GPIO pins together to drive a common output
—Each GPIO port can be configured as input s with internal pull-ups or open drain output s or traditional CMOS outputs
—Maskable interrupts on all I/O pins
• 12-bit free-running timer with one microsecond clock ticks
• Watchdog timer (WDT)
• Internal Power-on Reset (POR)
• USB Specification compliance
—Conforms to USB Specification, Version 1.1
—Conforms to USB HID Specification, Version 1.1
—Supports one or two device addresses with up to 5 user-configured endpoints
Up to two 8-byte control endpoints
Up to four 8-byte data endpoints
Up to two 32-byte data endpoints
—Integrated USB transceivers
—Supports seven (CY7C65013) or four (CY7C65113) downstream USB ports
—GPIO pins can provide individual power control outputs for each downstream USB port
—GPIO pins can provide individual port over current inputs for each downstream USB port
• Improved output drivers to reduce electromagnetic interference (EMI)
• Operating voltage from 4.0V to 5.5V DC
• Operating temperature from 0° to 70° C
• CY7C65013 available in 48-pin PDIP (-PC) or 48-pin SSOP (-PVC) packages
• CY7C65113 available in 28-pin SOIC (-SC) or 28-pin PDIP (-PC) packages
• Industry-standard programmer support.
2
C-compatible Controller (100 kHz) enabled through General-purpose I/O (GPIO) pins
CY7C6511
Document #: 38-08002 Rev. *BPage 6 of 51
Page 7
CY7C6501
3
3
2.0 Functional Overview
The CY7C65x13 device s are one-time pro grammable 8- bit microc ontrollers with a built- in 12-M bp s USB hu b t hat su pport s up to
seven downstream ports. The microcontroller instruction set has been optimized specifically for USB operations, although the
microcontrollers can be used for a variety of non-USB embedded applications.
GPIO
CY7C65013
The CY7C65013 featur es 22 GPIO pin s to support USB and other applicatio ns. The I/O p ins are grouped int o four port s (P0[7:0],
P1[7:4,2:0], P2[7:3], P3[1:0 ]) where eac h port can be co nfigured as inputs with internal pul l-ups, op en drain outpu ts, or tradi tional
CMOS outputs. Ports 0 to 2 are rated at 7 mA per pin (typical) sink current. Port 3 pins are rated at 12 mA per pin (typical) sink
current, which allows these pins to drive LEDs. Multiple GPIO pins can be connected together to drive a single output for more
drive current capa city. Additionally, ea ch I/O pin c an be u sed to genera te a GPI O inte rrupt to t he micr ocon troller. All of the GPIO
interrupts all share the same “GPIO” interrupt vector.
CY7C65113
The CY7C65113 has 11 GPIO pins (P0[7:0], P1[2:0]), both rated at 7 mA per pin (typical) sink current. Multiple GPIO pins can
be connected together to drive a single output for more drive current capacity.
Clock
The microcontroller us es an ex tern al 6 -MH z cry st a l an d an i nter nal oscillator to provide a referenc e to an inte rnal phase-locked
loop (PLL)-based clock generator. This technology allows the customer application to use an inexpensive 6-MHz fundamental
crystal that red uces the clock-related no ise emissions (EMI). A PLL cl ock generator provides the 6 -, 12-, and 48-MHz clock s ignals
for distribution within the microcontroller.
Memory
The CY7C65013 and the CY7C65113 are offered with 8 KB of PROM.
Power-on Reset, Watchdog, and Free-running Timer
These parts in clude power-o n reset logic , a Wa tchdog timer, and a 12-bit free-running timer. The PO R logic detect s when power
is applied to the device, resets the logic to a known state, and begins executing instructions at PROM address 0x0000. The
Watchdog timer is u sed to ensure the mi crocontrol ler rec overs afte r a perio d of ina ctivi ty. The firmware may become inactive for
a variety of reasons, including errors in the code or a hardware failure such as waiting for an interrupt that never occurs.
2
C
I
2
The microcontroller can communicate with external electronics through the GPIO pins. An I
dates a 100-kHz serial link with an external device.
Timer
The free-running 12-bit timer clocked at 1 MHz provides two interrupt sources, 128-µs and 1.024-ms. The timer can be used to
measure the duration of an event under firmware control by reading the timer at the start of the event and after the event is
complete. The difference between the two readings indicates the duration of the event in microseconds. The upper four bits of
the timer are lat ched into an internal regi ster when the firmware reads the lower e ight bits. A read from th e upper four bits actually
reads data from the inte rnal register , in stead of the ti mer . This featur e eliminates the ne ed for firmware to t ry to compensate if the
upper four bits increment immediately after the lower eight bits are read.
Interrupts
The microcontroller su ppo rts ten maskable interrupt s in the vectored interrupt contro lle r. Interrupt sources include the USB Bus
Reset interrupt, the 128-µs (bit 6 ) and 1.024-ms (bi t 9) outpu ts from the free -running ti mer, five USB end points, the USB h ub, the
GPIO ports, and the I
from LOW ‘0’ to HIGH ‘1’. Th e USB endpoi nts i nterrupt afte r the USB h ost has w ritten dat a to the endpoint FIFO or after the USB
controller sends a p ac ke t to th e U SB hos t. T he GPIO ports also hav e a le vel of masking to select w hic h GPI O inp uts can cause
a GPIO interrupt. Input transition polarity can be programmed for each GPIO port as part of the port configuration. The interrupt
polarity can be rising edge (‘0’ to ‘1’) or falling edge (‘1’ to ‘0’).
USB
The CY7C65013 and CY7C65113 include an integrated USB Serial Interface Engine (SIE) that supports the integrated peripherals and the hub controller function. The hardware supports up to two USB device addresses with one device address for the
hub (two endpoint s) and a device address for a compoun d device (three end points). The SIE a llows the USB host to c ommunicate
with the hub and fu nctions integrated into the microcon troller . The CY7C651 13 p art includes a 1:4 hub repeater with one upstream
port and four downstream ports, while the CY 7C65013 part inclu des a 1:7 hub repeater . The USB Hub allows power management
control of the downstream ports by using GPIO pins assigned by the user firmware. The user has the option of ganging the
downstream ports together with a single pair of power management pins, or providing power management for each port with four
(CY7C65113) or seven (CY7C65013) pairs of power management pins.
2
C-compatible master mode interface. The timer bits cause an interrupt (if enabled) when the bit toggles
C-compatible interface ac commo-
CY7C6511
Document #: 38-08002 Rev. *BPage 7 of 51
Page 8
CY7C6501
3
3
Logic Block Diagram
CY7C6511
6-MHz crystal
PLL
48 MHz
Clock
Divider
6 MHz
12 MHz
12-MHz
8-bit
CPU
PROM
8 KB
RAM
256 byte
12-bit
Timer
8-bit Bus
USB
SIE
Interrupt
Controller
GPIO
PORT 0
P0[0]
P0[7]
USB
Transceiver
Repeater
D+[0]
Upstream
USB Port
D–[0]
Downstream USB Ports
USB
Transceiver
USB
Transceiver
USB
Transceiver
USB
Transceiver
CY7C65013 only
Power management under firmware
control using GPIO pins
D+[1]
D–[1]
D+[4]
D–[4]
D+[5]
D–[5]
D+[7]
D–[7]
Watchdog
Timer
Power-on
Reset
GPIO
PORT 1
GPIO
PORT 2
GPIO
PORT 3
I2C comp.
Interface
2
*I
C-compatible interface enabled by firmware through
P2[1:0] or P1[1:0]
P1[0]
P1[2]
P2[7]
P2[3]
High Current
P3[1]
Outputs
P3[0]
CY7C65013 only
SCLK
SDATA
Document #: 38-08002 Rev. *BPage 8 of 51
Page 9
3
3
3.0 Pin Configurations
XTALOUT
XTALIN
48-pin SSOP
P1[1]
P1[5]
P1[7]
P3[1]
D+[0]
D–[0]
GND
D+[1]
D–[1]
V
REF
D+[2]
D–[2]
P2[3]
GND
P2[5]
D+[7]
D–[7]
P2[7]
P0[7]
P0[5]
P0[3]
P0[1]
CY7C65013
48
1
2
47
46
3
4
45
5
44
43
6
42
7
41
8
9
40
39
10
11
38
37
12
13
36
35
14
34
15
16
33
17
32
31
18
19
30
29
20
21
28
22
27
23
26
25
24
CY7C6501
Top View
CY7C65113
28-pin SOIC
V
CC
P1[0]
P1[2]
P1[4]
P1[6]
P3[0]
D–[3]
D+[3]
GND
D–[4]
D+[4]
V
REF
D–[5]
D+[5]
GND
P2[4]
D–[6]
D+[6]
P2[6]
V
PP
P0[0]
P0[2]
P0[4]
P0[6]
XTALOUT
XTALIN
V
GND
D+[0]
D–[0]
D+[1]
D–[1]
D+[2]
D–[2]
P0[7]
P0[5]
P0[3]
P0[1]
REF
1
28
V
2
3
4
5
6
7
8
9
10
11
12
13
14
CC
27
P1[1]
26
P1[0]
P1[2]
25
D–[3]
24
D+[3]
23
D–[4]
22
D+[4]
21
GND
20
19
V
PP
18
P0[0]
17
P0[2]
P0[4]
16
15
P0[6]
CY7C6511
4.0 Product Summary Tables
4.1Pin Assignments
Table 4-1. Pin Assignments
NameI/O48-pin28-pinDescription
D+[0], D–[0]I/O7, 85, 6Upstream port, USB differential data.
D+[1], D–[1]I/O10, 117, 8Downstream Port 1, USB differential data.
D+[2], D–[2]I/O13, 149, 10Downstream Port 2, USB differential data.
D+[3], D– [3]I/ O41, 4223, 24Downstream Port 3, US B differential data.
D+[4], D– [4]I/ O38, 3921, 22Downstream Port 4, US B differential data.
D+[5], D–[5]I/O35, 36Downstream Port 5, USB differential data.
D+[6], D–[6]I/O31, 32Downstream Port 6, USB differential data.
D+[7], D–[7]I/O18, 19Downstream Port 7, USB differential data.
P0I/OP1[7:0]
21, 25, 22, 26, 23, 27,
24, 28
P1I/OP1[7:4,2:0]
5, 44, 4, 45; 46, 3, 47
P2I/OP2[7:3]
20, 30, 17,33, 15
P3I/OP3[1:0]
6, 43
XTAL
IN
IN226-MHz crystal or external clock input.
P1[7:0]
11, 15, 12, 16, 13,
17, 14, 18
P1[2:0]
25, 27, 26
GPIO Port 0 capable of sinking 7 mA (typical).
GPIO Port 1 capable of sinking 7 mA (typical).
GPIO Port 2 capable of sinking 12 mA (typical).
GPIO Port 3, capable of sinking 12 mA (typical).
Document #: 38-08002 Rev. *BPage 9 of 51
Page 10
CY7C6501
3
3
Table 4-1. Pin Assignments (continued)
NameI/O48-pin28-pinDescription
XTAL
OUT
V
PP
V
CC
GND9, 16, 34, 404, 20Ground.
V
REF
4.2I/O Register Summary
I/O registers are accessed v ia the I/O Read (IORD) a nd I/O W rite (IOWR , IOWX) instructi ons. IORD reads data from the sel ected
port into the accumu lator . IOWR perform s the revers e; it wri tes dat a from the a ccumulator to the sel ected por t. Indexed I/O W rite
(IOWX) adds the co ntent s of X to t he add ress in th e ins tructio n to form the p ort add ress a nd wri tes da ta from th e acc umula tor t o
the specified port. Specifying address 0 (e.g., IOWX 0h) means the I/O register is selected solely by the contents of X.
All undefined registers are reserved. Do not write to reserved registers as this may cause an undefined operation or increased
current consumption during operation. When writing to registers with reserved bits, the reserved bits must be written with ‘0.’
Table 4-2. I/O Register Summary
Port 0 Data0x00R/WGPIO Port 0 Data 18
Port 1 Data0x01R/WGPIO Port 1 Data17
Port 2 Data0x02R/WGPIO Port 2 Data17
Port 3 Data0x03R/WGPIO Port 3 Data19
Port 0 Interrupt Enable0x04WInterrupt Enable for Pins in Port 019
Port 1 Interrupt Enable0x05WInterrupt Enable for Pins in Port 119
Port 2 Interrupt Enable0x06WInterrupt Enable for Pins in Port 219
Port 3 Interrupt Enable0x07WInterrupt Enable for Pins in Port 319
GPIO Configuration0x08R/WGPIO Port Configurations18
2
C Configuration0x09R/WI2C Position Configuration20
I
USB Device Address A0x10R/WUSB Device Address A36
EP A0 Counter Register0x11R/WUSB Address A, Endpoint 0 Counter 38
EP A0 Mode Register0x12R/WUSB Address A, Endpoint 0 Configuration 37
EP A1 Counter Register0x13R/WUSB Address A, Endpoint 1 Counter 38
EP A1 Mode Register0x14R/WUSB Address A, Endpoint 1 Configuration 38
EP A2 Counter Register0x15R/WUSB Address A, Endpoint 2 Counter 38
EP A2 Mode Register0x16R/WUSB Address A, Endpoint 2 Configuration 38
USB Status & Control0x1FR/WUSB Upstream Port Traffic Status and Control35
Global Interrupt Enable0x20R/WGlobal Interrupt Enable 25
Endpoint Interrupt Enable0x21R/WUSB Endpoint Interrupt Enables26
Interrupt Vector0x23RPending Interrupt Vector Read/Clear27
Timer (LSB)0x24RLower Eight Bits of Free-running Timer (1 MHz)20
Timer (MSB)0x25RUpper Four Bits of Free-running Timer 20
WDR Clear0x26WWatchdog Reset Clear17
2
C Control & Sta tus0x28R/WI2C Status and Control21
I
2
C Data0x29R/WI2C Data23
I
OUT116-MHz crystal out.
2919Programming voltage supply, tie to ground during normal
operation.
4828Voltage supply.
IN12, 373External 3.3V supply voltage for the down stream dif ferential
data output buffers and the D+ pull up.
Register NameI/O AddressRead/WriteFunctionPage
CY7C6511
Document #: 38-08002 Rev. *BPage 10 of 51
Page 11
CY7C6501
3
3
Table 4-2. I/O Register Summary (continued)
Register NameI/O AddressRead/WriteFunctionPage
Reserved0x30Reserved
Reserved0x31Reserved
Reserved0x32Reserved
Reserved0x38-0x3FReserved
USB Device Address B0x40R/WUSB Device Address B (not used in 5-endpoint mod e) 36
EP B0 Counter Register0x41R/WUSB Address B, Endpoint 0 Counter38
EP B0 Mode Register0x42R/WUSB Address B, Endpoint 0 Configuration, or
USB Address A, Endpoint 3 in 5-endpoint mode
EP B1 Counter Register0x43R/WUSB Address B, Endpoint 1 Counter38
EP B1 Mode Register0x44R/WUSB Address B, Endpoint 1 Configuration, or
USB Address A, Endpoint 4 in 5-endpoint mode
Hub Port Connect Status0x48R/WHub Downstream Port Connect Status31
Hub Port Enable0x49R/WHub Downstream Ports Enable32
Hub Port Speed0x4AR/WHub Downstream Ports Speed31
Hub Port Control (Ports [4:1])0x4BR/WHub Downstream Ports Control (Ports [4:1])33
Hub Port Control (Ports [7:5])0x4CR/WHub Downstream Ports Control (Ports [7:5])33
Hub Port Suspend0x4DR/WHub Downstream Port Suspend Control34
Hub Port Resume Status0x4ERHub Downstream Ports Resume Status35
Hub Ports SE0 Status0x4FRHub Downstream Ports SE0 Status33
Hub Ports Data0x50RHub Downstream Ports Differential Data34
Hub Downstream Force Low0x51R/WHub Downstream Ports Force LOW (Ports [1:4])33
Hub Downstream Force High0x52R/WHub Downstream Ports Force HIGH (Ports [5:7])33
Processor Status & Control0xFFR/WMicroprocessor Status and Control Register24
CY7C6511
37
38
4.3Instruction Set Summary
Refer to the CYASM Assembler User’s Guide for more details. Note that conditional jump instructions (i.e. JC, JNC, JZ, JNZ)
take five cycles if jump is taken, four cycles if no jump.
The 14-bit Program Counter (PC) allows access to up to 8 KB of PROM available with the CY7C65x13 architecture. The top
32 bytes of the ROM in the 8K part are re serve d for testing purposes. The program c ounter is clea red during re set, su ch that the
first instruction e xecuted a fter a res et is a t addres s 0x0 000h. Typically, this is a jum p ins tructio n to a res et han dler tha t initializes
the application (see Interrupt Vectors on page 27).
The lower eight bits of the program counter are incremented as instructions are loaded and executed. The upper six bits of the
program counter are increm ented by executing an XP AGE instructi on. As a result, the las t instruction exec uted within a 256-by te
“page” of sequen tial cod e should be an XPAGE instruction. The assemble r directive “XPAGEON” causes the as sembler to insert
XPAGE instructions au tomatical l y. Because instructions can be either one or two bytes lon g, the assembler may occasionally
need to insert a NOP followed by an XPAGE to execute correctly.
The address of the next ins truction to be execute d, the carry fl ag, and the zero fl ag are save d as two bytes on the progra m stack
during an interrupt acknowledge or a CALL instruction. The program counter, carry flag, and zero flag are restored from the
program stack during a RETI instruction. Only the program counter is restored during a RET instruction.
The program counter ca nnot be accesse d direct ly by the firm ware . The progr am st ack can be exam ined by read in g SRAM from
location 0x00 and up.
Document #: 38-08002 Rev. *BPage 12 of 51
Page 13
3
3
5.1.1Program Memory Organization
after resetAddress
14-bit PC0x0000Program execution begins here after a reset
0x0002USB Bus Reset interrupt vector
0x0004128-µs timer interrupt vector
0x00061.024-ms timer interrupt vector
0x0008USB address A endpoint 0 interrupt vector
0x000AUSB address A endpoint 1 interrupt vector
0x000CUSB address A endpoint 2 interrupt vector
0x000EUSB address B endpoint 0 interrupt vector
CY7C6501
CY7C6511
0x0010USB address B endpoint 1 interrupt vector
0x0012Hub interrupt vector
0x0014Reserved
0x0016GPIO interrupt vector
0x0018
0x001AProgram Memory begi ns here
I2C interrupt vector
0x1FDF(8 KB -32) PROM ends here (CY7C65013, CY7C65113)
Figure 5-1. Program Memory Space with Interrupt Vector Table
Note that
Document #: 38-08002 Rev. *BPage 13 of 51
the upper 32 bytes of the 8K PROM are reserved. Therefore, user’s program must not overwrite this space.
Page 14
CY7C6501
3
3
5.28-bit Accumulator (A)
The accumulator is the general-purpose register for the microcontroller.
5.38-bit Temporary Register (X)
The “X” register is available to the firmware for temporary st orage of intermediate resul ts. The microcontroller can perform indexed
operations based on the value in X. Refer to Section 5.6.3 for additional information.
5.48-bit Program Stack Pointer (PSP)
During a reset, the Program Stack Pointer (PSP) is set to 0x00 and “grows” upward from this address. The PSP may be set by
firmware, using the MOV PSP,A instruction. The PSP supports interrupt service under hardware control and CALL, RET, and
RETI instructions under firmware control. The PSP is not readable by the firmware.
During an interrupt a ck nowl edge, interrupts are dis abl ed and the 14-bit program coun ter, carry flag, and zero flag are written as
two bytes of dat a memory . The first byte is stored in the me mory addresse d by the PSP, then the PSP is increm ented. The second
byte is stored in memory addressed by the PSP, and the PSP is incremented again. The overall effect is to store the program
counter and flags on the program “stack” and increment the PSP by two.
The Return From Interr upt (RETI) instruc tion decrem ents the PSP, then restores the second byt e from memor y addressed by the
PSP . The PSP is decremented again and the first byte is restored from memory ad dressed by the PSP. After the program counter
and flags have b een rest ored from s tack, th e interrupt s are enab led. The o verall ef fect is t o restore the program counter and flags
from the program stack, decrement the PSP by two, and re-enable interrupts.
The Call Subroutine (CALL) instruction stor es the prog ram coun ter and fla gs on the prog ram st ac k and inc rem en t s the PSP by
two.
The Return From Subroutine (RET) instruction restores the program counter but not the flags from the program stack and
decrements the PSP by two.
CY7C6511
5.4.1Data Memory Organization
The CY7C65x13 microcontrollers provide 256 bytes of data RAM. Normally, the SRAM is partitioned into four areas: program
stack, user va riables, data s tack, and USB e ndpoint FIFOs. The following is one ex ample of where the program stack, dat a stack ,
and user variables areas could be located.
After resetAddress
8-bit DSP8-bit PSP0x00Program Stack Growth
(Move DSP
8-bit DSP
Notes:
1. Refer to Section 5.5 for a description of DSP.
2. Endpoint sizes are fixed by the Endpoint Size Bit (I/O register 0x1F, Bit 7). See Table17-1.
[1]
)
user selectedData Stack Growth
User variables
USB FIFO space for up to tw o Address es and f ive endp oint s
0xFF
[2]
Document #: 38-08002 Rev. *BPage 14 of 51
Page 15
CY7C6501
3
3
5.58-bit Data Stack Pointer (DSP)
The Data Stack Pointer (DSP) supports PUSH and POP instructions that use the data stack for temporary storage. A PUSH
instruction pre-decrements the DSP, then writes data to the memory location addressed by the DSP. A POP instruction reads
data from the memory location addressed by the DSP, then post-increments the DSP.
During a reset, the DSP is reset to 0x00. A PUSH instruction when DSP equals 0x00 writes data at the top of the data RAM
(address 0xFF). This writes dat a to the memory area res erved fo r USB en dp oin t FIFO s. There fore , the DSP shou ld b e ind ex ed
at an appropriate memory location that does not compromise the Program Stack, user-de fin ed me mory (variables), or the USB
endpoint FIFOs.
For USB applications , the firmware s hould set the DSP to an appropri ate location to avoid a mem ory conflict w ith RAM dedic ated
to USB FIFOs. The me mo ry requirements for the U SB en dpo ints are described in Sec t io n 1 7.2. Exa mp le as se mbl y ins truc ti ons
to do this with two device addresses (FIFOs begin at 0xD8) are shown below:
MOV A,20h; Move 20 hex into Accumulator (must be D8h or less)
SWAP A,DSP ; swap accumulator value into DSP register.
5.6Address Modes
The CY7C65013 and CY 7C65113 microcontrollers support three addressin g modes for ins tructions that require da ta opera nds::
data, direct, and indexed.
5.6.1Data (Immediate)
“Data” address m ode refers t o a data operand th at is actuall y a cons tant en coded in t he instruc tion. As an example, c onsider th e
instruction that loads A with the constant 0xD8:
• MOV A, 0D8h.
This instruction requires two bytes of code where the first byte identifies the “MOV A” instruction with a data operand as the
second byte. The second byte of the instruction is the constant “0xD8.” A constant may be referred to by name if a prior “EQU”
statement assigns the constant value to the name. For example, the following code is equivalent to the example shown above:
• DSPINIT: EQU 0D8h
• MOV A, DSPINIT.
CY7C6511
5.6.2Direct
“Direct” address mode is used when the data operand is a variable stored in SRAM. In that case, the one byte address of the
variable is encode d in the instruction. As an example, consider an ins truction that loads A with the c onte nt s of memory address
location 0x10:
• MOV A, [10h].
Normally , varia ble names ar e assigned to va riable address es using “EQU” st atements to improve the re adability of th e assembler
source code. As an example, the following code is equivalent to the example shown above:
• buttons: EQU 10h
• MOV A, [buttons].
5.6.3Indexed
“Indexed” address mode allows the firmware to manipulate arrays of data stored in SRAM. The address of the data operand is
the sum of a constan t encoded in the instru ction and the con tents of the “X” register . Norma lly , the co nstant is th e “base” address
of an array of data and the X register contains an index that indicates which element of the array is actually addressed:
• array: EQU 10h
•MOV X, 3
• MOV A, [X+array].
This would have the effect of loading A with the fourth element of the SRAM “array” that begins at address 0x10. The fourth
element would be at address 0x13.
Document #: 38-08002 Rev. *BPage 15 of 51
Page 16
3
3
6.0 Clocking
XTALOUT
(pin 1)
CY7C6501
CY7C6511
XTALIN
(pin 2)
30 pF
Figure 6-1. Clock Oscillator On-Chip Circuit
The XTALIN and XTALOUT are the clock pins to the microcontroller. The user can connect an external oscillator or a crystal to
these pins. When u si ng an ex ternal crystal, kee p PC B trac es b etw ee n t he ch ip leads and cryst al as s hort as p os si ble (l ess t han
2 cm). A 6-MHz fundament al frequency p arallel resonan t crystal can be c onnected to these p ins to provide a refe rence frequency
for the internal PLL. The two int ernal 30-pF lo ad caps app ear in series to the externa l cryst al and would be equivalen t to a 15-pF
load. Therefore, the crystal must have a required load capacitance of about 15–18 pF. A ceramic resonator does not allow the
microcontroller to meet the timing specifications of full speed USB and therefore a ceramic resonator is not recommended with
these parts.
An external 6-MHz clock can be applied to the XTALIN pin if the XTALOUT pin is left open. Grounding the XTALOUT pin when
driving XTALIN with an oscillator does not work because the internal clock is effectively shorted to ground.
To Internal PLL
30 pF
7.0 Reset
The CY7C65x13 supports two resets: POR and WDR. Each of these resets causes:
• all registers to be restored to their default states
• the USB device addresses to be set to 0
• all interrupts to be disabl ed
• the PSP and DSP to be set to memory address 0x00.
The occurrence of a reset is recorded in the Processor Status and Control Register, as described in Section. Bits 4 and 6 are
used to record the occurrence of POR and WDR respectively. Firmware can interrogate these bits to determine the cause of a
reset.
Program execution st arts at ROM address 0x000 0 af ter a re set . Although this looks like int errup t ve cto r 0, the re is an imp ort a n t
difference. Reset processing does NOT push the program counter, carry flag, and zero flag onto program stack. The firmware
reset handler shou ld configure the hardw are before t he “main” loop of code. Attempting to execute a R ET or RETI in the firmw are
reset handler causes unpredictable execution results.
7.1Power-on Reset
When VCC is first applied to the c hip, th e POR si gnal is asse rted and the C Y7C65x13 enters a “sem i-susp end” st ate . Durin g the
semi-suspend st ate, which i s diff erent from the suspend sta te defined i n the USB spec ification , the osci llator and al l other bl ocks
of the part are functional, except for the CPU. This semi-suspend time ensures that both a valid V
the internal PLL has time to stabilize before full operation begins. When the V
oscillator is st able, the POR is d easserted and th e on-chip timer st arts countin g. The first 1 ms of s uspend time is no t interruptible,
and the semi-suspe nd state conti nues for an addition al 95 ms unless the count is bypasse d by a USB Bus Reset on the up stream
port. The 95 ms provides time for V
If a USB Bus Reset occurs on the upstream port during the 95 ms semi-suspend time, the semi-suspend state is aborted and
program execution begins immediately from address 0x0000. In this case, the Bus Reset interrupt is pending but not serviced
until firmware sets the USB Bus Reset Interrupt Enable bit (Bit 0, Figure 14-1) and enables interrupts with the EI command.
The POR signal is asserte d whenever V
again. Behavior is the same as described above.
Document #: 38-08002 Rev. *BPage 16 of 51
to stabilize at a valid operating voltage before the chip executes code.
CC
drops below approxim ately 2.5V , and remains ass erted until VCC rises above this level
CC
has risen above approximately 2.5V, and the
CC
level is reached and that
CC
Page 17
CY7C6501
3
3
7.2Watchdog Reset
The WDR occurs when the internal Watchd og Tim er rolls over . W riting any value to the write -only W atchdog Rese t Clear Registe r
(Figure 7-1) clears the timer. The timer rolls ov er a nd WD R oc c urs if it is not cleared within t
23.0 for the value of t
register content s are set to 01 0X0001 by the WDR) . A Watch dog Timer Reset lasts fo r 2 ms, after which the microcontrolle r begins
execution at ROM address 0x0000.
). Bit 6 of the Processor Status and Control Register (Figure13-1) is set to record this event (the
WATCH
of the last clear (s ee Sec tion
WATCH
CY7C6511
t
WATCH
Last write to
Watchdog Timer
Register
Figure 7-1. Watchdog Reset (Address 0x26)
The USB transmitter is disabled by a Watchdog Reset because the USB Device Address Registers are cleared (see Section
17.1). Otherwise, the USB Controller would respond to all address 0 transactions.
It is possible for the WDR bit of the Processor Status and Control Register (Figure 13-1) to be set following a POR event. If a
firmware interrogates th e Processor St atus and Control Register for a set condition on the WDR bit, the WD R bit should be ignored
if the POR bit is set (Bit 3 of the Processor Status and Control Register).
No write to WDT
register, so WDR
goes HIGH
2 ms
Execution begins at
Reset Vector 0x0000
8.0 Suspend Mode
The CY7C65x13 can be placed into a low-power state by setting the Suspend bit of the Processor Status and Control register.
All logic blocks in the device are turned off except the GPIO interrupt logic and the USB receiver. The clock oscillator and PLL,
as well as the free-running and Watchdog timers, are shut down. Only the occurrence of an enabled GPIO interrupt or non-idle
bus activity at a USB upstream or downstream port wakes the part out of suspend. The Run bit in the Processor Status and
Control Register must be set to resume a part out of suspend.
The clock oscillator res tarts immediately after ex it ing suspend mode. The microco ntroller returns to a fully functi on al state 1 ms
after the oscillator is st able. The microcontroller executes the instruction follow ing the I/O write that placed the device into suspend
mode before servicing any interrupt requests.
The GPIO interrupt allo ws the controller to wak e-up periodically and poll system component s while maintain ing a very low average
power consumption. To achieve the lowest possible current during suspend mode, all I/O should be held at V
This also applies to internal port pins that may not be bonded in a particular package.
Typical code for entering suspend is shown below:
...; All GPIO set to low-power state (no floating pins)
...; Enable GPIO interrupts if desired for wake-up
mov a, 09h; Set suspend and run bits
iowr FFh; Write to Status and Control Register – Enter suspend, wait for USB activity (or GPIO Interrupt)
nop; This executes before any ISR
...; Remaining code for exiting suspend routine.
or Gnd. Note:
CC
Document #: 38-08002 Rev. *BPage 17 of 51
Page 18
3
3
9.0 General-purpose I/O Ports
V
CY7C6501
CY7C6511
CC
Q1
14 kΩ
Q3*
Q2
*Port 0,1,2: Low I
Port 3: High I
sink
GPIO
PIN
sink
OE
Internal
Data Bus
Port Write
Port Read
Reg_Bit
STRB
(Latch is Transparent)
Interrupt
Enable
Interrupt
Controller
GPIO
CFG
Data
Out
Latch
Data
In
Latch
Data
Interrupt
Latch
mode
2-bits
Control
Control
Figure 9-1. Block Diagram of a GPIO Pin
There are up to 32 GPIO pins (P0[7:0], P1[7:4,2:0], P2[7:3], and P3[1:0]) for the hardware interface. The number of GPIO pins
depends on package type. See Se ction 3.0 for the port pi ns avai labil ity on dif fere nt pa ckage typ es. Each port can be configu red
as inputs with inte rnal pull -up s, open drain outp uts , or traditi onal C MOS outputs. Port 3 offers a higher cu rrent driv e, with t ypical
current sink capability of 12 mA. The data for each GPIO port is accessible through the data registers. Port data registers are
shown in Figure 9-2 through Figure 9-5, and are set to 1 on reset
.
Port 0 DataAddress 0x00
Bit # 76543210
Bit NameP0.7P0.6P0.5P0.4P0.3P0.2P0.1P0.0
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 11111111
Figure 9- 2. Port 0 Data
Port 1 DataAddress 0x01
Bit # 76543210
Bit NameP1.7P1.6P1.5P1.4ReservedP1.2P1.1P1.0
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 11111111
Figure 9-3. Port1 Data
Port 2 DataAddress 0x02
Bit # 76543210
Bit NameP2.7P2.6P2.5P2.4P2.3ReservedReservedReserved
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 11111111
Figure 9- 4. Port 2 Data
Document #: 38-08002 Rev. *BPage 18 of 51
Page 19
CY7C6501
3
3
Port 3 DataAddress 0x03
Bit # 76543210
Bit NameReservedReservedRe servedReservedReservedReservedP3.1P3.0
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 11111111
Figure 9- 5. Port 3 Data
Special care should be t aken w ith any unu sed GPIO dat a bit s. An unused GPIO dat a bit, eithe r a pin on the ch ip or a port bit that
is not bonded on a particular package, must not be left floating when the device enters the suspend state. If a GPIO data bit is
left floating, the leakage current caused by the floating bit may violate the suspend current limitation specified by the USB
Specifications. If a ‘1’ is written to the unused data bit and the port is configured with open drain outputs, the unused data bit
remains in an indeterminate state. Therefore, if an unused port bit is programmed in open-drain mode, it must be written with a
‘0.’ Notice that the CY7C65113 always requires that P1[7:3], P2[7:0], and P3[7:0 ] be wr itte n with a ‘0 .’ Wh en the CY7 C65013 is
used, the P1[3], P2[2:0], and P3[7:2] should be written with a ‘0.’
A read from a GPIO port always returns the present state of the voltage at the pin, independent of the settings in the Port Data
Registers. During reset, all of the GPIO pins are set to a high-impedance input state. Writing a ‘0’ to a GPIO pin drives the pin
LOW. In this state, a ‘0’ is always read on that GPIO pin unless an external source overdrives the internal pull-down device.
9.1GPIO Configuration Port
Every GPIO port can be progra mmed as inputs w ith internal pull-u ps, outputs LO W or HIGH, or Hi-Z (floating , the pin is not driven
internally). In addition, the interrupt polarity for each port can be programmed. The Port Configuration bits (Figure 9-6) and the
Interrupt Enable bit (Figure 9-7 through Figure 9-10) determine the interrupt polarity of the port pins
.
GPIO ConfigurationAddress 0x08
Bit # 76543210
Bit NamePort 3
Config Bit 1
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 00000000
Port 3
Config Bit 0
Port 2
Config Bit 1
Figure 9-6. GPIO Configuration Register
Port 2
Config Bit 0
Port 1
Config Bit 1
Port 1
Config Bit 0
Config Bit 1
CY7C6511
Port 0
Port 0
Config Bit 0
As shown in Table 9-1 below, a positi ve polarity on an input pin repre sents a rising edge interrupt (LO W to HIGH), and a negative
polarity on an input pin represents a falling edge interrupt (HIGH to LOW).
The GPIO interrupt is generated when all of the following conditions are met: the Interrupt Enable bit of the associated Port
Interrupt Enable Register is enabled, the GPIO Interrupt Enable bit of the Global Interrupt Enable Register (Figure 14-1) is
enabled, the Interrup t Enable Sense (bi t 2, Figure 13-1) is set, and the GPIO pin of the po rt sees an eve nt matching th e interrupt
polarity.
The driving stat e of ea ch GPIO pin is determined by the valu e written to the pin’s Dat a Reg is ter ( Figure 9-2 through Figure 9-5)
and by its associated Port Configuration bits as shown in the GPIO Configuration Register (Figure 9-6). These ports are
configured on a per-port basis, so all pins in a given port are configured together. The possible port configurations are detailed
in Table 9-1. As shown in this table below, when a GPIO port is configured with CMOS outputs, interrupts from that port are
disabled.
During reset, all of the bits in the GPIO Configuration Register are written with ‘0’ to select Hi-Z mode for all GPIO ports as the
default configuration.
Document #: 38-08002 Rev. *BPage 19 of 51
Page 20
CY7C6501
3
3
Table 9-1. GPIO Port Output Control Truth Table and Interrupt Polarity
Port Config Bit 1 Port Config Bit 0 Data Register Output Drive Strength Interrupt Enable BitI nterrupt Polarity
110Output LOW0Disabled
1Resistive1– (Falling Edge)
100Output LOW0Disabled
1Output HIGH1Disabled
010Output LOW0Disabled
1Hi-Z1– (Falling Edge)
000Output LOW0Disabled
1Hi-Z1+ (Rising Edge)
Q1, Q2, and Q3 discussed below are the transistors referenced in Figure 9-2. The available GPIO drive strength are:
• Output LOW Mode: The pin’s Data Register is set to ‘0.’
Writing ‘0’ to the pi n’s Data Regi ster puts the p in in ou tput LO W mod e, reg ardless of th e cont ents of th e Port Config urat ion
Bits[1:0]. In this mode, Q1 and Q2 are OFF. Q3 is ON. The GPIO pin is driven LOW through Q3.
• Output HIGH Mode: The pin’s Data Register is set to 1 and the Port Configuration Bits[1:0] is set to ‘10.’
In this mode, Q1 and Q3 are OFF. Q2 is ON. The GPIO is pulled up through Q2. The GPIO pin is capable of sourcing... of
current.
• Resistive Mode: The pin’s Data Register is set to 1 and the Port Configuration Bits[1:0] is set to ‘11.’
Q2 and Q3 are O FF. Q1 is ON. The GPIO p in is p ull ed up w ith a n i nte rnal 1 4kΩ re sistor. In resistive mode, t he pin m ay s er v e
as an input. Reading the pin’s Data Register returns a logic HIGH if the pin is not driven LOW by an external source.
• Hi-Z Mode: The pin’s Data Register is set to1 and Port Configuration Bits[1:0] is set either ‘00’ or ‘01.’
Q1, Q2, and Q3 are all OFF. The GPIO pin is not driven internally. In this mode, the pin may serve as an input. Reading the
Port Data Register returns the actual logic value on the port pins.
CY7C6511
9.2GPIO Interrupt Enable Ports
Each GPIO pin can be individually enabled or disabled as an interrupt source. The Port 0–3 Interrupt Enable Registers provide
this feature with an Interrupt Enable bit for each GPIO pin.
During a reset, GPIO interrupts are disabled by clearing all of the GPIO Interrupt Enable bits. Writing a ‘1’ to a GPIO Interrupt
Enable bit enables GPIO interrupts from the corresponding input pin. All GPIO pins share a common interrupt, as discussed in
Section 14.7
.
Port 0 Interrupt EnableAddress 0x04
Bit # 76543210
Bit NameP0.7 Intr
Enable
Read/WriteWWWWWWWW
Reset 00000000
Port 1 Interrupt EnableAddress 0x05
Bit # 76543210
Bit NameP1.7 Intr
Enable
Read/WriteWWWWWWWW
Reset 00000000
P0.6 Intr
Enable
P1.6 Intr
Enable
P0.5 Intr
Enable
Figure 9-7. Port 0 Interrupt Enable
P1.5 Intr
Enable
Figure 9-8. Port 1 Interrupt Enable
P0.4 Intr
Enable
P1.4 Intr
Enable
P0.3 Intr
Enable
ReservedP0.2 Intr
P0.2 Intr
Enable
Enable
P0.1 Intr
Enable
P1.1 Intr
Enable
P0.0 Intr
Enable
P1.0 Intr
Enable
Document #: 38-08002 Rev. *BPage 20 of 51
Page 21
CY7C6501
3
3
Port 2 Interrupt EnableAddress 0x06
Bit # 76543210
Bit NameP0.7 Intr
Enable
Read/WriteWWWWWWWW
Reset 00000000
Port 3 Interrupt EnableAddress 0x07
Bit # 76543210
Bit NameReservedReservedReservedReservedRe servedReservedP3.1 Intr
Read/WriteWWWWWWWW
Reset 00000000
10.0 12-bit Free-Running Timer
The 12-bit timer operates with a 1 -µs tick, provides two interrupts (128µs and 1.02 4m s) an d all ows th e firm ware to dire ctl y time
events that are up to 4 ms in duration. The lower eight bits of the timer can be read directly by the firmware. Reading the lower
eight bits latch es the upper four bit s into a tempora ry register . When the firmwa re reads the upper fo ur bits of the timer , it is actually
reading the count stored in the temporary register. The effect of this is to ensure a stable 12-bit timer value can be read, even
when the two reads are separated in time.
Timer LSBAddress 0x24
Bit # 76543210
Bit NameTimer Bit 7TimerBit 6Timer Bit 5Timer Bit 4Timer Bit 3Timer Bit 2Timer Bit 1Timer Bit 0
Read/WriteRRRRRRRR
Reset 00000000
P0.6 Intr
Enable
P0.5 Intr
Enable
Figure 9-9. Port 2 Interrupt Enable
Figure 9-10. Port 3 Interrupt Enable
Figure 10-1. Timer LSB Register
P0.4 Intr
Enable
P0.3 Intr
Enable
ReservedReservedReserved
CY7C6511
Enable
P0.3 Intr
Enable
Bit [7:0]: Timer lower eight bits.
Timer MSBAddress 0x25
Bit #76543210
Bit NameReservedReservedReservedReservedTimer Bit 11 Timer Bit 10 Timer Bit 9Timer Bit 8
Read/Write––––RRRR
Reset 00000000
Figure 10-2. Timer MSB Register
Bit [3:0]: Timer higher nibble
Bit [7:4]: Reserved.
Document #: 38-08002 Rev. *BPage 21 of 51
Page 22
CY7C6501
3
3
1.024-ms interrupt
µ
s interrupt
128-
CY7C6511
1097856432
1011
1 MHz clock
L1L0L2L3
D3 D2 D1 D0 D7 D6 D5 D4 D3 D2 D1 D0
8
Figure 10-3. Timer Block Diagram
11.0 I2C Configuration Register
Internal hardware support s communi cation with extern al devices thro ugh an I2C-compatible int erface. I2C-compatibl e functio n is
discussed in det ail in Sec tion 12.0.
locations of the SCL (clock) and SDA (data) pins, either on Port 1 or Port 2 as shown in Table 11-1. These bits are cleared on
reset. When the GPIO is configu r ed for I
pull-up resistors on SCL and SDA is recommended
.
I2C ConfigurationAddress 0x09
Bit # 76543210
Bit NameI
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 00000000
Table 11-1. I2C Port Configuration
2
I
C Position (Bit7, Figure 11-1)I
2
C PositionReservedReservedReservedReservedReservedI2C Port
Don’t Care1I
00I
10I
[3]
The I2C Position bit (Bit 7, Figure 11-1) and I2C Port Width bit (Bit 1, Figure 11-1) select the
2
C function, the internal pull up s on the pin s are disabl ed. Ad diti on of an ex tern al w ea k
2
Figure 11-1. I
2
C Configuration Register
C Port Width (Bit1, Figure 11-1)I
To Timer Registers
Width
2
C Position
2
C on P2[1:0], 0:SCL, 1:SDA
2
C on P1[1:0], 0:SCL, 1:SDA
2
C on P2[1:0], 0:SCL, 1:SDA
Reserved
12.0 I2C-compatible Controller
The I2C-compatible block provides a versatile two-wire communication with external devices, supporting master, slave, and
multi-master modes of operation. The I2C-comp atible block functi ons by handling the low-l evel signaling in hardw are, and issuing
interrupts as needed to allow firmware to take appropriate action during transactions. While waiting for firmware response, the
hardware keeps the I2C-compatible bus idle if necessary.
The I2C-compatible block generates an interrupt to the microcontroller at the end of each received or transmitted byte, when a
stop bit is detected by the slave w hen in receive mode, or when arb itratio n is lost. D etai ls of the interrupt respons es are gi ven in
Section 14.8.
2
The I2C-compatibl e interface consist s of two registers, an I
(Figure 12-2). The I2C Data Register is imp lemen ted as sep arate r ead and writ e regis ters. G eneral ly, the I2C Sta tus an d Contro l
Register should o nly be m onitored a fter the I
read misleading bit status if a transaction is underway.
Note:
2
C-compatible function must be separately enabled, as described in Section 12.0.
3. I
Document #: 38-08002 Rev. *BPage 22 of 51
2
C interrupt, as all b its are valid at th at time. Po lling thi s registe r at other t imes could
C Data Register (Figure 12-1) and an I2C St atus and Contro l Register
Page 23
CY7C6501
3
3
CY7C6511
The I2C clock (SCL) is connected to bit 0 of either GPIO port 1 or GPIO port 2, and the I2C SDA data is connected to bit 1 of
either GPIO port 1 or GPIO port 2. The port selection is determined by settings in the I
2
C Port Configuration Register (Section
11.0). Once the I2C-compatible fun ctionali ty is enable d by setting the I2C Enable bit of the I2C Stat us and Control Register (bit 0,
Figure 12-2), the two LSB ([1:0]) of the correspondi ng GP IO port is pl aced in Op en D rain m ode, re gardle ss of the setti ngs of the
GPIO Configuration Register. In Open Drain mode, the GPIO pin outputs LOW if the pin’s Data Register is ‘0’, and the pin is in
Hi-Z mode if the pin’s Data Register is ‘1’. The electrical characteristics of the I
GPIO ports 1 and 2. Note that the I
All control of the I
2
C clock (SCL) and data (SDA) lines is performed by the I2C-compatible block.
(max) is 2 mA @ V
OL
= 2.0V for ports 1 and 2.
OL
2
C-compatible interface is the same as that of
I2C DataAddress 0x29
Bit #76543210
2
Bit Name I
C Data 7 I2C Data 6 I2C Data 5 I2C Data 4 I2C Data 3 I2C Data 2 I2C Data 1 I2C Data 0
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset XXXXXXXX
2
C Data Register
Bits [7..0] : I
2
C Data
Figure 12-1. I
Contains the 8-bit data on the I2C Bus.
2
I
C Status and ControlAddress 0x28
Bit #76543210
2
Bit NameMSTR Mode Continue/BusyXmit ModeACKAddrARB
Lost/Restart
Received
Stop
C Enable
I
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 00000000
2
Figure 12-2. I
2
The I
C Status and Control register bits are defined in Table 12-1, with a more detailed descripti on followi ng.
Table 12-1. I
2
C Status and Control Register Bit Definitions
C Status and Control Register
BitNameDescription
2
0I
C EnableWhen set to ‘1’, the I2C-compatible function is enabled. When cleared, I2C GPIO pins operate
normally.
2
1Received StopReads 1 only in slave rec eive mo de, whe n I
C Stop bit detec ted (unle ss firmwa re did n ot ACK the
last transaction).
2ARB Lost/Restart Reads 1 to indicate master has lost arbitration. Reads 0 otherwise.
Write to 1 in master mode to perform a restart sequence (also set Continue bit).
3AddrReads 1 during first byte after start/restart in slave mode, or if master loses arbitration.
Reads 0 otherwise. This bit should always be written as 0.
4ACKIn receive mode, write 1 to generate ACK, 0 for no ACK.
In transmit mode, reads 1 if ACK was received, 0 if no ACK received.
5Xmit ModeWrite to 1 for transmit mode, 0 for receive mode.
6Continue/BusyWrite 1 to indicate ready for next transaction.
Reads 1 when I
2
C-compatible block is busy with a transaction, 0 when transaction is complete.
7MSTR ModeWrite to 1 for master mode, 0 for slave mode. This bit is cleared if master loses arbitration.
Clearing from 1 to 0 generates Stop bit.
Bit 7 : MSTR Mode
2
Setting this bit to 1 causes the I
C-compatible block to initiate a master mode transaction by sending a start bit and
transmitting the first data byte from the data register (this typically holds the target address and R/W bit). Subsequent bytes
are initiated by setting the Continue bit, as described below.
Clearing this bit (set to 0) causes the GPIO pins to operate normally.
2
In master mode, the I
C-compatible block generates the clock (SCK), and drives the data line as required depending on
transmit or receive state. The I2C-compatible block performs any required arbitration and clock synchronization. IN the
event of a loss of arbitration, this MSTR bit is cleared, the ARB Lost bit is set, and an interrupt is generated by the
Document #: 38-08002 Rev. *BPage 23 of 51
Page 24
CY7C6501
3
3
microcontroller. If the chip is the target of an external master that wins arbitration, then the interrupt is held off until the
transaction from the external master is completed.
2
When MSTR Mode is cleared from 1 to 0 by a firmware write, an I
Bit 6 : Continue/Busy
This bit is written by the fi rmware to ind icate that t he firmware is ready for th e next byte t ransaction to begin. In other words,
the bit has respon ded to a n interru pt reque st and has c ompleted the require d updat e or read of the d ata registe r. During a
read this bit indicates if the hardware is busy and is lo cking out additi onal writes to the I
locking allows the hardware to compl ete c ert a in op erations that may requi re an ex ten ded period of time. F oll owin g an I
interrupt, the I2C-compatible block does not return to the Busy state until firmware sets the Continue bit. This allows the
firmware to make one control register write without the need to check the Busy bit.
Bit 5 : Xmit Mode
This bit is set by firmware to enter transmit mode and perform a data transmit in master or slave mode. Clearing this bit
sets the part i n rece ive m ode. Fi rmwa re gene rally d etermi nes th e val ue of th is bit from th e R/W bi t asso ciate d wit h the I
address packet. Th e Xmit Mode bit st ate is ignored whe n initially wri ting the MSTR Mode or th e Restart bit s, as these ca ses
always cause transmit mode for the first byte.
Bit 4 : ACK
This bit is set or cleared by firmware during receive operation to indicate if the hardware should generate an ACK signal
2
on the I
time. During transmits (Xmit Mode = 1), this bit should be cleared.
Bit 3 : Addr
This bit is set by the I
The Addr bit is cleared whe n the firmwa re se ts the Continue bit. This bit allows the firmware to re cogni ze w hen the mas ter
has lost arbitration, and in slave mode it allows the firmware to recognize that a start or restart has occurred.
Bit 2 : ARB Lost/Restart
This bit is valid as a status bit (ARB Lost) after master mode transactions. In master mode, set this bit (along with the
Continue and MSTR Mo de bit s) to pe rform an I
to the data regist er before setting the C ontinue bit. To prevent false ARB Lost signal s, the Restart bi t is cleared by h ardware
during the restart sequence.
Bit 1 : Receive Stop
This bit is set when the slave is in receive mode and detects a stop bit on the bus. The Receive Stop bit is not set if the
firmware terminates the I
e.g., in receive mode if firmware se ts the Continue bit and clears the ACK bit.
Bit 0 : I
Set this bit to overri de GPIO definition with I
these pins are free to fun ction as G PIO s. In I
of the GPIO configuration setting.
C-compatible bus. W riting a 1 to this bit genera tes an ACK (SDA LOW) on the I2C -comp atib le bus at the ACK bit
2
C-compatible block during the first byte of a slave receive transaction, after an I2C start or restart.
2
C restart sequence. The I2C target address for the restart must be written
2
C transaction by not acknowledging the previous byte transmitted on the I2C-compatible bus,
2
C Enable
2
C-compatible fu nction on the t wo I2C-compatible p ins. When this bit is cleared,
2
C-compatible m ode , the t wo pin s op era te in open drain mode, independent
C Stop bit is generated.
2
C St atus and Control register. This
CY7C6511
2
C
2
C
13.0 Processor Status and Control Register
Processor Status and ControlAddress 0xFF
Bit #76543210
Bit NameIRQ
Pending
Read/WriteRR/WR/WR/WR/WRR/WR/W
Reset 00010001
Bit 0: Run
This bit is manipulated by the HALT instruction. When Halt is executed, all the bits of the Processor Status and Control
Register are cleared to 0. Since the run bit is clea red, the processor stops at the end of the current in struction. The process or
remains halted until an appropriate reset occurs (power-on or Watchdog). This bit should normally be written as a ‘1.’
Bit 1: Reserved
Bit 1 is reserved and must be written as a zero.
Bit 2: Interrupt Enable Sense
Document #: 38-08002 Rev. *BPage 24 of 51
Watchdog
Reset
Figure 13-1. Processor Status and Control Register
USB Bus
Reset
Interrupt
Power-on
Reset
SuspendInterrupt
Enable
ReservedRun
Sense
Page 25
CY7C6501
3
3
This bit indicates w h eth er i nter r upts are enabled or dis abl ed. Firm w are has no di rec t c ontro l o ve r thi s b it a s wr i tin g a ze ro
or one to this bit position has no effect on interrupts. A ‘0’ indicates that interrupts are masked off and a ‘1’ indicates that
the interrupts are enab led. This bit is further gated with th e bit settings of the Glob al Interrupt Enable Registe r (Figure 14-1)
and USB End Point Interrupt Enable Register (Figure14-2). Instructions DI, EI, and RETI manipulate the state of this bit.
Bit 3: Suspend
Writing a ‘1’ to the Suspend bit halts the processor and cause the microcontroller to enter the suspend mode that significantly reduces power consumption. A pending, enabled interrupt or USB bus activity causes the device to come out of
suspend. After coming out of suspend, the devic e resumes firmware ex ecution at the in struction follow ing the IOWR which
put the part into suspend. An IOWR attempting to put the part into suspend is ignored if USB bus activity is present. See
Section 8.0 for more details on suspend mode operation.
Bit 4: Power-on Reset
The Power-on Reset is set to ‘1’ during a power-on reset. The firmware can check bits 4 and 6 in the reset handler to
determine whether a res et was ca used by a power-o n condi tion or a Watchdog timeout. A PO R event m ay be fo llowed b y
a Watchdog reset before firmware begins executing, as explained below.
Bit 5: USB Bus Reset Interrupt
The USB Bus Reset Interrupt bit is set when the USB Bus Reset is detec te d on receiv in g a USB Bus Rese t sig nal on the
upstream port. The USB Bus Reset signal is a single-ended zero (SE0) that lasts from 12 to 16 µs. An SE0 is defined as
the condition in which both the D+ line and the D– line are LOW at the same time. .
Bit 6: Watchdog Reset
The Watchdog Reset is set during a reset initiated by the Watchdog Timer. This indicates the Watchdog Timer went for
more than t
Bit 7: IRQ Pending
The IRQ pending, when set, indica tes that one or more o f the interrupt s has been recogniz ed as active. An interrupt remains
pending until its interrupt enable bit is set (Figure14-1, Figure 14-2) and interrupts are globally enable d. At th at po int, the
internal interrupt handling sequence clears this bit until another interrupt is detected as pending.
During power-up, the Processor S t a tus a nd C on trol R e gis ter is s et to 00 01 000 1, w hic h in dic ate s a POR (bi t 4 s et) has occurred
and no interrupts are pending (bit 7 clear). During the 96-ms suspend at start-up (explained in Section 7.1), a Watchdog Reset
also occurs unless this suspend is aborted by an upstream SE0 before 8 ms. If a WDR occurs during the power-up suspend
interval, firmware reads 010 10001 fro m the S t atus a nd Control Regist er after po wer-up. Nor mally, the POR bit should be cleared
so a subsequent WDR can be clearl y ident ified. If an ups tream bus reset is rec eived bef ore firmw are ex amine s this regis ter, the
Bus Reset bit may also be set.
During a Watc hdog Reset, the Pro cessor S tatus an d Control Regist er is set to 01XX0001 , which indica tes a Watc hdog Reset (bit
6 set) has occurred and no in terrupt s are p ending (b it 7 clear). Th e W atchdo g Reset does no t effec t the st ate of the POR and the
Bus Reset Interrupt bits.
(8 ms minimu m) between Watchdog clears. This can occur w ith a POR event, as noted below.
WATCH
CY7C6511
14.0 Interrupts
Interrupts are generated by GPIO pins, internal timers, I2C-compatible operation, internal USB hub and USB traffic conditions.
All interrupts are maskable by the Global Interrupt Enable Register and the USB End Point Interrupt Enable Register. Writing a
‘1’ to a bit position enables the interrupt associated with that bit position.
Global Interrupt Enable RegisterAddress 0X20
Bit # 76543210
2
Bit NameReservedI
Read/Write–R/WR/W-R/WR/WR/WR/W
Reset –00X0000
Bit 0 : USB Bus RST Interrupt Enable
1 = Enable Interrupt on a USB Bus Reset; 0 = Disable interrupt on a USB Bus Reset (Refer to section 14.3).
Bit 1 :128-µs Interrupt Enable
1 = Enable Timer interrupt every 128 µs; 0 = Disab le Timer Interrupt for every 128 µs.
Bit 2 : 1.024-ms Interrupt Enable
Document #: 38-08002 Rev. *BPage 25 of 51
C Interrupt
Enable
GPIO
Interrupt
Enable
Figure 14-1. Global Interrupt Enable Register
Reserved USB Hub
Interrupt
Enable
1.024-ms
Interrupt
Enable
128-µs
Interrupt
Enable
USB Bus
RST
Interrupt
Enable
Page 26
CY7C6501
3
3
1 = Enable Timer interrupt every 1.024 ms ; 0 = Disable Timer Interrupt every 1.024 ms.
Bit 3 : USB Hub Interrupt Enable
1 = Enable Interrupt on a Hub status change; 0 = Disable interrupt due to hub status change. (Refer to section 14.6.)
Bit 4 : Reserved .
Bit 5 : GPIO Interrupt Enable
1 = Enable Interrupt on falli ng/ris ing edge on any G PIO; 0 = Disa ble Inte rrupt on fal ling/ri sing e dge on any GPIO (Ref er to
section 14.7, 9.1 and 9.2.).
2
Bit 6 : I
Bit 7 : Reserved.
USB Endpoint Interrupt EnableAddress 0X21
Bit #76543210
Bit NameReservedReserved Reserved EPB1
Read/Write–––R/WR/WR/WR/WR/W
Reset –––00000
C Interrupt Enable
1 = Enable Interrupt on I2C related activity; 0 = Disable I2C related activity interrupt. (Refer to section 14.8.)
Interrupt
Enable
Figure 14-2. USB Endpoint Interrupt Enable Register
EPB0
Interrupt
Enable
EPA2
Interrupt
Enable
CY7C6511
EPA1
Interrupt
Enable
EPA0
Interrupt
Enable
Bit 0: EPA0 Interrupt Enable
1= Enable Interrupt on data activity through endpoint A0; 0= Disable Interrupt on data activity through endpoint A0
Bit 1: EPA1 Interrupt Enable
1= Enable Interrupt on data activity through endpoint A1; 0= Disable Interrupt on data activity through endpoint A1
Bit 2: EPA2 Interrupt Enable
1= Enable Interrupt on data activity through endpoint A2; 0= Disable Interrupt on data activity through endpoint A2.
Bit 3: EPB0 Interrupt Enable
1= Enable Interrupt on data activity through endpoint B0; 0= Disable Interrupt on data activity through endpoint B0
Bit 4: EPB1 Interrupt Enable
1= Enable Interrupt on data activity through endpoint B1; 0= Disable Interrupt on data activity through endpoint B1
Bit [7..5] : Reserved
During a reset, the contents the Global Interrupt Enable Register and USB End Point Interrupt Enable Register are cleared,
effectively, disabling all interrupts
The interrupt controller c ontains a sep arate flip-flo p for each interrupt. Se e Figure 14-3 for the logic block diagram of the interru pt
controller . Wh en an i nterrupt i s genera ted, it is first registere d as a pe nding i nterrupt. It stay s pend ing unti l it is serviced or a res et
occurs. A pending interrupt only generates an interrupt request if it is enabled by the corresponding bit in the interrupt enable
registers. The highest priority interrupt request is serviced following the completion of the currently executing instruction.
When servicing an interrupt, the hardware does the following:
1. Disables all interrupts by clearing the Global Interrupt Enable bit in the CPU (the state of this bit can be read at Bit 2 of the
Processor Status and Control Register, Figure 13-1).
2. Clears the flip-flop of the current interrupt.
3. Generates an automatic CALL instructio n to the RO M addre ss assoc iated with the int errupt bei ng serv iced (i.e., the In terrupt
Vector, see Section 14.1).
The instruction in th e interru pt ta ble is ty pica lly a JMP in struct ion to the add ress of the In terrupt Serv ice R outin e (ISR). The us er
can reenable interrupts in the interrupt service routine by executing an EI instruction. Interrupts can be nested to a level limited
only by the available stack space.
The Program Counter value as well as the Carry and Zero flags (CF, ZF) are stored onto the Program Stack by the automatic
CALL instruction gene rated as pa rt of the in terrupt ac know ledg e process . The use r firmware is resp onsible fo r ensuri ng that th e
processor state is preserved and restored during an interrupt. The PUSH A instruction should typically be used as the first
command in the ISR to save th e ac c um ula tor v alu e an d th e PO P A ins tru cti on s ho uld be u se d to re st ore th e ac c umu la tor v alu e
just before the RETI instruction. The program counter CF and ZF are restored and interrupts are enabled when the RETI
instruction is executed.
Document #: 38-08002 Rev. *BPage 26 of 51
Page 27
CY7C6501
3
3
e
The DI and EI instructions can be used to disable and enable interrupts, respectively. These instructions affect only the Global
Interrupt Enable bit of the CPU. If desired, EI can be used to re-enable interrupts while inside an ISR, instead of waiting for the
RETI that exits the ISR. While the global interrupt enable bit is cleared, the presence of a pending interrupt can be detected by
examining the IRQ Sense bit (Bit 7 in the Processor Status and Control Register).
14.1Interrupt Vectors
The Interrupt Vectors su ppo rted by t he U SB Con trol ler are listed in Table 14-1. The lowest-numbered interrupt (USB Bus Reset
interrupt) has the highest priority, and the highest-numbered interrupt (I
USB Reset Clear
1
USB Reset Int
1
AddrA ENP2 Int
I2C Int
CLR
D
Q
Enable [0]
CLK
CLR
D
CLK
CLR
1
D
CLK
(Reg 0x20)
Q
Enable [2]
(Reg 0x21)
Q
Enable [6]
(Reg 0x20)
USB Reset IRQ
128-µs CLR
128-µs IRQ
1-ms CLR
1-ms IRQ
AddrA EP0 CLR
AddrA EP0 IRQ
AddrA EP1 CLR
AddrA EP1 IRQ
AddrA EP2 CLR
AddrA EP2 IRQ
AddrB EP0 CLR
AddrB EP0 IRQ
AddrB EP1 CLR
AddrB EP1 IRQ
Hub CLR
Hub IRQ
DAC CLR
DAC IRQ
GPIO CLR
GPIO IRQ
2
C CLR
I
2
C IRQ
I
Interrupt Priority Encoder
2
C interrupt) has the lowest priority.
Interrupt
Vector
To CPU
CPU
IRQout
Global
Interrupt
Enable
Bit
CLR
Interrupt
Acknowledge
CY7C6511
IRQ Sense
IRQ
Int Enabl
Sense
Controlled by DI, EI, and
RETI Instructions
Figure 14-3. Interrupt Controller Function Diagram
Although Reset is not an interrupt, the first inst ructio n executed aft er a reset is at PRO M address 0x 0000h— which co rrespon ds
to the first entry in the Interrupt V ector T able. Because th e JMP instruction is two by tes long, the interrupt ve ctors occupy two bytes.
Table 14-1. Interrupt Vector Assignments
Interrupt Vector NumberROM AddressFunction
Not Applicable0x0000Execution after Reset begins here
10x0002USB Bus Reset interrupt
20x0004128-µs timer interrupt
30x00061.024-ms timer interrupt
40x0008USB Address A Endpoint 0 interrupt
50x000AUSB Address A Endpoint 1 interrupt
60x000CUSB Address A Endpoint 2 interrupt
70x000EUSB Address B Endpoint 0 interrupt
80x0010USB Address B Endpoint 1 interrupt
Interrupt latency can be calculated from the following equation:
CY7C6501
CY7C6511
Interrupt latency =(Number of clock cycles remaining in the current instruction) + (10 clock cycles for the CALL instruction) +
For example, if a 5-clock cycle instruction such as JC is being executed when an interrupt occurs, the first instruction of the
Interrupt Service Routine executes a minimum of 16 clocks (1+10+5) or a maximum of 20 clocks (5+10+5) after the interrupt is
issued. For a 12-MHz internal clock (6-MHz crystal), 20 clock periods is 20/12 MHz = 1.667 µs.
(5 clock cycles for the JMP instruction)
14.3USB Bus Reset Interrupt
The USB Controller recogni ze s a USB R es et wh en a Sing le En ded Zero (SE0 ) co ndi tio n pe rsi st s on the u p st ream U SB por t for
12–16 µs. SE0 is defined as the condition in which both the D+ line and the D– line are LOW. A USB Bus Reset may be recognized
for an SE0 as short as 12 µs, but is always reco gn ize d for an SE0 lon ger than 16 µs. When a USB Bus Reset is detected, bit 5
of the Processor S tatus an d Control Register (Figure 13-1) is set to record this event. In addition, the contr oller clears the follo wing
registers:
SIE Section:.... USB Device Address Registers (0x10, 0x40)
Hub Section:......................Hub Ports Connect Status (0x48)
..........................................Hub Ports Resume Status (0x4E)
.................................................Hub Ports SE0 Status (0x4F)
........................................................... Hub Ports Data (0x50)
.............................................Hub Downstream Force (0x51).
A USB Bus Reset Interrupt is generat ed at the end of the USB Bus Rese t condition when th e SE0 state is deass erted. If the USB
reset occurs during the start-up delay following a POR, the delay is aborted as described in Section 7.1.
14.4Timer Interrupt
There are two periodic timer interrupts: the 128-µs interrupt and the 1.024-ms interrupt. The user should disable both timer
interrupts befor e going into the suspen d mode to avoid possibl e conflicts between servicing the timer in terrupts first or the s uspend
request first.
14.5USB Endpoint Interrupts
There are five USB endpoint interrupts, one per endpoint. A USB endpoint interrupt is generated after the USB host writes to a
USB endpoint FIFO or afte r the USB co ntrol le r sen ds a p acket to the USB host. The inte rrupt is gen erat ed o n the las t packet of
the transaction (e.g., on the host’ s ACK on an IN t ransfer , or on th e device ACK on an OUT transfer). I f no ACK is recei ved during
an IN transaction, no interrupt is generated.
14.6USB Hub Interrupt
A USB hub interrupt is generat ed by the hardware af ter a conn ect/di sconnec t chang e, babbl e, or a resume event is de tected by
the USB repeater hardware. The babble and resume events are additionally gated by the corresponding bits of the Hub Port
Enable Register (Figure 16-3). The connect/disconnect event on a port does not generate an interrupt if the SIE does not drive
the port (i.e., the port is being forced).
14.7GPIO Interrupt
Each of the GPIO pins can generate an interrupt, if enabled. The interrupt polarity can be programmed for each GPIO port as
part of the GPIO configuration. All of the GPIO pins share a single interrupt vector, which means the firmware needs to read
theGPIO ports with e nable d in terrupt s to determi ne whic h pin o r pins cause d an in terrupt. A block diagra m of the G PIO int errupt
logic is shown in Figure 14-4
Document #: 38-08002 Rev. *BPage 28 of 51
Page 29
3
3
.
GPIO
Pin
Port
Configuration
Register
M
U
X
CY7C6501
OR Gate
(1 input per
GPIO pin)
GPIO Interrupt
Flip Flop
1
D
CLR
Q
Interrupt
CY7C6511
Priority
Encoder
IRQout
Interrupt
Vector
1 = Enable
0 = Disable
IRA
Port Interrupt
Enable Register
1 = Enable
0 = Disable
Global
GPIO Interrupt
Enable
(Bit 5, Register 0x20)
Figure 14-4. GPIO Interrupt Structure
Refer to Sections 9.1 and 9.2 for more information of setting GPIO interrupt polarity and enabling individual GPIO interrupts. If
one port pin has triggere d an interrupt, no other port pins can cause a GPIO interrupt unti l that port pin ha s returned to it s inactive
(non-trigger) state or its corresponding port interrupt enable bit is cleared. The USB Controller does not assign interrupt priority
to different port pins and the Port Interrupt Enable Registers are not cleared during the interrupt acknowledge process.
14.8I2C Interrupt
The I2C interrupt occurs after vario us events on the I2C-compatible bus to signal the nee d for firmware interaction. T his generally
involves reading the I
2
C Data Register as appropriate, and finally writing the Processor Status and Control Register (Figure 13-1) to initiate the
I
subsequent transacti on. The interru pt indi cates that st atus bi ts are st able an d it is sa fe to read an d write the I
to Section 12.0 for details on the I
When enabled, th e I
bits are in th e I
1. In slave receive mode, after the slave receives a by te of data: The Addr bit is set, if this is th e first byte sinc e a start or restart
signal was sent by the external master. Firmware must read or write the data register as necessary, then set the ACK, Xmit MODE, and Continue/Busy bits appropriately for the next byte.
2. In sla ve receive mode, after a stop bit is detected: The Received Stop bit is s et, if the stop bit follows a slave receive transactio n
where the ACK bit was cleared to 0, no stop bit detection occurs.
3. In slave transmit mode, after the slave trans mi t s a byte of data: The ACK bit indicates if the master that requ ested the byte
acknowledged the byte. If more bytes are to be sent, firmware writes the next byte into the Data Register and then sets the
XmitMODE and Continue/Busy bits as required.
4. In master transmit mode, after the master sends a byte of data. Firmware should load the Data Register if necessary, and
set the Xmit MODE, MSTR MODE, and Continue/Busy bits approp ria tely. Clearing the MSTR MODE bit issues a stop signal
2
to the I
C-compatible bus and return to the idle state.
5. In master receive mode, after the master receives a byte of data: Firmware should read the data and set the ACK and Continue/Busy bits appropriately for the next byte. Clearing the MSTR MODE bit at the same time causes the master state
machine to issue a stop signal to the I
6. When the master loses arbitration: This c ond iti on c le ars the MSTR MODE bit and sets the ARB Lost/Restart bi t im me dia tel y
and then waits for a stop signal on the I
The Continue/Busy bit is cleared by hard ware prior to inte rrupt conditions 1 to 4. Once th e Data Regi ster has been read or written,
firmware should c onfigure the other control bits and set the Continue/Busy bit for subs equent transa ctions. Foll owing an inte rrupt
from master mode, firmware should perform only one write to the Status and Control Register that sets the Continue/Busy bit,
without checking the value of the Continue/Busy bit. The Busy bit may otherwise be active and I
changed by the hardware during the transaction, until the I
2
C Status and Control Register (Figure 12-2) to determine the cause of the interrupt, loading/reading the
2
2
C registers.
2
C-compatible s tate machines generate interrupt s o n completi on of the follow ing cond itions. T he referenced
2
C Status and Control Register.
2
C-compatible bus and leave the I2C-compatible hardware in the idle state.
2
C-compatible bus to generate the interrupt.
2
2
C interrupt occurs.
C register contents may be
C registers. Refer
Document #: 38-08002 Rev. *BPage 29 of 51
Page 30
CY7C6501
3
3
15.0 USB Overview
The USB hardware includes a U SB Hub repeater w ith one upstre am and up to se ven downstre am ports. The USB Hub repeater
interfaces to the microcontroller through a full-speed serial interface engine (SIE). An external series resistor of R
placed in series with all upstream and downstr eam USB outputs in order to meet the USB driver requirements of the USB
specification. The CY7C65x13 microcontroller can provide the functionali t y of a co mp oun d dev ic e co ns is ting of a USB hu b and
permanent ly attached f unctions.
15.1USB Serial Interface Engine (SIE)
The SIE allows the C Y7C65x 13 mi croco ntrolle r to com municat e wi th the USB hos t throu gh th e USB rep eater p ortion of th e hub.
The SIE simplifies th e inte rface betwe en th e microc ontrol ler an d USB by inc orporati ng ha rdware th at ha ndles the f ollowin g US B
bus activity independen tly of the micro con trol le r:
• Bit stuffing/unstuffing
• Checksum genera tion / ch ec ki ng
• ACK/NAK/STALL
• Token type identifi ca tio n
• Address checking.
Firmware is required to handle the following USB interface tasks:
• Coordinate enumeration by responding to SETUP packets
• Fill and empty the FIFOs
• Suspend/Resume coordination
• Verify and select DATA toggle values.
CY7C6511
must be
ext
15.2USB Enumeration
The internal hub and any compound device functio n are enumerated under firmware c ontrol. The hub is enumerate d first, followed
by any integrated compound function. After the hub is enumerated, the USB host can read hub connection status to determine
which (if any) of the downstream ports need to be enumerated. The following is a brief summary of the typical enumeration
process of the CY7C6 5x13 by the USB host. For a det ailed description of the enumeration proc ess, refer to the USB specifi cation.
In this description, ‘Firmware’ refers to embedded firmware in the CY7C65x13 controller.
1. The host compu ter sends a SETUP packet followed by a DATA packet to USB address 0 requesting the Device descriptor.
2. Firmware decodes the request and retrieves its Device descriptor from the program memory tables.
3. The host computer performs a control read seq uence and Firmw are responds by s ending the Devic e descriptor over the USB
bus, via the on-chip FIFOs.
4. After receiving the descriptor, the host sends a SETUP packet followed by a DATA packet to address 0 assigning a new USB
address to the device.
5. Firmware stores the new address in its USB Device Address Register (for example, as Address B) after the no-data control
sequence complete s.
6. The host sends a request for the Device descriptor using the new USB address.
7. Firmware decodes the request and retrieves the Device descriptor from program memory tables.
8. The host performs a control read sequence and Firmware responds by sending its Device descriptor over the USB bus.
9. The host generates control reads from the device to request the Configuration and Report descriptors.
10.Once the device receives a Set Configuration request, its functions may now be used.
11.Following enumeration as a hub, Firmware can optionally indicate to the host that a compound device exists (for example, the
keyboard in a keyboard/hub device).
12.The host carries out the enumeration process with this ad ditional function as though it were attached downst ream from the hub.
13.When the host assigns an address to this device, it is stored as the other USB address (for example, Address A).
Document #: 38-08002 Rev. *BPage 30 of 51
Page 31
CY7C6501
3
3
16.0 USB Hub
A USB hub is required to support:
• Connectivity beh avi or: se rvi ce co nnect/disconnect detect ion
• Bus fault detection and recovery
• Full-/Low-speed devic e sup port
These features are mappe d onto a hub repeate r and a hub controller . T he hub controller is sup ported by the proces sor integrated
into the CY7C65x13 microcontrollers. The hardware in the hub repeater detects whether a USB device is connected to a
downstream port. The con nec tio n to a do wns trea m p ort i s th roug h a d ifferential signal pai r (D + an d D–) . Eac h do w nst rea m port
provided by the hub requires external R
device connected, the hub reads a LOW (zero) on both D+ and D–. This condition is used to identify the “no connect” state.
The hub must have a resistor R
The hub generates an EOP at EOF1, in accordance with the USB 1.1 Specification (section 11.2.2, page 234) as well as USB
2.0 specification (section 11.2.5, page 304).
connected between its upstream D+ line and V
UUP
16.1Connecting/Disconnecting a USB Device
A low-speed (1.5 Mbp s) USB de vice has a p ull-up resistor o n the D– p in. At co nnect time, th e bias resist ors set th e sign al lev els
on the D+ and D– lines. When a low-speed device is connected to a hub port, the hub sees a LOW on D+ and a HIGH on D–.
This causes the hub repeater to set a connect bit in the Hub Ports Connect Status register for the downstream port (see
Figure 16-1). Then the hub repeater generates a Hub Interrupt to notify the microcontroller that there has been a change in the
Hub downstream status. The firmware sets the speed of this port in the Hub Ports Speed Register (see Figure 16-2).
A full-speed (12 Mbps) USB device has a pu ll-u p re sis to r from the D + pi n, s o th e h ub s ee s a HI GH o n D + a nd a LO W o n D–. In
this case, the hub repeater sets a connect bit in the Hub Ports Connect Status register and generates a Hub Interrupt to notify
the microcontroller of the change in Hub status. The firmware sets the speed of this port in the Hub Ports Speed Register (see
Figure 16-2)
Connects are recorded by the time a non-SE0 state lasts for more than 2.5 µs on a downstream port.
When a USB device is disco nnected from th e Hub, the downstream s ignal p air eventual ly floats to a sing le-ended ze ro state. The
hub repeater recognizes a disconnect once the SE0 state on a downstream port lasts from 2.0 to 2.5 µs. On a disconnect, the
corresponding bit in the Hub Ports Connect Status register is cleared, and the Hub Interrupt is generated
.
Hub Ports Connect StatusAddress 0x48
Bit #76543210
Bit NameReservedPort 7
Connect
Status
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 00000000
resistors from each signal line to ground, so that when a downstream port has no
UDN
to indicate it is a full speed USB device.
REG
Port 6
Connect
Status
Figure 16-1. Hub Ports Connect Status
Port 5
Connect
Status
Port 4
Connect
Status
Port 3
Connect
Status
CY7C6511
Port 2
Connect
Status
Port 1
Connect
Status
Bit [0..6] : Port x Connect Status (where x = 1..7).
When set to 1, Port x is connected; When set to 0, Port x is disconnected.
Bit 7 : Reserved.
Set to 0.
The Hub Ports Con nect S tatus register is cl eared to zero by reset or USB bus reset, then set to matc h the hardware configuration
by the hub repeater hardware. The Reserved bit [7] should always read as ‘0’ to indicate no connection
Set to 1 if the device plugged in to Port x is Low Speed; Set to 0 if the device plugged in to Port x is Full Speed.
Bit 7 : Reserved.
Set to 0.
The Hub Ports Speed register is cleared to zero by reset or bus reset. This must be set by the firmware on issuing a port reset.
The Reserved bit [7] should always read as ‘0.’
16.2Enabling/Disabling a USB Device
After a USB device connection has been detected, firmware must update status change bits in the hub status change data
structure that is polled periodically by the USB host. The host responds by sending a packet that instructs the hub to reset and
enable the downstre am po rt. Firmwa re then set s the bit in the H ub Port s Ena ble reg ister (Figure 16-3), for the downstream por t.
The hub repeater h ardware respond s to an enable bit in the Hu b Ports Ena ble register (Figure 16-3) by enabling the downstre am
port, so that USB traffic can flow to and from that port.
If a port is marked enabled and is not suspended, it receives all USB traffic from the upstream port, and USB traffic from the
downstream port is passed to the upstream port (unless babble is detected). Low-speed ports do not receive full-speed traffic
from the upstream port.
When firmware writes to the Hu b Ports Enabl e register (Figure16-3) to enable a po rt, the port is n ot ena bled until th e end of a ny
packet currently being transmitted. If there is no USB traffic, the port is enabled immediately.
When a USB device di sconn ectio n has b een detec ted, firm ware mu st upd ate sta tus bi ts i n the hu b cha nge st a tus da ta s tructu re
that is polled period icall y by th e USB hos t. In su spend ed mod e, a co nnect or disc onnec t even t gener ates an interru pt (if the hu b
interrupt is enabled) even if the port is disabled
Set to 1 if Port x is enabled; Set to 0 if Port x is disabled
Bit 7 : Reserved.
Set to 0.
The Hub Ports Enable register is cleared to zero by reset or bus reset to disable all downstream ports as the default condition.
A port is also disabled by internal hub hardware (enable bit cleared) if babble is detected on that downstream port. Babble is
defined as:
• Any non-idle downstream traffic on an enabled downstream port at EOF2.
• Any downstream port with upstream connectivity established at EOF2 (i.e., no EOP received by EOF2).
16.3Hub Downstream Ports Status and Control
Data transfer on hub down stream port s is contro lled ac cordi ng to the bit setting s of the H ub Dow nstream Po rt s Contro l Regis ter
(Figure 16-4). Each downstre am port is controlled by two bits, as defined in Table 16-1 below. The Hub Downstream Port s Control
Register is cleared upon reset or bus reset, and the reset state is the state for normal USB traffic. Any downstream port being
forced must be marked as disabled (Figure 16-3) for proper operation of the hub repeater.
Firmware should use t his register for driving bus reset and resume signaling to downstrea m ports. Controlling the port pins through
this register uses standard USB edge rate control according to the speed of the port, set in the Hub Port Speed Register.
The downstream USB ports are designed for connection of USB devices, but can also serve as output ports under firmware
control. This all ows unus ed USB port s to be used for f unctions such as d riving LE Ds or pro viding a dditional i nput sign als. Pull ing
up these pins to voltages above V
This register is not reset by USB bus reset. These bits must be cleared before going into suspend.
may cause current flow into the pin.
REF
Document #: 38-08002 Rev. *BPage 32 of 51
Page 33
CY7C6501
3
3
Hub Downstream Ports Control RegisterAddress 0 x4B
Bit # 76543210
Bit NamePort 4
Control Bit 1
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 00000000
Table 16-1. Control Bit Definition for Downstream Ports
An alternate means of forcing the downstream ports is through the Hub Ports Force Low Register (Figure 16-5) and Hub Ports
Force High Register (Figure16-6). With these registers the pins of th e d owns tre am po rts can be indivi dua ll y forc ed L OW, or left
unforced. Unlike the Hub Downstream Ports Control Register, above, the Force Low Register does not produce standard USB
edge rate control on the fo rced pins. Howev er, this register allow s downstream port pins to be held LOW in suspend. This regis ter
can be used to drive SE0 on all downstream ports when unconfigured, as required in the USB 1.1 specification
The data state of downstream ports can be read through the HUB Ports SE0 Status Register (Figure 16-7) and the Hub Ports
Data Register (Figure 16-8). The data read from the Hub Ports Data Register is the differential data only and is independent of
the settings of the Hub Ports Speed Register (Figure 16-2). When the SE0 condition is sensed on a downstream port, the
corresponding bits of the Hub Ports Data Register hold the last differential data state before the SE0. Hub Ports SE0 Status
Register and Hub Ports Data Register are cleared upon reset or bus reset
.
Hub Ports SE0 StatusAddress 0x4F
Bit # 76543210
Bit NameReservedPort 7
SE0 Status
Read/WriteRRRRRRRR
Reset 00000000
Document #: 38-08002 Rev. *BPage 33 of 51
Port 6
SE0 Status
Figure 16-7. Hub Ports SE0 Status Register
Force Low
D–[7]
Port 5
SE0 Status
Force Low
D+[6]
Port 4
SE0 Status
Force Low
D–[6]
Port 3
SE0 Status
Force Low
D+[5]
Port 2
SE0 Status
Force Low
D–[5]
Port 1
SE0 Status
Page 34
CY7C6501
3
3
Bit [0..6]: Port x SE0 Status (where x = 1..7).
Set to 1 if a SE0 is output on the Port x bus; Set to 0 if a Non-SE0 is output on the Port x bus.
Bit 7: Reserved.
Set to 0
.
Hub Ports DataADDRESS 0x50
Bit # 76543210
Bit NameReservedPort 7 Diff.
Read/WriteRRRRRRRR
Reset 00000000
Bit [0..6] : Port x Diff Data (where x = 1..7).
Set to 1 if D+ > D- (force d dif fere ntial 1, if sig nal is dif fere ntial, i.e. n ot a SE0 or SE1). Set to 0 if D- > D+ (forced di ff erential
0, if signal is differential, i.e. not a SE0 or SE1).
Bit 7 : Reserved.
Set to 0.
Data
16.4Downstream Port Suspend and Resume
The Hub Ports Suspend R egister (Figure 16-9) and Hub Ports Resume S tat us Regist er (Figure16-10) indicate the sus pend and
resume conditions on downstream ports. The suspend register must be set by firmware for any ports that are selectively
suspended. Also, this register is only valid for ports that are selectively suspended.
If a port is marked as selectively suspended, normal USB traffic is not sent to that port. Resume traffic is also prevented from
going to that port , un le ss the R es um e co me s f r om the s ele ct ively suspended port. I f a resume condition is d ete cted on the port,
hardware reflects a Resume back to the port, sets the Resume bit in the Hub Ports Resume Register, and generates a hub
interrupt.
If a disconnect occurs on a port marked as selectively suspended, the suspend bit is cleared.
The Device Remote Wakeup bi t (bit 7) of the Hub Ports Suspend Regi ster controls whet her or not the resume signal is propag ated
by the hub after a connect or a disconnect event. If the Device Remote Wakeup bit is set, the hub will automatically propagate
the resume signal after a con nect or a di scon nect ev ent. If the Dev ice Remo te Wakeup bit is cleared, th e hub will no t prop ag ate
the resume signal. The setting of the Device Remote Wakeup flag has no impact on the propagation of the resume signal after
a downstream remote wakeup event. The hub will automatically propagate the resume signal after a remote wakeup event,
regardless of the st ate of the De vice Remote w akeup bit. The state o f this bit has no impac t on the genera tion of the hub interrupt.
A resume bit is set automa tic all y w he n ha rdw are dete cts a resume condition on a se lec ti vel y s us pen ded downstream port. The
resume condition is a differential ‘1’ for a low-speed device and a differential ‘0’ for a full-speed device.
These registers are cleared on reset or USB bus reset
.
Bit [0..6] : Port x Selective Suspend (where x = 1..7).
Set to 1 if Port x is Selectively Suspended; Set to 0 if Port x Do not suspend.
Bit 7 : Device Remote Wake up .
When set to 1, Enable hardware upstream resume signaling for connect/disconnect events during global resume.
When set to 0, Disable hardware upstream resume signaling for connect/disconnect events during global resume.
Document #: 38-08002 Rev. *BPage 34 of 51
Page 35
CY7C6501
3
3
Hub Ports ResumeAddress 0x4E
Bit # 76543210
Bit NameReservedResume 7Resume 6Resume 5Resume 4Resume 3Resume 2Resume 1
Read/Write- RRRRRRR
Reset 00000000
Figure 16-10. Hub Ports Resume Status Register
Bit [0..6] : Resume x (where x = 1..7).
When set to 1 Port x requesting to be resumed (set by hardware); default state is 0.
Bit 7 : Reserved.
Set to 0.
Resume from a selectively suspended port, with the hub not in suspend, typically involves the following actions:
1. Hardware detects the Resume , dri ves a K to the port, and generates the hub interrupt. The correspond ing bi t in the R es ume
Status Register (0x4E) reads ‘1’ in this case.
2. Firmware responds to hub interrupt, and reads register 0x4E to determine the source of the Resume.
3. Firmware begins driving K on the port for 10 ms or more through register 0x4B.
4. Firmware clears the Selective Suspend bit for the port (0x4D), which clears the Resume bit (0x 4E). This ends the hardware-driven Resume, but the firm ware- driv en R es ume c onti nu es. To prevent traffic bei ng f ed b y t he hub repeater to the port duri ng or
just after the Resume, firmware should disable this port.
5. Firmware drives a timed SE0 on the port for two low-speed b it tim es as a ppropriate. Firmware must dis ab le int errup t s during
this SE0 so the SE0 pulse isn’t inadvertently lengthened, and appear as a bus reset to the downstream device.
6. Firmware drives a J on the port for one low-speed bit time, then it idles the port.
7. Firmware re-enables the port.
Resume when the hub is suspended typically involves these actions:
1. Hardware detects the Resume, drives a K on the upstream (which is then reflected to all downstream enabled ports), and
generates the hub interrupt.
2. The part comes out of suspend and the clocks start.
3. Once the clocks are stable, firm ware ex ec uti on resumes. An internal cou nte r en sures that this takes at least 1 ms. Firmwa re
should check for Resume from any selectively suspended ports. If found, the Selective Suspend bit for the port should be
cleared; no other action is necessary.
4. The Resume ends when the host stops sending K from upstream. Firmware should check for changes to the Enable and
Connect Registers. If a port has become disabled but is still connected, an SE0 has been detec ted on the port. The port should
be treated as having been reset, and should be reported to the host as newly connected.
Firmware can choose to clear the Device Remote Wake-up bit (if set) to implement firmware timed states for port changes. All
allowed port changes wake the part. Then, the part can use internal timing to determine whether to take action or return to
suspend. If Device Remote Wake-up is set, automatic hardware assertions take place on Resume events.
CY7C6511
16.5USB Upstream Port Status and Control
USB status and co ntrol is re gulated by th e USB S t atus and Control Re gister, as shown in Figure 16-11. All bits in the register are
cleared during reset
.
USB Status and ControlAddress 0x1F
Bit # 76543210
Bit NameEndpoint
Size
Read/WriteR/WR/WRRR/WR/WR/WR/W
Reset 00000000
Bits[2..0]: Control Action
Set to control action as pe r table 16-2.Th e three control b its allow the upstream p ort to be driven manua lly by firmware . For
normal USB operation, all of these bits must be cleared. Table 16-2 shows how the control bits affect the upstream port.
Document #: 38-08002 Rev. *BPage 35 of 51
Endpoint
Mode
D+
Upstream
Figure 16-11. USB Status and Control Register
D–
Upstream
Bus ActivityControl
Action
Bit 2
Control
Action
Bit 1
Control
Action
Bit 0
Page 36
CY7C6501
3
3
Table 16-2. Control Bit Definition for Upstream Port
This is a “sticky” bit that indicates if any non-idle USB event has occurred on the upstream USB port. Firmware should
check and clear th is bit periodic ally to detect any loss of bus a ctivity . W riting a ‘0’ to the Bus Activity bi t clears it, whil e writing
a ‘1’ preserves the current value. In other words, the firmware can clear the Bus Activity bit, but only the SIE can set it.
Bits 4 and 5: D– Upstream and D+ Upstream.
These bits give the state of each upstream port pin individually: 1 = HIGH, 0 = LOW.
Bit 6: Endpoint Mode.
This bit used to configure the number of USB endpoints. See Section 17.2 for a detailed description.
Bit 7: Endpoint Size.
This bit used to configure the number of USB endpoints. See Section 17.2 for a detailed description.
The hub generates an EOP at EOF1 in accordance with the USB 1.1 Specification, Section 11.2.2.
CY7C6511
17.0 USB Serial Interface Engine Operation
The CY7C65x13 SIE supports operation as a single device or a compound device. This section describes the two device
addresses, the configurable endpoints, and the endpoint function.
17.1USB Device Addresses
The USB Controller provi des two USB Devic e Address Regi sters: A (addres sed at 0x 10)and B (addre ssed at 0x40). U pon re set
and under default con ditions, Device A h as three e ndpoint s and Dev ice B has two endpoint s. The USB Device Ad dress R egister
contents are cleared du ring a reset , setting th e USB device addresses to zero and disabling these addre sses. Figure 17-1 shows
the format of the USB Address Registers.
USB Device Address (Device A, B)Addresses 0x10(A) and 0x40(B)
Firmware writes this bits during the USB enumeration process to the non-zero address assigned by the USB host.
Bit 7: Device Address Enable.
Must be set by firmware before the SIE can respond to USB traffic to the Device Address.
17.2USB Device Endpoints
The CY7C65x13 c on trol ler su pports up to two a ddre sses an d five endpoints f or c om m uni ca tion w i th the ho st. The configuration
of these endpoints , and associa ted FIFOs, is cont rolled by bit s [7,6] of the USB S tatus and Control Re gister (Figure 16-11). Bit 7
controls the size of the endpoints and bit 6 controls the number of addresses. These configuration options are detailed in
Table 17-1. Endpoint FIFOs are part of user RAM (as shown in Section 5.4.1).
Device
Address
Bit 6
Device
Address
Bit 5
Figure 17-1. USB Device Address Registers
Device
Address
Bit 4
Device
Address
Bit 3
Device
Address
Bit 2
Device
Address
Bit 1
Device
Address
Bit 0
Document #: 38-08002 Rev. *BPage 36 of 51
Page 37
CY7C6501
3
3
Table 17-1. Memory Allocation for Endpoints
USB Status And Control Register (0x1F) Bits [7, 6]
When the SIE writes data to a FIFO, the internal data bus is driven by the SIE; not the CPU. This causes a short delay in the
CPU operation. The delay is three clock cycles per byte. For example, an 8-byte data write by the SIE to the FIFO generates a
delay of 2 µs (3 cycles/byte * 83.33 ns/cycle * 8 bytes).
Start
AddressSizeLabel
17.3USB Control Endpoint Mode Registers
All USB devices are required to have a control endpoint 0 (EPA0 and EPB0) that is used to initialize and control each USB
address. Endpoint 0 provides access t o the device con figuration information and allows generi c USB status and control accesses .
Endpoint 0 is bidirectional to both receive and transmit data. The other endpoints are unidirectional, but selectable by the user
as IN or OUT endpoints.
The endpoint mode registers are cleared durin g reset. Whe n USB Status And Control Regis ter Bits [6,7] are set to [0,0] or [1,0] ,
the endpoint zero EPA0 and EPB0 mode registers use the format shown in Figure 17-2.
Two USB Addresses:
A (3 Endpoints) and
B (2 Endpoints)
Start
AddressSizeLabel
One USB Address:
A (5 Endpoints)
Start
AddressSizeLabel
CY7C6511
One USB Address:
A (5 Endpoints)
Start
AddressSize
USB Device Endpoint Zero Mod e (A0, B0)Addresses 0x12(A0) and 0x42(B0)
These sets the mode which control how the control endpoint responds to traffic.
Bit 4: ACK.
This bit is set whenever the SIE engages in a transaction to the register’s endpoint that completes with an ACK packet.
Bit 5: Endpoint 0 OUT Received.
1= Token received is an O UT token . 0= Token received is not an OUT toke n. This bit is set by the SIE to re port the ty pe of
token received by the corresponding device address is an OUT token. The bit must be cleared by firmware as part of the
USB processing.
Bit 6: Endpoint 0 IN Received.
1= Token received is an IN token. 0= Token received is not an IN token. This bit is set by the SIE to report the type o f token
received by the corresponding device address is an IN token. The bit must be cleared by firmware as part of the USB
processing.
Bit 7: Endpoint 0 SETUP Received.
1 = Token received is a SETUP to ken . 0= Token received is not a SETUP token. Th is bit i s se t O NLY by the SIE to report
the type of token received by the corresponding device address is a SETUP token. Any write to this bit by the CPU will
clear it (set it to 0). The bit is forced HIGH from the start of the dat a p ac ke t phase of the SETUP transaction until the s t art
of the ACK packet returned by the SIE. The CPU should not clear this bit during this interval, and subsequently, until the
CPU first does an IORD to this endpoint 0 mode register. The bit must be cleared by firmware as part of the USB
processing.
[4]
Endpoint 0
IN
Received
Figure 17-2. USB Device Endpoint Zero Mode Registers
Endpoint 0
OUT
Received
ACKMode Bit 3 Mode Bit 2Mode Bit 1Mode Bit 0
Document #: 38-08002 Rev. *BPage 37 of 51
Page 38
CY7C6501
3
3
Bits[6:0] of the endp oint 0 mode regis ter are lock ed from CPU write op erat ions wh eneve r the SIE has update d one of the se bi ts ,
which the SIE does only at the end of the tok en phase of a transact ion (SETUP... Data... ACK, OUT... Data... ACK, or IN... Data...
ACK). The CPU can unlock these bits by doing a subsequent read of this register. Only endpoint 0 mode registers are locked
when updated. The locking mechanism does not apply to the mode registers of other endpoints.
Because of these hard ware locking features, fi rmware must perform an IORD afte r an IOWR to an endpoint 0 register. This verifies
that the contents have changed as desired, and that the SIE has not updated these values.
While the SETUP b it is set, the CP U cannot write to the endpoint zero FIFOs. This prevent s firmware from ov erwriting an inc oming
SETUP transaction before firmw are has a chance to read the SETU P data. Refer to Table 17-1 for the appropriate endpoint zero
memory locatio ns.
The Mode bits (bits [3:0]) control how the endpoint responds to USB bus traffic. The mode bit encoding is shown in Table 18-1.
Additional information on the mode bits can be found in Table 18-2 and Table 18-3.
17.4USB Non-control Endpoint Mode Registers
The format of the non-control endpoint mode registers is shown in Figure17-3.
USB Non-control Device Endpoint ModeAddresses 0x14, 0x16, 0x44
Bit #76543210
Bit NameSTALLReservedReservedACKMode Bit 3Mode Bit 2Mode Bit 1Mode Bit 0
Read/WriteR/WR/WR/WR/WR/WR/WR/WR/W
Reset 00000000
Figure 17-3. USB Non-control Device Endpoint Mode Registers
[5]
CY7C6511
Bits[3..0] : Mode.
These sets the mode which control how the control endpoint responds to traffic. The mode bit encoding is shown in
Table 18-1.
Bit 4 : ACK.
This bit is set whenever the SIE engages in a transaction to the register’s endpoint that completes with an ACK packet.
Bits[6..5]: Reserved.
Must be written zero during register writes.
Bit 7: STALL.
If this STALL is set, the SIE stalls an OUT packet if the mode bits are set to ACK-IN, and the SIE stalls an IN packet if the
mode bits are set to ACK-OUT. For all other modes, the STALL bit must be a LOW.
17.5USB Endpoint Counter Registers
There are five Endpoint Counter registers, with identical formats for both control and non-control endpoints. These registers
contain byte co unt information for USB transactions , as well as bit s for data p acket status . The format of these registers is shown
in Figure 17-4.
USB Endpoint CounterAddresses 0x1 1, 0x13, 0x15, 0x41, 0x43
4. In 5-endpoint mode (USB Status And Control Register Bits [7,6] are set to [0,1] or [1,1]), Register 0x42 serves as non-control endpoint 3, and has the format for
non-control endpoints shown in Figure 17-3.
5. The SIE offers an “Ack out – Status in” mode and not an “Ack out – Nak in” mode. Therefore, if following the status stage of a Control Write transfer a USB host
were to immediately start the next transfer, the new Setup packet could override the data payload of the data stage of the previous Control Write.
These counter bits indicate the number of data bytes in a transaction. For IN transactions, firmware loads the count with
the number of bytes to be transmitted to the host from the endpoint FIFO. Valid values are 0 to 32, inclusive. For OUT or
Document #: 38-08002 Rev. *BPage 38 of 51
Page 39
CY7C6501
3
3
SETUP transactions, the c ount is u pdated by hardware to the num ber of dat a byt es rece ived, pl us two for th e CRC byte s.
Valid values are 2 to 34, inclusive.
Bit 6: Data Valid.
This bit is set on receiving a proper CRC wh en the endpoint FI FO buf fer is loaded wi th data during tran sactions. This bit is
used OUT and SETUP tokens only. If the CRC is not correct, the endpoint interrupt occurs, but Data Valid is cleared to a
zero.
Bit 7: Data 0/1 Toggle.
This bit selects th e DAT A p acket’ s toggle state: 0 for DAT A0, 1 for DAT A1. F or IN transacti ons, firmwa re must set this bit to
the desired state. For OUT or SETUP transactions, the hardware sets this bit to the state of the received Data Toggle bit.
Whenever the count updates from a SETUP or OUT transa ction on en dpo int 0, the counter regist er l oc ks a nd ca nnot be written
by the CPU. Reading the re gister unlocks i t. This prevents firmware from overw riting a status update on incoming SETU P or OUT
transactions before firmware has a chance to re ad the dat a. Only endpoi nt 0 counter r egister is loc ked when upda ted. The locki ng
mechanism does not apply to the count registers of other endpoints.
17.6Endpoint Mode/Count Registers Upd ate and Locking Mechanism
The contents of the endpoint mode and counter registers are updated, based on the packet flow diagram in Figure 17-5. Two
time points, SETUP and UPDATE, are shown in the same figure. The following activities occur at each time point:
SETUP:
The SETUP bit of the endpoint 0 mo de register is forced HIGH at this time. Thi s bit is force d HIGH by the SIE unti l the end of the
data phase of a control write transfer. The SETUP bit can not be cleared by firmware during this time.
The affected mode and counter registers of e ndp oint 0 are locked from any C PU write s o nc e th ey are upd ated . Th es e re gis ters
can be unlocked by a CPU read, only if the read operation occurs after the UPDATE. The firmware needs to perform a register
read as a part of the endpoint ISR processing to unlock the effected registers. The locking mechanism on mode and counter
registers ensures that the firmware recognizes the changes that the SIE might have made since the previous IO read of that
register.
UPDATE:
1. Endpoint Mode Register – All the bits are updated (except the SETUP bit of the endpoint 0 mode register).
2. Counter Registers – All bits are updated.
3. Interrupt – If an interrupt is to be generated as a result of the transaction, the interrupt flag for the corresponding endpoint is
set at this time. For details on what conditions are required to generate an endpoint interrupt, refer to Table 18-2.
4. The contents of the updated en dpoint 0 mode and c ounter reg isters are locked, except the SET UP bit of the endpo int 0 mod e
register which was locked earlier.
CY7C6511
Document #: 38-08002 Rev. *BPage 39 of 51
Page 40
CY7C6501
3
3
1. IN Token
CY7C6511
H
O
S
T
Host To DeviceDevice To Host
S
Y
N
C
S
Y
N
C
A
D
IN
D
R
Token PacketData Pa c k et
Host To Device
A
D
IN
D
R
Token Packet
C
E
R
N
C
D
5
P
C
E
R
N
C
D
5
P
UPDATE
D
S
A
Y
T
N
A
C
1/0
Device To Host
S
Y
NAK/STALL
N
C
Data Packet
Data
2. OUT or SETUP Token without CRC error
Host To Device
Host To Device
C
R
C
16
Host To Device
S
A
Y
C
N
K
C
Hand
Shake
Packet
UPDATE
Device To Host
D
E
V
I
C
S
Y
N
C
O
A
U
D
T
D
/
R
Set
up
Token Packet
C
E
R
N
C
D
5
P
SETUP
S
Y
N
C
D
A
Data
T
A
1/0
Data Packet
3. OUT or SETUP Token with CRC error
Host To Device
O
U
S
T
Y
/
N
Set
C
up
Token Packet
A
D
D
R
Figure 17-5. Token/Data Packet Flow Diagram
C
E
R
N
C
D
5
P
Host To Device
D
S
A
Y
T
N
A
C
1/0
Data
Data Packet
C
R
C
16
UPDATE
C
R
C
16
UPDATE only if FIFO is
S
Y
N
C
written
ACK,
NAK,
STAL
Hand
Shake
Packet
E
Document #: 38-08002 Rev. *BPage 40 of 51
Page 41
CY7C6501
3
3
18.0 USB Mode Tables
Table 18-1. USB Register Mode Encoding
Moder
Disable 0000ignoreignoreignore Ignore all USB traffic to this endpoint
Nak In/Out0001acceptNAKNAK Forced from Setup on Control end po int, from mo des other than 000 0
Status Out Only0010acceptstallcheck For Control endpoints
Stall In/Out 0011acceptstallstall For Control endpoints
Ignore In/Out 0100 acceptignoreignore For Control endpoints
Isochronous Out0101ignoreignorealwaysFor Isochronous endpoints
Mode
Bits SETUPINOUTComments
CY7C6511
Status In Only0110 acceptTX 0
Isochronous In0111ignore TX Count ignore For Isochronous endpoints
Nak Out1000ignoreignoreNAK Is set by SIE on an ACK from mode 1001 (Ack Out)
[6]
1001
Ack Out(ST ALL
Ack Out(STAL L
Nak Out - Status In1010 acceptTX 0
Ack Out - Status In1011 acceptTX 0
Nak In1100ignoreNAKignore Is set by SIE on an ACK from mode 1101 (Ack In)
Ack IN(STALL
Ack IN(STALL
Nak In - Status Out1110acceptNAKcheck Is set by SIE on an ACK from mode 1111 (Ack In – Status Out)
Ack In - Status Out1 111accept TX Count check On issuance of an ACK this mode is c hanged by SIE to 1110 (NAK In
Mode
This lists the mn emoni c giv en to the di ff eren t mod es tha t can be se t in t he Endp oin t Mod e Regis ter by writ ing to the l ower nibb le
(bits 0..3). The bit settings for different modes are covered in the column marked “Mode Bits”. The Status IN and Status OUT
represent the Status stage in the IN or OUT transfer involving the control endpoint.
Mode Bits
These column lists the encoding for different modes by setting Bits[3..0] of the Endpoint Mode register. This modes represents
how the SIE responds to different tokens sent by the host to an endpoint. For instance, if the mode bits are set to “0001” (NAK
IN/OUT), the SIE will respond with an
• ACK on receiving a SETUP token from the host.
• NAK on receiving an OUT token from the host.
• NAK on receiving an IN token from the host.
Refer to section 13.0 for more information on the SIE functioning.
SETUP, IN, and OUT
These columns shows the SIE’s response to the host on receiving a SETUP, IN and OUT token depending on the mode set in
the Endpoint Mode Register.
=0)
[6]
=1)
1001
[6]
=0)
[6]
=1)
1101
1101
ignore
ignore
ignore
ignore
BYte
ignore
ignore
BYte
BYte
TX Count
stall
stall For Control Endpoints
ACK
On issuance of an ACK this mode is changed by SIE to 1000 (NAK
stall
Out)
NAK Is set by SIE on an ACK from mode 1011 (Ack Out – Status In)
ACK On issuance of an ACK this mode is changed by SIE to 1010 (NAK
Out – Status In)
ignore
On issuance of an ACK this mode is changed by SIE to 1 100 (NAK In)
ignore
– Status Out)
A “Check” on the OUT token column, implies that on receiving an OUT token the SIE checks to see whether the OUT packet is
of zero length and h as a Dat a Toggle (DTOG) set to ‘1.’ If the DT OG bit is se t and th e re ceived O UT Pack et has zero le ngt h, the
OUT is ACKed to comp lete th e transac tion. If either o f th is co nditio n is not m et the SI E will respond w ith a STALLL or just ignore
the transaction.
A “TX Count” entry in the IN colu mn impli es that the SIE tr ansmit the number of bytes specifi ed in the Byte Count (bit s 3..0 of th e
Endpoint Count Register) to the host in response to the IN token received.
Note:
6. STALL bit is bit 7 of the USB Non-control Device Endpoint Mode registers. For more information, refer to Section 17.4.
Document #: 38-08002 Rev. *BPage 41 of 51
Page 42
CY7C6501
3
3
A “TX0 Byte” entry in the IN column implies that th e SI E tra nsm it a zero length byte p ac ket in res po nse to th e IN token received
from the host.
An “Ignore” in any of the columns means that the device will not send any handshake tokens (no ACK) to the host.
An “Accept” in any of the columns means that the device will respond with an ACK to a valid SETUP transaction tot he host.
Comments
Some Mode Bits are automatically changed by the SIE in response to certain USB transactions. For example, if the Mode Bits
[3:0] are set to '1111' which is ACK IN-Status OUT mode as shown in Table 18-1, the SIE wil l change the endpoint Mode Bi ts [3:0]
to NAK IN-Status OUT mode (1110) after ACK’ing a valid status stage OUT token. The firmware needs to update the mode for
the SIE to respond appropriat ely . See Table 18-1 for more det ails on what modes w ill be changed by the SIE . A disabled endpoi nt
will remain disab led unt il cha nged b y firmwa re, and all end points reset to the disabl ed mod e (0000 ). Firmw are n ormall y enables
the endpoint mode after a SetConfiguration request.
Any SETUP packet to an enabled endpoint with mode set to accept SETUPs will be changed by the SIE to 0001 (NAKing INs
and OUTs). Any mode set to accept a SETUP will send an ACK handshake to a valid SETUP token.
The control endpoint has three sta tus bit s for ident ifying the toke n typ e received (SETUP, IN, or OUT), but the endpoint m ust be
placed in the correct mode to function as such. Non-control endpoints should not be placed into modes that accept SETUPs.
Note that most modes that contro l transactions inv olving an ending ACK, are ch anged by the SIE to a correspon ding mode which
NAKs subsequent packets following the ACK. Exceptions are modes 1010 and 1110
.
Table 18-2. Decode table for Table 18-3: “Details of Modes for Differing Traffic Conditions”
CY7C6511
Properties of Incoming
Packets
3 2 1 0
Endpoint Mode
encoding
Legend:TX : transmitUC : unchanged
TokencountbufferdvalDTOGDVALCOUNTSetupInOutACK3 2 1 0 Response Int
Received Token
(SETUP/IN/OUT)
The validity of the received data
The quality status of the DMA buffer
The number of received bytesAcknowledge phase completed
RX : receiveTX0 :Transmit 0 length packet
available for Control endpoint only
x: don’t care
Changes to the Internal Register made by the SIE on receiving an incoming packet
Byte Count (bits 0..5, Figure 17-4)
Data Valid (bit 6, Figure 17-4)
Data0/1 (bit7 Figure 1 7-4)
from the hostInterrupt
PID Status Bits
(Bit[7..5], Figure 17-2)
Endpoint Mode bits
Changed by the SIE
SIE’s Response
to the Host
The response of the SIE can be summarized as follows:
1. The SIE will only respond to valid transactions, and will ignore non-valid ones.
2. The SIE will generate an interrupt when a valid transaction i s completed or when the FIFO is corrupted. FIFO co rruption occurs
during an OUT or SETUP transaction to a valid internal address, that ends with a non-valid CRC.
3. An incoming Data packet is valid if the count is <
Endpoint Size + 2 (includes CRC) and passes all error checking;
4. An IN will be ignored by an OUT configured endpoint and visa versa.
5. The IN and OUT PID status is updated at the end of a transaction.
6. The SETUP PID status is updated at the beginning of the Data packet phase.
Document #: 38-08002 Rev. *BPage 42 of 51
Page 43
CY7C6501
3
3
7. The entire Endpoint 0 mode register and the Count register are locked to CPU writes at the end of any transaction to that
endpoint in which an ACK is transferred. These registers are only unlocked by a CPU read of the register, which should be
done by the firmware only afte r the trans action is comple te. This repre sent s abou t a 1-µs wi ndow in w hich the CPU is lo cked
from register writes to these USB registers. Normally the firmware should perform a register read at the beginning of the
Endpoint ISRs to unlock and get the mode register information. The interlock on the Mode and Count registers ensures that
the firmware recogniz es the chan ges that the SIE migh t have mad e during the pre vious transa ction. Note that the set up bit of
the mode register is NOT locked. This means that before writing to the mode register, firmware must first read the register to
make sure that the setup b it is not s et (which indicates a setup wa s received , while pro cessing th e current USB request ). This
read will of course unlock the register. So care must be taken not to overwrite the register elsewhere
.
Table 18-3. Details of Modes for Differing Traffic Conditions (see Table 18-2 for the decode legend)
SETUP (if accepting SETUPs)
Properties of Incoming PacketChanges made by SIE to Internal Registers and Mode Bits
Mode Bitstokencount bufferdvalDTOGDVALCOUNT SetupInOut ACKMode Bits ResponseIntr
See Table 18-1 Setup <= 10 datavalidupdates 1updates 1UC UC 10 001ACKyes
See Table 18-1 Setup> 10junkxupdates updates updates 1UC UCUCNoChange ignoreyes
See Table 18-1 Setupxjunkinvalidupdates0updates 1UCUCUCNoChange ignoreyes
Properties of Incoming PacketChanges made by SIE to Internal Registers and Mode Bits
Mode Bitstokencount bufferdvalDTOGDVALCOUNT SetupInOut ACKMode Bits ResponseIntr
CONTROL WRITE
Properties of Incoming PacketChanges made by SIE to Internal Registers and Mode Bits
Mode Bitstokencount bufferdvalDTOGDVALCOUNT SetupInOut ACKMode Bits ResponseIntr
CONTROL READ
Properties of Incoming PacketChanges made by SIE to Internal Registers and Mode Bits
Mode Bitstokencount bufferdvalDTOGDVALCOUNT SetupInOut ACKMode Bits ResponseIntr
OUT ENDPOINT
Properties of Incoming PacketChanges made by SIE to Internal Registers and Mode Bits
Mode Bitstokencount bufferdvalDTOGDVALCOUNT SetupInOut ACKMode Bits ResponseIntr
IN ENDPOINT
Properties of Incoming PacketChanges made by SIE to Internal Registers and Mode Bits
Mode Bitstokencount bufferdvalDTOGDVALCOUNT SetupInOut ACKMode Bits ResponseIntr
Normal In/erroneous Out
110 1OutxUCxUCUCUCUCUC UCUCNoChange ignoreno
0x09HAPI/I2C ConfigurationI2C Position ReservedReservedReservedReservedReservedI2C Port
C
2
I
HAPI
0x10USB Device Address ADevice
0x11EP A0 Counter
Register
0x12EP A0 Mode RegisterEndpoint0
0x13EP A1 Counter
Register
0x14EP A1 Mode RegisterSTALL--ACKMode Bit 3 Mode Bit 2 Mode Bit 1 Mode Bit 0
0x15EP A2 Counter
Register
0x16EP A2 Mode RegisterSTALL--ACKMode Bit 3 Mode Bit 2 Mode Bit 1 Mode Bit 0BBBBBBBB00000000
Enable
Enable
Enable
Config Bit 1
Address A
Enable
Data 0/1
Toggle
SETUP
Received
Data 0/1
Toggle
Data 0/1
Toggle
P0.6 Intr
Enable
P1.6 Intr
Enable
P2.6 Intr
Enable
Port 3
Config Bit 0
Device
Address A
Bit 6
Data Valid Byte Count
Endpoint0
Received
Data Valid Byte Count
Data Valid Byte Count
P0.5 Intr
Enable
P1.5 Intr
Enable
P2.5 Intr
Enable
Port 2
Config Bit 1
Device
Address A
Bit 5
Bit 5
Endpoint0
IN
OUT
Received
Bit 5
Bit 5
P0.4 Intr
Enable
P1.4 Intr
Enable
P2.4 Intr
Enable
Port 2
Config Bit 0
Device
Address A
Bit 4
Byte Count
Bit 4
ACKMode Bit 3 Mode Bit 2 Mode Bit 1 Mode Bit 0
Byte Count
Bit 4
Byte Count
Bit 4
P0.3 Intr
Enable
ReservedP1.2 Intr
P2.3 Intr
Enable
Port 1
Config Bit 1
Device
Address A
Bit 3
Byte Count
Bit 3
Byte Count
Bit 3
Byte Count
Bit 3
P0.2 Intr
Enable
Enable
ReservedReservedReserved
Port 1
Config Bit 0
Device
Address A
Bit 2
Byte Count
Bit 2
Byte Count
Bit 2
Byte Count
Bit 2
P0.1 Intr
Enable
P1.1 Intr
Enable
Enable
Port 0
Config Bit 1
Width
Device
Address A
Bit 1
Byte Count
Bit 1
Byte Count
Bit 1
Byte Count
Bit 1
P0.0 Intr
P1.0 Intr
P3.0 Intr
Config Bit 0
ReservedBBBBBBBB00000000
Address A
Byte Count
Byte Count
Byte Count
Enable
Enable
Enable
Device
CY7C6511
Port 0
Bit 0
Bit 0
Bit 0
Bit 0
oth/–[7]
BBBBBBBB11111111
BBBBBBBB11111111
WWWWWWWW 00000000
WWWWWWWW 00000000
WWWWWWWW 00000000
WWWWWWWW 00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
Default/
Reset
ENDPOINT A0, AI AND A2 CONFIGURATION
0x1FUSB Status and ControlEndpoint
CS
USB-
0x20Global Interrupt EnableReservedI2C
0x21Endpoint Interrupt
INTERRUPT
TIMER
C
2
I
ENDPOINT B0, B1 CONFIGURATION
Enable
0x24Timer (LSB)Timer Bit 7 Timer Bit 6 Timer Bit 5 Timer Bit 4 Timer Bit 3 Timer Bit 2 Timer Bit 1 Timer Bit 0RRRRRRRR00000000
0x25Timer (MSB)Reserved Reserved Reserved Reserved Timer Bit 11 Timer Bit 10 Time Bit 9Timer Bit 8----rrrr----0000
0x28I2C Control and StatusMSTR
0x29I2C Data I2C Data 7 I2C Data 6 I2C Data 5 I2C Data 4 I2C Data 3 I2C Data 2 I2C Data 1 I2C Data 0BBBBBBBBXXXXXXXX
0x40USB Device Address BDevice
0x41EP B0 Counter Register Data 0/1
0x42EP B0 Mode RegisterEndpoint 0
0x43EP B1 Counter Register Data 0/1
0x44EP B1 Mode RegisterSTALL--ACKMode Bit 3 Mode Bit 2 Mode Bit 1 Mode Bit 0BBBBBBBB00000000
Size
ReservedReservedReservedEPB1
Mode
Address B
Enable
Toggle
SETUP
Received
Toggle
Endpoint
ModeD+UpstreamD–Upstream
Interrupt
Enable
Continue/
Busy
Device
Address B
Bit 6
Data Valid Byte Count
Endpoint 0
IN
Received
Data Valid Byte Count
GPIO
Interrupt
Enable
Xmit
Mode
Device
Address B
Bit 5
Bit 5
Endpoint 0
OUT
Received
Bit 5
Reserved USB Hub
Interrupt
Enable
Device
Address B
Byte Count
Byte Count
Bus ActivityControl
Interrupt
Enable
EPB0
Interrupt
Enable
ACKAddrARB Lost/
Device
Bit 4
Bit 4
ACKMode Bit 3 Mode Bit 2 Mode Bit 1 Mode Bit 0BBBBBBBB00000000
Bit 4
Address B
Bit 3
Byte Count
Bit 3
Byte Count
Bit 3
Bit 2
1.024-ms
Interrupt
Enable
EPA2
Interrupt
Enable
Restart
Device
Address B
Bit 2
Byte Count
Bit 2
Byte Count
Bit 2
Control
Bit 1
128-µs
Interrupt
Enable
EPA1
Interrupt
Enable
Received
Stop
Device
Address B
Bit 1
Byte Count
Bit 1
Byte Count
Bit 1
Control
Bit 0
USB Bus
RESET
Interrupt
Enable
EPA0
Interrupt
Enable
I2C
Enable
Device
Address B
Bit 0
Byte Count
Bit 0
Byte Count
Bit 0
BBRRBBBB-0xx0000
-BBBBBBB-0000000
---
BBBBB---00000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
Note:
7. B: Read and Write; W: Write; R: Read.
Document #: 38-08002 Rev. *BPage 45 of 51
Page 46
3
3
19.0 Register Summary (continued)
AddressRegister Name Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Read/Write/B
0x48Hub Port Connect StatusReservedPort 7
0x49Hub Port EnableReservedPort 7
0x4AHub Port SpeedReservedPort 7
0x4BHub Port Control (Ports
4:1)
0x4CHub Port Control (Ports
7:5)
0x4DHub Port SuspendDevice
0x4EHub Port Resume StatusReservedResume 7Resume 6Resume 5Resume 4 Resume 3Resume 2Resume 10x4FHub Port SE0 StatusReservedPort 7
0x50Hub Ports DataReservedPort 7
0x51Hub Port Force Low
(Ports 4:1)
0x52Hub Port Force Low
(Ports 7:5)
HUB PORT CONTROL, STATUS, SUSPEND RESUME, SE0, FORCE LOW
0xFFProcess Status & ControlIRQ
Port 4
Control Bi t 1
ReservedReservedPort 7
Remote
Wakeup
Force Low
D+[4]
ReservedReservedForce Low
Pending
Connect
Status
Enable
Speed
Port 4
Control Bit 0
Port 7
Selective
Suspend
SE0 Status
Diff. Data
Force Low
D–[4]
Watchdog
Reset
Port 6
Connect
Status
Port 6
Enable
Port 6
Speed
Port 3
Control Bit 1
Control Bit 1
Port 6
Selective
Suspend
Port 6
SE0 Status
Port 6
Diff. Data
Force Low
D+[3]
D+[7]
USB Bus
Reset
Interrupt
Port 5
Connect
Status
Port 5
Enable
Port 5
Speed
Port 3
Control Bit 0
Port 7
Control Bit 0
Port 5
Selective
Suspend
Port 5
SE0 Status
Port 5
Diff. Data
Force Low
D–[3]
Force Low
D–[7]
Power-on
Reset
Port 4
Connect
Status
Port 4
Enable
Port 4
Speed
Port 2
Control Bit 1
Port 6
Control Bit 1
Port 4
Selective
Suspend
Port 4
SE0 Status
Port 4
Diff. Data
Force Low
D+[2]
Force Low
D+[6]
SuspendInterrupt
Port 3
Connect
Status
Port 3
Enable
Port 3
Speed
Port 2
Control Bit 0
Port 6
Control Bit 0
Port 3
Selective
Suspend
Port 3
SE0 Status
Port 3
Diff. Data
Force Low
D–[2]
Force Low
D–[6]
Enable
Sense
Port 2
Connect
Status
Port 2
Enable
Port 2
Speed
Port 1
Control Bit 1
Port 5
Control Bit 1
Port 2
Selective
Suspend
Port 2
SE0 Status
Port 2
Diff. Data
Force Low
D+[1]
Force Low
D+[5]
ReservedRunRBBBBRBB00010001
Port 1
Connect
Status
Port 1
Enable
Port 1
Speed
Port 1
Control Bit 0
Port 5
Control Bit 0
Port 1
Selective
Suspend
Port 1
SE0 Status
Port 1
Diff. Data
Force Low
D–[1]
Force Low
D–[5]
CY7C6501
CY7C6511
oth/–[7]
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
BBBBBBBB00000000
--BBBBBB--000000
BBBBBBBB00000000
RRRRRRR00000000
RRRRRRRR00000000
RRRRRRRR00000000
BBBBBBBB00000000
--BBBBBB00000000
Default/
Reset
Document #: 38-08002 Rev. *BPage 46 of 51
Page 47
3
3
20.0 Sample Schematic
3.3v Regulator
IN
22x2(R
6.000 MHz
USB-B
Vbus
DD+
GND
SHELL
Optional
2.2 uF
Vref
1.5K
(R
4.7nF
250 V A C
10M
UUP
)
Vbus
GND
ext
OUT
)
D0D0+
XTALO
XTALI
GND
GND
Vpp
.01 uF
Vcc
Vref
2.2 uF
.01 uF
Vref
D1D1+
D2-
D2+
D3-
D3+
D4-
D4+
22x8(R
15K(x8)
(R
UDN
CY7C6501
CY7C6511
USB-A
Vbus
DD+
GND
USB-A
)
ext
)
Vbus
DD+
GND
USB-A
Vbus
DD+
GND
USB-A
POWER
MANAGEMENT
Vbus
DD+
GND
21.0 Absolute Maximum Ratings
Storage Temperature ...................................................................................................................................–65°C to +150°C
Ambient Temperature with Power Applied..........................................................................................................0°C to +70°C
Supply voltage on V
DC Input Voltage................................................................................................................................... –0.5V to +V
DC Voltage applied to Outputs in High Z State..................................................................................... –0.5V to +V
relative to VSS..............................................................................................................–0.5V to +7.0V
CC
CC
CC
+ 0.5V
+ 0.5V
Power Dissipation.......................................................................................................................................................500 mW
Static Discharge Voltage ............................................................................................................................................> 2000V
Latch-up Current ..................................................................................................................................................... > 200 mA
Max Output Sink Current into Port 0, 1, 2, 3 ................................................................................................................ 60 mA
Max Output Sink Current into DAC[7:2] Pins................................................................................................................ 10 mA
Max Output Source Current from Port 1, 2, 3, 4, 5, 6, 7 .............................................................................................. 30 mA
Document #: 38-08002 Rev. *BPage 47 of 51
Page 48
CY7C6501
3
3
22.0 Electrical Characteristics
f
= 6 MHz; Operating Temperature = 0 to 70°C, VCC = 4.0V to 5.25V
OSC
ParameterDescriptionConditionsMin.Max.Unit
General
V
V
I
CC
I
SB1
I
ref
I
il
V
V
V
C
I
lo
R
R
R
t
vccs
V
V
Z
R
V
V
V
V
REF
pp
di
cm
se
in
ext
UUP
UDN
UOH
UOL
O
up
ITH
H
OL
OH
Reference Voltage3.3V ±5%3.153.45V
Programming Voltage (disabled)–0.40.4V
VCC Operating CurrentNo GPIO source current50mA
Supply Current—Suspend Mode50µA
V
Operating CurrentNo USB Traffic
REF
[8]
Input Leakage CurrentAny pin1µA
USB Interface
Differential Input Sensitivity | (D+)–(D–) |0.2V
Differential Input Common Mode Range0.82.5V
Single Ended Receiver Threshold0.82.0V
Transceiver Capacitance20pF
Hi-Z State Data Line Leakage0V < V
< 3.3V–1010µA
in
External USB Series ResistorIn series with each USB pin1921Ω
External Upstream USB Pull-up Resistor1.5 kΩ ±5%, D+ to V
Purchase of I2C components from Cypress, o r one of its s ublicensed Associated Com panies, c onveys a lic ense under the Philips
I2C Patent Rights to u se these component s in an I2C system, provided th at the system con forms to the I2C St andard Specifica tion
as defined by Philip s. All product and comp any names menti oned in this document are the trademarks of their resp ective holders.
Document Title: CY7C65013/CY7C65113 USB Hub with Microcontroller
Document Number: 38-08002
REV.ECN NO. Issue Date
**10996502/22/02SZVChange from Spec number: 38-00590 to 38-08002
*A12037212/17/02MONAdded register bit definitions.
*B12452203/13/03MONFixed the figure on page 42 regarding the update of mode registers. The
Orig. of
ChangeDescription of Change
Added default bit state of each regi ster.
Corrected the Schematic (location of the pull-up on D+).
Corrected the Logical Diagram (removed the extra GPIO Port 1).
Added register summary.
Modified Figure 17-5, more labeling.
Removed information on the availability of the part in PDIP package.
Modified Table 18-1 and provided more explanation regarding
locking/unlocking mechanism of the mode register.
Removed any inform ation regar ding the spe ed detect b it in Hub Port Speed
register being set by hardware.
arrows in the figure were misplaced and the figure was unreadable. This is
an important figure for understanding mode register functioning.
CY7C6511
Document #: 38-08002 Rev. *BPage 51 of 51
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.