Hi Nives, The warning can be ignored. It is a known issue that I believe was recently fixed.
Regards, Michael On Mon, Jun 18, 2018 at 2:10 AM, Nives Novković <novkovic.ni...@gmail.com> wrote: > Hi everyone, > > Thank you for all your help. I followed EJ's advice on adding the 2nd FIFO > block, also Michael's for making the file sink unbuffered and now I am > receiving the whole file no matter the size. :) > > Another issue that now came is the overflow warning: > > > [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501; > UHD_4.0.0.rfnoc-devel-788-g1f8463cc > > [INFO] [X300] X300 initialization sequence... > > [INFO] [X300] Maximum frame size: 1472 bytes. > > [INFO] [X300] Radio 1x clock: 200 MHz > > [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: > 0xF1F0D00000000000) > > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) > > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1301 MB/s) > > [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) > > [WARNING] [0/Radio_0] [0/Radio_0] defines 2 input buffer sizes, but 1 > input ports > > [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001) > > [WARNING] [0/Radio_1] [0/Radio_1] defines 2 input buffer sizes, but 1 > input ports > > [WARNING] [DEVICE3] No block definition found, using default block > configuration for block with NOC ID: 0x8878D731BF9A51F9 > > [INFO] [0/Block_0] Initializing block control (NOC ID: 0x8878D731BF9A51F9) > > [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000) > > [INFO] [0/FFT_0] Initializing block control (NOC ID: 0xFF70000000000000) > > [INFO] [0/FIFO_0] Initializing block control (NOC ID: 0xF1F0000000000000) > > [INFO] [0/FIFO_1] Initializing block control (NOC ID: 0xF1F0000000000000) > > [INFO] [0/FIFO_2] Initializing block control (NOC ID: 0xF1F0000000000000) > > [WARNING] [RFNOC] Assuming max packet size for 0/FIFO_0 > > timeout on chan 0 > timeout on chan 0 > timeout on chan 0 > > Although I get the warning I still receive the whole file back. Any idea > on why it is coming up at all? > > Kind regards, > Nives > > čet, 14. lip 2018. u 19:01 Michael West <michael.w...@ettus.com> napisao > je: > >> There may also be an issue with buffered I/O and how the flowgraph is >> stopped. The kill flowgraph button in the main window of GRC is like >> hitting Ctrl-C. Try closing the empty window that pops up. You can also >> try making the file sink unbuffered and see if that makes a difference. >> >> Regards, >> Michael >> >> On Wed, Jun 13, 2018 at 2:34 PM, Martin Braun <martin.br...@ettus.com> >> wrote: >> >>> I would expect it grow indefinitely, but it might slow down after 1.2 >>> MB. If repeat is on, expect lots of data. >>> >>> The 106 bytes vs. 64 bytes is more interesting. I don't see why, but >>> maybe somewhere the last 42 bytes are getting stuck. It might even be in >>> GNU Radio. >>> >>> Try a file that's a multiple of your SPP value, and see what happens >>> then (with repeat set to off). >>> >>> -- m >>> >>> >>> On 06/12/2018 01:37 AM, Nives Novković via USRP-users wrote: >>> > Hi Michael, >>> > >>> > Thank you for your answer. I am sending attached screenshot of the >>> > flowgraph and the console. I saw that if I modify the File Source block >>> > option repeat to "No" I receive only 64 bytes of a file that is 106 >>> > bytes large. If I set it to "Yes" then the content of the sent file >>> will >>> > repeat itself until it fills up 1.2MB on the receiving end. >>> > >>> > Also I tried using Head block but that only helps if I want to send a >>> > file that is smaller than 1.2MB. >>> > >>> > >>> > uto, 12. lip 2018. u 01:57 Michael West <michael.w...@ettus.com >>> > <mailto:michael.w...@ettus.com>> napisao je: >>> > >>> > Hi Nives, >>> > >>> > It is difficult to help without more information. If you share the >>> > flowgraph and console output, people on the list might be able to >>> > help more. >>> > >>> > Regards, >>> > Michael >>> > >>> > On Mon, Jun 11, 2018 at 1:01 AM, Nives Novković via USRP-users >>> > <usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> >>> wrote: >>> > >>> > Hi everyone, >>> > >>> > I am starting to familiarize myself with GNU radio and RFNoC. >>> > First thing I tried is simply to send a file to X310 using GNU >>> > radio and receive it back unchanged. For that I used blocks - >>> > File Source, Throttle, RFNoC: FIFO and File Sink. But no matter >>> > what size the file I send, I always receive 1.2MB. Even if my >>> > sent file is smaller than that it just multiplies the file >>> > content until it reaches 1.2MB. Do you have any idea what could >>> > be the problem? >>> > >>> > Kind regards, >>> > Nives >>> > >>> > _______________________________________________ >>> > USRP-users mailing list >>> > USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com> >>> > http://lists.ettus.com/mailman/listinfo/usrp-users_ >>> lists.ettus.com >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > USRP-users mailing list >>> > USRP-users@lists.ettus.com >>> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > >>> >>> >>
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
