Proxmark3 community

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Bricked - error writing block 64

Hey

I updated my PM3 using the windows batch files but suddenly got this response:
Flashing...
Writing segments for file: ..\firmware_win\osimage.elf
0x00118000..0x0013027f [0x18280 / 194 blocks]................................................................Error: Unexpected reply 0x00fe (expected ACK)
ERROR
Error writing block 64 of 194
Press any key to continue . . .

When I now check hw version I got this result:
#db# Prox/RFID mark3 RFID instrument                 
#db# bootrom: /-suspect 2014-09-19 10:31:37                 
#db# os: /-suspect 2014-09-13 11:21:04                 
#db# HF FPGA image built on 2014/ 6/19 at 21:26: 2                 
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 

Flashing bootloader, FPGA, OS or full image does not work any more... Any advice? I don't have a jtag connector and am not that technical.

Thanks!!

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: Bricked - error writing block 64

It looks like you failed when updating the osimage,   then it is just to flash that one again.
but was it the fullfgpa image?  hm,  you should be able to run the bootrom flash indiviually.
then the fpga..   and last the os image..

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Thanks iceman but everything I do immediately exits with an error code. Only the os will try and take a while before it throws the error.

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

This is flashing bootrom
                ====================================
                FLASHING bootrom.elf, please wait...
                ====================================

Loading ELF file '..\firmware_win\bootrom\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 com3. Found.

Flashing...
Writing segments for file: ..\firmware_win\bootrom\bootrom.elf
0x00100000..0x001001ff [0x200 / 1 blocks]Error: Unexpected reply 0x00fe (expect
ed ACK)
ERROR
Error writing block 0 of 1
Press any key to continue . . .

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: Bricked - error writing block 64

Now you failed with the bootrom,  which is kind of bad.   Do you know something about JTAG?

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Not at all is that the only way forward?

If so, I probably need to buy one of those as I don't have a machine with a parallel port:

http://www.benl.ebay.be/itm/SEGGER-8-08-90-EMULATOR-J-LINK-EDU-/171229907986?pt=UK_BOI_Electrical_Components_Supplies_ET&hash=item27de190c12

or

http://www.benl.ebay.be/itm/ARM-Emulator-ARM-Programmer-USB-JTAG-Realview-Ulink2-II-Debug-Adapter-Cortex-/111303809714?pt=UK_Computing_Other_Computing_Networking&hash=item19ea395ab2

Sorry for not linking, apparently I don't have the right to do that.

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

To be sure I bought the first one as this is referenced on the proxmark site as well

cupido

Member

Registered: 2013-03-16

Posts: 8

Re: Bricked - error writing block 64

Looks right, stijn. Let us know if you need further support to recover your pm3 when the Jtag arrives.

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Okay so I have the segger programmer by now. I followed the steps described https://code.google.com/p/proxmark3/downloads/detail?name=Compiling%20Proxmark%20source%20and%20firmware%20upgrading%20v1.pdf&can=2&q= but it gives error when I try to connect.

To explain:
- connected segger to usb port and tested the installation successfully
- connected the proxmark to other usb port
- connected cable from segger to proxmark
- got an error: could not perform target reset. Failed to connect.

Thanks!

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Anyone?

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: Bricked - error writing block 64

Sorry, can't help you here.

vivat

Contributor

Registered: 2010-10-26

Posts: 332

Re: Bricked - error writing block 64

Maybe this link or that one would help you...

Last edited by vivat (2014-11-18 07:01:07)

vivat

Contributor

Registered: 2010-10-26

Posts: 332

Re: Bricked - error writing block 64

Maybe this link or that one would help you...

Any updates?

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Thanks for the links, I had a look at them and think that this might be the issue: as it is saying that it doesn't reset on connect, I tried connecting without performing a reset. If it does that it says that it can't autodetect the CPU speed any more.

Also found this one but didn't get a reply yet how he solved it: http://www.proxmark.org/forum/viewtopic.php?id=1509

thefkboss

Contributor

Registered: 2008-10-26

Posts: 198

Re: Bricked - error writing block 64

where do you buy the segger (official or clone)
what version of segger software are you using??
the only importat steps to conect with the atmel are:

Click on the Target Interface tab.
Change the JTAG speed before init to 200 kHz.

Click on the CPU tab.
Select the Device radio button and select Atmel AT91SAM7S256 from the drop down list.
Change the Clock speed to Auto detection.

Apply and OK the changes.

after that press connect

open segger software with all connected.
it appears the segger version of your jtag in the console right?

be carefull with clones seggers if you used a new software version from (segger) it will break the segger boot and you need to reflash the segger jtag

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Hi, thanks for your interest!

I bought an official segger but EDU version so I don't get support from them they gave me 1 answer and than informed me that I'm not entitled for support but should use their forum. I'm starting to think that the chip is broken.

On their request I have replaced the auto reset by a halt but this is than going to the next error: auto detection of CPU clock frequency is not supported for this core. Failed to connect. I'm 100% sure of the speed settings and device settings.

I'm using j-flash project settings, starting a new project for it and than doing those settings, isn't that correct?

Thanks!

vivat

Contributor

Registered: 2010-10-26

Posts: 332

Re: Bricked - error writing block 64

Have you tried to replace the ARM? I would recommend to use 512kb version, it's pin compatible.

stijn

Contributor

Registered: 2014-11-09

Posts: 11

Re: Bricked - error writing block 64

Hey vivat no I didn't replace it yet. This is the last step I guess Now looking for help from Segger forum!

roquasroquas

Member

Registered: 2015-03-25

Posts: 3

Re: Bricked - error writing block 64

Stijn did you succeed in the meantime? If you're in the Netherlands, would you be able to help me unbrick my PM3? Thanks a lot!