• Low-cost solution for low-speed applications with high
I/O requirements such as keyboards, keyboards with
integrated pointing device, gamepads, and many
others
• USB Specification Compliance
— Conforms to USB Specification, V ersions 1.1 and 2.0
— Conforms to USB HID Specification, Version 1.1
— Supp orts 1 device address and 3 data endpoints
— Integrated USB transceiver
• Internal memory
— 256 bytes of RAM
— 8 Kbytes of EPROM
• Interface can auto-configure to operate as PS2 or USB
•I/O port
— The CY7C63413C/513C have 24 General Purpose I/O
(GPIO) pins (Port 0 to 2) cap able of sinking 7 mA per
pin (typical)
— The CY7C63613C has 12 General Purpose I/O (GPIO)
pins (Port 0 to 2) capable of sinking 7 mA per pin
(typical)
— The CY7C63413C/513C have eight GPIO pins (Port
3) capable of sinking 12 mA per pin (typical) which
can drive LEDs
— The CY7C63613C has four GPIO pins (Port 3) capable
of sinking 12 mA per pin (typical) which can driv e
LEDs
— Higher current drive is available by connecting
multiple GPIO pins together to drive a common
output
— Each GPIO port can be configured as inputs with
internal pull-ups or open drain outputs or traditional
CMOS outputs
— The CY7C63513C has an additional eight I/O pins on
a DAC port which has programmable current sink
outputs
— Mask able interrupts on all I/O pins
• 12-bit free-running timer with one microsecond clock
ticks
• Watch Dog Timer (WDT)
• Internal Power-On Reset (POR)
• Improved output drivers to reduce EMI
• Operating voltage from 4.0V to 5.5V DC
• Operating temperature from 0 to 70 degrees Celsius
• CY7C63413C available in 40-pin PDIP , 48-pin SSOP, 48pin SSOP - Tape reel, all in Lead-Free versions for
production
• CY7C63513C available in 48-pin SSOP Lead-Free
packages for production
• CY7C63613C available in 24-pin SOIC Lead-Free
packages for production
• Industry-standard programmer support
Functional Overview
The CY7C63413C/513C/613C are 8-bit RISC One Time
Programmable (OTP) microcontrollers. The instruction set has
been optimized specifically for USB operations, although the
microcontrollers can be used for a variety of non-USB
embedded applications.
The CY7C63413C/513C features 32 General-Purpose I/O
(GPIO) pins to support USB and other applications. The I/O
pins are grouped into four ports (Port 0 to 3) where each port
can be configured as inputs with internal pull -ups, open drain
outputs, or traditional CMOS outputs. The CY7C63413C/513C
have 24 GPIO pins (Ports 0 to 2) that are rated at 7 mA typical
sink current. The CY7C63413C/513C has 8 GPIO pins (Port
3) that are rated at 12 mA typical sink current, which allows
these pins to drive LEDs.
The CY7C63613C features 16 General-Purpose I/O (GPIO)
pins to support USB and other applications. The I/O pins are
grouped into four ports (Port 0 to 3) where each port can be
configured as inputs with internal pull-ups, open drain outputs,
or traditional CMOS outputs. The CY7C63613C has 12 GPIO
pins (Ports 0 to 2) that are rated at 7 mA typical sink current.
The CY7C63613C has 4 GPIO pins (Port 3) that are rated at
12 mA typical sink current, which allows these pins to drive
LEDs.
Multiple GPIO pins can be connected together to drive a single
output for more dri ve current capacity. Additionally, each I/O
pin can be used to generate a GPIO interrupt to the microcontroller. Note the GPIO interrupts all share the same “GPIO”
interrupt vector.
The CY7C63513C features an additional 8 I/O pins in the DAC
port. Every DAC pin includes an integrated 14-Kohm pull-up
resistor. When a “1” is written to a DAC I/O pin, the output
current sink is disabled and the output pin is driven high by the
internal pull-up resistor. When a “0” is written to a DAC I/O pin,
the internal pull-up is disabled and the output pin provides the
programmed amount of sink
current. A DAC I/O pin can
be used as an input with an
internal pull-up by writing a
“1” to the pin.
Cypress Semiconductor Corporation•198 Champion Court•San Jose, CA 95134-1709•408-943-2600
Document #: 38-08027 Rev. *B Revised January 6, 2006
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
The sink current for each DAC I/O pin can be individually
programmed to one of sixteen values using dedicated Isink
registers. DAC bits [1:0] can be used as high current outputs
with a programmable sink current range of 3.2 to 16 mA
(typical). DAC bits [7:2] have a programmable current sink
range of 0.2 to 1.0 mA (typical). Again, multiple DAC pins can
be connected together to drive a single output that requires
more sink current capacity. Each I/O pin can be used to
generate a DAC interrupt to the microcontroller and the
interrupt polarity for each DAC I/O pin is individually programmable. The DAC port interrupts share a separate “DAC”
interrupt vector.
The Cypress microcontrollers use an external 6-MHz ceramic
resonator to provide a reference to an internal clock generator.
This clock generator reduces the clock-related noise
emissions (EMI). The clock generator provide s the 6 a nd 12MHz clocks that remain internal to the microcontroller.
The CY7C63413C/513C/613C are offered with single EPROM
options. The CY7C63413C, CY7C63513C and the
CY7C63613C have 8 Kbytes of EPROM.
These parts include Power-on Reset logic, a Watch Dog Timer ,
a vectored interrupt controller, and a 12-bit free-running timer.
The Power-On Reset (POR) logic detects when power is
applied to the device, resets the logic to a known state, and
begins executing instructions at EPROM address 0x0000. The
Watch Dog Timer can be used to ensure the firmware never
gets stalled for more than approximately 8 ms. The firmware
can get stalled for a variety of reasons, including errors in the
code or a hardware failure such as waiting for an interrupt that
never occurs. The firmware should clear the Watch Dog Timer
periodically. If the Watch Dog Timer is not cleared for approximately 8 ms, the microcontroller will generate a hardware
watch dog reset.
The microcontroller supports eight maskable interrupts in the
vectored interrupt controller. Interrupt sources include the USB
Bus-Reset, the 128-µs and 1.024-ms outputs from the freerunning timer, three USB endpoints, the DAC port, and the
GPIO ports. The timer bits cause an interrupt (if enabled) when
the bit toggles from LOW “0” to HIGH “1.” The USB endpoints
interrupt after either the USB host or the USB controller sends
a packet to the USB. The DAC ports have an additional level
of masking that allows the user to select which DAC inputs can
cause a DAC interrupt. The GPIO ports also have a level of
masking to select which GPIO inputs can cause a GPIO
interrupt. For additional flexibility, the input transition polarity
that causes an interrupt is programmable for each pin of the
DAC port. Input transition polarity can be programmed for
each GPIO port as part of the port configuration. The interrupt
polarity can be either rising edge (“0” to “1”) or falling edge (“1”
to “0”).
The free-running 12-bit timer clocked at 1 MHz provides two
interrupt sources as noted above (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 twice: once at the start
of the event, and once after the event is complete. The
difference between the two readings indicates the durati on of
the event measured in microseconds. The upper four bits of
the timer are latched into an internal register when the
firmware reads the lower eight bits. A read from the upper four
bits actually reads data from the internal register, instead of the
timer. This feature eliminates the need for firmware to attempt
to compensate if the upper four bits happened to incre ment
right after the lower 8 bits are read.
The CY7C63413C/513C/613C include an integrated USB
serial interface engine (SIE) that supports the integrated
peripherals. The hardware supports one USB device address
with three endpoints. The SIE allows the USB host to communicate with the function integrated into the microcontroller.
Finally, the CY7C63413C/513C/613C support PS/2 operation.
With appropriate firmware the D+ and D– USB pins can also
be used as PS/2 clock and data signals. Products utilizing
these devices can be used for USB and/or PS/2 operation with
appropriate firmware.
1. CY7C63613C is not bonded out for all GPIO pins shown in Logic Block Diagram. Refer to pin configuration diagram for bonded out pins. See note on page 12
for firmware code needed for unused GPIO pins.
.
Document #: 38-08027 Rev. *BPage 3 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Pin Definitions
CY7C63413CCY7C63513C CY7C63613C
NameI/O
D+, D–I/O1,21,21,21,21,2USB differential data; PS/2 clock and
P0[7:0]I/O15,26,16
25,17,24
18,23
P1[3:0]I/O11,30,12,
P2I/O7,34,8,
P3[7:4]I/O3,38,4,
DACI/On/an/a15,34,16,
XTAL
IN
XTAL
OUT
V
PP
V
CC
Vss20,3924,4724,4724,4712, 23Ground
29,13,28,
14,27
33,9,32,
10,31
37,5,36,
6,35
21252525136-MHz ceramic resonator or external
IN
OUT22262626146-MHz ceramic resonator
1923232311Programming voltage supply, ground
4048484824Voltage supply
17,32,18
31,19,30
20,29
11,38,12,
37,13,36,
14,35
7,42,8,
41,9,40,
10,39
3,46,4,
45,5,44,
6,43
17,32,18,
31,19,30,
20,29
1 1,38,12,
37,13,36,
14,35
7,42,8,
41,9,40,
10,39
3,46,4,
45,5,44,
6,43
33,21,28,
22,27
17,32,18,31,
19,30,20,29
1 1,38,12,37,
13,36,14,35
7,42,8,41,9,
40,10,39
3,46,4,45,5,
44,6,43
15,34,16,33,
21,28,22,27
7, 18, 8, 17, 9,
16, 10, 15
5, 20, 6, 19GPIO Port 1 capable of sinking 7 mA
n/aGPIO Port 2 capable of sinking 7 mA
3, 22, 4, 21GPIO Port 3 capable of sinking 12 mA
n/aDAC I/O Port with programmable
Description40-Pin48-PinDie48-Pin24-Pin
data signals
GPIO port 0 capable of sinking 7 mA
(typical)
(typical).
(typical).
(typical).
current sink outputs. DAC[1:0] offer a
programmable range of 3.2 to 16 mA
typical. DAC[7:2] have a programmable sink current range of 0.2 to 1.0
mA typical. DAC I/O Port not bonded
out on CY7C63613C. See note on
page 12 for firmware code needed for
unused pins.
clock input
during operation
Programming Model
14-bit Program Counter (PC)
The 14-bit Program Counter (PC) allows access for up to 8
kilobytes of EPROM using the CY7C63413C/513C/613C
architecture. The program counter is cleared during reset,
such that the first instruction executed after a reset is at
address 0x0000. This is typically a jump instruction to a reset
handler that initializes the application.
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 incremented by executing an XPAGE
instruction. As a result, the last instruction executed within a
256-byte “page” of sequential code should be an XPAGE
instruction. The assembler directive “XPAGEON” will cause
the assembler to insert XPAGE instructions automatically. As
instructions can be either one or two bytes long, the assembler
may occasionally need to insert a NOP followed by an XPAGE
for correct execution.
The program counter of the next instruction to be executed,
carry flag, and zero flag are saved as two bytes on the program
stack during an interrupt acknowledge or a CALL instruction.
The program counter, carry flag, and zero flag are restored
from the program stack only during a RETI instruction.
Document #: 38-08027 Rev. *BPage 4 of 32
Please note the program counter cannot be accessed directly
by the firmware. The program stack can be examined by
reading SRAM from location 0x00 and up.
8-bit Accumulator (A)
The accumulator is the general purpose, do everything
register in the architecture where results are usually calculated.
8-bit Index Register (X)
The index register “X” is available to the firmware as an
auxiliary accumulator. The X register also allows the processor
to perform indexed operations by loading an index value into
X.
8-bit Program Stack Pointer (PSP)
During a reset, the Program Stack Pointer (PSP) is set to zero.
This means the program “stack” starts at RAM address 0x00
and “grows” upward from there. Note the program stack
pointer is directly addressable under firmware con trol, using
the MOV PSP,A instruction. The PSP supports interrupt
service under hardware control and CALL, RET, and RETI
instructions under firmware control.
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
During an interrupt acknowledge, interrupts are disabled and
the 14-bit program counter, carry flag, and zero flag are written
as two bytes of data memory. The first byte is stored in the
memory addressed by the program stack pointer, then the
PSP is incremented. The second byte is stored in memory
addressed by the program stack pointer and the PSP is incremented again. The net effect is to store the program counter
and flags on the program “stack” and increment the program
stack pointer by two.
The Return From Interrupt (RETI) instruction decrements the
program stack pointer, then restores the second byte from
memory addressed by the PSP. The program stack pointer is
decremented again and the first byte is restored from memory
addressed by the PSP. After the program counter and flags
have been restored from stack, the interrupts are enabled. The
effect is to restore the program counter and flags from the
program stack, decrement the program stack pointer by two,
and re-enable interrupts.
The Call Subroutine (CALL) instruction stores the program
counter and flags on the program stack and increments the
PSP by two.
The Return From Subroutine (RET) instruction restores the
program counter, but not the flags, from program stack and
decrements the PSP by two.
8-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 will pre-decrement the DSP, then write data
to the memory location addressed by the DSP. A POP
instruction will read data from the memory location addressed
by the DSP, then post-incre ment the DSP.
During a reset, the Data Stack Pointer will be set to zero. A
PUSH instruction when DSP equal zero will write data at the
top of the data RAM (address 0xFF). This would write data to
the memory area reserved for a FIFO for USB endpoint 0. In
non-USB applications, this works fine and is not a problem.
For USB applications, it is strongly recommended that the
DSP is loaded after reset just below the USB DMA buffers.
Address Modes
The CY7C63413C/513C/613C microcontrollers support three
addressing modes for instructions that require data operands:
data, direct, and indexed.
Data
The “Data” address mode refers to a data operand that is
actually a constant encoded in the instruction. As an example,
consider the instruction that loads A with the constant 0xE8:
• MOV A,0E8h
This instruction will require 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 ins truction will be the
constant “0xE8”. 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 0E8h
• MOV A,DSPINIT
Direct
“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 encoded in the instruction. As an example,
consider an instruction that loads A with the contents of
memory address location 0x10:
• MOV A, [10h]
In normal usage, variable names are assigned to variable
addresses using “EQU” statements to improve the readability
of the assembler source code. As an example, the following
code is equivalent to the example shown above:
• buttons: EQU 10h
• MOV A,[buttons]
Indexed
“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 constant encoded in the instruction
and the contents of the “X” register. In normal usage, the
constant will be the “base” address of an array of data and the
X register will contain 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.
HALT 007
ADD A,expr data014INC Aacc214
ADD A,[expr] direct026
ADD A,[X+expr] index037INC [expr]direct237
ADC A,exprdata044
ADC A,[expr]direct056
ADC A,[X+expr]index067DEC Xx264
SUB A,exprdata074
SUB A,[expr]direct086
SUB A,[X+expr]index097IORD expraddress295
SBB A,exprdata0A4
SBB A,[expr]direct0B6
SBB A,[X+expr]index0C7
OR A,exprdata0D4
OR A,[expr]direct0E6
OR A,[X+expr]index0F7SWAP A,X2F5
AND A,exprdata104
AND A,[expr]direct116
AND A,[X+expr]index127MOV [X+expr],Aindex326
XOR A,exprdata134
XOR A,[expr]direct146
XOR A,[X+expr]index157AND [expr],Adirect357
CMP A,exprdata165
CMP A,[expr]direct177
CMP A,[X+expr]index188XOR [X+expr] ,Aindex388
MOV A,exprdata194
MOV A,[expr]direct1A5
MOV A,[X+expr]index1B6ASL3B4
MOV X,exprdata1C4
MOV X,[expr]direct1D5
reserved1E
XPAGE1F4
MOV A,X404
MOV X,A414
MOV PSP,A604
CALLaddr50-5F10
JMPaddr80-8F5JCaddrC0-CF5
CALLaddr90-9F10
JZaddrA0-AF5JACCaddrE0-EF7
JNZaddrB0-BF5
NOP204
INC Xx224
INC [X+expr]index248
DEC Aacc254
DEC [expr]direct277
DEC [X+expr]index288
IOWR expraddress2A5
POP A2B4
POP X2C4
PUSH A2D5
PUSH X2E5
SWAP A,DSP305
MOV [expr],Adirect315
OR [expr],Adirect337
OR [X+expr],Aindex348
AND [X+expr],Aindex368
XOR [expr],Adirect377
IOWX [X+expr]index396
CPL3A4
ASR3C4
RLC3D4
RRC 3E4
RET 3F8
DI704
EI724
RETI738
JNCaddrD0-DF5
INDEXaddrF0-FF14
Document #: 38-08027 Rev. *BPage 6 of 32
[+] Feedback
Memory Organization
Program 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
0x000EReserved
CY7C63413C
CY7C63513C
CY7C63613C
0x0010Reserved
0x0012Reserved
0x0014DAC interrupt vector
0x0016GPIO interrupt vector
0x0018Reserved
0x001AProgram Memory begins here
(8K - 32 bytes)
0x1FDF8-KB PROM ends here (CY7C63413C, CY7C63513C, CY7C63613C)
Figure 1. Program Memory Space with Interrupt Vector Table
Document #: 38-08027 Rev. *BPage 7 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Data Memory Organization
The CY7C63413C/513C/613C microcontrollers provide 256
bytes of data RAM. In normal usage, the SRAM is partitioned
after resetAddress
8-bit PSP0x00Program Stack begins here and grows upward
8-bit DSPuserData Stack begins here and grows downward
The user determines the amount of memory required
User Variables
0xE8
USB FIFO for Address A endpoint 2
0xF0
USB FIFO for Address A endpoint 1
0xF8
USB FIFO for Address A endpoint 0
Top of RAM Memory0xFF
into four areas: program stack, data stack, user variables and
USB endpoint FIFOs as shown below:
Document #: 38-08027 Rev. *BPage 8 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
I/O Register Summary
I/O registers are accessed via the I/O Read (IORD) and I/O
Write (IOWR, IOWX) instructions. IORD reads the selected
port into the accumulator. IOWR writes data from the accumu-
Table 1. I/O Register Summary
Register NameI/O AddressRead/WriteFunction
Port 0 Data0x00R/WGPIO Port 0
Port 1 Data0x01R/WGPIO Port 1
Port 2 Data0x02R/WGPIO Port 2
Port 3 Data0x03R/WGPIO Port 3
Port 0 Interrupt Enable0x04WInterrupt enable for pins in Port 0
Port 1 Interrupt Enable0x05WInterrupt enable for pins in Port 1
Port 2 Interrupt Enable0x06WInterrupt enable for pins in Port 2
Port 3 Interrupt Enable0x07WInterrupt enable for pins in Port 3
GPIO Configuration0x08R/WGPIO Ports Configurations
USB Device Address A0x10R/WUSB Device Address A
EP A0 Counter Register0x11R/WUSB Address A, Endpoint 0 counter register
EP A0 Mode Register0x12R/WUSB Address A, Endpoint 0 configuration register
EP A1 Counter Register0x13R/WUSB Address A, Endpoint 1 counter register
EP A1 Mode Register0x14R/CUSB Address A, Endpoint 1 configuration register
EP A2 Counter Register0x15R/WUSB Address A, Endpoint 2 counter register
EP A2 Mode Register0x16R/CUSB Address A, Endpoint 2 configuration register
USB Status & Control0x1FR/WUSB upstream port traffic status and control register
Global Interrupt Enable0x20R/WGlobal interrupt enable register
Endpoint Interrupt Enable0x21R/WUSB endpoint interrupt enables
Timer (LSB)0x24RLower eight bits of free-running timer (1 MHz)
Timer (MSB)0x25RUpper four bits of free-running timer that are latched
WDR Clear0x26WWatch Dog Reset clear
DAC Data0x30R/WDAC I/O
DAC Interrupt Enable0x31WInterrupt enable for each DAC pin
DAC Interrupt Polarity0x32WInte rrupt polari ty for each DAC pin
DAC Isink0x38-0x3FWOne four bit sink current register for each DAC pin
Processor Status & Control0xFFR/WMicroprocessor status and control
Note:
2. DAC I/O Port not bonded out on CY7C63613C. See note on page 12 for firmware code needed for unused GPIO pins.
lator to the selected port. Indexed I/O Write (IOWX) adds the
contents of X to the address in the instruction to form the port
address and writes data from the accumulator to the specified
port. Note that specifying address 0 (e.g., IOWX 0h) means
the I/O port is selected solely by the contents of X.
when the lower eight bits are read.
[2]
Document #: 38-08027 Rev. *BPage 9 of 32
[+] Feedback
Clock Distribution
clk1x
(to USB SIE)
clk2x
(to Microcontroller)
Clock
Doubler
30 pF
Figure 2. Clock Oscillator On-chip Circuit
30 pF
CY7C63413C
CY7C63513C
CY7C63613C
XTALOUT
XTALIN
Clocking
The XTALIN and XTAL
troller. The user can connect a low-cost ceramic resonator or
an external oscillator can be connected to these pins to
provide a reference frequency for the internal clock distribution
and clock doubler.
An external 6-MHz clock can be applied to the XTAL
the XTAL
XTAL
tively shorted to ground.
pin is left open. Please note that grounding the
OUT
pin is not permissible as the internal clock is effec-
OUT
are the clock pins to the microcon-
OUT
IN
pin if
Reset
The USB Controller supports three types of resets. All
registers are restored to their default states during a reset. The
USB Device Addresses are set to 0 and all interrupts are
disabled. In addition, the Program Stack Pointer (PSP) and
Data Stack Pointer (DSP) are set to 0x00. For USB applications, the firmware should set the DSP below 0xE8 to avoid a
memory conflict with RAM dedicated to USB FIFOs. The
assembly instructions to do this are shown below:
Mov A, E8h; Move 0xE8 hex into Accumulator
Swap A,dsp; Swap accumulator value into dsp register
The three reset types are:
1. Power-On Reset (POR)
2. Watch Dog Reset (WDR)
3. USB Bus Reset (non hardware reset)
The occurrence of a reset is recorded in the Processor Status
and Control Register located at I/O address 0xFF. Bits 4, 5,
and 6 are used to record the occurrence of POR, USB Reset,
and WDR respectively. The firmware can interrogate these bits
to determine the cause of a reset.
The microcontroller begins execution from ROM address
0x0000 after a POR or WDR reset. Although this looks like
interrupt vector 0, there is an important difference. Reset
8.192 ms
to 14.336 ms
processing does NOT push the program counter, carry flag,
and zero flag onto program stack. That means the reset
handler in firmware should initialize the hardware and begin
executing the “main” loop of code. Attempting to execute either
a RET or RETI in the reset handler will cause unpredictable
execution results.
Power-On Reset (POR)
Power-On Reset (POR) occurs every time the V
the device ramps from 0V to an internally defined trip voltage
(Vrst) of approximately 1/2 full supply voltage. In addition to the
normal reset initialization noted under “Reset,” bit 4 (PORS) of
the Processor Status and Control Register is set to “1” to
indicate to the firmware that a Power-On Reset occurred. The
POR event forces the GPIO ports into input mode (high
impedance), and the state of Port 3 bit 7 is used to control how
the part will respond after the POR releases.
If Port 3 bit 7 is HIGH (pulled to V
the idle state (DM HIGH and DP LOW) the part will go into a
semi-permanent power down/suspend mode, waiting for the
USB IO to go to one of Bus Reset, K (resume) or SE0. If Port
3 bit 7 is still HIGH when the part comes out of suspend, then
a 128-µs timer starts, delaying CPU operation until the ceramic
resonator has stabilized.
If Port 3 bit 7 was LOW (pulled to V
ms timer, delaying CPU operation until V
then continuing to run as reset.
Firmware should clear the POR Status (PORS) bit in register
0xFF before going into suspend as this status bit selects the
128-µs or 96-ms start-up timer value as follows: IF Port 3 bit 7
is HIGH then 128-µs is always used; ELSE if PORS is HIGH
then 96-ms is used; ELSE 128-µs is used.
Watch Dog Reset (WDR)
The Watch Dog Timer Reset (WDR) occurs when the Most
Significant Bit (MSB) of the 2-bit Watch Dog Timer Register
transitions from LOW to HIGH. In addition to the normal reset
) and the USB IO are at
CC
) the part will start a 96-
SS
CC
voltage to
CC
has stabilized,
2.048 ms
At least 8.192 ms
since last write to WDT
Document #: 38-08027 Rev. *BPage 10 of 32
WDR goes high
for 2.048 ms
Figure 3. Watch Dog Reset (WDR)
Execution begins at
Reset Vector 0X00
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
initialization noted under “Reset,” bit 6 of the Processor Status
and Control Register is set to “1” to indicate to the firmware
that a Watch Dog Reset occurred.
The Watch Dog Timer is a 2-bit timer clocked by a 4.096-ms
clock (bit 11) from the free-running timer. Writing any value to
the write-only Watch Dog Clear I/O port (0x26) will clear the
Wat ch Dog Timer.
In some applications, the Watch Dog Timer may be cleared in
the 1.024-ms timer interrupt service routine. If the 1.024-ms
timer interrupt service routine does not get executed for 8.192
ms or more, a Watch Dog Timer Reset will oc cur . A Watch Dog
Timer Reset lasts for 2.048 ms after which the microcontroller
begins execution at ROM address 0x0000. The USB transmitter is disabled by a Watch Dog Reset because the USB
Device Address Register is cleared. Otherwise, the USB
Controller would respond to all address 0 transactions. The
USB transmitter remains disabled until the MSB of the USB
address register is set.
GPIO
CFG
Internal
Data Bus
Data
Out
Latch
General Purpose I/O Ports
Ports 0 to 2 provide 24 GPIO pins that can be read or written.
Each port (8 bits) can be configured as inputs with internal pullups, open drain outputs, or traditional CMOS outputs. Please
note an open drain output is also a high-impedance (no pullup) input. All of the I/O pins within a given port have the same
configuration. Ports 0 to 2 are considered low current drive
with typical current sink capability of 7 mA.
The internal pull-up resistors are typically 7 kΩ. Two factors
govern the enabling and disabling of the internal pull-up
resistors: the port configuration selected in the GPIO Configuration register and the state of the output data bit. If the GPIO
Configuration selected is “Resistive” and the output data bit is
“1,” then the internal pull-up resistor is e nabled for that GPIO
pin. Otherwise, Q1 is turned off and the 7-kΩ pull-up is
disabled. Q2 is “ON” to sink current whenever the output data
bit is written as a “0.” Q3 provides “HIGH” source current when
the GPIO port is configured for CMOS outputs and the output
data bit is written as a “1”. Q2 and Q3 are sized to sink and
source, respectively, roughly the same amount of current to
support traditional CMOS outputs with symmetric drive.
V
CC
mode
2 bits
Q1
Q3
7 kΩ
Q2
to Interrupt
Controller
ESD
GPIO
Pin
Interrupt
Enable
Port Write
Internal
Buffer
Control
Port Read
Control
Figure 4. Block Diagram of a GPIO Line
.
Table 2. Port 0 Data
Addr: 0x00Port 0 Data
P0[7]P0[6]P0[5]P0[4]P0[3]P0[2]P0[1]P0[0]
R/WR/WR/WR/WR/WR/WR/WR/W
Table 3. Port 1 Data
Addr: 0x01Port 1 Data
P1[7]P1[6]P1[5]P1[4]P1[3]P1[2]P1[1]P1[0]
R/WR/WR/WR/WR/WR/WR/WR/W
Table 4. Port 2 Data
Addr: 0x02Port 2 Data
P2[7]P2[6]P2[5]P2[4]P2[3]P2[2]P2[1]P2[0]
R/WR/WR/WR/WR/WR/WR/WR/W
Document #: 38-08027 Rev. *BPage 11 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Table 5. Port 3 Data
Addr: 0x03Port 3 Data
P3[7]P3[6]P3[5]P3[4]P3[3]P3[2]P3[1]P3[0]
R/WR/WR/WR/WR/WR/WR/WR/W
Table 6. DAC Port Data
Addr: 0x30DAC Port Data
Low current outputs
0.2 mA to 1.0 mA typical
DAC[7]DAC[6]DAC[5]DAC[4]DAC[3]DAC[2]DAC[1]DAC[0]
R/WR/WR/WR/WR/WR/WR/WR/W
High current outputs
3.2 mA to 16 mA typical
Port 3 has eight GPIO pins. Port 3 (8 bits) can be configured
as inputs with internal pull-ups, open drain outputs, or traditional CMOS outputs. An open drain output is also a highimpedance input. Port 3 offers high current drive with a typical
current sink capability of 12 mA. The internal pull-up resistors
are typically 7 kΩ.
Note: Special care should be exercised with any unused GPIO
data bits. An unused GPIO data bit, either a pin on the chip 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 Specification. If a ‘1’ is written to the unused data
bit and the port is configured with open drain outputs, the
unused data bit will be 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 CY7C63613C will always
require that data bits P1[7:4], P2[7:0], P3[3:0] and DAC[7:0] be
written with a ‘0’.
Table 7. Port 0 Interrupt Enable
Addr: 0x04Port 0 Interrupt Enable
P0[7]P0[6]P0[5]P0[4]P0[3]P0[2]P0[1]P0[0]
WWWWWWWW
Table 8. Port 1 Interrupt Enable
Addr: 0x05Port 1 Interrupt Enable
P1[7]P1[6]P1[5]P1[4]P1[3]P1[2]P1[1]P1[0]
WWWWWWWW
During reset, all of the bits in the GPIO to a default configuration of Open Drain output, positive interrupt polarity for all
GPIO ports.
GPIO Interrupt Enable Ports
During a reset, GPIO interrupts are disabled by clearing all of
the GPIO interrupt enable ports. Writing a “1” to a GPIO
Interrupt Enable bit enables GPIO interrupts from the corresponding input pin.
GPIO Configuration Port
Every GPIO port can be programmed as inputs with internal
pull-ups, open drain outputs, and traditional CMOS outputs. In
addition, the interrupt polarity for each port can be programmed. With positive interrupt polarity, a rising edge (“0” to
“1”) on an input pin causes an interrupt. With negative polarity,
a falling edge (“1” to “0”) on an input pin causes an interrupt.
As shown in the table below, when a GPIO port is configured
with CMOS outputs, interrupts from that port are disabled. The
GPIO Configuration Port register provides two bits per port to
program these features. The possible port configurations are
as shown in Table 11.
Table 9. Port 2 Interrupt Enable
Addr: 0x06Port 2 Interrupt Enable
P2[7]P2[6]P2[5]P2[4]P2[3]P2[2]P2[1]P2[0]
WWWWWWWW
Table 10.Port 3 Interrupt Enable
Addr: 0x07Port 3 Interrupt Enable
P3[7]P3[6]P3[5]P3[4]P3[3]P3[2]P3[1]P3[0]
WWWWWWWW
Document #: 38-08027 Rev. *BPage 12 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Table 11.Possible Port Configurations
Port Configuration bitsPin Interrupt BitDriver ModeInterrupt Polarity
In “Resistive” mode, a 7-kΩ pull-up resistor is conditionally
enabled for all pins of a GPIO port. The resistor is enabled for
any pin that has been written as a “1.” The resistor is disabled
on any pin that has been written as a “0.” An I/O pin will be
driven high through a 7-kΩ pull-up resistor when a “1” has
been written to the pin. Or the output pin will be driven LOW,
with the pull-up disabled, when a “0” has been written to the
pin. An I/O pin that has been written as a “1” can be used as
an input pin with an integrated 7-kΩ pull-up resistor. Resistive
mode selects a negative (falling edge) interrupt polarity on all
pins that have the GPIO interrupt enabled.
In “CMOS” mode, all pins of the GPIO port are outputs that are
actively driven. The current source and sink capacity are
roughly the same (symmetric output drive). A CMOS port is not
a possible source for interrupts.
A port configured in CMOS mode has interrupt generation
direction. If a port’s associated Interrupt Mask bits are cleared,
those port bits are strictly outputs. If the Interrupt Mask bits are
set then those bits will be open drain inputs. As open drain
inputs, if their data output values are ‘1’ those port pins will be
CMOS inputs (HIGH Z output).
In “Open Drain” mode the internal pull-up resistor and CMOS
driver (HIGH) are both disabled. An I/O pin that has been
written as a “1” can be used as either a high-impedance input
or a three-state output. An I/O pin that has been written as a
“0” will drive the output LOW. The interrupt polarity for an open
drain GPIO port can be selected as either positive (rising
edge) or negative (falling edge).
During reset, all of the bits in the GPIO Configuration Register
are written with “0.” This selects the default configuration:
Open Drain output, positive interrupt polarity for all GPIO
ports.
disabled, yet the interrupt mask bits serve to control port
Addr: 0x08GPIO Configuration Register
76543210
Port 3
Config Bit 1
Port 3
Config Bit 0
Port 2
Config Bit 1
Port 2
Config Bit 0
Port 1
Config Bit 1
Port 1
Config Bit 0
Port 0
Config Bit 1
WWWWWWWW
Table 12.GPIO Configuration Register
DAC Port
Port 0
Config Bit 0
V
CC
Internal
Data Bus
Interrupt
Enable
Interrupt
Polarity
DAC Write
Internal
Buffer
Data
Out
Latch
DAC Read
Isink
Register
Interrupt Logic
4 bits
Isink
DAC
to Interrupt
Controller
Q1
14 KΩ
DAC
I/O Pin
ESD
Figure 5. Block Diagram of DAC Port
Document #: 38-08027 Rev. *BPage 13 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Table 13.DAC Port Data
Addr: 0x30DAC Port Data
Low current outputs
0.2 mA to 1.0 mA typical
DAC[7]DAC[6]DAC[5]DAC[4]DAC[3]DAC[2]DAC[1]DAC[0]
R/WR/WR/WR/WR/WR/WR/WR/W
The DAC port provides the CY7C63513C with 8 programmable current sink I/O pins. Writing a “1” to a DAC I/O pin
disables the output current sink (Isink DAC) and drives the I/O
pin HIGH through an integrated 14 Kohm resistor. When a “0”
is written to a DAC I/O pin, the Isink DAC is enabled and the
pull-up resistor is disabled. A “0” output will cause the Isink
DAC to sink current to drive the output LOW. The amount of
sink current for the DAC I/O pin is programmable over 16
values based on the content s of the DAC Isink Register f or that
output pin. DAC[1:0] are the two high current outputs that are
programmable from a minimum of 3.2 mA to a maximum of 16
mA (typical). DAC[7:2] are low current outputs that are
programmable from a minimum of 0.2 mA to a maximum of 1.0
mA (typical).
When a DAC I/O bit is written as a “1,” the I/O pin is either an
output pulled high through the 14 Kohm resistor or an input
with an internal 14 Kohm pull-up resistor. All DAC port data bits
are set to “1” during reset.
DAC Port Interrupts
A DAC port interrupt can be enabled/disabled for each pin
individually. The DAC Port Interrupt Enable register provides
this feature with an interrupt mask bit for each DAC I/O pin.
Writing a “1” to a bit in this register enables interrupts from the
corresponding bit position. Writing a “0” to a bit in the DAC Port
Interrupt Enable register disables interrupts from the corresponding bit position. All of the DAC Port Interrupt Enable
register bits are cleared to “0” during a reset.
As an additional benefit, the interrupt polarity for each DAC pin
is programmable with the DAC Port Interrupt Polarity register.
Writing a “0” to a bit selects negative polarity (falling edge) that
will cause an interrupt (if enabled) if a falling edge tra nsition
occurs on the corresponding input pin. Writing a “1” to a bit in
this register selects positive polarity (rising edge) that will
cause an interrupt (if enabled) if a rising edge transition occurs
on the corresponding input pin. All of the DAC Port Interrupt
Polarity register bits are cleared during a reset.
DAC Isink Registers
Each DAC I/O pin has an associated DAC Isink register to
program the output sink current when the output is driven
LOW. The first Isink register (0x38) controls the current for
DAC[0], the second (0x39) for DAC[1], and so on until the Isink
register at 0x3F controls the current to DAC[7].
High current outputs
3.2 mA to 16 mA typical
Table 14.DAC Port Interrupt Enable
Addr: 0x31DAC Port Interrupt Enable
DAC[7]DAC[6]DAC[5]DAC[4]DAC[3]DAC[2]DAC[1]DAC[0]
WWWWWWWW
Table 15.DAC Port Interrupt Polarity
Addr: 0x32DAC Port Interrupt Polarity
DAC[7]DAC[6]DAC[5]DAC[4]DAC[3]DAC[2]DAC[1]DAC[0]
WWWWWWWW
Table 16.DAC Port Isink
Addr: 0x38-0x3FDAC Port Interrupt Polarity
ReservedIsink Value
Isink[3]Isink[2]Isink[1]Isink[0]
WWWW
Document #: 38-08027 Rev. *BPage 14 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
USB Serial Interface Engine (SIE)
The SIE allows the microcontroller to communicate with the
USB host. The SIE simplifies the interface between the microcontroller and USB by incorporating hardware that handles the
following USB bus activity independently of the microcontroller:
• Bit stuffing/unstuffing
• Checksum generation/checking
•ACK/NAK
• Token type identification
• Address checking
Firmware is required to handle the rest of the USB interface
with the following tasks:
• Coordinate enumeration by responding to set-up packets
• Fill and empty the FIFOs
• Suspend/Resume coordination
• Verify and select Data toggle values
USB Enumeration
The enumeration sequence is shown below:
1. The host computer sends a Setup packet followed by a
Data packet to USB address 0 requesting the Device descriptor.
2. The USB Controller decodes the request and retrieves its
Device descriptor from the program memory space.
3. The host computer performs a control read sequence and
the USB Controller responds by sending the Device
descriptor over the USB bus.
4. After receiving the descriptor, the host computer sends a
Setup packet followed by a Data packet to address 0
assigning a new USB address to the device.
5. The USB Controller stores the new address in its USB
Device Address Register after the no-data control
sequence is complete.
6. The host sends a request for the Device descriptor using
the new USB address.
Table 17.USB Status and Control Register
Addr:0x1FUSB Status and Control Register
76543210
ReservedReservedD+D–Bus ActivityControl
RRR/WR/WR/WR/W
7. The USB Controller decodes the request and retrieves the
Device descriptor from the program memory .
8. The host performs a control read sequence and the USB
Controller responds by sending its Device descriptor over
the USB bus.
9. The host generates control reads to the USB Controller to
request the Configuration and Report descriptors.
10.The USB Controller retrieves the descriptors from its
program space and returns the data to the host over the
USB.
PS/2 Operation
PS/2 operation is possible with the CY7C63413C/513C/613C
series through the use of firmware and several operating
modes. The first enabling feature:
1. USB Bus reset on D+ and D− is an interrupt that can be
disabled;
2. USB traffic can be disabled via bit 7 of the USB register;
3. D+ and D− can be monitored and driven via firmware as
independent port bits.
Bits 5 and 4 of the Upstream Status and Control register are
directly connected to the D+ and D− USB pins of the
CY7C63413C/513C/613C. These pins constantly monitor the
levels of these signals with CMOS input thresholds. Firmware
can poll and decode these signals as PS/2 clock and data.
Bits [2:0] defaults to ‘000’ at reset which allows the USB SIE
to control output on D+ and D−. Firmware can override the SIE
and directly control the state of these pins via these 3 control
bits. Since PS/2 is an open drain signaling protocol, these
modes allow all 4 PS/2 states to be generated on the D+ and
D− pins
USB Port Status and Control
USB status and control is regulated by the USB Status and
Control Register located at I/O address 0x1F as shown in
Figure 17. This is a read/write register. All reserved bits must
be written to zero. All bits in the register are cleared during
reset.
Control
Bit 2
Bit 1
Control
Bit 0
Document #: 38-08027 Rev. *BPage 15 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
The Bus Activity bit is a “sticky” bit that indicates if any non-idle
USB event has occurred on the USB bus. The user firmware
should check and clear this bit periodically to detect any loss
of bus activity . Writing a “ 0” to the Bus Activity bit clears it while
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. The 1.024-ms timer interrupt service routine is normally
used to check and clear the Bus Activity bit. The following table
shows how the control bits are encoded for this register.
USB Device Address A includes three endpoints: EPA0, EP A1,
and EPA2. End Point 0 (EPA0) allows the USB host to
recognize, set up, and control the device. In particular, EPA0
is used to receive and transmit control (including set-up)
packets.
USB Ports
The USB Controller provides one USB device address with
three endpoints. The USB Device Address Register contents
are cleared during a reset, setting the USB device address to
zero and marking this address as disabled. Figure 18 shows
the format of the USB Address Register.
Bit 7 (Device Address Enable) in the USB Device Address
Register must be set by firmware before the serial interface
engine (SIE) will respond to USB traffic to this address. The
Device Address in bits [6:0] must be set by firmware during the
USB enumeration process to an address assigned by the USB
host that does not equal zero. This register is cleare d by a
hardware reset or the USB bus reset.
Device Endpoints (3)
The USB controller communicates with the host using
dedicated FIFOs, one per endpoint. Each endpoint FIFO is
implemented as 8 bytes of dedicated SRAM. There are three
endpoints defined for Device “A” that are labeled “EPA0,”
“EPA1,” and EPA2.”
All USB devices are required to have an endpoint number 0
(EPA0) that is used to initialize and control the USB device.
End Point 0 provides access to the device configuration information and allows generic USB status and control accesses.
End Point 0 is bidirectional as the USB controller can both
receive and transmit data.
The endpoint mode registers are cleared during reset. The
EPA0 endpoint mode register uses the format shown in T able
19.
Bits[7:5] in the endpoint 0 mode registers (EPA0) are “sticky”
status bits that are set by the SIE to report the type of token
that was most recently received. The sticky bits must be
cleared by firmware as part of the USB processing.
The endpoint mode registers for EPA1 and EPA2 do not use
bits [7:5] as shown in Table 20.
Table 18.USB Device Address Register
Addr:0x10USB Device Address Register
Device
Address
Enable
R/WR/WR/WR/WR/WR/WR/WR/W
Table 19.USB Device EPA0, Mode Register
Addr:0x12USB Device EPA0, Mode Register
Endpoint 0
Set-up
Received
R/WR/WR/WR/WR/WR/WR/WR/W
Table 20.USB Device Endpoint Mode Register
Addr: 0x14, 0x16USB Device Endpoint Mode Register
ReservedReservedReservedAcknowledgeMode
R/WR/WR/WR/WR/WR/WR/WR/W
Device
Address
Bit 6
Endpoint 0
In
Received
Device
Address
Bit 5
Endpoint 0
Out
Received
Device
Address
Bit 4
AcknowledgeMode
Device
Address
Bit 3
Bit 3
Bit 3
Device
Address
Bit 2
Mode
Bit 2
Mode
Bit 2
Device
Address
Bit 1
Mode
Bit 1
Mode
Bit 1
Device
Address
Bit 0
Mode
Bit 0
Mode
Bit 0
Document #: 38-08027 Rev. *BPage 16 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
The ‘Acknowledge’ bit is set whenever the SIE engages in a
transaction that completes with an ‘ACK’ packet.
The ‘set-up’ PID status (bit[7]) is forced HIGH from the start of
the data packet phase of the set-up transaction, until the start
of the ACK packet returned by the SIE. The CPU is prevented
from clearing this bit during this interval, and subsequently
until the CPU first does an IORD to this endpoint 0 mode
register.
Bits[6:0] of the endpoint 0 mode register are locked from CPU
IOWR operations only if the SIE has updated one of these bits,
which the SIE does only at the end of a packet transaction (setup... Data... ACK, or Out... Data... ACK, or In... Data... ACK).
The CPU can unlock these bits by doing a subsequent I/O read
of this register.
Firmware must do an IORD after an IOWR to an endpoint 0
register to verify that the contents have changed and that the
SIE has not updated these values.
While the ‘set-up’ bit is set, the CPU cannot write to the DMA
buffers at memory locations 0xE0 through 0xE7 and 0xF8
through 0xFF. This prevents an incoming set-up transaction
from conflicting with a previous In data buffer filling operation
by firmware.
The mode bits (bits [3:0]) in an Endpoint Mode Register control
how the endpoint responds to USB bus traffic. The mode bit
encoding is shown in Section .
The format of the endpoint Device counter registers is shown
in Table 21.
Bits 0 to 3 indicate the number of data bytes to be transmitted
during an IN packet, valid values are 0 to 8 inclusive. Data
Valid bit 6 is used for OUT and set-up tokens only. Data 0/1
Toggle bit 7 selects the DATA packet’s toggle state: 0 for
DATA0, 1 for DATA1.
Bit 3
Byte count
Bit 2
Byte count
Bit 1
Byte count
Bit 0
Document #: 38-08027 Rev. *BPage 17 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
12-bit Free-running Timer
The 12-bit timer provides two interrupts (128 µs and 1.024 ms)
and allows the firmware to directly time events that are up to
4 ms in duration. The lower 8 bits of the timer can be read
directly by the firmware. Reading the lower 8 bits latches the
Timer (LSB)
Table 22.Timer Register
Addr: 0x24Timer Register (LSB)
Timer
Bit 7
RRRRRRRR
Timer (MSB)
Table 23.Timer Register
Addr: 0x25Timer Register (MSB)
ReservedReservedReservedReservedTimer
Timer
Bit 6
Timer
Bit 5
Timer
Bit 4
upper 4 bits into a temporary register. When the firmware
reads the upper 4 bits of the timer, it is actually reading the
count stored in the temporary register. The effect of this logic
is to ensure a stable 12-bit timer value can be read, even when
the two reads are separated in time.
Timer
Bit 3
Bit 11
RRRR
Timer
Bit 2
Timer
Bit 10
Timer
Bit 1
Timer
Bit 9
1.024-ms interrupt
128-
µs interrupt
Timer
Bit 0
Timer
Bit 8
10978
L1L0L2L3
D3D2D1D0D7D6D5D4D3D2D1D0
6432
5
1011
1-MHz clock
To Timer Register
8
Figure 6. Timer Block Diagram
Processor Status and Control Register
Table 24.Processor St atus and Control Register
Addr: 0xFFProcessor Status and Control RegisterPOR Default: 0x0101
76543210
IRQ
Pending
RR/WR/WR/WR/WRR/WR/W
The “Run” (bit 0) is manipulated by the HALT instruction. When
Halt is executed, the processor clears the run bit and halts at
the end of the current instruction. The processor remains
Watch Dog
Reset
USB Bus
Reset
Power-on
Reset
Suspend, Wait
for Interrupt
halted until a reset (Power On or Watch Dog). Notice, when
writing to the processor status and control register, the run bit
should always be written as a “1.”
Interrupt
Mask
WDC Reset: 0x41
Single StepRun
Document #: 38-08027 Rev. *BPage 18 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
The “Single Step” (bit 1) is provided to support a hardware
debugger. When single step is set, the processor will execute
one instruction and halt (clear the run bit). This bit must be
cleared for normal operation.
The “Interrupt Mask” (bit 2) shows whether interrupts are
enabled or disabled. The firmware has no direct control over
this bit as writing a zero or one to this bit position will have no
effect on interrupts. Instructions DI, EI, and RETI manipulate
the internal hardware that controls the state of the interrupt
mask bit in the Processor Status and Control Register.
Writing a “1” to “Suspend, Wait for Interrupts” (bit 3) will halt
the processor and cause the microcontroller to enter the
“suspend” mode that significantly reduces power
consumption. A pending interrupt or bus activity will cause the
device to come out of suspend. After coming out of suspend,
the device will resume firmware execution at the instruction
following the IOWR which put the part into suspend. An IOWR
that attempts to put the part into suspend will be ignored if
either bus activity or an interrupt is pending.
The “Power-on Reset” (bit 4) is only set to “1” during a powe r
on reset. The firmware can check bits 4 and 6 in the reset
handler to determine whether a reset was caused by a Power
On condition or a Watch Dog Timeout. PORS is used to
determine suspend start-up timer value of 128 µs or 96 ms.
The “USB Bus Reset” (bit 5) will occur when a USB bus reset
is received. The USB Bus Reset is a singled-ended zero (SE0)
that lasts more than 8 microseconds. An SE0 is defined as the
condition in which both the D+ line and the D– line are LOW
at the same time. When the SIE detects this condition, the
USB Bus Reset bit is set in the Processor Status and Control
register and an USB Bus Reset interrupt is generated. Please
note this is an interrupt to the microcontroller and does n ot
actually reset the processor.
The “Watch Dog Reset” (bit 6) is set during a reset initiated by
the Watch Dog Timer. This indicates the Watch Dog Timer
went for more than 8 ms between watch dog clears.
The “IRQ Pending” (bit 7) indicates one or more of the interrupts has been recognized as active. The interrupt
acknowledge sequence should clear this bit until the next
interrupt is detected.
During Power-on Reset, the Processor Status and Control
Register is set to 00010001, which indicates a Power-on Reset
(bit 4 set) has occurred and no interrupts are pending (bit 7
clear) yet.
During a Watch Dog Reset, the Processor St atus and Control
Register is set to 01000001, which indicates a Watch Dog
Reset (bit 6 set) has occurred and no interrupts are pending
(bit 7 clear) yet.
Interrupts
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. During a reset, the contents the Global
Interrupt Enable Register and USB End Point Interrupt Enable
Register are cleared, effectively disabling all interrupts.
Pending interrupt requests are recognized during the last clock
cycle of the current instruction. When servicing an interrupt,
the hardware will first disable all interrupts by clearing the
Interrupt Enable bit in the Processor Status and Control
Register. Next, the interrupt latch of the current interrupt is
cleared. This is followed by a CALL instruction to the ROM
address associated with the interrupt being serviced (i.e., the
Interrupt Vector). The instruction in the interrupt table is
typically a JMP instruction to the address of the Interrupt
Service Routine (ISR). The user can re-enable 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 automatically stored onto the Program Stack
by the CALL instruction as part of the interrupt acknowledge
process. The user firmware is responsible for insuring that the
processor state is preserved and restored during an interrupt.
The PUSH A instruction should be used as the first command
in the ISR to save the accumulator value and the POP A
instruction should be used just before the RETI instruction to
restore the accumulator value. The program counter CF and
ZF are restored and interrupts are enabled when the R ETI
instruction is executed.
Table 25.Global Interrupt Enable Register
Addr: 0x20Global Interrupt Enable Register
76543210
ReservedReservedGPIO
Interrupt
Enable
R/WR/WR/WR/WR/W
Table 26.USB End Point Interrupt Enable Register
Addr: 0x21USB End Point Interrupt Enable Register
76543210
ReservedReservedReservedReservedReservedEPA2
Document #: 38-08027 Rev. *BPage 19 of 32
DAC
Interrupt
Enable
Reserved1.024-ms
Interrupt
Enable
Interrupt
Enable
R/WR/WR/W
128-µsec
Interrupt
Enable
EPA1
Interrupt
Enable
USB Bus RST
Interrupt
Enable
EPA0
Interrupt
Enable
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Interrupt Vectors
The Interrupt Vectors supported by the USB Controller are
listed in Table 27. Although Reset is not an interrupt, per se,
the first instruction executed after a reset is at PROM address
Table 27.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
70x000EReserved
80x0010Reserved
Interrupt latency can be calculated from the following
equation:
Interrupt Latency =(Number of clock cycles remaining in the
current instruction)
+ (10 clock cycles for the CALL instruction)
+ (5 clock cycles for the JMP 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 will execute a min. of 16 clocks
(1+10+5) or a max. of 20 clocks (5+10+5) after the interrupt is
issued. Remember that the interrupt latches are sampled at
the rising edge of the last clock cycle in the current instruction.
USB Bus Reset Interrupt
The USB Bus Reset interrupt is asserted when a USB bus
reset condition is detected. A USB bus reset is indicated by a
single ended zero (SE0) on the upstream port for more than 8
microseconds.
Timer Interrupt
There are two timer interrupts: the 128-µs interrupt and the
1.024-ms interrupt. The user should disable both timer interrupts before going into the suspend mode to avoid possible
conflicts between servicing the interrupts first or the suspend
request first.
USB Endpoint Interrupts
There are three USB endpoint interrupts, one per endpoint.
The USB endpoints interrupt after the either the USB host or
the USB controller sends a packet to the USB.
0x0000—which corresponds to the first entry in the Interrupt
Vector Table. Because the JMP instruction is 2 bytes long, the
interrupt vectors occupy 2 bytes.
DAC Interrupt
Each DAC I/O pin can generate an interrupt, if enabled.The
interrupt polarity for each DAC I/O pin is programmable. A
positive polarity is a rising edge input while a negative polarity
is a falling edge input. All of the DAC pins share a single
interrupt vector, which means the firmware will need to read
the DAC port to determine which pin or pins caused an
interrupt.
Please note that if one DAC pin triggered an interrupt, no other
DAC pins can cause a DAC interrupt until that pin has returned
to its inactive (non-trigger) state or the corresponding interrupt
enable bit is cleared. The USB Controller does not assign
interrupt priority to different DAC pins and the DAC Interrupt
Enable Register is not cleared during the interrupt
acknowledge process.
GPIO Interrupt
Each of the 32 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 will need
to read the GPIO ports with enabled interrupts to determine
which pin or pins caused an interrupt.
Please note that if one port pin triggered an interrupt, no other
port pins can cause a GPIO interrupt until that port pin has
returned to its 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.
Document #: 38-08027 Rev. *BPage 20 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Truth Tables
Table 28.USB Register Mode Encoding
ModeEncodingSetupInOutComments
Disable0000ignoreignoreignoreIgnore all USB traffic to this endpoint
Nak In/Out
0001
Status Out Only0010acceptstallcheckFor Control endpoints
Stall In/Out 0011acceptstallstallFor Control endpoints
Ignore In/Out 0100acceptignoreignoreFor Control endpoints
Isochronous Out
0101
Status In Only0110acceptTX 0 stallFor Control Endpoints
Isochronous In
0111
Nak Out1000ignoreignoreNAKAn ACK from mode 1001 --> 1000
Ack Out1001ignoreignoreACKThis mode is changed by SIE on issuance of ACK --> 1000
Nak Out - Status In1010acceptTX 0NAKAn ACK from mode 1011 --> 1010
Ack Out - Status In1011acceptTX 0ACKThis mode is changed by SIE on issuance of ACK --> 1010
Nak In1100ignoreNAKignoreAn ACK from mode 1101 --> 1100
Ack In1101ignoreTX cntignoreThis mode is changed by SIE on issuance of ACK --> 1100
Nak In - Status Out1110acceptNAKcheckAn ACK from mode 1111 --> 1110 NAck In - Status Out
Ack In - Stat us Out1111acceptTX cntCheckThis mode is changed by SIE on issuance of ACK -->1110
acceptNAKNAKForced from Set-up on Control endpoint, from modes other
than 0000
ignoreignorealwaysAvailable to low speed devices, future USB spec
enhancements
ignoreTX cntignoreAvailable to low speed devices, future USB spec
enhancements
The ‘In’ column represents the SIE’s response to the token
type.
A disabled endpoint will remain such until firmware changes it,
and all endpoints reset to disabled.
Any Setup packet to an enabled and accepting endpoint will
be changed by the SIE to 0001 (NAKing). Any mode which
indicates the acceptance of a Setup will acknowledge it.
Most modes that control transactions involving an ending ACK
will be changed by the SIE to a corresponding mode which
NAKs follow on packets.
A Control endpoint has three extra status bits for PID (Setup,
In and Out), but must be placed in the correct mode to function
as such. Also a non-Control endpoint can be made to act as a
Control endpoint if it is placed in a non appropriate mode.
A ‘check’ on an Out token during a Status transaction checks
to see that the Out is of zero length and has a Data Toggle
(DTOG) of 1.
Document #: 38-08027 Rev. *BPage 21 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Figure 7. Decode table forTable 29: “Details of Modes for Differing Traffic Conditions”
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 IRQ when a valid transaction is
completed or when the DMA buffer is corrupted
3. an incoming Data packet is valid if the count is <= 10 (CRC
inclusive) and passes all error checking;
4. a Setup will be ignored by all non-Control endpoints (in
appropriate modes);
5. an In will be ignored by an Out configured endpoint and vice
versa.
The In and Out PID status is updated at the end of a tran saction.
TX0: transmit 0-length packet
The Setup PID status is updated at the beginning of the Data
packet phase.
The entire EndPoint 0 mode and the Count register are locked
to CPU writes at the end of any transaction in which an ACK
is transferred. These registers are only unlocked upon a CPU
read of these registers, and only if that read happens after the
transaction completes. This represents about a 1-µs window
to which to the CPU is locked from register writes to these USB
registers. Normally the firmware does a register read at the
beginning of the ISR to unlock and get the mode register information. The interlock on the Mode and Count registers
ensures that the firmware recognizes the changes that the SIE
might have made during the previous transaction.
Document #: 38-08027 Rev. *BPage 22 of 32
[+] Feedback
CY7C63413C
CY7C63513C
CY7C63613C
Table 29.Details of Modes for Differing Traffic Conditions
End Point ModePIDSet End Point Mode
3 2 1 0 tokencount bufferdvalDTOGDVALCOUNT Setup InOutACK3210response int
Setup Packet (if accepting)
See Table 28 Setup<= 10datavalidupdates1updates1UCUC10001ACKyes
See Table 28 Setup> 10junkxupdates updates updates1UCUCUCNoChangeignoreyes
See Table 28 Setupxjunkinvalidupdates0updates1UCUCUCNoChangeignoreyes
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
Max. Output Current into Port 0,1,2,3 and DAC[1:0] Pins................................................................................................... 60 mA
Max. Output Current into DAC[7:2] Pins............................................... .................................. .. .......................................... 10 mA
Power Dissipation...................... ............................................................................................. ................................. ... ... ...300 mW
Latch-up Current ........................................................................................................................................................... > 200 mA
DC Characteristics Fosc = 6 MHz; Operating Temperature = 0 to 70°C
General
V
CC (1)
V
CC (2)
I
CC1
I
CC2
I
SB1
V
PP
T
start
t
int1
t
int2
t
watch
I
il
I
sm
Power-On Reset
t
vccs
USB Interface
V
oh
V
ol
V
di
V
cm
V
se
C
in
I
lo
R
pu
R
pu
R
pd
General Purpose I/O Interface
R
up
V
ith
Notes:
3. Qualified with JEDEC EIA/JESD22-A114-B test method.
4. Functionality is guaranteed of the V
5. USB transmitter functionality is guaranteed over the V
6. Total current cumulative across all Port pins flowing to V
7. Port 3 bit 7 controls whether the parts goes into suspend after a POR event or waits 128 ms to begin running.
8. POR will re-occur whenever V
Operating Voltage4.05.5VNon USB activity (note 4)
Operating Voltage4.355.25VUSB activity (note 5)
VCC Operating Supply Current40mAV
VCC = 4.35V15mA
Supply Current - Suspend Mode30µAOscillator off, D– > Voh min
Programming Voltage (disabled)–0.40.4V
Resonator Start-up Interval256µsVCC = 5.0V, ceramic resonator
Internal Timer #1 Interrupt Period128128µs
Internal Timer #2 Interrupt Period1.0241.024ms
Watch Dog Timer Period8.19214.33ms
Input Leakage Current1µAAny pin
Max ISS IO Sink Current60mACumulative across all ports (note 6)
VCC Reset Slew0.001200msLinear ramp: 0 to 4.35V (notes 7,8)
Static Output HIGH2.83.6V15k ± 5% ohms to Gnd (note 5)
Static Output LOW0.3V
Differential Input Sensitivity 0.2V|(D+)–(D–)|
Differential Input Common Mode Range0.82.5V9-1
Single-Ended Receiver Threshold0.82.0V
Transceiver Capacitance20pF
Hi-Z State Data Line Leakage–1010µA0 V < Vin<3.3 V
Bus Pull-up Resistance (VCC option)7.35K7.65 kΩ7.5 kΩ ± 2% to VCC
Bus Pull-up Resistance (Ext. 3.3V option)1.4251.575kΩ1.5 kΩ ± 5% to 3.0–3.6V
Bus Pull-down Resistance14.2515.75 kΩ15 kΩ ± 5%