0175c2e84e
On rad1o, the UI update could block this loop from running for long enough that it could stall in a state where neither of the conditions was met. Fix this by removing the 'phase' variable, in favour of a counter tracking the number of bytes that have been scheduled for USB transfer. Whenever there are enough bytes to schedule the next transfer, do so. Meanwhile, the M0 count is prevented from wrapping around and clobbering data not yet sent, because the M0 code monitors the m4_count variable which is updated as each transfer completes.
HackRF
This repository contains hardware designs and software for HackRF, a low cost, open source Software Defined Radio platform.
(photo by fd0 from https://github.com/fd0/hackrf-one-pictures)
principal author: Michael Ossmann mike@ossmann.com
Information on HackRF and purchasing HackRF: https://greatscottgadgets.com/hackrf/
Documentation
Documentation for HackRF can be viewed on Read the Docs. The raw documenation files for HackRF are in the docs folder in this repository and can be built locally by installing Sphinx Docs and running make html. Documentation changes can be submitted through pull request and suggestions can be made as GitHub issues.
Getting Help
Before asking for help with HackRF, check to see if your question is listed in the FAQ.
For assistance with HackRF general use or development, please look at the issues on the GitHub project. This is the preferred place to ask questions so that others may locate the answer to your question in the future.
We invite you to join our community discussions on Discord. Note that while technical support requests are welcome here, we do not have support staff on duty at all times. Be sure to also submit an issue on GitHub if you've found a bug or if you want to ensure that your request will be tracked and not overlooked.
If you wish to see past discussions and questions about HackRF, you may also view the mailing list archives.
GitHub issues on this repository that are labelled "technical support" by Great Scott Gadgets employees can expect a response time of two weeks. We currently do not have expected response times for other GitHub issues or pull requests for this repository.