Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
I just received my proxmark and was trying to flash it with the latest firmware.
So i downloaded the latest windows release (proxmark3_win_bins_beta.zip) and installed its drivers.
Then when issuing the command "flasher -b ..\bootrom\bootrom.elf" I get this
0x00100000..0x001001ff [0x200 / 2 blocks]Error: Unexpected reply 0x00fe (expected ACK)
ERROR
Error writing block 0 of 2
Do you have any ideas?
I really hope I won't need the JTAG connector in order to solve this....
Last edited by kramxorpprompet (2010-07-23 13:35:10)
Offline
Unfortunately I have the same issue - it doesnt matter if I build from sources with Linux or Windows - nor if I try to flash with Linux or Windows.
C:\Proxmark\pm3-bin-r486\Win32>flasher.exe osimage.elf
Loading ELF file 'osimage.elf'...
Loading usable ELF segments:
1: V 0x00110000 P 0x00110000 (0x00013284->0x00013284) [R X] @0xb8
2: V 0x00200000 P 0x00123288 (0x00002ce0->0x00002ce0) [RWX] @0x13340
Note: Extending previous segment from 0x13284 to 0x15f68 bytes
Note: 0x4-byte hole created
Waiting for Proxmark to appear on USB...
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
Found.
Flashing...
Writing segments for file: osimage.elf
0x00110000..0x00125f67 [0x15f68 / 352 blocks]..................................
..............................Error: Unexpected reply 0x00fe (expected ACK)
ERROR
Error writing block 64 of 352
Did you have a solution for this? I have it with SVN Build rev 649 ...
Offline
Pages: 1