I think I made some progress in diagnosing the UHD/Beagleboard USRP1 issue. I've tried bitbaking Philip's GNU Radio 3.2.1 recipe and the compilation fails because of the libusb-0.1.12 link, more specifically the "libusb-gnur.a" library. For some reason GCC is expecting the library to have the "-fPIC" flag passed when building the library which doesn't make sense since it's trying to link against a static library and not a shared librar ... it was complaining about an ARM_MOV or something like that assembly command. To my understanding the libtool included in the libusb should make sure that such confusion doesn't happen which in using GCC 4.3 was not an issue but with the GCC 4.5 included in the new tree is an issue.
I also tried incorporating the libusb fix against the GNU Radio GIT recipe but the configure stage fails because gnuradio can't find the "USB_BULK_WRITE" function in the libusb library from libusb-0.1.12 which when I looked is actually there. When I bypass the configure check for USB_BULK_WRITE the gnuradio compilation fails at the same stage as gnuradio 3.2.1. I feel like the libusb-0.1.12 static library is corrupt for some reason more specifically I think libtool might be the culprit.
I assume that USB_BULK_WRITE is used in the USRP sink UHD block which might explain why I can receive but I can't write using the UHD driver. The libusb-0.1.12 fix included in the UHD driver, did it use GCC 4.5? did it use libusb-0.1.12? an older or newer version maybe? did it use a different libtool?
I need to find a way to pass the -fPIC flag to the configure stage of libusb-0.1.12 unfortunately I can't seem to find an easy way to do it and I'm about to head out of town for a few days. Other than that doese anyone have any suggestion?
Josh or Philip :)
al fayez
-----Original Message-----
From: Almohanad Fayez <address@hidden>
To: philip <address@hidden>
Cc: discuss-gnuradio <address@hidden>
Sent: Thu, Feb 24, 2011 6:42 pm
Subject: Re: [Discuss-gnuradio] UHD Driver in E100/Beagleboard
1- I'm using the host USB not the OTG
2- I'm using the 2.6.37 kernel with Angstrom 2010
3- The following is the dmesg output which looks ok ... at least to me :)
[ 108.369293] usb 1-2.3.1: USB disconnect, address 4
[ 108.770874] usb 1-2.3.1: new high speed USB device using ehci-omap and address 6
[ 108.889404] usb 1-2.3.1: New USB device found, idVendor=fffe, idProduct=0002
[ 108.889434] usb 1-2.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 108.889465] usb 1-2.3.1: Product: USRP Rev 4
[ 108.889465] usb 1-2.3.1: Manufacturer: Free Software Folks
[ 108.889495] usb 1-2.3.1: SerialNumber: 4bd1d69b
I think I'll try to attempt to redo your libusb hack by copying it from the older gnuradio recipes and attempt to use the original USRP USB driver if the problem ends up being too major ... unless you want to do that as a favor to me and push the recipe into the openembedded tree !!! pretty please :)
al fayez
-----Original Message-----
From: Philip Balister <
address@hidden>
To: Almohanad Fayez <
address@hidden>
Cc: discuss-gnuradio <
address@hidden>
Sent: Thu, Feb 24, 2011 2:20 pm
Subject: Re: [Discuss-gnuradio] UHD Driver in E100/Beagleboard
On 02/23/2011 11:25 PM, Almohanad Fayez wrote:
> I was wondering about people's experience with the UHD driver on the E100 or
the Beagleboard. I am able to use it to receive IQ data from the USRP but I
can't seem to transmit anything from it ... if I take the same flowgraph to a
laptop I'm able to transmit IQ using the same USRP/daughterboard and the UHD
driver however when I try to run the same transmitter on the Beagleboard and I
check my spectrum analyzer I don't see anything
>
> I already did a signal capture before sending to the USRP and made sure that
there is data getting pushed through ... is there a problem with UHD/USRP
sinking on the E100 and the Beagleboard ??? I also made sure that I'm using the
latest UHD firmware on the beagleboard.
>
>
> The following is the version info printed when I run the flowgraph:
> linux; GNU C++ version 4.5.3 20110214 (prerelease); Boost_104500;
UHD_0001.20110224034946.1
Al,
Which USB port are you using to connect the USRP1? What kernel version?
Can you run dmesg and see if there are any usb related messages at the end?
Philip