github/RRG-Proxmark3
1
0
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2025-08-21 13:53:55 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

typos

Browse source
This commit is contained in:
Philippe Teuwen 2020-10-23 01:24:54 +02:00
commit 18a6d3e92a
27 changed files with 55 additions and 54 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/md/Development/Coverity-Scan-Config-and-Run.md
View file

@ -1,6 +1,6 @@
## Coverity Scan Config & Run
Download the Coverity Scan Self-buld and install it.
Download the Coverity Scan Self-build and install it.
You will need to configure ARM-NON-EABI- Compiler for it to use:
Configure

2
doc/md/Installation_Instructions/Linux-Installation-Instructions.md
View file

@ -73,7 +73,7 @@ git clone https://github.com/RfidResearchGroup/proxmark3.git
# Check ModemManager
### ⚠️ Very important ⚠️
make sure ModemManager will not interfer, otherwise it could brick your Proxmark3!
make sure ModemManager will not interfere, otherwise it could brick your Proxmark3!
Read carefully [this page about ModemManager](ModemManager-Must-Be-Discarded.md) and follow its instructions.
# Check connection

8
doc/md/Installation_Instructions/ModemManager-Must-Be-Discarded.md
View file

@ -8,7 +8,7 @@ ModemManager is pre-installed on many different Linux distributions, very probab
It's intended to prepare and configure the mobile broadband (2G/3G/4G) devices, whether they are built-in or dongles.
Some are serial, so when the Proxmark3 is plugged and a `/dev/ttyACM0` appears, ModemManager attempts to talk to it to see if it's a modem replying to AT commands.
Now imagine what happens when you're flashing your Proxmark3 and ModemManager suddently starts sending bytes to it at the same time...
Now imagine what happens when you're flashing your Proxmark3 and ModemManager suddenly starts sending bytes to it at the same time...
Yes it makes the flashing failing. And if it happens while you're flashing the bootloader, it will require a JTAG device to unbrick the Proxmark3.
ModemManager is a threat for the Proxmark3, but also for many other embedded devices, such as some Arduino platforms.
@ -35,7 +35,7 @@ sudo systemctl disable ModemManager
# Solution 3: use filtering udev rules
If you *really* need ModemManager, e.g. for your 4G device, you'll have to use some filtering rules to make sure it doesn't interfer with the Proxmark3.
If you *really* need ModemManager, e.g. for your 4G device, you'll have to use some filtering rules to make sure it doesn't interfere with the Proxmark3.
Once you have cloned the Proxmark3 repository, you can run `make udev` to install udev rules that will tell ModemManager to not look at your Proxmark3.
@ -89,7 +89,7 @@ sudo journalctl -f|grep "ModemManager.*\[filter\]"
```
Now plug in the Proxmark 3.
If ModemManager interfers, you'll get logs like this:
If ModemManager interferes, you'll get logs like this:
```
ModemManager[xxxxx]: <debug> [filter] (tty/ttyACM0): port allowed: cdc-acm interface reported AT-capable
```
@ -108,7 +108,7 @@ sudo mmcli -G ERR
# I didn't read carefully this page and now my Proxmark3 is not responding
First of all, follow the instructions above to make sure ModemManager will not interfer with the Proxmark3 anymore.
First of all, follow the instructions above to make sure ModemManager will not interfere with the Proxmark3 anymore.
Now there are two possibilities:

4
doc/md/Installation_Instructions/Troubleshooting.md
View file

@ -66,7 +66,7 @@ Another possibility is if, when using the button for entering bootloader mode, t
### Determine if the bootloader was damaged or only the main OS image
Unplug, press the Proxmark3 button and keep it pressed when you plug it on USB. If the red LEDs show a "off/on/off/on" pattern, you're goot, you manually entered into the bootloader mode.
Unplug, press the Proxmark3 button and keep it pressed when you plug it on USB. If the red LEDs show a "off/on/off/on" pattern, you're good, you manually entered into the bootloader mode.
On new bootloaders, you can release the button. If the pattern disappears, you're on an older bootloader and you've to do it again and keep the button pressed during all the flashing operation.
Once in bootloader mode, flash the main image.
@ -200,7 +200,7 @@ brew remove proxmark3
brew reinstall proxmark3
```
On Ubuntu 16.04 (xenial) you should either conside a later release or you can install a later toolchain.
On Ubuntu 16.04 (xenial) you should either consider a later release or you can install a later toolchain.
sample error output:

2
doc/md/Installation_Instructions/Windows-Installation-Instructions.md
View file

@ -150,7 +150,7 @@ Note that it may take a quite long time for a freshly plugged Proxmark3 to be vi
Now you're ready to follow the [compilation instructions](/doc/md/Use_of_Proxmark/0_Compilation-Instructions.md).
## Color text on windows 10
In later versions of windows 10 you may be able to get color to work by setting this registery key
In later versions of windows 10 you may be able to get color to work by setting this registry key
```
[HKEY_CURRENT_USER\Console]
"VirtualTerminalLevel"=dword:00000001

2
doc/md/Use_of_Proxmark/2_Configuration-and-Verification.md
View file

@ -25,7 +25,7 @@ Set all t55xx settings to defaults (will set all 4 at once)
To make sure you got the latest sim module firmware.
_Lastest version is v3.11_
_Latest version is v3.11_
```
[usb] pm3 --> hw status