Re: Fwd: Fwd: request some hep for usb comminucation
Hi Thank you very much for the attention and support. Unfortunately I made a mistake, when I send data to the device, I expected that the device will send an answer for me, while I should read the response from the device. Thanks a lot M.Razavi 2013/6/11 Greg KH : > On Tue, Jun 11, 2013 at 12:29:19PM +0430, Mahdi Razavi wrote: >> Hi >> i install windowx XP and Ubuntu in vmware and install a USBlizer >> (trial) in host windows (win 7 64 bit). next snooping a message >> between an application and device. and send a same data from ubuntu to >> device. >> but device dosent responce. >> What reason might be that the device does not respond? > > No idea, you might want to contact the company to try to get the > specification for how to talk to the device from them. > > Good luck, reverse engineering is hard, > > greg k-h -- Best Regards M.Razavi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Fwd: request some hep for usb comminucation
On Tue, Jun 11, 2013 at 12:29:19PM +0430, Mahdi Razavi wrote: > Hi > i install windowx XP and Ubuntu in vmware and install a USBlizer > (trial) in host windows (win 7 64 bit). next snooping a message > between an application and device. and send a same data from ubuntu to > device. > but device dosent responce. > What reason might be that the device does not respond? No idea, you might want to contact the company to try to get the specification for how to talk to the device from them. Good luck, reverse engineering is hard, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Fwd: request some hep for usb comminucation
Hi i install windowx XP and Ubuntu in vmware and install a USBlizer (trial) in host windows (win 7 64 bit). next snooping a message between an application and device. and send a same data from ubuntu to device. but device dosent responce. What reason might be that the device does not respond? thanks a lot Mahdi Razavi 2013/6/10 Greg KH : > On Mon, Jun 10, 2013 at 10:25:26AM +0430, Mahdi Razavi wrote: >> Hi >> This is a Digital Radio which can report some data through USB to its >> application. The output of lsudb : >> Bus 002 Device 004: ID 238b:0a31 >> Device Descriptor: >> bLength18 >> bDescriptorType 1 >> bcdUSB 2.00 >> bDeviceClass 255 Vendor Specific Class > > Ick, a vendor-specific device :( > >> bDeviceSubClass 254 >> bDeviceProtocol 254 >> bMaxPacketSize0 8 >> idVendor 0x238b >> idProduct 0x0a31 >> bcdDevice0.00 >> iManufacturer 1 >> iProduct2 >> iSerial 0 >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 39 >> bNumInterfaces 1 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0xc0 >> Self Powered >> MaxPower4mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber2 >> bAlternateSetting 0 >> bNumEndpoints 3 >> bInterfaceClass 255 Vendor Specific Class >> bInterfaceSubClass255 Vendor Specific Subclass >> bInterfaceProtocol255 Vendor Specific Protocol >> iInterface 5 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x84 EP 4 IN >> bmAttributes2 >> Transfer TypeBulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 255 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes3 >> Transfer TypeInterrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0008 1x 8 bytes >> bInterval 1 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x04 EP 4 OUT >> bmAttributes2 >> Transfer TypeBulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 255 >> >> -- >> output od dmesg: >> [26785.637159] usb 2-2.1: new full-speed USB device number 11 using uhci_hcd >> [26785.748010] usb 2-2.1: config 1 has an invalid interface number: 2 >> but max is 0 >> [26785.748018] usb 2-2.1: config 1 has no interface number 0 >> [26785.759058] usb 2-2.1: New USB device found, idVendor=238b, idProduct=0a31 >> [26785.759064] usb 2-2.1: New USB device strings: Mfr=1, Product=2, >> SerialNumber=0 >> [26785.759069] usb 2-2.1: Product: Digital Radio >> [26785.759073] usb 2-2.1: Manufacturer: RIGOL Communications >> >> this device has a SDK for developing in windows but there isnt any in >> Linux. i know protocol specification of message, and try sniffing on >> windows verify protocol. >> but when send a same data in Linux(with pyusb) to device dosent >> response. i guess there is a initial handshake in driver layer between >> device and OS. > > There really shouldn't be, but you might want to run Windows under kvm > or vmware and snoop the data that way on the Linux side to determine the > whole protocol being used. > > Good luck, > > greg k-h -- Best Regards M.Razavi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Fwd: request some hep for usb comminucation
On Mon, Jun 10, 2013 at 10:25:26AM +0430, Mahdi Razavi wrote: > Hi > This is a Digital Radio which can report some data through USB to its > application. The output of lsudb : > Bus 002 Device 004: ID 238b:0a31 > Device Descriptor: > bLength18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class Ick, a vendor-specific device :( > bDeviceSubClass 254 > bDeviceProtocol 254 > bMaxPacketSize0 8 > idVendor 0x238b > idProduct 0x0a31 > bcdDevice0.00 > iManufacturer 1 > iProduct2 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 39 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xc0 > Self Powered > MaxPower4mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber2 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass255 Vendor Specific Subclass > bInterfaceProtocol255 Vendor Specific Protocol > iInterface 5 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x84 EP 4 IN > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 255 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes3 > Transfer TypeInterrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x04 EP 4 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 255 > > -- > output od dmesg: > [26785.637159] usb 2-2.1: new full-speed USB device number 11 using uhci_hcd > [26785.748010] usb 2-2.1: config 1 has an invalid interface number: 2 > but max is 0 > [26785.748018] usb 2-2.1: config 1 has no interface number 0 > [26785.759058] usb 2-2.1: New USB device found, idVendor=238b, idProduct=0a31 > [26785.759064] usb 2-2.1: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [26785.759069] usb 2-2.1: Product: Digital Radio > [26785.759073] usb 2-2.1: Manufacturer: RIGOL Communications > > this device has a SDK for developing in windows but there isnt any in > Linux. i know protocol specification of message, and try sniffing on > windows verify protocol. > but when send a same data in Linux(with pyusb) to device dosent > response. i guess there is a initial handshake in driver layer between > device and OS. There really shouldn't be, but you might want to run Windows under kvm or vmware and snoop the data that way on the Linux side to determine the whole protocol being used. Good luck, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: Fwd: request some hep for usb comminucation
Hi This is a Digital Radio which can report some data through USB to its application. The output of lsudb : Bus 002 Device 004: ID 238b:0a31 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 254 bDeviceProtocol 254 bMaxPacketSize0 8 idVendor 0x238b idProduct 0x0a31 bcdDevice0.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower4mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 255 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 255 -- output od dmesg: [26785.637159] usb 2-2.1: new full-speed USB device number 11 using uhci_hcd [26785.748010] usb 2-2.1: config 1 has an invalid interface number: 2 but max is 0 [26785.748018] usb 2-2.1: config 1 has no interface number 0 [26785.759058] usb 2-2.1: New USB device found, idVendor=238b, idProduct=0a31 [26785.759064] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [26785.759069] usb 2-2.1: Product: Digital Radio [26785.759073] usb 2-2.1: Manufacturer: RIGOL Communications this device has a SDK for developing in windows but there isnt any in Linux. i know protocol specification of message, and try sniffing on windows verify protocol. but when send a same data in Linux(with pyusb) to device dosent response. i guess there is a initial handshake in driver layer between device and OS. 2013/6/10 Greg KH : > On Mon, Jun 10, 2013 at 01:01:15AM +0430, Mahdi Razavi wrote: >> Hi >> I am mahdi. >> i want to communicate with a radio over USB. creator of this radio >> only support windows driver for communicate, but i want to have >> connection in Linux. > > What device is this exactly? What is the output of 'lsusb -v' with it > plugged in? > >> i have a SDK for windows and protocol specification of this device and >> do some sniffing USB port on connection in windows. >> may you help me how to have connection with this device in Linux? >> or how can i write a driver for this device in Linux? > > What type of interface to userspace do you need for this device? Can it > be a "dumb" serial-like interface that you send it AT modem commands? > Or do you need to do other stuff with it? > > What about just using libusb to talk directly to it from your program > from userspace, no kernel driver is needed for that. > > thanks, > > greg k-h -- Best Regards M.Razavi -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
