Custom firmware for the HackRF+PortaPack H1/H2
Go to file
Erwin Ried 86c326ef12
Update README.md (#1937)
Adding a warning
2024-02-26 17:50:11 +01:00
.github Rename problem-upgrading-the-firmware.md to 03_problem-upgrading-the-firmware.md 2024-02-23 14:13:54 +01:00
docs Update repo links (#1750) 2024-01-10 21:13:43 +13:00
firmware Fixed existing dir check (#1933) 2024-02-25 08:28:44 +01:00
flashing Update repo links (#1750) 2024-01-10 21:13:43 +13:00
hackrf@f5dd48a5bc updated submodule (#1551) 2023-11-04 22:41:38 -05:00
hackrf-portapack Create cmake target ppfw (#1716) 2024-01-04 22:59:25 +01:00
hardware Fonts for pcb 2023-07-13 15:21:05 +02:00
sdcard Fix Recon Modulation/Bandwidth presets (#1913) 2024-02-17 19:24:11 +01:00
.clang-format Formatted code (#1007) 2023-05-19 08:16:05 +12:00
.dockerignore Add file 2023-02-19 08:35:19 +01:00
.gitignore fix shift back in screenshot and mayhem hub (#1910) 2024-02-18 00:44:31 +08:00
.gitmodules Update hackrf 2020-06-14 22:14:14 +02:00
CMakeLists.txt Speedup compilation using ccache package (#1832) 2024-01-30 20:55:59 +01:00
LICENSE Create LICENSE 2021-11-17 12:15:52 +01:00
LICENSE.GPL-2.0-or-later cleanup (#1036) 2023-05-22 21:14:35 +12:00
README.md Update README.md (#1937) 2024-02-26 17:50:11 +01: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 added lz4 to dockerfile 2023-03-27 16:22:20 +02:00
dockerfile-alpine added lz4 to dockerfile 2023-03-27 16:22:20 +02:00
dockerfile-nogit Remove ccache hack from dockerfiles (#1835) 2024-01-30 21:32:01 +01:00
dockerfile-nogit-alpine Remove ccache hack from dockerfiles (#1835) 2024-01-30 21:32:01 +01:00
dockerfile-nogit-arm Remove ccache hack from dockerfiles (#1835) 2024-01-30 21:32:01 +01:00
format-code.sh Format script (#1123) 2023-06-10 07:50:21 +12:00

README.md

[!WARNING] Recently, we have become aware of certain individuals distributing prepackaged packages of Mayhem for a fee, and we want to bring this to your attention to ensure the integrity and security of our project.

We would like to clarify that none of the contributors to Mayhem receive any monetary compensation for their efforts. All the work put into this project is driven by passion and hobby, and we are committed to providing the community with an open-source solution that remains free of charge.

IF YOU'VE PAID FOR MAYHEM OR ANY PREPACKAGED PACKAGES, YOU'RE BEING SCAMMED. Seek a refund from your card company and report the issue immediately. The only legitimate link leading to our repositories is the organization portapack-mayhem. Please ensure that any download or access to our software is done exclusively through these trusted sources.

PortaPack Mayhem

Nightly Release CodeScene Code Health GitHub All Releases GitHub Releases Docker Hub Pulls Discord Chat

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

What is this?

If you are new to HackRF+PortaPack+Mayhem, check these:

HackRF 101 : Everything You Need to Know to Get Started!

Beginner's Guide To The HackRF & Portapak With Mayhem What is the HackRF One Portapack H2+?

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.

✔️ Our friends at OpenSourceSDRLab give away five units every three months in our discord (check the badge on top) of their PortaPack H2, you can support them too by ordering.

✔️ 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 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.

Contributors

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.

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.

Bountysource has not been reliable lately, so until this changes, please DO NOT post a bounty there. 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.