greatscottgadgets / greatscottgadgets/hackrf
Hardware documentation improvements
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 8.1k
- Forks
- 1.7k
- Avg merge
- 15d 7h
- Merged PRs (30d)
- 1
Description
Preamble
After checking out portapack I got quite an inspiration to use hackrf portably. Since hackrf doesn't have powerful enough hardware to do for example digital voice processing, it has to be done on the external hardware.
I would like to keep it as portable as possible and this means not using usb, but instead hackrf's motherboard headers.
I am, to say at least, not an expert in modern electronics. Devices like hackrf, raspberry pi and some arduino-like boards, are my toys on the way to proper understanding, but it contributes to a lot of questions.
Main problem
Hardware documentation and especially pin headers usage lacks information about my use case. Things that would be cool to see:
- More information about pins. ADC0_2, VBUSCTRL, WAKEUP, VBAT(hackrf doesn't have battery), B1AUX13, BANK2F3M2 are making me confused 😅.
- What each major part actually does.
Actual questions
For some of them there are conjectures in my brain but it would cool to clarify them and maybe help create hardware FAQ section in documentation.
- What should be done to start rx or tx operation? Is just passing signals to ADC/DAC on P9 header enough?
- How can RF gains, baseband filter and sampling rate be set trough pin headers?
- What is CPLD used for in hackrf? (i actually don't know what it's practical applications in general and have hard time understanding)
- How does mixer rated to such wide frequency range work with transceiver rated only to 2.3-2.7ghz?
- What is the proper way to supply power for hackrf trough pin headers and where can be power taken on hackrf to supply it to pheripherials?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing hardware documentation for the pin headers, especially P9, and the listed signals such as ADC0_2, VBUSCTRL, WAKEUP, and VBAT. Trace the questions about CPLD, mixer, transceiver, RF control, and power connections, then define the documentation sections or FAQ entries needed to answer them.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, embedded-iot
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100