Re: [Discuss-gnuradio] lock and unlock with transmit h_path and receive_path
Update: I moved the reconfiguration one level up, to transmit_path.py and it works for high interpolation values (low bit rate), but still hangs for the low ones. I'm quite puzzled now, it seems that lock() - unlock() gets stuck when there's too much flow going on. cheers, Veljko 2010/2/14 Veljko Pejovic : > Hi, > > I have a similar problem in my code. > I modified benchmark_tx.py from gnuradio-examples/ofdm and ofdm.py > from blks2impl so that I can change the number of active subcarriers > on fly. > > In the packet sending loop of benchmark_tx I periodically do the following: > > lock the top block (tb.lock()), call a function in ofdm.py which > disconnects the blocks within ofdm_mod: > > self.disconnect((self._pkt_input, 0), (self.preambles, 0)) > self.disconnect((self._pkt_input, 1), (self.preambles, 1)) > self.disconnect(self.preambles, self.ifft, self.cp_adder, > self.scale, self) > > rebuild them according to the parameters that I pass from > benchmark_tx and reconnects them. After that I call tb.unlock(). > > What happens is that sometimes it works, and sometimes it gets stuck > (some sort of deadlock I assume). I tried swapping lock-unlock with > stop-wait-start and that results in similar behavior (it actually goes > a few iterations further on average). I also tried moving lock-unlock > to the actual function in ofdm_mod, but that didn't change anything. > > Any suggestions? > > Thanks, > > > Veljko > > 2010/2/8 Eric Blossom : >> On Sun, Jan 24, 2010 at 02:21:12PM +0100, Carlo Donato Lecce wrote: >>> >>> Hello all, >>> >>> >>> I seem that using transmit_path and receive_path the reconfigure >>> of flow graph is bad. >>> The following code hung after the call of unlock. >>> >>> I think that there are a bugs in the transmit_path because >>> using a gr.null_source insted of transmit_path the program not hangs. >>> >>> Thanks, >>> >>> >>> Carlo. >> >> Carlo, >> >> It looks like you're missing the calls to connect that would have your >> top block know about the nested blocks. >> >> See below. >> >> Eric >> >> >>> from gnuradio import gr, gru, modulation_utils >>> from gnuradio import eng_notation >>> from gnuradio.eng_option import eng_option >>> from optparse import OptionParser >>> >>> import random, time, struct, sys, math >>> >>> # from current dir >>> from transmit_path import transmit_path >>> from receive_path import receive_path >>> >>> >>> class h_block(gr.hier_block2): >>> def __init__(self): >>> gr.hier_block2.__init__(self, "hello", gr.io_signature(0, 0, 0), >>> gr.io_signature(0, 0, 0)) >>> >>> class top_block(gr.top_block): >>> def __init__(self, mod_class, demod_class, rx_callback, options): >>> gr.top_block.__init__(self) >>> >>> self.txpath = transmit_path(mod_class, options) >>> self.rxpath = receive_path(demod_class, rx_callback, options) >> >> Try adding: >> >> self.connect(self.txpath) >> self.connect(self.rxpath) >> >> here. See also tunnel.py >> >> >>> self.source = gr.null_source(gr.sizeof_gr_complex) >>> self.sink = gr.null_sink(gr.sizeof_gr_complex) >>> >>> >>> self.connect(self.txpath, self.sink) >>> # self.connect(self.source2, self.sink2) >>> >>> def reconfigure(self): >>> self.lock() >>> self.disconnect(self.txpath, self.sink) >>> self.sink2 = gr.null_sink(gr.sizeof_gr_complex) >>> self.connect(self.txpath, self.sink2) >>> self.unlock() >> >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] modifying how-to-write-a-block 3.2.2
Hello all, I have been spending a considerable amount of time to modify the how- to-write-a-block to compile and make my own, different name, module. While changing the code withing the howto_square_ff.cc is a simple solution, it is unfulfilling. Sadly, I think I tried to make big changes in the code structure and a simple find/replace of Makefile.am and howto.i (as well as renaming the files) and other obvious files, does not suffice. I tried to look for instructions on exactly which files and lines to modify, but there seem to be none for the structure provided in the example for version 3.2.2. There are several places (Dawei Shen's tutorial amongst others) that explain the modification for a boilerplate model for, I believe, version 3.02 and before, but nothing for the newer version where the Makefiles.am in the src/lib directory is quite different. I will continue to hack on the current version, and keep notes so that so I can report what and how it works, but if anyone knows of an existing enumeration of steps on how to take the boilerplate provided by the how-to-write-a-block ver 3.2.2 and modify it to say a module name toneDetect, I will appreciate it. Regards, Affan. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Building USRP2 FPGA on ISE 11.4
I was able to place and route the design on ISE 11.4 using a 'high' effort and ensuring that the speed grade selected is -5 (that really made a difference of about 20MHz in the speed of the final design). However, when it comes time to generate the bitstream, it complains about the -g Match_cycle:Auto and insists on changing it to -g Match_cycle:NoWait, and then throws an error, with no information. Does this ring a bell for anyone? I haven't seen it before. Thanks, TMB ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] modifying how-to-write-a-block 3.2.2
Hi Affan, Why kind of problems have you been having? I did quite a bit of productive work with version 3.2.2 simply by creating a new set of "how_to" routines in addition to the examples. Are you having compile problems? Run-time problems? I remember having lots of run-time difficulties because I think the how-to gets put into /usr/local/lib by default and the usual gnuradio-3.2.2 stuff goes into /usr/lib (or vice versa, I forget) and you need to make sure both the regular stuff and the how-to stuff is configured with the --prefix=/usr option. -Tom On Mon, Feb 15, 2010 at 7:16 PM, Affan Syed wrote: > Hello all, > > I have been spending a considerable amount of time to modify the > how-to-write-a-block to compile and make my own, different name, module. > While changing the code withing the howto_square_ff.cc is a simple solution, > it is unfulfilling. > > Sadly, I think I tried to make big changes in the code structure and a > simple find/replace of Makefile.am and howto.i (as well as renaming the > files) and other obvious files, does not suffice. I tried to look for > instructions on exactly which files and lines to modify, but there seem to > be none for the structure provided in the example for version 3.2.2. There > are several places (Dawei Shen's tutorial amongst others) that explain the > modification for a boilerplate model for, I believe, version 3.02 and > before, but nothing for the newer version where the Makefiles.am in the > src/lib directory is quite different. > > I will continue to hack on the current version, and keep notes so that so I > can report what and how it works, but if anyone knows of an existing > enumeration of steps on how to take the boilerplate provided by the > how-to-write-a-block ver 3.2.2 and modify it to say a module name > toneDetect, I will appreciate it. > > Regards, > > Affan. > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Building USRP2 FPGA on ISE 11.4
Tracey- > I was able to place and route the design on ISE 11.4 using a 'high' effort > and ensuring that the speed grade selected is -5 (that really made a > difference of about 20MHz in the speed of the final design). However, when > it comes time to generate the bitstream, it complains about the -g > Match_cycle:Auto and insists on changing it to -g Match_cycle:NoWait, and > then throws an error, with no information. You didn't have to change any source files or the constraints file? No coregen errors? -Jeff ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Firmware / FPGA bitstream for USRP2 Rev 4
Hi all, I tried this the following on three machines with Gigabit interfaces, and got the same results: When I restrict the ethernet card to only advertise 1Gbps connections (ethtool -s eth0 advertise 0x020 or ox010), the link stays down. Therefore, each find_usprs call is not even sending any packet out. When I let it freely advertise anything, it settles for 10Mbps or 100Mbps, but the link is up and it actually sends packets out. After each packet is sent, the orange light on the ethernet interface of the USRP2 goes orange for a sec. But I still get no response from it! I have tried all possible pause combinations as well (autoneg = on/off, rx=on/off, tx=on/off), but I get the same results. I apologize again for sending so many (long) emails. Thanks, Omid On Sun, Feb 14, 2010 at 5:03 PM, Eric Blossom wrote: > On Sat, Feb 13, 2010 at 11:38:27PM -0600, Omid F wrote: > > Thanks Matt for the helpful suggestions. I apologize for the long back > and > > forths! I really appreciate your help. > > > > I checked the ethernet interface on two of my laptops. On both, I made > sure > > this is the setting: > > > > Pause parameters for eth0: > > Autonegotiate: on > > RX: on > > TX: on > > Actually what you want is > > Rx: on > Tx: off > > Eric > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] modifying how-to-write-a-block 3.2.2
Tom, most of my problems have to do with compilation i.e. my new block doesnt compile as somewhere there is a reference to the old how_to module structure. I didnt add any errors since I think I had attempted a very large change in one go (i.e. changed the code and module name and pared down from two classes to just one) and I can solve the problem by incrementally changing just one thing at a time. I still think I should be able solve this if I give it another 3-4 hrs (probably tomorrow) but was hoping to see if someone updated the howto that works for older versions. Affan On Feb 15, 2010, at 5:04 PM, Tom Gross wrote: Hi Affan, Why kind of problems have you been having? I did quite a bit of productive work with version 3.2.2 simply by creating a new set of "how_to" routines in addition to the examples. Are you having compile problems? Run-time problems? I remember having lots of run-time difficulties because I think the how-to gets put into /usr/local/lib by default and the usual gnuradio-3.2.2 stuff goes into /usr/lib (or vice versa, I forget) and you need to make sure both the regular stuff and the how-to stuff is configured with the --prefix=/usr option. -Tom On Mon, Feb 15, 2010 at 7:16 PM, Affan Syed wrote: Hello all, I have been spending a considerable amount of time to modify the how-to-write-a-block to compile and make my own, different name, module. While changing the code withing the howto_square_ff.cc is a simple solution, it is unfulfilling. Sadly, I think I tried to make big changes in the code structure and a simple find/replace of Makefile.am and howto.i (as well as renaming the files) and other obvious files, does not suffice. I tried to look for instructions on exactly which files and lines to modify, but there seem to be none for the structure provided in the example for version 3.2.2. There are several places (Dawei Shen's tutorial amongst others) that explain the modification for a boilerplate model for, I believe, version 3.02 and before, but nothing for the newer version where the Makefiles.am in the src/lib directory is quite different. I will continue to hack on the current version, and keep notes so that so I can report what and how it works, but if anyone knows of an existing enumeration of steps on how to take the boilerplate provided by the how-to-write-a-block ver 3.2.2 and modify it to say a module name toneDetect, I will appreciate it. Regards, Affan. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Building USRP2 FPGA on ISE 11.4
Nope, Nope, and Nope. I was rather shocked, things never go that well for me :) I pulled the u2_rev3 and just resolved my way through the source tree. I was not expecting it to generate cleanly. I did regenerate two cores as part of the process, dumped a couple of the generated .v files because they refused to resolve properly, but the first time through they regenerated and went right through place and route with no errors, and no timing issues like I had with it earlier (set to the -4 speed grade). I just havent been able to generate the bitstream, and I won't have a chance to do any testing til next week, if I do get it resolved. Tracey On Mon, Feb 15, 2010 at 6:52 PM, Jeff Brower wrote: > Tracey- > > > I was able to place and route the design on ISE 11.4 using a 'high' > effort > > and ensuring that the speed grade selected is -5 (that really made a > > difference of about 20MHz in the speed of the final design). However, > when > > it comes time to generate the bitstream, it complains about the -g > > Match_cycle:Auto and insists on changing it to -g Match_cycle:NoWait, > and > > then throws an error, with no information. > > You didn't have to change any source files or the constraints file? No > coregen errors? > > -Jeff > > -- Tracey Bernath 913-488-6284 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] modifying how-to-write-a-block 3.2.2
I guess what I'm saying is that I don't recall having any problems using the "howto" with 3.2.2. I understand your frustrations however. :-) On Mon, Feb 15, 2010 at 9:45 PM, Affan Syed wrote: > Tom, > most of my problems have to do with compilation i.e. my new block doesnt > compile as somewhere there is a reference to the old how_to module > structure. I didnt add any errors since I think I had attempted a very large > change in one go (i.e. changed the code and module name and pared down from > two classes to just one) and I can solve the problem by incrementally > changing just one thing at a time. I still think I should be able solve this > if I give it another 3-4 hrs (probably tomorrow) but was hoping to see if > someone updated the howto that works for older versions. > > Affan > On Feb 15, 2010, at 5:04 PM, Tom Gross wrote: > >> Hi Affan, >> >> Why kind of problems have you been having? I did quite a bit of >> productive work with version 3.2.2 simply by creating a new set of >> "how_to" routines in addition to the examples. >> >> Are you having compile problems? Run-time problems? I remember >> having lots of run-time difficulties because I think the how-to gets >> put into /usr/local/lib by default and the usual gnuradio-3.2.2 stuff >> goes into /usr/lib (or vice versa, I forget) and you need to make sure >> both the regular stuff and the how-to stuff is configured with the >> --prefix=/usr option. >> >> -Tom >> >> On Mon, Feb 15, 2010 at 7:16 PM, Affan Syed wrote: >>> >>> Hello all, >>> >>> I have been spending a considerable amount of time to modify the >>> how-to-write-a-block to compile and make my own, different name, module. >>> While changing the code withing the howto_square_ff.cc is a simple >>> solution, >>> it is unfulfilling. >>> >>> Sadly, I think I tried to make big changes in the code structure and a >>> simple find/replace of Makefile.am and howto.i (as well as renaming the >>> files) and other obvious files, does not suffice. I tried to look for >>> instructions on exactly which files and lines to modify, but there seem >>> to >>> be none for the structure provided in the example for version 3.2.2. >>> There >>> are several places (Dawei Shen's tutorial amongst others) that explain >>> the >>> modification for a boilerplate model for, I believe, version 3.02 and >>> before, but nothing for the newer version where the Makefiles.am in the >>> src/lib directory is quite different. >>> >>> I will continue to hack on the current version, and keep notes so that so >>> I >>> can report what and how it works, but if anyone knows of an existing >>> enumeration of steps on how to take the boilerplate provided by the >>> how-to-write-a-block ver 3.2.2 and modify it to say a module name >>> toneDetect, I will appreciate it. >>> >>> Regards, >>> >>> Affan. >>> >>> ___ >>> Discuss-gnuradio mailing list >>> Discuss-gnuradio@gnu.org >>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] modifying how-to-write-a-block 3.2.2
Hi Affan - Since you modified the how-to stuff to meet your needs, it'll be difficult for any of us to provide definitive assistance without seeing your code (I, personally, have very little free time this week until I get a presentation finished). That said, if you do succeed & come up with a set of notes on the process, I hope you decide to edit them into a wiki (GNU Radio's or some other) to help out others trying to do the same thing. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Receiver sensitivity/noise floor...
Hi All Does anybody have information on what the receiver sensitivity or noise floor is for the XCVR2450 boards with a USRP2. I need to know at what level a spurious signal from another source could cause noticeable interference to a desired signal. Regards Ian. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Building GNU Radio on the Beagle board
Hi; Sorry again but link is not working. I am unable to download it. Is it problem because of your ADSL ? You have a web site but may be openning project in Sourceforge.net can be usesful. Thanks On Mon, Feb 8, 2010 at 11:34 PM, Philip Balister wrote: > On 02/08/2010 04:29 PM, yerebakan wrote: > >> Hi; >> >> Sorry , but I am unable to reach get the files from "GNU radio sdk >> from philip at ... " (in given adress) is it http adress or do we have to >> request by mail ? >> > > Ask by email :) This is a very preliminary image atm, as you can tell from > my notes. The process is working for me though and I would appreciate some > testing. > > I'll send you the link in a minute, it is on my DSL line, so the download > speed is not great. > > Philip > > > >> Thanks >> >> On Wed, Feb 3, 2010 at 8:25 PM, Philip Balister >> wrote: >> >> From time to time people ask about building GNU Radio for the >>> Beagleboard. >>> In an attempt to make it easier for more people to work on this, I posted >>> some notes at: >>> >>> http://www.opensdr.com/node/17 >>> >>> describing how to build GNU Radio on the Beagleboard (obviously building >>> it >>> cross is much faster, but you need to be aware of some tricky bits). I >>> know >>> this is all a bit vague, but hopefully someone finds it useful :) >>> >>> If you have Beagle specific questions, please ask those on the >>> appropriate >>> list/irc channel. I'll be glad to respond to GNU Radio specific issues >>> here. >>> >>> Philip >>> >>> >>> ___ >>> Discuss-gnuradio mailing list >>> Discuss-gnuradio@gnu.org >>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >>> >> >> >> > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > Halid Ziya Yerebakan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
