|Subject:||Re: [Discuss-gnuradio] gr-ettus and GNU radio v3.8|
|Date:||Wed, 3 Jul 2019 10:20:33 +0000|
I got a step further. The rfnoc domain for grc can be defined by a file rfnoc.domain.yml.
Now I can connect the module and generate a Python file from the flowgraph.
The connections still do not work at run time, though , see below.
I have defined 'connect:' and 'cpp_connect:' in rfnoc.domain.yml, but this definitions have no effect since this file is not read at run time and not included in
Thanks and best regards,
Traceback (most recent call last):
Von: USRP-users <address@hidden> im Auftrag von Erik Heinz via USRP-users <address@hidden>
Gesendet: Freitag, 28. Juni 2019 18:12
An: address@hidden; address@hidden
Betreff: [USRP-users] gr-ettus and GNU radio v3.8
Have there been any efforts yet to port gr-ettus to the gnuradio master branch?
I made some trials today with gr-ettus under gnuradio-master and at least was able to compile and install it (except for fosphor which seems to need Qt4).
Automatic conversion of the grc xml files to the yml format was not possible, so I converted one by hand (uhd_rfnoc_dma_fifo).
I got so far that the block shows up in grc and most error messages went away.
There are still errors, however, about 'Domain key "rfnoc" is not registered' for the input and output ports. This is probably the reason as well why I cannot connect anything to this block (red arrows).
Any ideas? How do I register the rfnoc domain? Are there any serious reasons preventing the rfnoc blocks from working under v3.8?
|[Prev in Thread]||Current Thread||[Next in Thread]|