Closed wetechautomation closed 3 years ago
No. Interrupt transfer has handshake phase but isochronous transfer has not. There is error if host expects handshake but device has no response.
No actually I mentioned reverse , let say my host have interrupt endpoint and I want to communicate with device isochronous Endpoint ? And now my host sends ACK after data , and device being isochronous endpoints ignores that. can I keep doing this ?
Not recommended.
hello xiao,
in ux_host_class_hub_change_process.c file , can you please explain why length '0' is being send on line 109 and 110 ?
/* The actual length should be cleared for the next transfer. */
transfer_request -> ux_transfer_request_actual_length = 0;
I think it's something for backsword compatibility in case lower level driver does not reset actual length to 0 (actually that should be done by HCD but not in stack).
We are developing an example where device continuously stream data through an isochronous IN endpoint. Now my question was as interrupt and isochronous have lot of similarities :
can I use my host interrupt endpoint to configure is to read from device's isochronous endpoints ?
device isochronous endpoints is following :
I understand there is NACK/ACK token in the interrupt endpoints , but let say if device ignores this NACK/ACK token can I still communicate with device using my interrupt endpoints ?