Re: AW: Struggling with 3.10 OOT Module Porting: AttributeError: module has no attribute
Hi Luca, On 12/09/2022 17.15, Bachmaier, Luca wrote: > Re-installing my module gave me this cmake error: > > > > CMake Error at lib/CMakeLists.txt … Target > “gnuradio-myModule” links to: gnuradio::gnuradio-fec but the target was not > found. > > > > I was able to solve this by removing the gnuradio:: qualifier from > gnuradio-fec and gnuradio-analog. For some reason, only gnuradio-fec but not > gnuradio::gnuradio-fec is known. Could this be an unintended bug? Under Gnu > Radio 3.8.5 gnuradio::gnuradio-fec was able to be found. Yes, sounds like a bug. How did you install GNU Radio 3.10.3.0 on Debina 11 (bullseye)? Can you provide a minimal, reproducible example? > But right now I’m struggling with a new problem that I’m unable to solve: > > Calling import myModule_python in gr-myModule/build/python/myModule/bindings/ > throws a segmentation fault which gets traced back to > /usr/local/lib/python3.10/dist-packages/gnuradio/gr/__init__.py Run it trough gdb and take a backtrace. gdb -ex run --args python3 flowgraph.py (gdb) bt Regards, Vasil
Referring to a block by a specific name
Hi, I have some python snippets within the GRC that refer to certain blocks. However, the GRC generated names can be quite unintuitive (like blocks_stream_to_vector_1_0 etc.) . I was wondering whether it is possible to refer to certain blocks by user-defined names. I understand that there is an alias option in each block's GUI that corresponds to a set_block_alias() call in the top_block python script. Apparently there is a block registry ( https://github.com/gnuradio/gnuradio/blob/main/gnuradio-runtime/lib/block_registry.cc) that allows you lookups by alias but I could not figure out how to do that in python. What is the recommended approach for my scenario? Any help would be much appreciated. Best regards, T.K.
Re: Referring to a block by a specific name
Hi T.K. First you have enable the "Show All Block IDs" in GRC, then you can change the ID of the block to whatever you want it to be. In the snippet, then just refer to the block as self.blockname Hope this helps. Josh On Wed, Sep 14, 2022 at 1:08 PM Temir Karakurum wrote: > Hi, > > I have some python snippets within the GRC that refer to certain blocks. > However, the GRC generated names can be quite unintuitive (like > blocks_stream_to_vector_1_0 etc.) . I was wondering whether it is possible > to refer to certain blocks by user-defined names. > > I understand that there is an alias option in each block's GUI that > corresponds to a set_block_alias() call in the top_block python script. > Apparently there is a block registry ( > https://github.com/gnuradio/gnuradio/blob/main/gnuradio-runtime/lib/block_registry.cc) > that allows you lookups by alias but I could not figure out how to do that > in python. > > What is the recommended approach for my scenario? Any help would be much > appreciated. > > Best regards, > T.K. > > >
UHD 4.3.0.0 released!
UHD 4.3.0.0 is now available [1]! This release includes: * Extension framework support * FPGA builds using Xilinx Vivado 2021.1 (B2xx, E3xx, N3xx, X3xx, and X4xx devices) * Bug fixes and improvements for USRP devices. See the changelog. [1] We'd like to thank all the USRP users that have filed issues or directly contributed to UHD and meta-ettus. You contributions have helped the continued improvement of UHD. As always, please file issues to our GitHub repo [2], by posting in the USRP-users mailing list, or contacting supp...@ettus.com. Thanks! Steven [1] https://github.com/EttusResearch/uhd/releases/tag/v4.3.0.0 [2] https://github.com/EttusResearch/uhd/issues/