PDIUSBH12N PHILIPS [NXP Semiconductors], PDIUSBH12N Datasheet - Page 14

• Manufacturer Part Number: PDIUSBH12N
• Description: USB 2-port hub
• Manufacturer: PHILIPS [NXP Semiconductors]

Philips Semiconductors
Table 3. Error codes
Read Endpoint Status
Command
Data
Setup Packet
STALL
Data 0/1 Packet
Buffer Full
1999 Jul 22
ERROR
CODE
USB 2-port hub
0000
0001
0010
0100
0101
1000
1001
1010
0011
0110
0111
1011
1101
1111
No Error
PID encoding Error; bits 7–4 are not the inversion of
bits 3–0
PID unknown; encoding is valid, but PID does not
exist
Unexpected packet; packet is not of the type expected
(= token, data or acknowledge), or SETUP token to a
non-control endpoint
Token CRC Error
Data CRC Error
Time Out Error
Babble Error
Unexpected End-of-packet
Sent or received NAK
Sent Stall, a token was received, but the endpoint was
stalled
Overflow Error, the received packet was longer than
the available buffer space
Bitstuff Error
Wrong DATA PID; the received DATA PID was not the
expected one
X X
7
6
5
0
: 80–8Dh
: Read 1 byte
4
0
3
0
2
0
1
X
A ‘1’ indicates the last received
packet had a SETUP token.
A ‘1’ indicates the endpoint is
stalled.
or sent packet had a DATA1 PID.
full.
A ‘1’ indicates if the last received
A ‘1’ indicates that the buffer is
X
0
RESULT
POWER ON VALUE
RESERVED
SETUP PACKET
STALL
DATA 0/1 PACKET
BUFFER FULL
RESERVED
SV00833
14
Read Buffer
Command
Data
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 I
to get the number of data bytes, then read the rest in other
transactions).
The data in the buffer are organized as follows:
Write Buffer
Command
Data
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 I
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.
Clear Buffer
Command
Data
When a packet is received completely, an internal endpoint buffer
full flag is set. All subsequent packets will be refused by returning a
NAK. When the microcontroller has read the data, it should free the
buffer by the Clear Buffer command. When the buffer is cleared new
packets will be accepted.
Validate Buffer
Command
Data
When the microprocessor has written data into an IN buffer, it should
set the buffer full flag by the Validate Buffer command. This indicates
that the data in the buffer are valid and can be sent to the host when
the next IN token is received.
byte 0:
byte 1:
byte 2:
byte 3:
Reserved: can have any value
Number/length of data bytes
Data byte 1
Data byte 2
: F0h
: Read multiple bytes (max 10)
: F0h
: Write multiple bytes (max 10)
: F2h
: None
: FAh
: None
2
C transaction (read the first 2 bytes
2
C data transactions.
PDIUSBH12
Product specification