[Ftdi-usb-sio-devel] FT232AM/BM Vendor_Device: Request 90
Brought to you by:
bryder
From: John W. <joh...@wi...> - 2002-12-12 22:51:30
|
Hi All, I'm working through pages of SnoopyPro output, trying to work out how my ftdi-based device works under Windows. Most of the traces make sense, but on startup a lot of URB_FUNCTION_VENDOR_DEVICE urbs are sent down with small responses back. Examination of the returning urbs suggests it's getting the product and vendor strings. Example: 00000132 0.02340018 >>>>>>> URB 5 going down... 00000133 0.02340493 -- URB_FUNCTION_VENDOR_DEVICE: 00000134 0.02341275 TransferFlags = 00000003 (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK) 00000135 0.02341890 TransferBufferLength = 00000002 00000136 0.02342588 TransferBuffer = f403bbb2 00000137 0.02343063 TransferBufferMDL = 00000000 00000138 0.02343594 UrbLink = 00000000 00000139 0.02344069 RequestTypeReservedBits = 00 00000140 0.02344572 Request = 90 <<<HERE 00000141 0.02345075 Value = 0000 00000142 0.02345577 Index = 0001 Does this mean Request 90 is some type of 'get memory location' request? Can anyone confirm this and what the full structure of the request urb for it is? Thanks jw |