From febc5fe6e2debffd01ac06b390e08c76c394936f Mon Sep 17 00:00:00 2001 From: Philippe Teuwen Date: Sun, 27 Feb 2022 12:06:14 +0100 Subject: [PATCH] words --- doc/md/Installation_Instructions/Troubleshooting.md | 8 ++++---- doc/md/Use_of_Proxmark/0_Compilation-Instructions.md | 9 ++++----- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/doc/md/Installation_Instructions/Troubleshooting.md b/doc/md/Installation_Instructions/Troubleshooting.md index 7367bf08b..a69b0b9f9 100644 --- a/doc/md/Installation_Instructions/Troubleshooting.md +++ b/doc/md/Installation_Instructions/Troubleshooting.md @@ -47,16 +47,16 @@ Note that with the Bluetooth adapter, you *have to* use directly the client, and ## `pm3-flash*` stops and warns about up-to-date firmware images ^[Top](#top) -The Proxmark3 software and firmware is connected tightly. The strong recommendation is to use the client with a Proxmark3 device flashed with firmware images from same compilation time. -In the flash process you might get this message because the firmware images is downloaded or distributed and you have compiled your own client. Ie, not from same compilation time. -To minimize the risks the flasher warns about it and stops. +The Proxmark3 software and firmware is connected tightly. The strong recommendation is to use the client with a Proxmark3 device flashed with firmware images from same source version. +In the flash process you might get this message because the firmware images is downloaded or distributed and you have compiled your own client from a different source version. +To minimize the risks the flasher warns about it and stops. ``` Make sure to flash a correct and up-to-date version You can force flashing this firmware by using the option '--force' ``` -You need to add the `--force` param in order to continue flashing. +If you know what you are doing and want to proceed despite the mismatch, you need to add the `--force` param in order to continue flashing. ```sh pm3-flash-all --force diff --git a/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md b/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md index 8b03d016f..624c29630 100644 --- a/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md +++ b/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md @@ -110,17 +110,16 @@ proxmark3 /dev/ttyACM0 --flash --unlock-bootloader --image /tmp/my-bootrom.elf - ## flasher stops and warns you about firmware image ^[Top](#top) - -The Proxmark3 software and firmware is connected tightly. The strong recommendation is to use the client with a Proxmark3 device flashed with firmware images from same compilation time. -In the flash process you might get this message because the firmware images is downloaded or distributed and you have compiled your own client. Ie, not from same compilation time. -To minimize the risks the flasher warns about it and stops. +The Proxmark3 software and firmware is connected tightly. The strong recommendation is to use the client with a Proxmark3 device flashed with firmware images from same source version. +In the flash process you might get this message because the firmware images is downloaded or distributed and you have compiled your own client from a different source version. +To minimize the risks the flasher warns about it and stops. ``` Make sure to flash a correct and up-to-date version You can force flashing this firmware by using the option '--force' ``` -You will need to add the `--force` in order to continue flashing. +If you know what you are doing and want to proceed despite the mismatch, you need to add the `--force` param in order to continue flashing. ```sh pm3-flash-all --force