PDIUSBH11 Datasheet, PDF (11/26 Pages) NXP Semiconductors – Universal Serial Bus Hub

Philips Semiconductors
Universal Serial Bus Hub
Read Endpoint Status
Command
: 80–84h
Data
: Read 1 byte
Product specification
PDIUSBH11
76 54 3 2 1 0
00 00 0 0 0 0
POWER ON VALUE
RESERVED
SETUP PACKET
STALL
DATA 0/1 PACKET
BUFFER FULL
RESERVED
SETUP PACKET
STALL
DATA 0/1 PACKET
BUFFER FULL
A ‘1’ INDICATES THE LAST RECEIVED PACKET WAS A SETUP TOKEN
A ‘1’ INDICATES THE ENDPOINT IS STALLED
A ‘1’ INDICATES THAT THE LAST RECEIVED OR SENT PACKET HAD A DATA1 PID
A ‘1’ INDICATES THAT THE BUFFER IS FULL
SV00508
Read Buffer
Command
: F0h
Data
: Read multiple bytes (max 10)
The Read Buffer command is followed by a number of data reads, which return the contents of the selected endpoint data buffer. After each
read, the internal buffer pointer is incremented by 1.
The buffer pointer is not reset to the buffer start by the Read Buffer command. This means that reading or writing a buffer can be interrupted by
any other command (except for Select Endpoint), or can be done by more than one I2C transaction (read the first 2 bytes to get the number of
data bytes, then read the rest in other transactions).
The data in the buffer are organized as follows:
• byte 0: reserved: can have any value
• byte 1: Number / length of data bytes
• byte 2: Data byte 1
• byte 3: Data byte 2
Write Buffer
Command
: F0h
Data
: Write multiple bytes (max 10)
The Write Buffer command is followed by a number of data writes, which load the endpoints buffer. The data must be organized in the same
way as described in the Read Buffer command. The first byte (reserved) should always be 0. As in the Read Buffer command, the data can be
split up into different I2C data transactions.
WARNING
There is no protection against writing or reading over a buffer’s boundary or against writing into an OUT buffer or reading from an IN buffer. Any
of these actions could cause an incorrect operation. Data in an OUT buffer are only meaningful after a successful transaction.
1997 Aug 01
11