Hello,
We are running into an issue when our target USB device wakes from DOZE mode due to an OUT transfer from the USB host. The data in first OUT from the host wakes the target. The bus sniffer shows the first packet is ACK'ed (yes ACK'ed. Not NACK'ed, stalled, etc). Yet, the software doesn't see the transfer complete bit until the second OUT is ACK'ed.
I don't want to poison the well. But, it seems the software may not see the transfer complete interrupt for the first OUT because the CPU clock is off when it arrives. Is this plausible? Is there a way around this?
In preparation for doze mode:
Observations:
Thanks in advanced!
Stephen
Hi Stephen,
You could take a look at the following Community thread, and application note, in order to verify if this may apply in your case:
https://community.nxp.com/thread/464548
https://www.nxp.com/docs/en/application-note/AN3683.pdf
Hope this will be useful for you.
Best regards!
/Carlos
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Carlos,
Thanks for getting back to me. That was my community post. The problem was the OTG port hadn't been setup correctly. The first OUT packet size is 5 bytes. So I don't think that app note applies. Other thoughts?
Stephen