Custom firmware for the HackRF+PortaPack H1/H2
Go to file
2023-03-13 23:27:44 +01:00
.github Update version.txt 2022-12-29 15:35:54 +13:00
docs Update index.html 2020-06-09 00:13:23 +02:00
firmware aligned OPT to the right 2023-03-13 23:27:04 +01:00
flashing Included DLL files (#654) 2022-05-21 12:11:03 +12:00
hackrf@ae71cb5b7a Level meter (#827) 2023-03-10 14:25:38 +01:00
hardware Updated models 2020-10-07 20:44:09 +02:00
sdcard Merge branch 'eried:next' into next 2023-02-22 23:24:38 +00:00
.dockerignore Add file 2023-02-19 08:35:19 +01:00
.gitignore Included DLL files (#654) 2022-05-21 12:11:03 +12:00
.gitmodules Update hackrf 2020-06-14 22:14:14 +02:00
.travis.yml Format 2023-02-19 08:35:25 +01:00
CMakeLists.txt Fixed typo in cmake 2022-04-03 08:50:08 +12:00
docker-compose-nogit.yml Add file 2023-02-19 08:35:19 +01:00
docker-compose.yml Add file 2023-02-19 08:35:19 +01:00
dockerfile Format 2023-02-19 08:35:25 +01:00
dockerfile-alpine Add file 2023-02-19 08:35:19 +01:00
dockerfile-nogit Format 2023-02-19 08:35:25 +01:00
dockerfile-nogit-alpine Add file 2023-02-19 08:35:19 +01:00
LICENSE Create LICENSE 2021-11-17 12:15:52 +01:00
LICENSE.GPL-2.0-or-later license-correction 2021-11-17 10:15:36 +01:00
LICENSE.md removed duplicate file, README changes 2021-12-01 17:32:13 -05:00
README.md Update README.md 2023-01-25 15:34:09 +01:00

PortaPack Mayhem

Build Status Nightly Release CodeScene Code Health GitHub All Releases GitHub Releases Docker Hub Pulls Discord Chat Check bounties!

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.

PortaPack H2+HackRF+battery (clone) with a custom 3d printed case

Quick overview

If you are new to HackRF+PortaPack+Mayhem, there is an awesome introductory video by Tech Minds available:

Setup and overview

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 pack, that includes everything you need. Sadly, the people making the H2 never made the updated schematics available (against the terms of the license).

✔️ Another popular option is the clone of the PortaPack H1.

⚠️ 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:

image

⚠️ 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:

image

Where is the latest version?

The current stable release is on the GitHub release (latest by date) page. Follow the instructions you can find in the release description. The latest (nightly) release can be found here.

How can I collaborate

You can write documentation, fix bugs and answer issues or add new functionality. Please 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 colaborating 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.

Contributors

To support the people behind the hardware, please buy a genuine HackRF and PortaPack.

As a last option, if you want to send money directly to me for getting more boards, antennas and such:

paypal

What if I really want something specific?

If what you need can be relevant in general, you can request a feature.

You can create a bounty and invite people to your own bounty. This will incentivize coders to work on a new feature, solving a bug or even writting documentation. Start a bounty by creating or choosing an existing issue. Then, go to Bountysource and post a bounty using the link to that specific issue.

Promote your bounty over our Discord by clicking the chat badge on top.

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.