I have this that Beagle USB 2.0 analyzer complains as PID sequence error:
What I see is that the first OUT was done properly:
OUT token
DATA0 packet
NYET response
PING
ACK response
OUT token
DATA1 packet
NYET response
PING
ACK response
OUT token
DATA0 packet
NYET response
Then I saw the following marked as PID sequence error, which happened over 200us after NYET:
PING
ACK response
2 SOF's but the time stamp is later:
OUT token
DATA1 packet
NYET response
I wonder if the timing of over 200us between NYET and PING/ACK caused the analyzer to think the sequence is wrong. I don't think the sequence is wrong.
What I see is that the first OUT was done properly:
OUT token
DATA0 packet
NYET response
PING
ACK response
OUT token
DATA1 packet
NYET response
PING
ACK response
OUT token
DATA0 packet
NYET response
Then I saw the following marked as PID sequence error, which happened over 200us after NYET:
PING
ACK response
2 SOF's but the time stamp is later:
OUT token
DATA1 packet
NYET response
I wonder if the timing of over 200us between NYET and PING/ACK caused the analyzer to think the sequence is wrong. I don't think the sequence is wrong.