[Discuss-gnuradio] fpga halfband filter
Dear everyone: In the FPGA code of halfband_decim,v of USRP1, it has a input strobe_in, which indates a new data comes. Strobe_in is determined by the decimation rate. For example if we decimate by 6 we write to the register FR_DECIM_RATE 6/2-1=2 and strobe_in comes high every 3 clocks. My question is that if I want to use halfband filter only to get a decimation of 2 (for other purpose of my FPGA project, not used in USRP), how should I set strobe_in? I noticed that whether I set it equal to the clock or set it equal to 1, the strobe_out always comes high every two clocks and data_out is different. So can you tell me how I should set strobe_in? Besides my data are 8 bits wide, is it proper to pad 0 to my data to reach 16 bits wide? Best regards___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] volk work update - automatic alignment and custom dispatchers
Greetings VOLK enthusiasts, The last remaining frontier for VOLK development: Dealing automatically with buffer alignment, head cases, and tail cases. Here is my attempt... All work can be found on the volk_work branch of my github https://github.com/guruofquality/gnuradio/tree/volk_work --- -- Combining unaligned and aligned kernels --- So, A VOLK kernel is a computational function with one or more implementations of this function. Each implementation has a unique name and requirements for SIMD instructions sets and alignment. Currently, most VOLK kernels are actually split into two kernels, one called aligned and the other called unaligned... based on the ability for an implementation to handle randomly aligned pointers, or not. One of the things this branch does is combine those two separate kernels into one. What was bar_u.h and bar_a.h becomes bar.h. Here is the break down: 1) A kernel is now completely in one file, not two. After-all, its conceptually really just *one* kernel. Doing so lets us take advantage of potential common code. For example, we were copying the generic C implementation of the kernel and copying it twice or bar_a and bar_u. 2) The API need not be broken. Since the build system has a concept of implementations that do and do not require alignment, it can still provide separate function pointers for specifically aligned and unaligned implementations. So kernel bar.h provides bar() which is new; and the familiar bar_a(), and bar_u() 3) The build system can automatically dispatch based on alignment. If all of the pointers are on alignment boundaries, bar() will call bar_a(), otherwise, bar() will call bar_u(). Doing this, I was able to remove all of the conditional dispatching based on alignment inside of the various gnuradio work functions that were calling into volk. In other words, VOLK itself does the dirty work. 4) No tedious code shuffling required. This handy python script converts and combines all the old implementations automatically! https://github.com/guruofquality/gnuradio/blob/volk_work/volk/convert_kernels.py --- -- Custom dispatchers --- Now that unaligned and aligned kernels are conceptually together, the user can also implement custom dispatchers for a kernel within the same space as the kernel implementations. Why write a dispatcher? Well, the automatic behaviour has limitations. For example, suppose that one of the pointers is an accumulator and you dont care about its alignment constraints. A custom dispatcher also means that the user can now implement head and tail cases. Head cases mean that we can attempt to recover alignment when starting with unaligned pointers. And tail cases means that the kernel implementations themselves dont have to copy-paste the generic implementation to deal with remainder num_points. The following README contains two working examples of custom dispatchers: https://github.com/guruofquality/gnuradio/blob/volk_work/volk/kernels/README.txt --- -- GNU Radio considerations --- The VOLK changes should be API compatible, so we could change nothing. Usage of volk in work functions - with these changes its no longer necessary to perform the dispatching inside of the work function. This should be conceptually appealing at the very least. Usage of set_alignment_multiple - I suspect that we would still want the re-alignment aspect of this setting. That is, after handling an edge case, the scheduler tries to get back to a state of buffer alignment. On the other hand, if the author of the kernel writes a custom dispatcher that handles the head case, then there is nothing to gain by manipulating the scheduler in this way. Note: ignore the changes to gnuradio (outside of volk) on the volk_work branch. Those changes should be obviously, left to be decided. --- As always, feedback is welcome! -josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] b100 error
Hello to all After compiling with different versions of the library BOOST (1.46.1,1.47.0,1.48.0,1.49.0) the problem remained, so it is not the library BOOST the blame of the SID message problem. But in my case the problem has become much less evident after recompile the library LIBUSB, what I think happened was that the library will have built with gcc4.5.3 (x86_64-pc-linux-gnu-4.5.3) and compiled after with gcc-4.6.3 (x86_64-pc-linux-gnu-4.6.3) the SID message problem rarely manifests itself. I currently have libusb-1.0.9 and rarely see the SID messages, t think the problem is related to libusb in my case Linux uname -a Linux radio 3.4.4-gentoo #1 SMP PREEMPT Mon Jun 25 10:58:07 WEST 2012 x86_64 Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz GenuineIntel GNU/Linux gcc-4.6.3 (x86_64-pc-linux-gnu-4.6.3) glibc-2.15 UHD linux; GNU C++ version 4.6.3; Boost_104900; UHD_003.004.002-162-g485fe587 UHD-image 003.004.001-109-g6ca39ad9 Wed Apr 25 19:13:06 PDT 2012 Best regards, Jose Quaresma 2012/6/12 tzopik : > I think the problem is related to the host code, because i have an > UBUNTU installations where the SID message appears less times and b100 > hardware no need a reboot to working correctly. > > In GENTOO i have this version of the UHD: > > linux; GNU C++ version 4.6.3; Boost_104900; UHD_003.004.002-137-g49d4f8e4 > > cat /usr/share/uhd/images/003.004.001.tag > 003.004.001-109-g6ca39ad9 > Wed Apr 25 19:13:06 PDT 2012 > > md5sum /usr/share/uhd/images/usrp_b100_fpga.bin > /usr/share/uhd/images/usrp_b100_fw.ihx > 4016e7efd022cb9f7c7be7ecfcd89d16 /usr/share/uhd/images/usrp_b100_fpga.bin > 622e25ca14ac6bd4fbb518b32dbf58d6 /usr/share/uhd/images/usrp_b100_fw.ihx > > > I have my B100 with SBX about one week and in GENTOO freezes > constantly but in UBUNTU this happens less times. > I will try to compile UHD host code with the same "BOOST" version of > ubuntu in my gentoo to view if the problem persisting and then inform > the result. > > > Best regards, > Jose Quaresma > > > 2012/6/11 Josh Blum : >> Hey guys, >> >> I'm looking into this. I really thought I squashed this bug, so please >> make sure you have the latest image. If you are using the master branch >> this would be: >> >> md5sum /usr/local/share/uhd/images/usrp_b100_fpga.bin >> 4016e7efd022cb9f7c7be7ecfcd89d16 >> /usr/local/share/uhd/images/usrp_b100_fpga.bin >> >> -josh >> >> On 06/11/2012 10:51 AM, sumitstop wrote: >>> >>> Hi Josh, >>> Did you update the code :-) >>> >>> Josh Blum-3 wrote: > > the SID keeps changing although .. While I saw I similar problem earlier > in > this > thread(http://old.nabble.com/uhd-b100-problems-td33345827.html#a33345827 > ) > but I am afraid that the problem still persists :( > > my UHD version is uhd-images_003.004.001-109-g6ca39ad9 This is an RX issue. I really swear I had nailed this down a while ago. Do you mind trying an update? It looks like you are using the master branch. I would update the host code and grab images here: http://files.ettus.com/binaries/master_images/ -josh > > Thanks > > - > Sumit Kr. > Research Assistant > Communication Research center > IIIT Hyderabad > India ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >>> >>> - >>> Sumit Kr. >>> Research Assistant >>> Communication Research center >>> IIIT Hyderabad >>> India > > > > -- > Cumprimentos, > José Quaresma -- Cumprimentos, José Quaresma ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP2 + RFX900 + Antenna Anritsu
I can use the usrp2 + rfx900 Anritsu mark with an antenna with these characteristics? * * Product Description: Portable Antenna, SMA (m), 896-941 MHz, 50 Ohm ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Question about OFDM and USRP
Hi all , i have a question , while i am transmitting OFDM through USRP 2 board and receiving it through another board , USRP N210 , i received data after USRP source but after OFDM demod. block there is no thing received (demodulated) . when i connected OFDM_demod to a vector sink , and then , when i displayed output of this vector sink , it was () , which means an empty buffer (or vector) and no thing is demodulated .. What is the problem ? I need any help please . Thanks in-advance Amr, ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Sink and Source that pass on Stream Tags
I tried udp and file sink and source to pass on stream tags but I don't receieve them on the source side. Am I missing something? Are there any way to pass on steam tags to another machine or save them to a file. Thanks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Question about inter-block communications
Dear Discussion List, I'm just starting with GnuRadio and I would like to understand how the GnuRadio block threads communicate with each other and use shared memory. Does anyone have any insight and/or resources around this subject? Sincerely, Tommy J. Tracy II Computer Engineering University of Virginia signature.asc Description: Message signed with OpenPGP using GPGMail ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] What is input RF, Daugherboard RFX900 ?
What is input RF, Daugherboard RFX900 ? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP signal is different from the spectrum analyzer
Try reducing input pwr to usrp. John On Thursday, July 5, 2012, Julio Hector Aguilar Renteria < jhagui...@gmail.com> wrote: > The USRP, always show this picture, but is different from the spectrum analyzer and signal hound on the same frequency. > may be happening to the signal is different. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
