| .github/ISSUE_TEMPLATE | ||
| armsrc | ||
| bootrom | ||
| client | ||
| common | ||
| doc | ||
| driver | ||
| fpga | ||
| include | ||
| liblua | ||
| recovery | ||
| tools | ||
| traces | ||
| uart | ||
| zlib | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| appveyor.yml | ||
| CHANGELOG.md | ||
| COMPILING.txt | ||
| covbuild.sh | ||
| covconfig.sh | ||
| flash-all.sh | ||
| flash-bootrom.sh | ||
| flash-fullimage.sh | ||
| HACKING.md | ||
| install.sh | ||
| LICENSE.txt | ||
| Makefile | ||
| Makefile.platform.sample | ||
| prox.png | ||
| proxmark3.sh | ||
| rdv40.txt | ||
| README.md | ||
Proxmark3 RDV4.0 Dedicated Github
This repo is based on iceman fork for Proxmark3. It is dedicated to bringing the most out of the new features for Proxmark3 RDV4.0 new hardware and design.
PROXMARK INSTALLATION AND OVERVIEW
What has changed?
On the hardware side:
- added flash memory 256kb.
- added smart card module
- added FPC connector
On the software side: quite a lot, see the Changelog file.
Development
This fork now compiles just fine on
- Windows/mingw environment with Qt5.6.1 & GCC 4.8
- Ubuntu 1404, 1510, 1604, 1804, 1904
- Mac OS X / Homebrew
- ParrotOS
- WSL (Windows subsystem linux) on Windows 10
- Docker container
If you intend to contribute to the code, please read the coding style notes first.
- Internal notes on Coverity Scan Config & Run.
- Internal notes on UART
- Internal notes on Frame format
- Internal notes on standalone mode
Why didn't you base it on official Proxmark3 Master?
The separation from official Proxmark3 repo gives us a lot of freedom to create a firmware/client that suits the RDV40 features. We don't want to mess up the official Proxmark3 repo with RDV40 specific code.
Proxmark3 GUI
The official PM3-GUI from Gaucho will not work. The new universal GUI will work. Proxmark3 Universal GUI Almost, change needed in order to show helptext when client isn't connected to a device.
Issues
Please see the Proxmark Forum and see if your issue is listed in the first instance Google is your friend :) Questions will be answered via the forum by Iceman and the team.
It's needed to have a good USB cable to connect Proxmark3 to USB. If you have stability problems (Proxmark3 resets, firmware hangs, especially firmware hangs just after start, etc.) - check your cable with a USB tester (or try to change it). It needs to have a resistance smaller or equal to 0.3 Ohm.
The end
- @herrmann1001 July 2018
- updated Feb 2019 @5w0rdfish
Donations
Nothing says thank you as much as a donation. So if you feel the love, do feel free to become a iceman patron. For some tiers it comes with rewards.
https://www.patreon.com/iceman1001
All support is welcome!