[Discuss-gnuradio] Hierarchical blocks (arbitrary or variable numbers of inputs or outputs not supported)
Hello, I am trying to create a hierarchical block with a variable number of outputs, but I get this error: "RuntimeError: Hierarchical blocks do not yet support arbitrary or variable numbers of inputs or outputs" This appears to be a known issue [1], and I'm wondering what the best work around is. I think I can simply create an IO Signature with the maximum possible outputs I will need, and then connect a null source to all of the outputs I'm not intending to use. Is that a good idea? Thanks, Orin [1] https://lists.gnu.org/archive/html/discuss-gnuradio/2009-04/msg00011.html ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gr-bluetooth
Hello all, I've updated the gr-bluetooth [1] code to be compatible with GNU Radio 3.7. I'm trying to use it, but there's a segmentation fault that I need to figure out. Has anyone done anything with gr-bluetooth recently? Does anyone know if the current version of the code is even functional with GNU Radio 3.6? Were there changes in GNU Radio between 3.6 and 3.7 that would cause this issue to appear? My specific issue is outlined below. I have encountered a segmentation fault issue in the gr::bluetooth::multi_block code (which all the other gr-bluetooth blocks use) that did not appear while running the included QA code (though I'm not sure how reliable the test code was). I've spent the past couple days trying to track down with GDB what exactly is going wrong, so that I can fix it (the code looks fine to me, nothing is standing out as a big issue). From what I've gathered so far, it appears the issue is with "gr_vector_void_star& out", an input to multi_block::channel_samples(). I don't have a lot of experience with debugging, so if anyone has any suggestions about what to look for when tracking down segmentation faults (my understanding is that memory is being accessed which should not be accessed by the process), I would appreciate them. Best, Orin [1] https://github.com/greatscottgadgets/gr-bluetooth ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gr-bluetooth
Hello all, I've updated the gr-bluetooth [1] code to be compatible with GNU Radio 3.7. I'm trying to use it, but there's a segmentation fault that I need to figure out. Has anyone done anything with gr-bluetooth recently? Does anyone know if the current version of the code is even functional with GNU Radio 3.6? Were there changes in GNU Radio between 3.6 and 3.7 that would cause this issue to appear? My specific issue is outlined below. I have encountered a segmentation fault issue in the gr::bluetooth::multi_block code (which all the other gr-bluetooth blocks use) that did not appear while running the included QA code (though I'm not sure how reliable the test code was). I've spent the past couple days trying to track down with GDB what exactly is going wrong, so that I can fix it (the code looks fine to me, nothing is standing out as a big issue). From what I've gathered so far, it appears the issue is with "gr_vector_void_star& out", an input to multi_block::channel_samples(). I don't have a lot of experience with debugging, so if anyone has any suggestions about what to look for when tracking down segmentation faults (my understanding is that memory is being accessed which should not be accessed by the process), I would appreciate them. Best, Orin [1] https://github.com/greatscottgadgets/gr-bluetooth ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Getting overflows at 50 Msps (not sure why)
I appreciate the suggestions I received. It turns out that I was able to run GNU Radio with realtime priority, and that solved my overflow issues. I am now able to run flowgraphs that actually do things without getting overflows all the time. Thanks, Orin Lincoln On 06/04/2014 05:16 PM, Orin Lincoln wrote: Hello, I am trying to get samples from a B200 at 50 Msps into GNU Radio. The UHD benchmark_rate tool receives at 50 Msps without any overflows detected. My GNU Radio flowgraph is simply a USRP source connected to a null sink, and I'm still getting overflows. I've tried expanding the min_output_buffer for the USRP source, but that doesn't seem to help. I really don't know what is causing the problem. Any suggestions about what I should try? Thank you, Orin Lincoln ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Getting overflows at 50 Msps (not sure why)
Hello, I am trying to get samples from a B200 at 50 Msps into GNU Radio. The UHD benchmark_rate tool receives at 50 Msps without any overflows detected. My GNU Radio flowgraph is simply a USRP source connected to a null sink, and I'm still getting overflows. I've tried expanding the min_output_buffer for the USRP source, but that doesn't seem to help. I really don't know what is causing the problem. Any suggestions about what I should try? Thank you, Orin Lincoln ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
