You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use burst mode with hackrf and gnuradio. After having figured how to set the length tag of the soapy gnuradio driver I still cannot get the burst mode working.
I do see, that the burst mode related part of sink_impl.cc (GnuRadio) is getting called (because of an initial tPtG message), but the relevant flag SOAPY_SDR_END_BURST is not propagated to any place in the code of this repository where it could be used.
I see the flag put into the writeStream function, but the flag is only used within activate Stream. While activateStream is called from writeStream, the "flags" are not propagated since activateStream is only called indirectly via acquireWriteBuffer. The latter, however, has not parameter to propagate the flags.
Now I am asking where the error is: Is it in GnuRadios call sequence to SoapyHackRF or is it in the soapy driver?
The text was updated successfully, but these errors were encountered:
I am trying to use burst mode with hackrf and gnuradio. After having figured how to set the length tag of the soapy gnuradio driver I still cannot get the burst mode working.
I do see, that the burst mode related part of sink_impl.cc (GnuRadio) is getting called (because of an initial tPtG message), but the relevant flag SOAPY_SDR_END_BURST is not propagated to any place in the code of this repository where it could be used.
I see the flag put into the writeStream function, but the flag is only used within activate Stream. While activateStream is called from writeStream, the "flags" are not propagated since activateStream is only called indirectly via acquireWriteBuffer. The latter, however, has not parameter to propagate the flags.
Now I am asking where the error is: Is it in GnuRadios call sequence to SoapyHackRF or is it in the soapy driver?
The text was updated successfully, but these errors were encountered: