CY7C64013 CYPRESS [Cypress Semiconductor], CY7C64013 Datasheet - Page 29

no-image

CY7C64013

Manufacturer Part Number
CY7C64013
Description
Full-Speed USB (12 Mbps) Function
Manufacturer
CYPRESS [Cypress Semiconductor]
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
CY7C64013-PC
Manufacturer:
CY
Quantity:
101
Part Number:
CY7C64013-PC
Manufacturer:
CY
Quantity:
116
Part Number:
CY7C64013-PXC
Quantity:
17
Part Number:
CY7C64013-SC
Manufacturer:
CY
Quantity:
15 625
Part Number:
CY7C64013A-PXC
Manufacturer:
CY
Quantity:
548
Part Number:
CY7C64013C-SXC
Manufacturer:
CYPRESS/赛普拉斯
Quantity:
20 000
16.4
There are two periodic 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 timer interrupts first or the suspend
request first.
16.5
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 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.
16.6
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.
16.7
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 Figure 16-5. 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 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.
When HAPI is enabled, the HAPI logic takes over the interrupt vector and blocks any interrupt from the GPIO bits, including
ports/bits not being used by HAPI. Operation of the HAPI interrupt is independent of the GPIO specific bit interrupt enables, and
is enabled or disabled only by bit 5 of the Global Interrupt Enable Register (0x20) when HAPI is enabled. The settings of the
GPIO bit interrupt enables on ports/bits not used by HAPI still effect the CMOS mode operation of those ports/bits. The effect of
Document #: 38-08001 Rev. **
GPIO
Pin
IRA
1 = Enable
0 = Disable
Timer Interrupt
USB Endpoint Interrupts
DAC Interrupt
GPIO/HAPI Interrupt
Port Interrupt
Enable Register
Configuration
Register
M
U
X
Port
Figure 16-5. GPIO Interrupt Structure
1 = Enable
0 = Disable
(1 input per
OR Gate
GPIO pin)
(Bit 5, Register 0x20)
GPIO Interrupt
Global
Enable
1
GPIO Interrupt
Flip Flop
D
CLR
Q
Interrupt
Encoder
Priority
CY7C64013
CY7C64113
Page 29 of 48
Interrupt
IRQout
Vector

Related parts for CY7C64013