Isn't this behavior proper & expected ? It covers cases when ACK response got corrupted, causing the host to send a retry (having un-altered DATA0/DATA1 flag). A device then suppose to ignore the content and just respond with ACK.jdb wrote:Found the cause of this: Interrupt OUT packets were always sent with a DATA0 PID, instead of alternating DATA0/DATA1. The odd thing is that the PIC's USB engine always responds with ACK, i.e. accepted the packet, despite the evidence being that it discards it if it's wrong.
Good news, thanks.jdb wrote:Patch inbound should fix this
Best wishes, Ivan Zilic.