Proxmark3 community

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.

Announcement

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.

#1 2015-04-21 18:54:40

leftp
Member
Registered: 2015-04-21
Posts: 4

Unable to flash Proxmark - Error writing block

Hello there,
I recently acquired a proxmark board which i upgraded to the new CDC interface. Everything was working fine for a couple of months until i recently updated my clone of the repo and tried reflashing the card. Since then im getting an Error writing block 240 of 385 when i try to flash the full image file. The reason i was trying to reflash my board was because with the previous version i had i was doing some LF replaying / spoofing and everything was working fine. After the update, i can not in any way replay a cloned EM410 tag.

Below are the details of the board

proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: master/v2.0.0-37-gcb8220e-suspect 2015-04-20 12:49:57
#db# os: master/v2.0.0-37-gcb8220e-suspect 2015-04-15 14:44:49
#db# HF FPGA image built on 2015/03/09 at 08:41:42
uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

Any advise would be greatly appreciated

Offline

#2 2015-04-21 18:55:43

leftp
Member
Registered: 2015-04-21
Posts: 4

Re: Unable to flash Proxmark - Error writing block

I forgot to attach the full error iam getting:

test@test:~/tools/proxmark3$ sudo ./client/flasher /dev/cu.usbmodem1411 ./armsrc/obj/fullimage.elf
Loading ELF file './armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002d673->0x0002d673) [R X] @0x98
1: V 0x00200000 P 0x0012f678 (0x00002a30->0x00002a30) [RWX] @0x2d710
Note: Extending previous segment from 0x2d673 to 0x300a8 bytes
Note: 0x5-byte hole created

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on /dev/cu.usbmodem1411....... Found.

Flashing...
Writing segments for file: ./armsrc/obj/fullimage.elf
0x00102000..0x001320a7 [0x300a8 / 385 blocks]................................................................................................................................................................................................................................................Error: Unexpected reply 0x00fe (expected ACK)
ERROR
Error writing block 240 of 385

Offline

#3 2015-04-21 19:32:22

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: Unable to flash Proxmark - Error writing block

don't know if you need the fullimage.elf anymore..

If you have the latest source then you should be fine with the bootrom.elf and osimage.elf...

Offline

#4 2015-04-22 08:11:26

leftp
Member
Registered: 2015-04-21
Posts: 4

Re: Unable to flash Proxmark - Error writing block

Thanks for the reply iceman.
The bootrom flash finishes fine. However the osimage returns the same flashing error. 
Do you think i messed up something and should grab a JTAG? Basically im more interested as to why with previous versions i was able to fully emulate the tag and currently the em410xsim stops the moment i started it...

Thanks

Offline

#5 2015-04-22 08:35:53

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: Unable to flash Proxmark - Error writing block

Did you compile the latest bootrom?!?  Since there was breaking changes to the image layout,  you must use the latest flasher with the latest bootrom & osimage...

Offline

#6 2015-04-22 09:45:17

leftp
Member
Registered: 2015-04-21
Posts: 4

Re: Unable to flash Proxmark - Error writing block

Yep. The code is git pulled up to date. The bootrom flashes correctly:

Loading ELF file '../bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000b60->0x00000b60) [RWX] @0x298

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.

Flashing...
Writing segments for file: ../bootrom/obj/bootrom.elf
0x00100000..0x001001ff [0x200 / 1 blocks]. OK
0x00100200..0x00100d5f [0xb60 / 6 blocks]...... OK

Resetting hardware...
All done.

However when i try to flash the osimage i get the following

Loading ELF file '../armsrc/obj/osimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002d673->0x0002d673) [R X] @0x98
1: V 0x00200000 P 0x0012f678 (0x00002a30->0x00002a30) [RWX] @0x2d710
Note: Extending previous segment from 0x2d673 to 0x300a8 bytes
Note: 0x5-byte hole created

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on /dev/cu.usbmodem1411....... Found.

Flashing...
Writing segments for file: ../armsrc/obj/osimage.elf
0x00102000..0x001320a7 [0x300a8 / 385 blocks]................................................................................................................................................................................................................................................Error: Unexpected reply 0x00fe (expected ACK)
ERROR
Error writing block 240 of 385

I have tried with keeping the button pressed before connecting as well as without the button with the same results.

Offline

Board footer

Powered by FluxBB