On 4/21/22 22:51, Farhan Khan wrote:
I fooled around a bit with `-f Y`, because I was not certain if the
offset was 0 or 1, but I think (could be wrong) the value for the
interrupt and what the data is loaded over is interrupt 3.
It appears to me that the size of the interrupt is 1024 based on this:
-------
$ sudo usbdump -i usbus3 -s 256 -vvv -f 3
16:46:25.723242 usbus3.3 SUBM-CTRL-
EP=00000000,SPD=HIGH,NFR=2,SLEN=1024,IVAL=0
frame[0] WRITE 0 bytes
frame[1] WRITE 1024 bytes
flags 0x10 <PROXY_BUFFER|0>
status 0xea0a3
<OPEN|TRANSFERRING|STARTED|CONTROL_XFR|BDMA_ENABLE|BDMA_SETUP|CURR_DMA_
SET|CAN_CANCEL_IMMED|DOING_CALLBACK|0>
--------
Should this change make a difference to the interrupt issue?
- Farhan
If your device is ugenX.Y, usbdump is:
usbdump -i usbusX -f Y -s 256 -vvv
--HPS
