proxmark3/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md

100 lines
3.1 KiB
Markdown
Raw Normal View History

2019-05-06 01:53:58 +08:00
# Compilation instructions
2019-07-12 07:48:39 +08:00
## Tuning compilation parameters
The client and the Proxmark3 firmware should always be in sync.
Nevertheless, the firmware can be tuned depending on the Proxmark3 platform and options.
Indeed, the RRG/Iceman fork can be used on other Proxmark3 hardware platforms as well.
Via some definitions, you can adjust the firmware for a given platform, but also to add features like the support of the Blue Shark add-on or to select which standalone mode to embed.
To learn how to adjust the firmware, please read [Advanced compilation parameters](/doc/md/Use_of_Proxmark/4_Advanced-compilation-parameters.md).
2019-05-06 01:53:58 +08:00
## Get the latest commits
```sh
cd proxmark3
git pull
```
## Clean and compile everything
```sh
make clean && make all
```
2020-09-15 23:36:07 +08:00
### if you got an error
Read the [troubleshooting guide](/doc/md/Installation_Instructions/Troubleshooting.md),
For instance, on WSl-1 you usually get the _libQt5Core.so.5 not found_ message
[solution](/doc/md/Installation_Instructions/Troubleshooting.md#libQt5Coreso5-not-found)
2019-09-04 04:54:42 +08:00
## Install
This is an optional step. If you do
```sh
sudo make install
```
Then the required files will be installed on your system, by default in `/usr/local/bin` and `/usr/local/share/proxmark3`.
Maintainers can read [this doc](../Development/Maintainers.md) to learn how to modify installation paths via `DESTDIR` and `PREFIX` Makefile variables.
The commands given in the documentation assume you did the installation step. If you didn't, you've to adjust the commands paths and files paths accordingly,
e.g. calling `./pm3` or `client/proxmark3` instead of just `pm3` or `proxmark3`.
2019-05-06 01:53:58 +08:00
## Flash the BOOTROM & FULLIMAGE
2019-09-10 01:55:55 +08:00
In most cases, you can run the following script which try to auto-detect the port to use, on several OS:
2019-05-06 01:53:58 +08:00
2019-09-10 01:55:55 +08:00
```sh
pm3-flash-all
```
For the other cases, specify the port by yourself. For example, for a Proxmark3 connected via USB under Linux (adjust the port for your OS):
2019-05-06 01:53:58 +08:00
2019-09-04 04:54:42 +08:00
```sh
2019-09-10 01:55:55 +08:00
proxmark3 /dev/ttyACM0 --flash --unlock-bootloader --image bootrom.elf --image fullimage.elf
2019-09-04 04:54:42 +08:00
```
2019-09-10 01:55:55 +08:00
The firmware files will be searched in the expected locations (installed files, working repo files, user folder, etc.). You can also specify their location:
```sh
pm3-flash -b /tmp/my-bootrom.elf /tmp/my-fullimage.elf
```
or
2019-09-04 04:54:42 +08:00
2019-05-06 01:53:58 +08:00
```sh
2019-09-10 01:55:55 +08:00
proxmark3 /dev/ttyACM0 --flash --unlock-bootloader --image /tmp/my-bootrom.elf --image /tmp/my-fullimage.elf
2019-05-06 01:53:58 +08:00
```
2019-07-12 07:48:39 +08:00
## Run the client
2019-09-04 04:54:42 +08:00
In most cases, you can run the script `pm3` which try to auto-detect the port to use, on several OS.
2019-07-12 07:48:39 +08:00
For the other cases, specify the port by yourself. For example, for a Proxmark3 connected via USB under Linux:
2019-09-10 01:55:55 +08:00
Here, for example, for a Proxmark3 connected via USB under Linux (adjust the port for your OS):
```sh
2019-09-04 04:54:42 +08:00
proxmark3 /dev/ttyACM0
```
or from the local repo
```sh
client/proxmark3 /dev/ttyACM0
```
2019-05-06 01:53:58 +08:00
## Next steps
For the next steps, please read the following pages:
* [Validating proxmark client functionality](/doc/md/Use_of_Proxmark/1_Validation.md)
* [First Use and Verification](/doc/md/Use_of_Proxmark/2_Configuration-and-Verification.md)
2019-05-06 02:05:02 +08:00
* [Commands & Features](/doc/md/Use_of_Proxmark/3_Commands-and-Features.md)
2019-05-06 01:53:58 +08:00