Cool!
I'll point out that your new build actually got past the old failure point
you noted before, which was immediately after attempting to interact with
the SplitStream RFNOC block!
```
[INFO] [0/SplitStream_0] Initializing block control (NOC ID:
0x5757)
[ERROR] [UHD] Exception caug
I also haven't tested to see if this is a gr-ettus limitation or a UHD
limitation.
On Thu, Nov 14, 2019 at 3:04 PM Nick Foster wrote:
> You can't have heterogenous output destinations on RFNoC blocks -- i.e.,
> you can't send one output to the host and one output to another RFNoC block.
>
> I'm
You can't have heterogenous output destinations on RFNoC blocks -- i.e.,
you can't send one output to the host and one output to another RFNoC block.
I'm not sure why this limitation exists as there is no architectural reason
I can see.
Nick
On Thu, Nov 14, 2019 at 12:35 PM Jonathan Lockhart
wr
Greetings Brian,
Update: the noc_block_split_stream does work in the radio. However, it has
to be going to another hardware component first, like a FIFO, before it can
be passed to software blocks on the arm or the ZMQ to port to a host
machine. It was very interesting. I know in one of the troubl
Greetings Brian,
I was having some issues with the build process, as the build script
couldn't find the gain.v block file even though I was pointing the script
to it. I saw that ejk github has some .inc files, so I added those and it
seemed to clear up the issue. *crosses fingers* The bit file was
