6. Functional Description
S1R72V17*** Technical Manual (Rev.1.6)
EPSON
15
Table 6.6 lists the basic setup items for an alarm endpoint. Although this alarm endpoint currently is
not assigned to any general-purpose endpoints, it is provided to allow implementation of an endpoint
defined in the USB-defined interface. Set up these items appropriately according to the definitions
specified under the USB standard interface. Also, enable the settings made to configure a USB-defined
interface.
This alarm endpoint does not require a FIFO area.
Table 6.6 Basic Setup Items for an Alarm Endpoint
Item
Register/Bit
Description
Alarm endpoint
enable
D_EnEP_IN_H.EnEPn{n=8-15}IN,
D_EnEP_IN_L.EnEPn{n=1-7}IN,
D_EnEP_OUT_H.EnEPn{n=8-15}OUT,
D_EnEP_OUT_L.EnEPn{n=1-7}OUT
Enables an alarm endpoint
Isochronous mode
D_EnEP_IN_ISO_H.EnEPn{n=8-15}IN_ISO,
D_EnEP_IN_ISO_L.EnEPn{n=1-7}IN_ISO,
D_EnEP_OUT_ISO_H.EnEPn{n=8-15}OUT_ISO,
D_EnEP_OUT_ISO_L.EnEPn{n=1-7}OUT_ISO
To place the endpoint in Isochronous
transfer mode, set this bit to 1. For
endpoints set for Bulk or Interrupt
transfer, set this bit to 0.
6.2.2
Transactions
The LSI provides transaction execution functions in hardware and provides the firmware with the
interfaces necessary to execute transactions. The interfaces for the firmware are implemented as control
and status registers and the interrupt signals that are asserted by a status. For details on setting interrupt
assertion by status, refer to the relevant section on registers.
The LSI issues a status to the firmware for each transaction performed. However, the firmware does
not always need to manage each individual transaction. When responding to a transaction request, the
LSI inspects the FIFO to find its data quantity or free space to determine whether a data transfer can be
performed, and then performs the transaction automatically.
For an OUT endpoint, for example, the firmware can read data out of the FIFO through the CPU
interface (register read) to create a free space in the FIFO, thereby allowing OUT transactions to be
automatically executed in succession. For an IN endpoint also, the firmware can write data to the FIFO
through the CPU interface (register write) to create valid data in the FIFO, thereby allowing IN
transactions to be automatically executed in succession.
Table 6.7 lists the control items and status relating to the transaction control for the endpoint EP0.