Ah, ok. Multiple problems producing the same error, but ultimately the last one
was that I had fat fingered my device to 1 instead of 0 at some point, so the
real problem was between the chair and keyboard. Now at least that part is
working, my next hurdle is I’m getting “Bad CHDR header” errors
I’m doing more or less the same thing you are and trying to figure out a
standard way to port the existing blocks over. Rfnocmodtool is working but I’m
still not there with a straightforward process. I spent the better part of the
week last week trying to build up a siggen block and there are se
After poking around for awhile, I am starting to believe this is not due to my
omission. Out of all the blocks, split stream was the only one that did not
have a “split_stream_block_control_python.hpp” file. So I created that, added
the entry to pyuhd.cpp, and recompiled uhd and gr-ettus. That d
Nevermind, I see that this is outlined in the RFNoC 4 migration guide. Not sure
what I missed, however.
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
Just to pile on to this, I’ve attempted to make a grc block for split stream.
I’ve copied the structure of DDC and everything appears to compile and cross
compile just fine for my e320. I used image builder to put a split stream block
on my fpga and verified its existence with the probe command.
Hey Jonathan,
I’m starting the process of expanding gr-Ettus to include most (if not all) of
the existing blocks in the library. My thought was that I could use “gr_modtool
add” to create the basic block structure inside of gr-ettus then go ahead
creating the impl and header files to reflect the
We would probably vote for gr-ettus support for the following, in more or less
this order of preference: Split_stream, fir, replay, keep_one_in_n.
thx rb
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-u
Is there some particular RFNOc block that you’d like a gr-Ettus mapping for?
Sent from my iPhone
> On Jul 1, 2021, at 6:52 PM, Paul Atreides wrote:
>
> I’ve had a lot of success adding blocks using the Ettus tools like
> rfnoc_modtool. Have you tried that?
>
>
>
>
>>> On Jul 1, 2021, at 1
I’ve had a lot of success adding blocks using the Ettus tools like
rfnoc_modtool. Have you tried that?
> On Jul 1, 2021, at 10:32, rbl...@swri.org wrote:
>
>
> Thanks for that.
>
> Not a lot to work with there- too bad.
>
> thx
>
> rb
>
> ___
Thanks for that.
Not a lot to work with there- too bad.
thx
rb
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
Looking at my gnuradio screen, the available RFNoC blocks under gr-ettus are:
DDC, DUC, FFT, Fospphor, RX Radio, RX Streamer, TX Radio, TX Streamer.
___
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le..
Thanks Johnathon, that is very helpful. Can you please also state the list of
blocks that currently have gr-ettus support?We would really like to know
what we should be looking for in current UHD/gnuradio builds.
___
USRP-users mailing list -- usrp
Hi,
While all the blocks in the KB article are available for UHD apps, not all
of them have GNU Radio / gr-ettus support. The eventual goal is to port
most of the missing blocks, although I don't have a timeline on when that
will happen.
Jonathon
On Wed, Jun 30, 2021, 10:26 wrote:
> My underst
My understanding is that the currently available in-tree blocks does not match
the list in the reference that you point to. FOr instance, the “replay” block
shown in that list is not available. I’m not sure that siggen is available
either.
___
USRP-u
On 06/29/2021 06:01 PM, rbl...@swri.org wrote:
Request for a sanity check- I’m in the process of building UHD 4-
What In-tree ettus RFNoc blocks are actually currently available in
UHD4? I’m aware that it is less than the list of blocks in the Ettus
“knowlege base” note on RFnoc and UHD4, and
15 matches
Mail list logo
