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 2016-06-26 15:05:16

craycray
Contributor
Registered: 2016-06-26
Posts: 3

[solved] PM3 bricked?

Hi,

I was flashing my firmware yesterday and after flashing the bootrom the PM3 stopped working... even though no errors occurred!

For reference I was following the tutorial here:
https://github.com/Proxmark/proxmark3/w … DC_Flasher

So when going for step 22 the flasher kept waiting for PM3 to show up:

% ls /dev/cu*
/dev/cu.Bluetooth-Incoming-Port	/dev/cu.usbmodem1411

% ./client/proxmark3 /dev/cu.usbmodem1411
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: master/v1.1.0-80-g45dda9f-suspect 2015-01-02 21:33:16
#db# os: master/v1.1.0-80-g45dda9f-suspect 2015-01-02 21:33:16
#db# HF FPGA image built on 2014/ 6/19 at 21:26: 2
Prox/RFID mark3 RFID instrument

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 0 bytes ( 0). Free: 262144 bytes (100).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3> lf read
#db# buffer samples: 81 80 81 80 81 80 81 80 ...
proxmark3> quit

% ./client/flasher /dev/cu.usbmodem1411 -b bootrom/obj/bootrom.elf
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 (0x00000b68->0x00000b68) [RWX] @0x298

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: bootrom/obj/bootrom.elf
 0x00100000..0x001001ff [0x200 / 1 blocks]. OK
 0x00100200..0x00100d67 [0xb68 / 6 blocks]...... OK

Resetting hardware...
All done.

Have a nice day!
% ./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 (0x000296b8->0x000296b8) [R X] @0x94
1: V 0x00200000 P 0x0012b6b8 (0x00001a38->0x00001a38) [RW ] @0x2974c
Note: Extending previous segment from 0x296b8 to 0x2b0f0 bytes

Waiting for Proxmark to appear on /dev/cu.usbmodem1411.............[ad eternum]

If I connect the PM3 to my computer, with or without holding the button, the yellow and red LEDs are lit.

Please advise if my PM3 is bricked, and if so, what was my mistake so I can avoid it in the future...

Thank you!

EDIT: For reference here's the version I cloned

% git show
commit 83f11ccf729655f17c92b4cf9ae4e10278f8b2e3
Merge: 6fcb5dd fdcfbdc
Author: pwpiwi <pwpiwi@users.noreply.github.com>
Date:   Wed Jun 8 16:20:11 2016 +0200

    Merge pull request #181 from raburton/tune

    add l/h option to hw tune and optimize order of tuning

Last edited by craycray (2016-06-26 20:08:57)

Offline

#2 2016-06-26 20:09:37

craycray
Contributor
Registered: 2016-06-26
Posts: 3

Re: [solved] PM3 bricked?

solved with the advice from iceman in this thread:

http://www.proxmark.org/forum/viewtopic.php?id=3203

OP had the exact same problem as I did

Last edited by craycray (2016-06-26 20:09:57)

Offline

Board footer

Powered by FluxBB