at91cap7e ATMEL Corporation, at91cap7e Datasheet - Page 459

• Manufacturer Part Number: at91cap7e
• Description: Customizable Microcontroller
• Manufacturer: ATMEL Corporation

31.6.10
Register Name:
Access Type:
WARNING: Due to synchronization between MCK and UDPCK, the software application must wait for the end of the write
operation before executing another write by polling the bits which must be set/cleared.
• TXCOMP: Generates an IN Packet with Data Previously Written in the DPR
This flag generates an interrupt while it is set to one.
Write (Cleared by the firmware):
0 = Clear the flag, clear the interrupt.
1 = No effect.
Read (Set by the USB peripheral):
0 = Data IN transaction has not been acknowledged by the Host.
1 = Data IN transaction is achieved, acknowledged by the Host.
After having issued a Data IN transaction setting TXPKTRDY, the device firmware waits for TXCOMP to be sure that the
host has acknowledged the transaction.
• RX_DATA_BK0: Receive Data Bank 0
This flag generates an interrupt while it is set to one.
Write (Cleared by the firmware):
0 = Notify USB peripheral device that data have been read in the FIFO's Bank 0.
8549A–CAP–10/08
//! Clear flags of UDP UDP_CSR register and waits for synchronization
#define Udp_ep_clr_flag(pInterface, endpoint, flags) { \
//! Set flags of UDP UDP_CSR register and waits for synchronization
#define Udp_ep_set_flag(pInterface, endpoint, flags) { \
EPEDS
DIR
while (pInterface->UDP_CSR[endpoint] & (flags)) \
}
while ( (pInterface->UDP_CSR[endpoint] & (flags)) != (flags) ) \
}
31
23
15
–
7
pInterface->UDP_CSR[endpoint] &= ~(flags); \
pInterface->UDP_CSR[endpoint] |= (flags); \
UDP Endpoint Control and Status Register
RX_DATA_
BK1
30
22
14
–
–
6
FORCE
STALL
29
21
13
–
–
5
UDP_ CSRx [x = 0..5]
Read/Write
TXPKTRDY
28
20
12
–
–
4
RXBYTECNT
STALLSENT
ISOERROR
DTGLE
27
19
11
–
3
RXSETUP
26
18
10
2
RXBYTECNT
RX_DATA_
EPTYPE
BK0
25
17
9
1
AT91CAP7E
TXCOMP
24
16
8
0
459