CY7C64113C-PVXC Cypress Semiconductor Corp, CY7C64113C-PVXC Datasheet - Page 29

no-image

CY7C64113C-PVXC

Manufacturer Part Number
CY7C64113C-PVXC
Description
IC MCU 8K FULL SPEED USB 48-SSOP
Manufacturer
Cypress Semiconductor Corp
Series
M8™r
Datasheet

Specifications of CY7C64113C-PVXC

Applications
USB Microcontroller
Core Processor
M8C
Program Memory Type
OTP (8 kB)
Controller Series
CY7C641xx
Ram Size
256 x 8
Interface
I²C, USB, HAPI
Number Of I /o
36
Voltage - Supply
4 V ~ 5.25 V
Operating Temperature
0°C ~ 70°C
Mounting Type
Surface Mount
Package / Case
48-SSOP
For Use With
428-1339 - KIT LOW SPEED PERSONALITY BOARD
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Table 30. Interrupt Vector Assignments
Interrupt Latency
Interrupt latency can be calculated from the following equation:
Interrupt latency =
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.
USB Bus Reset Interrupt
The USB Controller recognizes a USB Reset when a Single
Ended Zero (SE0) condition persists on the upstream USB port
for 12–16 µs (the Reset may be recognized for an SE0 as short
as 12 µs, but is always recognized for an SE0 longer than 16 µs).
SE0 is defined as the condition in which both the D+ line and the
D– line are LOW. Bit 5 of the Status and Control Register is set
to record this event. The interrupt is asserted at the end of the
Bus Reset. If the USB reset occurs during the start-up delay
following a POR, the delay is aborted as described in
Reset (POR) on page
generated when the SE0 state is deasserted.
A USB Bus Reset clears the following registers:
Timer Interrupt
There are two periodic timer interrupts: the 128- µs interrupt and
the 1.024-ms interrupt. The user should disable both timer inter-
rupts before going into the suspend mode to avoid possible
conflicts between servicing the timer interrupts first or the
suspend request first.
USB Endpoint Interrupts
There are five USB endpoint interrupts, one per endpoint. A USB
endpoint interrupt is generated after the USB host writes to a
Document Number: 38-08001 Rev. *D
SIE Section:USB Device Address Registers (0x10, 0x40)
Interrupt Vector Number
Not Applicable
10
12
11
1
2
3
4
5
6
7
8
9
(Number of clock cycles remaining in the
(5 clock cycles for the JMP instruction)
14. The USB Bus Reset Interrupt is
ROM Address
0x000C
0x0000
0x000A
0x000E
0x0002
0x0004
0x0006
0x0008
0x0010
0x0012
0x0014
0x0016
0x0018
Power-On
USB endpoint FIFO or after the USB controller sends a packet
to the USB host. The interrupt is generated on the last packet of
the transaction (e.g., on the host’s ACK during an IN, or on the
device ACK during on OUT). If no ACK is received during an IN
transaction, no interrupt is generated.
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 needs to read the DAC port to
determine which pin or pins caused an interrupt.
If one DAC pin has 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/HAPI 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 the
GPIO ports with enabled interrupts to determine which pin or pins
caused an interrupt. A block diagram of the GPIO interrupt logic
is shown in
Port on page 16
more information of setting GPIO interrupt polarity and enabling
individual GPIO interrupts.
If one port pin has 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.
Figure 8 on page
USB Address A Endpoint 0 interrupt
USB Address A Endpoint 1 interrupt
USB Address A Endpoint 2 interrupt
USB Address A Endpoint 3 interrupt
USB Address A Endpoint 4 interrupt
Execution after Reset begins here
and
USB Bus Reset interrupt
1.024-ms timer interrupt
128- µs timer interrupt
GPIO Interrupt Enable Ports on page 17
GPIO interrupt
DAC interrupt
I
2
Function
Reserved
C interrupt
30. Refer to
CY7C64013C
CY7C64113C
GPIO Configuration
Page 29 of 53
for
[+] Feedback

Related parts for CY7C64113C-PVXC