command doesn't exist
]]>for flash the proxmark3 rdv401 is ok ?
i need help i tried to flash the proxmark3 rdv from rdv40-64-20201119- to
pm3-bin r763 and after this is not appear to any com port i try it in linux the same the leds A and C are on and they blinks the j-link-v8 is not aviable
i see how you doing with ST-Link V2 ( http://wiki.yobi.be/wiki/Proxmark ) but me i need the to flash this version C:\proxmark3\pm3-bin-756 (cdc+lua)\pm3-bin-756\firmware_win
there it have many images fullimage.elf ,fpgaimage.elf, osimage.elf and in \pm3-bin-756\firmware_win\bootrom folder bootrom.elf
question 1
what is difference of ,fpgaimage.elf, osimage.elf, fullimage.elf i use the fullimage.elf ?for full image and bootrom.elf for boot ?
question 2.
the elf files they supported with telenet only or i can convert to bin?
is more easy for me to use the proxmark3 rdv4 with proxmark tool couse i am beginner to commands than to use the precompile software and drivers like rdv40-64-20201119
]]>Proxmark Client By El Gaucho De La Livida Palude Version 1.7 ??
1.7? ( or is there an even newer one? )
2
Can anyone give me the latest compiled version
pm3-bin-2.5.0
Or maybe newer
I would be very grateful for any help in advance thanks a lot.
p/s If this is important, I work with Windows 10 (64bit) and I have proxmark3 Easy.
]]>Until you get your compile environment figured out this link has a bit newer compiled stuff. http://www.proxmark.org/forum/viewtopic.php?id=3975
]]>Please I have doubts of whether or not to upgrade my proxmark3.
https /store.ryscc. com/blogs/news/upgrading-your-proxmark3-to-v2-3-over-usb
]]>Just out of curiosity, do all builds come with a new FW/bootrom to flash?
*Newbie trying to learn. I did read the wiki but it's still confusing.
Edit
Edit 2: Yes to above I think i get it.
]]>I'm a little stuck here. I can't seem to upgrade my elechouse V2.
I ran two different flashers, the easy flasher and the one included in 2.5 but my unit keeps saying:
C:\zip\pm3-bin-2.5.0\win32 (client+GUI)>proxmark3 com3
Prox/RFID mark3 RFID instrument
bootrom: /-suspect 2015-11-19 10:08:02
os: /-suspect 2015-11-19 10:08:09
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8
uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 169916 bytes (32%). Free: 354
372 bytes (68%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>
It's :
bootrom: /-suspect 2015-11-19 10:08:02
os: /-suspect 2015-11-19 10:08:0
So it hasn't upgraded to 2016...
Any clues why?
]]>The breaking changes made the os image redundant.
In v2.x.x you only need to flash bootrom and fullimage. *Simpler*
but in last pm3-bin-2.5.0 there is no OS image.
why? just need to make fullimage and boot rom since 2.0?
When will be the upgrade of pm3-bin to version 2.6.0.
Could you put the hardnested and do something else. As a suggestion
Thanks
]]>