- C 71.4%
- C++ 20.1%
- Makefile 2.5%
- HTML 1.6%
- Assembly 1.1%
- Other 3.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
834076356e* VDL2 RX: VHF Data Link mode 2 receiver, ACARS per aircraft New external app (RX menu). Receives one VDL2 channel (136.975 MHz and the other European and North American ones): D8PSK at 10500 symbols/s, synced on the training sequence with the carrier offset taken from it, the header FEC, descrambling, RS(255,249) with erasures for the short last block, de-interleaving, HDLC and the X.25 FCS. The app lists aircraft by ICAO address with registration, flight and frame count (registration, model and operator from the ADS-B database when the frames don't carry them) and ground stations; the detail view shows frames by kind, the OOOI times and the last ACARS messages. Config: log to LOGS/VDL2.TXT, small font. * VDL2 RX: review fixes (thread start, M0 heap, detail rows) - start the baseband thread only after the filters are configured - keep at most 16 entries with 3 messages of 64 characters, for the M0 heap on a HackRF One; the log keeps the messages whole - the frame counts on two rows, so they fit 30 columns * VDL2 RX: Messages view, all ACARS texts of an aircraft in full The detail view gets a Messages button next to Back: a scrollable view (up/down, encoder) of every message of that aircraft, wrapped, with time and direction. The texts live in one store for the app, at most 32 messages and 4 KiB, oldest out first, instead of shortened copies in each entry; the view reads it in place. * VDL2 RX: no copyright line in the new files * VDL2 RX: detail view, two fields a row (ICAO and Reg, Flight and Type) |
||
| .github | ||
| .vscode | ||
| docs | ||
| firmware | ||
| flashing | ||
| hackrf@b80cddb56b | ||
| hardware | ||
| scripts/toolchain | ||
| sdcard | ||
| tools | ||
| .clang-format | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| AGENT.md | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| docker-compose-nogit.yml | ||
| docker-compose.yml | ||
| dockerfile | ||
| dockerfile-alpine | ||
| dockerfile-nogit | ||
| dockerfile-nogit-alpine | ||
| dockerfile-nogit-arm | ||
| dockerize.sh | ||
| format-code.ps1 | ||
| format-code.sh | ||
| LICENSE | ||
| LICENSE.GPL-2.0-or-later | ||
| mbt | ||
| README.md | ||
| SECURITY.md | ||
PortaPack Mayhem
This is a fork of the Havoc firmware, which itself was a fork of the PortaPack firmware, an add-on for the HackRF. A fork is a derivate, in this case one that has extra features and fixes when compared to the older versions.
What is this?
If you are new to HackRF+PortaPack+Mayhem, check these:
Frequently Asked Questions
This repository expands upon the previous work by many people and aims to constantly add new features, bugfixes and generate documentation to make further development easier. Collaboration is always welcomed and appreciated.
What to buy?
✔️ 
✔️ A recommended one is this PortaPack H2, that includes everything you need with the plastic case "inspired" on this.
✔️ Some individuals lean towards the H2 with a metal enclosure, but its advantages remain debated. Share your insights on our wiki.
⚠️ Be cautious , ask the seller about compatibility with the latest releases. Look out for the description of the item, if they provide the firmware files for an older version or they have custom setup instructions, this means it might be NOT compatible, for example:
⚠️ If it looks too different, this might mean that they are using their own recipe, check the different models in our wiki. For example all the H3 and clones of that version use their own version of the firmware. They do not contribute the changes back and eventually you will be left with a device that nobody maintains:
Where is the latest version?
The current stable release is on the 
How can I collaborate
We warmly welcome your contributions! Please refer to our Contributing Guidelines for details.
You can write documentation, fix bugs and answer issues or add new functionality. Please also check the following guide with details.
Consider that the hardware and firmware has been created and maintain by a lot of people, so always try collaborating your time and effort first. For coding related questions, if something does not fit as an issue, please join our Discord by clicking the chat badge on top.
To support the people behind the hardware, please buy a genuine HackRF and PortaPack.
What if I really want something specific?
If what you need can be relevant in general, you can request a feature. Alternatively, go to our Discord by clicking the chat badge on top and discuss there.
What if I need help?
First, check the documentation. If you find a bug or you think the problem is related to the current repository, please open an issue.
You can reach the official community in Facebook, and our Discord by clicking the chat badge on top.