At this time we have decided on a slight design change which makes it so that I no longer NEED gnuradio, therefore i am going to build the latest UHD code and rewrite my code using only UHD. Hopefully these errors will go away by doing this.
Please let me know if anyone has any further information, ideas, or solutions. Thanks. ----------------------------- Jacob Knoles On Mon, Jul 9, 2018 at 1:16 PM Jacob Knoles <knole...@gmail.com> wrote: > I've attached the cpp files that I have written for the USRP. Some of the > other functions defined in the hpp file are implemented in other files that > I have not included as they are not relevant. > > I can't necessarily speak for what Windows may or may not be doing because > "Windows", but for the housekeeping, I think I am doing that fine, ( see > end_tx function in n_usrp_impl.cpp ) when I Stop the flowgraph, wait for it > to finish then reset it to clear the memory. > > Also to reiterate these errors occur when using GNURadio python and the > companion to create the same code. > > Thanks for the help. > ----------------------------- > Jacob Knoles > > > > On Mon, Jul 9, 2018 at 12:38 PM Marcus D. Leech <mle...@ripnet.com> wrote: > >> On 07/09/2018 02:00 PM, Jacob Knoles wrote: >> > When using GNURadio Companion, they only appear when closing the >> > flowgraph. On my application, which uses the same gnuradio code >> > directly in c++ multiple times ( creates a usrp, then a flowgraph that >> > uses it, stops the flowgraph, then starts another after a few seconds) >> > I see the errors at the end of the first, then during streaming on all >> > subsequent flowgraphs. >> > >> > Occasionally I am getting a IOError: no response packet AssertionError >> > when I start streaming (typically after a couple of other stream >> > instances) and it causes my entire application to hang. >> > >> > ----------------------------- >> > Jacob Knoles >> > >> The issue may be twofold: >> >> (A) When windows shuts-down a socket, it may do so in a way that is >> "dirty" from UHD's perspective >> >> (B) The correct housekeeping is probably not being done by your app to >> deal with flow-graph shutdown and restart, leading to "dangling" >> socket descriptors and the like. >> >> If you could post the relevant parts of your code, or reduce it to the >> minimum that shows the issue and post that, it would help us >> decide whether this is a bug in UHD, or you're just using it >> improperly. >> >> >>
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
