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

doc

Browse source
This commit is contained in:
Philippe Teuwen 2020-05-02 23:11:49 +02:00
commit 0cb21c89c3
2 changed files with 10 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
armsrc/Standalone/readme.md
View file

@ -131,7 +131,7 @@ Remember only one can be selected at a time for now.
The final steps is to The final steps is to
- force recompilation of all code. ```make clean``` - force recompilation of all code. ```make clean```
- compile ```make -j8``` - compile ```make -j```
- flash your device - flash your device
- connect to your device - connect to your device
- press button long time to trigger ledshow and enter your new standalone mode - press button long time to trigger ledshow and enter your new standalone mode

13
doc/bt_manual_v10.md
View file

@ -55,7 +55,7 @@ https://github.com/RfidResearchGroup/proxmark3
To compile the client and firmware with FPC support, the easiest way is to To compile the client and firmware with FPC support, the easiest way is to
1. Copy the sample file: `Makefile.platform.sample` ⇒ `Makefile.platform` 1. Copy the sample file: `Makefile.platform.sample` ⇒ `Makefile.platform`
* `mv Makefile.platform.sample Makefile.platform` * `cp Makefile.platform.sample Makefile.platform`
2. Edit `Makefile.platform`, uncomment the line `#PLATFORM_EXTRAS=BTADDON` by removing the `#` 2. Edit `Makefile.platform`, uncomment the line `#PLATFORM_EXTRAS=BTADDON` by removing the `#`
3. Recompile the project: 3. Recompile the project:
* `make clean; make -j` * `make clean; make -j`
@ -113,10 +113,15 @@ http://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp
This requires to have compiled the client with Bluetooth support. This requires to have compiled the client with Bluetooth support.
Be sure your user has permissions to use Bluetooth
* On most distributions, you've to be part of group `bluetooth`: `sudo adduser $USER bluetooth` then log out and log in
* else, run the following commands as root : `sudo ...`
1. Find the MAC address of the Bluetooth add-on, named PM3_RDV4.0. 1. Find the MAC address of the Bluetooth add-on, named PM3_RDV4.0.
```sh ```sh
sudo hcitool scan hcitool scan
Scanning ... Scanning ...
aa:bb:cc:dd:ee:ff PM3_RDV4.0 aa:bb:cc:dd:ee:ff PM3_RDV4.0
``` ```
@ -136,7 +141,7 @@ restart it again after pairing.
If your OS doesn't prompt you for pairing, you can do it in command line, e.g. (again, replace with your addon MAC address): If your OS doesn't prompt you for pairing, you can do it in command line, e.g. (again, replace with your addon MAC address):
```sh ```sh
sudo bluetoothctl bluetoothctl
[bluetooth]# pairable on [bluetooth]# pairable on
[bluetooth]# scan on [bluetooth]# scan on
Discovery started Discovery started
@ -178,7 +183,7 @@ rfcomm is a deprecated tool which might be unavailable in your Linux distributio
1. Find the MAC address of the Bluetooth add-on, named PM3_RDV4.0. 1. Find the MAC address of the Bluetooth add-on, named PM3_RDV4.0.
```sh ```sh
sudo hcitool scan hcitool scan
Scanning ... Scanning ...
aa:bb:cc:dd:ee:ff PM3_RDV4.0 aa:bb:cc:dd:ee:ff PM3_RDV4.0
``` ```