* Document & comment code
* document functions & add pages for groups
* Run clang-format
* Fix most review change requests
* Fix typos, add information on using multiple Opera Cake boards
* Update documentation
* Changes requested by @Straithe
- update project brief
- set paper type to letter
- move doxyfile
* Changes requested by @martinling
Excluding the USB API versioning
* Remove incomplete USB version info
The required versions were only noted at a few places. Will add complete info later, but for now, it's removed
* reorganize and update existing HackRF documentation
* include changes suggested by martinling
* Update software support page
* fix typo
* Update acrylic case link
* docs: make adjustments based on feedback from epenelope
Previously we checked for OG support instead of r9 support because we
didn't yet have a way to tag firmware binaries with support for multiple
platforms.
During r9 hardware development it was thought that the MAX2839 would use
a different GPIO pin for chip select, but it ended up being the same pin
as is used for MAX2837 on other hardware revisions.
This takes the MAX283x abstraction a bit further and fixes a bug with
hackrf_debug -m.
The bootloader is configured by pin straps on certain pins. We use some
of those for other purposes in r9 which causes the bootloader to
misbehave if the device is reset from software. By switching these pins
from outputs to inputs just before reset this problem is avoided.
On the first spin of r9 one of the pins used for platform detection is
pulled up to VAA, not VCC, and VAA hasn't been switched on yet at the
time of platform detection. This results in r9 being misidentified as OG
from time to time.
As a temporary workaround until the next board spin, change the platform
from OG to r9 if it is detected as OG but has r9 pin straps.
Writing to the output bits in the TIMER3 external match register
resulted in intermittent failures that varied in likelihood from board
to board and from commit to commit for no apparent reason.
