Hello Kevin,
\
Are you using one of the default bitfiles?\
It looks to me like the issue might be caused by the fact that your Radio and
your PolConverter are connected to the Same SEP, namely SEP3.\
\
The RFNoC crossbar might not be able to find a valid route if source and
destination are the s
Hey Brian,
I do not know of any examples of the top of my head that use metadata for
higher CHDR_W’s.\
\
I suspect that on the Host side, 64bit is just the data type used because it is
the lowest common denominator for all CHDR_W’s. In the CHDR header , the
metadata is not counted in terms of b
Hi Brian,
Remote UDP streaming is currently only supported for the RX streaming
direction. TX Remote UDP streaming is currently not supported.
As far as I know, nothing has been announced regarding when TX Remote UDP
streaming might be added.
Regarding RFNoC Remote streaming, it should be as y
Hey,\
\
Have you tried using a single replay block?\
The replay block can be configured to have multiple ports that each can be
connected the radio.
For example the
[x410_X4_200_rfnoc_image_core.yaml](https://github.com/EttusResearch/uhd/blob/master/fpga/usrp3/top/x400/x410_X4_200_rfnoc_image_co
If you only need very simple downsampling/decimation, I think i saw a
[keep-one-in-n rfnoc block in the
repo](https://github.com/EttusResearch/uhd/tree/master/fpga/usrp3/lib/rfnoc/blocks/rfnoc_block_keep_one_in_n)
that only keeps every n-th sample. You might be able to use it, or at least
use i
Hi Kevin,\
\
As per the [RFNoC
specification](https://files.ettus.com/app_notes/RFNoC_Specification.pdf)
Section 2.2.2.1, if you are using bursts, only the first packet of each burst
is required to have a timestamp. All subsequent packets of the same burst do
not need to have a timestamp includ
Hi,\
\
How are you setting your clock/time source?\
\
If you are setting the clock/time source using the \`set_clock_source()\` or
\`set_time_source()\` function to set your external sources, you might want to
try setting these via the [device
arguments](https://uhd.readthedocs.io/en/latest/page
Hi,\
\
Some RFNoC blocks which process samples in in batches can require \`spp\` to be
set to the batch size or a multiple/divider of it.\
\
To my knowledge the updated FFT block is one of them. At least the [example
specifies that the SPP should evenly divide the FFT
size](https://github.com/Et
Sorry, I misread your question as PPS via GPIO instead of GPSDO as you
specified.\
\
As mentioned in my code example you can set the time_source to gpsdo instead of
external
I am not sure if you can get access to the actual internal PPS rising edge
coming from GPSDO, but what you might be able
anant.tripa...@technosci.com wrote:
> Pretty much what the title says, our goal is to sync the timestamps to the
> rising edge of the 1PPS signal such that they get reset exactly on the rising
> edge of the 1pps signal, and increment the count of a custom metadata tag, to
> the outgoing stream
Hi Kevin, \
have you tried giving your IP directory via the \`--include-dir\` argument of
the rfnoc_image_builder? That’s usually the way to include OOT modules.\
\
Or does your IP need to be generated first and you want this to be part of the
overall bitfile generation process?\
\
The rfnoc_imag
Hey Kevin,\
\
As far as I am aware, the FPGA has [a fixed MTU size of 8192
bytes](https://github.com/EttusResearch/uhd/blob/master/fpga/usrp3/top/x400/x4xx.sv#L334),
which equates to 2^10 words of CHDR_W 64.
The MTU size is distributed to all RFNoC blocks and as far as I know changing
this for
Hi Brian,\
\
I had to play around with the crossbar route matrix myself yet,\
but looking at the code it seems like [at least for transport adapters the
routes to themselves have to be included for route discovery
purposes](https://github.com/EttusResearch/uhd/blob/master/host/python/uhd/rfnoc_ut
Hi Kevin,\
\
As far as I know, the \`radio_\*_stb\` signals are strobe signals that are
coming from outside of the image_core from the RF Analog HW on the
daughterboards, signaling when the radio data can be transmitted/received.\
They can be understood as signals that are similar to tready signa
Hi David,\
\
there is an option of adding contraints via the block description yaml file by
specifying them in the constraints section.
For OOT blocks, you can find an example here on how this could be done:\
[Aurora OOT block description
file](https://github.com/EttusResearch/rfnoc-oot-blocks/b
15 matches
Mail list logo
