Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
I connected the USRP to the USB 2.0 port and obtained the information of the device using the lsusb -v command in Ubuntu. The output is attached below. Even in Ubuntu, the interfaces and endpoints come out to be different than those defined in usrp_interfaces.h. So what is going on here? Which are the actual interfaces and end points? Bus 005 Device 003: ID fffe:0002 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0xfffe idProduct 0x0002 bcdDevice0.02 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 171 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x88 EP 8 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 2 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7
Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
On Fri, Apr 24, 2009 at 05:27:06PM +0600, Ujala Qasim wrote: I connected the USRP to the USB 2.0 port and obtained the information of the device using the lsusb -v command in Ubuntu. The output is attached below. Even in Ubuntu, the interfaces and endpoints come out to be different than those defined in usrp_interfaces.h. So what is going on here? Which are the actual interfaces and end points? Bus 005 Device 003: ID fffe:0002 As Philip pointed out, you haven't loaded the FX2 firmware yet. You can tell this by looking at the bcdDevice field. When it's got the real firmware loaded, it has a non-zero value to the left of the radix point. Here's what it looks like after you load std.ihx: Bus 001 Device 011: ID fffe:0002 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0xfffe idProduct 0x0002 bcdDevice1.02 iManufacturer 1 Free Software Folks iProduct2 USRP Rev 2 iSerial 6 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 50 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 3 Command Status Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 4 Transmit Path Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Receive Path Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
Thanks for pointing out the problem. But doesn't the FX2 firmware download automatically? Isn't it a part of the USRP's boot sequence? How can I load the firmware then to get rid of this problem? On Fri, Apr 24, 2009 at 11:27 PM, Eric Blossom e...@comsec.com wrote: On Fri, Apr 24, 2009 at 05:27:06PM +0600, Ujala Qasim wrote: I connected the USRP to the USB 2.0 port and obtained the information of the device using the lsusb -v command in Ubuntu. The output is attached below. Even in Ubuntu, the interfaces and endpoints come out to be different than those defined in usrp_interfaces.h. So what is going on here? Which are the actual interfaces and end points? Bus 005 Device 003: ID fffe:0002 As Philip pointed out, you haven't loaded the FX2 firmware yet. You can tell this by looking at the bcdDevice field. When it's got the real firmware loaded, it has a non-zero value to the left of the radix point. Here's what it looks like after you load std.ihx: Bus 001 Device 011: ID fffe:0002 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0xfffe idProduct 0x0002 bcdDevice1.02 iManufacturer 1 Free Software Folks iProduct2 USRP Rev 2 iSerial 6 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 50 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 3 Command Status Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 4 Transmit Path Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Receive Path Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
On Sat, Apr 25, 2009 at 01:23:40AM +0600, Ujala Qasim wrote: Thanks for pointing out the problem. But doesn't the FX2 firmware download automatically? Isn't it a part of the USRP's boot sequence? How can I load the firmware then to get rid of this problem? If you use the C++ interface we provide, then yes, it does get loaded by the library. Since you're not, you'll need to load it yourself. I suggest that you go back and look at the code for these constructors: usrp_basic, usrp_basic_rx, usrp_basic_tx, usrp_standard, usrp_stardard_rx, usrp_standard_tx. Are you sure you don't want to create a C-callable wrapper for the known correct C++ code? Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
Ujala Qasim wrote: Hi, I am writing a Windows interface for USRP using libusb-win32. However, I am facing a problem. When I run the testlibusb wizard (a utility tool for displaying information about USB devices) in Windows, it tells me that the USRP has only one interface: Interface 0. This interface has three alternative settings. Each having 6 endpoints. These interfaces are different than those defined in usrp_interfaces.h. Please let me know which interface should I be using as the RX and TX interface in Windows? Is this before you download the data files to the USRP? If so, I think the additional endpoints are configured after you load the firmware into the FPGA. Philip smime.p7s Description: S/MIME Cryptographic Signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
On Fri, Apr 24, 2009 at 01:01:39AM +0600, Ujala Qasim wrote: Hi, I am writing a Windows interface for USRP using libusb-win32. However, I am facing a problem. When I run the testlibusb wizard (a utility tool for displaying information about USB devices) in Windows, it tells me that the USRP has only one interface: Interface 0. This interface has three alternative settings. Each having 6 endpoints. These interfaces are different than those defined in usrp_interfaces.h. Please let me know which interface should I be using as the RX and TX interface in Windows? Thanks. Are you sure you're plugged into a USB 2.0 port? The USRP requires USB 2.0. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Definition of USB Interfaces is different in Windows
Yes, I am sure. Because I am running USRP on Ubuntu with GNU Radio on the same computer and usb port and it is running absolutely fine. I read another thread on a forum, which gives same interfaces and endpoint numbers on Windows: http://www.nabble.com/usrp-and-u...@-fedora-9-td22833152.html I get the exact information on Windows as he gets them on Fedora 9. Thanks. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
