Hi Jonathon, Thank you for replying back, I have watched both videos RFNoC 3 and 4 and based on them along with the UHD 4 guide, I noticed that the DmaFIFO was used in some cases.
For instance, based on the video RFNoC 3, in the fosphor demo with 100M Rate, DmaFIFO and RFNoC FIFO blocks were used, also in your gain example you used RFNoC: FIFO block. In our case, using UHD 4 with ubuntu 20.04 when we run the benchmark, based on the FPGA default image (there is no DmaFIFO), we noticed that there are several U, D and Os. So I decided to tune the system following the USRP tips and tricks guide, the system improved but still a handful of Us in 60 seconds 100Msps both channels in x310. On the other hand, last year I used the same x310 for 5G base station with "*ubuntu 16.04 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.15.0.HEAD-0-gaea0e2de* *[00:00:00.000002] Creating the usrp device ..*.." and tuned based on the USRP tricks and tips guide. I could run the benchmark for 600 seconds 100MSPS 2 channels with no issues using the default image which for that UHD version it had DmaFIFO. For our project we want to achieve 100Msps in a loopback mode with the host in the middle but we can not afford losing data. What do you think would be our best approach, going back to 16.04 OR keep using the 20.04 and add the DmaFIFO which might help when running the benchmark at 100MSPS loopback mode? We still need to add our own RFNoC block. Thanks again. JC On Thu, Mar 25, 2021 at 12:55 AM Jonathon Pendlum < [email protected]> wrote: > Hi Julian, > > The DmaFIFO block, which I believe is now called axi_ram_fifo in RFNoC 4, > does not have GNU Radio support. There is an effort to add support for > several blocks missing from GNU Radio, but I'm not sure if axi_ram_fifo > will be included in that effort. If it were available, can you share how > you were going to use it? > > Jonathon > > On Fri, Mar 19, 2021 at 4:48 PM <[email protected]> wrote: > >> hi all, >> >> I am trying to add DmaFIFO block following UHD 4 Getting started guide in >> the same way the FFT block was added, but when looking into gr-ettus/grc/ >> folder, I did not find any ettus_rfnoc_dmaFIFO yaml file like the rest of >> default blocks.. >> >> This is what I found in /usr/local/share/… and did not see any rfnoc >> DmaFIFO block. >> >> >> -rw-r--r-- 1 root root 166 Mar 2 14:58 ettus_fpga_clk.domain.yml >> >> -rw-r--r-- 1 root root 171 Mar 2 14:58 ettus_fpga_ctrl.domain.yml >> >> -rw-r--r-- 1 root root 168 Mar 2 14:58 ettus_fpga_data.domain.yml >> >> -rw-r--r-- 1 root root 618 Mar 2 14:58 ettus_fpga_ddc.block.yml >> >> -rw-r--r-- 1 root root 617 Mar 2 14:58 ettus_fpga_duc.block.yml >> >> -rw-r--r-- 1 root root 131 Mar 2 14:58 ettus_fpga_fft.block.yml >> >> -rw-r--r-- 1 root root 200 Mar 2 14:58 ettus_fpga_io_ctrl_port.domain.yml >> >> -rw-r--r-- 1 root root 181 Mar 2 14:58 ettus_fpga_io_radio.domain.yml >> >> -rw-r--r-- 1 root root 205 Mar 2 14:58 >> ettus_fpga_io_time_keeper.domain.yml >> >> -rw-r--r-- 1 root root 820 Mar 2 14:58 ettus_fpga_radio.block.yml >> >> -rw-r--r-- 1 root root 811 Mar 2 14:58 ettus_fpga_sep.block.yml >> >> -rw-r--r-- 1 root root 663 Mar 2 14:58 ettus_fpga_x310.block.yml >> >> -rw-r--r-- 1 root root 1056 Mar 2 14:58 ettus_rfnoc_ddc.block.yml >> >> -rw-r--r-- 1 root root 1022 Mar 9 13:36 ettus_rfnoc_duc.block.yml >> >> -rw-r--r-- 1 root root 2174 Mar 2 14:58 ettus_rfnoc_fft.block.yml >> >> -rw-r--r-- 1 root root 3990 Mar 2 14:58 ettus_rfnoc_fosphor.block.yml >> >> -rw-r--r-- 1 root root 4842 Mar 2 14:58 ettus_rfnoc_graph.block.yml >> >> -rw-r--r-- 1 root root 1950 Mar 2 14:58 ettus_rfnoc_rx_radio.block.yml >> >> -rw-r--r-- 1 root root 1266 Mar 2 14:58 ettus_rfnoc_rx_streamer.block.yml >> >> -rw-r--r-- 1 root root 1580 Mar 2 14:58 ettus_rfnoc_tx_radio.block.yml >> >> -rw-r--r-- 1 root root 1187 Mar 2 14:58 ettus_rfnoc_tx_streamer.block.yml >> >> -rw-r--r-- 1 root root 675 Mar 2 14:58 ettus.tree.yml >> >> >> I wonder if I am missing a step to make the DmaFIFO works with gnuradio >> like the FFT block example. >> >> >> Thanks >> _______________________________________________ >> USRP-users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
