So I could agree with the direction (host->device). It looks to me that wireshark/usbmon trace at a higher stack level and tries to deduce what would be on the wire from that.Īn example of what I can see is given below, what to we see here?.Ī)I could not even find bmtype=0x20 (of the setup, frame No=599)in the specs.ī)Because I have a HID device, I assumed this could be a report/feature config (the enumeration is passed at this stage).
there is no mention of that in the usb protocol as far as I could see. seems sometimes to be displayed with the setup data (8 bytes) and sometime not. And the data part of the enumeration, hid report etc. At least,it does not match my expectations :-). The direction of the transaction is very strange as well (to/from fields). I have looked at the usb protocol from What does wireshark show?ġ)One line per packet? (token, data, handshake)Ģ)One line per transaction? (token + + handshake) (my guess) I am trying to reverse engineer an usb (HID) device and cannot really figure out how what I see on wireshark (usbmon + wireshark on linux, or windows) relates to the usb protocol?.
0 kommentar(er)
