I believe RFNoC tries to flush any partially transmitted packets out of blocks during initialization before resetting them. The idea is to get rid of any leftover data that might still be in the data pipes. I think a timeout means the noc_shell never saw the end of the last packet before the timeout. I usually see this warning if I stopped the previous session abruptly without properly stopping the data transfer.
I think you'll see this warning if your block stops data transfer mid-packet. Then, on the next session, it can't finish the packet it started on the previous session. Or something like that. It's probably OK to ignore if your block uses the resets coming out of the noc_shell to reset everything. Wade On Mon, Jan 25, 2021 at 7:28 PM Rob Kossler via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi, > Using RFNOC 4.0 with a few of my custom blocks, I get the following > warning at UHD startup (after having run it at least once before): > > [WARNING] [RFNOC::GRAPH] One or more blocks timed out during flush! > > I'm confident it is something that I'm doing incorrectly with my block, > but I'm wondering if anyone can comment on what causes this and / or what > my block should be doing to avoid it. > > Rob > _______________________________________________ > 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
