Update to include USCUID-UL chips
Removed hidden block reading and writing from UFUID chips, as these do not have hidden blocks.
Signed-off-by: Akury83 <87064827+Akury83@users.noreply.github.com>
I think the last advice to backup is important, but the command does not work.
"mem dump p f flash_signature_dump o 262015 l 128" is now "mem dump -f flash_signature_dump -o 262015 -l 128". (OS: Iceman/master/v4.18218)
Signed-off-by: Benjamin Møller <37707273+LupusE@users.noreply.github.com>
In part 2 of the guide we create an EM4100 with an ID of 1122334455, and then check that we are successful. The sample show to check against however is for an EM4100 with ID of 0F0368568B.
- Removed dump of EM4100 with ID: 0F0368568B
- Added dump of EM4100 with ID: 1122334455
Signed-off-by: krislyon <kris.lyon@gmail.com>
This was implemented with a new pair of RPCs CMD_HF_MIFARE_READBL_EX and CMD_HF_MIFARE_WRITEBL_EX
these RPCs support all combinations of read/write commands, wakeup, and auth options so
in time can replace the other MFC read/write commands too reduce armsrc code size
and complexity.
Also added config parsing for the gdm cfg block when reading with hf mf gdmcfg and
explicitly with hf mf gdmparsecfg.
Works when the device is running either osimage or bootloader.
- New memory reading command in osimage and bootloader.
- Extended 'hw readmem' command with length parameter, file writing and hex viewer.
- Introduced '--dumpmem' option to proxmark3 executable to support dumping from bootloader.
Simple interactive examples:
hw readmem -f flashdump
hw readmem -l 1024
CLI example:
./pm3 --dumpmem flashdump.bin
Reading from arbitrary memory ranges can be unlocked using the 'raw' option.
