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

Merge pull request #1956 from wh201906/unit

Browse source 
Fix units
This commit is contained in:
Iceman 2023-04-07 10:56:02 +02:00 • committed by GitHub
commit dc24c4b6ac
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 31 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/ext_flash_notes.md
View file

@ -19,9 +19,9 @@ External 256kbytes flash is a unique feature of the RDV4 edition.
Flash memory is
* 256kb (0x40000= 262144)
* divided into 4 pages of 64kb (0x10000 = 65536)
* 4 pages divided into 16 sectors of 4kb (0x1000 = 4096), so last sector is at 0x3F000
* 256KB (0x40000= 262144)
* divided into 4 pages of 64KB (0x10000 = 65536)
* 4 pages divided into 16 sectors of 4KB (0x1000 = 4096), so last sector is at 0x3F000
Therefore a flash address can be interpreted as such:
```

42
doc/md/Use_of_Proxmark/4_Advanced-compilation-parameters.md
View file

@ -10,7 +10,7 @@
- [PLATFORM](#platform)
- [PLATFORM_EXTRAS](#platform_extras)
- [STANDALONE](#standalone)
- [256kb versions](#256kb-versions)
- [256KB versions](#256KB-versions)
- [Next step](#next-step)
@ -48,10 +48,10 @@ make SKIPBT=1
## Firmware
^[Top](#top)
By default, the firmware is of course tuned for the Proxmark3 RDV4 device, which has built-in support for 256kb onboard flash SPI memory, Sim module (smart card support), FPC connector.
By default, the firmware is of course tuned for the Proxmark3 RDV4 device, which has built-in support for 256KB onboard flash SPI memory, Sim module (smart card support), FPC connector.
These features make it very different from all other Proxmark3 devices, there is non other like this one.
**Recommendation**: if you don't have a RDV4, we strongly recommend your device to have at least a 512kb arm chip, since this repo is crossing 256kb limit. There is still a way to skip parts to make it fit on a 256kb device, see below.
**Recommendation**: if you don't have a RDV4, we strongly recommend your device to have at least a 512KB arm chip, since this repo is crossing 256KB limit. There is still a way to skip parts to make it fit on a 256KB device, see below.
If you need to tune things and save the configuration, create a file `Makefile.platform` in the root directory of the repository, see `Makefile.platform.sample`.
For an up-to-date exhaustive list of options, you can run `make PLATFORM=`.
@ -73,7 +73,7 @@ The MCU version (256 or 512) will be detected automatically during flashing.
Known issues:
* 256kb Arm chip devices: The compiled firmware image from this repo may/will be too large for your device.
* 256KB Arm chip devices: The compiled firmware image from this repo may/will be too large for your device.
* PM3 Evo: it has a different led/button pin assignment. It tends to be messed up.
* Proxmark Pro: it has different fpga and unknown pin assignments. Unsupported.
@ -136,10 +136,10 @@ Here are the supported values you can assign to `STANDALONE` in `Makefile.platfo
By default `STANDALONE=LF_SAMYRUN`.
## 256kb versions
## 256KB versions
^[Top](#top)
If you own a Proxmark3 Easy with only 256kb, you can use a few definitions to help you getting a smaller firmware.
If you own a Proxmark3 Easy with only 256KB, you can use a few definitions to help you getting a smaller firmware.
First thing is of course to use the `PLATFORM=PM3GENERIC`.
Adding `PLATFORM_SIZE=256` will provoke an error during compilation of the recovery image if your image is too big, so you can detect the problem before trying to flash the Proxmark3, e.g.
@ -155,22 +155,22 @@ a series of `SKIP_*` allow to skip some of the functionalities and to get a smal
| Definitions | Rough estimation of the saved space |
|---------------------|-------------------------------------|
|STANDALONE= | 3.6kb
|SKIP_LF=1 | 25.8kb
|SKIP_HITAG=1 | 24.2kb
|SKIP_EM4x50=1 | 2.9kb
|SKIP_ISO15693=1 | 3.2kb
|SKIP_LEGICRF=1 | 3.9kb
|SKIP_ISO14443b=1 | 3.7kb
|SKIP_ISO14443a=1 | 63.0kb
|SKIP_ICLASS=1 | 10.5kb
|SKIP_FELICA=1 | 4.0kb
|SKIP_NFCBARCODE=1 | 1.4kb
|SKIP_HFSNIFF=1 | 0.5kb
|SKIP_HFPLOT=1 | 0.3kb
|SKIP_ZX8211=1 | 0.3kb
|STANDALONE= | 3.6KB
|SKIP_LF=1 | 25.8KB
|SKIP_HITAG=1 | 24.2KB
|SKIP_EM4x50=1 | 2.9KB
|SKIP_ISO15693=1 | 3.2KB
|SKIP_LEGICRF=1 | 3.9KB
|SKIP_ISO14443b=1 | 3.7KB
|SKIP_ISO14443a=1 | 63.0KB
|SKIP_ICLASS=1 | 10.5KB
|SKIP_FELICA=1 | 4.0KB
|SKIP_NFCBARCODE=1 | 1.4KB
|SKIP_HFSNIFF=1 | 0.5KB
|SKIP_HFPLOT=1 | 0.3KB
|SKIP_ZX8211=1 | 0.3KB
So for example, at the time of writing, this is a valid `Makefile.platform` compiling an image for 256k:
So for example, at the time of writing, this is a valid `Makefile.platform` compiling an image for 256KB:
```
PLATFORM=PM3GENERIC
PLATFORM_SIZE=256