Re: [Discuss-gnuradio] The build-gnuradio install script fails for Ubuntu 15.04
:) 2015-04-30 23:45 GMT+01:00 Marcus D. Leech mle...@ripnet.com: On 04/30/2015 06:37 PM, Murray Thomson wrote: Hi, I've noticed that the script in http://gnuradio.org/redmine/projects/gnuradio/wiki/InstallingGRFromSource fails for Ubuntu 15.04. The fix is simple, just add version 15 in the line 509. I've attached the script with this change. Thanks, Murray ___ Discuss-gnuradio mailing listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio Well, Ubuntu 15.04 is less than a month old. Took me by surprise... ___ 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] benchmark_rx.py segmentation fault
Did you update GNU Radio *after* you updated UHD? If not, that's what you should do. http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the M On 30.04.2015 08:59, Richard Bell wrote: Hello, I'm using Ubuntu 14.04, gnuradio 3.7.8, USRP N210 and the latest UHD. Everything was recently (3 days ago) updated to newest versions and USRP's reflashed. I have custom flowgraphs that use the USRP N210's that work fine. I decided to play around with the benchmark_tx and benchmark_rx scripts to see what they could do, but I'm not able to receive anything because a segmentation fault crashes the benchmark_rx script as soon as I start the tx script. Even with the -v flag, I don't get any error output other then 'Segmentation fault (core dumped)'. Here is an example of the commands I use to start the scripts. I start the rx and then the tx. TX: *./benchmark_tx.py -v -f 10 -r 80 --args=addr=10.0.8.5 -A TX/RX --tx-gain=15* RX: *./benchmark_rx.py -v -f 10 -r 80 --args=addr=10.0.8.4 -A RX2 --rx-gain=15 * Am I doing something wrong on my end or is there a script issue? Thanks, Rich ___ 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] benchmark_rx.py segmentation fault
I use pybombs to update, which automatically updates UHD first and then GNU Radio. Rich On Fri, May 1, 2015 at 10:20 AM, Martin Braun martin.br...@ettus.com wrote: Did you update GNU Radio *after* you updated UHD? If not, that's what you should do. http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the M On 30.04.2015 08:59, Richard Bell wrote: Hello, I'm using Ubuntu 14.04, gnuradio 3.7.8, USRP N210 and the latest UHD. Everything was recently (3 days ago) updated to newest versions and USRP's reflashed. I have custom flowgraphs that use the USRP N210's that work fine. I decided to play around with the benchmark_tx and benchmark_rx scripts to see what they could do, but I'm not able to receive anything because a segmentation fault crashes the benchmark_rx script as soon as I start the tx script. Even with the -v flag, I don't get any error output other then 'Segmentation fault (core dumped)'. Here is an example of the commands I use to start the scripts. I start the rx and then the tx. TX: *./benchmark_tx.py -v -f 10 -r 80 --args=addr=10.0.8.5 -A TX/RX --tx-gain=15* RX: *./benchmark_rx.py -v -f 10 -r 80 --args=addr=10.0.8.4 -A RX2 --rx-gain=15 * Am I doing something wrong on my end or is there a script issue? Thanks, Rich ___ 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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GRC Feature Request
Hi Richard, we have an infinite list of GRC feature requests, and this sounds like it's already on there. What we're lacking is people working on the GUI side of things -- maybe this is something you want to contribute? Also, this isn't as easy at it sounds, as there's no 1:1 relationship between GRC blocks and source files. Also, people might not even have the sources on their computer. There's this: http://gnuradio.org/redmine/projects/gnuradio/wiki/GRCroadmap ...but I know it's not up to date. Sebastian is in charge of GRC development, and I'm not sure how he tracks efforts. Cheers, Martin On 30.04.2015 11:07, Richard Bell wrote: Hi all, In the gui config window that pops up when you double click a block in grc, in the documentation tab, two buttons that you can click that open up either the block.cc source file or the block.h source file. Takes confusion out of which source file you should look at or where to even look for beginners. I realize there are some logistics that would need to be handled, like python blocks or hier_blocks, but you get the idea. v/r, Rich ___ 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] GRC Feature Request
Martin and all developers, I realize you're overworked. My intent is not to come across demanding anything. I just make requests as I find myself wanting/needing a feature in my everyday use of the tool. There is no expectation that the feature will be implemented in any timely manner. This is open source after all. I hope to eventually have the skills needed to implement things like this to contribute back to the community. I'm not there yet at this time. I appreciate all the hardwork GNU Radio developers put in and commend you. It is a great tool and I enjoy using it and learning with it. v/r, Rich On Fri, May 1, 2015 at 10:17 AM, Martin Braun martin.br...@ettus.com wrote: Hi Richard, we have an infinite list of GRC feature requests, and this sounds like it's already on there. What we're lacking is people working on the GUI side of things -- maybe this is something you want to contribute? Also, this isn't as easy at it sounds, as there's no 1:1 relationship between GRC blocks and source files. Also, people might not even have the sources on their computer. There's this: http://gnuradio.org/redmine/projects/gnuradio/wiki/GRCroadmap ...but I know it's not up to date. Sebastian is in charge of GRC development, and I'm not sure how he tracks efforts. Cheers, Martin On 30.04.2015 11:07, Richard Bell wrote: Hi all, In the gui config window that pops up when you double click a block in grc, in the documentation tab, two buttons that you can click that open up either the block.cc source file or the block.h source file. Takes confusion out of which source file you should look at or where to even look for beginners. I realize there are some logistics that would need to be handled, like python blocks or hier_blocks, but you get the idea. v/r, Rich ___ 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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] benchmark_rx.py segmentation fault
I remember I had the same issue before when testing the benchmark. What I did to avoid the crash is to start the tx first, and then the rx. It seems that you are doing it in reverse order, which is reasonable but not working according to my test. On Fri, May 1, 2015 at 10:51 AM, Richard Bell richard.be...@gmail.com wrote: I forgot to mention that I also re-cloned pybombs before doing the update. So to be explicit, I deleted the target and pybombs directory. I then re-cloned pybombs and performed a new ./pybombs install gnuradio. This recognized I had all dependencies installed via rpm and only needed to remove and re-install uhd and gnuradio. It then did this. As I mentioned, my custom radio flowgraph is working on this updated system. v/r, Rich On Fri, May 1, 2015 at 10:46 AM, Richard Bell richard.be...@gmail.com wrote: I use pybombs to update, which automatically updates UHD first and then GNU Radio. Rich On Fri, May 1, 2015 at 10:20 AM, Martin Braun martin.br...@ettus.com wrote: Did you update GNU Radio *after* you updated UHD? If not, that's what you should do. http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the M On 30.04.2015 08:59, Richard Bell wrote: Hello, I'm using Ubuntu 14.04, gnuradio 3.7.8, USRP N210 and the latest UHD. Everything was recently (3 days ago) updated to newest versions and USRP's reflashed. I have custom flowgraphs that use the USRP N210's that work fine. I decided to play around with the benchmark_tx and benchmark_rx scripts to see what they could do, but I'm not able to receive anything because a segmentation fault crashes the benchmark_rx script as soon as I start the tx script. Even with the -v flag, I don't get any error output other then 'Segmentation fault (core dumped)'. Here is an example of the commands I use to start the scripts. I start the rx and then the tx. TX: *./benchmark_tx.py -v -f 10 -r 80 --args=addr=10.0.8.5 -A TX/RX --tx-gain=15* RX: *./benchmark_rx.py -v -f 10 -r 80 --args=addr=10.0.8.4 -A RX2 --rx-gain=15 * Am I doing something wrong on my end or is there a script issue? Thanks, Rich ___ 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 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] benchmark_rx.py segmentation fault
OK, then I have no clue. If you can present a stack trace here, someone might have a better idea. Cheers, Martin On 01.05.2015 10:51, Richard Bell wrote: I forgot to mention that I also re-cloned pybombs before doing the update. So to be explicit, I deleted the target and pybombs directory. I then re-cloned pybombs and performed a new ./pybombs install gnuradio. This recognized I had all dependencies installed via rpm and only needed to remove and re-install uhd and gnuradio. It then did this. As I mentioned, my custom radio flowgraph is working on this updated system. v/r, Rich On Fri, May 1, 2015 at 10:46 AM, Richard Bell richard.be...@gmail.com mailto:richard.be...@gmail.com wrote: I use pybombs to update, which automatically updates UHD first and then GNU Radio. Rich On Fri, May 1, 2015 at 10:20 AM, Martin Braun martin.br...@ettus.com mailto:martin.br...@ettus.com wrote: Did you update GNU Radio *after* you updated UHD? If not, that's what you should do. http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the M On 30.04.2015 08:59, Richard Bell wrote: Hello, I'm using Ubuntu 14.04, gnuradio 3.7.8, USRP N210 and the latest UHD. Everything was recently (3 days ago) updated to newest versions and USRP's reflashed. I have custom flowgraphs that use the USRP N210's that work fine. I decided to play around with the benchmark_tx and benchmark_rx scripts to see what they could do, but I'm not able to receive anything because a segmentation fault crashes the benchmark_rx script as soon as I start the tx script. Even with the -v flag, I don't get any error output other then 'Segmentation fault (core dumped)'. Here is an example of the commands I use to start the scripts. I start the rx and then the tx. TX: *./benchmark_tx.py -v -f 10 -r 80 --args=addr=10.0.8.5 -A TX/RX --tx-gain=15* RX: *./benchmark_rx.py -v -f 10 -r 80 --args=addr=10.0.8.4 -A RX2 --rx-gain=15 * Am I doing something wrong on my end or is there a script issue? Thanks, Rich ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org mailto:Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org mailto: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] benchmark_rx.py segmentation fault
I forgot to mention that I also re-cloned pybombs before doing the update. So to be explicit, I deleted the target and pybombs directory. I then re-cloned pybombs and performed a new ./pybombs install gnuradio. This recognized I had all dependencies installed via rpm and only needed to remove and re-install uhd and gnuradio. It then did this. As I mentioned, my custom radio flowgraph is working on this updated system. v/r, Rich On Fri, May 1, 2015 at 10:46 AM, Richard Bell richard.be...@gmail.com wrote: I use pybombs to update, which automatically updates UHD first and then GNU Radio. Rich On Fri, May 1, 2015 at 10:20 AM, Martin Braun martin.br...@ettus.com wrote: Did you update GNU Radio *after* you updated UHD? If not, that's what you should do. http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the M On 30.04.2015 08:59, Richard Bell wrote: Hello, I'm using Ubuntu 14.04, gnuradio 3.7.8, USRP N210 and the latest UHD. Everything was recently (3 days ago) updated to newest versions and USRP's reflashed. I have custom flowgraphs that use the USRP N210's that work fine. I decided to play around with the benchmark_tx and benchmark_rx scripts to see what they could do, but I'm not able to receive anything because a segmentation fault crashes the benchmark_rx script as soon as I start the tx script. Even with the -v flag, I don't get any error output other then 'Segmentation fault (core dumped)'. Here is an example of the commands I use to start the scripts. I start the rx and then the tx. TX: *./benchmark_tx.py -v -f 10 -r 80 --args=addr=10.0.8.5 -A TX/RX --tx-gain=15* RX: *./benchmark_rx.py -v -f 10 -r 80 --args=addr=10.0.8.4 -A RX2 --rx-gain=15 * Am I doing something wrong on my end or is there a script issue? Thanks, Rich ___ 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 mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
