Re: [Discuss-gnuradio] Funcube Dongle source block for GNU Radio
Hi Alex, Thanks for that, by changing to 'hidmac.c' it now compiles fine. Unfortunately, I am now getting a segmentation fault wen I run your grc NBFM receiver :( I'll have a deeper look when I get time. Cheers, Mike M0MIK On 21 July 2011 16:20, Alexandru Csete wrote: > On Thu, Jul 21, 2011 at 3:12 PM, Mike Jameson wrote: > > Hi Alex, > > > > Thanks for the fantastic job on gr-FCD, it works beautifully on Ubuntu > 11.04 > > x64. > > > > Now I am trying to get it to work on my Mac but have an issue with > 'make'. > > Does the following error instantly ring any bells for you? > > ... > > Hi Mike, > > I only made it work on Linux, but only because lack of time and I > didn't have GNU Radio on Mac or windows. The control code is the same > as in qthid and should therefore work on all platforms. > > On linux gr-fcd uses libusb-1.0 but on Mac and Windows it is supposed > to use native IO libs. > > To make it work on Mac, the lib/Makefile.am has to be updated to > compile hidmac.c instead of hid-libusb.c > The same on windows: should compile hidwin.c instead of hid-libusb.c > (note that all three use the same interface hidapi.h) > > Also, the libusb dependency can be removed on Mac and windows. On the > other hand one needs to link to the corresponding native IO libs on > Mac and windows, see qthid.pro lines 48-50: > https://github.com/csete/qthid/blob/master/qthid.pro > > Alex > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] New build-gnuradio
Mr. UHD, being a man of some comedic genius, has once again roto-rootered the file structure on the web server that serves up UHD Firmware/FPGA images :-) So, I had to change build-gnuradio to deal with the new world. http://www.sbrac.org/build-gnuradio -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] New build-gnuradio
On 07/23/2011 12:27 PM, Josh Blum wrote: Is it because the version names changed? Can you wget the whole directory and pick out the first tar.gz file? This is what I now do: # # First, get listing of ettus.com/downloads/uhd_releases/master_images # We use spider mode, and use -r to descend # wget -np -r --spider http://www.ettus.com/downloads/uhd_releases/master_images >tmp$$ 2>&1 # # Now search the resulting log file for .tar.gz files that match the appropriate # pattern. # grep 'UHD-images.*tar.gz' tmp$$ |sed -e 's@.*Removing @http://@' |sort -r |head -1 >tmp2$$ Then # # Fetch the tar file (whose name is in ../tmp2$$) # fn=`cat ../tmp2$$|sed -e s/.$//` wget -nd $fn >/dev/null 2>&1 -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] New build-gnuradio
On 07/23/2011 01:16 PM, Marcus D. Leech wrote: On 07/23/2011 12:27 PM, Josh Blum wrote: Is it because the version names changed? Can you wget the whole directory and pick out the first tar.gz file? If you mess with the paths, be aware the OE reciep that grabs the firmware and repackages it for the E100 uses this recipe: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/uhd/uhd-firmware.inc You can use your imagination to work out what path I am depending on. Philip This is what I now do: # # First, get listing of ettus.com/downloads/uhd_releases/master_images # We use spider mode, and use -r to descend # wget -np -r --spider http://www.ettus.com/downloads/uhd_releases/master_images >tmp$$ 2>&1 # # Now search the resulting log file for .tar.gz files that match the appropriate # pattern. # grep 'UHD-images.*tar.gz' tmp$$ |sed -e 's@.*Removing @http://@' |sort -r |head -1 >tmp2$$ Then # # Fetch the tar file (whose name is in ../tmp2$$) # fn=`cat ../tmp2$$|sed -e s/.$//` wget -nd $fn >/dev/null 2>&1 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-dsp Library Block Parameters
Chris, I FINALLY got around looking at and fixing the problem ... I pushed updates to the easyCom-gpp and easyCom-dsp repos and updated the gpp prebaked packages there was a memory alignment issue that i didn't backup properly so I didn't push to the repos ... moral of the story regular backups are a good thing :) Try to keep your filter input and taps as multiples of 4, I added extra data points to the python file you sent me to do that. The DSP will always load 4 data points at a time which might not be an issue if the buffer has zeros in the latter locations but if you have left over data points from a previous filter operation it can throw your result off ... I need to add code that automatically pads unaligned input by zeros to address this but I won't get around to it for a while. As a piece of advise if you start developing code for the DSP, memory alignment can be an absolute nightmare so I really need to add API functions to handle it so developers won't have to face them with each newly developed function. Tell me if this update works for you. al -Original Message- From: Christopher Dean To: Almohanad Fayez Cc: discuss-gnuradio Sent: Thu, Jul 14, 2011 12:53 pm Subject: Re: [Discuss-gnuradio] gr-dsp Library Block Parameters I compiled the DSP code, as of Monday. How long ago did you find/fix the issue? On 7/14/2011 12:50 PM, Almohanad Fayez wrote: Did yourecompile the DSP code or did you download the the precompiled binary? I think there was an issue that I fixed in the DSP code but didn't update the binary. al -Original Message- From: Christopher Dean To: Almohanad Fayez Cc: discuss-gnuradio Sent: Thu, Jul 14, 2011 11:12 am Subject: Re: [Discuss-gnuradio] gr-dsp Library Block Parameters HiAl, That really clears things up conceptually. Thanks for the insight. Given that, I went back and modified the dsp test case to use a scaling factor of 15, normalized input, and normalized output, so the block invocation was "dsp.fir_ccf (src_coeff,15, 1, 0, 0, 0, 0)". Running the test provides: -0.0102 - 0.0102i -0.0104 - 0.0103i -0.0105 - 0.0105i -0.0106 - 0.0106i -0.0107 + 0.0010i 0.0111 + 0.0031i 0.0334 + 0.0061i 0.0671 + 0.0102i 0.1122 + 0.0154i However, this differs from the output of the gr.fir_filter_ccf block and the result of direct computationin MATLAB: 0.0010 + 0.0111i 0.0030 + 0.0334i 0.0061 + 0.0671i 0.0102 + 0.1122i 0.0154 + 0.1689i 0.0205 + 0.2255i 0.0257 + 0.2822i 0.0308 + 0.3388i 0.0360 + 0.3954i I've checked the magnitude and phase of each of these results, and it doesn't look like they're a simple rotationor multiple of each other. I thought that it might just not work for decimal sources/coefficients, so I adjusted the tests so that src = (1,1,1,1,1,1,1,1,1) and src_coeff = (1,1,1,1,1). Since we no longer needed to scale it before or after, our block invocation is "dsp.fir_ccf (src_coeff, 15, 1, 1, 1, 0,0)". This gives the output: 1.0e+04 * 3.2748 + 3.2751i 3.2762 + 3.2752i 3.2762 + 3.2767i 3.2763 - 3.2768i -3.2768 - 0.0001i 0 - 0.0002i 0 - 0.0003i 0 - 0.0004i 0 - 0.0005i 0 0 0 0 0 2.8678 - 3.2752i -3.2757 - 3.2751i -3.2757 + 0.0001i 0.0005 - 3.2768i -3.2768 The output from the gr.fir_filter_ccf test is the first nine elements of the MATLAB output: 1 2 3 4 5 5 5 5 5 Finally, I thought that the issue might be that I'm not normalizing my source coefficients. So, I normalized themin MATLAB, yielding src_coeff = (0.4472, 0.4472, 0.4472,0.4472, 0.4472), which provided the output:
Re: [Discuss-gnuradio] UHD Announcement - July 19th 2011
There are two more things I am not clear with. > > > > I understand that the FPGA and firmware images have to be updated, i.e. the > > newest images downloaded and "flashed" on the SD card in case of USRP2. > > However, since the source code is new too, should I rebuild and reinstall > > the UHD from the new source? > > > > The host code and images must match. If you want to use the latest > images, you have to download and install the latest UHD host code as > well. http://code.ettus.com/redmine/ettus/projects/uhd/wiki#Source-code 1. Why must code and images match? If FPGA image is newer than the UHD code one have installed, according to my logic only things that are different would not work. 2. I want to adjust the FPGA image slightly. I want to write some extra Verilog code and build it myself with Xilinx. However, since I change the image on the FPGA, and the installed UHD code has to match to the image, how can this work? Thank you in advance. Nemanja ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Hardware extending
Hello, I see that many guys here are using USRP hardware which is really great. However, I am interested in extending compatible hardware list by using any manufacturer FPGA development kit. The majority takes Altera development kits using HSMC port for additional hardware or Xilinx using FMC. Basically, yes, I am considering doing a new motherboard like the USRP which could be connected to the any FPGA development kit from Altera or Xilinx. All other ports for daughterboards should be the same and fit the new motherboard. My plan is to use Altera Stratix II GX development kit, which has PCIe x8 and 1Gbit ethernet and I will add CY7C68013 for USB connection. Now the more interesting part is ADC and DAC selection. We all know that USRP2 use at least 100MSPS ADC and DAC, 14bit and 16bit accuracy accordingly, so that would be the point of base: DACs: AD9777 from Analog devices. ADCs: LTC2284 from Linear Technologies. These devices are selected for 2 channels I/O or one pair I-Q, but can we consider other (possibly cheaper) options? For example it is possible to buy pretty cheap dual channel ADC 250MSPS here: http://cgi.ebay.com/ADS62P48-ADC-250MSPS-14bit-DDR-Parallel-Out-/180671130732?pt=LH_DefaultDomain_0&hash=item2a10d6ac6c , but are there any special hardware requirements? This particular option would be better for any student/amateur to buy, instead of using Digikey, Farnell, etc. I see a lot of documentation regarding GNU Radio, but there are almost nothing about hardware. I am not interested in taking over Ettus Research, but I hope to attract more people in hardware development :-) Stratix II GX development board: http://www.altera.com/products/devkits/altera/kit-pciexpress_s2gx.html EP2SGX90F1508C3 FPGA, 36384 ALMs (90960 eq. LEs), 48 DSP blocks, 192 18x18 multipliers, 8 PLLs, 4.5MB on chip memory. Thank You. Sincerely, Tomas D. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] New build-gnuradio
Hi Marcus, > > # > # First, get listing of ettus.com/downloads/uhd_releases/master_images > # We use spider mode, and use -r to descend > # > wget -np -r --spider > http://www.ettus.com/downloads/uhd_releases/master_images >tmp$$ 2>&1 > > # > # Now search the resulting log file for .tar.gz files that match > the appropriate > # pattern. > # > grep 'UHD-images.*tar.gz' tmp$$ |sed -e 's@.*Removing @http://@' > |sort -r |head -1 >tmp2$$ > - What do you mean by "the appropriate pattern" in the above comment, present in your script? Sorry, I am a newbie. BTW, in one of the recent mails you addressed you site with: www.sbrac.org/build-gnuradio which gives 404 error. The right address is: www.sbrac.org/files/build-gnuradio Thanks in advance. Nemanja ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] UHD Announcement - July 19th 2011
On Sat, 2011-07-23 at 18:55 +0100, Nemanja Trecakov wrote: > There are two more things I am not clear with. > > > > > > > I understand that the FPGA and firmware images have to be updated, > i.e. the newest images downloaded and "flashed" on the SD card in case > of USRP2. > > > However, since the source code is new too, should I rebuild and > reinstall the UHD from the new source? > > > > > > > The host code and images must match. If you want to use the latest > > images, you have to download and install the latest UHD host code as > > well. > http://code.ettus.com/redmine/ettus/projects/uhd/wiki#Source-code > > 1. Why must code and images match? If FPGA image is newer than the UHD > code one have installed, according to my logic only things that are > different would not work. Because we tend to change all sorts of stuff under the hood between releases. We try to keep things sane by using a FPGA "compatibility number", and use that compatibility number to ensure you're using compatible host code and FPGA images. > > 2. I want to adjust the FPGA image slightly. I want to write some > extra Verilog code and build it myself with Xilinx. However, since I > change the image on the FPGA, and the installed UHD code has to match > to the image, how can this work? You can do whatever you want to the FPGA image, we're just saying you should start with corresponding FPGA and UHD host code versions. --n > > Thank you in advance. > > Nemanja > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] New build-gnuradio
On 07/23/2011 02:09 PM, Nemanja Trecakov wrote: Hi Marcus, # # First, get listing of ettus.com/downloads/uhd_releases/master_images # We use spider mode, and use -r to descend # wget -np -r --spider http://www.ettus.com/downloads/uhd_releases/master_images>tmp$$ 2>&1 # # Now search the resulting log file for .tar.gz files that match the appropriate # pattern. # grep 'UHD-images.*tar.gz' tmp$$ |sed -e 's@.*Removing @http://@' |sort -r |head -1>tmp2$$ - What do you mean by "the appropriate pattern" in the above comment, present in your script? Sorry, I am a newbie. The pattern given by the "grep" regular expression and "sed" regular expression above, in the script. The right address is: www.sbrac.org/files/build-gnuradio Yup, sorry about that! -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
